Microsoft · Power Platform admin center
Service updates in unified environments: why developers should test against two versions
- Who it affects
- Finance and Operations customers, partners and ISVs.
- What changes
- Production can take every update or every other update. You can skip one, not two.
- D365FO impact
- Customers run the latest version or the one before. Legal changes can arrive one cycle later.
This one is not about Portuguese tax. It matters for any developer who wants to test against the versions customers really run, and the Power Platform admin center (PPAC) has changed how that works.
What the docs say
For unified environments, Microsoft publishes the service update schedule and sends a Message center notice at least one week before a rollout. Production environments get two settings:
- Every update: the environment takes the next service update.
- Every other update: the environment skips one and takes the one after.
Microsoft’s own example: an environment on 10.0.47 set to every other update skips 10.0.48 and goes to 10.0.49.
Some other rules from the same pages:
- Microsoft releases four service updates a year, in February, April, July and October.
- Customers must take at least two a year. They can pause one update at a time.
- Sandboxes usually get an update 10 to 15 days before production. Before production updates, a check confirms that at least one sandbox in the tenant took the same update at least five days earlier.
- New environments are not eligible for updates in their first seven days.
- The production maintenance settings are in PPAC. Sandbox settings go through the Power Platform API.
What I take from it
You can skip one update, but not two. So a production environment is on the latest version or the one before it. The tenant’s sandboxes are at the latest or ahead of production.
An older Microsoft page for ISVs still talks about customers running “one of the last three monthly updates”. That was written for a monthly cadence. With the current rules I would plan for two versions, not three. This is my reading, so check it against your own customers’ settings.
What I would do as a developer
- Test on the latest version and on the previous one.
- If you ship a solution to several customers, build it on the oldest platform release you support. Microsoft says updates are meant to be binary backward compatible.
- Look at the schedule for your region. For service update 10.0.49, the published dates for West Europe are 12 and 13 October 2026 for sandboxes and 24 and 25 October for production.
- Remember that regulatory changes arrive inside service updates. A customer on every other update can get a legal change one cycle later. If a law has an enforcement date, check which version carries the change before that date.
Sources: Manage service updates for unified environments, Release schedule for service updates (unified environments), One Version service updates FAQ, Delivering ISV solutions using One Version.