Merge pull request #16803 from MicrosoftDocs/main

Publish main to live, 10:30AM PST, 12/02

memdocs/intune/apps/app-management.md

@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 08/09/2024
+ms.date: 12/02/2024
 ms.topic: overview
 ms.service: microsoft-intune
 ms.subservice: apps

windows-365/enterprise/cross-region-disaster-recovery-set-up.md

@@ -51,7 +51,8 @@ ms.collection:
     When configuring a backup location, consider things like data sovereignty and geographic distance between the user and the Cloud PC backup location. The greater the distance between your backup Cloud PC and your user’s connect location increases network latency and impacts performance. Full copies of your Cloud PCs are kept in the backup location, including all data stored on the Cloud PC disk.
 
 6. Select **Next**.
-7. On the **Assignments** page, add the groups that you want this user setting applied to. All Cloud PCs associated with a user share the same cross region disaster recovery settings.
+1. On the **Assignments** page, add the groups containing users that you want this user setting applied to. All Cloud PCs associated with a user will share the same cross region disaster recovery settings.
+
 8. On the **Review + create** page, select **Create**.
 
 After you finish this configuration, the first backup of the Cloud PC may take several days. To see the current state of backups, check the [Cross region disaster recovery report](cross-region-disaster-recovery-report.md). After the first backup, the recovery point objective (RPO) will be the same as for point-in-time restore plus a few minutes to replicate across regions.

windows-365/link/conditional-access-policies-synchronize.md

@@ -9,7 +9,7 @@ ms.author: erikje
 manager: dougeby
 ms.date: 11/19/2024
 ms.topic: overview
-ms.service: windows-365
+ms.service: windows-365-link
 ms.subservice:
 ms.localizationpriority: high
 ms.assetid: 

windows-365/link/control-alt-delete.md

@@ -9,7 +9,7 @@ ms.author: erikje
 manager: dougeby
 ms.date: 11/19/2024
 ms.topic: overview
-ms.service: windows-365
+ms.service: windows-365-link
 ms.subservice:
 ms.localizationpriority: high
 ms.assetid: 

windows-365/link/create-intune-filter.md

@@ -9,7 +9,7 @@ ms.author: erikje
 manager: dougeby
 ms.date: 11/19/2024
 ms.topic: overview
-ms.service: windows-365
+ms.service: windows-365-link
 ms.subservice:
 ms.localizationpriority: high
 ms.assetid: 

windows-365/link/deployment-overview.md

@@ -9,7 +9,7 @@ ms.author: erikje
 manager: dougeby
 ms.date: 11/19/2024
 ms.topic: overview
-ms.service: windows-365
+ms.service: windows-365-link
 ms.subservice:
 ms.localizationpriority: high
 ms.assetid: 

windows-365/link/enrollment-restrictions.md

@@ -9,7 +9,7 @@ ms.author: erikje
 manager: dougeby
 ms.date: 11/19/2024
 ms.topic: overview
-ms.service: windows-365
+ms.service: windows-365-link
 ms.subservice:
 ms.localizationpriority: high
 ms.assetid: 

windows-365/link/index.yml

@@ -4,13 +4,13 @@ summary: Official product documentation for Windows 365 Link
 
 metadata:
   services: service
-  ms.service: windows-365
+  ms.service: windows-365-link
   ms.topic: hub-page
   author: erikjeMS
   ms.author: erikje
   manager: dougeby
   ms.date: 11/192024
-  ms.subservice: windows-365-link
+  ms.subservice: 
 
 highlightedContent:
   items:

windows-365/link/intune-automatic-enrollment.md

@@ -9,7 +9,7 @@ ms.author: erikje
 manager: dougeby
 ms.date: 11/19/2024
 ms.topic: overview
-ms.service: windows-365
+ms.service: windows-365-link
 ms.subservice:
 ms.localizationpriority: high
 ms.assetid: 

windows-365/link/join-microsoft-entra.md

@@ -9,7 +9,7 @@ ms.author: erikje
 manager: dougeby
 ms.date: 11/19/2024
 ms.topic: overview
-ms.service: windows-365
+ms.service: windows-365-link
 ms.subservice:
 ms.localizationpriority: high
 ms.assetid:

windows-365/link/onboarding.md

@@ -9,7 +9,7 @@ ms.author: erikje
 manager: dougeby
 ms.date: 11/19/2024
 ms.topic: overview
-ms.service: windows-365
+ms.service: windows-365-link
 ms.subservice:
 ms.localizationpriority: high
 ms.assetid: 

windows-365/link/requirements.md

@@ -45,21 +45,21 @@ The user who joins the device to Microsoft Entra ID must have permissions to joi
 
 Windows 365 Link devices can be used to connect to Cloud PCs that are either Entra joined or Entra hybrid joined.
 
-Windows 365 Link devices use automatic [mobile device management](/windows/client-management/mdm-overview) (MDM) enrollment to enroll in Intune for managment by the organization. To use this feature, the user who Entra joins the device must have a Microsoft Entra ID Premium license.
+Windows 365 Link devices use [automatic enrollment](/mem/intune/enrollment/windows-enroll) in Intune for management by the organization. To use this feature, the user who Entra joins the device must have a Microsoft Entra ID Premium license.
 
 For more information, see [Join Windows 365 Link to Microsoft Entra](join-microsoft-entra.md).
 
 ## Microsoft Intune requirements
 
-Windows 365 Link devices enroll for management with Intune during the Out of Box experience. The user performing enrollment must have permission to enroll the devices and comply with any defined Enrollment restrictions.
+Windows 365 Link devices enroll for management with Intune during the Out of Box Experience (OOBE). The user performing enrollment must have permission to enroll the devices and comply with any defined Enrollment restrictions.
 
 Optionally, Windows 365 Link devices can be used with the Intune corporate identifier enrollment feature to pre-upload the serial number, manufacturer, model to ensure only trusted devices go through enrollment.
 
 For more information, see [Automatically enroll Windows 365 Link in Intune](intune-automatic-enrollment.md).
 
 ## Windows 365 SSO requirements
 
-Windows 365 Link devices can only be used to connect to Windows 365 Cloud PCs that have Entra ID single sign-on (SSO) enabled. If SSO is not enabled on the Cloud PC, the user:
+Windows 365 Link devices can only be used to connect to Windows 365 Cloud PCs that have Entra ID single sign-on (SSO) enabled. If SSO isn't enabled on the Cloud PC, the user:
 
 - Gets an error that their Cloud PC doesn't support Entra ID single sign-on
 - Can't connect to their Cloud PC.
@@ -75,7 +75,7 @@ After SSO is enabled, Windows 365 Link devices can be used to connect to those C
 
 If you're using Conditional Access to protect access to Cloud PC, make sure to include the SSO Cloud App resource in the target resources of those Conditional Access policies.
 
-Also consider suppressing the SSO Consent Prompt by configuring the SSO on service principals. (see how-to configure environment for guidance)
+Also consider suppressing the SSO Consent Prompt by configuring the SSO on service principals.
 
 ## Microsoft Teams requirements