What Microsoft announced
Microsoft's update describes Entra authentication as a more secure, identity-based way to sign in to HorizonDB. Teams can manage identities and access centrally instead of relying only on locally managed database passwords. Microsoft says this reduces credential-management overhead and strengthens security posture. Those are vendor claims, not independently measured results.
Microsoft calls Entra authentication the recommended approach for HorizonDB. It is not mandatory. Customers can use it exclusively, to get stronger protection against password-based risks. They can also enable it alongside HorizonDB password authentication when local credentials are still needed. The announcement does not say password authentication is being removed.
Why the timing matters
Microsoft announced the general availability of Azure HorizonDB at Ignite on November 17, 2026, alongside a public preview of Fabric HorizonDB. Azure HorizonDB is available in 13 Azure regions across the Americas, Europe and Asia Pacific, with more coming. That regional figure applies to the HorizonDB service launch. The Entra announcement does not give its own regional or licensing details.
Entra sign-in is not new to HorizonDB. The preview announcement a year ago already promised native Entra ID support, Private Endpoints and data encryption. The change now is the production-ready label. For regulated or conservative shops, that label decides whether identity-based database access can go into a real design.
Microsoft's launch post frames the feature in governance terms. Entra ID authentication centralizes identity-based access to the database and helps teams apply consistent identity governance across the Azure environment. The practical argument is simple. Joiners, movers and leavers are handled in the directory you already run, not in a per-database list of roles and passwords.
How it is configured
Microsoft Learn models authentication methods as child resources of a HorizonDB cluster. Entra authentication is a resource named microsoftEntra, with the type Microsoft.HorizonDb/clusters/authentications. Its only documented setting is state, which is either Enabled or Disabled. Microsoft says no other properties are required.
The documentation gives declarative examples for several tools:
- REST API: a
PUTto the cluster'sauthentications/microsoftEntrapath creates or replaces the method. - Bicep and ARM templates: set the child resource name to
microsoftEntraandproperties.statetoEnabled. - Terraform (AzAPI provider): the same resource type and body, using the AzAPI provider.
- SDK samples: generated examples show the same
EnabledorDisabledstate.
Repeating the same request is idempotent. That suits infrastructure-as-code pipelines, because re-running a deployment will not change anything.
Password authentication is a separate sibling resource named passwordMethod. It has its own state, plus an administrator login and password supplied at initial setup. The two methods are configured independently, which is what lets Microsoft offer the mixed Entra-plus-password option. The documentation excerpts I reviewed do not say which method is on by default for new or existing clusters, so check your cluster rather than assuming.
A version label to read carefully
The management API pages are labelled 2026-10-01-preview. That is the API version string on the reference documentation. It does not undo the general availability of the feature itself. It also does not show that this particular API version is a stable one. If you pin API versions in templates, watch for a non-preview version and plan an update when one appears.
The cleanup trap
Microsoft's API description includes a warning that is easy to miss. Disabling Entra authentication does not remove or change database roles or users created earlier. This covers principals created through the MicrosoftEntraAdministrators control-plane API or directly through pgaadauth extension functions.
Turning the method off is therefore not an offboarding step. Treat authentication-method state and database-principal cleanup as two separate tasks. Audit the roles inside the database as well, particularly if you are rolling back a pilot.
Client support
Microsoft's HorizonDB connection guide shows one client path with Entra support. It describes the PostgreSQL extension for Visual Studio Code as offering Entra authentication for Azure HorizonDB. The same guide shows standard psql connection strings and says HorizonDB works with existing PostgreSQL clients, drivers and ORMs. It does not say every driver or tool handles Entra token sign-in identically. Test your own stack, such as ORMs, connection poolers and CI jobs, before removing password fallback.
Practical guidance
- Decide your target state. Choose between Entra-only and a transition period with both methods enabled. Microsoft supports both.
- Manage it as code. Put the
microsoftEntraresource in your Bicep, ARM or Terraform definitions so the setting is reviewable. - Inventory service accounts. Applications and automation that use passwords need a tested Entra-based path before you drop password authentication.
- Plan role cleanup separately. Remember that disabling the method leaves Entra-created database roles in place.
- Check regions. Confirm your target region is among the launch regions before planning a rollout.
What is still unclear
The sources I reviewed do not detail token-acquisition mechanics, enforcement controls, a migration sequence or a compatibility matrix. They do not give fees or region limits specific to the Entra feature. Anyone planning a production change should read the current HorizonDB setup and connection documentation before acting.
Bottom line
This is a modest but meaningful hardening milestone. Identity-based access for HorizonDB is now production-supported, with passwords kept as an optional fallback. The setting itself is simple. The harder work is the same as with any Entra rollout: inventorying who and what connects, and cleaning up the roles left behind.
References
- (Launched) Generally Available: Microsoft Entra authentication for Azure HorizonDB Azure Updates · 2026-11-17T20:00:32Z
- Microsoft Entra Authentications - Create Or Replace - REST API (Azure HorizonDB) | Microsoft Learn learn.microsoft.com
- HorizonDB: PostgreSQL for enterprises, developers, and agents on Azure and Fabric techcommunity.microsoft.com