Merge branch 'mde-policies' of https://github.com/batamig/defender-docs-pr into mde-policies

Author: batamig

unified-secops-platform/TOC.yml

@@ -113,8 +113,8 @@
               href: mto-tenants.md
             - name: Create and manage endpoint security policies
               href: mto-endpoint-security-policy.md
-            - name: Manage content distribution with profiles
-              href: mto-deployment-profiles.md
+            - name: Manage content distribution across tenants
+              href: mto-distribution-profiles.md
             - name: Manage tenants in other Microsoft clouds
               href: mto-cross-cloud.md
             - name: Manage unified role-based access control (URBAC) for multitenant management

unified-secops-platform/mto-cross-cloud.md

@@ -122,7 +122,7 @@ To remove tenants from the list, select the tenant, then select **Remove tenants
 After successfully adding tenants from other clouds, you can view these tenants in other multitenant pages like the incidents and device inventory pages.
 
 > [!NOTE]
-> When a cross-cloud tenant is added to a deployment profile and subsequently removed from cross-cloud visibility, the tenant's name is removed from the tenant list and won’t be available for content management. This is a recognized limitation of cross-cloud visibility and is currently under review. See [Troubleshooting issues](mto-troubleshoot.md#content-assignment-failure-in-cross-cloud-tenant-management) for more information.
+> When a cross-cloud tenant is added to a distribution profile and subsequently removed from cross-cloud visibility, the tenant's name is removed from the tenant list and won’t be available for content management. This is a recognized limitation of cross-cloud visibility and is currently under review. See [Troubleshooting issues](mto-troubleshoot.md#content-assignment-failure-in-cross-cloud-tenant-management) for more information.
 
 ## Next steps
 

unified-secops-platform/mto-troubleshoot.md

@@ -51,11 +51,11 @@ Here’s an example of the policy setting in the Microsoft Entra admin center.
 
 ## Content assignment failure in cross-cloud tenant management
 
-You see the following error when assigning content to deployment profiles:
+You see the following error when assigning content to distribution profiles:
 
 :::image type="content" source="media/mto-troubleshoot/tenant-perms-error.png" alt-text="Screenshot of permissions error when assigning content to tenants" lightbox="media/mto-troubleshoot/tenant-perms-error.png":::
 
-When a cross-cloud tenant is added to a deployment profile and subsequently removed from cross-cloud visibility, the tenant's name is removed from the tenant list and won't be available for content management, which causes the error. This is a recognized limitation of cross-cloud tenant management and is currently under review.
+When a cross-cloud tenant is added to a distribution profile and subsequently removed from cross-cloud visibility, the tenant's name is removed from the tenant list and won't be available for content management, which causes the error. This is a recognized limitation of cross-cloud tenant management and is currently under review.
 
 ## Related content