Microsoft Cloud for Sustainability

Import jobs are accessible (for editing or even examination) only to the creator of that import. That job can be transferred by that user to someone else. The documentation says that it's possible for an admin to transfer import jobs.

However, users with an admin security role in MSM are not able to do this. It may be a global admin who can do this outside MSM. But we don't know. This gives us risk because our imports are complex, and if someone were to leave the company without transferring, we'd have to rebuild these jobs. And they aren't easy to document, so we wouldn't have much to go on.

I'd suggest that either the system is modified so that those in the admin security role are able to transfer import jobs or eliminate this ownership restriction. No other parts of the tool (like calculations or All Emissions) are restricted to the creator. Imports (from our perspective) aren't in more need of this "protection" than other functions.

I would like to see the screen for MSM's main influencer function add the ability to remove information that is not useful and to view additional analysis results that are not displayed on the screen.

This feature will improve customer convenience.

This was raised via MS ticket Tracking ID#2409270030002995

In UAT, Users reported issues when exporting from the All Emissions tab - Error Message when exporting all Emissions.

This will become an issue when more metrics are added to MSM.

Advised by MS, there is a limitation to export only 5000 records.  

Here's the correspondence:  

There are multiple reasons why we would see slow view load performance or SQL timeout.

Here are few:

• Excessive number of columns in the view

• Missing index for the columns in the view

• Calculated Fields in the view column

• A lookup field set to sort in a view causing slower performance

• SQL timeout due to TotalRecordCount (TRC query)

Mitigation:

 1. Excessive number of columns in the view :

  - 1. When you load a view the number of columns selected will affected the performance.

  - 2. You can go to Advanced find and select the entity from the list and select the view.

  - 3. Then click on "Edit Columns" and select the column and click on "Remove"

  - 4. Now test the performance and see if that improve.

 2. Calculated Fields in the view column:

We can't index calculated field so it will affect the performance. In Unify you'll find a page of unindexable columns. Remove the calculate field from the view and see if that improves the performance.

Suggested to narrow down the filter and then export.

This is just not good enough with increasing volumes of data over numerous years, expected increase number of business units and increase number of metrics, data sources, data categories, etc.

It was observed that some emission factor values do not populate the respective areas in the final emissions. This was the case where the emission factors have Other GHGs and its respective units filled in, but the value fails to come through post emission calculations.

Currently, the weight measurement unit is set to mtCO2e as default, which comes up in both the emission and the waste dashboards available in Microsoft Sustainability Manager.

It would be helpful if there is an option to choose the default unit for reporting on each of the dashboards. Organizations would be using tonnage (tonnes, kilotonnes, megatonnes) for waste reporting, and similarly varied units for their emission metrics.

Currently, the automated update for goals happens on a daily basis, which sometimes gives an incorrect status update that a particular goal has been met when it has not. This is because there is no emission data being calculated for organizations on a daily basis, and the goals are analyzed on a monthly or an annual basis.

It would be helpful if the automation refresh could be set to a custom duration (monthly, quarterly, annually, etc) which would give users the freedom to set it up according to their needs. The current workaround only seems to be manual goal updates, which gets time consuming if there are a lot of goals being monitored.

Currently, editing a calculation model requires us to delete all the steps and nodes and build the model from scratch depending on where we would want to make an edit.

Would be helpful if users and developers were given an option to add and modify intermediary nodes without having to remove/reconfigure the existing steps that might come after that.

Would be great to have a social and governance data model to capture all aspects of ESG evaluation and reporting.

Please bring in the SSRS based reporting and Basic dashboard capabilities on the Sustainability manager. While there are out of box reports and dashboards, will be good to have basic capabilities enabling end users create their own versions, similar to what we have on Sales and Services apps.

Currently, in MSM, emissions associated with individual GHGs (e.g., CH4, N2O) are calculated in standard units such as kilograms or tonnes. The total CO2e value, which aggregates all individual GHG emissions by applying their respective Global Warming Potential (GWP), is also available.

However, we are encountering specific client requirements where they need the CO2e breakdown for each GHG as part of their reporting needs. This feature would help avoid the need for additional custom development on our end.