microsoft / microsoft/finops-toolkit

Azure Lighthouse related issue - when running for two delated subscriptions with same Tenant - it only picks up one

Open
#2,014 8 comments 0 reactions 1 assignee View on GitHub

@arthurclares is already working on this.

Since Feb 19, 2026.

Needs: Attention 👋 Tool: WACOA
Dominant language
PowerShell
Stars
603
Forks
248
Avg merge
7d 11h
Merged PRs (30d)
11

Description

🐛 Problem

TODO: Customer provided access to two subscriptions (ex: contoso-prod and contoso-core) under same tenant via Azure Lighhouse.

👣 Repro steps

  1. Start PS command prompt
  2. Run Az login
  3. After login selected one of the Customer delegated subscriptions (ex contoso-core)
  4. Ran all usual commands (Invoke-WebRequest -Uri https://aka.ms/acorl/tools/costcollector -OutFile collectCostRecommendations.ps1 and .\collectCostRecommendations.ps1 -verbose"
  5. I scope it to MyScope.json file where I am only mentioning target subscription (contoso-core)
  6. It doesn't pick up any recommendation despite I see that there are Advisor recommendation in the subscription

🤔 Expected

It should output recommendations for that subscriptions in a CSV file but it doesn't output only manual recommendations.

📷 Screenshots

Image

ℹ️ Additional context

Additionally, when I use entire scope, it picks up all subscription (including @microsoft.com and also contoso-prod) but it doesn't pick up contoso-core. It's really weird. I tried restart PS, it tried with 4 other SMEs over my shoulder but it's not picking up recommendations from contoso-core, whatsoever.

🙋‍♀️ Ask for the community

We could use your help:

  1. Please vote this issue up (👍) to prioritize it.
  2. Leave comments to help us solidify the vision.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.