Function app in Azure is not working due to the Visual Studio Team Services Project getting an error when deploying

Question

Function app in Azure is not working due to the Visual Studio Team Services Project getting an error when deploying

Logan Angel 0

The deployment fails when trying to get the access token. This was working without issues until recently. We have looked through various places to locate the resource it is failing to find or key that is expired, but the original developers didn't leave any notes. There are app registrations we found that are expired, however, we don't know if these are related and, if new secrets are created, where to apply them.

##[debug]Deployment Failed with Error: Error: Failed to get resource ID for resource type 'Microsoft.Web/Sites' and resource name 'DFM'. Error: Could not fetch access token for Azure. Status code: invalid_client, status message: Error(s): 7000222 - Timestamp: 2025-07-01 20:32:41Z - Description: AADSTS7000222: The provided client secret keys for app '***' are expired. Visit the Azure portal to create new keys for your app: https://aka.ms/NewClientSecret, or consider using certificate credentials for added security: https://aka.ms/certCreds. Trace ID: c59494a9-5dbc-4950-b6bc-0a28915f5500 Correlation ID: 4603d1e9-b4c0-477f-9b6a-96dbca9a3746 Timestamp: 2025-07-01 20:32:41Z - Correlation ID: 4603d1e9-b4c0-477f-9b6a-96dbca9a3746 - Trace ID: c59494a9-5dbc-4950-b6bc-0a28915f5500

Chiugo Okpala 1,905 Reputation points MVP

2025-07-02T17:04:33.9266667+00:00
@Logan Angel welcome to the Microsoft Q&A community.

You're seeing a deployment failure because the client secret for the Azure AD App Registration used in the deployment pipeline has expired.

Key Error Details:

AADSTS7000222: The provided client secret keys for app '***' are expired.

What’s Happening

Your Azure DevOps pipeline (or release pipeline) is trying to authenticate using an App Registration with a client secret. That secret has now expired, so it can no longer retrieve an access token, and the deployment fails when attempting to access the Azure Function App (Microsoft.Web/Sites).

Resolution Steps

Identify the Right App Registration

You need to find which App Registration is used for authentication.

Go to Azure DevOps → Project Settings → Service connections.

Look for a Service Principal or connection (probably of type Azure Resource Manager).

In the connection details, find the App Registration/client ID being used (or tenant/client ID).

If you have access to the Azure AD, go to:

Azure Portal → Azure Active Directory → App registrations → search using the client ID (from above).

Open the app registration and verify Secrets under Certificates & secrets.

Create a New Secret

In the identified App Registration:

Go to Certificates & secrets.

Click New client secret.

Set an appropriate expiration (e.g., 12 or 24 months).

Copy the value immediately—you won’t be able to retrieve it again.

Update the Service Connection in Azure DevOps

Go back to the Service connection in Azure DevOps.

Click Edit.

Replace the old client secret with the new one.

Save and verify connection to ensure it authenticates correctly.

Re-run the Pipeline

After updating the client secret:

Re-run the deployment pipeline.

It should now be able to get a token and proceed with the deployment.

Optional Clean-Up

Delete any expired secrets from the App Registration.

Rotate secrets every 6–12 months as best practice.

Consider using certificate-based authentication instead of secrets for more secure and longer-lived credentials (recommended for production).

N/B: I have generated the above answer using chatgpt as an AI tool. Also I have validated and updated the AI output.

I hope these helps. Let me know if you have any further questions or need additional assistance.

Also if these answers your query, do click the "Upvote" and click "Accept the answer" of which might be beneficial to other community members reading this thread.

Share via

Function app in Azure is not working due to the Visual Studio Team Services Project getting an error when deploying

Your answer