MicrosoftDocs · sericks007 · Jun 10, 2024 · Jun 9, 2024 · Jun 9, 2024 · Jun 10, 2024
@@ -19,7 +19,7 @@ contributors:
 
 Microsoft Power Platform and Dynamics 365 apps services operated by 21Vianet are designed to comply with regulatory requirements in China. The services are a physically separated environment of cloud services that's currently operated and transacted by a local operator, Shanghai Blue Cloud Technology Co., Ltd ("21Vianet"). This is a wholly owned subsidiary of Beijing 21Vianet Broadband Data Center Co., Ltd., located in China.
 
-The Dyamics 365 apps include Dynamics 365 Sales, Dynamics 365 Customer Service, Dynamics 365 Field Service, Dynamics 365 Marketing, and Dynamics 365 Project Service Automation.
+The Dynamics 365 apps include Dynamics 365 Sales, Dynamics 365 Customer Service, Dynamics 365 Field Service, Dynamics 365 Marketing, and Dynamics 365 Project Service Automation.
 
 ## Provisioning
 

@@ -29,10 +29,10 @@ Only tables that are enabled for system-managed access teams can be specified in
 
 If you change access rights in the team template, the changes are only applied to new system-managed access teams. The existing teams aren’t affected.  
 
-For information about how to create a team template, enable an table for system-managed access teams and how to customize the table form to add the team template, see [Create a team template and add to an table form](create-team-template-add-entity-form.md).
+For information about how to create a team template, enable a table for system-managed access teams and how to customize the table form to add the team template, see [Create a team template and add to a table form](create-team-template-add-entity-form.md).
 
 ### See also  
- [Create a team template and add to an table form](create-team-template-add-entity-form.md)   
+ [Create a team template and add to a table form](create-team-template-add-entity-form.md)   
  [Manage teams](manage-teams.md)    
 
 

@@ -119,7 +119,7 @@ There's a difference in the models for adding users to an environment with a Dat
 </tr>
 <tr>
 <td width="20%"> Dynamics 365 admin </td>
-<td width="50%"> These admins need to be owners or members of the team (because every team is linked to an Microsoft 365 group and the Dataverse for Teams environment will always be restricted for access to that Microsoft 365 group) to have System Administrator&ndash;level privileges to manage the health and maintenance of the environment. </td>
+<td width="50%"> These admins need to be owners or members of the team (because every team is linked to a Microsoft 365 group and the Dataverse for Teams environment will always be restricted for access to that Microsoft 365 group) to have System Administrator&ndash;level privileges to manage the health and maintenance of the environment. </td>
 <td width="30%"> System Administrator if they are an owner in the team; System Administrator and Teams Member if they are a member in the team. No access if they aren't an owner or member in the team. </td>
 </tr>
 <tr>

@@ -64,7 +64,7 @@ There are certain capabilities that continue to be unavailable in Unified Interf
 
 ## Read-only entities on Unified Interface
 
