Custom x-resource group, x-subscription reporting
On Enterprise level, cost governance / cost control teams may have different scope than single RG, or single subscription. Today the only possibility to control costs at this level is to extract full cost data for all subscriptions (via "beta" connector), and then filter / limit in client tool. It's not manageable to do it RG-by-RG, and frequently even full subscription visibility is not possible (subscriptions may include resources given cost control team shouldn't have visibility to). We need to be able to provide aggregated views on costs not limited to full subscription / single resource group setup - allowing user to setup scope out of all RGs he/she has access to, in any subscription (or to start - even in single subscription).
Makes sense. The current recommendation is to organize a single team’s applications into resource groups within a single subscription per environment (e.g. production vs. dev/test), then organize subscriptions into management groups which map to the logical hierarchy within the organization. This allows you to report at all layers of the organization and manage access accordingly. We understand not all organizations are setup this way and will plan work to simplify this. Please vote this up to let us know how important this is for you.
Chris Thomas commented
If you are sharing cost analysis report which is scoped to subscription level with user who got only resource group level access then the error is expected behavior and user need to have subscription level access.
You can scope cost analysis to resource group level and then you will be able to share the report with user's who got resource group access which they themselves can login to Azure portal and access the cost analysis for that resource group. This is by design but not sustainable for these times anymore. We make different solutions for different customers, internal and external. The business units, product owners, customers want to see the costs on daily basis. Giving subscription level access is really not ok.
Yes that is perfectly defined, any changes will be appreciated.