Microsoft Dynamics 365 Finance and Operations release schedule

Understanding the Microsoft Dynamics 365 Finance and Operations release schedule is crucial for any business using this ERP system. Microsoft delivers updates to Dynamics 365 Finance & Operations (D365 F&O) on a predictable timetable, which helps organizations plan for new features, testing, and training.

The Dynamics 365 Finance and Operations release schedule is the structured timeline Microsoft follows to roll out both major release waves and ongoing minor updates throughout the year. Knowing this schedule matters because it ensures you stay current with improvements, remain supported on the latest version, and avoid surprises when Microsoft updates your system.

Microsoft Dynamics 365 Finance & Operations (D365 F&O) is a cloud-based enterprise resource planning (ERP) solution designed for medium to large organizations. It unifies core business processes such as finance, supply chain, sales, purchasing, and inventory into a single platform for better visibility and efficiency. Companies use D365 F&O to manage complex financial transactions, streamline operations, and gain real-time insights across departments, all within one integrated system.

D365 F&O actually consists of two primary applications: Dynamics 365 Finance and Dynamics 365 Supply Chain Management. The D365 Finance app focuses on financial management (general ledger, budgeting, reporting, etc.), while the D365 Supply Chain Management app covers operational processes (inventory, manufacturing, warehousing, logistics). Businesses can implement either module individually or use both together for a comprehensive ERP solution tailored to their needs. By leveraging these applications, organizations can modernize their accounting practices, automate supply chain workflows, and ensure all parts of the business are working from the same data and processes.

The Dynamics 365 Finance & Operations release schedule refers to Microsoft’s calendar for rolling out updates to the F&O platform. Using a continuous update model known as One Version, Microsoft ensures all environments remain current with the latest features, security patches, and system improvements. The release schedule is structured into three types of updates, each serving a distinct purpose in keeping your system functional, compliant, and evolving.

• Release waves: Major feature updates delivered twice a year (Wave 1 in spring, Wave 2 in fall). These introduce new capabilities across finance, supply chain, and user experience.
• Service updates: Quarterly updates focused on platform health, performance, and regulatory compliance. These updates are mandatory, with flexibility to pause one per year.
• Quality updates: Frequent hotfixes and patches that resolve bugs and stability issues. These are automatically applied and cannot be deferred.

Understanding how these updates work together helps you plan proactively, avoid disruption, and align internal testing and change management with Microsoft’s schedule.

Microsoft delivers new features for Dynamics 365 Finance and Operations through two major release waves each year. These waves are Microsoft’s way of introducing functional enhancements, UI improvements, and new capabilities in a controlled, phased approach. Each wave spans six months and covers a wide range of areas, including finance, supply chain, human resources, and platform usability.

There are two release waves per year:

• Release wave 1: Features begin rolling out between April and September
• Release wave 2: Features begin rolling out between October and March

These waves ensure users receive regular innovation without needing to perform major system upgrades.

Each release wave follows a predictable timeline. Microsoft gives customers time to explore new features in advance, test them in non-production environments, and prepare for what’s coming. This structure supports smoother adoption and proactive change management.

Key milestones in each wave:

• Release plan announcement: Microsoft publishes a comprehensive overview of new features planned for the upcoming wave. This allows teams to review what’s coming and assess which features may impact their operations, compliance requirements, or business workflows.
• Early access Program: Select features become available in sandbox environments before general rollout. This gives organizations the opportunity to test new functionality, validate customizations, and train users ahead of time—reducing surprises when updates reach production.
• General availability (GA): The official start of the release wave. Features begin rolling out to production environments across regions. Not all features activate at once; Microsoft staggers deployment and some remain optional during the wave’s window.
• Mandatory enablement: By the end of the wave period, Microsoft may enforce certain features, making them active in all environments regardless of prior configuration. This ensures consistency and full adoption across the platform.

Early access lets your team test and evaluate features in a sandbox before they affect live business operations. This preview period is optional, but highly recommended, especially for organizations with customizations, integrations, or industry-specific processes.

Each release wave introduces a curated set of new features and product improvements. Microsoft groups these updates by application area, such as finance, supply chain, procurement, or warehousing. Some waves include entirely new modules, while others focus on refining existing capabilities or improving performance and user experience.

Typical release wave updates may include:

• New features or modules across D365 Finance, Supply Chain, and Project Operations
• User interface changes or workflow enhancements
• AI-driven insights and reporting capabilities
• Global regulatory updates and localization improvements
• Platform upgrades that support better performance or integration extensibility

