Licensing is an architecture input, not a procurement detail. The agreement you buy through decides where Azure commitments, cost allocation and billing scopes can sit, and the Microsoft 365 plan decides which identity, endpoint, email and data controls you can design with. This guide maps EA, MCA and CSP to Azure billing structure, and E3, E5, the $12 suites and E7 to the security designs each one unlocks, checked against Microsoft's documentation in September 2026.
Microsoft 365 Copilot and its agents are paid for in three different ways, and each one bills to a different place: per-user seats on the Microsoft 365 invoice, prepaid Copilot Credits allocated to Power Platform environments, and pay-as-you-go charges on an Azure subscription. This guide explains the three cost shapes, the controls Microsoft provides for each, and a chargeback model built on them, checked against Microsoft's documentation in September 2026.
Once you have decided to extend Microsoft 365 Copilot, there are three ways to do it, and they are not interchangeable. Copilot connectors change what Copilot knows, declarative agents change how it behaves, and custom engine agents replace its engine. This guide compares the three on licensing, governance and who carries the risk, with every claim checked against Microsoft's documentation in September 2026.