In a recent LinkedIn post, Clare Kitching discusses Microsoft Copilot’s expanding feature set and the costs that can accompany it. This article reports on Kitching’s observations in that post; it is not written by her. She describes a rollout that mixes familiar updates with features that use pay-per-use credits.
“Copilot continues to do more than you expect. Unfortunately, it also costs more than you expect too.”
Familiar tools, new names and capabilities
Kitching says Microsoft has been rolling out features announced in September, with updates appearing gradually in users’ tenants. Some changes, she notes, mainly reshape how existing capabilities are organized. Agents are becoming plugins, while Notebooks are now Workspaces intended for teams. In her description, personal projects in Cowork remain private to their owner.
She also points to inbox triage, which lets users ask Copilot to move, archive or file messages. Kitching says Copilot asks for confirmation before acting on more than five emails. These examples illustrate the range of workflow changes users may encounter as the product evolves.
Where usage-based charges enter
Kitching’s central concern is the distinction between features included in a licence and those that consume credits. She contrasts a scheduled prompt in Copilot Chat, which she says is included, with a scheduled task in the Automations tab, which uses credits each time it runs.
“For many teams, Cowork features that can do more will be worth paying for.”
That view leaves room for teams to decide that paid capabilities are useful, while emphasizing the need for a deliberate budget decision. Kitching advises organizations to agree who owns the credit budget and set per-user limits in the admin centre before users create recurring tasks such as daily briefings.
Make cost ownership part of rollout planning
According to Kitching, new interfaces can make credit-based features more visible and easier to adopt. Her post suggests that administrators should make the financial boundaries clear as teams explore what Copilot can do. The operational question is not only which features are available, but also who can authorize their use and monitor the resulting credit consumption.
Keep users informed as Copilot changes
Kitching also recommends that organizations already using Copilot send employees a short monthly update explaining what has changed. She presents ongoing communication as a way to help users remain confident while the product continues to shift. A regular note can also clarify which capabilities are included and which may incur usage costs.
“Things will keep on changing, so here’s a list of 11 changes for now.”
Her post closes by asking readers which features they have seen and used. That question reflects the uneven pace of rollout she describes, including her own experience of receiving updates shortly before delivering Copilot training. Kitching’s broader message is that organizations need to track product changes alongside their budgets and keep employees informed as new options arrive.
📝 About This Content
This article is based on insights shared by Clare Kitching on LinkedIn.
📅 Originally posted on November 7, 2026 | View original post on LinkedIn →