Microsoft publishes a detailed release plan with every wave, outlining what’s new and when each feature will become available. Some features are turned on by default, while others must be manually enabled using feature management. By the end of each wave, Microsoft enforces certain features system-wide, so organizations should monitor the plans and begin testing during early access windows whenever possible.

As part of the Dynamics 365 Finance and Operations release schedule, Microsoft delivers minor updates known as service updates focused on system maintenance rather than new features. These updates fall under the One Version model, which ensures all customers remain on a supported version of Dynamics 365 Finance & Operations (D365 F&O). Microsoft releases service updates four times per year, typically in February, April, July, and October, applying improvements across both the platform and application layers.

Service updates are designed to keep environments secure, stable, and compliant between major release waves. They include performance enhancements, bug fixes, and regulatory changes (such as tax or accounting updates), and may occasionally activate features held behind feature flags from earlier waves. Their primary purpose is to maintain operational continuity, reduce risk, and ensure readiness for future functionality—without introducing disruption to business processes.

Key details of the One Version policy:

• Release cadence: Microsoft releases four service updates per year typically in February, April, July, and October. These updates are cumulative and apply to both the platform and application layers.
• Mandatory cadence: You must apply at least two service updates per year to remain on a supported version.
• Flexibility to pause: You may pause one update cycle (skip one update), but you must apply the next one. You cannot skip two in a row.
• Auto-update windows: Microsoft provides two auto-update windows for each release, spaced four weeks apart. If you choose to pause, both windows are skipped, and your environment will be updated in the next cycle.

As another layer of the D365 Finance and Operations release schedule, Microsoft delivers quality updates, minor, targeted patches aimed at maintaining system reliability and performance. Often referred to as Proactive Quality Updates (PQUs), these updates address specific bugs, security vulnerabilities, and stability issues without introducing new features. Quality updates are released on a monthly cadence, and in some cases more frequently, and are applied automatically to all environments. Because they’re small, well-tested, and low risk, they usually require little to no downtime and are rarely disruptive. Their purpose is to correct issues between scheduled service or wave updates, ensuring a more resilient and consistent user experience.

Unlike release waves or service updates, quality updates cannot be skipped or paused. All Dynamics 365 Finance & Operations customers are automatically enrolled in the PQU process, and Microsoft applies the updates during predefined maintenance windows. These patches are not optional—they are a required part of staying current on the platform. Microsoft typically communicates the timing and contents of each quality update through the Microsoft 365 Message Center and Lifecycle Services (LCS). To support validation, early access to the update is often made available in sandbox environments about a week before production rollout, giving teams a brief window to perform targeted testing on critical business processes. In short, quality updates act as the stability layer of the release schedule—continuously fine-tuning the system with minimal overhead for internal IT teams.

The D365 Finance and Operations release schedule is designed to deliver continuous improvements through a coordinated mix of major and minor updates. Microsoft combines release waves, service updates, and quality updates to keep Dynamics 365 Finance and Operations current, secure, and aligned with evolving business and regulatory needs. This layered cadence helps organizations adopt new capabilities while maintaining system stability and performance year-round.

Release waves introduce significant features twice a year. In between, service updates provide quarterly platform and application improvements, while quality updates address issues through regular, targeted patches. Together, these update types support a proactive approach to system maintenance and readiness.

Planning ahead is essential to staying compliant with the Dynamics 365 Finance & Operations release schedule. These practical steps can help your team anticipate and adapt to upcoming changes with less disruption.

1. Map your update windows to business cycles: Align testing and deployment around critical periods like fiscal close or peak operational times. Avoid applying updates during GA or mandatory enablement dates that may overlap with high-impact workflows.
2. Use sandbox environments for early access testing: Testing new features in advance allows your team to validate critical processes and spot issues before production. Enabling early access for both release waves gives more control over adoption.
3. Validate all customizations before each update: Even service updates and PQUs can affect extensions or ISV solutions. Review and test these components in sandbox to catch potential conflicts early.
4. Stay proactive with the One Version policy: Microsoft requires you to apply at least two service updates per year to remain supported. You can pause one cycle annually, but must track timing and prepare for auto-updates and monthly PQUs.
5. Communicate updates with key stakeholders: Inform finance, operations, and IT teams ahead of each release to align expectations and readiness. Sharing testing timelines and upcoming feature summaries improves adoption and reduces surprises.
6. Document and audit every update: Maintain a clear record of what was tested, when it was deployed, and who approved it. This improves governance and supports internal reviews or compliance audits.
7. Work with a trusted D365 F&O partner: An experienced partner can guide you through update cycles with less risk and effort. They bring tools, validation processes, and deep platform knowledge to help your environment stay optimized and compliant.

Keeping up with the Dynamics 365 Finance & Operations release schedule takes planning, testing, and technical oversight, especially for organizations with limited IT bandwidth or highly customized environments. Partnering with an experienced Microsoft D365 F&O partner like Rand Group gives your team the support needed to stay current without disruption. With deep expertise in Dynamics 365 Finance & Operations, we help businesses manage the full update lifecycle, from release planning to validation, deployment, and user adoption.

Rand Group’s D365 Finance & Operations update services include:

• Release schedule planning and advisory: We help you monitor the D365 Finance and Operations release schedule, assess what’s changing, and align those changes with your internal business cycles.
• Testing and validation support: Before each wave or service update, we assist in applying preview builds to sandbox environments, validating business processes, and confirming customizations continue to function as expected.
• Post-update training and enablement: Once new features are live, we provide user training, documentation, and support to help your teams adopt improvements and unlock new capabilities quickly.
• Ongoing support and issue resolution: Should an update or quality patch trigger unexpected behavior, Rand Group offers rapid response and escalation services to resolve issues and maintain operational continuity.

With Rand Group as your trusted partner, you gain proactive support for every stage of the Dynamics 365 Finance & Operations release schedule, ensuring your ERP system remains stable, secure, and fully aligned with Microsoft’s ongoing enhancements.

• How many release waves does Microsoft deploy for Dynamics 365 Finance & Operations each year, and when do they occur?
  Microsoft delivers two major release waves per year as part of the Dynamics 365 Finance & Operations release schedule. Release Wave 1 runs from April through September, with public feature announcements in January and early access previews in February. Release Wave 2 spans October through March, with announcements in July and early access starting in August.
• How often are service updates released, and do we have to install all of them?
  Microsoft issues four service updates per year—typically in February, April, July, and October—to keep D365 Finance & Operations secure, compliant, and current. Under the One Version policy, businesses must apply at least two service updates annually to remain supported. You can pause one update per year, but the next one becomes mandatory. This flexible approach allows organizations to align updates with internal cycles without falling behind on compliance or platform support.
• Can I skip or delay a D365 Finance & Operations update if our organization isn’t ready?
  You have limited flexibility, and the rules vary by update type. For service updates, Microsoft allows you to pause one update per year, but you must apply the next one—you cannot skip two consecutive updates. For release waves, Microsoft automatically rolls out features to all environments by the end of the wave period, and there is no option to opt out. For quality updates, there is no ability to delay or pause; they are pushed automatically to ensure the platform remains stable and secure. While some flexibility exists for timing service updates, your organization should take advantage of sandbox testing and Microsoft’s two auto-update windows per release to better manage timing and reduce potential disruption.
• What are proactive quality updates (PQUs) in Dynamics 365 F&O?
  Proactive quality updates are minor, automated patches that Microsoft applies on a monthly (or more frequent) basis. These updates focus exclusively on bug fixes, security improvements, and performance corrections. PQUs do not introduce new features and cannot be opted out of—they are automatically applied during scheduled maintenance windows to all D365 Finance & Operations environments. They serve as a key component of the Finance and Operations release schedule, helping maintain platform stability with minimal disruption.
• How can we prepare for new updates or test upcoming Dynamics 365 features early?
  For release waves, early access begins about two months before general availability, allowing teams to test new features in a sandbox. For service updates, preview builds are made available in Lifecycle Services (LCS) roughly one week before the update is applied to production. Organizations should take advantage of these windows to validate customizations, run regression tests, and involve key users in testing. Proactive testing helps identify potential issues early and ensures smoother transitions across all update types in the Finance and Operations release schedule.

Staying ahead of the Dynamics 365 Finance & Operations release schedule requires more than just reacting to updates, it demands a clear plan. By understanding the timing and scope of release waves, service updates, and quality updates, your team can stay prepared, reduce risks, and take advantage of new functionality. Regular sandbox testing and internal communication ensure updates are adopted with minimal disruption.

If you need expert guidance, Rand Group can help you manage every aspect of the Dynamics 365 Finance & Operations update process. From planning and testing to deployment and user training, we tailor our support to fit your environment and priorities. Contact us today to learn how we can help you stay current, supported, and aligned with Microsoft’s release schedule.