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.
During a CIJ implementation, it is common for purposes and topics to be created in the early stages of the project, which may require changes later on. If you ultimately decide that a particular purpose or topic is no longer needed, it cannot be deleted. As a result, it remains visible in the consent component on the contact form. This is not desirable when you are simply configuring the product and want to go live with only the purposes and topics that will actually be used.
In addition to this issue, when the production orders are linked using pegged supply line type in the BOM. Resetting the status of the parent production order to "Created" to add a route will remove the child production orders which results in losing data and can impact scheduling, costing, and planning.