A company wants to deploy a Copilot Studio agent on their internal SharePoint intranet site accessible to 500 employees. The IT manager asks which licensing model applies to this scenario. Which statement correctly describes the licensing for internal users accessing a Copilot Studio agent embedded on SharePoint?

Copilot Studio licensing uses a consumption-based model at the tenant level, not a per-user seat model for end consumers.

Option C is correct. Organizations purchase a Copilot Studio capacity add-on (previously called Power Virtual Agents capacity) at the tenant level. This capacity is measured in messages or sessions depending on the SKU. Microsoft 365 licensed employees can interact with agents without needing individual Copilot Studio licenses — the consumption charges are tracked against the tenant-level capacity purchase. The agent builders/administrators need Copilot Studio maker licenses, but not the end users.

Option A is incorrect. End users (the 500 employees) do not need individual Copilot Studio per-user licenses to chat with an agent. Only the makers (those who build and manage agents) require maker access licenses.

Option B is incorrect. Microsoft 365 licensing does not include Copilot Studio agent interaction capacity. SharePoint Online being included in M365 covers the SharePoint platform, not the AI agent interaction credits consumed when users chat with a Copilot Studio agent embedded on a SharePoint page.

Option D is incorrect. There is no blanket 'free' tier for internal agents. Power Automate flow calls from agent topics consume flow runs (which have their own licensing), and connector calls are also subject to their respective licensing rules. The agent itself still requires message capacity regardless of whether flows are involved.

Exam tip: AB-620 tests licensing awareness. Distinguish between maker licenses (who builds agents) and consumer capacity (what it costs when users talk to agents).