Announcements
No record found.
We're currently exploring ways to mitigate risks associated with using the Configuration Migration Tool (CMT) in Microsoft Sustainability Manager. As it stands, the tool appears to require migrating all models and profiles with each execution. While this worked well for our initial deployment to PROD, it poses challenges for incremental updates—especially when we only intend to push one or two targeted changes. The potential to unintentionally deploy unrelated components is a concern we'd like to avoid.
I'm posting this in the community to seek alternate approaches, if any, that would allow for selective migration of specific models and profiles in MSM between environments
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Stars!
Thanks to all of our 2025 Community Spotlight stars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
ManoVerse 12 Super User 2026 Season 1
DU-21011536-0 10
CL-04020835-0 2