Connect with us

TECHNOLOGY

How to Enroll Windows IoT Devices in Microsoft Intune: Pick the Edition

Enroll Windows IoT Devices in Microsoft Intune with a package for IoT Enterprise, an SD card for IoT Core, and Autopilot only for Teams Rooms.

Published

on

The box on your bench is a menu board, a kiosk, or a panel PC, and you want it in the same Microsoft Intune tenant as the laptops. To enroll Windows IoT devices in Microsoft Intune, match the steps to the edition, because a laptop playbook sends this hardware down the wrong path.

Windows IoT Enterprise, the full Windows image for a fixed-purpose device, joins with a provisioning package you build in Windows Configuration Designer. Autopilot’s requirement list includes that edition only for a Microsoft Teams Rooms device. Windows IoT Core, the smaller single-app image, still follows an SD card method from the previous-versions documentation. The sections below cover the tenant checks, both builds, and the misses that leave a device off the list.

Which Windows Edition Is on the IoT Device?

Three Windows names show up on IoT hardware, and the client steps on this page cover IoT Enterprise and IoT Core. IoT Enterprise is the common image for a locked screen or a machine on a line. Intune’s supported platform list includes Windows 11 IoT Enterprise, and it includes IoT Enterprise on Windows 10 LTSC 2019, Windows 10 LTSC 2021, and Windows 11 LTSC 2024.

Edition How you enroll it Support mark
Windows IoT Enterprise Provisioning package from Windows Configuration Designer, from a USB drive at first setup or from Settings after setup Listed for Intune on Windows 11 IoT Enterprise and on IoT Enterprise LTSC editions noted above
Windows 10 IoT Core Windows IoT Core Dashboard image on a microSD card, with the package copied into the provisioning folder before first boot Non-LTSC product retired on November 10, 2020
Windows 10 IoT Core LTSC Same card and folder path, and it requires a Windows 10 IoT Core Services subscription Mainstream support ended January 10, 2024; extended support runs through January 10, 2029
Windows Server IoT A Windows Server edition, not the desktop wizard and not the IoT Core card folder Licensing and distribution are the differences called out for this edition

On a device that already reaches the desktop, read the edition under Settings, System, About. On a board you are about to flash, the edition is the image you picked in the dashboard or the license you bought. Each configuration service provider lists the editions it covers, so a setting that applies on Windows Enterprise can be absent on another edition.

A Teams Rooms console is the IoT Enterprise case named for Autopilot, and that console can stay on that path. A menu board or a factory panel is a package job. If the sticker says IoT Core, use the card steps even when the board looks like a tiny PC. For a row of identical panels, set the device name in the package to something like SHOP-%SERIAL% so each serial shows up in the Intune device list instead of ten objects with one generic name.

What Must Be Ready in the Tenant First?

The package can join the device only when Windows automatic enrollment is already on and the account you use is allowed to create a bulk token. The older IoT Core write-up still points at Azure Active Directory, then Mobility (MDM and MAM), then Microsoft Intune, with MDM user scope set to All. The part you still need from that setting is the same: the account that requests the token has to sit inside the MDM user scope. Scope set to Some works when that account’s group is the group you selected.

THE ACCOUNT THAT REQUESTS THE TOKEN

  • The role: Use Cloud Device Administrator, Intune Administrator, or Password Administrator, and keep that account free of an administrative unit scope.
  • The scope: Leave the account inside the MDM user scope tied to Windows automatic enrollment, because taking it out of that group stops bulk enrollment.
  • The sign-in: Use a password or certificate-based authentication, since other methods are rejected for this request, and a federated account in a staged rollout cannot retrieve the token.
  • The service: Microsoft.Azure.SyncFabric has to exist in the tenant, or Windows Configuration Designer cannot fetch a bulk token.

Check for that service principal with Get-MgServicePrincipal and a filter on AppId 00000014-0000-0000-c000-000000000000. An empty result means you still need New-MgServicePrincipal with that same AppId. Then open the Default enrollment restriction and confirm the Windows platform is allowed. This method is userless, so only that Default restriction is evaluated, and a Windows block there fails the join even when the file itself is valid.

Enroll Windows IoT Devices in Microsoft Intune With a Provisioning Package

