Skip to content
Cloud Governance Tools

Disable service account key creation

Disable service account key creation is a Google Cloud guardrail written in organization Policy Service. Stops users from creating new external service account keys and Cloud Storage HMAC keys in the scope where it is enforced. No documented way to test it before enforcement was found on 10 Nov 2026.

More identity and privilege guardrails ยท About Organization Policy Service

constraints/iam.disableServiceAccountKeyCreation
This boolean constraint, when enforced, disables the creation of service account external keys and Cloud Storage HMAC keys.
By default, service account external keys can be created by users based on their Cloud IAM roles and permissions.
This constraint is automatically provisioned as part of Google Cloud security baseline .
For more information, see Disable service account key creation .
Blocks
Stops users from creating new external service account keys and Cloud Storage HMAC keys in the scope where it is enforced. (legacy managed constraint, boolean.)
Breaks
Google documents that user-managed credentials cannot be created for service accounts in affected projects, so tools or workloads that depend on newly created keys cannot get them. (source)
Test before applying
As for every Organization Policy Service guardrail: how to test before enforcing
Mechanism
Organization Policy Service (managed and legacy constraints): Resources in the organization, folder or project where the policy is set and its descendants; Google says application of new policies is usually not retroactive.
Taken from
provider documentation, provider documentation

What the source says

"This boolean constraint, when enforced, disables the creation of service account external keys and Cloud Storage HMAC keys." (read 10 Nov 2026).

On what it breaks: "When this constraint is set, user-managed credentials cannot be created for service accounts in projects affected by the constraint."

Sources

  1. Disable service account key creation, read 10 Nov 2026
  2. What it breaks, read 10 Nov 2026
  3. How to test it first, read 10 Nov 2026

Last reviewed 16 Nov 2026.