How the New Copilot App Changes Your Microsoft Licensing Budget

In this blog post How the New Copilot App Changes Your Microsoft Licensing Budget we will explain why Microsoft’s latest Copilot changes could make your AI bill less predictable, even if your user count stays exactly the same.

At a high level, the new Microsoft Copilot app brings AI chat, document creation and delegated work into one place. The important budget change is Cowork, which can complete multi-step tasks across Microsoft 365 and uses a consumption model called Copilot Credits.

This means Copilot is no longer only a fixed per-user licence. For organisations using Cowork, the total cost can include the base Microsoft 365 Copilot licence plus variable charges based on how much work the AI performs.

What changed in the new Microsoft Copilot app

Microsoft announced the redesigned Copilot app on 25 September 2026. Its new Home experience brings Chat and Cowork together, while Office in Copilot lets users create and edit Word documents, Excel workbooks and PowerPoint presentations without constantly moving between applications.

Chat is designed for quick questions, summaries and drafts. Cowork is designed for work you delegate, such as preparing an RFP response, producing a customer briefing or coordinating a reporting process across multiple files and applications.

Microsoft is also introducing Code, which helps people build applications and automations using plain-English instructions, and Autopilot, a more proactive assistant that can continue working in the background. Availability will vary as these capabilities move through Microsoft’s rollout and preview programs.

We covered the broader product announcement in what Microsoft’s new Copilot changes mean for SMBs. The issue we are focusing on here is what happens when these new capabilities meet your licensing budget.

The technology behind Cowork in plain English

Cowork is what Microsoft calls an agentic system. That simply means it can plan and carry out a series of actions instead of responding with text and waiting for the next instruction.

If you ask ordinary AI chat to prepare a customer briefing, it might give you an outline. Cowork can potentially find the relevant emails, review meeting notes, collect information from approved files, create the briefing document and prepare a message for the account team.

Behind this is Work IQ, Microsoft’s intelligence layer for understanding workplace information. It uses the Microsoft 365 content a person is already allowed to access, including emails, meetings, documents and Teams conversations, to provide context for the task.

A typical Cowork task follows four broad steps:

1. Understand the outcome. Cowork interprets what the user is trying to achieve.
2. Build a plan. It breaks the request into smaller actions and selects suitable AI models and tools.
3. Perform the work. It searches approved information, creates content and coordinates actions across Microsoft 365.
4. Request approval. The user can review important actions before Cowork sends messages or makes significant changes.

This can save considerable time, but it also requires more computing work than answering a simple chat question. That additional work is why Copilot Credits matter.

Copilot Credits create a second layer of cost

Microsoft calls its usage unit a Copilot Credit. Credits measure the work performed by supported AI services, including Cowork.

The number of credits used can vary according to the selected AI model, the amount of business information reviewed, the number of tools called and how long the task runs. A short task using one document will normally consume less than a process involving dozens of files, several applications and multiple outputs.

For business use, Cowork requires an eligible Microsoft 365 Copilot licence as well as usage-based billing. Organisations can use pay-as-you-go billing, prepaid options or supported combinations, depending on their agreement and Microsoft setup.

The basic budgeting formula is:

Monthly Copilot cost = Fixed user licences
 + Copilot Credits consumed
 + Applicable taxes and currency adjustments

Microsoft’s public pay-as-you-go reference price is currently US$0.01 per Copilot Credit, although Australian pricing, exchange rates, GST and commercial agreements can affect the amount you actually pay. Confirm your contracted rate rather than building a board budget from a public US price.

This builds on the packaging issues discussed in our Microsoft 365 Business with Copilot licensing update. The key difference is that you now need to model both who has a licence and what those users ask Cowork to do.

Why apparently small tasks can produce budget surprises

Usage varies significantly between employees

Two people with the same licence may create very different costs. One might use Cowork twice a month, while another delegates complex research, reporting and document production every day.

Allocating the same monthly allowance to every role may therefore waste credits in some departments while restricting teams that can produce measurable value.

Credits are shared across supported services

Copilot Credits can be pooled at the organisation level across supported Microsoft AI experiences. Without good reporting, finance may see a growing total but struggle to identify which team, task or service produced it.

This is similar to the governance problem discussed in how GitHub AI Credits turn Copilot spend into a board metric. AI consumption needs an owner, a budget and a way to connect cost with business value.

A spending policy also controls access

Microsoft’s spending policies are not just financial limits. For Cowork, being included in a relevant spending policy can grant access to the service.

Setting a very low credit limit is not the same as blocking a user. If someone should not use Cowork, they should be excluded from the policy or group that provides access.

An illustrative 200-person business scenario

Consider a 200-person professional services company with 60 Microsoft 365 Copilot users. It enables Cowork for all 60 because the existing Copilot licences have already been approved.

Most employees use it lightly, but the sales team starts delegating tender responses and the operations team uses it for weekly reporting. A few complex users quickly account for most of the consumption.

If 25 active users average 1,500 credits each during the month, that is 37,500 credits. At the public US pay-as-you-go reference rate, the variable component would be US$375 for that month, on top of existing licences.

That amount may be excellent value if it removes dozens of hours of manual work. The problem is not the cost itself; it is approving a flat licensing budget and discovering the consumption cost later.

Five steps to control your Copilot budget

• Begin with a controlled group. Give Cowork access to employees with clear use cases instead of enabling every Copilot user immediately.
• Set limits and alerts. Configure organisation and user-level spending controls, then alert IT and finance before limits are reached.
• Review automatic access. Check whether spending policies automatically include future Copilot services. New capabilities should be reviewed before they inherit a budget.
• Measure cost per outcome. Compare credit consumption with time saved, turnaround improvements or revenue supported.
• Review permissions first. Cowork can only be as well governed as your Microsoft 365 data. Remove outdated access and excessive file sharing before allowing AI to work across it.

Users can enter /cost within a Cowork task to see an approximate credit total. This is useful for awareness, but the Microsoft 365 administration dashboard should remain the source used for budget monitoring and reporting.

Licensing and security now need one conversation

Cowork can improve productivity, but broad access to poorly organised information creates risk. Australian organisations should assess it alongside the Essential Eight, the Australian Government’s cybersecurity framework, as well as privacy obligations and internal information-handling policies.

This is not simply a licence purchase. It involves identity, device security, data permissions, cost controls and employee training.

CloudProInc approaches these reviews with more than 20 years of enterprise IT experience across Microsoft 365, Azure, Intune, Microsoft Defender, OpenAI, Claude and Wiz. As a Melbourne-based Microsoft Partner and Wiz Security Integrator, we can help connect licensing decisions with practical security and financial controls.

If you are unsure whether the new Copilot app will save money or quietly add another variable cloud bill, we are happy to review your licences, Cowork access and likely credit consumption with you—no strings attached.