After announcing the release of Managed Identity and Service Principal support in public preview last March, we were overcome by the positive response many of you had. We’re grateful to those who have taken the time to implement a managed identity within your apps and tools. With your help, we’ve collected valuable feature feedback and resolved some hidden bugs to improve the overall performance of this feature, bringing us to today, when we’re happy to announce that the feature is now in General Availability (GA).
Some notable GA user-facing updates worth calling out:
1. Set object-level permissions on service principals and managed identities across the site:
We’ve scoured the site to look for every dropdown where it makes sense to include service principals. They have now been added to many object-level permissions dialogs across the platform, allowing you to set specific permissions for service principals in objects, such as Agent Pools, Feeds, Packages, Service Connections, and more.
2. Extended capabilities for service principals and managed identities in the Boards space:
Service principals are now a little more powerful in Boards! Service principal support in Boards has been extended in the following places:
- Assign To field of a work item,
- Boards’ configuration pages, including for swimlane and style rules,
- Boards’ cards,
- Process rules and custom identities
3. Service principals and managed identities are blocked from using Azure DevOps OAuth:
To reduce confusion on how service principals might be used, we have disabled any implementation of service principals in Azure DevOps OAuth flows, as they only pertain to the Microsoft Identity platform, and not Azure DevOps’s OAuth platform.
We continue to welcome any new feedback you have on how we can improve this feature. But we hope the bug fixes and feature improvements we’ve made over these past few months will mean even more of you will explore implementing it more broadly within your organizations. Docs have also been clarified to address questions that have come up since public preview.
And as always, the comments section and the Developer Community remain open for you to share any thoughts and concerns you’d like us to hear!