1

We have a service connection from Azure DevOps to an Azure Subscription that has been stable and working for several years. A few days ago, the key that it used to retrieve an access token expired, and deployments began to fail.

We refreshed the key, but now when we try to run a deployment we get the same Could not fetch Access Token for azure error, as if the key is cached somewhere.

If we create a new subscription connection, then deployment succeeds, but we have dozens of deployments using the same subscription connection, so it is a large job to replace them all.

How can we get Azure to recognise correctly that we have refreshed the key - or are there steps in renewing token access that we have missed?

Jude Fisher
  • 11,138
  • 7
  • 48
  • 91

1 Answers1

1

You could update a created Service Connection in Project Settings -- Service Connection -- Update service Connection.

enter image description here

You could use the full version of the service connection dialog

If you are using preview feature of service connections. All you have to do is navigate to the service connection, click "Edit" in the upper right corner and then save without any changes.

enter image description here

More details take a look at this similar question:

PatrickLu-MSFT
  • 49,478
  • 5
  • 35
  • 62