Bicep foundation overview
The AI Landing Zone Bicep foundation is maintained in
Azure/agent-landing-zone under infra/bicep/.
It is repository-owned source, reviewed and released with Agent Landing Zone,
alongside application composition, service configuration and deployment hooks.
Run the lifecycle from the Agent Landing Zone repository root, not infra/.
See the AI Landing Zone architecture for the platform design context.
Deployment modes
The network design is distinct from the Agent application's orchestrator topology.
deploymentMode records intent; explicit flags and resource IDs determine the
actual resources, routing and reuse.
For production or sensitive data, set NETWORK_ISOLATION=true explicitly,
whether you manage a standalone network or use an existing hub. The template
currently defaults to false, leaving service endpoints public. Reserve that
option for approved, short-lived evaluations without sensitive data.
| Foundation shape | Intent | Reference |
|---|---|---|
| Self-contained | standalone; use NETWORK_ISOLATION=true for the recommended private network |
Standalone network |
| Existing hub integration | ailz-integrated; explicit private networking, hub routing, peering, DNS and shared-service inputs |
Hub-and-spoke network |
Neither preset automatically supplies an operational hub, DNS resolver or connected deployment host.
What gets deployed
Enabled parameters select Foundry/model services, workload data services, container runtimes, configuration/secrets, observability, network resources and optional add-ons. Service-specific conditions and existing-resource inputs determine which are created, reused or omitted.
Infrastructure-only provisioning can leave selected Container Apps running placeholder images; these are not the deployed Agent Application. Foundry Agent Service backing resources are distinct from workload data stores. Review the resource inventory and cost scenarios for foundation scope and the parameter reference for supported inputs. Do not infer the selected application footprint from native Bicep defaults alone.
Access and validation
Managed identities and scoped role assignments provide service-to-service access; Permissions describes the default Agent layout's Foundry-hosted runtime, Container Apps frontend and separate deployment/caller grants. Other application definitions and infrastructure-only selections can produce different assignments.
The preprovision hook checks inputs, BYO resource references, network constraints and regional readiness. A passing check is not proof of regional capacity, private DNS resolution, data-plane authorization or application readiness. Resolve findings instead of skipping the checks.
Use the deployment guides
- Deploy infrastructure only — provision the incorporated foundation without application image deployment.
- Deploy the full stack — deploy the Agent foundation and selected application.
For implementation details, see Bicep deployment considerations, parameterization and Application Gateway ingress.