Could not fetch access token for Azure. Verify if the Service Principal used is valid and not expired.

Question

When we are deploying the web app we are facing this issue:

Error: Failed to get resource ID for resource type 'Microsoft.Web/Sites' and resource name 'DPSREQUESTFORMS'. Error: Could not fetch access token for Azure. Verify if the Service Principal used is valid and not expired. For more information refer https://aka.ms/azureappservicedeploytsg

Answer 1

Could not fetch access token for Azure. Verify if the Service Principal used is valid and not expired.

if you are facing this issue , you can navigate to

Azure Devops _____> ProjectSettings ------> PipeLines --------> Service Connections --------->

here you can find the list of service connections available were displayed . select the service connection which you are facing issue

you will find this screen

it will navigate to expired page

then you can observe expired token one , delete that and create a new certificate .

final step is you need to go to back like

Azure Devops _____> ProjectSettings ------> PipeLines --------> Service Connections --------->

select the service connection which you are facing issue ---> select the edit button ---and just click on save button _---------> it will asks azure authentication ------> once you are done with
successful authentication , release pipe line works like as usual ,.

Answer 2

Thanks for asking question! To elaborate on this you may want to know that Azure App Service Deploy task uses the service principal in the service connection to authenticate with Azure. The task fails with this error if the service principal has expired or doesn't have permissions to the App Service.

Recommend you to verify the validity of the service principal used and if it's present in the app registration.

You may refer to Use role-based access control to manage access to your Azure subscription resources and SO link here

Also check this blog on Automating Azure Resource Group deployment using a Service Principal in Visual Studio Online: Build/Release Management

Let us know if further query on this or issue remains.

Answer 3

If you are here because of a YAML AzureDevops Pipeline failure, this happens because the authentication with GitHub has expired. You cannot create a new token because you cannot edit the expire done.

Instead, the fix is really easy and is a two-click operation.

1. Go to your pipeline's settings page
2. Under "get sources" select the connection to GitHub.
3. You'll see a "Authorized with service connection" setting. Just drop down that caret and select "create new connection.

See my screenshot