Building and customizing solutions using Microsoft 365 Copilot APIs and tools
Yes—end users do not each need the Microsoft 365 Copilot add-on, but a document-grounded Agent Builder agent requires eligible Copilot Chat access and tenant usage-based billing for users without that add-on.
Microsoft 365 Copilot Chat is included with eligible Microsoft 365 subscriptions. Declarative agents based only on instructions or public websites have no additional consumption charge, while agents accessing shared tenant data such as SharePoint or Copilot connectors consume Copilot Credits for users without the Copilot add-on ^1^.
Supported configuration
- Verify each end-user license
- Confirm that the specific Microsoft 365 or Office 365 SKU provides Microsoft 365 Copilot Chat.
- Do not assume that every product described internally as a “basic” license is eligible.
- Copilot Chat is available at no additional cost to Microsoft Entra users with an eligible Microsoft 365 or Office 365 subscription ^2^.
- License the agent owner or enable tenant billing
- Keeping the Microsoft 365 Copilot add-on for the owner is a supported authoring option.
- Agent Builder is available to users with that add-on and can also be available in tenants where Copilot Studio pay-as-you-go is enabled ^3^.
- Authoring eligibility and end-user consumption are separate considerations; licensing depends on the capabilities, users, channel, and tenant billing configuration ^4^.
- Enable usage-based billing for organizational knowledge
- A Microsoft 365 or billing administrator must configure the tenant’s Copilot usage-based billing backed by an Azure subscription and billing policy.
- Include the intended non-Copilot-licensed users in the applicable billing policy/security group.
- These users can then access enhanced agents, with organizational-data usage charged as Copilot Credits ^5^.
- Share the agent
- Open the created agent and select Share.
- Add users or groups as Can chat, or enable Org-wide sharing for chat access if permitted by organizational policy.
- Copy and distribute the Chat link.
- A user still receives an error if their license or tenant billing configuration does not cover the agent’s configured capabilities ^6^.
- Grant access to the underlying content
- For SharePoint and OneDrive knowledge, users must retain permission to the source content; the agent respects existing permissions and sensitivity labels ^7^.
- Agent sharing does not automatically grant broad access to SharePoint content. Automatic source sharing is limited to specific security groups; otherwise, update file or folder permissions manually ^8^.
Embedded documents versus SharePoint documents
Agent Builder supports up to 20 files uploaded directly from a device, as well as SharePoint and OneDrive sources ^7^. However, the published cost guidance explicitly identifies SharePoint and Copilot connectors as metered shared tenant data; it does not state as precisely how every embedded-file configuration is classified.
Before rollout, test the exact agent with:
- One owner holding the Copilot add-on.
- One end user with only the intended eligible Microsoft 365 SKU.
- The final document-source type.
- The user included in the applicable billing policy.
Confirm that the user can add the agent, retrieve document-grounded answers, and that consumption appears under the expected Copilot Credits billing arrangement.
Usage-based billing is not supported in GCC or GCCH environments ^5^. Because licensing terms can change, validate the selected SKUs and billing model against the current licensing terms before purchasing or production deployment ^9^.
References
- Plan licensing and cost
- Prerequisites for managing agents in Microsoft 365
- Agents admin guide for Microsoft 365
- Choose between Agent Builder and Copilot Studio to build your agent
- Set up your development environment for your plugin
- Share and manage agents built in Agent Builder
- Add knowledge sources to an agent in Agent Builder
- Agent Builder overview
- License options for Microsoft Copilot