Notifications
Announcements
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
PowerSoumyo 14
André Arnaud de Cal... 8 Super User 2025 Season 2
Vahid Ghafarpour 4 Super User 2025 Season 2