Microsoft’s New Flexible Service Update Schedule for Dynamics 365 Finance and Operations: What You Need to Know
Image Source: Microsoft Learn
Earlier this year, Microsoft announced important changes to the One Version program, which delivers service updates and proactive quality updates.
As of April 2024, these updates come with new options for flexibility and scheduling, designed to make the update process smoother and more predictable for customers. Here’s an in-depth look at these changes and what they mean for businesses.
There are three key changes:
- Microsoft is now releasing four updates per year instead of seven, in February, April, July, and October. However, only two updates per year are required.
- You can only skip one release at a time instead of three.
- Microsoft is providing two auto-update windows per release, four weeks apart. If you pause a specific version, you need to pause both auto-update windows.
Why is Microsoft Changing the One Version Program?
With the release of version 10.0.39, organizations can choose from two auto-update windows four weeks apart. Microsoft's update schedule, allows companies to align better their internal processes, such as testing and validation. By selecting the update window that best fits their operational needs, companies can avoid potential disruptions and ensure a smoother transition when new features are implemented.
A Shift Toward Flexibility in 2024
This is a significant shift in Microsoft's update approach. Previously, updates were applied automatically on a fixed schedule. Now, with the ability to choose between two windows, organizations have more control over when updates are applied to their systems. This change is particularly beneficial for businesses with complex operations that require a longer validation period before new software is deployed.
Auto-update Cadence: Twice the Options, Same Reliability
Microsoft has maintained its predictable release cadence, with four annual updates scheduled for February, April, July, and October. These service updates contain both application and platform changes, which include crucial updates such as regulatory compliance fixes and new feature rollouts. While customers are required to apply at least two updates per year, they can now take up to four service updates. The flexibility to pause one update at a time has also been retained. This pause applies to both sandbox and production environments, giving companies the ability to control when and how these updates affect their systems.
However, starting in 2024, the maximum number of consecutive pauses has been reduced. Customers can only pause one update at a time, a change from the previous policy where three consecutive updates could be paused. This change ensures that businesses remain on a supported version of Dynamics 365 while also giving them some leeway to manage the update process.
New Update Windows: What’s Changed?
The introduction of dual auto update windows provides more flexibility but also requires organizations to be more strategic about their update planning. Here’s how the new process works:
- Preview and Self-Update Availability: Before any production update occurs, Microsoft releases a preview of the update. This is made available as a deployable package in the Lifecycle Services (LCS) Shared asset library. The preview is crucial for businesses that want to validate customizations or test new features before the update is applied to their live systems.
- First and Second Auto-update Windows: Each release will have two separate auto-update windows spaced four weeks apart. This allows organizations to choose when their production environment will be updated, helping them avoid any conflicts with internal schedules or busy periods.
- Sandbox Updates Precede Production: Microsoft updates sandbox environments seven days before production environments. This allows businesses to validate the update in a testing environment before it goes live in production, ensuring that any potential issues are caught early.
Managing the Update Process: Self-Update vs Auto-update
While Microsoft offers auto-updates for convenience, customers are encouraged to take control of the update process by self-deploying updates. By applying updates manually, businesses can control when and how new features are rolled out, minimizing disruption. Those who prefer a hands-off approach can simply stick to the auto-update schedule, trusting that Microsoft will apply the latest updates at the designated time.
For organizations that want even more control, Microsoft offers the First Release program. Participants in this program receive updates earlier than other customers, with updates being applied to a UAT sandbox environment first, followed by production after seven days. Microsoft engineers closely monitor these environments, providing businesses with the confidence that any issues will be identified and resolved before the update is applied to all customers.
What Happens If You Pause an Update?
The pause feature allows businesses to delay an update to better align with internal projects or busy periods. However, with the reduction in the number of consecutive pauses allowed, businesses need to be more strategic in how they use this feature. If a company fails to apply a service update within the designated pause period, Microsoft will automatically apply the latest update based on the settings configured in Lifecycle Services.
Microsoft has designed the service update process to be as smooth as possible, but for organizations that need more time to prepare, pausing updates is a useful tool. However, businesses must be aware of the risks involved with pausing too many updates, such as falling behind on critical regulatory updates or missing out on new features that could provide a competitive advantage.
Service Update Lifecycle: What to Expect
Each service update goes through a well-defined release process. After internal validation and testing by Microsoft, the service update is made available as a preview. This gives customers early access to the update, allowing them to test it in a non-production environment. Once the update is finalized, it becomes available for self-update or auto-update, depending on the customer's preference.
To make the update process easier to follow, Microsoft has updated its release naming convention. Starting with the 10.0.38 release, each version number will include the calendar year and quarter of the scheduled auto-update. Major releases will be marked with an asterisk, making it easier for businesses to track which updates contain significant changes.
Update Support Overview: How Stoneridge Can Help You Prepare for Updates
Stoneridge experts can help you follow update steps to ensure system stability, functionality, compliance, and customization integrity from pre-update to deployment. We will work with you through each activity to minimize disruption, address integration points, and maintain an optimal performance.
Here is a detailed outline of the support activities we can help you with during an update cycle:
- Service update planning meeting
- Code freeze
- Refresh data
- Prepare the development and build server for the service update
- Update ISVs
- Deploy updates to the sandbox
- Schedule update to production
- Update Tier 1 boxes
Our team also works closely with you to ensure testing and backups are completed. Additionally, we are ready to provide prompt support if you run into any speed bumps.
Want More Information on Changes to the One Version Program for Dynamics 365 Finance and Operations Updates?
Microsoft's new approach to service updates in 2024 provides businesses with greater flexibility and control over the update process.
Get in touch with us today to learn more.
Co-Author: Fernando Juarez
Under the terms of this license, you are authorized to share and redistribute the content across various mediums, subject to adherence to the specified conditions: you must provide proper attribution to Stoneridge as the original creator in a manner that does not imply their endorsement of your use, the material is to be utilized solely for non-commercial purposes, and alterations, modifications, or derivative works based on the original material are strictly prohibited.
Responsibility rests with the licensee to ensure that their use of the material does not violate any other rights.