School district IT and finance disagree about who owns Copilot pay-as-you-go billing policy decisions. Which fundamentals framing is correct?

School district IT and finance should jointly own monitoring and managing pay-as-you-go billing policies so technical enablement and budget controls stay aligned. IT understands feature enablement, connectors, and usage drivers; finance owns appropriations and invoice validation. Shared ownership prevents "IT turned it on" versus "finance saw the bill" gaps that produce surprise invoices on metered Copilot.

Jointly managing pay-as-you-go billing policies in Azure Cost Management fails because policies are created and managed in the Power Platform admin center where the Azure subscription is linked, while Azure Cost Management only reports on costs and cannot configure the billing policy. Jointly configuring pay-as-you-go rates per agent in Copilot Studio fails because rates are fixed Microsoft meters that cannot be set per agent, while Copilot Studio builds agents and the pay-as-you-go link to Azure is managed as a billing policy in the Power Platform admin center. Jointly monitoring pay-as-you-go billing policies through Microsoft Purview fails because Purview governs data security and compliance, not metered billing, while policy monitoring and usage controls live in the Power Platform admin center with Azure cost views.

Exam caveat: Joint ownership is an operating-model answer at fundamentals depth; exact RACI charts vary by district. Keep policies, alerts, and monthly reviews on a shared calendar regardless of who clicks the admin blade.

Operational check: Name an IT owner and a finance owner for Copilot PAYG policies, schedule a monthly usage-and-guardrail review, and confirm billing policy monitoring stays in the Power Platform admin center with Azure cost views rather than in Microsoft Purview.