Blog Post

Azure Arc Blog
2 MIN READ

Securing Azure Arc-enabled servers with TPM-backed identity and user-assigned identities (preview)

yunishussein's avatar
yunishussein
Icon for Microsoft rankMicrosoft
Nov 17, 2026

Hardware-protected credentials and flexible, reusable identities for your hybrid servers

As organizations expand their hybrid environments, protecting server identities becomes increasingly critical. Azure Arc-enabled servers use managed identities to securely access Azure services, and until now those identity credentials have been stored on disk and protected by local access controls. Each server has also been limited to a single system-assigned identity that is created with the server and deleted with it.

Today we are excited to announce two capabilities that work together to change that: TPM-backed identity, which protects managed identity credentials with the Trusted Platform Module (TPM) or virtual TPM (vTPM), and user-assigned managed identity support, which lets you connect a server with one or more identities you create and manage yourself. Both are available in public preview today.

TPM-backed identity: hardware protection for server credentials

With TPM-backed identity, the managed identity's private key is sealed by the server's TPM. By onboarding servers with TPM-backed key storage, you gain:

  • Hardware-backed credential protection, so the identity key is sealed by a hardware component instead of relying on local access controls alone.
  • Unexportable credentials, so even privileged users cannot extract or export the identity material from the TPM.

You opt in at onboarding with a single parameter, --identity-key-store, and the agent handles the rest of the process transparently.

User-assigned managed identities: identities you control

A system-assigned identity is tied to the life of one server. A user-assigned managed identity is a standalone Azure resource that you create, govern and reuse. With this preview you can:

  • Connect a server with one or more existing user-assigned managed identities, up to 10 per server.
  • Choose whether the server uses only user-assigned identities or keeps a system-assigned identity alongside them.
  • Add, replace or detach user-assigned identities after onboarding, without reconnecting the server.
  • Add a system-assigned identity later, even to a server onboarded with only user-assigned identities.

Because a UAMI exists independently of any one machine, you can grant its role assignments once and attach the same identity to many servers or rotate a server to a new identity on your own schedule.

Better together

TPM-backed identity and user-assigned managed identities bring hardware-backed protection and flexible identity management together. UAMI onboarding requires TPM-backed key storage, helping protect credentials while giving you control over which identities your servers use.

The result: access can evolve with your organization while credential protection remains anchored to the server’s hardware.

Get started

To get started, explore the prerequisites, onboarding commands and verification steps for TPM-backed identity and user-assigned managed identities for Azure Arc-enabled servers.

Updated Nov 17, 2026
Version 1.0