Skip to main content
Niteshift obtains and refreshes OIDC tokens for Azure workload identity authentication.
Ask the agent in a task to connect Azure. It writes the configuration, walks you through the cloud-side setup below, and verifies access. See the quick start.
For the Niteshift configuration, declare the Microsoft Entra tenant ID and the identity’s client ID in the environment’s committed settings.yaml:
settings.yaml
Run ns oidc-token --inspect --audience 'api://AzureADTokenExchange' in the Niteshift terminal tab to see the trust values without printing the token. On the app registration identified by clientId, add a federated credential with the exact inspected iss, aud, and environment-specific sub. Microsoft Entra checks all three values with case-sensitive matching. Replace the placeholders below with the inspected values:
The subject is the entire inspected org:<org_id>:environment:<environment_id> value. Use a distinct credential name for each environment you authorize. Separately grant the app’s service principal only the permissions it needs on the intended Azure resources. See Microsoft Entra’s federated credential guide for the Azure-side setup.