Merge pull request #8686 from MicrosoftDocs/main

Publish main to live on 10/6 @ 10:30 am

Author: v-stsavell

memdocs/autopilot/known-issues.md

@@ -24,6 +24,10 @@ This article describes known issues that can often be resolved by configuration
 
 ## Known issues
 
+### TPM attestation failure with error code 0x81039001
+
+Some devices may intermittently fail TPM attestation during Windows Autopilot pre-provisioning technician flow or self-deployment mode with the error code 0x81039001 E_AUTOPILOT_CLIENT_TPM_MAX_ATTESTATION_RETRY_EXCEEDED. This failure occurs during the 'Securing your hardware' step for Windows Autopilot devices deployed using self-deploying mode or pre-provisioning mode. Subsequent attempts to provision may resolve the issue. A fix is expected by the end of October 2022.
+
 ### Autopilot deployment report shows "failure" status on a successful deployment
 
 The Autopilot deployment report (preview) will show a failed status for any device that experiences an initial deployment failure. For subsequent deployment attempts, using the **Try again** or **Continue to desktop** options, it won't update the deployment state in the report. If the user resets the device, it will show as a new deployment row in the report with the previous attempt remaining as failed.

memdocs/configmgr/core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures.md

@@ -86,7 +86,7 @@ The following features are no longer supported. In some cases, they're no longer
 |Task sequences: <br /> - OSDPreserveDriveLetter <br /><br /> During an operating system deployment, by default, Windows Setup now determines the best drive letter to use (typically C:). If you want to specify a different drive to use, you can change the location in the Apply Operating System task sequence step. Go to the **Select the location where you want to apply this operating system** setting. Select **Specific logical drive letter** and choose the drive that you want to use. |June 20, 2016 |Version 1606 |
 |[Network Access Protection](#network-access-protection) (NAP) - as found in System Center 2012 Configuration Manager|July 10, 2015|Version 1511|
 |[Out of Band Management](#out-of-band-management) - as found in System Center 2012 Configuration Manager|October 16, 2015|Version 1511|
-|[System Center Configuration Manager Management Pack  - for System Center Operations Manager is not available for download |October 16, 2015|Version 1511|
+|System Center Configuration Manager Management Pack  - for System Center Operations Manager is not available for download |October 16, 2015|Version 1511|
 
 ### WINS
 

memdocs/intune/enrollment/device-enrollment-program-enroll-ios.md

@@ -442,6 +442,7 @@ You'll sometimes need to renew your tokens:
 - Renew your ADE token yearly. The Endpoint Manager admin center shows the expiration date.
 - If the Apple ID password changes for the user who set up the token in Apple Business Manager, renew your enrollment program token in Intune and Apple Business Manager.
 - If the user who set up the token in Apple Business Manager leaves the organization, renew your enrollment program token in Intune and Apple Business Manager.
+- If you change the Apple ID used to create the ADE token, the change will not affect currently enrolled devices.
 
 ### Renew your tokens
 

windows-365/enterprise/create-azure-network-connection.md

@@ -62,6 +62,10 @@ To create an ANC, you must:
 6. Select **Next**.
 7. For hybrid Azure AD join ANCs, on the **AD domain** page, provide the following information:
     - **AD domain name**: The DNS name of the Active Directory domain that you want to use for connecting and provisioning Cloud PCs. For example, corp.contoso.com.
+
+  > [!NOTE]
+ > If your on-premises Active Directory environment has more than one domain or parent-child domains, be sure to enter the specific domain in which the Cloud PCs need to be domain joined.
+ 
     - **Organizational unit**: (Optional.) An organizational unit (OU) is a container within an Active Directory domain, which can hold users, groups, and computers. Make sure that this OU is enabled to sync with Azure AD Connect. Provisioning will fail if this OU isn't syncing.
     - **AD domain username**: The username, in user principal name (UPN) format, that you want to use for connecting the Cloud PCs to your Active Directory domain. For example, [email protected]. This service account must have permission to join computers to the domain and, if set, the target OU.
     - **AD domain password**: The password for the user specified above.

windows-365/enterprise/known-issues-enterprise.md

@@ -53,7 +53,7 @@ Upgrading an existing Cloud PC from Windows 10 to Windows 11 using the Settings
 1. Edit the related provisioning policy to change the gallery image to Windows 11.
 2. Reprovision the Cloud PC.
 
-## In-place Windows updgrade may change computer name
+## In-place Windows upgrade may change computer name
 
 Upgrading an existing Cloud PC between release versions of Windows 10 to Windows 11 may cause the computer name to be changed to a name with a prefix of "pps" while leaving the Intune device name unchanged.
 

windows-365/enterprise/set-up-tenants-windows-365-gcc.md

@@ -49,7 +49,7 @@ The Azure Government tenant includes Microsoft Azure subscription and associated
 - Other Azure Resources, including Cloud PC resources.
 
 >[!NOTE]
-> While the GCC users' Cloud PCs are hosted and secured in the Azure Government cloud, the admin and end user experience is similar to the commercial business uer experience. This is because the endpoints for admins and end users are in the commercial Azure domain.
+> While the GCC users' Cloud PCs are hosted and secured in the Azure Government cloud, the admin and end user experience is similar to the commercial business user experience. This is because the endpoints for admins and end users are in the commercial Azure domain.
 
 ## Azure AD options