Follow deployment status

Check the managed application and its Azure deployment operations while the platform completes provisioning and readiness checks.

Customer-visible lifecycle

State	Meaning	Your action
Accepted	Azure accepted the create request	Wait and monitor deployment operations
Succeeded	Azure completed the resource deployment	Continue waiting until service readiness is confirmed
Failed	Azure or a downstream readiness step failed	Preserve evidence and follow deployment troubleshooting
Deleting	Azure accepted deletion	Do not recreate resources with the same identity
Deleted	The application and managed resource group are gone	Confirm required records and data-retention actions

Azure resource deployment success and application readiness are separate milestones. Elasticsearch, Kibana, networking, certificates, and managed automation can require additional reconciliation after ARM reports success.

Azure resource success is one gate in the managed-platform lifecycle, not the final readiness signal.

Readiness gates

Gate	Evidence	Complete when
Marketplace accepted	Azure create request	Azure created a deployment record
ARM succeeded	Resource-group deployment	All required ARM operations succeeded
Managed reconciliation complete	Health and Sync Status	The managed application reports the desired state
Service ready	Elasticsearch and Kibana health	Customer-facing services report healthy
Endpoints published	Deployment outputs or properties	Authoritative URLs and identifiers are present
Customer connectivity ready	Client-side checks	Network, DNS, TLS, and authentication work
Handover complete	Recorded validation	Owners accept access, monitoring, support, and recovery

Monitor progress

1. In the Azure portal, open Managed applications.
2. Select the application and review its provisioning state.
3. Open the application resource group and review Deployments.
4. If a deployment is active, wait rather than starting a duplicate.
5. When Azure reports success, use the managed application view or approved deployment details to confirm endpoints and platform health.
6. Record the first time at which the application is ready for customer use.

When to escalate

Escalate when:

• Azure reports Failed;
• progress stops and no deployment operation is active;
• the managed application is successful but no authoritative endpoints appear;
• the service remains unavailable after the documented readiness process.

Include the safe evidence listed in troubleshoot deployment problems. Do not include tokens, passwords, private keys, or unredacted deployment parameter values.