Microsoft Cloud for Sustainability

Automation of data ingestion to fill out requirement of datapoints and pre-built templates to facilitate compliance.

I'm looking over the video on how to create a scorecard, and when choosing the baseline, you select the year and then manually enter the amount/value for that baseline. It would be much more efficient and useful for the data to be pulled from what already exists in the activity data. For example if i select 2019 for X facility, and the platform can detect that i have information for that year and that facility, then it should give me the option to generate that value automatically with that data, or enter it manually. Would be much more efficient and logical.

We have over 200 calculation profiles. It can be easy to accidentally misconfigure a calculation profile, or even build the wrong logic in the first place. It would be helpful to be able to generate a view that compares the calculation profiles and identifies any overlap

For troubleshooting calculation profiles, especially when trying to identify any overlap between calculation profiles, it would be nice to be able to disable or deactivate a profile.

Today, the calculation job errors log provides the Activity ID guid which is a system specific reference. This makes troubleshooting calculation errors challenging for the customer. Adding [msdyn_origincorrelationid] and/or [msdyn_name] to all error logs will facilitate faster troubleshooting as these attributes are known to the customer and will enable the customer to more quickly identify and correct specific data gaps.

It would be useful in order to enable accurate tracking and responsibilities for various stakeholders to bring the subscription ID&Azure service when doing the data ingestion (e.g. even in a tag/description attribute).

Customers who want to have all the information in MSM and take further actions based on one repository find it difficult that the EID data doesn’t have the granularity from the dashboard, so they could set their goals based on departments/services.

The workaround is to look only in EID, but that would lead to using 2 tools, which bypasses the value of “a single source of truth and action” via MSM.

Prediction of near real time catastrophic event, identified Physical risk perils, like

1. Flood
2. Landslide
3. Earthquake
4. Rising sea level
5. Storms
6. Heat wave
7. Tsunami

Needs at a high level a "Data aggregation platform integrated with a GIS Platform and visualization layer".

To develop the use model for a chosen industry.

Having GIS world map --> Elevation map ---> Location base map ---> Property / asset information ---> Focus interest ----> Climate change physical risk

To build PREDICTIVE models, for a specific industry locations, assets, covering:

1. Climate event
2. Vulnerability
3. Exposure
4. Quantification of all above

We aim to simplify the process of calculating carbon emissions in Microsoft Sustainability Manager by automating the mapping of data to default calculations. Upon data ingestion, the system will prompt users to prioritize factors from more specific sources (e.g., supplier or facility-specific data) to more general references (e.g., EPA or Defra factors). Based on the chosen prioritization, the system will automatically map the data to default emission calculation formulas and automatically calculate emissions, saving users time and effort in manual calculations. Users can have confidence in the accuracy and consistency of their emission calculations without the need for extensive data mapping.

However, we understand that flexibility is essential, so customers who prefer to use their custom carbon emissions calculations can still do so. They will have the option to input their own calculations, providing complete control over the emission calculation process.

• Once an external dataverse table is defined (via maker portal or another application), configure MSM to ingest that entity directly within the application.
• Use the external table in PFX calculations and reference via lookups in activities.
• Use the table as a pivot to select different emission factors on activities.
• Be able to export reports and view in PBI

I have many final users that will be reporting in MSM and I would like to be able to place a time limit on how far back the user can go to edit and/or delete information that they have previously uploaded. For example, not allowing users to edit or erase anything that is older than 3 months.