June 17, 2026

The free ride is over: What Copilot Cowork’s new billing model means for your organisation

Steve Bedwell
Technical Specialist for Modern Work, Data#3

Copilot Cowork has quickly become one of the most talked-about additions to Microsoft 365. Since arriving in Frontier in March 2026, it has been Microsoft’s fastest-growing preview feature ever, and for a few months organisations have been delegating complex, multi-step work that used to swallow entire weeks, all at no additional cost.

Today, Microsoft has announced the global general availability of Cowork, alongside the introduction of a usage-based billing model.

For customers that had at least one user using Cowork through Frontier during the preview period, there is a grace period until 1 July 2026 to implement billing policies, with no additional charges during that time. For all other customers, usage billing begins with general availability. Cowork is off by default, giving admins the opportunity to set spending limits, allocate budgets and decide who should have access before turning it on.

For any organisation, the announcement is likely to prompt immediate questions about cost, control and access, particularly where Cowork has been trialled through Frontier and is already becoming part of day-to-day workflows.

We sat down with Data#3 Technical Specialist for Modern Work, Steve Bedwell, to break down what’s changing, why it matters and how Data#3 can support organisations with their next steps.

What is Cowork?

Steve: Copilot Cowork extends Copilot to support more complex, ongoing work that spans multiple steps and systems. Rather than responding to single prompts, it allows users to delegate longer‑running tasks, such as preparing reports, pulling together data from across the organisation or maintaining regular updates, and then review the output as the work progresses.

It sits alongside Copilot rather than replacing it and is designed for scenarios where work needs to be planned, executed and monitored over time, rather than completed in one interaction.

At Data#3, we’ve been using Cowork throughout its Frontier preview, and it’s quickly become one of those tools our team genuinely relies on day-to-day. It’s incredibly powerful and easy to see the impact, so much so that for many of us, it’s fast become something we can’t imagine working without, especially when applied to the right use cases with clear governance and outcomes in place.

What’s changing with Cowork?

Steve: Until now, Cowork has effectively been available within the broader Copilot experience without a separate usage charge, so users could access it without directly thinking about how much each interaction or task was consuming. Since its introduction earlier this year, that has made it feel more like an included capability than a metered service. The key change now is the move to a consumption-based model. While Copilot remains included in the Microsoft 365 Copilot licence, Cowork is shifting to consumption billing, based on usage.

In practice, that means moving away from a model where usage sat in the background and felt effectively unlimited for the end user, to one where every task executed in Cowork contributes to measurable usage costs rather than being absorbed under a fixed licence.

Why is Microsoft moving to a consumption model?

Steve: It comes down to cost and scale. Cowork performs long-running, multi-step workflows which require significant compute and access to underlying AI models. These costs vary depending on how heavily the platform is used.

Because usage can differ so widely between organisations and even individual users, Microsoft is moving to a model where customers pay for what they use.

Who does this impact?

Steve: The impact reaches across the organisation. IT will be responsible for configuring policies, controls and billing settings, while Business leaders will need to decide who gets access, how it’s used and how budgets are managed. End users will also feel the change, as they may need to work within usage limits set by the business and make sensible choices about when Cowork is the right tool and when Copilot will do the job.

This is something that needs to be planned across the organisation.

What does this mean in practice?

Steve: Organisations will need to actively manage usage. Microsoft is introducing tools like forecasting calculators based on usage profiles (light, medium, heavy), controls at the tenant, group and user level, and budgeting and limits with notifications and exception handling.

This allows organisations to allocate usage across departments and manage costs appropriately.

Is there any urgency for customers here?

Steve: Yes. Customers that used Cowork through Frontier need to implement billing policies before the grace period expires to retain access to Cowork. For all other customers, billing starts with general availability, so now is the time to review access, budgets and cost controls before enabling Cowork.

Is Cowork something everyone needs?

Steve: Not necessarily, but it’s not just for power users either. There are amazing use cases for Cowork that apply to many different roles. While Copilot will continue to handle most everyday needs, Cowork adds value wherever work is multi-step, ongoing or worth delegating. Adoption support is what turns Cowork into value, helping users build the skills to use it well and the judgement to know when it’s the right tool for the job.

What are the risks organisations need to consider?

Steve: The biggest risk is uncontrolled usage leading to unexpected costs. Without clear governance, a small number of users could significantly increase consumption. That’s why budgeting, monitoring and policy controls are essential from day one.

There’s also a broader challenge of understanding how AI usage fits into overall cloud and data strategy, particularly as consumption-based models become more common.

What are the next steps for organisations?

Steve: There are a few key steps I would recommend:

  • Assess business needs: Identify where Cowork provides real value.
  • Define user roles: Determine which users need advanced capabilities.
  • Set budgets and controls: Establish limits at organisational, department, and user levels.
  • Align IT and business: Collaborate on governance and implementation.
  • Plan for adoption: Educate users on when to use Cowork versus Copilot.

Ultimately, this is a shift toward more strategic AI usage. It needs planning, not just enablement.

How can Data#3 help?

Steve: This is where organisations often need guidance. At Data#3, we help across the full journey:

  • Assessment and planning: Understanding use cases, roles and expected usage, through our consultancy arm, Business Aspect.
  • Governance design: Setting up cost controls, policies and billing structures.
  • Technical implementation: Configuring the Microsoft environment and integrating controls.
  • Adoption and enablement: Helping users understand how to use Copilot and Cowork effectively.

Importantly, we bridge the gap between business and IT, ensuring organisations not only implement the technology, but use it in a way that delivers value while managing cost.

We are continually evolving our AI managed services to help organisations effectively govern, optimise, and realise value from AI through ongoing cost management, adoption support, and performance tracking.

The shift from Copilot to Cowork represents a broader move toward agentic AI and consumption-based models. While this introduces new complexity, it also unlocks significant opportunity for organisations to automate and scale work in new ways.

With the right planning, governance and support, organisations can adopt these capabilities confidently and maximise the value of their AI investments.

To discuss your next step following these changes or to learn more about Data#3’s AI services, contact your Data#3 Account Manager or get in touch with our team today.

Contact us

Information provided within this form will be handled in accordance with our privacy statement.