Microsoft Copilot Cowork

How Cowork is billed

Cowork uses Copilot Credits, a single, pooled billing currency that meters AI usage across Copilot services and agents. Credits are shared at the tenant level, with policy controls to assign limits by group or user. Credit usage per task depends on the mix of tokens used, models used, data and tools invoked, and safety/policy checks performed.

Choose your billing model

You fund Credits two ways, and most organizations use both together.

How to think about the two:

• Prepaid first. An annual commitment gives the lowest per-credit cost. This is ideal once you’re confident in a baseline. If you already run Copilot Studio agents, this is likely where you’ll land, since you can pool credits across services.
• Pay-as-you-go as the safety net. At one cent per credit with no commitment, PAYG is the natural starting point if you don’t have usage history yet or want to pilot before committing volume.

Set up Copilot Credits

All credit-based billing is configured in the Microsoft 365 admin center: Copilot → Cost Management → Configuration. At a high level, here’s what you’ll do:

1. Create a billing policy and name it.
2. Scope it to all users, specific security groups, or individual users. Security groups are recommended for department-level control.
3. Set limits and alerts: choose an unlimited or limited monthly budget, define custom spend thresholds with estimated cost visibility, configure alert emails to admins and stakeholders, and apply optional per-user caps to protect the shared pool.
4. Select the agents and services the policy covers.
5. Set the billing method — prepaid credits or pay-as-you-go via an Azure subscription.
6. Review and activate. A consolidated screen summarizes scope, services, billing method, limits, and alerts before you go live.

Three key cost management scenarios

Three situations come up most often. Each maps to a control you have in Cost Management within the admin center.

1. One user is using the team’s credit pool: Apply a per-user hard cap within the group policy so no single user can drain the shared pool. Review usage by group to spot heavy users early, before they hit a limit.
2. A department exceeds its monthly allocation: Use a group-scoped policy with a hard limit targeted to a security group, and watch group usage so you can act before an overrun.
3. An agent is using premium services for routine tasks: Bind specific agents to a spend limit through policy, surface the cost-driving agent in the agents-and-services view, and apply per-agent caps.

Plan your budget with cost modeling

Before you set spending limits, model expected costs with your early adopters so your budgets reflect real usage rather than arbitrary caps. Follow the recommended steps below or use the Customer Cowork Estimator to help size your budget.

1. Identify a representative group of Champions for the roles you want to model.
2. Ask them to collect their key Cowork activities, how many times per week each is used, and the average Credit cost per activity.
3. Calculate weekly cost per role: cost per activity × frequency, summed across activities.
4. Use those numbers to set realistic group and user budgets in Cost Management — with confidence.

Prepare your tenant

Objective: Ensure your security and identity posture is ready for Cowork to take action.

• Confirm Microsoft Copilot licenses are assigned to the pilot group.
• Review SharePoint and OneDrive sharing in your pilot group’s sites. Tighten any broad “Everyone except external users” links on sensitive content.
• Verify that sensitivity labels, DLP, and retention policies cover the content the pilot group will work with.
• Brief your security and compliance partners on the Cowork audit trail and what to expect in Purview.

Select your users

Objective: Identify which users to enable Cowork for.

Determine the group of business users that will get the most value from this capability. Work with stakeholders and adoption staff to designate these people.

Enable and deploy

Objective: Make Cowork available to your pilot group with the controls you want from day one.

• Enable Anthropic models in MAC if you plan to use them.
• Set Cowork availability to specific users or groups and add your pilot security group.
• Deploy Cowork to the pilot group so it appears in their Copilot rail without manual install.
• Pin Cowork in the rail, so the pilot group sees it the first time they open Copilot.

Set budgets and policies

Objective: Turn on Copilot Credits with spend controls.

• Turn on credit-based billing for Copilot services and agents.
• Choose prepaid Credits, pay-as-you-go, or both — match the model your finance team uses elsewhere.
• Create a billing policy scoped to your pilot security group. For example, set a monthly budget and an alert at the 70% threshold.
• Apply user-level caps to protect shared capacity during the learning curve.
• Optional: add your IT, finance, and AI Leader stakeholders to the alert distribution list.

