3.2.3. Specialty Devices: Teams Rooms, HoloLens 2, and Zebra
💡 First Principle: Specialty devices run a fixed job with no regular user at the keyboard, so their management choices follow from that: they deploy userless, they sign in automatically, and settings built around a person — passwords, MFA, the user phase of setup — either don't apply or break them. When a question involves a meeting room, a headset or a warehouse scanner, start by removing every assumption that a user is present.
Intune counts "specialty device management" (AR/VR headsets, large smart screens and meeting-room devices) among its advanced capabilities, alongside firmware-over-the-air (FOTA) updates for Android. Microsoft's pricing FAQ lists both among the Plan 2 capabilities that Microsoft 365 E3 gained in mid-2026.
Microsoft Teams Rooms on Windows deploys with Autopilot self-deploying mode and Autologin. Its requirements are specific:
- Teams Rooms Pro licenses, which include Intune and Microsoft Entra ID P1. Teams Rooms Basic licenses don't include Intune, so those devices won't enroll.
- Entra joined (no hybrid join) and running Windows 11.
- The hardware hash's Group Tag must start with
MTR-, so the Teams Rooms Pro Management portal recognizes the devices. A dynamic group can collect them with(device.devicePhysicalIds -any _ -startswith "[OrderID]:MTR-"). - The Teams Rooms app update tool deployed as a Win32 app with a forced restart.
- An ESP with Block device use = Yes, Allow use on error = No, the update tool as the selected blocking app, and Only fail selected blocking apps in technician phase = Yes. The user phase isn't recommended, and the ESP Install Windows quality updates setting should be No because Teams Rooms signs in automatically.
Compliance and Conditional Access must fit a device with no person. Teams Rooms on Windows supports compliance settings such as BitLocker, Secure Boot, firewall, TPM and Defender, but not password policies or OS minimum and maximum versions. Conditional Access supports Require compliant device and Filter for devices, but not Require MFA, Require hybrid joined, Require app protection policy or Sign-in frequency. Microsoft recommends LAPS for these devices, and to redeploy one you run the Teams Rooms Recovery Tool before an Intune wipe.
Teams Android devices (Teams Rooms on Android, phones and panels) enroll with AOSP device management through a corporate-owned, user-associated profile with For Microsoft Teams devices enabled — one such profile per tenant.
HoloLens 2 supports Autopilot self-deploying mode only, and Microsoft Entra join only. You create its profile with Create profile > HoloLens, and Convert all targeted devices to Autopilot isn't supported. The TenantLockdown CSP (RequireNetworkInOOBE = true) makes the device wait during setup until it gets its Autopilot profile, and the setting persists through a reflash. Classic Autopilot is required for HoloLens; device preparation doesn't support it.
Zebra rugged Android devices are configured through OEMConfig. Zebra OEMConfig Powered by MX supports Android 11 and later; Legacy Zebra OEMConfig supports Android 11 and earlier. Unlike other manufacturers, Zebra devices can take multiple OEMConfig profiles when you use the legacy app. Zebra firmware is updated through the Zebra LifeGuard OTA integration:
- Licensing: Intune Plan 2 or an additional subscription, plus Zebra LifeGuard entitlements.
- Supported on Android Enterprise dedicated and fully managed devices, connected at Tenant administration > Connectors and tokens > Firmware over-the-air update.
- Deployments (Devices > Android > Manage updates > Android FOTA deployments) are fire-and-forget: they can't be edited, don't downgrade firmware and don't support assignment filters, and a device can be in only one deployment at a time.
- Group membership is captured when the deployment is created, so devices added to the group later aren't included.
⚠️ Exam Trap: "Require MFA" in a Conditional Access policy that covers Teams Rooms breaks the room, because no one is there to complete the prompt. The supported controls are Require compliant device and Filter for devices, and the compliance policy itself can't include password requirements.
Reflection Question: You add 40 new Zebra scanners to the group targeted by yesterday's LifeGuard firmware deployment. Why won't they update, and what should you do instead?