Connect with managed identity to Azure Database for PostgreSQL - Flexible Server
APPLIES TO: 
Azure Database for PostgreSQL - Flexible Server
You can use both system-assigned and user-assigned managed identities to authenticate to Azure Database for PostgreSQL flexible server. This article shows you how to use a system-assigned managed identity for an Azure Virtual Machine (VM) to access an Azure Database for PostgreSQL flexible server instance. Managed Identities are automatically managed by Azure and enable you to authenticate to services that support Microsoft Entra authentication without needing to insert credentials into your code.
You learn how to:
- Grant your VM access to an Azure Database for PostgreSQL flexible server instance.
- Create a user in the database that represents the VM's system-assigned identity.
- Get an access token using the VM identity and use it to query an Azure Database for PostgreSQL flexible server instance.
- Implement the token retrieval in a C# example application.
Prerequisites
- If you're not familiar with the managed identities for Azure resources feature, see this overview. If you don't have an Azure account, sign up for a free account before you continue.
- To do the required resource creation and role management, your account needs "Owner" permissions at the appropriate scope (your subscription or resource group). If you need assistance with a role assignment, see Assign Azure roles to manage access to your Azure subscription resources.
- You need an Azure VM (for example, running Ubuntu Linux) that you'd like to use to access your database using Managed Identity
- You need an Azure Database for PostgreSQL flexible server instance that has Microsoft Entra authentication configured
- To follow the C# example, first, complete the guide on how to Connect with C#
Create a system-assigned managed identity for your VM
Use az vm identity assign with the identity assign command enables the system-assigned identity to an existing VM:
az vm identity assign -g myResourceGroup -n myVm
Retrieve the application ID for the system-assigned managed identity, which you'll need in the next few steps:
# Get the client ID (application ID) of the system-assigned managed identity
az ad sp list --display-name vm-name --query [*].appId --out tsv
Create an Azure Database for PostgreSQL flexible server user for your Managed Identity
Now, connect as the Microsoft Entra administrator user to your Azure Database for PostgreSQL flexible server database, and run the following SQL statements, replacing <identity_name> with the name of the resources for which you created a system-assigned managed identity:
Please note pgaadauth_create_principal must be run on the Postgres database.
select * from pgaadauth_create_principal('<identity_name>', false, false);
Success looks like:
pgaadauth_create_principal
-----------------------------------
Created role for "<identity_name>"
(1 row)
For more information on managing Microsoft Entra ID enabled database roles, see how to manage Microsoft Entra ID enabled Azure Database for PostgreSQL - Flexible Server roles
The managed identity now has access when authenticating with the identity name as a role name and the Microsoft Entra token as a password.
Note
If the managed identity is not valid, an error is returned: ERROR: Could not validate AAD user <ObjectId> because its name is not found in the tenant. [...].
Note
If you see an error like "No function matches...", make sure you're connecting to the postgres database, not a different database that you also created.
Retrieve the access token from the Azure Instance Metadata service
Your application can now retrieve an access token from the Azure Instance Metadata service and use it for authenticating with the database.
This token retrieval is done by making an HTTP request to http://169.254.169.254/metadata/identity/oauth2/token and passing the following parameters:
api-version=2018-02-01resource=https://ossrdbms-aad.database.windows.netclient_id=CLIENT_ID(that you retrieved earlier)
You get back a JSON result containing an access_token field - this long text value is the Managed Identity access token you should use as the password when connecting to the database.
For testing purposes, you can run the following commands in your shell.
Note
Note you need curl, jq, and the psql client installed.
# Retrieve the access token
export PGPASSWORD=`curl -s 'http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https%3A%2F%2Fossrdbms-aad.database.windows.net&client_id=CLIENT_ID' -H Metadata:true | jq -r .access_token`
# Connect to the database
psql -h SERVER --user USER DBNAME
You're now connected to the database you configured earlier.
Connect using Managed Identity
This section shows how to get an access token using the VM's user-assigned managed identity and use it to call Azure Database for PostgreSQL flexible server. Azure Database for PostgreSQL flexible server natively supports Microsoft Entra authentication, so it can directly accept access tokens obtained using managed identities for Azure resources. When creating a connection to Azure Database for PostgreSQL flexible server, you pass the access token in the password field.
Connect using Managed Identity in Python
For a Python code example, please refer to the Quickstart: Use Python to connect and query data in Azure Database for PostgreSQL - Flexible Server
Connect using Managed Identity in Java
For a Java code example, please refer to the Quickstart: Use Java and JDBC with Azure Database for PostgreSQL - Flexible Server
Connect using Managed Identity in C#
Here's a .NET code example of opening a connection to Azure Database for PostgreSQL flexible server using an access token. This code must run on the VM to use the system-assigned managed identity to obtain an access token from Microsoft Entra ID. Replace the values of HOST, USER (with <identity_name>), and DATABASE.
using System;
using System.Net;
using System.IO;
using System.Collections;
using System.Collections.Generic;
using System.Text.Json;
using System.Text.Json.Serialization;
using Npgsql;
using Azure.Identity;
namespace Driver
{
class Script
{
// Obtain connection string information from the portal for use in the following variables
private static string Host = "HOST";
private static string User = "USER";
private static string Database = "DATABASE";
static async Task Main(string[] args)
{
//
// Get an access token for PostgreSQL.
//
Console.Out.WriteLine("Getting access token from Azure AD...");
// Azure AD resource ID for Azure Database for PostgreSQL Flexible Server is https://ossrdbms-aad.database.windows.net/
string accessToken = null;
try
{
// Call managed identities for Azure resources endpoint.
var sqlServerTokenProvider = new DefaultAzureCredential();
accessToken = (await sqlServerTokenProvider.GetTokenAsync(
new Azure.Core.TokenRequestContext(scopes: new string[] { "https://ossrdbms-aad.database.windows.net/.default" }) { })).Token;
}
catch (Exception e)
{
Console.Out.WriteLine("{0} \n\n{1}", e.Message, e.InnerException != null ? e.InnerException.Message : "Acquire token failed");
System.Environment.Exit(1);
}
//
// Open a connection to the PostgreSQL server using the access token.
//
string connString =
String.Format(
"Server={0}; User Id={1}; Database={2}; Port={3}; Password={4}; SSLMode=Prefer",
Host,
User,
Database,
5432,
accessToken);
using (var conn = new NpgsqlConnection(connString))
{
Console.Out.WriteLine("Opening connection using access token...");
conn.Open();
using (var command = new NpgsqlCommand("SELECT version()", conn))
{
var reader = command.ExecuteReader();
while (reader.Read())
{
Console.WriteLine("\nConnected!\n\nPostgres version: {0}", reader.GetString(0));
}
}
}
}
}
}
When run, this command gives an output like this:
Getting access token from Azure AD...
Opening connection using access token...
Connected!
Postgres version: PostgreSQL 11.11, compiled by Visual C++ build 1800, 64-bit
Next steps
- Review the overall concepts for Microsoft Entra authentication with Azure Database for PostgreSQL - Flexible Server