Connect to Microsoft Azure
Secure backend access with OIDC federation is available on all plans
To understand how Azure supports OIDC through Workload Identity Federation, consult the Azure documentation.
- Navigate to All services
- Select Identity
- Select Manage Identities and select Create
- Choose your Azure Subscription, Resource Group, Region and Name
- Go to Federated credentials and select Add Credential
- In the Federated credential scenario field select Other
- Enter the Issuer URL, the URL will depend on the issuer mode setting:
- Team: , replacing with the path from your Vercel team URL
- Global:
- In the Subject identifier field use:
- Replace with your team identifier from the Vercel's team URL
- Replace with your project's name in your project's settings
- In the Name field, use a name for your own reference such as:
- In the Audience field use:
- Replace with your team identifier from the Vercel's team URL
Azure does not allow for partial claim conditions so you must specify the and fields exactly. However, it is possible to create mutliple federated credentials on the same managed identity to allow for the various claims.
In order to connect to the Azure service that you would like to use, you need to allow your Managed Identity to access it.
For example, to use Azure CosmosDB, associate a role definition to the Managed Identity using the Azure CLI, as explained in the Azure CosmosDB documentation.
You are now ready to connect to your Azure service from your project's code. Review the example below.
In the following example, you create a Vercel function in a Vercel project where you have defined Azure account environment variables. The function will connect to Azure using OIDC and use a specific resource that you have allowed the Managed Identity to access.
Install the following packages:
In the API route for this function, use the following code to perform a database query from an Azure CosmosDB instance:
Was this helpful?