Skip to content

Deployment planning

Complete this worksheet before starting the Marketplace deployment. Use values approved by the owning Azure teams; do not invent or reconstruct them.

Application and ownership

  • Azure subscription and tenant:
  • Application resource group:
  • Azure region:
  • Environment name and classification:
  • Billing and application owner:
  • Primary technical contact:
  • Security and network contacts:

Workload

  • Primary use case: search, observability, analytics, or mixed:
  • Expected daily ingestion:
  • Expected searchable data:
  • Retention objective:
  • Availability objective:
  • Recovery point and recovery time objectives:
  • Expected concurrent users and query pattern:

Use these inputs to select only the profiles and options shown in the approved offer. Do not interpret a profile label as a capacity guarantee; review its displayed resource definition.

Connectivity

  • Access model: public or private:
  • Client networks:
  • Client VNet and Private Endpoint subnet:
  • Routing or peering owner:
  • DNS authority:
  • Private DNS or conditional-forwarding owner:
  • Approved service hostnames:
  • Certificate authority and renewal owner:

Security and operations

  • Elasticsearch administrators:
  • User and role approval owner:
  • Single sign-on requirement:
  • License source and owner:
  • Maintenance window and time zone:
  • Snapshot and recovery-test owner:
  • Customer workload monitoring and support-evidence owner:
  • Decommissioning approver:

Readiness decision

Proceed only when Marketplace access, quota, policy, networking, identity, and ownership are confirmed. Resolve unknown deployment-specific values with the owning team or iVedha support rather than copying values from another environment.