Monitor deployment
After selecting Create in Azure Marketplace, monitor both the Azure deployment and the iVedha deployment notifications.
A successful Azure deployment does not by itself mean that Elasticsearch, Kibana, Fleet, or other managed services are ready for customer use.
Deployment stages
The customer-visible deployment lifecycle has three main milestones.
| Milestone | What it means | Customer action |
|---|---|---|
| Request received | Azure Marketplace accepted the deployment and iVedha received the onboarding request | No action required |
| Marketplace deployment completed | Azure provisioning succeeded and managed-platform onboarding continues | Wait for iVedha readiness checks to complete |
| Your deployment is ready | Managed-platform readiness checks passed and deployment details are available | Begin the documented Next Steps |
Do not begin endpoint, DNS, certificate, or application configuration until you receive Your deployment is ready.
Deployment notifications
Deployment notifications are sent to each configured delivery address, or to the account address when no separate delivery address is configured. See Support contacts.
The expected sequence is:
- Your request for
<deployment>has been received - Marketplace deployment completed — onboarding is in progress
- Your deployment is ready
The first notification confirms that the request entered the managed onboarding process.
The second confirms that Azure provisioning completed successfully, but iVedha is still configuring the platform and running readiness checks.
The third notification is the authoritative customer-facing readiness handoff.
Make sure the support email address entered during deployment is monitored and can receive these messages.
Monitor Azure provisioning
Use the Azure portal to monitor the Managed Application deployment while Azure resources are being created.
Azure can report states such as:
- Accepted;
- Running;
- Succeeded;
- Failed.
If Azure reports Failed, review the deployment operations and identify the first failed resource operation.
Common Azure-side causes include:
- insufficient permissions;
- Azure Policy restrictions;
- subscription quota;
- Marketplace eligibility or purchasing restrictions;
- unsupported resource configuration.
See Deployment issues for troubleshooting guidance.
Understand Azure success versus platform readiness
There are two separate status layers.
Azure provisioning
Azure creates the Managed Application and required infrastructure.
Azure Succeeded means that the Azure deployment completed. It does not mean that the managed Elasticsearch platform is ready for customer use.
Managed-platform readiness
After Azure provisioning succeeds, iVedha continues onboarding the deployment and running platform readiness checks.
Customers do not need to inspect or modify internal Kubernetes, Elasticsearch, or other managed components during this stage.
The authoritative readiness signal is the Your deployment is ready notification.
When the deployment is ready
The Your deployment is ready notification provides the deployment reference and the service information required to continue.
Depending on the enabled components, it can include endpoints for:
- Elasticsearch;
- Kibana;
- Fleet;
- Logstash.
After receiving the notification, continue to Review deployment details, then complete the Next steps.
If the deployment does not complete
Use Deployment issues if:
- Azure reports Failed;
- Azure provisioning succeeds but onboarding does not progress;
- the Your deployment is ready notification does not arrive within the expected onboarding period;
- you receive an onboarding failure notification.
When contacting iVedha, provide the deployment reference when available and any relevant Azure correlation ID or redacted error message.
Do not modify resources in the managed resource group in an attempt to repair the deployment.