Skip to main content
Version: 3.0.0-preview

AZDO.1036 - (Tenant) Restrict Personal Access Token full scope.

Overviewโ€‹

Restrict creation of full-scoped Personal Access Tokens (PATs) should be enabled.

Prerequisitesโ€‹

  • Your organization must be linked to a Microsoft Entra tenant.
  • You must be an Azure DevOps Administrator to configure tenant policies.

Rationaleโ€‹

Restricting full-scoped Personal Access Token (PAT) creation enforces least privilege, reduces the risk of credential exposure, and limits the blast radius if a token is compromised. It also helps meet compliance requirements and prevents accidental or malicious use of overly permissive tokens.

Remediation actionโ€‹

Enable the tenant policy to restrict creation of full-scoped personal access tokens.

  1. Sign in to your organization (https://dev.azure.com/{yourorganization}).
  2. Select Organization settings (gear icon).
  3. Select Microsoft Entra, find the "Restrict creation of full-scoped personal access tokens" policy.
  4. Move the toggle to On.

Allowlist and exceptionsโ€‹

  • Use Microsoft Entra groups for allowlists; adding named users can create identity residency concerns.
  • Users or groups on the allowlist are exempt from the restriction and can create PATs of any scope.

Existing PATs:

Existing PATs remain valid until their configured expiration date and are not retroactively restricted.

Results:

When enabled, new personal access tokens (PATs) must have limited, defined scopes. Creation of full-scope PATs (tokens that grant all accessible scopes) will be blocked for users who are not on the allowlist.

Test Metadataโ€‹

FieldValue
Test IDAZDO.1036
SeverityHigh
SuiteMaester
CategoryAzure DevOps
PowerShell testTest-AzdoRestrictFullScopePersonalAccessToken
ServicesAzureDevOps
Learn morehttps://learn.microsoft.com/azure/devops/organizations/accounts/manage-pats-with-policies-for-administrators?view=azure-devops#restrict-creation-of-full-scoped-pats-tenant-policy
TagsAZDO, AZDO.1036

Sourceโ€‹