Method: services.tenancyUnits.applyProjectConfig

Apply a configuration to an existing tenant project. This project must exist in an active state and have the original owner account. The caller must have permission to add a project to the given tenancy unit. The configuration is applied, but any existing settings on the project aren't modified. Specified policy bindings are applied. Existing bindings aren't modified. Specified services are activated. No service is deactivated. If specified, new billing configuration is applied. Omit a billing configuration to keep the existing one. A service account in the project is created if previously non existed. Specified labels will be appended to tenant project, note that the value of existing label key will be updated if the same label key is requested. The specified folder is ignored, as moving a tenant project to a different folder isn't supported. The operation fails if any of the steps fail, but no rollback of already applied configuration changes is attempted. Operation<response: Empty>.

HTTP request


The URL uses gRPC Transcoding syntax.

Path parameters



Name of the tenancy unit. Such as 'services/'.

Authorization requires the following Google IAM permission on the specified resource name:

  • serviceconsumermanagement.tenancyu.addResource

Request body

The request body contains data with the following structure:

JSON representation
  "tag": string,
  "projectConfig": {
    object (TenantProjectConfig)


Tag of the project. Must be less than 128 characters. Required.


object (TenantProjectConfig)

Configuration that should be applied to the existing tenant project.

Response body

If successful, the response body contains an instance of Operation.

Authorization Scopes

Requires the following OAuth scope:


For more information, see the Authentication Overview.

Try it!