-There are certain entities that are currently read-only on Unified Interface. Users will not be able to make changes to these entity records within an Unified Interface app. We are working to make them editable in future releases.
+There are certain entities that are currently read-only on Unified Interface. Users will not be able to make changes to these entity records within a Unified Interface app. We are working to make them editable in future releases.
 
 > [!NOTE]
 > Some entities are being deprecated. More information: [Important changes (deprecations) coming](/dynamics365/customer-service/deprecations-customer-service#contracts-contract-line-items-and-contract-templates-entities-are-deprecated)

@@ -47,7 +47,7 @@ If an environment has already been deleted, you have a limited window of time to
 
 A cleanup mechanism in Power Platform automatically removes environments that aren't being used. After 90 days of inactivity, an environment is disabled. After 30 days, if no action is taken, the disabled environment is deleted. You have seven days to recover deleted environments.
 
-Only developer and [Dataverse for Teams environments](inactive-teams-environment.md) are affected by the actvity-based automatic cleanup.
+Only developer and [Dataverse for Teams environments](inactive-teams-environment.md) are affected by the activity-based automatic cleanup.
 
 > [!IMPORTANT]
 > You can't turn off this cleanup mechanism. However, you can review the last activity date for developer environments in the Power Platform admin center. 

@@ -132,7 +132,7 @@ Before you [create an email server profile](connect-exchange-server-on-premises.
 - HMA Application Id: The App ID for HMA-App. It can be found on the main page for the app registration of HMA-App.
 - Key Vault Uri: The URI of the Key Vault used for certificate storage. 
 - Key Vault KeyName: The certificate name used in Key Vault. 
-- KeyVault Application Id: The the app ID of the KV-App used by Dynamics to retrieve the certificate from Key Vault.
+- KeyVault Application Id: The app ID of the KV-App used by Dynamics to retrieve the certificate from Key Vault.
 - KeyVault Client Secret: The client secret for the KV-App used by Dynamics 365. 
 
   > [!div class="mx-imgBorder"] 

@@ -238,15 +238,15 @@ Confirm that search returns expected results. If results aren't accurate, you ca
   - Flows are initially disabled.
   - When enabling a flow, if an error is encountered, then open the flow in the designer to review errors and flow checker warnings. Adjust and resave the flow as needed.   
   - Flow run history won't be copied to the target environment.
-  - Flows with a "When a HTTP request is received" trigger has a new HTTP URL.
+  - Flows with a "When an HTTP request is received" trigger has a new HTTP URL.
   - If the source environment was a default environment, then integrating services like SharePoint, Excel, Teams, Power BI, and OneDrive continue to point at any related flows in the source environment. Consider if those integration flows can remain in the source default environment. Remove any integration flows from the target environment that stays behind in the source default environment.
 
 Action items:
 1. Review the flows in the target environment to ensure that triggers and actions are pointing at the correct locations.
 2. Review flows that use custom connectors to ensure they're pointing at the new custom connector in the target environment. For more details, see [Custom Connectors](#custom-connectors) below.
 3. Before enabling flows in the target environment, consider if the corresponding flows should be disabled in the source environment and if appropriate, then disable those flows. Ensure that flow runs have completed before disabling flows.
 4. Enable flows as needed. Any child flows need to be enabled before parent flows can be enabled.
-5. For any flows using the "When a HTTP request is received" trigger, adjust any dependent flows or apps to call the new HTTP URL. If the flows in the source environment are disabled, then testing that the dependent apps have been redirected correctly becomes easier.
+5. For any flows using the "When an HTTP request is received" trigger, adjust any dependent flows or apps to call the new HTTP URL. If the flows in the source environment are disabled, then testing that the dependent apps have been redirected correctly becomes easier.
 
 #### Connection References
   - Connection References require new connections.

@@ -75,7 +75,7 @@ You can find personal data from Dataverse users within the following resources:
 |Resource | Purpose | Website access | Programmatic access  |
 | --- | --- | --- | ---  |
 | Table row | Known as the system User table, it stores a user's personal data. | [Power Platform admin center](https://admin.powerplatform.microsoft.com/) | Through the [Web API](/powerapps/developer/common-data-service/webapi/update-delete-entities-using-web-api#basic-update)  |
-| Audit history | Allows customers to identify resources that users created, accessed, changed, or deleted at an table level. | [Power Platform admin center](https://admin.powerplatform.microsoft.com/) | Through the [Web API](/powerapps/developer/common-data-service/webapi/update-delete-entities-using-web-api#basic-update)  |
+| Audit history | Allows customers to identify resources that users created, accessed, changed, or deleted at a table level. | [Power Platform admin center](https://admin.powerplatform.microsoft.com/) | Through the [Web API](/powerapps/developer/common-data-service/webapi/update-delete-entities-using-web-api#basic-update)  |
 
 #### User
 User personal data is stored in the Microsoft Entra and is automatically synced to all environments with a Dataverse database. System administrators cannot update this personal data directly in Dataverse while the user is active&mdash;they must update the data from within the Microsoft 365 admin center. System administrators can add personal data (for example, custom attributes) directly to Dataverse, but they must manually manage this data.
@@ -183,7 +183,7 @@ From the [Power Platform admin center](https://admin.powerplatform.microsoft.com
 12. Select **Next**, and then select **Submit**.
 
 #### Permanently delete user
-You can either remove user's personal data or permanently delete the user record from the Datavese user table. More information: [Permanently delete users in Power Platform](/power-platform/admin/delete-users#permanently-delete-users-in-power-platform). 
+You can either remove user's personal data or permanently delete the user record from the Dataverse user table. More information: [Permanently delete users in Power Platform](/power-platform/admin/delete-users#permanently-delete-users-in-power-platform). 
 
 When the user record is permanently deleted, the user's name in all records where the deleted user was the creator or last modified by and in the audit logs will show as **No Name**.
 
@@ -267,7 +267,7 @@ From the [Power Platform admin center](https://admin.powerplatform.microsoft.com
 Dataverse System Administrators can delete an individual's personal data from records where that data is stored.  The Dataverse System Administrator can choose to either delete the record where the personal data is stored, or remove the contents of the personal data from the record.  
 
 > [!NOTE]
-> Dataverse administrators can customize an environment to prevent a record from being deleted from an table. If configured in this way, you'll have to remove the contents of the personal data from the record rather than delete the record itself.
+> Dataverse administrators can customize an environment to prevent a record from being deleted from a table. If configured in this way, you'll have to remove the contents of the personal data from the record rather than delete the record itself.
 
 From the Dataverse search results, to the following:
 
@@ -284,7 +284,7 @@ You may be storing personal data from individuals (such as your own customers) w
 
 Dataverse System Administrators are responsible for maintaining an inventory of where personal data is being stored within various tables for each individual so that they can locate that data in response to any DSR requests.  
 
-Personal data can then be exported, rectified, or deleted in an table using the in-product functionality.  
+Personal data can then be exported, rectified, or deleted in a table using the in-product functionality.  
 
 ### Discover
 When Dataverse System Administrators receives a DSR request from an individual, they must identify which environments/environments with a Dataverse database contain personal data from that individual. Personal data is typically stored in key tables (for example, Account, Contact, Lead, Opportunity, etc.), but it's your responsibility to develop policies and procedures for maintaining an inventory of where you store each individual's personal data so you're prepared to respond to DSR requests.

@@ -30,7 +30,7 @@ Microsoft 365 Groups, available with Dynamics 365 apps, provides a new environme
 
 - Customer engagement apps
 
-- This feature requires that you have an Microsoft 365 subscription or a subscription to an online service such as SharePoint Online or Exchange Online.
+- This feature requires that you have a Microsoft 365 subscription or a subscription to an online service such as SharePoint Online or Exchange Online.
 
 - To use document storage with Microsoft 365 Groups, you will need SharePoint Online and access to the group OneNote notebook.
 
@@ -44,7 +44,7 @@ Microsoft 365 Groups, available with Dynamics 365 apps, provides a new environme
  Microsoft 365 Groups is a solution you provision from your Microsoft 365 admin center.  
 
 > [!NOTE]
->  Users must have an Exchange Online mailbox set up to use Microsoft 365 Groups. Exchange Online is already properly configured for organizations as a part of Microsoft 365. You also need to enable server-based SharePoint integration to see documents in an Microsoft 365 Group; you don't have to use SharePoint integration, only set up the connection to SharePoint Online.  Server-based SharePoint integration is also required to enable the group OneNote notebook.  
+>  Users must have an Exchange Online mailbox set up to use Microsoft 365 Groups. Exchange Online is already properly configured for organizations as a part of Microsoft 365. You also need to enable server-based SharePoint integration to see documents in a Microsoft 365 Group; you don't have to use SharePoint integration, only set up the connection to SharePoint Online.  Server-based SharePoint integration is also required to enable the group OneNote notebook.  
 > 
 > More information: [Set up customer engagement apps to use SharePoint Online](set-up-dynamics-365-online-to-use-sharepoint-online.md)  
 

@@ -27,7 +27,7 @@ A good way to categorize connectors is to place them in groups based on the busi
 When a new policy is created, by default all connectors are placed in the **Non-Business** group. From there they can be moved to **Business** or **Blocked** based on your preference. You manage the connectors in a data group when you create or modify the properties of a DLP policy from the admin center. See [Manage data policies](prevent-data-loss.md). You can also change the initial classification of connectors by editing your DLP policy. More information: [Edit a data policy](prevent-data-loss.md#edit-a-data-policy)
 
 > [!NOTE]
-> Until recently, some HTTP connectors weren't readily available for DLP policy configuration by using the DLP policy UI or PowerShell. As of May 2020, the following HTTP connectors can now be classified by using the DLP policy UI and PowerShell, like any other Power Platform connector: **HTTP**, **HTTP Webhook**, and **When a HTTP request is received**. If legacy DLP policies are being updated by using the new DLP UI, a warning message will be displayed to admins indicating that these three HTTP connectors are now being added to the DLP purview and that they should ensure that these connectors are placed in the right DLP grouping.
+> Until recently, some HTTP connectors weren't readily available for DLP policy configuration by using the DLP policy UI or PowerShell. As of May 2020, the following HTTP connectors can now be classified by using the DLP policy UI and PowerShell, like any other Power Platform connector: **HTTP**, **HTTP Webhook**, and **When an HTTP request is received**. If legacy DLP policies are being updated by using the new DLP UI, a warning message will be displayed to admins indicating that these three HTTP connectors are now being added to the DLP purview and that they should ensure that these connectors are placed in the right DLP grouping.
 >
 > Because child flows share an internal dependency with the HTTP connector, the grouping that admins choose for HTTP connectors in a DLP policy might affect the ability to run child flows in that environment or tenant. Make sure your HTTP connectors are classified in the appropriate group for your child flows to function. If there are any concerns in classifying the connector as **Business** in shared environments such as the default environment, our advice is to classify it as **Non-Business** or to block it. Then, create dedicated environments where makers can use HTTP connectors, but restrict the maker list so that you can unblock makers from building child flows.
 >

@@ -165,9 +165,9 @@ This error occurs because these filter by options aren't currently supported wit
 
 ### Next and previous page arrow buttons in the SharePoint grid do not work
 
-The next and previours page arrow buttons in the SharePoint grid do not work. This is a known issue.
+The next and previous page arrow buttons in the SharePoint grid do not work. This is a known issue.
 
-**Resolution**: Users can selet the **Load More** button at the bottom of the page or select **Open Location** to go to the SharePoint site to access files.
+**Resolution**: Users can select the **Load More** button at the bottom of the page or select **Open Location** to go to the SharePoint site to access files.
 
 ### See also
 

@@ -34,7 +34,7 @@ The customer engagement apps (Dynamics 365 Sales, Dynamics 365 Customer Service,
 
  [!INCLUDE[proc_more_information](../includes/proc-more-information.md)] [Define service level agreements (SLAs)](/dynamics365/customer-service/define-service-level-agreements)  
 
-## Considerations when you choose a SLA type  
+## Considerations when you choose an SLA type  
  Because there are two types of SLAs that have different functionality, consider the following features before you choose an SLA type. We recommend that you use only one type of SLA for an organization.  
 
 -   After you select an SLA type, either standard or enhanced, you cannot change the SLA type for any record associated with the SLA.  

@@ -72,7 +72,7 @@ The following principals are supported for each role type.
 > - In the Default environment, all users in a tenant are granted access to the Environment Maker role. 
 > - Microsoft Entra tenant Global Administrators have admin access to all environments.
 
-#### FAQ - What permissions exist at an Microsoft Entra tenant level? 
+#### FAQ - What permissions exist at a Microsoft Entra tenant level? 
 
 Today, Microsoft Power Platform admins can do the following: 
 

@@ -19,7 +19,7 @@ There are different ways to obtain access to a particular record in Dataverse. T
 
 ## Privilege check
 
-The privilege check is the first barrier that needs to be passed in order to do a certain action with a record of an table. The privilege checks validate that the user has the required privilege for that table. For each table, whether out of the box or custom, there exist different privileges to provide interaction capabilities with the records of that type. 
+The privilege check is the first barrier that needs to be passed in order to do a certain action with a record of a table. The privilege checks validate that the user has the required privilege for that table. For each table, whether out of the box or custom, there exist different privileges to provide interaction capabilities with the records of that type. 
 
 For example, for Account, the privileges are: