แก้ไข

แชร์ผ่าน

Tutorial: Set up and configure a cloud-native Windows endpoint with Microsoft Intune

  • บทความ

Tip

When reading about cloud native endpoints, you see the following terms:

  • Endpoint: An endpoint is a device, like a mobile phone, tablet, laptop, or desktop computer. "Endpoints" and "devices" are used interchangeably.
  • Managed endpoints: Endpoints that receive policies from the organization using an MDM solution or Group Policy Objects. These devices are typically organization owned, but can also be BYOD or personally owned devices.
  • Cloud native endpoints: Endpoints that are joined to Microsoft Entra. They aren't joined to on-premises AD.
  • Workload: Any program, service, or process.

This guide walks you through the steps to create a cloud-native Windows endpoint configuration for your organization. For an overview of cloud-native endpoints, and their benefits, see What are cloud-native endpoints.

This feature applies to:

  • Windows cloud-native endpoints

Tip

If you want a Microsoft recommended, standardized solution to build on top of, then you might be interested in Windows in cloud configuration. For an Intune Guided Scenario, see Windows 10/11 in cloud configuration.

The following table describes the key difference between this guide and Windows in cloud configuration:

Solution Objective
Tutorial: Get started with cloud-native Windows endpoints (this guide) Guides you through creating your own configuration for your environment, based on Microsoft recommended settings, and helps you start testing.
Windows in cloud configuration A guided scenario experience that creates and applies a pre-built configuration based on Microsoft best practices for frontline, remote, and other workers with more focused needs.

You can use this guide combined with Windows in cloud configuration to customize the pre-built experience even more.

How to get started

Use the five ordered phases in this guide, which build on each other to help you prepare your cloud-native Windows endpoint configuration. By completing these phases in order, you see tangible progress and are ready to provision new devices.

Phases:

Five phases for setting up cloud-native Windows endpoints using Microsoft Intune and Windows Autopilot.

  • Phase 1 – Set up your environment
  • Phase 2 – Build your first cloud-native Windows endpoint
  • Phase 3 – Secure your cloud-native Windows endpoint
  • Phase 4 – Apply your custom settings and applications
  • Phase 5 – Deploy at scale with Windows Autopilot

At the end of this guide, you have a cloud-native Windows endpoint ready to start testing in your environment. Before you get started, you might want to check out the Microsoft Entra join planning guide at How to plan your Microsoft Entra join implementation.

Phase 1 – Set up your environment

Image that shows phase 1, set up your environment for cloud native endpoints with Microsoft Intune

Before you build your first cloud-native Windows endpoint, there are some key requirements and configuration that need to be checked. This phase walks you through checking the requirements, configuring Windows Autopilot, and creating some settings and applications.

Step 1 - Network requirements

Your cloud-native Windows endpoint needs access to several internet services. Start your testing on an open network. Or, use your corporate network after providing access to all the endpoints that are listed at Windows Autopilot networking requirements.

If your wireless network requires certificates, you can start with an Ethernet connection during testing while you determine the best approach for wireless connections for device provisioning.

Step 2 - Enrollment and Licensing

Before you can join Microsoft Entra and enroll in Intune, there are a few things you need to check. You could create a new Microsoft Entra group, such as the name Intune MDM Users. Then, add specific test user accounts and target each of the following configurations at that group to limit who can enroll devices while you set up your configuration. To create a Microsoft Entra group, go to Manage Microsoft Entra groups and group membership.

  • Enrollment restrictions Enrollment restrictions allow you to control what types of devices can enroll into management with Intune. For this guide to be successful, make sure Windows (MDM) enrollment is allowed, which is the default configuration.

    For information on configuring Enrollment Restrictions, go to Set enrollment restrictions in Microsoft Intune.

  • Microsoft Entra Device MDM settings When you join a Windows device to Microsoft Entra, Microsoft Entra can be configured to tell your devices to automatically enroll with an MDM. This configuration is required for Windows Autopilot to work.

    To check your Microsoft Entra Device MDM settings are enabled properly, go to Quickstart - Set up automatic enrollment in Intune.

  • Microsoft Entra company branding Adding your corporate logo and images to Microsoft Entra ensures that users see a familiar and consistent look-and-feel when they sign-in to Microsoft 365. This configuration is required for Windows Autopilot to work.

    For information on configuring custom branding in Microsoft Entra, go to Add branding to your organization's Microsoft Entra sign-in page.

  • Licensing Users enrolling Windows devices from the Out Of Box Experience (OOBE) into Intune require two key capabilities.

    Users require the following licenses:

    • A Microsoft Intune or Microsoft Intune for Education license
    • A license like one of the following options that allows for automatic MDM enrollment:
      • Microsoft Entra Premium P1
      • Microsoft Intune for Education

    To assign licenses, go to Assign Microsoft Intune licenses.

    Note

    Both types of licenses are typically included with licensing bundles, like Microsoft 365 E3 (or A3) and higher. View comparisons of M365 licensing here.

