Deployment options

The exact fields and available values depend on the selected Marketplace plan.

Use this page to understand the main deployment options. The Azure Marketplace form is authoritative for the options available to your deployment.

Option	What it controls	What to choose	Can be changed later?
Subscription	Azure subscription where the managed application is deployed and billed	Select the target subscription	No — redeployment is required to move to another subscription
Resource group	Resource group containing the Azure Managed Application resource	Select or create the application resource group	No — treat as a deployment setting
Region	Azure region where the platform is deployed	Select a supported region	No — redeployment is required to move regions
Application name	Customer-visible name of the Managed Application	Use your organization's naming standard	Treat as a deployment setting
Workload	Primary platform use case	Search or Observability	Depends on supported iVedha workflows
Capacity	Initial platform capacity	Small, Medium, or Large	Yes, through supported iVedha capacity-change workflows
Topology	Elasticsearch node-role and data-tier layout	Select one of the topologies available for the workload and plan	Depends on supported iVedha workflows
Machine learning	Optional ML or inference capacity	Enable only when required and available	Depends on the selected plan and supported iVedha workflows
Public access	Whether public HTTPS endpoints are enabled	Enable or disable	Depends on supported iVedha network workflows
DNS domain	Domain used for Elasticsearch and Kibana service hostnames	Platform-provided DNS domain or company-owned DNS domain	Changing later can require DNS and certificate changes
Maintenance window	Preferred time for supported maintenance	Select the day, time, time zone, and other options shown by the form	Yes, through the supported iVedha maintenance workflow
Elastic license	Elastic license or entitlement used by the deployment	Follow the license option provided by the selected plan	Yes, through the supported license-management workflow
Support contacts	Contacts used for deployment notifications, service communication, and support	Enter monitored organization contacts	Yes, through supported iVedha configuration workflows when available

Workload

Choose the primary platform use case:

Search
Observability

The workload determines which capacity and topology options are available.

See choose capacity and topology.

Capacity and topology

Choose an initial capacity:

Small
Medium
Large

Then select one of the topology options available for the selected workload and Marketplace plan.

The initial capacity can be reviewed after deployment based on actual platform usage.

Public access

Choose whether the platform exposes supported public HTTPS endpoints.

Enabled — public access is available after deployment.
Disabled — configure private connectivity after deployment.

Private Endpoint, routing, DNS, and certificate configuration are completed under Next Steps.

DNS domain

Choose one of the supported DNS domain options:

Platform-provided DNS domain
Company-owned DNS domain

If you select a company-owned DNS domain, enter the domain or subdomain required by the Marketplace form.

The platform publishes the authoritative DNS targets after deployment.

Maintenance window

Select the maintenance options exposed by the Marketplace form.

Depending on the plan, these can include:

occurrence or frequency;
day;
start time;
time zone;
duration.

The maintenance window can later be managed through the supported iVedha maintenance workflow.

Support contacts

Enter the operational and support contact information requested by the Marketplace form. Each item can use either form:

account@example.com
account@example.com|delivery@example.com

The account address on the left is the identity that can access and manage the deployment through supported iVedha workflows. The optional delivery address on the right receives one-time passwords and service communication. A delivery address does not grant access to the deployment.

Separate multiple items with commas or semicolons. You can mix delimiters and add whitespace around items or the | separator. The value is stored in a stable comma-separated form. For example:

admin@example.com; operator@example.com | alerts@example.net,
legacy@example.org

is stored in canonical form as:

admin@example.com,operator@example.com|alerts@example.net,legacy@example.org

The first and third items are legacy entries: their account addresses also receive email. The mapped second item authorizes operator@example.com, but sends its one-time passwords and service communication to alerts@example.net.

Account matching is exact and case-insensitive. An address authorizes access only when it matches a complete account address; matching a delivery address or part of another address is denied.

The configuration is rejected when it contains:

empty items, including leading, trailing, or repeated delimiters;
a missing or invalid account or delivery address;
an item containing more than one | separator;
multiple items with the same account address, including case-only differences.

Different accounts can use the same delivery address. Broadcast service communication is sent only once to each delivery recipient, using case-insensitive recipient matching.

The configured delivery recipients are used for deployment lifecycle notifications, including:

deployment request received;
Marketplace deployment completed and onboarding in progress;
Your deployment is ready.

Use a monitored organization email address.

Never enter passwords, tokens, private keys, or other secrets in contact or free-text fields.

Additional options

Some Marketplace plans can expose additional settings.

If an option is not described here:

review the description in the Marketplace form;
confirm what the option controls before changing the default;
contact support if the effect of the setting is unclear.

For the deployment procedure, see Deploy from Azure Marketplace.