One-version service update application frequency is short.
I would like to suggest that the frequency of applying one-version service updates should not be tight as it is now but should have some more spare time to adjust internal development to the service release.
This is because there are some situations that users cannot keep up with the service update schedule with the current frequency.
[Voice of customer]
Users is finding it very inconvenient that the version they are using is immediately taken out of service after the three versions have been suspended.
Users develop and validate add-ons and so on.
It will not be supported by Microsoft Support when a version is not supported.
Microsoft should understand the actual usage of D365FO by users and make the schedule of service update application more relaxed than the current frequency.