Merge branch 'main' into patch-11

.github/workflows/BuildValidation.yml

@@ -0,0 +1,21 @@
+name: PR has no warnings or errors
+
+permissions:
+  pull-requests: write
+  statuses: write
+
+on: 
+  issue_comment:
+    types: [created]
+
+jobs:
+
+  build-status:
+    uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-BuildValidation.yml@workflows-prod
+    with:
+      PayloadJson: ${{ toJSON(github) }}
+    secrets:
+      AccessToken: ${{ secrets.GITHUB_TOKEN }}
+
+
+

.openpublishing.redirection.json

@@ -4,7 +4,7 @@
       "source_path": "memdocs/intune/enrollment/chrome-enterprise-device-details.md",
       "redirect_url": "/mem/intune/remote-actions/chrome-enterprise-device-details",
       "redirect_document_id": true
-    },    
+    },
     {
       "source_path": "memdocs/intune/enrollment/chrome-enterprise-remote-actions.md",
       "redirect_url": "/mem/intune/remote-actions/chrome-enterprise-remote-actions",
@@ -14,27 +14,27 @@
       "source_path": "memdocs/intune/user-help/sso-dialog-faqs.yml",
       "redirect_url": "https://support.microsoft.com/topic/a6505ceb-1a20-4b15-889c-250175481506",
       "redirect_document_id": false
-    },  
+    },
     {
       "source_path": "memdocs/intune/user-help/you-need-to-resolve-a-threat-found-by-zips-android.md",
       "redirect_url": "/mem/intune/user-help/set-up-mobile-threat-defense",
       "redirect_document_id": false
-    },  
+    },
     {
       "source_path": "memdocs/intune/user-help/you-need-to-resolve-a-threat-found-by-checkpoint-android.md",
       "redirect_url": "/mem/intune/user-help/set-up-mobile-threat-defense",
       "redirect_document_id": false
-    },    
+    },
     {
       "source_path": "memdocs/intune/user-help/you-need-to-resolve-a-threat-found-by-skycure-android.md",
       "redirect_url": "/mem/intune/user-help/set-up-mobile-threat-defense",
       "redirect_document_id": false
-    },    
+    },
     {
       "source_path": "memdocs/intune/user-help/you-need-to-resolve-a-threat-found-by-lookout-for-work-android.md",
       "redirect_url": "/mem/intune/user-help/set-up-mobile-threat-defense",
       "redirect_document_id": false
-    },    
+    },
     {
       "source_path": "memdocs/intune/user-help/you-need-to-resolve-a-threat-found-by-zips-ios.md",
       "redirect_url": "/mem/intune/user-help/set-up-mobile-threat-defense",
@@ -2735,7 +2735,7 @@
       "redirect_url": "/windows-365/enterprise/requirements-omnissa-horizon",
       "redirect_document_id": false
     },
-   {
+    {
       "source_path": "memdocs/configmgr/core/clients/manage/monitor-windows-analytics.md",
       "redirect_url": "/mem/configmgr/core/clients/manage/upgrade-readiness#bkmk_remove",
       "redirect_document_id": false
@@ -2774,6 +2774,71 @@
       "source_path": "memdocs/intune/protect/endpoint-security-firewall-rule-tool.md",
       "redirect_url": "/mem/intune/protect/endpoint-security-firewall-policy",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "windows-365/link/conditional-access-policies-synchronize.md",
+      "redirect_url": "/windows-365/link/conditional-access-policies",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows-365/business/troubleshoot-windows-365-business.md",
+      "redirect_url": "/troubleshoot/windows-365/troubleshoot-windows-365-business",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows-365/business/known-issues.md",
+      "redirect_url": "/troubleshoot/windows-365/known-issues",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows-365/enterprise/known-issues-enterprise.md",
+      "redirect_url": "/troubleshoot/windows-365/known-issues-enterprise",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows-365/enterprise/troubleshoot-azure-network-connection.md",
+      "redirect_url": "/troubleshoot/windows-365/troubleshoot-azure-network-connection",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows-365/enterprise/health-checks.md",
+      "redirect_url": "/troubleshoot/windows-365/health-checks",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows-365/enterprise/connection-errors.md",
+      "redirect_url": "/troubleshoot/windows-365/connection-errors",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows-365/enterprise/provisioning-errors.md",
+      "redirect_url": "/troubleshoot/windows-365/provisioning-errors",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows-365/enterprise/troubleshoot-partner-connector.md",
+      "redirect_url": "/troubleshoot/windows-365/troubleshoot-partner-connector",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows-365/enterprise/troubleshoot-windows-365-app.md",
+      "redirect_url": "/troubleshoot/windows-365/troubleshoot-windows-365-app",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows-365/enterprise/troubleshoot-windows-365-boot.md",
+      "redirect_url": "/troubleshoot/windows-365/troubleshoot-windows-365-boot",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows-365/enterprise/windows-365-boot-known-issues.md",
+      "redirect_url": "/troubleshoot/windows-365/windows-365-boot-known-issues",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows-365/enterprise/windows-365-switch-known-issues.md",
+      "redirect_url": "/troubleshoot/windows-365/windows-365-switch-known-issues",
+      "redirect_document_id": false
     }
   ]
 }

