After launch, a transit authority needs to watch how its new agent is performing. Which admin practice fits?

After launch, a transit authority should monitor agent usage and operational insights using Microsoft 365 and Power Platform admin center concepts. Launch is not the end of administration: usage, health, and operational signals tell whether the municipal agent is adopted, failing, or drifting. Monitoring after launch is how transit IT catches unused agents, error patterns, or capacity issues while the service is live.

Monitoring agent sessions and outcome rates after launch using Microsoft Purview data protection and retention policy concepts fails by concept—it's a data protection and retention activity, not a way to monitor agent usage and operational insights after launch. Monitoring agent usage and billing reconciliation after launch using Azure Cost Management scope and subscription metering concepts fails by concept—it's a cost management and billing activity, not a way to monitor agent usage and operational insights after launch. Monitoring agent activity and sharing trends after launch using Microsoft Intune device compliance and app rollout concepts fails by concept—it's a device management activity, not a way to monitor agent usage and operational insights after launch.

Exam caveat: AB-900 Domain 3 includes monitoring agent usage and awareness of Microsoft 365 admin center and Power Platform admin center concepts for agent operations. Don't confuse monitoring agent sessions and outcome rates using Microsoft Purview data protection and retention policy concepts, monitoring agent usage and billing reconciliation using Azure Cost Management scope and subscription metering concepts, or monitoring agent activity and sharing trends using Microsoft Intune device compliance and app rollout concepts with monitoring agent usage and operational insights.

Operational check: After transit agent launch, review usage and operational insights on a defined cadence in the relevant Microsoft 365 and Power Platform admin center views, note inactive or error-prone agents, assign an owner for each finding, and feed results into enablement or retirement actions rather than waiting for resident complaints.