Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Microsoft Entra authentication is a mechanism for connecting to Azure HorizonDB by using identities defined in Microsoft Entra ID. By using Microsoft Entra authentication, you can manage database user identities and other Microsoft services in a central location, which simplifies permission management.
Benefits of using Microsoft Entra ID include:
- Authentication of users across Azure services in a uniform way.
- Centralized management of identities and authentication policies.
- Support for multiple forms of authentication, which can eliminate the need to store credentials.
- The ability to manage access through Microsoft Entra groups, rather than managing group member's access individually.
- The use of HorizonDB cluster roles to authenticate identities at the database level.
- Support of token-based authentication for applications that connect to Azure HorizonDB.
How Microsoft Entra ID works in Azure HorizonDB
Microsoft Entra authentication is configured at the cluster level, so the authentication configuration applies to all pools created under the cluster. To authenticate Microsoft Entra identities, Azure HorizonDB uses OAuth 2.0 access tokens. After Microsoft Entra ID verifies an identity, it issues an access token that is used to authenticate the connection to the HorizonDB cluster. The following steps describe how the authentication flow works.
- The client requests a Microsoft Entra access token to authenticate to Azure HorizonDB.
- Microsoft Entra ID verifies the identity and returns an OAuth 2.0 access token as a JSON Web Token (JWT).
- The client uses the access token to authenticate the connection to the HorizonDB cluster.
- The HorizonDB cluster validates the access token with Microsoft Entra ID.
For the steps to configure Microsoft Entra ID with Azure HorizonDB, see Configure Microsoft Entra authentication in Azure HorizonDB.
Administrator roles
When you turn on Microsoft Entra authentication for your Microsoft Entra principal as a Microsoft Entra administrator, the account:
- Gets the same privileges as the original PostgreSQL administrator.
- Can manage other Microsoft Entra roles on the server.
Azure HorizonDB supports both a local administrator and a Microsoft Entra administrator. The administrator you use determines which identities you can create and manage.
The local administrator is created during cluster provisioning and uses password authentication. A Microsoft Entra administrator is a Microsoft Entra identity that you configure separately, either during or after cluster provisioning, and uses Microsoft Entra authentication.
The Microsoft Entra administrator has administrator privileges in the database and can create and manage Microsoft Entra-based database roles, including roles mapped to Microsoft Entra users, groups, and managed identities. The Microsoft Entra administrator can also manage local PostgreSQL roles. The local administrator can manage local PostgreSQL roles but can't create or manage roles based on Microsoft Entra identities.
For service-specific considerations that apply to Microsoft Entra authentication and administration in Azure HorizonDB, see Limitations.
Connection via Microsoft Entra identities
Microsoft Entra authentication in Azure HorizonDB supports the following methods to obtain an access token for connecting to a cluster:
- Microsoft Entra password authentication
- Microsoft Entra integrated authentication
- Microsoft Entra universal with multifactor authentication
- Service principal authentication using a certificate or client secret
- Managed identity
After Microsoft Entra ID authenticates the identity, the client obtains an access token and supplies it when connecting to HorizonDB. The token is used instead of a local database password.
Limitations and considerations
When you use Microsoft Entra authentication with Azure HorizonDB, keep the following limitations and considerations in mind:
- Microsoft Entra authentication management requires available compute. Some Microsoft Entra authentication operations, including adding, updating, or removing a Microsoft Entra administrator, aren't available when the HorizonDB cluster doesn't have an available compute pool. Ensure that compute is available before performing these operations.
- Automatic Microsoft Entra group synchronization isn't supported. Azure HorizonDB supports authentication with Microsoft Entra group identities, but changes to group membership aren't automatically synchronized with the cluster.
- Microsoft Entra authentication is limited to a single tenant. Azure HorizonDB doesn't support multitenant Microsoft Entra authentication. Microsoft Entra identities used to authenticate to HorizonDB must belong to the same Microsoft Entra tenant associated with the cluster.