Merge branch 'master' into pehecke-accessibility-updates

Author: phecke

powerapps-docs/developer/common-data-service/best-practices/business-logic/avoid-batch-requests-plugin.md

@@ -31,7 +31,7 @@ search.app:
 
 ## Symptoms
 
-Due to their long-running nature, using <xref:Microsoft.Xrm.Sdk.Messages.ExecuteMultipleRequest> or <xref:Microsoft.Xrm.Sdk.Messages.ExecuteTransactionRequest> message request classes within the context of a plug-in or workflow activity expose sandbox-isolated plug-in types to the two-minute (12000ms) channel timeout exception and can degrade the user experience for synchronous registrations.
+Due to their long-running nature, using <xref:Microsoft.Xrm.Sdk.Messages.ExecuteMultipleRequest> or <xref:Microsoft.Xrm.Sdk.Messages.ExecuteTransactionRequest> message request classes within the context of a plug-in or workflow activity expose sandbox-isolated plug-in types to the two-minute (120000ms) channel timeout exception and can degrade the user experience for synchronous registrations.
 
 
 <a name='guidance'></a>

powerapps-docs/maker/canvas-apps/common-issues-and-resolutions.md

@@ -18,6 +18,9 @@ search.app:
 
 This article lists some common issues that you might encounter while using Power Apps. Where applicable, workarounds are provided.
 
+1. **AAD Conditional access with the policy "Require device to be marked as compliant" does not work in Power Apps for Windows** (July 30, 2020)
+   When setting the conditional access policy "Require device to be marked as compliant" in Azure Active Directory, users will face login errors with the message "The application contains sensitive information and can only be accessed from devices or client applications that meet your enterprise management compliance policy" and won't be able to access their Power Apps. As a workaround, please use your browser.
+
 1. **Connection.Connected returns the wrong value during OnStart in Power Apps for Windows** (July 21, 2020)
    While offline, **Connection.Connected** may wrongly return **true** immediately after starting an app in the Windows app. As a workaround, delay when the logic depending on it is executed by using a **Timer** control. 
 

powerapps-docs/maker/canvas-apps/embed-apps-dev.md

@@ -34,6 +34,11 @@ If you have an app you want to embed, the first step is to set parameters for th
 ```
 https://apps.powerapps.com/play/[AppID]?source=iframe
 ```
+For GCC users
+
+```
+https://apps.gov.powerapps.us/play[AppID]?source=iframe
+```
 
 > [!IMPORTANT]
 > As of August 2019, the URI format has changed from https://web.powerapps.com/webplayer to https://apps.powerapps.com/play. Please update any embedded iframes to use the new URI format. References to the previous format will be redirected to the new URI to ensure compatibility.

powerapps-docs/maker/canvas-apps/functions/function-form.md

@@ -14,16 +14,19 @@ search.audienceType:
 search.app: 
   - PowerApps
 ---
+
 # EditForm, NewForm, SubmitForm, ResetForm, and ViewForm functions in Power Apps
+
 View, edit, or create an item, save the contents, and reset the controls in an **[Edit form](../controls/control-form-detail.md)** control.
 
 ## Overview
+
 These functions change the state of the **Edit form** control.  The form control can be in one of these modes:
 
 | Mode | Description |
 | --- | --- |
 | **FormMode.Edit** |The form is populated with an existing record and the user can modify the values of the fields.  Once complete, the user can save the changes to the record. |
-| **FormMode.New** |The form is populates with default values and the user can modify the values of the fields.  Once complete, the user can add the record to the data source. |
+| **FormMode.New** |The form is populated with default values and the user can modify the values of the fields.  Once complete, the user can add the record to the data source. |
 | **FormMode.View** |The form is populated with an existing record but the user cannot modify the values of the fields. |
 
 ## Description
@@ -56,7 +59,7 @@ The **ResetForm** function resets the contents of a form to their initial values
 The **ViewForm** function changes the Form control's mode to **FormMode.View**. In this mode, the contents of the Form control's **[Item](../controls/control-form-detail.md)** property are used to populate the form.  The **SubmitForm** and **ResetForm** functions have no effect when in this mode.
 
 ### DisplayMode Property
