# The AOS Math That Kept One Admin Up At Night - And Why PPAC's New F&O Details UX Finally Puts It To Rest 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 another with fewer than 100 users consuming 6 Interactive and 8 Batch AOS instances. To be honest, I was expecting to run into capacity issues when migrating to PPAC."* Anyone who has planned a PPAC migration for a large F&O tenant knows that feeling. You have the LCS numbers memorized. You have a spreadsheet somewhere tracking AOS counts against user load. And you are about to move that entire topology into a new admin surface where, frankly, the visibility into "what am I actually getting" has never been as sharp as it needed to be. That is about to change. ![](https://cdn.hashnode.com/uploads/covers/6154a77b414f78089df3d420/16a8c420-e2da-4621-b7be-a62a747d923a.png align="center") ## **What's Actually Rolling Out** Microsoft's Dynamics 365 engineering team confirmed that the **F&O Details UX in PPAC (Power Platform Admin Center)** is rolling out in phases over the coming two weeks. This isn't a cosmetic refresh - it's the first-time architects and admins get a native, PPAC-side view into the AOS topology that has historically lived buried in LCS and support tickets. Three things are worth flagging for anyone running D365 Finance & Operations at scale: * **F&O Details UX** - rolling out and next across PPAC environments * **SQL Write Access in Sandbox** - confirmed as "coming soon," a capability many architects have been requesting for data-seeding and debugging scenarios * **Public Power Platform API with SDK and connector support** - landing the first week of August, opening the door to programmatic environment management and automation for F&O the same way Power Platform admins have had for Dataverse environments If you want to see it today, it is simple: add .preview. to your PPAC URL right after admin. [admin.preview.powerplatform.microsoft.com](http://admin.preview.powerplatform.microsoft.com) or [admin.powerplatform.microsoft.com](http://admin.powerplatform.microsoft.com) That one change unlocks the new experience for early explorers. ### **Story One: "Does 0 Batch AOS on UDE Mean Something Is Broken?"** Here's a scenario every solution architect has hit during development. You spin up a **UDE (Unified Development Environment)** for X++ debugging, open the new F&O Details UX, and see **0 Batch AOS** listed. Panic sets in for a second. *Did the deployment fail? Are batch jobs going to silently queue forever?* The real story, once clarified by the engineering team, is far less dramatic - and it's exactly the kind of nuance the old topology views never made obvious: UDE is a special topology configuration that requires a single AOS for you to debug X++. It will always show just a single AOS, and it's dual-mode - meaning that one AOS handles both interactive and batch processing simultaneously. In other words: 0 Batch AOS on a UDE isn't a gap in your environment. It's by design. A single dual-mode AOS is doing double duty, and your batch jobs are executing just fine on it. This is precisely the kind of question the new F&O Details UX is built to pre-empt. Instead of an admin second-guessing a raw number and escalating a support ticket, the UI can now surface topology context inline - so "0 Batch AOS" reads as "expected for UDE" rather than "something's wrong." ![](https://cdn.hashnode.com/uploads/covers/6154a77b414f78089df3d420/f5f9493b-a1d0-4a32-8e33-e21c731ad84d.png align="center") ### **Story Two: The 900-User Migration and the AOS Math Nobody Could Confirm** This is the story that opened this post, and it's worth sitting with because it's the exact anxiety every architect carries into a PPAC migration. The admin's LCS environment showed **10 AOS instances** allocated based on licensing. In PPAC, the same environment now displayed **10 Interactive AOS and 10 Batch AOS** - and the natural question was: *is that 10 total, split across both, or 20 total, 10 of each?* That's not a small distinction. For an environment carrying 900 users and consuming 8 Interactive + 4 Batch AOS in production, the answer determines whether a migration is safe or whether it triggers a capacity crisis on day one. The confirmed answer: Interactive and Batch AOS instances are allocated independently. Up to 10 Interactive AOS instances and up to 10 Batch AOS instances - a total capacity of 20, not a shared pool of 10. For the admin who asked the question, this was the difference between dreading a migration and walking into it with confidence. Their production environment's real consumption - 8 Interactive and 4 Batch - sat comfortably inside independent ceilings of 10 and 10, rather than competing against each other inside a single shared cap of 10. This is the story that makes the case for the F&O Details UX better than any feature list could. Before this rollout, this kind of clarity required a forum post, a wait, and a confirmation from someone at Microsoft. After this rollout, that math is meant to be visible directly in PPAC - no guesswork, no escalation, no 11:40 PM messages into a community channel hoping someone with the answer is still awake. ## **Why This Matters for Architects Planning PPAC Migrations** If you're a Solution Architect sitting on an LCS-to-PPAC migration roadmap - and most of us are, in some form, this year - here's what this rollout changes in practical terms: * **Topology transparency moves left.** You no longer need to infer AOS allocation behavior from tribal knowledge or support escalations; it's becoming visible in the admin surface itself. * **Capacity planning gets more defensible.** Independent Interactive/Batch ceilings, once confirmed only informally, are exactly the kind of detail that belongs in a migration runbook - and now belongs in the UI too. * **UDE behaviour stops looking like a bug.** Dual-mode single-AOS topology for debugging environments is now something the UX can contextualize, not just display as a raw, alarming zero. * **The roadmap keeps compounding.** SQL write access in sandbox and a public API with SDK/connector support signal that PPAC is being built out as the durable, long-term control plane for F&O - not a lightweight LCS mirror. ## **Try it out:** If you're managing F&O environments today, there's no reason to wait for the rollout to reach you organically. Point your browser at: [admin.preview.powerplatform.microsoft.com](http://admin.preview.powerplatform.microsoft.com) Walk through your own environment topology. If you've got a migration on the calendar, this is the moment to reconcile your LCS numbers against what PPAC now shows - before you're the one posting the 11:40 PM question. And keep an eye out for SQL write access in sandbox and the public API landing in early August. Between the three, this is shaping up to be one of the more consequential quarters for D365 FO environment management in recent memory. ## **Thank you for reading - Let's Connect!** Thank you for reading this piece. If you enjoyed it, please let others know. Hit the subscribe button to read more posts from this blog. [**LinkedIn**](https://www.linkedin.com/in/rakeshdarge/), [**Twitter**](https://twitter.com/DargeRakesh?s=08), [**YouTube**](https://www.youtube.com/user/rakeshdarge/videos) Stay tuned!