Azure
Azure is a first-class provider slug in the integration registry. The current product stores credentials, validates required fields, and exposes them to generic project and agent connectors.
Purpose
Configure Azure access in ActsAsGeek through the authenticated integration routes, then use the project monitoring, secret storage, and usage-ingestion surfaces that already exist in the product.
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 the integrations settings surface to attach the credential to a project or environment.
3
Store environment-specific secrets with /api/projects/[projectId]/env-secrets when the target workload needs additional configuration.
API & contracts
| Field | Type | Description |
|---|---|---|
| azure | oauth2 · api_key | Provider slug accepted by the integration registry. |
- The verifier requires UUID-formatted `tenant_id` and `client_id` fields plus `client_secret`.
- Project 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.
- Project binding fails when the selected credential is not in `connected` status.
Partial
Credential storage, verification, and connector binding are implemented. Azure-specific resource fetching and webhook handling are not implemented in the current codebase.