README.md

@@ -6,7 +6,7 @@ Anyone who is interested can contribute to the topics. When you contribute, your
 
 ### Quickly update an article using GitHub.com
 
-Contributors who only make infrequent or small updates can edit the file directly on GitHub.com without having to install any additional software. This article shows you how. [This two-minute video](https://www.microsoft.com/videoplayer/embed/RE1XQTG) also covers how to contribute.
+Contributors who only make infrequent or small updates can edit the file directly on GitHub.com without having to install any additional software. This article shows you how. [This two-minute video](https://learn-video.azurefd.net/vod/player?id=b5167c5a-9c69-499b-99ac-e5467882bc92) also covers how to contribute.
 
 1. Make sure you're signed in to GitHub.com with your GitHub account.
 2. Browse to the page you want to edit on Microsoft Learn.

autopilot/device-preparation/faq.yml

@@ -9,7 +9,7 @@ metadata:
   ms.author: frankroj
   ms.reviewer: jubaptis
   manager: aaroncz
-  ms.date: 07/29/2024
+  ms.date: 11/25/2024
   ms.collection:
     - M365-modern-desktop
     - highpri
@@ -74,7 +74,7 @@ sections:
       - question: |
           How do users know when the required setup is complete?
         answer: |
-          Many users aren't sure when the provisioning process is complete. To help mitigate confusion and calls to support, we added a completion page in OOBE. Administrators can configure the page to require a user to manually select **Continue** or set the page to auto-continue. This message lets the user know that OOBE setup is complete. However, additional installations that were assigned to the device group but not specified in the Windows Autopilot device preparation policy might still be occurring in the background.
+          Many users aren't sure when the provisioning process is complete. To help mitigate confusion and calls to support, we added a completion page in OOBE. The completion page lets the user know that OOBE setup is complete. However, additional installations that were assigned to the device group but not specified in the Windows Autopilot device preparation policy might still be occurring in the background.
 
       - question: |
           Can Windows Autopilot Device preparation be used by non-Microsoft mobile device management (MDM) providers?

autopilot/device-preparation/known-issues.md

@@ -8,7 +8,7 @@ author: frankroj
 ms.author: frankroj
 ms.reviewer: jubaptis
 manager: aaroncz
-ms.date: 10/18/2024
+ms.date: 01/06/2025
 ms.collection:
   - M365-modern-desktop
   - highpri
@@ -40,14 +40,26 @@ This article describes known issues that can often be resolved with:
 
 ## Known issues
 
-## Deployments fail when Managed installer policy is enabled for the tenant
+## Exporting logs during the out-of-box experience (OOBE) doesn't show result
 
-Date added: *October 10, 2024*<br>
-Date updated: *October 18, 2024*
+Date added: *January 6, 2025*
+
+When a failure occurs during the provisioning process, an **Export logs** option is displayed to the user. When selected, it saves the file to the first USB drive on the device without displaying the browse dialog. The browse dialog isn't displayed for security reasons. Currently, users don't see failure or success messages to indicate the logs were saved. This issue will be fixed in the future.
+
+## Apps and scripts tabs don't display properly when editing the Windows Autopilot device preparation profile
+
+Date added: *December 18, 2024*
 
-When the [Managed installer policy](/mem/intune/protect/endpoint-security-app-control-policy#managed-installer) is **Active** for a tenant and Win32 apps are selected in the Windows Autopilot device preparation policy, Windows Autopilot device preparation deployments fails. The issue is being investigated.
+During the editing flow of the Windows Autopilot device preparation policy, there's a known issue when displaying the **Applications** and **Scripts** tabs where the tabs might display incorrect information. For example, under the **Scripts** tab, a list of applications might be shown instead of a list of scripts. The issue is impacting only the view in Microsoft Intune and not the configuration being applied to the device. The issue is being investigated.
+
+As a workaround, select the table header **Allowed Applications** or **Allowed Scripts** to reload the table's contents.
+
+## Win32 and WinGet applications are skipped when Managed installer policy is enabled for the tenant
+
+Date added: *October 10, 2024*<br>
+Date updated: *November 15, 2024*
 
-As a workaround, remove Win32 applications from the list of selected apps in all device preparation policies.
+When the [Managed installer policy](/mem/intune/protect/endpoint-security-app-control-policy#managed-installer) is **Active** for a tenant, Win32 apps and Microsoft Store apps aren't delivered during OOBE. The apps are instead installed after the device gets to the Desktop and the Managed installer policy is delivered. The [Windows Autopilot device preparation deployment status report](whats-new.md#windows-autopilot-device-preparation-deployment-status-report-available-in-the-monitor-tab-under-enrollment) reports the apps as **Skipped.**
 
 For more information, see [Known issue: Windows Autopilot device preparation with Win32 apps and managed installer policy](https://techcommunity.microsoft.com/t5/intune-customer-success/known-issue-windows-autopilot-device-preparation-with-win32-apps/ba-p/4273286).
 

autopilot/device-preparation/overview.md

@@ -8,7 +8,7 @@ author: frankroj
 ms.author: frankroj
 ms.reviewer: jubaptis
 manager: aaroncz
-ms.date: 06/03/2024
+ms.date: 01/14/2025
 ms.topic: overview
 ms.collection:
   - M365-modern-desktop
@@ -134,7 +134,9 @@ For more information, see [Enrollment time grouping in Microsoft Intune](/mem/in
 
 ### Corporate identifiers for Windows
 
-Windows Autopilot device preparation supports the Intune corporate identifier enrollment feature. Corporate identifiers in Intune allows pre-uploading of Windows device identifiers (serial number, manufacturer, model) and ensures only trusted devices go through Windows Autopilot device preparation. Corporate identifiers for Windows is optional for Windows Autopilot device preparation. Corporate identifiers for Windows isn't required for a Windows Autopilot device preparation deployment to work. For more information, see:
+Windows Autopilot device preparation supports the Intune corporate identifier enrollment feature. Corporate identifiers in Intune allows pre-uploading of Windows device identifiers (serial number, manufacturer, model) and ensures only trusted devices go through Windows Autopilot device preparation.
+
+Windows Autopilot device preparation only requires corporate identifiers for Windows if Intune enrollment restrictions are being used to block personal device enrollments. For more information, see:
 
 - [Identify devices as corporate-owned](/mem/intune/enrollment/corporate-identifiers-add).
 - [What are enrollment restrictions?](/mem/intune/enrollment/enrollment-restrictions-set).

autopilot/device-preparation/requirements.md

@@ -6,9 +6,9 @@ ms.subservice: autopilot
 ms.localizationpriority: medium
 author: frankroj
 ms.author: frankroj
-ms.reviewer: jubaptis
+ms.reviewer: madakeva
 manager: aaroncz
-ms.date: 09/05/2024
+ms.date: 01/24/2025
 ms.collection:
   - M365-modern-desktop
   - highpri
@@ -54,6 +54,7 @@ Windows Autopilot device preparation depends on specific features available in W
 
 #### Windows 11
 
+- Windows 11, version 24H2 or later
 - Windows 11, version 23H2 with [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) or later - Windows installation media dated April 2024 or later has [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) included.
 - Windows 11, version 22H2 with [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) or later - Windows installation media dated April 2024 or later has [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) included.
 
@@ -69,6 +70,7 @@ The following editions are supported:
 - Windows 11 Pro for Workstations.
 - Windows 11 Enterprise.
 - Windows 11 Education.
+- [Windows 11 Enterprise LTSC](/windows/whats-new/ltsc/overview).
 
 ## [:::image type="icon" source="../images/icons/wifi-ethernet-18.svg"::: **Networking**](#tab/networking)
 

autopilot/device-preparation/tutorial/user-driven/entra-join-allow-users-to-join.md

@@ -7,7 +7,7 @@ author: frankroj
 ms.author: frankroj
 ms.reviewer: jubaptis
 manager: aaroncz
-ms.date: 06/03/2024
+ms.date: 01/14/2025
 ms.topic: tutorial
 ms.collection:
   - tier1
@@ -31,7 +31,7 @@ Windows Autopilot device preparation user-driven Microsoft Entra join steps:
 - Step 4: [Create a user group](entra-join-user-group.md)
 - Step 5: [Assign applications and PowerShell scripts to device group](entra-join-assign-apps-scripts.md)
 - Step 6: [Create Windows Autopilot device preparation policy](entra-join-autopilot-policy.md)
-- Step 7: [Add Windows corporate identifier to device (optional)](entra-join-corporate-identifier.md)
+- Step 7: [Add Windows corporate identifier to device](entra-join-corporate-identifier.md)
 
 For an overview of the Windows Autopilot device preparation user-driven Microsoft Entra join workflow, see [Windows Autopilot device preparation user-driven Microsoft Entra join overview](entra-join-workflow.md#workflow).
 

autopilot/device-preparation/tutorial/user-driven/entra-join-assign-apps-scripts.md

@@ -7,7 +7,7 @@ author: frankroj
 ms.author: frankroj
 ms.reviewer: jubaptis
 manager: aaroncz
-ms.date: 06/03/2024
+ms.date: 01/14/2025
 ms.topic: tutorial
 ms.collection:
   - tier1
@@ -31,7 +31,7 @@ Windows Autopilot device preparation user-driven Microsoft Entra join steps:
 > - **Step 5: Assign applications and PowerShell scripts to device group**
 
 - Step 6: [Create Windows Autopilot device preparation policy](entra-join-autopilot-policy.md)
-- Step 7: [Add Windows corporate identifier to device (optional)](entra-join-corporate-identifier.md)
+- Step 7: [Add Windows corporate identifier to device](entra-join-corporate-identifier.md)
 
 For an overview of the Windows Autopilot device preparation user-driven Microsoft Entra join workflow, see [Windows Autopilot device preparation user-driven Microsoft Entra join overview](entra-join-workflow.md#workflow).
 

autopilot/device-preparation/tutorial/user-driven/entra-join-automatic-enrollment.md

@@ -7,7 +7,7 @@ author: frankroj
 ms.author: frankroj
 ms.reviewer: jubaptis
 manager: aaroncz
-ms.date: 06/03/2024
+ms.date: 01/14/2025
 ms.topic: tutorial
 ms.collection:
   - tier1
@@ -30,7 +30,7 @@ Windows Autopilot device preparation user-driven Microsoft Entra join steps:
 - Step 4: [Create a user group](entra-join-user-group.md)
 - Step 5: [Assign applications and PowerShell scripts to device group](entra-join-assign-apps-scripts.md)
 - Step 6: [Create Windows Autopilot device preparation policy](entra-join-autopilot-policy.md)
-- Step 7: [Add Windows corporate identifier to device (optional)](entra-join-corporate-identifier.md)
+- Step 7: [Add Windows corporate identifier to device](entra-join-corporate-identifier.md)
 
 For an overview of the Windows Autopilot device preparation user-driven Microsoft Entra join workflow, see [Windows Autopilot device preparation user-driven Microsoft Entra join overview](entra-join-workflow.md#workflow).
 

autopilot/device-preparation/tutorial/user-driven/entra-join-autopilot-policy.md

@@ -7,7 +7,7 @@ author: frankroj
 ms.author: frankroj
 ms.reviewer: jubaptis
 manager: aaroncz
-ms.date: 06/28/2024
+ms.date: 01/14/2025
 ms.topic: tutorial
 ms.collection:
   - tier1
@@ -31,7 +31,7 @@ Windows Autopilot device preparation user-driven Microsoft Entra join steps:
 >
 > - **Step 6: Create Windows Autopilot device preparation policy**
 
-- Step 7: [Add Windows corporate identifier to device (optional)](entra-join-corporate-identifier.md)
+- Step 7: [Add Windows corporate identifier to device](entra-join-corporate-identifier.md)
 
 For an overview of the Windows Autopilot device preparation user-driven Microsoft Entra join workflow, see [Windows Autopilot device preparation user-driven Microsoft Entra join overview](entra-join-workflow.md#workflow).
 
@@ -172,11 +172,11 @@ In the **Configuration settings** page:
 
 If multiple Windows Autopilot device preparation polices are deployed to a user, the policy with the highest priority as displayed in the **Home** > **Enroll devices | Windows enrollment** > **Device preparation policies** screen gets priority. The policy with the highest priority is higher in the list and has the smallest number under the **Priority** column. To change a policy's priority, move it in the list by dragging the policy within the list.
 
-## Next step: Add Windows corporate identifier to device (optional)
+## Next step: Add Windows corporate identifier to device
 
 > [!div class="nextstepaction"]
-> [Step 7: Add Windows corporate identifier to device (optional)](entra-join-corporate-identifier.md)
+> [Step 7: Add Windows corporate identifier to device](entra-join-corporate-identifier.md)
 
 > [!NOTE]
 >
-> Adding a [corporate identifier](../../overview.md#corporate-identifiers-for-windows) to the device is an optional step. If corporate identifiers aren't being used, then the next step is to deploy the device.
+> Windows Autopilot device preparation only requires [corporate identifiers for Windows](../../overview.md#corporate-identifiers-for-windows) if Intune enrollment restrictions are being used to block personal device enrollments. If Intune enrollment restrictions aren't being used to block personal device enrollments, then the next step is to deploy the device.