Deployment fields
The exact fields and allowed values depend on the offer and plan. This reference explains common categories; it does not override the live deployment form.
| Category | Purpose | Evidence to prepare |
|---|---|---|
| Subscription and region | Selects the Azure ownership and location | Approved subscription, policy, quota, and region |
| Application identity | Names and tags the managed application | Naming standard, environment, and ownership tags |
| Workload profile | Describes Search or Observability intent | Ingestion, search, retention, and user demand |
| Capacity and topology | Selects available resource layout | Capacity estimate and availability requirement |
| Public access | Enables approved public endpoints | Exposure approval, DNS owner, domain, and restrictions |
| Private access | Enables private service connectivity | Client VNet, subnet, routes, DNS, and certificate owner |
| Domain settings | Defines customer or managed hostnames | Approved DNS zone and certificate names |
| Maintenance | Records a controlled change schedule | Occurrence, weekday, start time, time zone, duration |
| License | Selects or supplies supported licensing | Entitlement owner and approved license material |
| Identity or OIDC | Configures supported authentication | Tenant, application, redirect, claims, and owners |
| Contacts | Identifies deployment or support users | Approved business email addresses |
| Advanced settings | Applies supported expert configuration | Product-owner approval and documented validation |
Never place a password, private key, access token, or connection string in tags, contacts, advanced YAML, or another field not explicitly designed for a secret.