From 08584563a89357ccb7f9aa48d95ba0a2180608b4 Mon Sep 17 00:00:00 2001 From: John Kaiser <35939694+CoveMiner@users.noreply.github.com> Date: Wed, 13 Nov 2024 10:01:27 -0800 Subject: [PATCH 1/4] link updates --- surface-hub/enroll-surface-hub-mdm.md | 2 +- surface/surface-manage-dfci-guide.md | 4 +--- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/surface-hub/enroll-surface-hub-mdm.md b/surface-hub/enroll-surface-hub-mdm.md index 533c804ea..ace178f20 100644 --- a/surface-hub/enroll-surface-hub-mdm.md +++ b/surface-hub/enroll-surface-hub-mdm.md @@ -32,7 +32,7 @@ You can enroll Surface into Microsoft Intune or other MDM provider via manual or ## Auto Enrollment — Microsoft Entra affiliated -During the [initial setup process](/surface-hub/first-run-program-surface-hub#microsoft-azure-active-directory), when affiliating Surface Hub with a Microsoft Entra tenant that has Intune auto enrollment enabled, the device will automatically enroll with Intune. To learn more, refer to [Intune enrollment methods for Windows devices](/intune/enrollment/windows-enrollment-methods). Microsoft Entra affiliation and Intune auto enrollment are required for the Surface Hub to be a "compliant device" in Intune. +During the [initial setup process](/surface-hub/first-run-program-surface-hub#microsoft-azure-active-directory), when affiliating Surface Hub with a Microsoft Entra tenant that has Intune auto enrollment enabled, the device will automatically enroll with Intune. To learn more, refer to [Enroll Windows client devices in Microsoft Intune](/mem/intune/fundamentals/deployment-guide-enrollment-windows). Microsoft Entra affiliation and Intune auto enrollment are required for the Surface Hub to be a "compliant device" in Intune. ## Manage Surface Hub via MDM diff --git a/surface/surface-manage-dfci-guide.md b/surface/surface-manage-dfci-guide.md index 19280500c..7800cb878 100644 --- a/surface/surface-manage-dfci-guide.md +++ b/surface/surface-manage-dfci-guide.md @@ -27,9 +27,7 @@ Designed to be used with software-level mobile device management (MDM), DFCI ena ## Prerequisites - Windows 11 or Windows 10 version 1809 (released November 2018) -- Devices must be registered with Windows Autopilot via one of the following methods: - - [Microsoft Cloud Solution Provider (CSP) partner](https://partner.microsoft.com/membership/cloud-solution-provider) - - [Directly from Surface](https://prod.support.services.microsoft.com/supportrequestform/0d8bf192-cab7-6d39-143d-5a17840b9f5f) +- Devices must be registered with Windows Autopilot. To learn more, see [Surface Registration Support for Windows Autopilot](surface-autopilot-registration-support.md) > [!NOTE] > Devices manually or self-registered for Autopilot, such as imported from a CSV file, aren't allowed to use DFCI. By design, DFCI management requires external attestation of the device's commercial acquisition via a Microsoft CSP partner or Surface registration. From ab4ecc229e734550d9d5d8dcab2f29987e1a76ef Mon Sep 17 00:00:00 2001 From: John Kaiser <35939694+CoveMiner@users.noreply.github.com> Date: Wed, 13 Nov 2024 10:14:53 -0800 Subject: [PATCH 2/4] Update enroll-surface-hub-mdm.md --- surface-hub/enroll-surface-hub-mdm.md | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/surface-hub/enroll-surface-hub-mdm.md b/surface-hub/enroll-surface-hub-mdm.md index ace178f20..22e3288da 100644 --- a/surface-hub/enroll-surface-hub-mdm.md +++ b/surface-hub/enroll-surface-hub-mdm.md @@ -1,39 +1,40 @@ --- title: Enroll Surface Hub to MDM provider -description: This page explains how to enroll Surface Hub to MDM provider +description: Learn how to enroll Surface Hub in MDM via manual or auto methods, including Intune setup for streamlined management and compliance manager: frankbu ms.service: surface-hub author: coveminer ms.author: chauncel ms.topic: how-to -ms.date: 01/27/2023 +ms.date: 11/13/2024 ms.localizationpriority: medium appliesto: - Surface Hub 2S - Surface Hub --- + # Enroll Surface Hub into MDM management -You can enroll Surface into Microsoft Intune or other MDM provider via manual or auto enrollment. +Learn how to enroll Surface Hub into Microsoft Intune or other Mobile Device Management (MDM) providers using manual or automatic enrollment options. ## Manual enrollment -1. Open the **Settings** app and sign in as a local administrator. Select **Surface Hub** > **Device management** and then select **+Device management**. -2. You will be prompted to sign in with the account to use for your MDM provider. After authenticating, the device automatically enrolls with your MDM provider. +1. Open the **Settings** app, sign in as a local administrator, and go to **Surface Hub** > **Device management**. Select **+Device management**. +2. Sign in with the account to use with your MDM provider. After authentication, the device automatically enrolls with your MDM provider. -> [!TIP] -> If you’re using Intune and the server address is not detected, enter **manage.microsoft.com**. +> [!TIP] +> If you’re using Intune and the server address isn’t automatically detected, enter **manage.microsoft.com**. -> [!NOTE] -> MDM enrollment uses the account details provided for authentication. The account must have permissions to enroll a Windows device as well as an Intune license (or the equivalent enrollment promissions configured in your third-party MDM provider). +> [!NOTE] +> MDM enrollment uses the provided account for authentication. Ensure this account has permissions to enroll a Windows device and an Intune license or equivalent permissions in your third-party MDM provider. -## Auto Enrollment — Microsoft Entra affiliated +## Auto enrollment with Microsoft Entra affiliation -During the [initial setup process](/surface-hub/first-run-program-surface-hub#microsoft-azure-active-directory), when affiliating Surface Hub with a Microsoft Entra tenant that has Intune auto enrollment enabled, the device will automatically enroll with Intune. To learn more, refer to [Enroll Windows client devices in Microsoft Intune](/mem/intune/fundamentals/deployment-guide-enrollment-windows). Microsoft Entra affiliation and Intune auto enrollment are required for the Surface Hub to be a "compliant device" in Intune. +During the [initial setup process](/surface-hub/first-run-program-surface-hub#microsoft-azure-active-directory), if you affiliate Surface Hub with a Microsoft Entra tenant that has Intune auto enrollment enabled, the device automatically enrolls in Intune. For more information, see [Enroll Windows client devices in Microsoft Intune](/mem/intune/fundamentals/deployment-guide-enrollment-windows). Microsoft Entra affiliation and Intune auto enrollment are required for Surface Hub to be a "compliant device" in Intune. ## Manage Surface Hub via MDM -- See [Manage Surface Hub with an MDM provider](manage-settings-with-mdm-for-surface-hub.md) +- For more management options, see [Manage Surface Hub with an MDM provider](manage-settings-with-mdm-for-surface-hub.md). \ No newline at end of file From 8d4adbb3c4adca18444605c749893d2c1e2fa04f Mon Sep 17 00:00:00 2001 From: John Kaiser <35939694+CoveMiner@users.noreply.github.com> Date: Wed, 13 Nov 2024 10:20:33 -0800 Subject: [PATCH 3/4] Update surface-manage-dfci-guide.md --- surface/surface-manage-dfci-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/surface/surface-manage-dfci-guide.md b/surface/surface-manage-dfci-guide.md index 7800cb878..fb4fc0745 100644 --- a/surface/surface-manage-dfci-guide.md +++ b/surface/surface-manage-dfci-guide.md @@ -26,7 +26,7 @@ Designed to be used with software-level mobile device management (MDM), DFCI ena ## Prerequisites -- Windows 11 or Windows 10 version 1809 (released November 2018) +- Windows 11 or Windows 10 version 1809 or later - Devices must be registered with Windows Autopilot. To learn more, see [Surface Registration Support for Windows Autopilot](surface-autopilot-registration-support.md) > [!NOTE] From f45f0599061aa116716bd56855b58e7e7256727e Mon Sep 17 00:00:00 2001 From: John Kaiser <35939694+CoveMiner@users.noreply.github.com> Date: Wed, 13 Nov 2024 10:23:53 -0800 Subject: [PATCH 4/4] Update surface-manage-dfci-guide.md --- surface/surface-manage-dfci-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/surface/surface-manage-dfci-guide.md b/surface/surface-manage-dfci-guide.md index fb4fc0745..37f7aeda9 100644 --- a/surface/surface-manage-dfci-guide.md +++ b/surface/surface-manage-dfci-guide.md @@ -27,7 +27,7 @@ Designed to be used with software-level mobile device management (MDM), DFCI ena ## Prerequisites - Windows 11 or Windows 10 version 1809 or later -- Devices must be registered with Windows Autopilot. To learn more, see [Surface Registration Support for Windows Autopilot](surface-autopilot-registration-support.md) +- Devices must be registered with Windows Autopilot. To learn more, see [Surface Registration Support for Windows Autopilot](surface-autopilot-registration-support.md). > [!NOTE] > Devices manually or self-registered for Autopilot, such as imported from a CSV file, aren't allowed to use DFCI. By design, DFCI management requires external attestation of the device's commercial acquisition via a Microsoft CSP partner or Surface registration.