Compatibility Inquiry Regarding Surface Pro 12 (Snapdragon ARM64) for Enterprise Deployment

Shusoma Haque Shamma 0 Reputation points
2026-06-14T05:24:59.61+00:00

Dear Microsoft Support Team,

We are currently evaluating the Surface Pro 12 (Snapdragon ARM64 platform) for deployment within our organization and would appreciate your guidance regarding enterprise compatibility.

Our environment includes the following technologies:

• Microsoft 365 Business Standard and Business Basic

• Exchange Online and Exchange Online Protection (EOP)

• Active Directory Domain Services (on-premises)

• Group Policy management

• Trend Micro Endpoint Security

• Trend Micro Vision One / XDR

• ManageEngine ServiceDesk Plus

• Managed network printing solution

• Windows domain-joined laptops and desktops

Before proceeding with procurement, we would like clarification on the following points:

  1. Are there any known limitations of Surface Pro 12 ARM64 devices in Active Directory domain environments?
  2. Are there any known issues related to Group Policy processing, domain authentication, SMB file sharing, or enterprise management?
  3. Are there any documented compatibility concerns with printer drivers or enterprise print management solutions on Surface Pro 12 ARM64 devices?
  4. Does Microsoft maintain a list of known software categories that may experience compatibility limitations on Snapdragon ARM64 platforms?
  5. Are there any enterprise deployment considerations, best practices, or recommendations specific to Surface Pro 12 ARM64 devices?

We would appreciate any official documentation, compatibility matrices, or deployment guidance that can help us assess the suitability of this device for enterprise use.

Thank you for your assistance.

Best regards,
Shusoma Haque Shamma
TEAM Group

Surface | Surface Laptop | Install and update

4 answers

