Guided scenario - Windows 10 in cloud configuration

Windows 10 in cloud configuration is a Microsoft-recommended device configuration. You can turn any Windows 10 Professional, Enterprise, and Education device into a cloud-optimized device.

It’s ideal for:

  • Frontline workers
  • Remote workers
  • Other users with focused workflow needs, like productivity and browsing

Cloud config makes these devices easy to use, and secures these devices with Microsoft-recommended security features.

With Windows 10 in cloud configuration:

  • You can configure new devices, or reuse existing hardware.
  • End users get an easy-to-use, and familiar Windows experience.
  • Administrators get a uniform device configuration across devices, which makes management and troubleshooting easier.
  • You can customize the names of your resources, so they're easy to see and monitor.

Tip

To learn more about Windows 10 in cloud configuration, see Windows 10 in cloud configuration.

What this guided scenario does

Using Microsoft Endpoint Manager, you can use a guided scenario to deploy a cloud configuration. The guided scenario automatically creates all the resources you need, including the following resources:

  • Creates a new Azure AD security group, or uses an existing Azure AD security group.

  • Deploys the Microsoft Edge and Microsoft Teams apps. For more information on deploying these apps individually, see:

  • Creates a Windows 10 security baseline policy with recommended security settings that are already configured.

    For more information about security baselines, and what they do, see Use security baselines to configure Windows 10 devices.

  • Creates a Windows Autopilot enrollment profile that automatically enrolls devices in Microsoft Intune.

    For more information on creating your own Autopilot profile, see Configure Autopilot profiles.

  • Turns on and configures the Autopilot enrollment status page (ESP). This page shows users the enrollment progress.

    For more information about the ESP, see Set up the Enrollment Status Page.

  • Creates an administrative template that configures OneDrive with the Known Folder Move settings. With these settings, user files and data are automatically saved in OneDrive.

    For information on this setting, see Redirect and move Windows known folders.

  • Creates an administrative template that configures some SmartScreen settings in the Microsoft Edge app. For more information on creating your own profile, see Configure Microsoft Edge policy settings.

  • Creates a compliance policy that monitors compliance and health. Users are allowed to use noncompliant devices, and access resources. If your organization blocks access to non-compliant devices, then create another compliance policy that blocks access, and assign it to the same group.

    For more information on the compliance settings you can configure on your own, see Windows 10 and later settings to mark devices as compliant or not compliant.

  • Deploys a Windows PowerShell script that removes built-in apps, and simplifies the Start menu.

    For more information about PowerShell scripts, see Use PowerShell scripts on Windows 10 devices.

  • Creates a Windows 10 update ring policy. This policy automatically updates the devices, including product updates, drivers, and Windows updates.

    For more information about update rings, and creating your policy, see Update rings for Windows 10 and later policy.

Tip

This guided scenario creates all these resources for you, automatically. If you want create your own individual resources, and not use the guided scenario, then you can. For the specific steps, see the cloud config overview and setup guide.

Prerequisites

Step 1 - Introduction

  1. Open the Microsoft Endpoint Manager admin center.
  2. Select Troubleshooting + support > Guided scenarios > Deploy Windows 10 in cloud configuration > Start.
  3. Select Next.

Step 2 - Basics

Choose how your devices are named when they enroll, and choose the prefix of all the resources created.

  • Autopilot device name template: This guided scenario enrolls your devices in Windows Autopilot. When they enroll, you can optionally name your devices using a unique pattern that applies to all devices. Your options:

    • Apply device name template: No doesn't create a template or pattern when naming your devices. The device will have the OEM name, such as DESKTOP-, followed by some random characters. Select Yes to create a unique pattern to name your devices. For example, enter Contoso-%RAND:7% to name all your devices Contoso- followed by seven random characters.

      The names:

      • Must be 15 characters or less.
      • Can include letters (a-z, A-Z), numbers (0-9), and hyphens.
      • Can't be only numbers, and can't include a blank space.
      • Can use the %SERIAL% macro to add a hardware-specific serial number.
      • Can use the %RAND:x% macro to add a random string of characters, where x equals the number of characters to add.
  • Resource name prefix: When you deploy this guided scenario, several resources are automatically created. To distinguish the items used in this deployment, add a prefix:

    • Enter a resource prefix name: Enter some text that will be at the beginning of the items created. For example, enter Windows cloud config. All resources created will be named something like Windows cloud config Autopilot profile, or Windows cloud config compliance policy.

    Your settings look similar to the following image:

    Configure the device name template and resource name prefix in a Windows 10 in cloud configuration guided scenario in Microsoft Intune and Endpoint Manager.

  • Select Next.

