Azure DevOps service connection, FrontDoor webroot

Torben 20 Reputation points
2023-02-23T15:03:51.38+00:00

Hello,

I received this error today in my pipelines in Azure DevOps:
##[error]Error: Failed to get resource ID for resource type 'Microsoft.Web/Sites' and resource name 'custom-prod'. 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

After this I figured it out that the application, which is automatically installed when adding a service connection in my DevOps panel has an outdated secret. Unfortunately I am not the creator of this connection, so I can not hit save here once again to renew the client credentials.

Therefore I created a new service connection in DevOps. I used: Azure Resource Manager -> Service principal (automatic)
CleanShot 2023-02-23 at 15.59.04@2x

After this I changed my azureSubscription in my pipeline yaml to reflect "Marketing2". I hit rerun for the pipeline and it worked smoothly. Unfortnately now I see this:
CleanShot 2023-02-23 at 16.00.24@2x

Now I wonder, can this occur because I have changed the service connection in my pipeline? It would be a surprise for me.
Also in FrontDoor I see a path like '/de' on the backend pool, but where is the webroot /home/site/wwwroot/public set up?

Does somebody has answers?

Community Center | Not monitored
{count} votes

1 answer

Sort by: Most helpful
  1. ChaitanyaNaykodi-MSFT 27,476 Reputation points Microsoft Employee Moderator
    2023-02-28T20:09:25.4866667+00:00

    @Torben

    Thank you for reaching out. Currently Azure Dev Ops is not supported on Microsoft Q&A forum, for any questions related to Azure Dev OPS you can reach out on this forum

    Based on the error message above, I assume you have Azure App service as backend pool of Azure Front Door. If that is true, you can through this similar issue and see if that helps to resolve the issue. Thank you!

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.