Skip to content

Delete the application

Deleting the Azure Managed Application removes the managed application and its managed resource group.

Treat deletion as a permanent decommissioning action.

Before deletion

Before deleting the deployment:

  • confirm that the application is no longer required;
  • stop or redirect applications and ingestion sources;
  • identify any Elasticsearch data that must be retained;
  • confirm recovery or retention requirements with iVedha when required;
  • identify customer-owned DNS records and Private Endpoints that will need to be removed;
  • identify application credentials, API keys, and integrations that should be revoked.

For observability deployments, also plan to:

  • unenroll or reassign Elastic Agents;
  • update Fleet policies where required;
  • redirect OpenTelemetry exporters or integrations to another destination.

Preserve required data

If data must be retained after the deployment is deleted, coordinate the retention or recovery requirement with iVedha before deletion.

Elasticsearch snapshots can protect Elasticsearch data, but snapshot retention and access after platform deletion depend on the deployed backup configuration.

Do not delete the platform until required recovery data has been confirmed.

For assistance, see back up and restore.

Delete the Azure Managed Application

In the Azure portal:

  1. Open the deployed Azure Managed Application.
  2. Confirm that you selected the correct deployment.
  3. Select Delete.
  4. Confirm the deletion when prompted.
  5. Monitor the Azure operation until the Managed Application is removed.

Do not manually delete individual resources inside the managed resource group to speed up deletion.

Deleting individual managed resources can leave the deployment in an inconsistent state.

What deletion removes

Deletion of the Managed Application removes the managed Azure resources associated with the deployment.

This includes the managed platform infrastructure deployed inside the managed resource group.

Customer-owned resources outside the managed resource group might not be removed automatically.

Remove customer-owned connectivity

After the managed application has been deleted, remove customer-owned resources that are no longer required.

This can include:

  • Azure Private Endpoints;
  • private DNS records;
  • public DNS records for company-owned domains;
  • firewall or allowlist rules;
  • routing configuration created specifically for the deployment.

Do not remove shared networking or DNS resources used by other applications.

Remove credentials and integrations

Revoke or remove credentials that were created specifically for the deployment.

Examples include:

  • application API keys;
  • local Elastic users that are no longer required;
  • SSO application credentials;
  • integration credentials;
  • automation secrets.

For observability workloads, also remove or update:

  • Elastic Agent policies;
  • enrollment configuration;
  • OpenTelemetry exporters;
  • application telemetry destinations.

Check Marketplace and billing state

After deletion, confirm that the Marketplace subscription or commercial arrangement associated with the deployment is in the expected state.

Deleting Azure resources and changing Marketplace commercial terms are separate concerns.

If you are unsure whether any Marketplace action is still required, contact iVedha.

Need help before deletion

For assistance with decommissioning, data retention, or Marketplace status:

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

Provide the deployment reference and describe the intended decommissioning date.

Do not include passwords, API keys, private keys, or other secrets.

Warning

Do not delete the Managed Application until any required data-retention or recovery plan has been confirmed.

After decommissioning

When deletion, customer-owned resource cleanup, credential revocation, and Marketplace checks are complete, the deployment lifecycle is finished. Return to the documentation home to choose another supported journey.