Step 3 - Import your test device

To test the cloud-native Windows endpoint, we need to start by getting a virtual machine or physical device ready for testing. The following steps get the device details and upload them into the Windows Autopilot service, which are used later in this article.

Note

While the following steps provide a way to import a device for testing, Partners and OEMs can import devices into Windows Autopilot on your behalf as part of purchasing. There is more information about Windows Autopilot in Phase 5.

  1. Install Windows (preferably 20H2 or later) in a virtual machine or reset physical device so that it's waiting at the OOBE setup screen. For a virtual machine, you can optionally create a checkpoint.

  2. Complete the necessary steps to connect to the Internet.

  3. Open a command prompt by using the Shift + F10 keyboard combination.

  4. Verify that you have internet access by pinging bing.com:

    • ping bing.com

  5. Switch into PowerShell by running the command:

    • powershell.exe

  6. Download the Get-WindowsAutopilotInfo script by running the following commands:

    • Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process
    • Install-Script Get-WindowsAutopilotInfo

  7. When prompted, enter Y to accept.

  8. Type the following command:

    • Get-WindowsAutopilotInfo.ps1 -GroupTag CloudNative -Online

    Note

    Group Tags allow you to create dynamic Microsoft Entra groups based on a subset of devices. Group Tags can be set when importing devices or changed later in the Microsoft Intune admin center. We'll use the Group Tag CloudNative in Step 4. You can set the tag name to something different for your testing.

  9. When prompted for credentials, sign in with your Intune Administrator account.

  10. Leave the computer at the out of box experience until Phase 2.

Step 4 - Create Microsoft Entra dynamic group for the device

To limit the configurations from this guide to the test devices that you import to Windows Autopilot, create a dynamic Microsoft Entra group. This group should automatically include the devices that import to Windows Autopilot and have the Group Tag CloudNative. You can then target all your configurations and applications at this group.

  1. Open the Microsoft Intune admin center.

  2. Select Groups > New group. Enter the following details:

    • Group type: Select Security.
    • Group Name: Enter Autopilot Cloud-Native Windows Endpoints.
    • Membership type: Select Dynamic Device.

  3. Select Add dynamic query.

  4. In the Rule Syntax section, select Edit.

  5. Paste the following text:

    (device.devicePhysicalIds -any (_ -eq "[OrderID]:CloudNative"))

  6. Select OK > Save > Create.

Tip

Dynamic groups take a few minutes to populate after changes occur. In large organizations, it can take much longer. After creating a new group, wait a few minutes before you check to confirm the device is now a member of the group.

For more information about dynamic groups for devices, go to Rules for devices.

Step 5 - Configure the Enrollment Status Page

The enrollment status page (ESP) is the mechanism an IT pro uses to control the end-user experience during endpoint provisioning. See Set up the Enrollment Status Page. To limit the scope of the enrollment status page, you can create a new profile and target the Autopilot Cloud-Native Windows Endpoints group created in the previous step, Create Microsoft Entra dynamic group for the device.

  • For the purposes of testing, we recommend the following settings, but feel free to adjust them as required:
    • Show app and profile configuration progress - Yes
    • Only show page to devices provisioned by out-of-box experience (OOBE) – Yes (default)

Step 6 - Create and assign the Windows Autopilot profile

Now we can create the Windows Autopilot profile and assign it to our test device. This profile tells your device to join Microsoft Entra and what settings to apply during OOBE.

  1. Open the Microsoft Intune admin center.

  2. Select Devices > Device onboarding > Enrollment > Windows > Windows Autopilot > Deployment profiles.

  3. Select Create profile > Windows PC.

  4. Enter the name Autopilot Cloud-Native Windows Endpoint, and then select Next.

  5. Review and leave the default settings and select Next.

  6. Leave the scope tags and select Next.

  7. Assign the profile to the Microsoft Entra group you created called Autopilot Cloud-Native Windows Endpoint, select Next, and then select Create.

