Known issues and mitigations

This article lists known issues in Microsoft Sustainability Manager and provides mitigations, including fixes and recommendations.

Note

For a list of fixes included with each monthly release, view that month's What's new article.

Important

Hotfixes for Microsoft Sustainability Manager release with a staggered rollout to different countries/regions. Hotfixes aren't available in some countries/regions until a week or so after their initial release.

To take advantage of a hotfix, manually reinstall Microsoft Sustainability Manager from the Power Platform admin center.

Date Issue Mitigation
April 10, 2026 In a calculation model, using a Calculate node after an Aggregation node causes the following issues:

- The output unit locks to the original input unit.

- Subsequent nodes (Calculate or Estimation) continue to use the Aggregation unit by default, even if you select a new output variable.

- For the Allocation node, the unit dropdown might incorrectly display the Aggregation unit name instead of the Calculate node's output variable unit, which can result in duplicate unit options.		 If you see an "unresolved column" error, manually re-select the unit in the Allocation node and rerun the calculation model.
February 05, 2026 If you transfer ownership of a Data Import connection to another user, the data-source credentials and access permissions aren't updated automatically. As a result, import jobs might continue to fail after the transfer. This behavior is expected because Data Import uses the Dataflows service, which requires valid credentials to connect to the data source. The new owner must create a new data connection and validate their access permissions to the data source by using the Data Import wizard.
January 31, 2026 In calculation profiles, the Preview results stage doesn't show the correct GWP factor values and calculated CO₂e emissions for individual gases. Preview results uses Global Warming Potential (GWP) factor values from the Custom AR version, regardless of the AR version selected in the calculation profile. There's no current mitigation or workaround. This issue doesn't affect actual calculation output and isn't blocking.
January 05, 2026 After the January 2026 release, upsert operations might create duplicate records for data that was ingested earlier. This issue is caused by a change in OCID hash generation. An entity name prefix prevents OCID collisions across entities. Records ingested before the release use a different hash format, so Dataverse might treat an upsert as a new record. As a result, duplicates might be created between January 5, 2026, and January 21, 2026. Identify records duplicated between January 5, 2026, and January 21, 2026, and delete the duplicates created by the upsert. After you remove the duplicates, run ingestion again. Ingestion doesn't create duplicate records.
September 26, 2025 IEA provides emission factor values for individual gases in CO₂ equivalent (CO₂e) units. To align with our data model, these values are converted into individual gas values by dividing the CO₂e values by their respective Global Warming Potential (GWP). However, when converting these values back to CO₂e, minor discrepancies can occur due to decimal point rounding. This rounding issue will be fixed in a future release.
June 07, 2025 The "By sustainability category" visual on the emission insights doesn't show the breakdown by product category hierarchy. There's no current mitigation or workaround. This issue will be fixed in a future release.
May 28, 2025 Incremental refresh in data imports of Microsoft Sustainability Manager is doing the full refresh, instead of only refreshing the new data based on time selected. There's no current mitigation or workaround. Although full refresh is used instead of incremental refresh, the actual data isn't affected — records are either updated (if OCID values are present and mapped) or imported as duplicates. The only impact is the additional processing time required to import all records.
April 03, 2025 Maps in the Facilities tab of Company Profile aren't loading, or the address autocompletion isn't working in the General section of Company Profile. Upgrade the application to the latest version available (on or after February 2025 release).
March 05, 2025 The IEA 2022 Emission Factors library shows the following description: "Factors related to emissions from electricity generation for 2022 (pub 2024). IEA provided CH4 and N2O values in CO2e using AR4 GWP factors. Microsoft converted those CO2e values to basic CH4 and N2O values in grams." However, the IEA emission factors were published using AR6, and the values reflect raw values derived using AR6. The description will be fixed in a future release to accurately reflect the emission factors' derivation source and data conversion process.
March 05, 2025 In calculation models with dropdown menus containing more than 100 values (such as facility selection in condition nodes), the dropdown list might display incomplete results. Some values might not be visible in the selection menu. You can write a PowerFx expression to set the required values. For example, Activity.<lookup>.name = <value>.
March 05, 2025 Sometimes you might get the error message: Unable to create connection due to unknown data type(s). Replace with valid data type(s) and try again. This error occurs when unsupported data types are used when creating a connection. Edit the data type either through the Edit import wizard from the list page or through Edit transformations in the details page. For more information on how to edit data imports, see Edit data transformations.
January 13, 2025 Customizations to the Microsoft Sustainability Manager sitemap can be overwritten by the new integrated sitemap experience included in the January release. This issue typically affects sitemap changes published as an unmanaged layer (solution) using the maker portal. For more information, see Solution layering in Dataverse. Ensure that all solutions are upgraded to the latest version. Then, re-add the navigation nodes manually and republish the sitemap. Deploy any sitemap customizations by using a managed solution.
November 15, 2024 In certain edge cases for advanced calculation scenarios, a calculation error results from a difference in the unit of calculation/estimation node and the report node. This error can result in incorrect emissions calculation due to an incorrect unit being applied if all of these three conditions exist:

- A calculation or estimation node is used.

- The output unit of that node isn't a specific unit (for example, the quantity unit is chosen) and the selection for the input unit doesn't match the selection for the output unit.

- The activity units flowing through the calculation model are diverse, or the output units of mapped estimation factors are diverse.

In this case, an activity flows through the calculation or estimation node and establishes the input unit for a downstream Report, Water, Waste, Emissions, or Estimation node. The downstream node doesn't reset itself for new activity data with different unit groups, so an error occurs.

If the unit groups are the same, there might be an incorrect unit conversion, but calculation occurs, resulting in an incorrect emissions output. Otherwise, the calculation of other activity records fails with a unit conversion error.		 This issue will be fixed in a future release.
November 13, 2024 In some cases in Microsoft Sustainability Manager, the Update field in a data import report doesn't show the actual number of records updated. This issue generally occurs with updated records, not inserted records. A fix for this issue is planned for a future release. For an explanation of how the record update process works, go to Determine record uniqueness.
October 22, 2024 In Microsoft Sustainability Manager, some market-based emissions incorrectly display as location-based, even when the Is Market based field (now deprecated) is set to true. This field was replaced by a new accounting method entity with the introduction of the alternate emissions feature. The issue affects customers who performed an upgrade or a fresh install of Sustainability Manager version 2.22 or later. A fix was deployed to ensure that this issue doesn't occur in the future, and that emissions data marked or calculated as "Market-based" is correctly captured without defaulting to location-based values. Reach out to the engineering team for further assistance.
October 15, 2024 Exports from Emission or Activity tables with more than 5,000 records time out. To retrieve more data, turn on pagination to request more than 5,000 rows.
  • Last updated on