Teams Rooms on Windows devices can be enrolled in Microsoft Intune like other Windows PCs, and with Windows Autopilot plus Autologin they can be provisioned zero-touch: unbox, connect Ethernet, power on, and the room signs in to its resource account on its own. Autopilot and Autologin for Teams Rooms needs Teams Rooms Pro licenses (which include the needed Intune and Entra ID P1 rights), Windows 11, Microsoft Entra join, and the Teams Rooms Pro Management portal. Teams Rooms on Android devices are enrolled in Intune as Android devices with a different process.

Requirements for Autopilot and Autologin
| Requirement | Detail |
|---|---|
| License | Teams Rooms Pro, one per device |
| OS | Windows 11 |
| Join type | Microsoft Entra joined (hybrid join not supported for this flow) |
| Intune | Automatic Windows enrollment configured |
| Roles | Intune Administrator or Policy and Profile Manager; Teams Rooms Pro Manager in the Pro portal |
| Accounts | Resource accounts created for each room |
| Network | Wired internet at first boot |
How zero-touch provisioning works
- Register the device hardware hash in Intune as an Autopilot device. Your OEM or reseller can register it for you, or you can upload it.
-
Set a Group Tag starting with
MTR-. This is how the Pro Management portal recognizes Teams Rooms devices. -
Create a dynamic device group that matches the
MTR-tag. - Deploy Microsoft's Teams Rooms update tool as a required Win32 app to that group, so the device runs a Teams Rooms app version that supports Autologin.
- Create an Enrollment Status Page profile that blocks use until the tool installs.
- Create a self-deploying Autopilot profile and assign it to the group.
- Add a Windows LAPS policy to manage the local admin password (recommended).
- In the Pro Management portal, go to Planning > Autopilot devices, sync, and assign a resource account to each device.
- Power on the device on a wired network. It runs Autopilot, installs the app and signs in.
Microsoft's article "Autopilot and Autologin for Teams Rooms on Windows" on learn.microsoft.com has the exact settings.
Intune policies for Teams Rooms
Teams Rooms are shared, unattended devices. Treat them as their own group:
- Exclude Teams Rooms from user-PC policies. Desktop baselines, BitLocker prompts, Windows Hello, reboot schedules and app deployments meant for laptops often break rooms.
- Don't block the Skype local user account. The Teams Rooms app runs under it.
- Let the Teams Rooms app handle updates. Avoid Windows Update policies that force reboots during the day.
- Compliance policies: keep them simple (OS version, BitLocker, firewall). Overly strict compliance can block sign-in.
Conditional access and MFA
Resource accounts can't do interactive MFA. Common approaches:
- Require a compliant device for the resource accounts instead of MFA.
- Use named/trusted locations so room accounts sign in only from your offices.
- Exclude room accounts from per-user MFA and from policies that require app protection.
Microsoft documents supported conditional access settings for Teams Rooms. If rooms fail to sign in after a policy change, see Teams Rooms sign-in problems.
Resets and redeployment
- A reset from inside the Teams Rooms app doesn't reset Windows.
- Before an Intune Wipe, run the Teams Rooms Recovery Tool; afterward the device redeploys through Autopilot and Autologin.
- If a resource account assignment shows "Consumed," reassign it before resetting the device.
- Delete returned or swapped devices from Autopilot so they aren't tied to your tenant.
See how to reset or recover a Teams Rooms device.
Teams Rooms on Android and Intune
Android-based bars and panels can be enrolled in Intune as Android Open Source Project (AOSP) devices, so conditional access requiring a compliant device can apply to them. Not every Android device model supports it; check Microsoft's supported device list. See Teams Rooms on Android.
Devices that fit this model
Windows Teams Rooms compute such as the Poly Studio 5 Room Compute and Poly Studio 7 Room Compute, paired with a console like the Logitech Tap, are standard Windows 11 devices you can bring into Autopilot. Ask the OEM or reseller to register hardware hashes at order time. More on licensing: Teams Rooms Pro license.
Deploying a batch of Windows rooms? Send us the room count and we'll quote hardware ready for Autopilot.
Related guides
- Teams Rooms for GCC High and government tenants
- Teams Rooms on Windows: Compute, Consoles and Setup
- Teams Rooms XML Config (SkypeSettings.xml) Guide
- How to Reset or Recover a Microsoft Teams Rooms Device
- How to Set Up Microsoft Teams Rooms: Step by Step
- Microsoft Teams Rooms requirements: hardware and accounts
Outfitting several rooms, or reselling? Get a volume quote or apply for wholesale pricing →