Communicate and scale

Objective: Turn the early adopters’ usage into a story you can share, then expand access with confidence.

• Share early outcomes with leadership: task volume, time saved, examples of completed work.
• Refine budgets based on observed patterns. Lift user-level caps where they create friction without protecting spend.
• Expand Cowork access to the next security group, then repeat the budget-and-monitor cycle.
• Send periodic feedback pulses so you hear when something is slowing users down.

Collect feedback

Objective: Watch the patterns, catch problems early, and build a repeatable governance rhythm.

• Add the Cost Management dashboard in MAC to your weekly IT operations review.
• Identify users approaching their cap so you can coach them before they hit it.
• Pull a monthly snapshot of usage by user and by group for your AI leader and CFO.
• Audit a sample of Cowork actions in Purview so the security team can verify policies are landing as expected.
• Define an escalation path for users who hit their limit mid-task and need more capacity.

What you can monitor today

Cost Management in the admin center gives you credit-usage visibility from day one:

• Overall usage — total Credit usage over time against your budget.
• Usage by user — per-user usage against limits, to spot heavy users early.
• Usage by group — group-level usage against group budgets.
• Usage by agent and service — which agents/services use credits.

Pair this with the Microsoft Purview audit log, where Cowork actions are recorded alongside the rest of your estate.

Perform service health reviews

Service health reviews (SHR) are where the implementation team and business stakeholders come together to review the insights from their AI transformation projects. Gather your AI Council members and stakeholders to understand usage patterns, challenges, and success stories. Use the Microsoft 365 admin center and the Copilot Dashboard data for these check-ins along. Use insights to alter continued deployment and adoption plans.

How Cowork is billed

Cowork uses Copilot Credits, a shared billing currency that meters AI usage across Copilot services and agents. Copilot Credits are managed through spending policies, monthly spending limits, and optional per-user limits. The number of Credits a task uses depends on factors such as the AI model, tokens processed, connected data and tools, and safety and policy checks.

Choose your billing model

The right billing model depends on your rollout strategy. Most organizations use a combination of prepaid and pay-as-you-go Copilot Credits.

When to use each billing model:

• Prepaid. Best for predictable, ongoing usage once you’ve established a baseline. An annual commitment provides the lowest per-credit cost, and credits can be pooled across Copilot services.
• Pay-as-you-go. Best for pilots, variable workloads, or organizations without usage history. With no commitment, it’s an easy way to get started before committing to prepaid credits.

Configure credit-based billing 

Configure credit-based billing in the Microsoft 365 admin center. You’ll create spending policies, assign users or groups, choose a billing method, set budgets and alerts, and review your configuration before activating it. 

1. Create a spending policy. Give the policy a descriptive name so it’s easy to identify later.  
2. Choose who the policy applies to. Scope it to individual users, security groups, or the entire organization. Security groups work well for managing pilot participants and department-level deployments.
3. Define spending policies and alerts. Set monthly spending limits, spending thresholds, and optional per-user limits to help manage credit consumption. 
4. Select the services to include. Choose which Copilot agents and services the policy should cover. 
5. Choose a billing method. Use prepaid Copilot Credits, pay-as-you-go through Azure, or both. 
6. Review and activate. Confirm your scope, services, budgets, alerts, and billing method before activating the policy.  

Plan your budget with cost modeling

Before you configure budgets and spending limits, estimate expected usage to create budgets that reflect real-world usage instead of arbitrary caps. Follow these steps or use the Customer Cowork Estimator to calculate your initial budget: 

1. Identify representative users. Select a group of Champions who represent the roles you want to model. 
2. Estimate typical usage. Ask each Champion to identify their key Cowork activities, how many times they expect to perform each activity per month, and the average Copilot Credit cost per activity. 
3. Calculate expected monthly usage by role. Multiply the average credit cost of each activity by its monthly frequency, then total the results for each role. 
4. Set initial budgets. Use these estimates to configure spending policies, monthly spending limits, and alerts in the Cost Management dashboard. 

