Back in September 2025, Microsoft made a pretty big deal out of bringing Copilot Chat directly into the Microsoft 365 apps for everyone with an Enterprise license. Not the full Copilot experience, but still something meaningful. It gives users the ability to reason about their local data directly in the app, while also grounding responses in information from the web.
You could open Word, Excel, PowerPoint, Outlook and Onenote and have Copilot Chat right there. Ask questions, get help, summarize etc. It felt like a natural step forward. Not everything needs a full Copilot license, but a lighter entry point made sense. In a way It was also more or less positioned as part of the value of enterprise licensing.
And now… it is being scaled back….
Microsoft recently communicated via the Microsoft 365 Message Center (MC1253858) that Copilot Chat in the Microsoft 365 apps will be limited to organizations below a certain size threshold. More specifically, it will not be available for tenants with more than 2,000 users after April 15, 2026.
So this is not a full removal. But for many of the organizations that typically sit on E3 and E5, it will be.
Let that sink in for a moment.
The customers who are most likely to standardize on these enterprise licenses are also the ones who will not get access to the feature that was previously positioned as part of the value.
The 2000 user limit
And then there is the threshold itself. What happens to an organization with 1995 users that hires five more people?
Overnight, they cross the 2000 user limit. And with that, a feature people have started to use and rely on is suddenly no longer available. No gradual transition. No soft landing. Just gone.
That is a tough message to explain internally. It is also a strange user experience. Features do not usually disappear because your company is growing. If anything, you would expect the opposite.
And it is not just about the feature itself. Organizations may already have invested both time and money into training, communication, and user adoption around this capability. People have learned how to use it. Internal champions have started promoting it. Expectations have been set. And then it disappears.
That investment does not just pause. It is lost. In many organizations this will most likely also add extra costs due to service desk calls from co-workers that think that something is broken.
A strange decision
I think this is what makes it hard to understand. This was not a niche feature. It was part of a broader narrative.
Bring AI closer to where people work
Lower the barrier to entry
Let more users get some value without needing full Copilot licenses
A smart way to introduce Copilot Chat and build adoption before asking organizations to go all in.
And, honestly, also a safer way to use it.
If users can work directly with their data inside the apps, there is less need to download or upload documents into separate chat interfaces. That alone reduces the risk of data ending up in the wrong place.
It is not hard to imagine a portal that looks exactly like Copilot. Same colors, same layout, same experience. But it is not. A malicious site designed to trick users into uploading sensitive documents.
Keeping the experience inside the trusted Microsoft 365 apps helps reduce that risk. And even if we like to think that sensitivity labels and DLP are everywhere, that is not always the case. For many organizations, that level of protection is still something they are working towards. Not something they can fully rely on today.
Costs vs Features
When Microsoft introduced Copilot Chat in the apps, it was not presented as a small experiment. It was positioned as added value across Microsoft 365. A way to bring AI into everyday work for more users, not just those with full Copilot licenses.
That message matters because at roughly the same time, Microsoft also announced price increases for the enterprise plans. And when that happens, people naturally connect the dots.
More value
More capability
A higher price
To me, that is a fair equation.
But if part of that value is later removed or restricted for the very customers who are paying for those enterprise licenses, the equation starts to look different. Especially for larger organizations.
The ones who invest the most, standardize the most and often drive adoption and change management at scale. They are now the ones who do not get access to a feature that was part of the broader value story. These organizations might have:
- Planned for a broader AI adoption using the lighter experience
- Communicated internally that “something is coming”
- Started building expectations among users
And now you have to start over. That is never a great place to be as an IT organization.
My thoughts
I get that things change. AI is moving fast, licensing is evolving, and Microsoft is clearly trying to balance innovation with revenue. But this one still feels a bit off.
Not because the feature is already gone, but because it is going away. And even more because of how it was positioned in the first place.
When something is introduced as part of the journey, especially as part of the value of an enterprise license, it sets expectations. Not just technically, but also in how organizations plan, invest, and communicate internally.
So when that direction changes, it needs to be handled carefully.
Have you looked at this in your organization yet? Did you plan around Copilot Chat in the apps? Or are you already all in on full Copilot licenses? Let me know in the comments.
