Skip to main content

Azure services

Services map

Profiles enable only the components a project needs. Do not infer that every service below exists in every environment.

ServiceRepository use
App ServiceHosts containerized Mastra runtime, ingestion web API, Admin UI, Widget, Handbook App, Grafana, documentation, and diagnostics HTTP components selected by a profile.
Azure FunctionsHosts the main Function App, ingestion processor blueprints, and health aggregator timers.
Azure Container RegistryStores immutable and environment-tagged images produced by promotion/build workflows.
API ManagementRoutes external traffic, applies caller auth/policy, publishes backend prefixes, and supports deployment smoke/slot validation.
Azure SQLDurable operational, agent-profile/model, domain, ingestion, memory, and observability data defined by db/sqlproj/**.
Storage AccountBlob/File/Queue/Table backing used by application and Functions workloads; exact role grants differ by component.
Key VaultEnvironment secrets and deployment/runtime references. Managed identity is preferred over copying secret values.
Azure AI servicesModel deployments used by runtime agents and workbenches; deployment metadata is reconciled with Core model tables.
Azure AI Content SafetyTenant-hosted moderation used by TAP and other selected flows.
Document IntelligenceDocument extraction used by ingestion/Handbook flows.
Azure AI SearchOptional retrieval index, notably used by Handbook profiles.
Application Insights + Log AnalyticsService telemetry, diagnostics, and operational queries.
Static Web AppsOptional hosting surface selected by documentation/static-site parameters.

Component selection begins in azure_template/profiles/*.json; runtime and gateway details come from environments/**/*.yml and .github/config/projects/*.yml.