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 lists known issues in Microsoft Cloud for Sustainability. It also provides mitigations, which can include fixes and recommendations.
Note
For a list of fixes included with each monthly release, view that month's What's new article.
Microsoft Sustainability Manager
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, you must manually reinstall Microsoft Sustainability Manager from the Power Platform admin center.
| Date | Issue | Mitigation |
|---|---|---|
| April 03, 2025 | Maps in the Facilities tab of Company Profile aren't loading and/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 has 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 corrected 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 may 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 may 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, readd the navigation nodes manually and republish the sitemap. We recommend that you deploy any sitemap customizations 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 node of bullet 1 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 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. | We expect to include a fix for this issue in 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 are incorrectly displaying as location-based, even when the Is Market based field (now deprecated) was set to true. This field was replaced with 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. | We deployed a fix 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, you need to Turn on pagination to request more than 5,000 rows. |