Project Resource Limits
AZDO.1011InfoAzure DevOpsResource usage and limitsPreview 3.0
Part of Maester · Azure DevOps · Resource usage and limits · All checks
Invoke-Maester -TestId AZDO.1011Overview
Section titled “Overview”Azure DevOps supports up to 1,000 projects within an organization.
Rationale: Each project consumes metadata, service endpoints, pipelines, and storage. Maintaining a large number of rarely used or abandoned projects can increase management overhead and may impact organization performance or hit the hard limit.
Remediation action
Section titled “Remediation action”Regularly audit your project list and retire, archive, or consolidate projects that are no longer active. Consider using areas/teams within existing projects instead of creating new ones when possible.
Results: Keeping your project count well below the limit prevents service errors and keeps the organization easier to govern.
Related links
Section titled “Related links”Details
Section titled “Details”Every attribute of this check
| Field | Value |
|---|---|
| Test ID | AZDO.1011 |
| Severity | Info |
| Suite | Maester |
| Product | Azure DevOps |
| Feature | Resource usage and limits |
| Area | Engineering systems |
| Resource type | Project |
| MITRE ATT&CK | None |
| PowerShell test | Test-AzdoResourceUsageProject |
| Services | AzureDevOps |
| Learn more | https://learn.microsoft.com/azure/devops/organizations/projects/about-projects?view=azure-devops |