Merge branch 'master' into portals-1948172

Author: tapanm-MSFT

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/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*: