What you need to know
- The Microsoft Emissions Impact Dashboard previously went by the name of the Microsoft Sustainability Calculator.
- It lets you know what the greenhouse gas impact is of Microsoft cloud services.
- It debuted in January 2020 and is now hitting general availability.
Microsoft has finally let its Emissions Impact Dashboard (formerly known as the Microsoft Sustainability Calculator) enter general availability, so any organization interested in learning about its carbon emission output with relation to its Microsoft cloud services usage can now be informed and better tackle sustainability challenges.
This tool from Microsoft has been around since January 2020, though it's been expanded between then and now, allowing it to do more and, by extension, offer users more valuable insights and data with which to help organizations in their sustainability planning. Here's how Microsoft describes its tool:
You can learn more about the Emissions Impact Dashboard over at Microsoft's blog post (opens in new tab) discussing the service's move to general availability. Microsoft has a history of focusing on how its cloud operations, and those of other organizations, affect sustainability efforts, hence why it has released offerings such as its Cloud for Sustainability package.
Many of Microsoft's operations rely on the cloud, especially as it's the foundation of key partnerships with giants including Mars and Wells Fargo. The company's calculator and other assorted tools are measures to keep an eye on all those initiatives' overall ecological impact.
Robert Carnevale is the News Editor for Windows Central. He's a big fan of Kinect (it lives on in his heart), Sonic the Hedgehog, and the legendary intersection of those two titans, Sonic Free Riders. He is the author of Cold War 2395. Have a useful tip? Send it to email@example.com.
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.