Use this path for Windows IoT Enterprise, including IoT Enterprise LTSC. You build one provisioning package on an admin PC, then apply that file to each device. The wizard, the token rules, and the restart behavior are in the bulk enrollment guide for Windows devices. Install the builder from Windows Configuration Designer in the Microsoft Store before you open a project.

  1. Open Windows Configuration Designer and choose Provision desktop devices.
  2. Name the project, pick a folder, add a description if you want one, and finish the dialog.
  3. On Set up device, set the device name. The page accepts %SERIAL% when you want the hardware serial in the name, and %RAND:x% for a random set of characters. A product key, shared-use setup, and removal of preinstalled software are optional.
  4. On Set up network, add a Wi-Fi profile or leave it empty. With no Wi-Fi profile, the device needs a cable the first time it starts.
  5. On Account management, choose Enroll in Azure AD. That label is the one still printed on the button, and the join it performs is to Microsoft Entra ID. Enter a Bulk Token Expiry date inside the 180 days the token stays valid, then select Get Bulk Token.
  6. Sign in with the account you checked above. When the bulk token shows as fetched, continue. Add applications or certificates only when this fleet needs them inside the file. You can put a password on the package. Then choose Create.

KEEP THE ADMIN PC OUT OF THE TENANT

  • The prompt: On the page that asks you to stay signed in to all your apps, choose “No, sign in to this app only.”
  • The miss: Leaving the other choice selected enrolls the PC you are using to build the package.

When the.ppkg file is in the project folder, copy it to the root of a USB drive, not into a subfolder. A package buried in a folder is invisible to first-time setup. One file can join many devices until you revoke it or the token date passes.

Apply the Package on the First Setup Screen

  1. Start at the first setup screen. If someone already clicked past it, reset the device from Settings, System, Recovery, Reset this PC, and begin again.
  2. Insert the USB drive. If the screen does not react, press the Windows key five times. You can also press Esc if a long provisioning run needs to stop.
  3. A drive that holds a single package applies it. A drive that holds several asks you to choose Install provisioning package, then the file, then Yes.
  4. Wait until you see “You can remove your removable media now!” and pull the USB drive. Windows keeps going. The device restarts in one minute, then connects to Microsoft Entra ID and enrolls in Intune.

Apply the Package on a Device Already in Use

A device that is past first setup can take the same file without the five key presses. Applying a package after setup requires a local administrator on that device. Open Settings, Accounts, Access work or school, then Add or remove a provisioning package, and pick the file. Double-clicking the.ppkg from a local folder or a network share is the other documented route, and Windows asks you to trust the source before it runs.

After either route, look in the Intune device list for the name you set in the wizard. Microsoft Entra users who sign in on these devices are standard users, and they receive the policies and required apps you assign. They do not become local administrators unless you created a local admin account while you built the package.

How to Enroll a Windows IoT Core Device

Follow this section only when the device really is Windows IoT Core. The non-LTSC Windows 10 IoT Core product retired on November 10, 2020. IoT Core LTSC is the line that still has a support date in the table above, and it requires Windows 10 IoT Core Services. The enrollment steps published for this edition start with the Windows IoT Core Dashboard, not with a USB stick at a normal Windows setup screen.

  1. Put a microSD card in the reader on your PC. The dashboard formats that card, and anything stored on it is deleted.
  2. Install the Windows IoT Core Dashboard, open it, and choose Set up a new device. Enter a device name and a new administrator password. Select the Wi-Fi box only when the board will not use Ethernet. Accept the license terms, then choose Download and install.
  3. When the format confirmation appears, choose to format the card. That dialog can sit behind another window. If the card is not formatted, the board will not boot. Wait until the page says the SD card is ready, then leave the dashboard open until the package is copied.
  4. In Windows Configuration Designer, choose Provision desktop devices, then Enroll in Azure AD, set a bulk token expiry date, and select Get Bulk Token. Sign in and allow the app to read directory information. After the token succeeds, switch to the advanced editor and confirm the switch. Keep the account settings and remove the other settings. Select OOBE and remove it. If SharedPC is listed, remove that too.
  5. Export a provisioning package, accept the defaults on the following pages, pick a folder if you do not want the suggested path, and build. Open the output location and copy the.ppkg file.
  6. On the card, open the MainOS drive and copy the file to c:\windows\provisioning\packages. You may have to grant yourself permission before that folder will take the file.
  7. Seat the card in the IoT Core device, power it on, and wait until the standard screen is up. Then refresh the Intune device list. Enrollment could take 15 minutes or more.

Removing OOBE and SharedPC is part of the IoT Core instructions. Leave those pages in place on an IoT Enterprise package built with the current desktop wizard, which never tells you to strip them. The card folder is also a different spot from the USB root used at IoT Enterprise first setup. Copying a file to the wrong one is why a good package still produces an empty device list.

Where Does Autopilot Fit a Windows IoT Device?

Windows Autopilot is the path most laptop fleets use, and it is the path people try first on a panel that runs IoT Enterprise. The limit is written in the Windows Autopilot software requirements, which include Windows 11 IoT Enterprise only when the device is used in Microsoft Teams Rooms, and Windows 10 IoT Enterprise on the same terms. A kiosk or a line panel sits outside that line.

