Deployment Script Error "DeploymentScriptOperationFailed"

Question

Deployment Script Error "DeploymentScriptOperationFailed"

Luke Kolodziej 0

I have a deployment script that is throwing a "DeploymentScriptOperationFailed" error code containing this message "Encountered an internal server error. The tracking activity id is '77dc9dbe-98a9-46ea-8d31-5a46d563a660', correlation id is '2ce207e8-1706-4e7c-b945-26361ca69b66'."

The script uses the GoDaddy API to query and update DNS records based on values needed to assign a custom domain to an Azure App Service also created by the bicep deployment.

Siva Nair 345 Reputation points Microsoft External Staff Moderator

2025-08-07T17:58:57.6266667+00:00
Hi Luke Kolodziej,

The error message you are encountering is indicating that there is an unexpected internal server error. This error can be caused by a temporary problem with the Azure servers.

You can try to resolve this issue by retrying the deployment. If the issue persists, you can try to get more details by enabling debug logging when running the deployment.

If retrying does not resolve the issue, can you please check here to see how to check the deployment logs, which should provide more detailed error messaging.

Check Deployment Logs in Azure Portal:

Go to the Resource Group > Deployments section and inspect the detailed logs for the failed deployment. Look for any specific error messages or failed operations.

Enable Verbose Logging in Your Script:

Add detailed logging to your deployment script to capture API responses and errors from GoDaddy.

Retry the Deployment:

Since this might be a transient issue, retrying the deployment after a short wait can sometimes resolve it.

Test the Script Outside Azure:

Run the script locally or in a test environment to verify that the GoDaddy API calls work as expected.

Use az deployment-scripts CLI for Debugging:

You can inspect the deployment script resource using powershell: az`` deployment-scripts show --name <script-name> --resource-group <rg-name>

Let me know , if you need further assistance.
Siva Nair 345 Reputation points Microsoft External Staff Moderator

2025-08-08T18:28:29.23+00:00

Hi Luke Kolodziej,

Just checking back to see if the above response was helpful, let me know if you have any other questions or queries, happy to help you.
Siva Nair 345 Reputation points Microsoft External Staff Moderator

2025-08-11T16:59:00.51+00:00

Hi Luke Kolodziej,

Just checking back to see if the above response was helpful, let me know if you have any other questions or queries, happy to help you.
Luke Kolodziej 0 Reputation points

2025-08-11T17:44:17.3933333+00:00

For clarification, the error message I posted was from the Deployment Logs in the Azure Portal (Suggestion 1) (Subscription > Deploment Stack > Deployment >> Script). I had already added detailed logging to the script (Suggestion 2) but was not able to find or see any of the output in the portal. I had also retried the deployment several times (Suggestion 3) with the same result.

Suggestion 4 lead me to find the docs for configuring a development environment and I was able to use the Docker method to run the script locally and see the actual error which turned out to be a jq query failure.

Your answer

Siva Nair 345 Reputation points Microsoft External Staff Moderator

2025-08-07T17:58:57.6266667+00:00

Hi Luke Kolodziej,

The error message you are encountering is indicating that there is an unexpected internal server error. This error can be caused by a temporary problem with the Azure servers.

You can try to resolve this issue by retrying the deployment. If the issue persists, you can try to get more details by enabling debug logging when running the deployment.

If retrying does not resolve the issue, can you please check here to see how to check the deployment logs, which should provide more detailed error messaging.

Check Deployment Logs in Azure Portal:

Go to the Resource Group > Deployments section and inspect the detailed logs for the failed deployment. Look for any specific error messages or failed operations.

Enable Verbose Logging in Your Script:

Add detailed logging to your deployment script to capture API responses and errors from GoDaddy.

Retry the Deployment:

Since this might be a transient issue, retrying the deployment after a short wait can sometimes resolve it.

Test the Script Outside Azure:

Run the script locally or in a test environment to verify that the GoDaddy API calls work as expected.

Use az deployment-scripts CLI for Debugging:

You can inspect the deployment script resource using powershell: az`` deployment-scripts show --name <script-name> --resource-group <rg-name>

Let me know , if you need further assistance.
Siva Nair 345 Reputation points Microsoft External Staff Moderator

2025-08-08T18:28:29.23+00:00

Hi Luke Kolodziej,

Just checking back to see if the above response was helpful, let me know if you have any other questions or queries, happy to help you.
Siva Nair 345 Reputation points Microsoft External Staff Moderator

2025-08-11T16:59:00.51+00:00

Hi Luke Kolodziej,

Just checking back to see if the above response was helpful, let me know if you have any other questions or queries, happy to help you.
Luke Kolodziej 0 Reputation points

2025-08-11T17:44:17.3933333+00:00

For clarification, the error message I posted was from the Deployment Logs in the Azure Portal (Suggestion 1) (Subscription > Deploment Stack > Deployment >> Script). I had already added detailed logging to the script (Suggestion 2) but was not able to find or see any of the output in the portal. I had also retried the deployment several times (Suggestion 3) with the same result.

Suggestion 4 lead me to find the docs for configuring a development environment and I was able to use the Docker method to run the script locally and see the actual error which turned out to be a jq query failure.

Share via

Deployment Script Error "DeploymentScriptOperationFailed"

Your answer