Need help converting multiple azure devops organizations Workload identity service connections to old format
We use Workload identity service connections in Azure DevOps. We have a requirement that these entra id app are configured multi-tenant however by a change of Microsoft is not working in the new format we need help converting our devops organizations back to the old method so we can keep on working without interruption.
This is the issue we are having
Update: Workload identity federation uses Entra issuer: We've changed the format of the federated credential for new Azure and Docker service connections. Specifically, we changed the Issuer and Subject format as shown: ||Azure DevOps Issuer|Entra Issuer (new service connections)| | -------- | -------- | -------- | |Issuer|
https://vstoken.dev.azure.com/<organization id>|https://login.microsoftonline.com/<Entra tenant id>/v2.0| |||| |Issuer|https://vstoken.dev.azure.com/<organization id>|https://login.microsoftonline.com/<Entra tenant id>/v2.0| |Subject|sc://<organization name>/<project name>/<service connection name>|<entra prefix>/sc/<organization id>/<service connection id>|Existing service connections will work as before without any changes required. There's no change in configuration and the way tokens are obtained stays the same. Pipeline tasks don't need to be updated and work as before. For more information, review Workload identity federation uses Entra issuer. Impacted scenarios:
- If you're using automation scripts or the Terraform Azure DevOps provider to create workload identity federation–based service connections, review the Automation section of the release notes for changes you will need to make.
- If you're facing issues with third-party tasks, contact the task owners.
- Contact your Microsoft Entra tenant administrator to make sure the federation policy in your Entra tenant supports the new format. See our Troubleshooting documentation for more information.
- The new Entra issuer format has a limitation with multi-tenant app scenarios. If you're creating a service connection for this purpose, first evaluate if your scenario actually requires multi-tenant app registration. If required, reach out to Microsoft support to request the feature be disabled for your organization.