Merge branch 'main' into metadata

Author: aditisrivastava07

unified-secops-platform/media/mto-endpoint-security-policy/mto-distributed.png

@@ -107,7 +107,7 @@ Common reasons for a sync to fail include:
 
 If the issue is with the target tenant, try creating an identical custom detection rule for further diagnosis. If the issue is with accessing the source data, try accessing the custom detection.
 
-A known issue exists with distribution profile errors. In some scenarios, such as when a user without the required permissions selects **See the assignment** on a policy error, an indefinite loading state might be shown without a clear error message. Users might also encounter generic or unclear error messages if Microsoft Entra is temporarily unavailable.
+A known issue exists with distribution profile errors. In some scenarios, such as when a user without the required permissions selects **See the assignment** on a policy error, an indefinite loading state might be shown without a clear error message. Users might also encounter generic or unclear error messages if Microsoft Entra is temporarily unavailable. In such cases, close the error message and verify your permissions and Microsoft Entra availability.
 
 ## Related content
 

unified-secops-platform/mto-distribution-profiles.md

@@ -75,6 +75,6 @@ Endpoint security policies that are distributed across tenants with the multiten
 
 :::image type="content" source="media/mto-endpoint-security-policy/mto-distributed.png" alt-text="Screenshot of the endpoint security policies page in multitenant management highlighting distributed policies" lightbox="media/mto-endpoint-security-policy/mto-distributed.png":::
 
-The **Last Distribution Status** for the original policy reflects the overall status of its distributed copies, and the **Tenants** and **Tenant Groups** sections indicate the distribution profile recipients of the policy. For more information, see [Content distribution in multitenant management](mto-distribution-profiles.md).
+The **Last Distribution Status** for the original policy reflects the overall status of its distributed copies, and the **Tenants** and **Distribution profiles** columns indicate the distribution profile recipients of the policy. For more information, see [Content distribution in multitenant management](mto-distribution-profiles.md).
 
 [!INCLUDE [Microsoft Defender XDR rebranding](../includes/defender-m3d-techcommunity.md)]

unified-secops-platform/mto-endpoint-security-policy.md

@@ -38,7 +38,7 @@ For more information, see [Content distribution using distribution profiles in m
 
 ### Distribute Microsoft Defender for Endpoint security policies with multitenant management
 
-Microsoft Defender for Endpoint security policies can now be distributed as content across multiple tenants using the Defender multitenant portal, empowering security teams to manage endpoint security policies at scale. Distributed policies are shown in the **Configuration management > Endpoint security policies** page in a hierarchical view so that you can identify parent policies and their distributed copies across tenants. Distribution profiles are listed in the **Tenant groups** column.
+Microsoft Defender for Endpoint security policies can now be distributed as content across multiple tenants using the Defender multitenant portal, empowering security teams to manage endpoint security policies at scale. Distributed policies are shown in the **Configuration management > Endpoint security policies** page in a hierarchical view so that you can identify parent policies and their distributed copies across tenants.
 
 :::image type="content" source="media/mto-endpoint-security-policy/mto-distributed.png" alt-text="Screenshot of an expanded, distributed policy." lightbox="media/mto-endpoint-security-policy/mto-distributed.png":::