As announced with the update 4, Microsoft will release monthly updates so that new and existing environments can stay up-to-date with the latest innovations with a click of a button. Hopefully this make it easier to stay on the newest platform. We are also assuming and hoping that this approach in the future will extend to also cover business functionality (eg ApplicationSuite). A faster update cycle also results that there are more versions currently used in at customers. As seen here are all the official releases that Microsoft have made available for Dynamics 365 for operations. With a monthly update cycle the list will be extended quickly. Keeping track on versions does not give any actual customers value. But in a SaaS approach, creating faster and simplified updated on business functionality will require a better and more visible release policy, not based on build numbers.
We need to make this upgrade and update experience easier to understand and easier to follow. The work that the Microsoft Office and Windows team have done is a great example that I think is something we also should have for Dynamics 365: The introduction of release channels.
|
Update channel |
Primary purpose |
Feature updates |
Platform updates |
Security Updates |
|
Preview Channel |
Provide users to evaluate the newest features of Dynamics 365 as soon as possible. The channel is only available through an insider program, and is not deployable into a production environment. |
Weekly |
Weekly |
Weekly |
|
First Channel |
Provide users with the newest features of Dynamics 365. |
Monthly |
Monthly |
Monthly |
|
Current Channel |
Provide users with the released and stable features of Dynamics 365. |
Every 3 months |
Monthly |
Monthly |
|
Deferred Channel |
Provide users with new features of Dynamics 365 only a few times a year. |
Every 6 months |
Monthly |
Monthly |
What channel you would like to have should be a setting in LCS, and the customers can switch between the channels as wanted. Visually the release and update schedule could then look something like this.
With the introduction of Microsoft AppSource and for ISV’s this would mean that they could commit to a specific channel, and “front-runners” like myself would have early access to the newest and hottest. Some customers are deadly serious about stability, and new features could potentially cripple business processes. In this way customers can for them self’s decide their speed for adding new functionality.
Dear Microsoft; Can we have something like this also for Dynamics 365?