For a Teams Rooms device, Autopilot still needs automatic enrollment in the tenant, and the device has to be registered for Autopilot before first setup. For every other IoT Enterprise box, the provisioning package is the bulk join to Microsoft Entra ID and Intune. Treat a failed Autopilot profile on a menu board as a cue to build the package, not as a cue to collect hardware hashes again.

Enrollment is the join, and the lockdown comes later. Once the device is visible, Intune can assign a kiosk profile for one app or for several. Assigned Access, the Windows feature behind that lock, lists IoT Enterprise and IoT Enterprise LTSC among the editions that support it. Assign the profile to the device group after the object exists. A profile aimed at a group the device has not joined yet changes nothing on the bench.

Why Does an IoT Device Never Show in Intune?

Match the wait to the edition before you build a second file. An IoT Core board needs the wait in the card steps above. An IoT Enterprise device needs time to finish the restart that follows the package, then another refresh of the device list. If the object is still missing, the cause is almost always in the file’s location, the network, or the tenant check you ran at the start.

CHECKS WHEN THE DEVICE IS MISSING

  • Wrong media spot: IoT Enterprise first setup reads the package from the root of the USB drive. IoT Core reads it from MainOS at c:\windows\provisioning\packages.
  • Network left blank: With no Wi-Fi profile in the wizard, the first start needs a cable, or the join never reaches Microsoft Entra ID.
  • Windows blocked: Only the Default enrollment restriction is evaluated for this userless method, so a Windows block there stops enrollment.
  • Token account drifted: The account still needs its role, no administrative unit scope, and a place inside the MDM user scope. A federated account in a staged rollout will not retrieve a token.
  • Format dialog missed: On IoT Core, a format prompt hidden behind another window leaves the card unformatted, and the board does not boot.
  • Admin PC joined: During Get Bulk Token, agreeing to stay signed in to every app enrolls the computer you are working on.

If Get Bulk Token fails before a file exists, check the service principal and the sign-in method before you touch the device. A password or a certificate is what the app can use for that request. When the file exists and the device lands on a normal desktop with no Intune object, look at the media spot and the Default restriction first.

Frequently Asked Questions

Can You Revoke a Provisioning Package Before the Token Expires?

You revoke a provisioning package before its expiry by removing the associated package_{GUID} user account from Microsoft Entra ID. That account is what the bulk token uses, and deleting it is the revocation step in the bulk enrollment documentation. When you still have devices to join, build a new package and fetch a new token.

Does Conditional Access Apply After Bulk Enrollment?

Conditional Access is available for a device enrolled with bulk enrollment when that device runs Windows 11 or Windows 10, version 1803 and later. The token request is a separate step, and MFA is not supported there, so a policy that requires MFA needs an exclusion or MFA turned off for the request. Sign in with a password or with certificate-based authentication when you fetch the token.

Can Windows 10 IoT Enterprise Still Enroll in Intune?

A Windows 10 IoT Enterprise device can still enroll after the end of support for Windows 10. That end of support date is October 14, 2025, and the version remains allowed in Intune. The device can use eligible features, but functionality will not be guaranteed and can vary.

Where Do Apps Come From After an IoT Device Enrolls?

Required apps and the policies you assign come from Intune once the device has joined, and the Microsoft Entra users on that device are standard users. Optional apps are installed from the Company Portal app, which Windows devices enrolled through bulk enrollment can use. A local administrator is present only if you created one in the package.

Is Windows Server IoT Enrolled the Same Way?

Windows Server IoT is a Windows Server edition for IoT systems, and licensing and distribution are the differences called out for it. The USB provisioning package and the IoT Core card folder on this page are written for the client editions. Point a server box at the management path you use for Windows Server rather than at the desktop wizard.

Put SHOP-%SERIAL%, or your own prefix plus that token, in the package name so each panel is obvious in the device list. Copy the file to the USB root for IoT Enterprise and to c:\windows\provisioning\packages on MainOS for IoT Core, then confirm the object before you duplicate the stick or the card for the next unit on the bench.

Harry is the editor and publisher of MIND CRON, an independent title built on ten years of journalism that took him from the reporter's notebook to the editor's chair. Breaking news is where his rules are strictest. A story goes out when the primary document is in hand or two independent sources confirm the same fact, and not before, however loud the rumour. Anything still moving is labelled as developing, each update carries the time it was made, and the original wording stays visible so readers can see what changed. That discipline applies whether the story is a market shock in business, an outage in technology, a result in sports, a launch in gaming or a recall in auto, and it is no looser for science, entertainment, lifestyle, travel or the wider news pages. Numbers are checked against the source before publication. Errors are corrected openly under a public corrections policy. Tips from readers are checked the same way as everything else, and Harry reads and answers that mail himself at support@mindcron.com.

Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Trending