Microsoft is changing the way it delivers product updates.
For years, organisations using Dynamics 365 and the wider Microsoft ecosystem have become accustomed to release waves – defined periods where new features, functionality and platform improvements were announced.
Now, Microsoft is moving towards a more continuous approach to innovation, bringing updates together through a single ecosystem roadmap and giving organisations greater visibility of what’s coming, when it’s expected and how features are progressing.
So, what does this mean for organisations using Microsoft technology?
Why is Microsoft moving away from release waves?
Microsoft’s technology ecosystem has become increasingly interconnected. Dynamics 365, Microsoft 365, Power Platform, Copilot and the wider Microsoft cloud no longer operate as completely separate products.
AI is accelerating this shift further.
AI capabilities can work across multiple applications and data sources, while the speed of development means waiting for a traditional six-month release cycle is becoming less practical.
The new approach reflects this shift, with features published as they become available and greater visibility into where they are within the development and rollout process.
Continuous change doesn't mean losing control
Moving away from release waves doesn't mean new functionality will simply appear in your production environment without warning.
Organisations will still be able to manage features through appropriate development, testing and UAT processes before deployment.
The difference is the rhythm of change.
Instead of preparing for two significant release periods each year, organisations need to become comfortable with continuously reviewing new functionality and deciding what is relevant to them.
And importantly, just because a feature is available doesn't mean it needs to be enabled.
Start with business value
With new AI and Copilot capabilities arriving rapidly, it can be tempting to focus on what's new rather than what the organisation actually needs.
Before adopting a feature, start with the business case.
What problem does it solve? Does it improve an existing process? Will it benefit users? And is automation actually appropriate for that particular interaction?
Organisations should also consider how success will be measured. Whether the objective is saving time, improving quality, reducing manual work or enhancing the user experience, there needs to be a clear way of demonstrating value.
Ultimately, the question shouldn't simply be “Can we enable this?” but “What value will enabling this create?”
Keep security and compliance at the centre
Security and compliance become particularly important as AI capabilities increasingly work across organisational data.
Before enabling new functionality, organisations need to understand what information it can access, whether personal or sensitive data is involved and whether existing data governance policies remain appropriate.
Data quality matters too. AI can only generate outputs based on the information available to it, so incomplete or inconsistent data can affect the quality of the results.
Existing approaches to GDPR, data retention and consent may also need reviewing if information is being accessed or used in a new way.
Think about people as well as technology
New technology can also change how people work.
A feature might alter an established business process, require new documentation or introduce a different way for employees to complete a task.
Training therefore needs to form part of the implementation process – particularly with generative AI, where the way users prompt and interact with a tool can affect the quality and consistency of its outputs.
This is why enabling new functionality should be treated as a mini project, rather than simply switching something on.
Features can move through development, testing and UAT before reaching production, giving organisations an opportunity to assess integrations, data access, training requirements and expected outcomes along the way.
Creating a framework for continuous innovation
Microsoft’s move away from traditional release waves reflects a wider change in technology: innovation, particularly around AI, is becoming continuous.
That means organisations need processes that allow them to embrace new functionality without compromising security, compliance or business value.
The goal isn't to enable every new feature as quickly as possible. It's to create a clear framework for deciding what to adopt, why to adopt it and how to introduce it responsibly.
With the right governance, testing, training and measurement in place, organisations can turn continuous innovation into meaningful, measurable value.
Ready to explore what’s next?
At mhance, we help organisations get more from their Microsoft technology – from Dynamics 365 and Power Platform to data, AI and Copilot.
If you're reviewing upcoming Microsoft functionality or considering how new capabilities could fit into your technology estate, get in touch with our team.