Share via

Managed App Deployment failing

Pavan Kesamreddy 55 Reputation points
2026-01-20T08:15:52.55+00:00

I am trying to install a managed app from service catalog. I am getting the following error in a deployment script related to the managed app:

<code id='' style='white-space:pre-wrap'><div>Encountered an internal server error. The tracking activity id is '273678d7-baf2-47e0-bef7-0f07f66a5d39', correlation id is '<PII removed>'.</div></code></br> (Code: DeploymentScriptOperationFailed)

Is there any way to see the actual server logs?

Azure Managed Applications
Azure Managed Applications

An Azure service that enables managed service providers, independent software vendors, and enterprise IT teams to deliver turnkey solutions through the Azure Marketplace or service catalog.


1 answer

Sort by: Most helpful
  1. Bharath Y P 7,715 Reputation points Microsoft External Staff Moderator
    2026-01-20T10:38:13.61+00:00

    Hello Pavan Kesamreddy,

    We understand that you are deploying a managed application from the Azure Service Catalog and encountering the error: DeploymentScriptOperationFailed with the message "Encountered an internal server error". This indicates that the deployment script tied to the managed app failed, but the error message is generic and doesn’t expose the actual server-side logs.

    Managed applications are designed so that the publisher controls the underlying resources. As a consumer, you only see what the deployment script outputs. Direct server logs are not exposed for security and isolation reasons. Instead, Azure surfaces deployment diagnostics through resources like Microsoft.Resources/deploymentScripts, activity logs, and linked storage accounts.

    You can check the Deployment Script resource:

    1. Navigate to the Resource Group where the managed app is being deployed.
    2. Look for a resource of type deploymentScripts.
    3. Open it and check:
      • Logs tab > shows execution logs.
      • Outputs tab > shows script outputs.

    This is usually where you’ll see the actual PowerShell or Bash error message that caused the failure. Storage Account Logs (stdout / stderr)

    If the deployment script was configured with a storage account:

    • Open the linked Storage Account > Go to Containers.
    • Look for containers like: azscripts or deployment-script-logs
    • Inside, open files such as: stdout.txt or stderr.txt

    These files contain the raw script output and error messages.

    Deployment Details in Resource Group

    • Open the Resource Group > Go to Deployments.
    • Select the failed deployment.

    Expand Operation details.

    This shows which step or script failed, often with more context.

    Activity Log (Azure Monitor)

    • Go to Monitor > Activity Log.
    • Filter by: Time range, Resource Group or Correlation ID

    Helpful for identifying permission or identity-related issues that may have blocked the script.

    Reference:

    Deploy a service catalog managed application - Azure Managed Applications | Microsoft Learn

    Troubleshoot common Azure deployment errors - Azure Resource Manager | Microsoft Learn

    Hope this helps! If you need any further assistance, please do let us know, thanks.

    0 comments No comments

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.