Skip to content
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.

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

Access to the Resource is forbidden when using Power BI & the Governance.storage report #1268

Open
denverwilliams opened this issue Jan 26, 2025 · 1 comment
Assignees
Labels
OKR: 1.2 Reliability Issues that improve reliability and resiliency Resolution: External Issue is external to the FinOps toolkit Tool: Power BI Power BI reports Tool: Resource Graph External issues related to Azure Resource Graph

Comments

@denverwilliams
Copy link

🐛 Problem

When using the Governance.storage PowerBI Report, there are a few tables, 'AdvisorRecommendations, AdvisorReservationRecommendations, Disks, ManagementGroups' that run Azure Resource Graph Queries to populate the report. 

I am able to get this report to work if I setup PowerBI to use a Global Admin Account to connect to Azure Resource Graph. Which seems overkill, and from documentation I've seen, only Reader should be required. 

If I try to run the same Azure Resource Graph queries that are being used in PowerBI with az-cli/powershell and Reader Access, I can execute the queries just fine and don't have any access issues. But when running the PowerBI report, if it's done with anything less than Global Admin, the report fails with forbidden errors.

The Azure Resource Graph queries in PowerBI run at a tenant level, and I suspect this is why these fail with just Reader access. 

👣 Repro steps

  1. Run the Governance.storage.pbit Power BI Report. 

  2. Connect to Azure Resource Graph using an account with Reader Access only. 

🤔 Expected

It would be good to get clarity on what the minimum access requirements are in order to run the Governance.storage PowerBI Report. Or is Global Admin really the minimum required for this report?

📷 Screenshots

Image

@denverwilliams denverwilliams added Needs: Triage 🔍 Untriaged issue needs to be reviewed Type: Bug 🐛 Something isn't working labels Jan 26, 2025
@flanakin flanakin added the Tool: Power BI Power BI reports label Jan 28, 2025
@flanakin flanakin added OKR: 1.2 Reliability Issues that improve reliability and resiliency and removed Type: Bug 🐛 Something isn't working labels Jan 30, 2025
@flanakin
Copy link
Collaborator

flanakin commented Feb 2, 2025

This is very strange. I don't have global admin access and I've never run into this. I would file a support request against ARG to get assistance with this. I'm not sure how to troubleshoot this without having someone else try their account.

@nteyan Have you seen anything like this before?

@flanakin flanakin added Resolution: External Issue is external to the FinOps toolkit Tool: Resource Graph External issues related to Azure Resource Graph labels Feb 2, 2025
@flanakin flanakin added this to the 2025-02 - February milestone Feb 2, 2025
@flanakin flanakin removed the Needs: Triage 🔍 Untriaged issue needs to be reviewed label Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OKR: 1.2 Reliability Issues that improve reliability and resiliency Resolution: External Issue is external to the FinOps toolkit Tool: Power BI Power BI reports Tool: Resource Graph External issues related to Azure Resource Graph
Projects
None yet
Development

No branches or pull requests

3 participants