Skip to content

Planning overview

Before opening Azure Marketplace, make only the decisions required to create the managed application.

Most platform configuration can be completed or adjusted after deployment.

Decisions to make

Decision What to choose
Stack version Current version approved for new managed deployments
Azure environment Azure subscription and region
Workload Search or Observability
Capacity Initial Small, Medium, or Large profile available in the Marketplace plan
Public access Enable or disable public access
DNS domain Platform-provided DNS domain or company-owned DNS domain
Maintenance Preferred maintenance window and time zone
Support Operational and support contacts

See available stack versions to confirm the current target and understand how managed version selection works.

Choose the Azure environment

Confirm the Azure subscription and region where the platform will be deployed.

Before deployment, make sure the subscription can purchase the Marketplace offer and has the required permissions, policy allowances, and quota.

See Azure and Marketplace prerequisites.

Choose the workload

Choose the primary workload for the deployment:

  • Search — application, document, vector, or knowledge search.
  • Observability — logs, metrics, traces, and operational data.

The workload selection determines which platform profiles and topology options are available.

Choose the initial capacity

Select the initial capacity available in the approved Marketplace plan:

  • Small
  • Medium
  • Large

The initial capacity is a starting point. Platform health and actual usage can be reviewed after deployment, and supported capacity changes can be made when required.

See choose capacity and topology.

Choose access and DNS domain options

Before deployment, decide whether the platform will expose public endpoints and which DNS domain will be used for Elasticsearch and Kibana.

Public access

Choose whether to enable public access.

  • Enabled — Elasticsearch and Kibana can be reached through public HTTPS endpoints.
  • Disabled — access must be completed through the supported private connectivity workflow after deployment.

Private access can require a customer-managed Azure Private Endpoint, network routing, and private DNS configuration after deployment.

See plan connectivity.

DNS domain

Choose one of the supported DNS domain options:

  • Platform-provided DNS domain — use the default domain and hostnames provided by the managed platform.
  • Company-owned DNS domain — use a domain or subdomain owned by your organization.

If you choose a company-owned DNS domain, confirm before deployment that the appropriate DNS owner can create the required records.

The platform publishes the authoritative endpoint and DNS information after deployment. Do not create DNS records based on assumed resource names or hostnames.

DNS and certificate configuration is completed under Next Steps.

Choose a maintenance window

Select a preferred maintenance window and time zone.

The maintenance window is used for supported platform maintenance and lifecycle operations.

Detailed maintenance management is covered under Manage maintenance.

Provide support contacts

Provide the contacts required for deployment and ongoing service communication.

At minimum, identify:

  • service or application owner;
  • technical contact;
  • support or escalation contact.

Use organization-approved contact information.

Ready to deploy

You are ready to deploy when:

  • the Azure subscription and region are approved;
  • the current stack version is compatible with the planned clients and integrations;
  • Search or Observability is selected;
  • an initial capacity is selected;
  • public access is enabled or disabled;
  • the platform-provided or company-owned DNS domain option is selected;
  • the maintenance window is agreed;
  • support contacts are available.

Use the deployment checklist for the final review.

Then continue to Deploy from Azure Marketplace.