Skip to content

Deployment issues

Use this guide when an Azure Marketplace deployment fails, remains incomplete, or does not reach managed-platform readiness.

Start with Troubleshooting overview.

Understand the deployment stages

A successful deployment normally progresses through these stages:

  1. Azure Marketplace accepts the deployment.
  2. Azure creates the Managed Application and required resources.
  3. iVedha receives and begins processing the deployment.
  4. Managed platform onboarding and readiness checks run.
  5. You receive the Your deployment is ready notification.

Azure provisioning success does not necessarily mean the managed platform is ready yet.

Marketplace validation fails

If Azure reports an error before deployment starts:

  1. Read the complete validation message.
  2. Confirm the selected:
  3. subscription;
  4. region;
  5. Marketplace plan.
  6. Check whether Marketplace purchases are permitted for the subscription.
  7. Confirm the deploying identity has the required permissions.
  8. Review any Azure Policy or quota error reported by Azure.
  9. Correct the reported issue and run Review + create again.

Common causes include:

  • Marketplace purchasing restrictions;
  • plan availability;
  • insufficient permissions;
  • Azure Policy restrictions;
  • insufficient subscription quota;
  • unsupported region or resource configuration.

Do not grant broad permissions or disable policy simply to bypass the validation error.

Azure resource deployment fails

If Marketplace deployment starts but Azure reports a deployment failure:

  1. Open the Managed Application or application resource group in the Azure portal.
  2. Review the failed deployment operation.
  3. Find the first failed resource operation, not only the final DeploymentFailed message.
  4. Record:
  5. deployment name;
  6. failure time;
  7. Azure correlation ID;
  8. error code;
  9. redacted error message.

Typical Azure-side causes include:

  • Azure Policy denial;
  • insufficient RBAC permissions;
  • role-assignment restrictions;
  • quota;
  • unsupported resource operation;
  • naming or regional restrictions.

Do not manually modify or delete partially deployed managed resources unless instructed by iVedha support.

Marketplace deployment completed but onboarding continues

After Azure Marketplace provisioning completes, you can receive the notification Marketplace deployment completed — onboarding is in progress.

This means the Azure deployment succeeded, but iVedha is still onboarding the deployment and running platform readiness checks.

No action is normally required while onboarding is progressing.

Wait for the Your deployment is ready notification before starting post-deployment configuration.

Deployment does not become ready

If Azure succeeded but you do not receive the ready notification within the expected onboarding period, contact iVedha.

Provide:

  • deployment name;
  • deployment reference from the notification email;
  • approximate deployment time;
  • current Azure deployment state;
  • any relevant redacted error messages.

Do not attempt to repair Kubernetes, Elasticsearch, or other managed resources directly.

Deployment notification was not received

Deployment notifications are sent to each configured delivery address, or to the account address when no separate delivery address is configured.

Check:

  • the configured account and delivery addresses;
  • spam or junk folders;
  • organizational mail filtering.

If a mapped delivery address is configured, check that mailbox. The delivery address receives email but does not grant access to the deployment. Review the support-contact mapping if the configuration is unclear.

If the Azure deployment succeeded but no deployment notification was received, contact iVedha and provide the deployment name and Azure subscription information.

Deployment failed after onboarding started

If you received the initial request received or onboarding in progress notification but later receive an error or the deployment stops progressing, the problem is likely in the managed onboarding process rather than the initial Marketplace deployment.

Use:

  • AI chat: https://copilot.opsflw.io
  • Support portal: https://support.ivedha.com/

Provide the deployment reference from the notification email.

What to include when contacting support

Useful information includes:

  • deployment reference;
  • deployment name;
  • Azure subscription ID;
  • Azure region;
  • approximate start time;
  • Azure correlation ID when available;
  • error code;
  • redacted error message;
  • which deployment notification was received last.

Do not include:

  • passwords;
  • API keys;
  • bootstrap tokens;
  • private keys;
  • certificate private keys;
  • other secrets.

Next step

If the deployment reaches Your deployment is ready but you cannot reach Elasticsearch or Kibana, continue with Connectivity issues.