Skip to main content

108: Specialty, AR/VR & Spatial Computing Devices (Android XR, visionOS & tvOS)

Implementation Effort: Medium – Requires Apple Business Manager (ABM) for userless visionOS/tvOS Automated Device Enrollment or Managed Google Play for Android XR corporate enrollment.

User Impact: Low – Streamlines zero-touch out-of-box setup and applies core compliance and security policies.

Overview​

Microsoft Intune supports enterprise enrollment, configuration, app deployment, and compliance enforcement for spatial computing, AR/VR headsets, and shared display appliances—included with Microsoft 365 E3 / E5 and Microsoft Intune Plan 2 (Specialty Device Management).

Key 2026 platform additions include:

  • Android XR Device Management (April 2026): Intune supports Android XR headsets and spatial devices using Android Enterprise Dedicated (COSU) and Fully Managed (COBO) enrollment modes. Admins can enroll Android XR devices, deploy apps via Managed Google Play, and enforce core security and compliance policies alongside standard Android devices.
  • Userless Apple Automated Device Enrollment (ADE) for visionOS and tvOS (April & July 2026 / 2604 & 2607):
    • Supports ADE without user affinity for Apple Vision Pro (visionOS 26+) and Apple TV (tvOS 26+) through Apple Business Manager or Apple School Manager.
    • Includes Setup Assistant screen skip controls (such as Apple ID, Diagnostics Data, and Location Services) during ADE enrollment (2607).
    • Supports Settings Catalog policies, custom configuration profiles, default enrollment restrictions, and remote device actions under the Apple mobile filter in the Intune admin center.

Implementation Guidance​

  1. Validate support by platform first. A mixed fleet might include HoloLens, Android-based immersive devices, or vendor-specific headsets. Do not build policy assumptions from one platform and apply them to another without checking Microsoft support documentation.
  2. Define the user model: single user, shared user, kiosk, or technician device. This determines whether you need standard user enrollment, shared account handling, device-only usage, or line-of-business launcher experiences.
  3. Lock down hardware capabilities to what the workflow requires. Review camera, microphone, Bluetooth, USB, browser access, local file storage, and sideloading behavior against the business need and privacy rules.
  4. Package only approved apps and test update behavior carefully. AR/VR workflows are often sensitive to app latency, peripheral compatibility, and OS version changes.
  5. Plan Wi-Fi, certificates, VPN or private access, and Conditional Access for the specific places these devices operate. Field and warehouse scenarios often fail because the network design was treated as an afterthought.
  6. Monitor device health and have an operational replacement process. Specialized headsets usually need spare inventory and faster incident handling than knowledge-worker laptops.

Reference​