Catatan
Akses ke halaman ini memerlukan otorisasi. Anda dapat mencoba masuk atau mengubah direktori.
Akses ke halaman ini memerlukan otorisasi. Anda dapat mencoba mengubah direktori.
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 Microsoft Cloud Solution Center.
| Date | Issue | Mitigation |
|---|---|---|
| August 15, 2024 | The August 2024 release includes the alternate emissions feature, which allows you to calculate alternate emissions outputs using the same source data. In Sustainability Manager, we adhere to Greenhouse Gas Protocol (GHG Protocol) guidelines, calculating emissions using either location-based or market-based accounting methods. If you don't specify an accounting method, Sustainability Manager defaults to location-based accounting. Because only scope 2 emissions vary based on the selected accounting method, while scope 1 and scope 3 emissions remain unchanged, emissions dashboards should accurately reflect this distinction. However, due to recent updates to the alternate emissions feature, when you select Market based from the Accounting method dropdown on the Executive dashboard or Emissions insights dashboard, scope 1 and scope 3 emissions don't display. |
Select Location based from the Accounting method dropdown to view your scope 1 and scope 3 emissions. We released a hotfix for this issue. |
| July 26, 2024 | With the July release, if you select the View errors while reviewing a data import, an error might appear that says Unexpected end of JSON input. | This error means that the View errors option isn't ready yet. You can try again after the import completes or reaches 1,000 errors. |
| June 28, 2024 | With the June release, editing a mapping for an existing Power Query data connection is broken, with no source fields being available for selection. This issue only affects the user experience of editing mappings for existing data connections. It doesn't affect running existing, unedited data connections or new data connections. |
We released a fix for this issue. Be sure to install the latest version of Microsoft Sustainability Manager. To recover the connection without the fix: 1. Edit the connection. 2. On the Manage data source page, rename the Power Query query to refresh the connection map table.  3. Remap. 4. Complete the connection wizard sequence. Related documentation: Import data with Power Query Copy connections from one environment to another |
| June 3, 2024 | In a calculation that has errors, the Retry job button doesn't appear on the page. | To make the button appear, select and then unselect a row in the grid. The button should appear, and you can continue with the process in Retry calculations. A fix is expected in a future release. |
Related information
- What's new in Microsoft Cloud for Sustainability overview
- What's new and planned for Microsoft Cloud for Sustainability 2023 wave 2
