microsoft · Copilot · Oct 10, 2025 · Oct 10, 2025 · Oct 10, 2025 · Mar 11, 2026
@@ -3,7 +3,7 @@ title: FinOps toolkit changelog
 description: Review the latest features and enhancements in the FinOps toolkit, including updates to FinOps hubs, Power BI reports, and more.
 author: MSBrett
 ms.author: brettwil
-ms.date: 03/04/2026
+ms.date: 03/11/2026
 ms.topic: reference
 ms.service: finops
 ms.subservice: finops-toolkit
@@ -37,6 +37,9 @@ The following section lists features and enhancements that are currently in deve
 
 ### [Implementing FinOps guide](../implementing-finops-guide.md) v14
 
+- **Added**
+  - Added detailed mitigation guidance for [Azure Resource Graph payload size limit errors](help/errors.md#response-payload-size-is-and-has-exceeded-the-limit) with step-by-step instructions for filtering by subscription, tags, and removing columns.
+  - Added "Known limitations" section to [Governance report](power-bi/governance.md) and [Workload optimization report](power-bi/workload-optimization.md) documentation explaining Azure Resource Graph payload limits and when to use filtering.
 - **Fixed**
   - Updated FinOps Foundation video on the overview page to use the latest public video ([#2026](https://github.com/microsoft/finops-toolkit/issues/2026)).
 - **Removed**

@@ -3,7 +3,7 @@ title: Troubleshoot common FinOps toolkit errors
 description: This article describes common FinOps toolkit errors and provides solutions to help you resolve issues you might encounter.
 author: flanakin
 ms.author: micflan
-ms.date: 02/24/2026
+ms.date: 03/11/2026
 ms.topic: troubleshooting
 ms.service: finops
 ms.subservice: finops-toolkit
@@ -751,9 +751,60 @@ This error means that you have more resources than are supported in an unfiltere
 
 **Mitigation**: If you experience this error, there are several options:
 
-- Remove columns that are not necessary for your needs.
-- Filter the query to return fewer resources based on what's most important for you (e.g., subscriptions, tags).
-- Disable the query so it doesn't block other queries from running.
+### Option 1: Filter by subscription
+
+Modify the Azure Resource Graph queries to filter by specific subscriptions:
+
+1. Open Power BI Desktop and select **Transform data** from the ribbon.
+2. In the **Queries** pane on the left, expand the **Resource Graph** folder.
+3. Select the query that's failing (e.g., **NetworkSecurityGroups**, **Resources**).
+4. In the query editor, find the `query = "` section in the formula bar.
+5. Add a filter clause to the query. For example, to filter by subscription:
+
+   ```kusto
+   | where subscriptionId in~ ('subscription-id-1', 'subscription-id-2')
+   ```
+
+   Add this line after the `resources` line and before any `| extend` clauses.
+
+6. Select **Close & Apply** to save changes.
+
+### Option 2: Filter by tags
+
+If your resources use tags to organize by environment, cost center, or other criteria, you can filter by tags:
+
+1. Follow steps 1-4 from Option 1.
+2. Add a tag filter to the query:
+
+   ```kusto
+   | where tags.Environment in~ ('Production', 'Staging')
+   ```
+
+   Or filter by multiple tag conditions:
+
+   ```kusto
+   | where tags.CostCenter == '12345' and tags.Environment =~ 'Production'
+   ```
+
+### Option 3: Remove unnecessary columns
+
+Reduce the payload size by removing columns you don't need:
+
+1. Open the query in Power Query Editor (steps 1-3 from Option 1).
+2. In the query text, remove column names from the `extend` or `project` statements that you don't need for your analysis.
+3. Be careful not to remove columns that are used in report visuals or relationships.
+
+### Option 4: Disable problematic queries
+
+If a specific query consistently fails and isn't critical to your needs:
+
+1. In Power Query Editor, right-click the failing query in the **Queries** pane.
+2. Uncheck **Enable load** to prevent the query from loading data.
+3. The query will remain in the report but won't execute during refresh.
+
+For more information about Azure Resource Graph limits and pagination, see:
+- [Working with large Azure resource data sets](/azure/governance/resource-graph/concepts/work-with-data)
+- [Troubleshoot errors using Azure Resource Graph](/azure/governance/resource-graph/troubleshoot/general)
 
 <br>
 

@@ -3,7 +3,7 @@ title: FinOps toolkit Governance report
 description: Summarize cloud governance posture including areas like compliance, security, operations, and resource management in Power BI.
 author: flanakin
 ms.author: micflan
-ms.date: 02/24/2026
+ms.date: 03/11/2026
 ms.topic: concept-article
 ms.service: finops
 ms.subservice: finops-toolkit
@@ -119,6 +119,20 @@ The **Network security groups** page lists network security groups and network s
 
 <br>
 
+## Known limitations
+
+The Governance report uses Azure Resource Graph to query resource details. Azure Resource Graph has a response payload limit of 16 MB per query. The report is designed for small- and medium-sized environments and may not work for organizations with millions of resources.
+
+If you experience a "Response payload size... exceeded the limit" error, try the following:
+
+- **Filter by subscription or tags** – Update queries in Power Query Editor to filter resources by specific subscriptions or tags that are most important for your governance reporting.
+- **Remove unnecessary columns** – Edit queries to remove columns that aren't needed for your analysis to reduce the payload size.
+- **Disable problematic queries** – If a specific query consistently fails, you can disable it in Power Query Editor to allow other queries to load successfully.
+
+For detailed troubleshooting steps, see [Response payload size exceeded the limit](../help/errors.md#response-payload-size-is-and-has-exceeded-the-limit) in the error reference guide.
+
+<br>
+
 ## Looking for more?
 
 We'd love to hear about any reports, charts, or general reporting questions you're looking to answer. Create a new issue with the details that you'd like to see either included in existing or new reports.

@@ -3,7 +3,7 @@ title: FinOps toolkit Workload optimization report
 description: Learn about the Workload optimization report, which identifies opportunities for rightsizing and removing unused resources to enhance efficiency.
 author: flanakin
 ms.author: micflan
-ms.date: 02/24/2026
+ms.date: 03/11/2026
 ms.topic: concept-article
 ms.service: finops
 ms.subservice: finops-toolkit
@@ -79,10 +79,17 @@ The chart shows the cost of each disk over time. The table shows the disks with
 
 <br>
 
-## See also
+## Known limitations
 
-- [Common terms](../help/terms.md)
-- [Data dictionary](../help/data-dictionary.md)
+The Workload optimization report uses Azure Resource Graph to query resource details. Azure Resource Graph has a response payload limit of 16 MB per query. The report is designed for small- and medium-sized environments and may not work for organizations with millions of resources.
+
+If you experience a "Response payload size... exceeded the limit" error, try the following:
+
+- **Filter by subscription or tags** – Update queries in Power Query Editor to filter resources by specific subscriptions or tags that are most important for your workload optimization.
+- **Remove unnecessary columns** – Edit queries to remove columns that aren't needed for your analysis to reduce the payload size.
+- **Disable problematic queries** – If a specific query consistently fails, you can disable it in Power Query Editor to allow other queries to load successfully.
+
+For detailed troubleshooting steps, see [Response payload size exceeded the limit](../help/errors.md#response-payload-size-is-and-has-exceeded-the-limit) in the error reference guide.
 
 <br>
 
@@ -99,6 +106,11 @@ We'd love to hear about any reports, charts, or general reporting questions you'
 
 ## Related content
 
+Related resources:
+
+- [Common terms](../help/terms.md)
+- [Data dictionary](../help/data-dictionary.md)
+
 Related FinOps capabilities:
 
 - [Reporting and analytics](../../framework/understand/reporting.md)