Merge pull request #19319 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-16 18:30 UTC

Author: learn-build-service-prod[bot]

autopilot/includes/intune-connector.md

@@ -14,9 +14,7 @@ Headings are driven by article context. -->
 The **Intune Connector for Active Directory**, also known as the Offline Domain Join (ODJ) Connector, joins computers to an on-premises domain during the Windows Autopilot process. The connector creates computer objects in a specified Organizational Unit (OU) in Active Directory during the domain join process.
 
 > [!IMPORTANT]
-> Starting with Intune 2501, the Intune Connector for Active Directory is updated and improves security by following least-privilege principles using a [Managed Service Account (MSA)](/windows-server/identity/ad-ds/manage/understand-service-accounts#standalone-managed-service-accounts). When you download the connector from Intune, you automatically get the updated version.
-> 
-> The [deprecated legacy connector is still available](https://www.microsoft.com/download/details.aspx?id=105392) and will soon stop accepting enrollment requests. If you still use the legacy connector, update immediately to avoid loss of functionality. For more information, see the [Intune Connector for Active Directory with low-privileged account for Windows Autopilot Hybrid Microsoft Entra join deployments](https://aka.ms/Intune-Connector-blog) blog post.
+> The Intune Connector for Active Directory versions older than 6.2501.2000.5 are deprecated and can no longer process enrollment requests. For more information, see the [Intune Connector for Active Directory with low-privileged account for Windows Autopilot Hybrid Microsoft Entra join deployments](https://aka.ms/Intune-Connector-blog) blog post.
 > 
 > To update the connector, you must:
 > 

autopilot/known-issues.md

@@ -78,17 +78,12 @@ The following issues are under active investigation:
 
   For information on how to mitigate this error, see [Troubleshooting FAQ](/autopilot/troubleshooting-faq#troubleshooting-the-intune-connector-for-active-directory).
 
-### TPM attestation isn't working for TPMs which use high-range RSA 3072EK
-
-Date added: *April 4, 2025*
-
-Platforms with TPMs which use high-range RSA 3072EK might fail TPM attestation. This failure impacts Windows Autopilot pre-provisioning and Windows Autopilot self-deploying flows. The issue is being investigated.
-
 ### Setting up keyboard automatically doesn't accurately update keyboard language
 
 Date added: *April 4, 2025*
+Date updated: *December 16, 2025*
 
-The Windows Autopilot profile setting which enables automatic configuration of the keyboard language based on the **Language (Region)** setting might fail to apply during provisioning due to a known OS issue. There's no timeline for resolving this issue at this time.
+The Windows Autopilot profile setting which enables automatic configuration of the keyboard language based on the **Language (Region)** setting might fail to apply during provisioning due to a known OS issue. To resolve this issue, use [KB5072033](https://support.microsoft.com/en-us/topic/december-9-2025-kb5072033-os-builds-26200-7462-and-26100-7462-0c1a4334-19ba-406d-bb1e-88fcffc87b79) or above.
 
 ### Windows Autopilot report incorrectly shows failure even though the deployment was successful