Live publish

Author: buck1ey

powerapps-docs/maker/model-driven-apps/create-edit-powerbi-report-dataset-components.md

@@ -5,7 +5,7 @@ author: paulinbar
 manager: kfollis
 ms.component: cds
 ms.topic: how-to
-ms.date: 09/16/2022
+ms.date: 09/21/2022
 ms.subservice: dataverse-maker
 ms.author: painbar
 search.audienceType: 
@@ -38,15 +38,17 @@ In this article, you'll learn how to do the following tasks:
 
 ## General limitations and restrictions
 
-* The **Power BI Extensions (Preview)** system solution must be installed. It is installed in new environments by default. Existing environments must install it manually from PPAC before importing solutions and creating Power BI components. To install the extension, go to the [Power Platform admin center](https://aka.ms/powerbi_extension).
-* Connection references to Power BI data sources aren't supported.
-* Only datasets created with the enhanced dataset model are supported. Paginated reports aren't supported.
+* The **Power BI Extensions (Preview)** system solution must be installed. In new environments it's installed by default. Existing environments must install it manually from PPAC before importing solutions and creating Power BI components. To install the extension, go to the [Power Platform admin center](https://aka.ms/powerbi_extension).
+* Only Power BI reports and datasets can be added to a solution. Only datasets created with the enhanced dataset model are supported. Any other artifact type is not supported (such as dashboard, dataflow, and paginated report).
+* Connection references to Power BI data sources aren't supported (for example, in composite models).
 * The Power BI dataset parameter types "Any" and "Binary" aren't supported in the Power BI integration with Power Apps solutions.
 * Sharing Power BI reports and datasets can only be done from Power BI (sharing the model driven app doesn't share the embedded report).
 * Recovery from workspace deletion isn't supported. Once the dedicated environment workspace has been deleted, you won't be able to add/import any Power BI component to the Power Apps environment.
 * Power Apps Application IDs aren't supported during public preview.
 * The Power Apps environment and the Power BI workspaces all need to be in the same geography. For more information, see [Considerations working with the Power Apps/Power BI integration](/power-bi/collaborate-share/service-power-bi-powerapps-integration-considerations#cross-geo-operations).
-* Environment life cycle operations aren't supported during public preview. More information: [Considerations working with the Power Apps/Power BI integration](/power-bi/collaborate-share/service-power-bi-powerapps-integration-considerations#environment-life-cycle-operations).  
+* Environment life cycle operations aren't supported during preview. More information: [Considerations working with the Power Apps/Power BI integration](/power-bi/collaborate-share/service-power-bi-powerapps-integration-considerations#environment-life-cycle-operations).
+* Dataverse for Teams environments are not supported.
+* National clouds are not currently supported.  
 
 ## Create Power BI report and dataset components
 

powerapps-docs/maker/portals/important-changes-deprecations.md

@@ -2,10 +2,9 @@
 title: Important upcoming changes and deprecations in Power Apps portals
 description: Learn about the important changes, including deprecations, coming soon to Power Apps portals.
 author: sandhangitmsft
-
 ms.topic: conceptual
 ms.custom: 
-ms.date: 09/09/2022
+ms.date: 09/21/2022
 ms.subservice: portals
 ms.author: sandhan
 ms.reviewer: ndoelman
@@ -37,10 +36,12 @@ At launch, users with the system administrator role along with [service admins](
 
 ## OAuth 2.0 implicit grant flow within your portal 
 
-Starting June 2022, [authorize endpoint](oauth-implicit-grant-flow.md#authorize-endpoint-details), [token endpoint](oauth-implicit-grant-flow.md#token-endpoint-details) using GET request, and using the default certificate for OAuth 2.0 implicit grant flow will be deprecated. No action is needed for newly created portals or for existing portals that don't use this feature. If you're already using this feature, you need to use the token endpoint POST request to get a secure access token to authorize the external APIs. 
+The [authorize endpoint](oauth-implicit-grant-flow.md#authorize-endpoint-details), [token endpoint](oauth-implicit-grant-flow.md#token-endpoint-details) using GET request, and using the default certificate for OAuth 2.0 implicit grant flow is deprecated. No action is needed for newly created portals or for existing portals that don't use this feature. If you're already using this feature, you need to use the token endpoint POST request to get a secure access token to authorize the external APIs.
 
 > [!NOTE]
-> All existing customers who are using this deprecated feature need to migrate to the supported method by October 2022.
+> - All existing customers who are using this deprecated feature need to migrate to the supported method by October 2022.
+> - For more information on using a custom certificate, go to [Using a custom certificate](oauth-implicit-grant-flow.md#custom-certificates).
+> - For sample code on using POST calls on the Token endpoint, go to [Token endpoint sample](oauth-implicit-grant-flow.md#token-endpoint-sample).
 
 ## List OData feed 
 
@@ -111,4 +112,4 @@ Starting with portals version [9.3.4.x](versions/version-9.3.4.x.md), the follow
 
 [Important changes (deprecations) coming in Power Apps, Power Automate, and customer engagement apps](/power-platform/important-changes-coming)
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/maker/portals/oauth-implicit-grant-flow.md

@@ -2,10 +2,9 @@
 title: Use OAuth 2.0 implicit grant flow within your portal
 description: Learn how to make client-side calls to external APIs and secure them by using OAuth implicit grant flow in your portal.
 author: gitanjalisingh33msft
-
 ms.topic: conceptual
 ms.custom: 
-ms.date: 05/11/2022
+ms.date: 09/21/2022
 ms.subservice: portals
 ms.author: gisingh
 ms.reviewer: ndoelman
@@ -25,7 +24,7 @@ OAuth 2.0 implicit grant flow supports [token](#token-endpoint-details) endpoint
 
 ## Custom certificates 
 
-Custom certificates provide another layer of security while using the OAuth 2.0 end point. Use the [Power Platform admin center](/admin/manage-custom-certificates) to upload the custom certificate. After uploading the custom certificate, you need to update site settings as below 
+Using the default certificate for OAuth 2.0 implicit grant flow is [deprecated](important-changes-deprecations.md#oauth-20-implicit-grant-flow-within-your-portal). You will need to use a custom certificate while using the OAuth 2.0 endpoint. Use the [Power Platform admin center](/admin/manage-custom-certificates) to upload the custom certificate. After uploading the custom certificate, you need to update site settings as below: 
 
 1. Go to [portal settings](manage-existing-portals.md#settings) and select **Site Settings**. 
 
@@ -161,4 +160,4 @@ This sample is an ASP.NET based project and is used to validate the ID token iss
 This sample shows how you can use the getAuthenticationToken function to fetch an ID token using the Token endpoint in Power Apps portals. The sample can be found here: [Token Endpoint sample](https://github.com/microsoft/PowerApps-Samples/blob/master/portals/TokenEndpoint.js).
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]