Work Items Tags Limits
AZDO.1012 is in Maester 3.0.0-preview and not in the stable 2.3.0 release yet. It will be in the next stable release. To use it now, install the preview:
Install-Module Maester -AllowPrerelease -ForceHow to get the preview, and go backUse the preview in GitHub Actions
Part of Maester · Azure DevOps · Resource usage and limits · All checks
Invoke-Maester -TestId AZDO.1012Overview
Section titled “Overview”Azure DevOps supports up to 150,000 tag definitions per organization or collection.
Rationale: Tags are useful for categorizing and querying work items, but an excessive number of unique tags can degrade performance and make management difficult. Hitting the limit may prevent users from creating new tags and could cause UI slowdowns.
Remediation action
Section titled “Remediation action”Regularly review your tag inventory and delete unused or obsolete tags. Consider standardizing on a controlled vocabulary or using area/iteration paths when appropriate.
Results: Keeping the tag count below the limit ensures responsive work item searches and avoids hitting a hard cap that would block new tags.
Related links
Section titled “Related links”Details
Section titled “Details”Every attribute of this check
| Field | Value |
|---|---|
| Test ID | AZDO.1012 |
| Severity | Info |
| Suite | Maester |
| Product | Azure DevOps |
| Feature | Resource usage and limits |
| Area | Engineering systems |
| Resource type | Tenant |
| MITRE ATT&CK | None |
| PowerShell test | Test-AzdoResourceUsageWorkItemTag |
| Services | AzureDevOps |
| Learn more | https://learn.microsoft.com/azure/devops/organizations/settings/work/object-limits?view=azure-devops |
Source
Section titled “Source”About this check
- Severity
- Info
- Product
- Azure DevOps
- Feature
- Resource usage and limits
- Area
- Engineering systems
- Suite
- Maester