/api/v1/organization:activate
Creates an Organization for the signed-in Microsoft Entra directory, makes the signed-in account its first Owner, and starts its trial. An existing active member receives the Organization with HTTP 200. Another account in an already activated directory receives HTTP 409 and needs an invitation from an Owner. Requires a delegated GV.Access token for a work or school account; no Organization role is required.
Operation ID · activate_organization
Request example
Authentication and access
- Required role: GV.Access
- Data classification: metadata
- Side effects: configurationWrite
- Microsoft Entra delegated user token
Request body
Requiredapplication/json
Schema V1OrganizationActivateobject
Properties
name— Required
string
minimum length: 1 · maximum length: 255
Additional properties are not allowed.
Responses
This guide summarizes response status codes and headers. Retrieve the deployed, authenticated OpenAPI document for the exact response body schemas and examples. The API also provides an authenticated Swagger UI; opening it in a browser does not automatically attach a bearer token. Error responses useapplication/problem+json. The response’s stable code and type map to the error-code reference.
200
The directory was already activated; the caller is an active member.Headers
- ETag:
string - Location:
string
201
Organization activated with the caller as its first Owner.Headers
- ETag:
string - Location:
string
401
A valid Microsoft Entra bearer token is required.403
The authenticated principal does not have the required role.409
The operation conflicts with current resource or Azure state.422
The request is syntactically valid but semantically invalid.429
The bounded application request rate was exceeded.Headers
- Retry-After: Seconds to wait before retrying.
integerminimum: 1
503
A required dependency is temporarily unavailable.Headers
- Retry-After: Seconds to wait before retrying.
integerminimum: 1