From 2ad25942481071697295576dd0bdd6e7218bd567 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 15 Oct 2026 05:51:36 +0000 Subject: [PATCH 1/2] Initial plan From d95cd5d48b23396922bc860ff7f1cfb35914383e Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 15 Oct 2026 05:54:34 +0000 Subject: [PATCH 2/2] Document ARM lease review failures Co-authored-by: jianingwang123 <141212663+jianingwang123@users.noreply.github.com> --- .github/arm-leases/README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.github/arm-leases/README.md b/.github/arm-leases/README.md index 8d60096ea9b9..a43bb90dee06 100644 --- a/.github/arm-leases/README.md +++ b/.github/arm-leases/README.md @@ -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 `//[]/lease.yaml` with lowercase org name