Common cost management scenarios 

Here’s how to use Cost Management to address common spending challenges:  

1. One user is using the team’s credit pool: Apply a per-user hard cap within the group policy so no single user can drain the shared pool. Review usage by group to identify the highest-consuming users before they reach their limit. 
2. A department exceeds its monthly allocation: Use a group-scoped policy with a hard limit for the department’s security group. Monitor group usage so you can identify trends and adjust spending proactively.
3. An agent or service drives higher Copilot Credit usage during routine tasks: Use spending policies to control which users or groups can access specific agents and services, monitor agent and service consumption in the Consumption tab, and adjust spending policy limits or access where appropriate.

Prepare your tenant

Before launching a pilot, ensure that your tenant is ready for Cowork. 

• Confirm Microsoft 365 Copilot licenses are assigned to the pilot group. 
• Review sharing settings for the pilot group’s SharePoint sites and OneDrive files. Remove or restrict Everyone except external users links on sensitive content.
• Verify that sensitivity labels, data loss prevention (DLP) policies, and retention policies cover the content the pilot group will work with. 
• Brief your security and compliance partners on Cowork auditing and the information they can expect to see in Microsoft Purview. 

Select your users

Objective: Identify the users who will participate in your pilot.

• Determine which business users are likely to get the most value from Cowork.
• Work with stakeholders and your adoption team to designate the pilot participants.

Enable and deploy

Objective: Make Cowork available to your pilot group with the right controls from day one.

• Make Cowork available to your pilot security group. 
• Deploy Cowork to the pilot group so it appears in the Copilot navigation rail without manual installation. 
• Pin Cowork in the rail so pilot users see it the first time they open Copilot. 

Set budgets and policies

Objective: Configure Copilot Credits, budgets, and spending controls.

• Turn on credit-based billing for Copilot services and agents.
• Choose prepaid Credits, pay-as-you-go, or both based on your organization’s existing billing model.
• Create a spending policy scoped to your pilot security group. For example, set a monthly budget and an alert at the 70% threshold. 
• Apply per-user credit limits to protect shared capacity during the learning curve.
• Optional: add IT, finance, and AI leadership to the spending alert distribution list.

Communicate and scale

Objective: Use early results to inform broader deployment.

• Share pilot outcomes with leadership, including task volume, time saved, and examples of work completed with Cowork. 
• Expand Cowork access to the next security group, then repeat the budget-and-monitor cycle. 
• Send periodic pulse surveys to check in with users throughout the pilot. 

Monitor usage and collect feedback 

Objective: Monitor usage patterns, catch problems early, and build a repeatable governance rhythm.

• Add the Cost Management dashboard in the admin center to your weekly IT operations review. 
• Refine budgets based on observed patterns. Lift per-user limits if they’re limiting productivity without meaningfully reducing spend. 
• Identify users approaching their cap so you can help them avoid interruptions. 
• Pull a monthly snapshot of usage by user and by group for your AI lead and CFO. 
• Audit a sample of Cowork actions in Microsoft Purview so the security team can verify policies are working as intended. 
• Define an escalation path for users who reach their spending limit mid-task, including how they can request a limit increase and how admins will review credit requests or adjust spending policy limits. 

What you can monitor today

Cost Management in the admin center gives you credit-usage visibility from day one, including: 

• Overall usage — total Credit usage over time against your budget.
• Usage by user — per-user usage against limits so you can identify high-consumption users early.
• Usage by group — group-level usage against group budgets.
• Usage by agent and service — credit usage for each agent and service.

Pair the Cost Management dashboard with the Microsoft Purview audit log to review Cowork actions alongside other activity in your Microsoft 365 environment. 

Perform service health reviews

Service health reviews (SHRs) bring the implementation team and business stakeholders together to review insights from AI transformation projects. During these check-ins, assess usage patterns, challenges, and success stories using data from the Copilot dashboard. Refine your deployment and adoption plans based on those insights.