Fix expired secrets in Azure DevOps Service Connections
· 2 min read
Workload Identity Federation is the recommended approach for Service Connection.
So why would I use the old approach with an app registration where I need to rotate the secret by myself?
Well, there are some pipeline tasks which doesn't support Workload Identity Federation.
And in this case, you have to use the old approach.
And today was the day of rotation.
And a team member tried to renew the secret but didn't know how to do it, because the problem is still not fixed correctly in the UI.
Let's check the steps to fix it.
