How should you deploy Foundry infrastructure repeatedly?
Why D is the answer
By using Bicep templates and the Azure CLI
Bicep templates and the Azure CLI deploy the same Foundry infrastructure each time.
In detail
- Bicep templates and the Azure CLI give repeatable deployments.
- Run the same templates through a pipeline.
Use case
An illustrative scenario, not a real incident.
A team creates Foundry resources from Bicep and the Azure CLI, so every environment comes out the same.
See it in different ways
flowchart LR A["Bicep in Git"] --> B["GitHub Actions"] B --> C["Dev workspace"] B --> D["Test workspace"] B --> E["Prod workspace"]
sequenceDiagram participant D as Developer participant G as GitHub participant A as GitHub Actions participant Z as Azure D->>G: Merges a Bicep change G->>A: Starts the workflow A->>Z: Signs in with OpenID Connect A->>Z: Deploys to dev, test and prod
flowchart LR S0["Bicep template"] --> S1["Azure CLI"] --> S2["Foundry resources"]
Key point: Deploy Foundry infrastructure as code.
Why the other options are wrong
- A. By copying a resource's settings into a document
- A document does not deploy anything.
- B. By asking each team to create its own by hand
- Each team doing it by hand drifts too.
- C. By clicking through the portal for each environment
- Clicking through the portal drifts.