MicrosoftDocs · sericks007 · Jun 7, 2024 · Jun 7, 2024
@@ -149,7 +149,7 @@ For more information on the different roles for managing your tenant across the
 > |      Workflow Executions      | This chart shows how many workflows have been executed in the environment with a Dataverse database over the specified time. | 
 > |     System Jobs Pass Rate     | This chart shows the system job's pass rate as percentage of system jobs that were executed in the environment with a Dataverse database over the specified time.  | 
 > | System Jobs Throughput/Minute | This chart shows the average system jobs that have been executed per hour in the environment with a Dataverse database over the specified time. | 
-> |    Executions and Backlog     |  This chart shows the number of executions and the backlog for system jobs in the environment with a Dataverse databaset over the specified time.   | 
+> |    Executions and Backlog     |  This chart shows the number of executions and the backlog for system jobs in the environment with a Dataverse database over the specified time.   | 
 > |     Most Active Workflows     |  This chart shows top 10 most executed workflows in the environment with a Dataverse database over the specified time.  | 
 > |   Top Workflows by Failures   | This chart shows top 10 most failing workflows in the environment with a Dataverse database over the specified time. Click on a workflow to see the failures and their number of occurrences. | 
 

@@ -46,7 +46,7 @@ Open XrmToolBox and connect to your organization. On the **Configuration** tab,
 
 ## Step 1. Check the current default sync filter 
 
