Skip to content

Lifecycle states

The Azure Marketplace deployment and the managed platform onboarding process have separate lifecycle stages.

An Azure deployment can complete successfully before the managed Elasticsearch platform is ready for use.

Deployment lifecycle

Stage Customer meaning Customer action
Deployment requested Azure Marketplace accepted the deployment request No action required
Azure provisioning Azure is creating the Managed Application and its resources Monitor the Azure deployment
Marketplace deployment completed Azure provisioning succeeded Wait while iVedha onboarding continues
Onboarding in progress iVedha is configuring the platform and running readiness checks No action required unless an error is reported
Deployment ready Platform readiness checks passed and customer endpoints are available Continue with post-deployment configuration
Deployment failed Azure provisioning or managed onboarding could not complete Review the error and contact support when required
Deleting Azure is removing the Managed Application and managed resources Wait for deletion to complete
Deleted The Managed Application has been removed Complete cleanup of customer-owned resources

Deployment requested

After Azure Marketplace accepts the request, iVedha sends a notification similar to:

Your request for <deployment> has been received

This confirms that the deployment request entered the managed onboarding process.

No customer action is normally required.

Azure provisioning

Azure creates the Managed Application and the resources required by the selected Marketplace plan.

During this stage, Azure can report states such as:

  • Accepted;
  • Running;
  • Succeeded;
  • Failed.

These are Azure resource deployment states.

They do not by themselves indicate that Elasticsearch, Kibana, Fleet, or other managed services are ready.

Marketplace deployment completed

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

At this point:

  • the Azure Managed Application has been created;
  • required Azure infrastructure has been provisioned;
  • iVedha onboarding and platform configuration are still running.

Do not begin endpoint, DNS, certificate, or application configuration yet.

Onboarding in progress

During onboarding, the managed platform performs configuration and readiness work required for the selected deployment.

This can include preparation of:

  • Elasticsearch;
  • Kibana;
  • Fleet and Fleet Server;
  • Elastic Agent;
  • OpenTelemetry components;
  • Logstash when enabled;
  • networking and ingress;
  • platform monitoring.

The exact internal steps can vary by platform version.

Customers do not need to monitor or modify these internal components.

Deployment ready

The authoritative readiness event is the Your deployment is ready notification.

This means managed platform readiness checks have completed successfully.

The notification provides the deployment information required to continue, including available service endpoints.

Depending on the enabled components, these can include:

  • Kibana;
  • Elasticsearch;
  • Fleet;
  • Logstash.

After receiving this notification, continue with Next Steps:

  1. Reset the administrator password.
  2. Configure network access.
  3. Configure DNS.
  4. Configure TLS certificates.
  5. Verify access.

Deployment failed

A deployment can fail during either:

  • Azure provisioning — for example because of policy, permissions, quota, Marketplace eligibility, or another Azure error.
  • Managed onboarding — Azure provisioning succeeds, but platform onboarding cannot complete.

Do not recreate the deployment immediately without understanding the failure.

See Deployment issues for troubleshooting guidance.

Deleting

When the Azure Managed Application is deleted, Azure removes the managed application and its managed resource group.

Do not manually delete individual managed resources while deletion is running.

Deleted

After Azure reports the Managed Application as deleted, the managed deployment is no longer available.

Customer-owned resources outside the managed resource group may still need cleanup, including:

  • Private Endpoints;
  • DNS records;
  • credentials;
  • application integrations;
  • telemetry destinations.

See Delete the application for the complete decommissioning process.

Important distinction

Azure Succeeded does not mean platform ready.

Use the Your deployment is ready notification as the customer-facing readiness signal.

If Azure provisioning succeeds but the ready notification does not arrive, see Deployment issues or Contact support.