Emergency-management needs operational monitoring awareness for agents beyond Microsoft 365 admin center alone. Which additional admin center concept is in scope?

Emergency-management should include Power Platform admin center awareness for agent operational monitoring alongside the Microsoft 365 admin center. Agent operations are not confined to a single portal: Microsoft 365 admin center concepts cover important administration and lifecycle views, while Power Platform admin center concepts add operational monitoring awareness for agents in that ecosystem. Knowing both surfaces is the fundamentals-complete answer for monitoring beyond Microsoft 365 admin center alone.

Using Microsoft Entra admin center awareness for agent operational monitoring alongside Microsoft 365 admin center fails by concept—Entra admin center is an identity scope, not the operational agent monitoring that Power Platform admin center adds alongside Microsoft 365 admin center. Treating Microsoft Purview compliance center awareness for agent operational monitoring alongside Microsoft 365 admin center as the answer fails because Purview compliance scope is governance and compliance, not the AB-900 operational monitoring answer that pairs Microsoft 365 admin center with Power Platform admin center. Using Azure AI Foundry portal awareness for agent operational monitoring alongside Microsoft 365 admin center as the primary agent pairing fails for the same reason: wrong system class entirely.

Exam caveat: AB-900 Domain 3 explicitly pairs Microsoft 365 admin center and Power Platform admin center awareness for agent administration and monitoring. Remember “alongside Power Platform admin center,” not “alongside Microsoft Entra admin center,” “alongside Microsoft Purview compliance center,” or “alongside Azure AI Foundry portal.”

Operational check: Map which emergency-management agents are visible in Microsoft 365 admin center versus which operational insights appear in Power Platform admin center concepts, grant the ops team least-privilege access to both as policy allows, define a joint monitoring checklist, and verify after the next agent change that both surfaces still show expected status and usage signals.