This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article describes common FinOps toolkit errors and provides information about solutions. If you get an error when using FinOps toolkit solutions that you don't understand or can't resolve, find the following corresponding error code with mitigation steps to resolve the problem.
Here's a list of common error codes with mitigation information.
If the information provided doesn't resolve the issue, try the Troubleshooting guide.
Severity: Critical
This error generally means the account you are connected with does not have access to the resource you're attempting to use.
Mitigation: Confirm you are using the correct account in the correct Microsoft Entra ID tenant.
Severity: Critical
This error typically occurs when updating a FinOps hub deployment with a different storage account configuration than was originally used during creation. While most properties can be changed, there are a few properties that can only be set once when the storage account is created and cannot change. The one known case of this for FinOps hubs is the "requireInfrastructureEncryption" property. If this property was enabled or disabled during the first FinOps hub deployment, then it cannot be changed. You will see the following error when this happens:
The property 'requireInfrastructureEncryption' was specified in the input, but it cannot be updated as it is read-only.
Mitigation: If you did not mean to change this setting, confirm whether your storage account is configured to use infrastructure encryption and re-deploy the FinOps hub template with the same value (either on or off). If you want to change the setting, we recommend deploying a new FinOps hub instance, as this will require reingesting all data.
You can try to delete the existing storage account and redeploy the template with infrastructure encryption changed; however, we have not thoroughly tested this. While we do not anticipate issues, we cannot confirm if it will cause problems.
Severity: Critical
FinOps hubs 0.2 isn't operational. Upgrade to version 0.3 or later.
Mitigation: Upgrade to the latest version of FinOps hubs.
Severity: Critical
There may be multiple instances of this error. The one known instance is when Key Vault returns the following error:
A vault with the same name already exists in deleted state. You need to either recover or purge existing key vault. Follow this link https://go.microsoft.com/fwlink/?linkid=2149745 for more information on soft delete.
This generally means you're deploying on top of an old deployment that was deleted, but Key Vault kept the old vault instance in a recoverable delete state.
Mitigation: To fix this, purge the deleted Key Vault in the Azure portal.
You can now retry the deployment.
Severity: Warning
ContractedCost (based on negotiated discounts) is less than EffectiveCost (after commitment discounts) in the data from Cost Management. This should never happen unless the commitment discount provides less of a discount than your existing negotiated discounts. This will cause your savings calculations to not add up precisely.
Mitigation: Confirm the ContractedUnitPrice in the cost data matches what's in the price data. If the contracted price is correct, file a support request with the Cost Management team to confirm the x_EffectiveUnitPrice and EffectiveCost are correct. If they are correct, consider returning the commitment discount.
Severity: Critical
Data Explorer ingestion failed. The new data will not be available for reporting.
Mitigation: Review the Data Explorer error message and resolve the issue. Rerun data ingestion for the specified folder using the ingestion_ExecuteETL pipeline in Azure Data Factory. Report unresolved issues at https://aka.ms/ftk/ideas.
Severity: Critical
Data Explorer ingestion mapping could not be created for the specified table.
Mitigation: Please fix the error and rerun ingestion for the specified folder path. If you continue to see this error, please report an issue at https://aka.ms/ftk/ideas.
Severity: Critical
Data Explorer ingestion timed out after 2 hours while waiting for available capacity.
Mitigation: Please re-run this pipeline to re-attempt ingestion. If you continue to see this error, please report an issue at https://aka.ms/ftk/ideas.
Severity: Critical
Data Explorer post-ingestion cleanup (drop extents from the final table) failed. Data from a previous ingestion may be present in reporting, which could result in duplicated and inaccurate costs.
Mitigation: Review the Data Explorer error message and resolve the issue. Rerun data ingestion for the specified folder using the ingestion_ExecuteETL pipeline in Azure Data Factory. Report unresolved issues at https://aka.ms/ftk/ideas.
Severity: Critical
Data Explorer pre-ingestion cleanup (drop extents from the raw table) failed. Ingestion was not completed.
Mitigation: Review the Data Explorer error message and resolve the issue. Rerun data ingestion for the specified folder using the ingestion_ExecuteETL pipeline in Azure Data Factory. Report unresolved issues at https://aka.ms/ftk/ideas.
Severity: Major
FinOps hubs 0.8 sets the Azure Data Explorer "trustedExternaltenants" security setting to lock the cluster down so it can only be access from specific, trusted tenants. This setting can be set for the first deployment, but cannot be set again in a second deployment. You may see the following error if you try to redeploy FinOps hubs 0.8 on top of an existing 0.8 deployment:
The template output 'clusterUri' is not valid: The language expression property 'uri' doesn't exist, available properties are 'trustedExternalTenants, enableStreamingIngest, publicNetworkAccess, enableAutoStop, provisioningState'.
We are following up with the Azure Data Explorer team to identify the correct resolution.
Mitigation: Deploy FinOps hubs 0.9. This setting has been removed from the template.
Severity: Critical
Exports weren't found in the specified storage path.
Mitigation: Confirm that a Cost Management export was created and configured with the correct storage account, container, and storage path. After created, select 'Run now' to start the export process. Exports can take 15-30 minutes to complete depending on the size of the account. If you intended to use FinOps hubs, correct the storage URL to point to the 'ingestion' container. Refer to the storageUrlForPowerBI output from the FinOps hub deployment for the full URL.
Severity: Critical
This billing scope type is not supported by managed exports.
Mitigation: Remove the unsupported billing scope from settings.json, confirm the billing scope is supported by FinOps hubs and manually create new Cost management exports for the billing scope.
Severity: Critical
Microsoft Customer Agreements are not supported for managed exports.
Mitigation: Remove the MCA billing scope from settings.json and manually create new Cost Management exports for each MCA billing profile for FOCUS cost, pricesheet, reservation details, reservation transactions and reservation recommendations.
Severity: Critical
FinOps hub data was not found in the specified storage account.
Mitigation: This error assumes you are connecting to a FinOps hub deployment. If using raw exports, please correct the storage path to not reference the ingestion container. Confirm the following:
StorageUrlForPowerBI output on the FinOps hub deployment.msexports container.For more details and debugging steps, see Validate your FinOps hub deployment.
Severity: Critical
Unable to locate parquet files to ingest from the specified folder path.
Mitigation: Confirm the folder path is the full path, including the ingestion container and not starting with or ending with a slash (/). Copy the path from the last successful ingestion_ExecuteETL pipeline run.
Severity: Major
As of November 2024, Cost Management has a known bug where savings plan purchases are internally tracked as both actual and amortized costs. Because of this, FOCUS includes savings plan purchases in the calculation for EffectiveCost, which leads to inaccurate numbers in FinOps toolkit reports.
Mitigation: File a support request with the Microsoft Cost Management team with details about the issue to fix the underlying data. As of November 2024, the team is aware of the issue, but the fix has not yet been prioritized. In the interim, update to FinOps toolkit 0.7, which includes a workaround for FinOps hubs and storage-based Power BI reports.
Severity: Critical
This file looks like it might be exported from Cost Management but it isn't in the correct container.
Mitigation: Update your Cost Management export to point to the 'msexports' storage container. The 'ingestion' container is only used for querying ingested cost data.
Severity: Critical
FinOps hubs require FOCUS cost exports but this file looks like a legacy Cost Management export.
Mitigation: Create a new Cost Management export for FOCUS cost and either stop the current export or change it to export to a different storage container.
Severity: Critical
FinOps hubs 0.1.1 and earlier don't work with the Data ingestion Power BI report.
Mitigation: Upgrade to the latest version of FinOps hubs or download Power BI reports from release 0.1.1.
Severity: Informational
The export path isn't a valid scope ID. FinOps hubs expect the export path to be an Azure resource ID for the scope the export was created to simplify management. It shouldn't cause failures, but might result in confusing results for scope-related reports.
Mitigation: Update the storage path for the Cost Management export to use the full Azure resource ID for the scope.
Severity: Informational
This error code is shown when the ingested data uses an older version of FOCUS. When found in the x_SourceChanges column, the code is informational only. When shown in Power BI storage reports when the Costs query fails to load, this means the Deprecated: Perform Extra Query Optimizations parameter is disabled.
FinOps hubs converts data to the latest FOCUS version so this should not cause an issue; however, the modernization transform cannot account for all scenarios and may result in unexpected results in some cases. Refer to documentation for known issues.
Mitigation: There are several ways to mitigate this message, depending on which tool you're using.
If using FinOps hubs with Data Explorer and seeing this in the x_SourceChanges column of the Costs table or related functions, update Cost Management cost exports to use the latest FOCUS version. No additional changes need to be made all data will be merged during Data Explorer ingestion.
If using storage reports and seeing this in the x_SourceChanges column of the Costs query, this message is a warning that this FOCUS version will be removed in a future update. While you can safely ignore this message, it will require an update in a future release. To avoid the message, update Cost Management exports to the latest FOCUS version, delete or move any older data using an older FOCUS version, and reexport historical data. If using FinOps hubs, delete or move data outside of the ingestion container. If hosting your own exports in storage, change the Storage URL parameter to a different folder path that does not include older FOCUS versions.
As of FinOps toolkit 0.7, support for older FOCUS versions has been deprecated to improve performance and scalability. We recommend updating to the latest FOCUS version and reexporting data to improve your experience. Set the Deprecated: Perform Extra Query Optimizations parameter to TRUE to ensure older FOCUS versions are supported and set it to FALSE to speed up performance and support larger datasets covering more cost or time. As of 0.7, this parameter is enabled by default for backwards compatibility. In FinOps toolkit 0.8, it will be disabled by default, but still available for backwards compatibility until on or after June 2025. If you cannot move off of old FOCUS versions or for the best performance and support for larger accounts or longer periods of time, we recommend using FinOps hubs with Data Explorer.
Severity: Warning
ListCost (based on public, retail prices) is less than ContractedCost (based on negotiated discounts) in the data from Cost Management. This should never happen. This will cause your savings calculations to not add up precisely.
Mitigation: Confirm the ListUnitPrice in the cost data matches what's in the price data. If the list price is correct, file a support request with the Cost Management team to confirm both the ListUnitPrice and ContractedUnitPrice are correct and explain why the price after negotiated discounts would be higher than public, retail rates.
Severity: Critical
FinOps hub msexports_ExecuteETL pipeline failed to read the Cost Management manifest file.
Mitigation:
To confirm the manifest schema (#1) or API version (#2):
{
"exportConfig": {
"resourceId": "<scope-id>/providers/Microsoft.CostManagement/exports/<export-name>",
"dataVersion": "<dataset-version>",
"apiVersion": "2023-07-01-preview",
"type": "<dataset-type>",
...
},
...
}
Tip
If you consider yourself a power user, you may want to try updating the pipeline yourself for the quickest resolution. To do that, open Data Factory, navigate to Author > Pipelines > msexports_ExecuteETL, and select the applicable "Set" activities and update the Settings > Value property as needed. If you do this, you do not need to re-create the export with an older version. Please still report the issue and consider sharing the new JSON from the {} icon at the top-right of the pipeline designer._
I am using Cost Management exports to pull my cost data into ADLS. I have an ADF pipeline that is processing the data when manifest files are written. My pipeline was built on API version
<your-supported-api-version>which expectsexportConfig.resourceId,exportConfig.type, andexportConfig.dataVersionproperties to be delivered consistently. I noticed these files are not being included in the manifest file for this API version for my export that ran on<your-export-date>. My expectation is that the manifest file should never change for an existing API version. Can you please revert these changes?To help you troubleshoot, here is my manifest file: {your-manifest-json}
If the manifest properties look good and it was a new or upgraded FinOps hub instance, confirm the deployment:
We try to respond to issues and discussions within two business days.
Severity: Informational
This error code is shown in the x_SourceChanges column when ContractedCost is either null or 0 and EffectiveCost is greater than 0. The error indicates Microsoft Cost Management didn't include ContractedCost for the specified rows, which means savings can't be calculated.
Mitigation: As a workaround to the missing data, FinOps toolkit reports copy the EffectiveCost into the ContractedCost column for rows flagged with this error code. Savings aren't available for these records.
To calculate complete savings, you can join cost and usage data with prices. For more information, see issue #873.
Severity: Informational
This error code is shown in the x_SourceChanges column when ContractedUnitPrice is either null or 0 and EffectiveUnitPrice is greater than 0. The error indicates Microsoft Cost Management didn't include ContractedUnitPrice for the specified rows, which means savings can't be calculated.
Mitigation: As a workaround to the missing data, FinOps toolkit reports copy the EffectiveUnitPrice into the ContractedUnitPrice column for rows flagged with this error code. Savings aren't available for these records.
To calculate complete savings, you can join cost and usage data with prices. For more information, see issue #873.
Severity: Informational
This error code is shown in the x_SourceChanges column when ListCost is either null or 0 and ContractedCost is greater than 0. The error indicates Microsoft Cost Management didn't include ListCost for the specified rows, which means savings can't be calculated.
Mitigation: As a workaround to the missing data, FinOps toolkit reports copy the ContractedCost into the ListCost column for rows flagged with this error code. Savings aren't available for these records.
To calculate complete savings, you can join cost and usage data with prices. For more information, see issue #873.
Severity: Informational
This error code is shown in the x_SourceChanges column when ListUnitPrice is either null or 0 and ContractedUnitPrice is greater than 0. The error indicates Microsoft Cost Management didn't include ListUnitPrice for the specified rows, which means savings can't be calculated.
Mitigation: As a workaround to the missing data, FinOps toolkit reports copy the ContractedUnitPrice into the ListUnitPrice column for rows flagged with this error code. Savings aren't available for these records.
To calculate complete savings, you can join cost and usage data with prices. For more information, see issue #873.
Severity: Informational
This error code is shown in the x_SourceChanges column when ProviderName is null. The error indicates the provider of the dataset (for example, Microsoft Cost Management) did not include a ProviderName value for the specified rows.
Mitigation: As a workaround to the missing data, FinOps toolkit reports attempt to identify the provider based on the available columns.
Severity: Minor
The source of this error is unknown. This error may be surfaced randomly when refreshing Power BI data.
Mitigation: If you receive this error, select Apply change again.
This error has only been reported in storage reports. If you have long data refresh times or experience this error often, consider switching to FinOps hubs with Data Explorer. Data Explorer uses KQL reports which do not require scheduling or incremental refresh. Data is pulled when the report is opened, so reports always show the latest data.
Power BI: An exception of the 'Microsoft.Mashup.Engine.Interface.ResourceAccessForbiddenException' type was thrown
Indicates that the account loading data in Power BI doesn't have the Storage Blob Data Reader role. Grant this role to the account loading data in Power BI.
If you deleted FinOps Hubs and are attempting to redeploy it with the same values, including the Managed Identity name, you might encounter the following known issue:
"code": "RoleAssignmentUpdateNotPermitted",
"message": "Tenant ID, application ID, principal ID, and scope are not allowed to be updated."
To fix that issue you have to remove the stale identity:
Severity: Critical
FinOps hub msexports_ETL_ingestion pipeline failed to load the schema file.
Mitigation: Review the error message to note the dataset type and version, which are formatted with an underscore (for example, <type>_<version> or FocusCost_1.0). Confirm that the dataset and type are both supported by the deployed version of FinOps hubs. See supported datasets for details.
Severity: Critical
FinOps hub msexports_ExecuteETL pipeline wasn't able to find the schema mapping file for the exported dataset.
Mitigation: Confirm the dataset type and version are supported. See supported datasets for details. If the dataset is supported, confirm the hub version with the Data ingestion report.
To add support for another dataset, create a custom mapping file and save it to config/schemas/<dataset-type>_<dataset-version>.json. The <dataset-type> <dataset-version> values much match what Cost Management uses. To identify the datatype for each column, use an existing schema file as a template. Some datasets have different schemas for EA and Microsoft Customer Agreement (MCA). They can't be identified via these attributes and might cause an issue if you have both account types. We're working on adding datasets and account for the EA and MCA differences by aligning to FOCUS.
Severity: Major
If you are experiencing this in FinOps toolkit 0.8 reports, the error is because of a reference to a parameter that does not exist.
Mitigation: This was fixed in FinOps toolkit 0.9. Update to the latest release to apply the fix. If you need to apply the fix directly to the 0.8 reports, edit the ftk_DemoFilter function in the advanced editor and change the contents to: () => "". Save, then close and apply all changes.
Severity: Informational
The file in hub storage doesn't look like it was exported from Cost Management. File is ignored.
Mitigation: The msexports container is intended for Cost Management exports only. Move other files in another storage container.
Severity: Informational
This error code is shown in the x_SourceChanges column when a FOCUS version could not be identified.
Mitigation: Validate that the FOCUS dataset is using a supported FOCUS version. Report this issue with an anonymized sample of the data at https://aka.ms/ftk/ideas to investigate further.
Severity: Critical
Unable to identify the version of FinOps hubs from the settings file. Verify settings are correct. FinOps hubs 0.1.1 and earlier doesn't work with this Power BI report.
Mitigation: Upgrade to the latest version of FinOps hubs or download Power BI reports from the FinOps toolkit v0.1.1 release.
Severity: Critical
Unable to ingest the specified export file because the file type isn't supported.
Mitigation: Either convert the file to a supported file format before adding to the msexports container or add support for converting the new file type to the msexports_ETL_ingestion pipeline.
Severity: Warning
The export manifest in hub storage indicates the export was for an unsupported dataset. Exported data is reported as ingestion errors.
Mitigation: Create a new Cost Management export for FOCUS cost and either stop the current export or change it to export to a different storage container.
Open the subscription in the Azure portal, then select Settings > Resource providers, select the resource provider row (for example, Microsoft.EventGrid), then select the Register command at the top of the page. Registration might take a few minutes.
Cost Management exports before February 28, 2024 had a bug where x_PricingSubcategory was being set incorrectly for committed usage. You should expect to see values like Committed Spend and Committed Usage. Instead, you might see values like:
Committed /providers/Microsoft.BillingBenefits/savingsPlanOrders/###/savingsPlans/###Committed /providers/Microsoft.Capacity/reservationOrders/###/reservations/###If you see these values, re-export the cost data for that month. If you need to export data for an older month that isn't available, contact support to request the data be exported for you to resolve the data quality issue from the previous export runs.
If your report is missing all data for one or more months, check the Number of Months, RangeStart, and RangeEnd parameters to ensure the data isn't being filtered out.
To check parameters, select Transform data > Edit parameters in the ribbon or select the individual parameters in the 🛠️ Setup folder from the query editor window.
For more information, see Set up your first report.
If you don't see any data in your Power BI or other reports or tools, try the following based on your data source:
Billing Account ID and Number of Months parameters to ensure they're set correctly. Keep in mind old billing accounts might not have data in recent months.If the ingestion container is empty, open the Data Factory instance in Data Factory Studio and select Manage > Author > Triggers and verify the msexports_FileAdded trigger is started. If not, start it.
If the trigger fails to start with a "resource provider isn't registered" error, open the subscription in the Azure portal, then select Settings > Resource providers, select the Microsoft.EventGrid row, then select the Register command at the top of the page. Registration might take a few minutes.
After registration completes, start the msexports_FileAdded trigger again.
After the trigger is started, rerun all connected Cost Management exports. Data should be fully ingested within 10-20 minutes, depending on the size of the account.
If the issue persists, check if Cost Management exports are configured with file partitioning enabled. If you find it disabled, turn it on and rerun the exports.
Confirm the ingestion container is populated and refresh your reports or other connected tools.
If the ingestion container isn't empty, confirm whether you have parquet or csv.gz files by drilling into the folders.
Once you know, verify the FileType parameter is set to .parquet or .gz in the Power BI report. See Connect to your data for details.
If you're using another tool, ensure it supports the file type you're using.
Indicates that the storage account name is incorrect. If using FinOps hubs, verify the StorageUrl parameter from the deployment. See Connect to your data for details.
Indicates that the Billing Account ID parameter is empty. If using FinOps hubs, set the value to the desired billing account ID. If you don't have access to the billing account or don't want to include commitment purchases and refunds, set the value to 0 and open the CostDetails query in the advanced editor and change the 2 to a 1. It informs the report to not load actual/billed cost data from the Cost Management connector. See Connect to your data for details.
Applicable versions: 0.1 - 0.1.1 (fixed in 0.2)
This error typically indicates that data wasn't ingested into the ingestion container.
If you just upgraded to FinOps hubs 0.2, the problem could result from the Power BI report being old (from 0.1.x) or because you aren't using FOCUS exports. See the Upgrade guide for details.
See Reports are empty (no data) for more troubleshooting steps.
Let us know how we're doing with a quick review. We use these reviews to improve and expand FinOps tools and resources.
If you're looking for something specific, vote for an existing or create a new idea. Share ideas with others to get more votes. We focus on ideas with the most votes.
If you don't see the error you're experiencing, walk through the troubleshooting guide. If you have any questions, start a discussion or create an issue in GitHub.
Training
Learning path
Use advance techniques in canvas apps to perform custom updates and optimization - Training
Use advance techniques in canvas apps to perform custom updates and optimization
Certification
Microsoft Certified: Power BI Data Analyst Associate - Certifications
Demonstrate methods and best practices that align with business and technical requirements for modeling, visualizing, and analyzing data with Microsoft Power BI.