Step 7 - Sync Windows Autopilot devices

The Windows Autopilot service synchronizes several times a day. You can also trigger a sync immediately so that your device is ready to test. To synchronize immediately:

  1. Open the Microsoft Intune admin center.

  2. Select Devices > Device onboarding > Enrollment > Windows > Windows Autopilot > Devices.

  3. Select Sync.

The sync takes several minutes and continues in the background. When the sync is complete, the profile status for the imported device displays Assigned.

Step 8 - Configure settings for an optimal Microsoft 365 experience

We've selected a few settings to configure. These settings demonstrate an optimal Microsoft 365 end-user experience on your Windows cloud-native device. These settings are configured using a device configuration settings catalog profile. For more information, go to Create a policy using the settings catalog in Microsoft Intune.

After you've created the profile and added your settings, assign the profile to the Autopilot Cloud-Native Windows Endpoints group created previously.

  • Microsoft Outlook To improve the first run experience for Microsoft Outlook, the following setting automatically configures a profile when Outlook is opened for the first time.

    • Microsoft Outlook 2016\Account Settings\Exchange (User setting)
      • Automatically configure only the first profile based on Active Directory primary SMTP address - Enabled

  • Microsoft Edge To improve the first run experience for Microsoft Edge, the following settings configure Microsoft Edge to sync the user's settings and skip the first run experience.

    • Microsoft Edge
      • Hide the first-run experience and splash screen - Enabled
      • Force synchronization of browser data and do not show the sync consent prompt - Enabled

  • Microsoft OneDrive

    To improve the first sign-in experience, the following settings configure Microsoft OneDrive to automatically sign in and redirect Desktop, Pictures, and Documents to OneDrive. Files On-Demand (FOD) is also recommended. It's enabled by default and isn't included in the following list. For more information on the recommended configuration for the OneDrive sync app, go to Recommended sync app configuration for Microsoft OneDrive.

    • OneDrive

      • Silently sign in users to the OneDrive sync app with their Windows credentials - Enabled
      • Silently move Windows known folders to OneDrive – Enabled

      Note

      For more information, go to Redirect Known Folders.

The following screenshot shows an example of a settings catalog profile with each of the suggested settings configured:

Screenshot that shows an example of a settings catalog profile in Microsoft Intune.

Step 9 - Create and assign some applications

Your cloud-native endpoint needs some applications. To get started, we recommend configuring the following applications and targeting them at the Autopilot Cloud-Native Windows Endpoints group created previously.

  • Microsoft 365 Apps (formerly Office 365 ProPlus) Microsoft 365 Apps such as Word, Excel, and Outlook can easily be deployed to devices using the built-in Microsoft 365 apps for Windows app profile in Intune.

    • Select configuration designer for the settings format, as opposed to XML.
    • Select Current Channel for the update channel.

    To deploy Microsoft 365 Apps, go to Add Microsoft 365 apps to Windows devices using Microsoft Intune

  • Company Portal app Deploying the Intune Company Portal app to all devices as a required application is recommended. Company Portal app is the self-service hub for users that they use to install applications from multiple sources, like Intune, Microsoft Store, and Configuration Manager. Users also use the Company Portal app to sync their device with Intune, check compliance status, and so on.

    To deploy Company Portal as required, see Add and assign the Windows Company Portal app for Intune managed devices.

  • Microsoft Store App (Whiteboard) While Intune can deploy a wide variety of apps, we deploy a store app (Microsoft Whiteboard) to help keep things simple for this guide. Follow the steps in Add Microsoft Store apps to Microsoft Intune to install Microsoft Whiteboard.

Phase 2 - Build a cloud-native Windows endpoint

Phase 2.

