Discussion on "The AOS Math That Kept One Admin Up At Night - And Why PPAC's New F&O Details UX Finally Puts It To Rest"

Rakesh Darge · 2026-09-08T10:06:01.214Z

It was 11:40 PM when the message landed in a Dynamics 365 community channel. "We currently have one LCS environment with around 900 users that consumes 8 Interactive and 4 Batch AOS instances, and ano

The explanation of the AOS math and PPAC’s new F&O details is an interesting look at how a complicated admin problem can become much easier to understand through better UX. It would be useful to see more examples of how the new interface reduces the manual calculations and makes the underlying values clearer.

As a D365 Admin, I'm happy to read that someone has any kind of information about these new fields in PPAC we are seeing...

Can you share how you learned about this information? I've been searching online and can't much at all about the new UX fields we are seeing. Scheduled updates was visible starting last week and now this week we are seeing Application / Platform version. Another observation is that these fields are only visible with an elevated role in PPAC. An environment system administrator cannot see them.

Hi Paul, thanks for reading and for the detailed observations - this is genuinely useful data from the field.

On sourcing: most of what I shared came from poking around PPAC as these fields rolled out, cross-checking what's visible in the UI, plus conversations in the MVP community, my own experience, and dialogs with the support team, and MS Office hours meetings. Nothing formally documented yet that I've found either - this still feels like it's ahead of the public docs.

Your point about role visibility is a really important catch. Can you please share which specific role? In my case, as a system admin in PPAC, I can see it.

Search Hashnode

The AOS Math That Kept One Admin Up At Night - And Why PPAC's New F&O Details UX Finally Puts It To Rest

Responses(3)