-The current mode can be read through the **Mode** property.  The mode also determines the value of the **DisplayMode** property which can be used by data cards and controls within the form control.  Often, the data card's **DisplayMode** property will be set to **Parent.DisplayMode** (referencing the form) as will the control's **DisplayMode** property (referencing the data card): 
+The current mode can be read through the **Mode** property.  The mode also determines the value of the **DisplayMode** property, which can be used by data cards and controls within the form control.  Often, the data card's **DisplayMode** property will be set to **Parent.DisplayMode** (referencing the form) as will the control's **DisplayMode** property (referencing the data card): 
 
 | Mode | DisplayMode | Description |
 | --- | --- | --- |

powerapps-docs/maker/canvas-apps/use-native-cds-connector.md

@@ -7,7 +7,7 @@ ms.service: powerapps
 ms.topic: conceptual
 ms.custom: canvas
 ms.reviewer: tapanm
-ms.date: 07/09/2020
+ms.date: 07/29/2020
 ms.author: lanced
 search.audienceType: 
   - maker
@@ -109,7 +109,11 @@ To convert your app that uses the Dynamics 365 connector, you'll need to remove
 3. Add the connections to your data sources to the Common Data Service using the new data source selection experience. 
 
     > [!NOTE] 
-    > If you have connections to other environments (other than current), select the *Entity* category and then the *More* (...) option to change the environment. You can then select an entity from a different environment to add to your application. Cross-tenant connections don't work with the improved native connector. You'll need to use data integration to access data cross-tenant.
+    > - If you have connections to other environments (other than current), select the *Entity* category and then the *More* (...) option to change the environment. You can then select an entity from a different environment to add to your application. Cross-tenant connections don't work with the improved native connector. You'll need to use data integration to access data cross-tenant.
+    > - You need to meet one of the following requirements to be able to see an environment that you want to add the connection to:
+    >   - You're the **Owner** of the app, or the app is [shared](share-app.md) with you as a **Co-owner**.
+    >   - You're a member of at least one of these security roles: **Environment Admin**, **Environment Maker**, or **System Administrator**. For more information about the security roles in an environment, go to [Configure user security to resources in an environment](https://docs.microsoft.com/power-platform/admin/database-security).
+
 4.	Save your application.
 
 *Possible errors and suggestions*:

powerapps-docs/maker/portals/configure/media/use-simplified-authentication-configuration/issuer-url.png

@@ -5,7 +5,7 @@ author: sandhangitmsft
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 05/05/2020
+ms.date: 07/29/2020
 ms.author: sandhan
 ms.reviewer: tapanm
 ---
@@ -181,8 +181,24 @@ Configure the following site settings and password reset policy for your Azure A
 <br> To get the issuer URL:
 
    1. Open the sign-up and sign-in user flow you created in [step 1](#step-1---configure-the-azure-active-directory-b2c-application). For this step, you need to go to the Azure AD B2C tenant on [Azure portal](https://portal.azure.com).
-   1. Select **Run user flow**, and in the **Open** dialog box, select the URL at the top to open the configuration document. <br> The URL refers to the *OpenID Connect identity provider configuration document*, also known as the *OpenID well-known configuration endpoint*.
-   1. Copy the URL of the **Issuer** from the configuration document that opens in a new browser.  
+
+        ![Select the user flow](media/use-simplified-authentication-configuration/user-flow.png "Select the user flow")
+
+   1. Select **Run user flow**.
+
+        ![Run user flow](media/use-simplified-authentication-configuration/run-user-flow.png "Run user flow")
+
+   1. Select the OpenID configuration URL to open in a new browser window or a tab.
+
+        ![Select the OpenID configuration URL](media/use-simplified-authentication-configuration/select-openid-configuration-url.png "Select the OpenID configuration URL")
+        
+        The URL refers to the *OpenID Connect identity provider configuration document*, also known as the *OpenID well-known configuration endpoint*.
+
+   1. Copy the URL of the **Issuer** from the new browser window or tab.
+
+        ![Copy the Issuer URL](media/use-simplified-authentication-configuration/issuer-url.png "Copy the Issuer URL")
+
+        Ensure you copy only the URL, without the double quotation marks (*""*). <br> For example, `https://tailspintoysorg.b2clogin.com/acf18993-4325-4d94-b519-96824b0d06db/v2.0/`
 
 - **Client ID​** - Enter the **Application ID** of the Azure AD B2C application created in [step 1](#step-1---configure-the-azure-active-directory-b2c-application).