AZ Azure Infrastructure & Service Catalogue
Add only the Azure services a customer needs, then capture the Bicep-ready requirement contract for each one.
Customer & deployment basics
Used for the branch and PR title.
Feeds resource naming and tagging.
Creates the named GitHub folder containing main.bicep, main.bicepparam and modules/.
Azure services
Every service can be given an explicit Azure resource name and uses the same enterprise discovery pattern: naming, region, SKU/capacity, networking, identity, resilience, backup, monitoring, governance and dependencies. Future PRs use the same segregated main/modules structure as the AI Agent stack.
0 services added
No services added yet. Click + Add Azure service to start the customer’s infrastructure package.
Package readiness
Add Azure services above to see live readiness checks here.
Live architecture diagram
Generated named infrastructure package
Customer decisions become a named main.bicep + main.bicepparam + modules/ GitHub package. Validated Resource Group, Managed Identity, VNet and Storage selections emit real conditional Bicep; submission opens a review PR and never deploys Azure.