Sort by: Newest
Most helpful Newest Oldest
  1. S.Sengupta 32,031 Reputation points MVP Volunteer Moderator
    2026-09-11T11:26:35.7433333+00:00

    Question 1: Are there any known limitations of Surface Pro 12 ARM64 devices in Active Directory domain environments?

    No AD-specific limitations are documented. Arm-based Surface Pro devices can be joined to on-premises Active Directory via Microsoft Entra hybrid join (typically after Autopilot deployment), and then managed with standard enterprise tools. The one caveat: if you co-manage with Configuration Manager, it installs the 32-bit x86 ConfigMgr client (running under emulation), not a native ARM64 client.

    Question 2: Are there any known issues related to Group Policy processing, domain authentication, SMB file sharing, or enterprise management?

    No documented issues. These are core Windows OS functions and behave the same on ARM64 as on x64 — Microsoft's own deployment guidance for Arm-based Surface devices doesn't flag any of these as problem areas. Two unrelated notes worth knowing: MDT isn't supported on Windows 11 at all (any architecture), and WinPE technically works but isn't recommended, since Microsoft doesn't supply the ISO/drivers needed to support it on Arm-based Surface devices.

    Question 3: Are there any documented compatibility concerns with printer drivers or enterprise print management solutions on Surface Pro 12 ARM64 devices?

    Yes — this is the one area with genuine, documented friction:

    Kernel-mode and user-mode printer drivers must be native ARM64 binaries; emulation cannot substitute for a missing native driver.

    Microsoft has publicly acknowledged that vendor-supplied printer installers can fail on Arm devices, and recommends adding printers directly via Windows Settings instead.

    Print servers don't push ARM64 drivers to clients as smoothly as x64 drivers — your options are built-in Type-4 class drivers, OEM-supplied ARM64 drivers (coverage varies by brand/model), or a third-party universal driver with ARM64 support.

    If staff use Remote Desktop into an x64 print/terminal server, RDP printer redirection can break at the architecture boundary, since Windows won't hand an x64 print driver to an ARM64 spooler or vice versa.

    Recommended mitigation: move to driverless IPP/Mopria/Universal Print queues (Microsoft's built-in IPP Class Driver) instead of vendor driver packages.

    Question 4: Does Microsoft maintain a list of known software categories that may experience compatibility limitations on Snapdragon ARM64 platforms?

    Yes. Microsoft's Arm compatibility documentation identifies these risk categories:

    Kernel-mode software — VPN clients, antivirus/EDR agents, anti-cheat drivers — these require full Arm64 rewrites; emulation doesn't cover kernel-mode components, so failures are hard failures, not slowdowns.

    Hardware-dependent apps — printers, scanners, audio interfaces, smart-card readers, USB security keys — anything needing a driver that must itself be ARM64-native.

    Shell-modifying / customization apps — IMEs, some cloud-sync clients, deep OS-integration tools.

    Certain games (not relevant to your deployment, but part of Microsoft's official list).

    Microsoft also runs the App Assure program, free for commercial customers, to help resolve LOB/ISV app compatibility issues on Windows on Arm.

    Question 5: Are there any enterprise deployment considerations, best practices, or recommendations specific to Surface Pro 12 ARM64 devices?

    Use Windows Autopilot as the primary deployment method — it's Microsoft's recommended path and supports zero-touch setup with preinstalled Microsoft 365 Apps for enterprise.

    Intune is recommended but not required; Configuration Manager also supports full image-based OS Deployment (OSD) for Windows 11 on current-generation Snapdragon Surface devices.

    Use SEMM (with the Surface IT Toolkit) or Intune + DFCI profiles for firmware-level management.

    Keep automatic driver/firmware updates enabled via Windows Update — this is the designed update path for Arm-based Surface devices, not traditional imaging-based driver delivery.

    Run a pilot of 2–3 units before full procurement, specifically testing: Trend Micro Vision One agent feature parity on ARM64 (supported since Sept 2024, but not all features are available), the ManageEngine Endpoint Central agent (ARM64 support confirmed), and real-world printing against your managed print solution — the one area most likely to surface problems.

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. kenneth southwick 0 Reputation points
    2026-09-08T03:55:43.03+00:00

    Arm processor to put it simply works with nothing. Very few apps and software works with arms

    Was this answer helpful?

    0 comments

  4. AI answer

    2026-06-14T05:25:24.55+00:00
    1. Active Directory domain environment limitations

    Arm-based Surface devices (including Snapdragon-based Surface Pro models) run Windows 11 and participate in enterprise environments similarly to x64 devices. The context does not document any AD domain join–specific limitations for Arm-based Surface devices. Devices can be joined to Active Directory or Microsoft Entra ID, including hybrid join, and then managed with standard enterprise tools.

    1. Group Policy, domain authentication, SMB, and management

    The provided guidance for Arm-based Surface devices focuses on app/driver compatibility rather than core Windows features. There are no documented issues in the context with:

    • Domain authentication
    • Group Policy processing
    • SMB file sharing

    Enterprise management is supported via:

    • Microsoft Intune with Device Firmware Configuration Interface (DFCI) for firmware-level control on Arm-based Surface devices
    • Management via Microsoft Entra ID and Intune, or co-management with Configuration Manager (using the 32-bit x86 ConfigMgr client)

    See “Deploy, manage, and service Arm-based Surface devices” for details on Intune, Entra ID, co-management, and DFCI.

    1. Printer drivers and enterprise print management

    For Arm-based Windows 11 devices, printer and scanner support depends on driver availability:

    • Drivers must be designed for Arm-based devices, or be built into Windows.
    • Peripheral compatibility (including printers and scanners) depends on Arm64 drivers provided by the hardware vendor or included in Windows.
    • If the hardware developer does not provide Arm64 drivers, functionality may be limited. In such cases, installing the printer via Windows’ built-in mechanisms may still provide basic functionality. See “Install a printer in Windows” in the referenced FAQ.

    The context does not list specific enterprise print-management products, but any solution that depends on custom kernel-mode or user-mode drivers must have Arm64-compatible components to be fully supported.

    1. Categories of software with potential compatibility limitations

    The documentation highlights several software categories that may have limitations on Arm-based Surface devices:

    • Drivers and hardware-dependent apps: Any app that relies on drivers must have Arm64-compatible drivers.
    • Certain games: Titles that require OpenGL > 3.3 or anti-cheat drivers not updated for Arm may not work.
    • Customization and shell-modifying apps: Input Method Editors (IMEs), cloud storage sync clients, and other apps that modify the Windows experience may have limited functionality unless optimized for Arm64.
    • Antivirus/endpoint security: Many non-Microsoft antivirus products now support Arm-based PCs, but compatibility must be confirmed with the vendor. Some non-Microsoft antivirus software cannot be installed on Arm-based processors.
    • Windows Fax and Scan: Not available on Arm-based devices.

    More generally, the app-compat guidance for Windows on Arm notes:

    • Most x86 Win32 apps are supported via emulation.
    • Native Arm64 and Microsoft Store UWP apps provide the best performance and battery life.
    • x64 emulation in Windows 11 significantly broadens app compatibility.
    • Apps that do not meet these criteria should be checked with the publisher for an Arm64 version.

    Microsoft also points to an evolving third-party list of compatible apps and games at www.worksonwoa.com.

    1. Enterprise deployment considerations and best practices

    Key considerations and recommendations for deploying Arm-based Surface devices in enterprise environments include:

    • App compatibility and testing
      • Most x86 Win32 apps and many x64 apps run via emulation; however, any app that installs drivers, low-level security components, or shell extensions should be validated for Arm64 support.
      • Use native Arm64 versions of apps where available (for example, Microsoft 365 Apps, Microsoft Teams, Adobe Photoshop/Lightroom, Microsoft Edge, and other Arm64-optimized software) for best performance and battery life.
      • For apps with issues, commercial customers can use the App Assure program (part of Microsoft FastTrack) at no extra cost to help remediate compatibility problems for Windows 10/11 on Arm.
    • Management and security
      • Manage Arm-based Surface devices with Intune and DFCI for firmware-level control, just as with other Surface devices.
      • Integrate with Microsoft Entra ID for cloud-based management and policy enforcement.
      • Co-manage with Configuration Manager using the 32-bit x86 ConfigMgr client where required.
      • Microsoft Defender is fully supported and protects Windows 10/11 on Arm-based PCs throughout the device lifecycle. Non-Microsoft AV/EDR solutions must be validated with the vendor for Arm64 support.
    • Virtual desktops and remote workloads
      • Azure Virtual Desktop is supported and can be used to deliver Windows desktops and apps to Arm-based Surface devices, which can be useful when specific line-of-business apps or tools are not yet Arm64-compatible.
    • General platform characteristics
      • Arm-based Surface devices (e.g., Surface Pro 11th Edition and Surface Laptop 7th Edition with Snapdragon X series) are positioned for strong performance, excellent battery life, and high compatibility with both native and emulated apps.
      • Prism, the emulation engine, optimizes x86/x64 app performance and reduces CPU usage, helping emulated apps perform on par with or better than older x64 Surface models.

    For any specific third-party products in the environment (Trend Micro endpoint/XDR, ManageEngine ServiceDesk Plus, print management solutions), the vendor’s documentation should be checked for Windows 11 on Arm/Arm64 support, especially for components that install drivers, kernel hooks, or low-level agents.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.