-1. In [XrmToolBox](https://www.xrmtoolbox.com/), go to the the **Tools** menu and open **Sync Filter Manager.** 
+1. In [XrmToolBox](https://www.xrmtoolbox.com/), go to the **Tools** menu and open **Sync Filter Manager.** 
 
    > [!div class="mx-imgBorder"] 
    > ![Open the Sync Filter Manager.](media/default-sync-filter-5.png "Sync filter manager")

@@ -372,7 +372,7 @@ We are in the process of moving application user management from the legacy web
 A stub user is a user record that has been created as a placeholder. For example, records have been imported that refer to this user but the user doesn't exist in customer engagement apps. This user can't sign in, can't be enabled, and can't be synchronized to Microsoft 365. This type of user can only be created through data import. 
 
 > [!CAUTION]
-> To prevent creating duplicate user records with the same UPN or throw errors during data import workflows, ensure that users exist in Entra ID and are sufficiently licensed for pre-provisioning. Office licenses aren't supported for pre-provisioning, but any Power Apps Premium or Dynamics 365 licenses are supported for pre-provisioning. Once users meet these requirements, they are syncronized with Dataverse environments.  
+> To prevent creating duplicate user records with the same UPN or throw errors during data import workflows, ensure that users exist in Entra ID and are sufficiently licensed for pre-provisioning. Office licenses aren't supported for pre-provisioning, but any Power Apps Premium or Dynamics 365 licenses are supported for pre-provisioning. Once users meet these requirements, they are synchronized with Dataverse environments.  
 > If you must reassign records from a stub user to another user, use the [Add-BulkRecordsToUsers](https://github.com/microsoft/PowerApps-Samples/tree/master/powershell/UserManagement/Microsoft.PowerPlatform.Administration.UserManagement#command-add-bulkrecordstousers).
 
 A default security role is automatically assigned to these imported users. The **Salesperson** security role is assigned in an environment and the **Basic User** security role is assigned in a Power Apps environment.

@@ -32,7 +32,7 @@ Admins can apply various rules to groups to govern many environments in bulk, re
 
 There are many ways to manage pockets of environments within your tenant using environment groups. For example, global organizations can create an environment group for all environments in each geographic region to ensure compliance with legal and regulatory requirements. You can also organize environment groups by department or other criteria.
 
-:::image type="content" source="media/environment-groups-strategy.png" alt-text="Diagram depicting one strategy for using environment groups and aligning it to your existing orgnizational structure.":::
+:::image type="content" source="media/environment-groups-strategy.png" alt-text="Diagram depicting one strategy for using environment groups and aligning it to your existing organizational structure.":::
 
 This article covers how to augment your _default environment strategy_ by combining _environment groups_ with [_default environment routing_](default-environment-routing.md). Default environment routing gives makers their own personal developer environment. This environment is a secure space to build with Microsoft Dataverse and is similar to [OneDrive](https://www.microsoft.com/microsoft-365/onedrive/online-cloud-storage) for personal productivity.
 

@@ -54,7 +54,7 @@ Complete the following steps to assign Power Apps premium licenses to users.
 
 8. Select the license you want to assign to the users. Click **Assign**.
 
-## View recently assiged licenses
+## View recently assigned licenses
 Near the bottom of the page, admins can see the history of license assignment, including a summary of users who were assigned licenses and the date of assignment.   
 
 [!INCLUDE[footer-include](../includes/footer-banner.md)]
@@ -69,7 +69,7 @@ Securing a field with field-level security can impact synchronization between cu
 
 6. Select the new profile > **Users** > **Add**  
 
-7. Select users and then celect **Select** > **Add**.  
+7. Select users and then select **Select** > **Add**.  
 
 ### Set field permissions  
  With a field security profile created and users added to the profile, John can now set permissions on the fields to match the organization's requirements.  

@@ -106,7 +106,7 @@ In this case, the user would have access to the record if both of the following
 
 ## Record access check
 
-For each record that is displayed in the web client, the user has the ability to see how they were granted access to the record through the [**Check Access**](/power-apps/user/access-checker) option on the command bar. The user can also see other users who have accecss to the record and their respective access level.
+For each record that is displayed in the web client, the user has the ability to see how they were granted access to the record through the [**Check Access**](/power-apps/user/access-checker) option on the command bar. The user can also see other users who have access to the record and their respective access level.
 
 There are two environment database settings to configure to use the **Who has access** feature. [Install the **OrganizationSettingsEditor** tool](environment-database-settings.md#install-the-organizationsettingseditor-tool) and set the following to true:
 

@@ -21,7 +21,7 @@ All environments of Microsoft Dataverse use [!INCLUDE[pn_MS_SQL_Server](../inclu
  By default, [!INCLUDE[cc_Microsoft](../includes/cc-microsoft.md)] stores and manages the database encryption key for your environments so you don't have to. The manage keys feature in the Microsoft Power Platform admin center gives administrators the ability to self-manage the database encryption key that is associated with the Dataverse tenant. 
 
 > [!IMPORTANT]
-> - As of June 2, 2023, this service is upgraded to [Customer-managed encryption key](customer-managed-key.md). New customers who need to manage their own encryption key will use the upgraded service as this service is no longer offerred.
+> - As of June 2, 2023, this service is upgraded to [Customer-managed encryption key](customer-managed-key.md). New customers who need to manage their own encryption key will use the upgraded service as this service is no longer offered.
 > - Self-managed database encryption keys are only available for customers who have more than 1000 Power Apps per user licenses, or more than 1000 Dynamics 365 Enterprise licenses, or more than 1000 licenses from a combination of both in a single tenant. To opt in to this program, submit a [support request](./support-overview.md#using-support).
 
 Encryption key management is only applicable to Azure SQL environment databases. The following features and services continue to use the Microsoft-managed encryption key to encrypt their data and can't be encrypted with the self-managed encryption key:

@@ -31,7 +31,7 @@ To ensure compliance and prevent surprises, admins should keep up-to-date with t
 - Admins are encouraged to enable Auto-claim so license assignment is automated.
 - Admins should periodically review the Power Automate license reporting, which now includes both tenant and environment level reporting views. To learn more, go to [View license consumption for Power Apps and Power Automate (preview)](../view-license-consumption-issues.md).
 
-    The report identifies flows that require a license for a subset of scenarios that are in scope of the power platform licensing guide. This subset of scenarios constitues the current scope of enforcement. We expect customers to ensure compliance with all licensing requirements covered in the [Power Platform Licensing Guide](https://go.microsoft.com/fwlink/?linkid=2085130). We expect to add more scenarios to this report to help administrators identify flows that require their attention. We might broaden the scope of enforcements at such time.
+    The report identifies flows that require a license for a subset of scenarios that are in scope of the power platform licensing guide. This subset of scenarios constitutes the current scope of enforcement. We expect customers to ensure compliance with all licensing requirements covered in the [Power Platform Licensing Guide](https://go.microsoft.com/fwlink/?linkid=2085130). We expect to add more scenarios to this report to help administrators identify flows that require their attention. We might broaden the scope of enforcements at such time.
 
 ## Types of enforcements
 

@@ -144,7 +144,7 @@ Allow canvas editors to insert the Copilot answer component, which allows users
 | Enable Finance and Operations user impersonation in Dataverse | When enabled, the Finance and Operations application in this environment has permissions to impersonate Dataverse users. This allows users of Finance and Operations to make calls to Dataverse which run as that same user in Dataverse, using the Dataverse permissions assigned to that user. Only select this option if the Finance and Operations administrator is trusted with the same level of permissions in Dataverse as the Dataverse administrator. | Off |
 
 > [!IMPORTANT]
-> Beginning March 1, 2024 the **Enable Finance and Operations user impersonation in Dataverse** toggle will be removed. With continued efforts to unify finance and operations apps with the Power Platform through the [Power Platform integration](/dynamics365/fin-ops-core/dev-itpro/power-platform/overview) and [unified admin exeriences](unified-experience/finance-operations-apps-overview.md), finance and operations apps are now considered applications within the Power Platform environment. In a unified environment, the capabilities granted by the toggle are now assumed to be true for any environment with finance and operations apps installed with the same level of governance, oversight and scrutiny as all other apps in a Power Platform environment.
+> Beginning March 1, 2024 the **Enable Finance and Operations user impersonation in Dataverse** toggle will be removed. With continued efforts to unify finance and operations apps with the Power Platform through the [Power Platform integration](/dynamics365/fin-ops-core/dev-itpro/power-platform/overview) and [unified admin experiences](unified-experience/finance-operations-apps-overview.md), finance and operations apps are now considered applications within the Power Platform environment. In a unified environment, the capabilities granted by the toggle are now assumed to be true for any environment with finance and operations apps installed with the same level of governance, oversight and scrutiny as all other apps in a Power Platform environment.
 
 ## Data validation
 | Setting | Description | Default value |

@@ -63,7 +63,7 @@ How appointments sync between Dynamics 365 and Exchange depends on the sync dire
 
 ### Appointment organizer
 
-The appointment organizer is a key field for appointment synchronization. It drives different synchronization behaviors. For example, only the Dynaamics 365 appointment organizer can synchronize and distribute appointments from Dynamics 365 to Exchange attendees. When you create appointments using customizations such as Power Automate or custom code, make sure the organizer is specified correctly. The organizer field isn't exposed on the appointment form by default. You can add it to forms, views, or advanced find queries, as needed, to confirm the value is present and correct.
+The appointment organizer is a key field for appointment synchronization. It drives different synchronization behaviors. For example, only the Dynamics 365 appointment organizer can synchronize and distribute appointments from Dynamics 365 to Exchange attendees. When you create appointments using customizations such as Power Automate or custom code, make sure the organizer is specified correctly. The organizer field isn't exposed on the appointment form by default. You can add it to forms, views, or advanced find queries, as needed, to confirm the value is present and correct.
 
 If an appointment organizer is changed in Dynamics 365 after it has been synchronized to Exchange, this may cause the original organizer to issue a cancellation. This can happen because the appointment no longer meets the conditions of the user’s sync filters. Additionally, the new organizer may synchronize the appointment as a new meeting in Exchange. The behavior of sending a cancellation from the previous organizer can be modified using the [OrgDBOrgSetting](https://support.microsoft.com/en-us/topic/orgdborgsettings-tool-for-microsoft-dynamics-crm-20a10f46-2a24-a156-7144-365d49b842ba) named DistinctPhysicalAndLogicalDeletesForExchangeSync.
 

@@ -155,7 +155,7 @@ Your trial will be extended 30 days from the original expiration date.
 
 ## Extend a trial (subscription-based) environment
 
-The expiration of subscription-based trial (also know as an admin trial) environments is tied to the expiration of the subscription. Therefore, subscription-based trial environments cannot be independently extended. There are limited options for extending admin trial subscriptions which affects extending the expiration of any associated trial environments.
+The expiration of subscription-based trial (also known as an admin trial) environments is tied to the expiration of the subscription. Therefore, subscription-based trial environments cannot be independently extended. There are limited options for extending admin trial subscriptions which affects extending the expiration of any associated trial environments.
 
 **To extend a subscription-based (admin) trial:**
 

@@ -134,7 +134,7 @@ The **Environments** tab on the **Licenses (preview)** page displays licensing i
 | Premium feature | Indicates if a premium feature, such as a premium connector, custom connector, or Dataverse connector, was used in the flow. |
 | Flow type | Indicates if the flow is scheduled, instant, or automated. |
 | Download | Downloads the information in CSV format. Select a specific license type to start the download. After a CSV file is generated, you can download the same file again within five days without having to start a new download. |
-| Attention needed | Summary count of flows requiring licensing attention, which includes: </br><ul></br><li>List of flow not having an owner.</li></br><li>Standalone, Premium flow using standard or expired licenses.</li></br><li>Out of Context flow, such as Premium flows using Power Apps, Microsoft Copilot Studio, or Dynamics 365 licenses but not running in in the context of Power Apps, Microsoft Copilot Studio, or Dynamics 365.</li></br></ul> |
+| Attention needed | Summary count of flows requiring licensing attention, which includes: </br><ul></br><li>List of flow not having an owner.</li></br><li>Standalone, Premium flow using standard or expired licenses.</li></br><li>Out of Context flow, such as Premium flows using Power Apps, Microsoft Copilot Studio, or Dynamics 365 licenses but not running in the context of Power Apps, Microsoft Copilot Studio, or Dynamics 365.</li></br></ul> |
 
 ## Other ways to view licensing pages
 

@@ -484,7 +484,7 @@ public void DependencyReport(Dependency dependency)
       requiredComponentTypeName = opt.Label.UserLocalizedLabel.Label;
      }
     }
- // The name or display name of the compoent is retrieved in different ways depending on the component type
+ // The name or display name of the component is retrieved in different ways depending on the component type
     dependentComponentName = getComponentName(dependency.DependentComponentType.Value, (Guid)dependency.DependentComponentObjectId);
     requiredComponentName = getComponentName(dependency.RequiredComponentType.Value, (Guid)dependency.RequiredComponentObjectId);
 

@@ -10,6 +10,6 @@ The command returns output like the following:
 
 ```Text
 Name                           Bot ID                               Component State Is Managed Solution ID                          Status Code State Code
-Ask Me Anytyhing Copilot       584e012c-dc95-46d6-af5a-1263b6a44342 Published       Unmanaged  285af946-6383-49a0-8615-4e2afafeaf38 Active      Provisioned
+Ask Me Anything Copilot       584e012c-dc95-46d6-af5a-1263b6a44342 Published       Unmanaged  285af946-6383-49a0-8615-4e2afafeaf38 Active      Provisioned
 New Test Copilot               9ee3f7aa-ab79-4cf6-a726-d85c8c18cc3e Published       Unmanaged  285af946-6383-49a0-8615-4e2afafeaf38 Active      Provisioned
 ```
@@ -35,7 +35,7 @@ Look for people with skills and strengths in the following roles:
 
 - **Citizen developers**: Continue to bring their day-to-day experience to how their job is done; when provided the right tools and training, can create apps to drive value.
 
-- **Pro developers**: Will design advanced interfaces using [Power Apps componenet framework](/powerapps/developer/component-framework/overview) in addition to building complex relationships or integrations with other applications, when the out-of-the-box limits have been reached, and the app needs to be extended.
+- **Pro developers**: Will design advanced interfaces using [Power Apps component framework](/powerapps/developer/component-framework/overview) in addition to building complex relationships or integrations with other applications, when the out-of-the-box limits have been reached, and the app needs to be extended.
 
 - **Trainers**: Are necessary to train others on how to use the apps that are built and made available across the organization, in addition to providing training on how to build apps.
 

@@ -43,7 +43,7 @@ The **Power Apps Adoption** page shows you further insights into how Power Apps
 
 ### Desktop flows usage
 
-The **Desktop flows usage** page provides an overview of UI-based robotic process automateion (RPA) flow runs in your environment:
+The **Desktop flows usage** page provides an overview of UI-based robotic process automation (RPA) flow runs in your environment:
 
 - Number of runs per date and desktop flow type
 - Total number of runs