Azure
The integration registry includes Azure. The product stores credentials, checks required fields, and makes them available to generic Environment and agent connectors.
Purpose
Store Azure credentials and bind them to an Environment. Live provider verification, resource retrieval, and cloud actions are unavailable.
Prerequisites
- A signed-in Supabase session.
- A CSRF token for POST and PATCH requests.
- Azure tenant_id, client_id, and client_secret values for the current UI flow.
Setup
1
Create the credential with POST /api/integrations using provider `azure`.
2
Use Integrations settings to attach the credential to an Environment.
3
Store secrets for this Environment with /api/projects/[projectId]/env-secrets when the workload needs more configuration.
API & contracts
| Field | Type | Description |
|---|---|---|
| azure | api_key | Provider slug accepted by the integration registry. |
- The verifier requires UUID-formatted `tenant_id` and `client_id` fields plus `client_secret`.
- A connected status records saved credentials. It does not prove provider access.
- Environment connector bindings accept the `azure` connector type.
- The current agentic connector registry uses a generic API-key connector for Azure rather than an Azure-specific fetch layer.
Failure modes
- POST /api/integrations returns 400 when required Azure fields are missing or malformed.
- Mutation routes return 401 without a session and 403 when the CSRF token is missing.
- Environment binding fails when the selected credential is not in `connected` status.
Partial
The product stores credentials, validates fields, and binds Connectors. Field validation does not contact the provider or confirm permissions. Azure-specific resource fetching and webhook handling are not implemented in the current codebase.