Frontline worker for Windows devices in Microsoft Intune
Windows has different devices and cloud services that can be used for frontline workers (FLW). These devices are used globally and in many industries & scenarios, including digital signage, check-in tasks, presentations, kiosks, and more.
You can use physical Windows devices or use Windows 365 Cloud PCs.
Using Intune, you can manage Windows devices used by frontline workers in your organization. This article:
- Helps you determine the best enrollment option and the best device management experience for you and your end users.
- Includes decisions admins need to make, including determining how the device is used, and configuring the device experience.
This article applies to:
- Windows devices owned by the organization and enrolled in Intune
For an overview on FLW devices in Intune, go to FLW device management in Intune.
Use this article to get started with Windows FLW devices in Intune. Specifically:
- Windows 365 Cloud PCs
- Step 1 - Select your enrollment option
- Step 2 - Shared device or user associated device
- Step 3 - Device experience and kiosk
Windows 365 Cloud PCs
Windows 365 Cloud PCs are virtual machines that are hosted in the Windows 365 service. They're accessible from anywhere and from any device. They include a Windows desktop experience and are associated with a user. Basically, end users have their own PC in the cloud.
✅ Windows 365 Cloud PCs are ideal for frontline workers that need a Windows desktop experience, but don't need a physical device. For example, a call center worker that needs access to a Windows desktop app.
These devices enroll in Intune, and are managed like any other device, including apps, configuration settings, and updates.
For information on Windows 365 Cloud PCs, and to learn more, go to:
- Windows 365 Cloud PCs overview - Enterprise
- Windows 365 Cloud PCs overview - Small & medium business
Step 1 - Select your enrollment option
✅ Determine the enrollment option that's best for your organization.
Determining the enrollment option is the first step. Enrollment determines how the devices are added to Intune for you to manage. The option you choose depends on your business needs and the devices you have.
For FLW devices using Windows, you can use Windows Autopilot enrollment or use a provisioning package. This section focuses on these enrollment options.
Windows Autopilot is the recommended option for FLW devices. You can ship the devices directly to the location without ever touching the devices. With self-deploying mode, users turn on the device, and the enrollment automatically starts.
✅ If you have Microsoft Entra Premium and you're getting new devices from an OEM, then use Windows Autopilot. You can use the Windows OEM version preinstalled on the devices to automatically enroll the devices. End users only need to turn on the device; no other end user interaction is required.
You can use Windows Autopilot on existing devices. When the existing devices are reset, the Windows Autopilot enrollment can automatically start.
❌ Windows Autopilot requires Microsoft Entra Premium. If you don't have Entra Premium, then use a provisioning package. There are other Windows enrollment options available, but they're not commonly used for FLW devices.
For information on Windows Autopilot, go to Windows Autopilot overview and Windows Autopilot self-deploying mode.
Note
There are other Windows enrollment options available. This article focuses on the enrollment options commonly used for FLW devices. For information on all the Windows enrollment options, go to Enrollment guide: Enroll Windows client devices in Microsoft Intune.
Step 2 - Shared device or user associated device
✅ Determine if the devices are shared with many users or assigned to a single user.
In this step, this decision depends on your business needs and the end user requirements. It also impacts how these devices are managed with Intune.
These features are configured using Intune device configuration profiles. When the profile has the settings you want, you assign the profile to the devices. The profile can be deployed during Intune enrollment.
Step 3 - Device experience and kiosk
✅ Configure the device experience.
This step is optional and depends on your business scenario. If many users share these devices, then we recommended you configure the device experience using the features described in this section.
On Windows devices, you can configure the home screen and device experience. In this step, consider what frontline workers are doing on the devices and the device experience they need for their jobs. This decision impacts how you configure the device.
Some examples of kiosks include self-service terminals in airports, retail stores, government offices, and other public spaces. These devices allow users to do specific tasks, like check-in for flights, access information, or complete transactions.
These features are configured using device configuration profiles. When the profile has the settings you want, you assign the profile to the devices. The profile can be deployed during Intune enrollment.
The following scenarios are common.
Scenario 1 - Kiosk with one app or many apps
For this scenario, you configure the device as a kiosk, which allows you to customize the device experience.
For example, you can use the device in a lobby so customers can see your product catalog. Or, use the device to show visual content as a digital sign. For information, go to Configure kiosks and digital signs on Windows desktop editions (opens another Microsoft web site).
You can pin one app or many apps, select a wallpaper, set icon positions, and more. This scenario is often used for dedicated devices, such as shared devices. You can create a Shared PC profile and configure it be a kiosk using the kiosk settings in Intune.
What you need to know:
- Only features added to the kiosk are available to end users. So, you can restrict end users from accessing settings and other device features.
- When you pin one app or pin many apps to the kiosk, only those apps open. They're the only apps users can access. Users are locked to those apps, can't close the apps, or do anything else on the devices. This scenario is used on devices dedicated to a specific use, like airport terminals.
To get started, use the following links:
Add apps to Microsoft Intune. When the apps are added, you create app policies that deploy the apps to the devices.
Create a device configuration kiosk profile and configure the Windows kiosk profile - settings list.
The following example shows the kiosk profile settings for a single app. Make sure you add the app to Intune before you configure the kiosk profile.
The following example shows the kiosk profile settings for multiple apps. Make sure you add the apps to Intune before you configure the kiosk profile.
Scenario 2 - Device wide access with many apps
This scenario is a good scenario for Windows 365 Cloud PCs. Users have access to the apps and settings on the device. You can restrict users from different features, such as simple passwords, features in the Settings app, and more.
This scenario also applies to physical devices. It expands the boundary of traditional frontline worker scenarios by also including knowledge workers.
To configure devices for this scenario, you deploy the apps to the devices. Then, use device configuration policies to allow or block device features.
To get started, use the following links:
Add apps to Microsoft Intune. When the apps are added, you create app policies that deploy the apps to the devices.
Create a device configuration restrictions profile that allows or restricts features using Intune. There are hundreds of settings available for you to configure, including more in the Settings Catalog.
