Share via

Deployment Script Error "DeploymentScriptOperationFailed"

Luke Kolodziej 20 Reputation points
2025-08-07T15:49:45.9633333+00:00

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.

Azure App Service
Azure App Service

Azure App Service is a service used to create and deploy scalable, mission-critical web apps.


Answer accepted by question author

  1. Siva Nair 835 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.

    1. 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.
    2. Enable Verbose Logging in Your Script:
      • Add detailed logging to your deployment script to capture API responses and errors from GoDaddy.
    3. Retry the Deployment:
      • Since this might be a transient issue, retrying the deployment after a short wait can sometimes resolve it.
    4. Test the Script Outside Azure:
      • Run the script locally or in a test environment to verify that the GoDaddy API calls work as expected.
    5. 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.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

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