Microsoft Dynamics 365 | Integration, Dataverse...

Evergreen CRM wave 1 2026

(0) Share

Report

Posted on by SD-25031333-0

Evergreen CRM wave 1 2026 and when monthly updates were switched on by Microsoft instead of 6 monthly updates within our own control

All our environments have been switched to Monthly release without a clear notification to us and not under our control – we do 6 monthly releases for our Preprod and Prod environments. When were these changes made?

Can you explain why are we seeing multiple versions instead of the latest version from those Monthly releases across our instances of our CRM environments?

When we can expect cut off dates for the 6 monthly release (wave 1 2026)?

What steps do we need to take to ensure the monthly update moves to the latest version rather than our environments being misaligned on different monthly versions?

Are the cut off dates the ‘drop dead date’ when the services will be a forced release to our environments and restarted?

Categories:

Dynamics 365 general

I have the same question (0)

All responses (2)

Answers (0)

Sort by

11manish 726 on at

Like (0)

Report
Copy link

Link copied!
Key Dates for 2026 Release Wave 1
The 2026 Wave 1 represents the "major" biannual milestone that still exists alongside monthly updates:

Release Plans Available: March 18, 2026.

General Availability (GA): April 1, 2026.

Cut-off (Drop Dead Date): By the end of April 2026, all instances will have these mandatory capabilities applied automatically.

Reference : https://learn.microsoft.com/en-us/dynamics365/get-started/release-schedule

Was this reply helpful? Yes No
SD-25031333-0 4 on at

Like (0)

Report
Copy link

Link copied!

The website are example dates, it says so underneath.

If you are in the UK or Europe its a release date of weekend of 3rd April or 10th April respectively, we need two weeks to do DEV/TEST and testing as we have multiple apps on the instances to test, 1 week to test Preprod and 1 weeks to test prod which takes us up to 8th May, this is why i am asking as we will need to reduced time spent testing if the cut off is 1st May, this is why we need the exact cut off dates. Dev teams can't plan currently whilst we wait for Microsoft to provide clarity on that.

Also my questions on the monthly update stand.

Was this reply helpful? Yes No