Storage Usage Limit
AZDO.1029 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.1029Overview
Section titled “Overview”Azure Artifacts provides 2 GiB of free storage for each organization. Once your organization reaches the maximum storage limit, you will not be able to publish new artifacts. To continue, you can either delete some of your existing artifacts or increase your storage limit.
Rationale: The storage limit should not be reached; hitting it blocks artifact publication.
Remediation action
Section titled “Remediation action”- Configure retention policies
- Set up billing
- Increase Artifacts storage limit
- Set up billing for your organization.
- Sign in to your Azure DevOps organization, select Organization settings > Billing, and select No limit, pay for what you use from the Usage limit dropdown.
- Select Save when you are done.
Related links
Section titled “Related links”Details
Section titled “Details”Every attribute of this check
| Field | Value |
|---|---|
| Test ID | AZDO.1029 |
| 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-AzdoOrganizationStorageUsage |
| Services | AzureDevOps |
| Learn more | https://learn.microsoft.com/azure/devops/artifacts/reference/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