Skip to content

Limits and checklists

Limits rule

Use limits shown by the approved Marketplace plan, Azure subscription quota, deployed resource configuration, and current Elastic version. Do not copy fixed capacity, retention, availability, or timing values from another deployment.

Pre-deployment

  • [ ] Marketplace purchasing and plan are approved.
  • [ ] Subscription, region, quota, policy, and RBAC are confirmed.
  • [ ] Workload and recovery objectives are documented.
  • [ ] Public or private access is approved.
  • [ ] DNS, routing, certificate, and support owners are identified.
  • [ ] Maintenance and license decisions are recorded.

Handover

  • [ ] Azure and service readiness are successful.
  • [ ] Authoritative endpoints and resource IDs are recorded.
  • [ ] DNS, TLS, authentication, and least-privilege access are tested.
  • [ ] Synthetic ingestion and search are successful.
  • [ ] Monitoring, snapshots, and support routes are verified.
  • [ ] No secrets are present in handover records.

Before a change

  • [ ] Scope, owner, risk, validation, and rollback are approved.
  • [ ] Health and capacity are acceptable.
  • [ ] A usable snapshot is verified when required.
  • [ ] Affected users and clients are notified.

Before deletion

  • [ ] Data and recovery approvals are complete.
  • [ ] Ingestion is stopped or redirected.
  • [ ] Required exports and final snapshot are verified.
  • [ ] Dependent DNS, Private Endpoints, identities, and alerts are inventoried.