To build your first cloud-native Windows endpoint, use the same virtual machine or physical device that you gathered and then uploaded the hardware hash to the Windows Autopilot service in Phase 1 > Step 3. With this device, go through the Windows Autopilot process.

  1. Resume (or reset if necessary) your Windows PC to the Out of Box Experience (OOBE).

    Note

    If you're prompted to choose setup for personal or an organization, then the Autopilot process hasn't triggered. In that situation, restart the device and ensure it has internet access. If it still doesn't work, try resetting the PC or reinstalling Windows.

  2. Sign in with Microsoft Entra credentials (UPN or AzureAD\username).

  3. The enrollment status page shows the status of the device configuration.

Congratulations! You've provisioned your first cloud-native Windows endpoint!

Some things to check out on your new cloud-native Windows endpoint:

  • The OneDrive folders are redirected. When Outlook opens, it's configured automatically to connect to Office 365.

  • Open the Company Portal app from the Start Menu and notice that Microsoft Whiteboard is available for installation.

  • Consider testing access from the device to on-premises resources like file shares, printers, and intranet sites.

    Note

    If you haven't set up Windows Hello for Business Hybrid, you might be prompted on Windows Hello logons to enter passwords to access on-premises resources. To continue testing single sign on access you can configure Windows Hello for Business Hybrid or logon to the device with username and password rather than Windows Hello. To do so, select the key shaped icon on the logon screen.

Phase 3 – Secure your cloud-native Windows endpoint

Phase 3.

This phase is designed to help you build out security settings for your organization. This section draws your attention to the various Endpoint Security components in Microsoft Intune including:

Microsoft Defender Antivirus (MDAV)

The following settings are recommended as a minimum configuration for Microsoft Defender Antivirus, a built-in OS component of Windows. These settings don't require any specific licensing agreement such as E3 or E5, and can be enabled in the Microsoft Intune admin center. In the admin center, go to Endpoint Security > Antivirus > Create Policy > Windows and later > Profile type = Microsoft Defender Antivirus.

Cloud Protection:

  • Turn on cloud-delivered protection: Yes
  • Cloud-delivered protection level: Not configured
  • Defender Cloud Extended Timeout In Seconds: 50

Real-time protection:

  • Turn on real-time protection: Yes
  • Enable on access protection: Yes
  • Monitoring for incoming and outgoing files: Monitor all files
  • Turn on behavior monitoring: Yes
  • Turn on intrusion prevention: Yes
  • Enable network protection: Enable
  • Scan all downloaded file and attachments: Yes
  • Scan scripts that are used in Microsoft browsers: Yes
  • Scan network files: Not Configured
  • Scan emails: Yes

Remediation:

  • Number of days (0-90) to keep quarantined malware: 30
  • Submit samples consent: Send safe samples automatically
  • Action to take on potentially unwanted apps: Enable
  • Actions for detected threats: Configure
    • Low threat: Quarantine
    • Moderate threat: Quarantine
    • High threat: Quarantine
    • Severe threat: Quarantine

Settings configured in the MDAV profile within Endpoint Security:

Screenshot that shows an example of a Microsoft Defender Antivirus profile in Microsoft Intune.

For more information on Windows Defender configuration, including Microsoft Defender for Endpoint for customer's licensed for E3 and E5, go to:

Microsoft Defender Firewall

Use Endpoint Security in Microsoft Intune to configure the firewall and firewall rules. For more information, go to Firewall policy for endpoint security in Intune.

Microsoft Defender Firewall can detect a trusted network using the NetworkListManager CSP. And, it can switch to the domain firewall profile on endpoints running the following OS versions:

Using the domain network profile allows you to separate firewall rules based on a trusted network, a private network, and a public network. These settings can be applied using a Windows custom profile.

Note

Microsoft Entra joined endpoints cannot leverage LDAP to detect a domain connection in the same way that domain-joined endpoints do. Instead, use the NetworkListManager CSP to specify a TLS endpoint that when accessible will switch the endpoint to the domain firewall profile.

BitLocker Encryption

Use Endpoint Security in Microsoft Intune to configure encryption with BitLocker.

These settings can be enabled in the Microsoft Intune admin center. In the admin center, go to Endpoint Security > Manage > Disk encryption > Create Policy > Windows and later > Profile = BitLocker.

When you configure the following BitLocker settings, they silently enable 128-bit encryption for standard users, which is a common scenario. However, your organization might have different security requirements, so use the BitLocker documentation for more settings.

