Pre-flight · one-time per tenant
Confirm tenant-scoped prerequisites
Before you create your first site, four things have to exist somewhere in your tenant. Launchpad doesn't provision them — it confirms they're there and tells you where to go if they aren't.
Pre-flight checks
stub for demo0 of 6 confirmedArc-connected cluster with OIDC + workload identity
AIO runs on top of an Arc-connected Kubernetes cluster with OIDC issuer + workload identity enabled. The cluster itself has to exist before any deploy runs.
Scale Kit repo in your GitHub org
Launchpad reads and writes manifests against your copy of the IoT Operations Scale Kit (created from the template repo, or forked). Releases, sites, and secrets all live in this repo.
Storage account (HNS) for Schema Registry
An HNS-enabled storage account backs the Schema Registry. Required for every AIO deployment regardless of mode.
Key Vault (RBAC mode)
Backs sync-secrets as the central source of truth. One Key Vault usually serves the whole tenant — if one already exists, point at it. If this is your first federated tenancy, create one now.
UAMI · components
Federated managed identity used by AIO core components (broker, dataflow runtime). Usually created per tenancy.
UAMI · secrets
Federated managed identity used by the secret-sync controller to read site secrets from the Key Vault above. Usually created per tenancy.