Step 3 - Apps

Select the apps you want to deploy to devices. Microsoft recommends deploying the smallest number of apps as possible. The idea is to keep your cloud config devices simple, and easy to manage.​

  • Cloud config defaults: This guided scenario automatically includes the Microsoft Edge and Microsoft Teams apps. They can't be removed when creating the guided scenario. You can delete or uninstall these apps after the guided scenario finishes.

    To remove the Microsoft Edge app, see Uninstall the app.

  • Select additional M365 apps (optional): From the list, add more Microsoft 365 apps that you want on the devices. Remember, keep the list small, and only include apps your users need. The idea is to keep the devices simple.

    Tip

    To add apps not listed, or add line-of-business apps, complete this guided scenario. In the Endpoint Manager admin center, go to Apps, and create a policy. Deploy the app policy to the same group that you deployed this cloud config guided scenario. For more information on adding apps, see Add apps to Microsoft Intune.

  • Select Next.

Step 4 - Assignments

Select the groups that will receive this guided scenario, and all the resources it creates.

  • Create new group: Creates a new group, and deploys the guided scenario policies to this group. As devices are added to this group, they'll start to receive this guided scenario.

    • Group name: Enter the group name. For example, enter Cloud configured devices.
  • Choose an existing group: Select an existing group. You guided scenario policies are deployed to this group.

  • Select Next.

Step 5 - Review + deploy

A summary of the settings and the values you configured are shown. You can go back to the other tabs, and change any values you added.

Look at the following properties:

  • Configurations to be made: Expand this option to see all the resources that will be created, including the policies.

  • Deploy: Select this option to save your changes, and deploy the guided scenario. The groups you added will receive the policies in this guided scenario.

    As the resources are being created in the Endpoint Manager admin center, the status is shown, similar to the following image:

    Review and the Windows 10 in cloud configuration guided scenario deployment status in Microsoft Intune and Endpoint Manager.

If there's an error, then the guided scenario isn't deployed, and all changes are reverted. The Cloud configuration overview and setup guide is also a good resource.

When it deploys successfully, you can use the monitoring and reporting features in the Endpoint Manager admin center:

What you need to know

  • You can complete the guided scenario before there are any devices in the group. When devices are added to the group, and have internet access, then they'll automatically start receiving the policies in this guided scenario.

    You can also:

    • Add preregistered Windows Autopilot devices to the group. Add them to the group before you enroll or apply any policies.
    • Add existing Windows 10 devices that are already enrolled. Microsoft recommends removing other apps and profiles targeted to these devices. After adding them to the group, reset the devices so they start fresh with just cloud config applied.

    For information on the policy refresh times, see Common questions and answers with device policies in Microsoft Intune.

  • Microsoft recommends only assigning cloud config settings and apps. After this guided scenario deploys, then you can add any other required resources, such as certificates, VPN profiles, line-of-business apps, and more. Be sure to deploy these policies to the same group as this guided scenario. Remember, keep the list small, and only include resources your users need.

  • Microsoft doesn't recommend using Windows 10 in cloud configuration with shared devices, because of a OneDrive sync issue with shared devices. Shared devices typically have multiple users that sign in and sign out.

  • After the guided scenario is deployed, you can go to a policy, and see the settings and their configured values. You can change any of these settings to another value, if you like.

  • To remove the guided scenario settings from devices, go to each policy created by the cloud config guided scenario. Configure the settings to Not Configured. Deploy each policy again to the same group as this guided scenario.

    The next time the device checks in, the setting is no longer locked. The setting can be changed by another policy, and possibly the end user. It's possible the setting might have the same value set by the guided scenario.

    Now, you can delete the individual items created by this guided scenario, including apps, policies, the Windows PowerShell script, and the group.

Next steps