diff --git a/powerbi-docs/connect-data/service-connect-cloud-data-sources.md b/powerbi-docs/connect-data/service-connect-cloud-data-sources.md
index d81e45b9d6..2426c26ac1 100644
--- a/powerbi-docs/connect-data/service-connect-cloud-data-sources.md
+++ b/powerbi-docs/connect-data/service-connect-cloud-data-sources.md
@@ -64,9 +64,9 @@ Enabling the creation of new connections makes it easy to create separate sharea
 
 ## Default connection settings
 
-When connecting to a data source, your Microsoft Entra Single Sign-On (SSO) credentials are used by default.
+When connecting to a Fabric data source specifically, your Entra ID Single Sign-On (SSO) credentials are used by default.
 
-You can also use your shareable cloud connection settings instead of your SSO credentials to connect a semantic model to a data source, and thereby retain the settings you configured for that shareable cloud connection. This enables you to bind the data source to the shareable cloud connection, and override the default SSO connection for that data source.
+You can also use a shareable cloud connection instead of the default connection settings to connect a semantic model to a Fabric data source, and thereby apply the settings you configured for that shareable cloud connection, such as fixed credentials. This enables you to bind the data source to the shareable cloud connection, and override the default SSO connection for that data source.
 
 To select your shareable cloud connection instead of your default SSO settings, select the shareable cloud connection in the **Maps to:** drop-down for the data source to which you want your semantic model to connect, as shown in the following image:
 
diff --git a/powerbi-docs/enterprise/service-premium-per-user-faq.yml b/powerbi-docs/enterprise/service-premium-per-user-faq.yml
index bd39ac6096..0f9d69f895 100644
--- a/powerbi-docs/enterprise/service-premium-per-user-faq.yml
+++ b/powerbi-docs/enterprise/service-premium-per-user-faq.yml
@@ -94,7 +94,7 @@ sections:
         answer: |
           Anyone with either a Premium Per User (PPU) license or a Pro license can receive the subscription and any attachment it includes, if the attachment is the same for all users. Pro users can't view the content in the product portal. 
           
-          To add subscription capabilities that allow different data views for different recipients, a PPU license (or Premium capacity) is required. A PPU license doesn't allow sending e-mail subscriptions to external users. The content must be hosted in a Premium capacity to offer subscriptions to external users.  
+          To add subscription capabilities that allow different data views for different recipients, a Premium capacity is required.  
           
           Users without a license can't view datasets, and reports that are built on these datasets, that were created in a PPU workspace. For example, users without a license can't access a report created from a Power BI dataset in a PPU workspace, and published in a non-PPU workspace. Similarly, content in a PPU workspace shared using **Publish to Web** isn't accessible to unlicensed users.
           
diff --git a/powerbi-docs/natural-language/q-and-a-limitations.md b/powerbi-docs/natural-language/q-and-a-limitations.md
index 35d8b816eb..b214765a21 100644
--- a/powerbi-docs/natural-language/q-and-a-limitations.md
+++ b/powerbi-docs/natural-language/q-and-a-limitations.md
@@ -23,7 +23,7 @@ Power BI Q&A supports the following configurations of data sources in the Power
 - Live connect to SQL Server Analysis Services (with a gateway)
 - Power BI semantic models
 
-In each of these configurations, row-level security and object-level security is also supported.
+In each of these configurations, row-level security is also supported.
 
 #### DirectQuery support for Q&A (preview)
 
@@ -40,7 +40,10 @@ If the model contains a mix of data sources, we only index import columns or col
 
 ### Data sources not supported
 
-Power BI Q&A doesn't support Reporting Services.
+Power BI Q&A doesn't support the following configurations:
+
+- Object level security with any type of data source
+- Reporting Services 
 
 ## Tooling limitations