Would it be possible to add any rules to releases of updates to BC as "weekly 2nd Sunday of the month".
First scenario: customer in manufacturing wants to do updates on Sunday. When the new version is released, it is automatically scheduled on random Thursday, and I need to manually change it with every update.
Second scenario: customer requires that sandboxes are updated two weeks before production. Automatic scheduling installs updates first to production and next day to sandboxes. It must be controlled manually too.
Examples: Azure Maintenance Configuration schedule, Azure Automation Account schedule
Comments
The solution has been found by our own scripting. It would still be nice to have an official tool for this.We handle it with an Azure Automation runbook (PowerShell) that talks to the BC Admin Center API using an Entra app registration with Automation.ReadWrite.All consented across our tenants. It runs daily: for every environment with a pending update, it computes a target date and writes it back via the API's update-scheduling endpoint.The core rule is phased — sandboxes are always scheduled ahead of production, giving a validation window before the live environment moves. The runbook only touches dates Microsoft auto-assigned; anything a human deliberately picked is detected and left alone, and it never lets a production run ahead of its own sandboxes.
Category: Tenant Administration
Strongly agree.I have worked for over 10 years in an accounting services company managing around 100 customer environments across NAV 4.0, NAV 5.0, NAV 2009, NAV 13, 15, 16, 17, 18 and BC14 On-Premises.In my experience, those older on-premises versions have not caused anywhere near the same amount of operational disruption as the current online update model.The challenge is that accounting firms and service providers often manage large numbers of customers. When an update introduces a regression, the impact is multiplied across dozens or even hundreds of companies, creating a significant support burden with little warning and no additional resources.We need more control over update scheduling, better phased rollouts, and the ability to keep sandboxes ahead of production for a meaningful validation period.Not every update needs to land in the middle of the summer vacation season.
Category: Tenant Administration