BitLocker – Base Settings:

  • Enable full disk encryption for OS and fixed data drives: Yes
  • Require storage cards to be encrypted (mobile only): Not configured
  • Hide prompt about third-party encryption: Yes
    • Allow standard users to enable encryption during Autopilot: Yes
  • Configure client-driven recovery password rotation: Enable rotation on Microsoft Entra-joined devices

BitLocker – Fixed Drive Settings:

  • BitLocker fixed drive policy: Configure
  • Fixed drive recovery: Configure
    • Recovery key file creation: Blocked
    • Configure BitLocker recovery package: Password and key
    • Require device to back up recovery information to Azure AD: Yes
    • Recovery password creation: Allowed
    • Hide recovery options during BitLocker setup: Not configured
    • Enable BitLocker after recovery information to store: Not configured
    • Block the use of certificate-based data recovery agent (DRA): Not configured
    • Block write access to fixed data-drives not protected by BitLocker: Not configured
    • Configure encryption method for fixed data-drives: Not configured

BitLocker – OS Drive Settings:

  • BitLocker system drive policy: Configure
    • Startup authentication required: Yes
    • Compatible TPM startup: Required
    • Compatible TPM startup PIN: Block
    • Compatible TPM startup key: Block
    • Compatible TPM startup key and PIN: Block
    • Disable BitLocker on devices where TPM is incompatible: Not configured
    • Enable preboot recovery message and url: Not configured
  • System drive recovery: Configure
    • Recovery key file creation: Blocked
    • Configure BitLocker recovery package: Password and key
    • Require device to back up recovery information to Azure AD: Yes
    • Recovery password creation: Allowed
    • Hide recovery options during BitLocker setup: Not configured
    • Enable BitLocker after recovery information to store: Not configured
    • Block the use of certificate-based data recovery agent (DRA): Not configured
    • Minimum PIN length: leave blank
    • Configure encryption method for Operating System drives: Not configured

BitLocker – Removable Drive Settings:

  • BitLocker removable drive policy: Configure
    • Configure encryption method for removable data-drives: Not configured
    • Block write access to removable data-drives not protected by BitLocker: Not configured
    • Block write access to devices configured in another organization: Not configured

Windows Local Administrator Password Solution (LAPS)

By default, the built-in local administrator account (well known SID S-1-5-500) is disabled. There are some scenarios where a local administrator account can be beneficial, such as troubleshooting, end-user support, and device recovery. If you decide to enable the built-in administrator account, or create a new local administrator account, it's important to secure the password for that account.

Windows Local Administrator Password Solution (LAPS) is one of the features you can use to randomize and securely store the password in Microsoft Entra. If you're using Intune as your MDM service, then use the following steps to enable Windows LAPS.

Important

Windows LAPS assumes that the default local administrator account is enabled, even if it's renamed or if you create another local admin account. Windows LAPS doesn't create or enable any local accounts for you.

