I have seen several requests where partners require different approaches to controlling BaseApp updates. While Feature Update Management represents a significant step forward, it still does not fully address all partner needs.

With a few additional enhancements, the Admin Center API could better support partners in building robust custom solutions. At the moment, the data returned by Get Updates endpoint is not sufficient for informed decision-making. In particular, the following information is missing:

1)Who scheduled the update

It would be extremely helpful to know who scheduled a given update. This would allow us to distinguish whether the update was scheduled automatically by MS, by a partner via the API (for example, through an Entra application), or manually by a user in the Admin Center.

This distinction is critical. For instance, if an update was scheduled automatically, we might want to reschedule it according to our own rollout plan. However, if the update was already intentionally scheduled by a user or another application, we should not override that decision. Even a simple indicator of the scheduling source would greatly improve our ability to act responsibly and avoid unintended conflicts.

2) When the update became available

We have observed that update availability may differ depending on factors such as version, country, or possibly even specific tenants or environments. 

Having the exact availability date exposed via the API would enable better planning and more precise scheduling on the partner side.

3) Improved update states

Currently, all entries appear as “Scheduled,” even those that have already been successfully applied. While this is workable, it would be much clearer to distinguish completed updates using states such as “Applied” or “Finished.” 

Improving the clarity of update states would significantly enhance the usability and interpretability of the API data.

Overall, these seem like relatively small additions - particularly the first two - but they would have a substantial impact. 

They would make the update endpoint easier to consume, reduce the need for complex internal logic, and enable partners to build better, safer, and more predictable update management solutions.