Skip to content

Document ARM Modeling Review lease failures #47318

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Copilot wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Document ARM Modeling Review lease failures #47318

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2ad2594
Initial plan
Copilot Oct 15, 2026
d95cd5d
Document ARM lease review failures
Copilot Oct 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions .github/arm-leases/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,14 @@ All lease files are automatically validated with the following requirements:

## Troubleshooting

### ARM Modeling Review reports a missing or expired lease

If a pull request for a newly detected resource provider fails the **ARM Modeling Review** check with an error that no lease file was found, the lease has expired, or the resource provider does not have a valid ARM lease, treat it as an ARM lease requirement issue rather than a generic validation failure.

- Follow the pull request's **next steps to merge** instructions to resolve the lease requirement.
- Verify that the required lease exists and is valid on public `main`. The check reads leases from public `main`, so a lease file added only in the pull request branch will not satisfy it.
- If the pull request instructions or check output direct you to, contact the **ARM Modeling Review** check owner for help completing the lease resolution process.

If your PR check **"ARM Lease Validation"** is failing, review the error messages in the check output and fix the issues in your `lease.yaml` file. Common causes include:

- **Invalid folder structure**: Ensure the path follows `<orgName>/<rpNamespace>/[<serviceName>]/lease.yaml` with lowercase org name
Expand Down