You need to create or enable any local accounts separately from configuring Windows LAPS. You can script this task or use the Configuration Service Providers (CSP's), such as the Accounts CSP or Policy CSP.

  1. Make sure your Windows 10 (20H2 or later) or Windows 11 devices have the April 2023 (or later) security update installed.

    For more information, go to Microsoft Entra operating system updates.

  2. Enable Windows LAPS in Microsoft Entra:

    1. Sign in to Microsoft Entra.
    2. For the Enable Local Administrator Password Solution (LAPS) setting, select Yes > Save (top of the page).

    For more information, go to Enabling Windows LAPS with Microsoft Entra.

  3. In Intune, create an endpoint security policy:

    1. Sign in to the Microsoft Intune admin center.
    2. Select Endpoint Security > Account Protection > Create Policy > Windows 10 and later > Local admin password solution (Windows LAPS) > Create.

    For more information, go to Create a LAPS policy in Intune.

Security Baselines

You can use security baselines to apply a set of configurations that are known to increase the security of a Windows endpoint. For more information about security baselines, go to Windows MDM security baseline settings for Intune.

Baselines can be applied using the suggested settings and customized as per your requirements. Some settings within baselines might cause unexpected results or be incompatible with apps and services running on your Windows endpoints. As a result, baselines should be tested in isolation. Only apply the baseline to a selective group of test endpoints without any other configuration profiles or settings.

Security Baselines Known Issues

The following settings in the Windows security baseline can cause issues with Windows Autopilot or attempting to install apps as a standard user:

  • Local Policies Security Options\Administrator elevation prompt behavior (default = Prompt for consent on the secure desktop)
  • Standard user elevation prompt behavior (default = Automatically deny elevation requests)

For more information, see Troubleshooting policy conflicts with Windows Autopilot.

Windows Update for Business

Windows Update for Business is the cloud technology for controlling how and when updates are installed on devices. In Intune, Windows Update for Business can be configured using:

For more information, go to:

If you'd like more granular control for Windows Updates and you use Configuration Manager, consider co-management.

Phase 4 – Apply customizations and review your on-premises configuration

Phase 4.

In this phase, you apply organization-specific settings, apps, and review your on-premises configuration. The phase helps you build any customizations specific to your organization. Notice the various components of Windows, how you can review existing configurations from an on-premises AD Group Policy environment, and apply them to cloud-native endpoints. There are sections for each of the following areas:

Microsoft Edge

Microsoft Edge Deployment

Microsoft Edge is included on devices that run:

  • Windows 11
  • Windows 10 20H2 or later
  • Windows 10 1803 or later, with the May 2021 or later cumulative monthly security update

After users sign in, Microsoft Edge updates automatically. To trigger an update for Microsoft Edge during deployment, you can run the following command:

Start-Process -FilePath "C:\Program Files (x86)\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe" -argumentlist "/silent /install appguid={56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}&appname=Microsoft%20Edge&needsadmin=True"

To deploy Microsoft Edge to previous versions of Windows, go to Add Microsoft Edge for Windows to Microsoft Intune.

Microsoft Edge Configuration

Two components of the Microsoft Edge experience, which apply when users sign in with their Microsoft 365 credentials, can be configured from the Microsoft 365 Admin Center.

  • The start page logo in Microsoft Edge can be customized by configuring the Your organization section within the Microsoft 365 admin center. For more information, go to Customize the Microsoft 365 theme for your organization.

  • The default new tab page experience in Microsoft Edge includes Office 365 information and personalized news. How this page is displayed can be customized from the Microsoft 365 admin center at Settings > Org settings > News > Microsoft Edge new tab page.

You can also set other settings for Microsoft Edge using settings catalog profiles. For example, you might want to configure specific sync settings for your organization.

  • Microsoft Edge
    • Configure the list of types that are excluded from synchronization - passwords

Start and Taskbar layout

You can customize and set a standard start and taskbar layout using Intune.

Settings catalog

The settings catalog is a single location where all configurable Windows settings are listed. This feature simplifies how you create a policy, and how you see all the available settings. For more information, go to Create a policy using the settings catalog in Microsoft Intune.

Note

  • Some settings might not be available in the catalog but are available in Templates for Intune device configuration profiles.

  • Many of the settings you're familiar with from group policy are already available in the settings catalog. For more information, go to The latest in Group Policy settings parity in Mobile Device Management.

  • If you intend to leverage either ADMX templates or settings catalog (recommended), be sure to update your devices with the September 2021 'patch Tuesday' update (KB5005565) for Windows 10 versions 2004 and later. This monthly update includes KB5005101 which brings 1,400+ group policy settings to MDM. Failure to apply this update will result in a 'Not Applicable' message alongside the setting in the Intune admin center. While initially only appliable to the Enterprise and Edu versions of Windows, as of May 2022, these additional settings now also work on the Pro versions of Windows 10/11. If using the Pro versions of Windows 10/11, ensure that you install KB5013942 or later on Windows 10 and KB5013943 or later on Windows 11 as mentioned in The latest in Group Policy settings parity in Mobile Device Management.

Following are some settings available in the settings catalog that might be relevant to your organization:

  • Azure Active Directory preferred tenant domain This setting configures the preferred tenant domain name to be appended to a user's username. A preferred tenant domain allows users to sign in to Microsoft Entra endpoints with only their username rather than their whole UPN so long as the user's domain name matches the preferred tenant domain. For users that have different domain names, they can type their whole UPN.

    The setting can be found in:

    • Authentication
      • Preferred AAD Tenant Domain Name - Specify domain name, like contoso.onmicrosoft.com.

  • Windows Spotlight By default, several consumer features of Windows are enabled which results in selected Store apps installing and third-party suggestions on the lock screen. You can control this using the Experience section of the settings catalog.

    • Experience
      • Allow Windows Consumer Features - Block
      • Allow Third-Party Suggestions in Windows Spotlight (user) - Block

  • Microsoft Store Organizations typically want to restrict the applications that can install on endpoints. Use this setting if your organization wants to control which applications can install from the Microsoft Store. This setting prevents users from installing applications unless they're approved.

  • Block Gaming Organizations might prefer that corporate endpoints can't be used to play games. The Gaming page within the Settings app can be hidden entirely using the following setting. For additional information on the settings page visibility, go to the CSP documentation and the ms-settings URI scheme reference.

    • Settings
      • Page Visibility List – hide:gaming-gamebar;gaming-gamedvr;gaming-broadcasting;gaming-gamemode;gaming-trueplay;gaming-xboxnetworking;quietmomentsgame

  • Control Chat Icon Visibility in Taskbar The visibility of the Chat icon in the Windows 11 taskbar can be controlled using the Policy CSP.

    • Experience
      • Configure Chat Icon - Disabled

  • Control which tenants the Teams desktop client can sign in to

    When this policy is configured on a device, users can only sign in with accounts homed in a Microsoft Entra tenant that is included in the "Tenant Allow List" defined in this policy. The "Tenant Allow List" is a comma separated list of Microsoft Entra tenant IDs. By specifying this policy and defining a Microsoft Entra tenant, you also block sign in to Teams for personal use. For more information, go to How to restrict sign in on desktop devices.

    • Administrative Templates \ Microsoft Teams
      • Restrict sign in to Teams to accounts in specific tenants (User) - Enabled

Device Restrictions

Windows Device restrictions templates contain many of the settings required to secure and manage a Windows endpoint using Windows Configuration Service Providers (CSPs). More of these settings will be made available in the settings catalog over time. For more information, go to Device Restrictions.

To create a profile that uses the Device restrictions template, in the Microsoft Intune admin center, go to Devices > Manage devices > Configuration > Create > New policy > Select Windows 10 and later for platform > Templates Device restrictions for profile type.

  • Desktop background picture URL (Desktop only) Use this setting to set a wallpaper on Windows Enterprise or Windows Education SKUs. You host the file online or reference a file that has been copied locally. To configure this setting, on the Configuration settings tab in the Device restrictions profile, expand Personalization and configure Desktop background picture URL (Desktop only).

  • Require users to connect to a network during device setup This setting reduces the risk that a device can skip Windows Autopilot if the computer is reset. This setting requires devices to have a network connection during the out of box experience phase. To configure this setting, on the Configuration settings tab in the Device restrictions profile, expand General and configure Require users to connect to network during device setup.

    Note

    The setting becomes effective the next time the device is wiped or reset.

Delivery Optimization

Delivery Optimization is used to reduce bandwidth consumption by sharing the work of downloading supported packages among multiple endpoints. Delivery Optimization is a self-organizing distributed cache that enables clients to download those packages from alternate sources, like peers on the network. These peer sources supplement the traditional Internet-based servers. You can find out about all the settings available for Delivery Optimization and what types of downloads are supported at Delivery Optimization for Windows updates.

To apply Delivery Optimization settings, create an Intune Delivery Optimization profile or a settings catalog profile.

Some settings that are commonly used by organizations are:

  • Restrict peer selection – Subnet. This setting restricts peer caching to computers on the same subnet.
  • Group ID. Delivery Optimization clients can be configured to only share content with devices in the same group. Group IDs can be configured directly by sending a GUID through policy or using DHCP options in DHCP scopes.

Customers using Microsoft Configuration Manager can deploy connected cache servers that can be used to host Delivery Optimization content. For more information, go to Microsoft Connected Cache in Configuration Manager.

Local Administrators

If there's only one user group that needs local administrator access to all Microsoft Entra joined Windows devices, then you can add them to the Microsoft Entra Joined Device Local Administrator.

You might have a requirement for IT helpdesk or other support staff to have local admin rights on a select group of devices. With Windows 2004 or later, you can meet this requirement by using the following Configuration Service Providers (CSPs).

  • Ideally use Local Users and Groups CSP, which requires Windows 10 20H2 or later.
  • If you have Windows 10 20H1 (2004) use the Restricted Groups CSP (no update action, only replace).
  • Windows versions prior to Windows 10 20H1 (2004) can't use groups, only individual accounts.

For more information, go to How to manage the local administrators group on Microsoft Entra joined devices

Group Policy to MDM Setting Migration

There are several options for creating your device configuration when considering a migration from Group Policy to cloud-native device management:

  • Start fresh and apply custom settings as required.
  • Review existing Group Policies and apply required settings. You can use tools to help, like Group Policy analytics.
  • Use Group Policy analytics to create Device Configuration profiles directly for supported settings.

The transition to a cloud-native Windows endpoint represents an opportunity to review your end-user computing requirements and establish a new configuration for the future. Wherever possible, start fresh with a minimal set of policies. Avoid carrying forward unnecessary or legacy settings from a domain-joined environment or older operating systems, like Windows 7 or Windows XP.

To start fresh, review your current requirements and implement a minimal collection of settings to meet these requirements. Requirements might include regulatory or mandatory security settings and settings to enhance the end-user experience. The business creates a list of requirements, not IT. Every setting should be documented, understood, and should serve a purpose.

Migrating settings from existing Group Policies to MDM (Microsoft Intune) isn't the preferred approach. When you transition to cloud-native Windows, the intention shouldn't be to lift and shift existing group policy settings. Instead, consider the target audience and what settings they require. It's time consuming and likely impractical to review each group policy setting in your environment to determine its relevance and compatibility with a modern managed device. Avoid trying to assess every group policy and individual setting. Instead, focus on assessing those common policies that cover most devices and scenarios.

Instead, identify the group policy settings that are mandatory and review those settings against available MDM settings. Any gaps would represent blockers that can prevent you from moving forward with a cloud-native device if unresolved. Tools such as Group Policy analytics can be used to analyze group policy settings and determine if they can be migrated to MDM policies or not.

Scripts

You can use PowerShell scripts for any settings or customizations that you need to configure outside of the in-built configuration profiles. For more information, go to Add PowerShell scripts to Windows devices in Microsoft Intune.

Mapping Network Drives and Printers

Cloud-native scenarios have no built-in solution for mapped network drives. Instead, we recommend that users migrate to Teams, SharePoint, and OneDrive for Business. If migration isn't possible, consider the use of scripts if necessary.

For personal storage, in Step 8 - Configure settings for an optimal Microsoft 365 experience, we configured OneDrive Known Folder move. For more information, go to Redirect Known Folders.

For document storage, users can also benefit from SharePoint integration with File Explorer and the ability to sync libraries locally, as referenced here: Sync SharePoint and Teams files with your computer.

If you use corporate Office document templates, which are typically on internal servers, consider the newer cloud-based equivalent that allows users to access the templates from anywhere.

For printing solutions, consider Universal Print. For more information, go to:

Applications

Intune supports the deployment of many different Windows application types.

If you have applications that use MSI, EXE, or script installers, you can deploy all of these applications using Win32 app management in Microsoft Intune. Wrapping these installers in the Win32 format provides more flexibility and benefits, including notifications, delivery optimization, dependencies, detection rules, and support for the Enrollment Status Page in Windows Autopilot.

Note

To prevent conflicts during installation, we recommend that you stick to using the Windows line-of-business apps or Win32 apps features exclusively. If you have applications that are packaged as .msi or .exe, those can be converted to Win32 apps (.intunewin) by using the Microsoft Win32 Content Prep Tool, which is available from GitHub.

Phase 5 – Deploy at scale with Windows Autopilot

Phase 5.

Now that you've configured your cloud-native Windows endpoint and provisioned it with Windows Autopilot, consider how you can import more devices. Also consider how you can work with your partner or hardware supplier to start provisioning new endpoints from the cloud. Review the following resources to determine the best approach for your organization.

If for some reason Windows Autopilot isn't the right option for you, there are other enrollment methods for Windows. For more information, go to Intune enrollment methods for Windows devices.

Follow the cloud-native endpoints guidance

  1. Overview: What are cloud-native endpoints?
  2. 🡺 Tutorial: Get started with cloud-native Windows endpoints (You are here)
  3. Concept: Microsoft Entra joined vs. Hybrid Microsoft Entra joined
  4. Concept: Cloud-native endpoints and on-premises resources
  5. High level planning guide
  6. Known issues and important information

Helpful online resources