Platform Overview¶

Welcome. This platform offers self-service Azure and Entra ID APIs. After the cluster is bootstrapped, teams describe what they need in YAML, commit it, and Crossplane creates and keeps the resources in sync.

Day-to-day provisioning happens through Git rather than direct portal or az changes.

What you can create¶

Compose Azure infrastructure from building blocks such as virtual networks, automatically allocated IP space, and Linux or Windows virtual machines. Run containerized workloads with Container Apps, or use managed PostgreSQL and App Service APIs. For a more complete starting point, XWebApplication provisions a resource group, database, App Service, and Key Vault-backed database credential, with optional custom-domain and Entra ID sign-in support.

The platform also includes Entra ID APIs for security groups, enterprise applications, and access packages.

Browse the full composition reference for every available API, its fields, prerequisites, and examples.

How it fits together¶

A typical team starts with a resource group, adds networking, and then places workloads inside it:

flowchart LR
    rg["XResourceGroup"] --> nm["XNetworkManager"]
    nm --> ipam["XNetworkManagerIPAMPool"]
    ipam --> vnet["XVirtualNetwork"]
    rg --> vnet
    vnet --> vm["XVirtualMachine"]
    rg --> vm

Most Azure compositions reference prerequisites by logical name, not by Azure resource ID, so teams do not need to copy long identifiers between manifests. The reference pages describe any API-specific references.

Getting started¶

1. Create your team namespace under teams/.
2. Choose an API from the list above and follow its reference page, including any prerequisites and example manifest.
3. Commit and push. Flux applies it, and Crossplane does the rest.