Copilot Licensing: Free vs Credits

Key insights

• Copilot Credits replaced message-based limits on September 1, 2025.
  The system now measures the compute and complexity of each AI action, so one "message" can use different credit amounts depending on the task.
• Copilot Chat (free) remains included with some Microsoft 365 plans for basic chat and web-style queries.
  Advanced features, custom agents, and high-compute tasks move into paid credit consumption or require specific licenses.
• Microsoft 365 Copilot license unlocks extra features like Work IQ and lets licensed users run Copilot Studio agents in Teams or SharePoint without consuming billable credits when deployed to those channels.
  Organizations should assign this license to frequent end users to reduce credit costs.
• Copilot Studio offers a free "maker pass" experience to build agents, but running those agents often consumes credits unless run by users with the right Microsoft 365 Copilot license.
  Studio also has trial and user-license options for creators.
• Copilot Cowork now uses Copilot Credits, while GitHub Copilot Credits remain a separate pool for developer-focused usage.
  Microsoft Scout requires GitHub-related licensing or integration, so teams must plan which credit pool and accounts they will use.
• Purchase and cost-control options include prepaid credit packs, pay-as-you-go Azure meters, and committed plans.
  To control costs, pick the right tool (Chat vs Cowork vs Scout vs Studio), monitor credit usage, deploy agents to Teams/SharePoint for licensed users, and use prepaid or commit plans if you need predictable billing.

Video Summary and Context

In a recent YouTube presentation, Shane Young [MVP] lays out Microsoft’s updated Copilot licensing in clear, practical terms. He explains how Microsoft moved from message-based access toward a usage-based system centered on Copilot Credits, and he shows what remains free versus what now consumes credits. Consequently, the video helps IT leaders and makers decide the right license and deployment path for their teams.

Moreover, Shane highlights where common tools fit into the new model and why the change matters for budget planning. He makes the distinctions accessible by walking through concrete examples and common scenarios. Therefore, the piece serves as a helpful guide for both evaluators and operational teams navigating the shift.

How the Copilot Credits Model Works

Shane describes Copilot Credits as a unified billing unit for advanced Copilot features, replacing the old "message" counting method as of September 1, 2025. He explains that credits measure computational work rather than dialog turns, so complex AI actions like agent runs or large document summarizations consume more credits than simple chats. As a result, organizations must think in terms of compute consumption instead of message counts.

In addition, Shane covers purchase methods: prepaid credit packs, pay-as-you-go meters through an Azure subscription, and pre-purchase commitments for predictable use. He notes that one advantage of prepaid plans is cost predictability, while pay-as-you-go suits variable workloads. However, he also warns that unpredictable agent behavior can still cause unexpected spend without monitoring and governance.

Licenses, Roles, and Where Credits Apply

The video clarifies several licensing points that often confuse buyers. First, basic Copilot Chat remains available in many Microsoft 365 plans at no extra credit cost for routine tasks, but advanced features typically consume credits. Second, a Microsoft 365 Copilot license unlocks additional capabilities and, importantly, lets licensed end users run Copilot Studio agents deployed to Microsoft 365 channels without consuming billable credits in certain contexts.

Shane also explains that creating agents in Copilot Studio usually requires a maker license but does not automatically impose credit costs for the maker role itself. Meanwhile, collaborative experiences like Copilot Cowork now count against Copilot Credits, and Microsoft Scout has its own GitHub-related licensing requirements. Therefore, teams must map user roles and deployment channels carefully to predict cost flows.

Tradeoffs and Practical Challenges

Shane emphasizes the tradeoffs inherent in the credits model. On one hand, credits offer granular cost control and unified billing across Copilot Studio and AI Builder, which simplifies chargebacks and budgeting over time. On the other hand, they increase operational complexity because administrators must estimate credit consumption per agent and manage multiple purchasing options to avoid overspend.

Furthermore, he points out technical challenges such as measuring the computational complexity of custom agents and balancing contextual richness against cost. For example, adding long document context or multi-step automation enhances outcomes but consumes more credits. Consequently, teams face a balancing act between delivering rich AI experiences and maintaining predictable costs.

Tips, Recommendations, and Governance

To manage the new model, Shane recommends several practical steps. First, start small: prototype agents on pay-as-you-go to observe actual credit use before committing to prepaid packs. Second, design agent logic and prompts to be efficient, and limit unnecessary context where possible to reduce consumption. In addition, tagging and monitoring usage helps identify expensive agents and optimize them over time.

He also advises combining licensing approaches: use prepaid packs for steady baseline workloads and pay-as-you-go for spikes. Finally, establish governance policies that define who can publish high-cost agents and require regular reviews of credit consumption. By following these steps, organizations can harness powerful Copilot capabilities while keeping costs under control.

Conclusion: Choosing the Right Tool for the Job

In conclusion, Shane Young’s video translates a complex licensing shift into actionable guidance for decision makers. It highlights that while some Copilot features remain free, advanced capabilities increasingly rely on Copilot Credits, and that different tools—whether Copilot Chat, Copilot Cowork, Microsoft Scout, or Copilot Studio—serve distinct needs and cost profiles. Therefore, teams should match the tool to the business requirement and plan purchases accordingly.

Overall, the update means more precise billing and better scalability, yet it requires clearer governance and careful design to avoid surprises. Shane’s walkthrough helps readers weigh the tradeoffs, anticipate challenges, and adopt licensing strategies that balance capability, cost, and control.

Keywords

Copilot licensing explained, Microsoft Copilot pricing, Copilot free vs paid, Copilot credits cost, Copilot subscription plans, Copilot licensing for business, Copilot billing and credits, Copilot pricing tiers