powering productive workplaces
latest
Front page
FeatureProductivity AI47m · 15:57 GMT · 13 min read

What If Microsoft Has Got It Wrong? Don't Bet on One Vision

What if the agent-first future of work doesn't arrive the way Microsoft predicts? In this guest post, Dominic Kent asks what businesses risk if they rebuild around one vendor's vision, from lost skills and murky accountability to runaway costs and outages, and why flexibility matters.

What If Microsoft Has Got It Wrong? Don't Bet on One Vision

This is a guest post by Dominic Kent. The views are his own.

We’ve been told what the future of work looks like. But what happens if businesses invest millions building toward a future that never actually arrives?

Before going any further, this isn’t a post declaring that Microsoft has definitely got it wrong. Far from it. Microsoft has an impressive track record of innovation, and I believe AI and autonomous agents will fundamentally change how businesses operate.

This is simply a question of what if?

  • What if the future doesn’t unfold quite as Microsoft predicts?

  • What if the way businesses ultimately use AI looks very different from the vision being presented today?

It’s a question that every business should be asking, regardless of its technology provider. Because there’s a difference between embracing innovation and betting the future of your business on one particular vision of it.

Microsoft has a pretty impressive track record.

From Office and Exchange to SharePoint, Azure, and Microsoft Teams, its technology has fundamentally changed how businesses operate. It has consistently pushed the boundaries of what workplace technology can do, often bringing together capabilities that previously required multiple products and vendors.

Its investment in AI is no different. Copilot and the emerging agent ecosystem represent some of the most significant developments in enterprise technology for years.

But even Microsoft doesn’t get everything right.

Remember when we were going to:

  • Hold meetings in the metaverse?

  • Replace video conferencing with virtual reality headsets?

  • Represent ourselves as avatars in virtual meetings?

These weren’t just ideas discussed at technology conferences. They were presented as the future of work. Businesses were encouraged to explore them, invest in them, and consider how they might transform the way their employees collaborated.

Yet most businesses still meet in much the same way they did before.

I’m not suggesting these technologies were bad ideas. Some have found legitimate applications. But the widespread transformation that was predicted never really happened.

Which brings me to Copilot.

Microsoft is increasingly presenting a future in which agents do the work, Copilot becomes the primary interface for employees, and traditional applications become something we interact with through AI rather than directly.

It’s an exciting vision. There are genuine opportunities here.

But what if Microsoft has got it wrong?

Not necessarily about AI itself, but about how people will use it, how much autonomy businesses will give it, and whether a Copilot-first world is actually where we want to end up.

What Happens When You Build Your Business Around Someone Else’s Vision?

There’s a difference between adopting a technology and fundamentally redesigning your business around it.

A business might introduce Copilot to help employees write documents, summarize meetings, analyze information, and automate repetitive tasks. If it works, great. If it doesn’t, employees can go back to doing things the way they did before.

But imagine a business that goes much further.

It rebuilds its processes around autonomous agents. It invests in agent development, integrations, governance, and training. It changes employee responsibilities, restructures teams, and encourages people to delegate work rather than carry it out themselves.

It also moves toward a Copilot-first interface, where employees are expected to access their information, applications, and business processes through a conversational AI experience.

That’s a much bigger commitment.

The business is no longer simply using Microsoft’s technology. It’s building its operating model around Microsoft’s prediction of how work will happen in the future.

And that introduces some significant risks.

1. What Happens if the Interface Isn’t Better?

One of Microsoft’s biggest ambitions is to make Copilot the starting point for work.

Rather than opening Word, Excel, PowerPoint, or other business applications, employees increasingly interact with Copilot and ask it to perform tasks on their behalf.

Microsoft Copilot building a Q4 sales report in Excel from a prompt

The appeal is obvious. Why navigate multiple applications when you can simply describe what you want to achieve?

But is a conversational interface always the best interface?

Think about Excel. It’s an incredibly powerful application because people can interact directly with data, manipulate formulas, build models, and explore information visually.

Now imagine having to explain every interaction to an AI.

Sometimes that’s easier. Sometimes it isn’t.

The same applies to PowerPoint, Dynamics, and countless other business applications.

There is a danger that we introduce an additional layer between employees and the tools they need, creating friction in the name of removing it.

Consider the consequences:

  • An employee knows exactly what they want to do but has to explain it to an AI.

  • A simple task that takes five seconds in an application becomes a conversation.

  • The AI misunderstands an instruction and makes an incorrect change.

  • Employees lose visibility of what’s happening behind the interface.

  • Troubleshooting becomes more complicated because the employee doesn’t know which application, agent, or process caused the problem.

There’s also the question of choice.

Will employees still be able to access applications directly, or will businesses increasingly encourage, or even mandate, a Copilot-first experience?

We shouldn’t confuse a conversational interface with a better interface.

2. What Happens When Your Employees Lose the Ability to Do the Work?

This is potentially one of the biggest long-term consequences of an agent-first strategy.

If agents increasingly write reports, analyze data, manage customer interactions, create presentations, and execute business processes, what happens to the underlying skills?

Microsoft Copilot creating a 10-slide PowerPoint business review from a prompt

Think about how organizations have changed over the past few decades.

We’ve automated processes, introduced software, and removed manual tasks. That’s generally been a good thing.

But there is a difference between using technology to make people more productive and removing the need for people to understand how the work is done.

Imagine a business where junior employees never learn how to build a financial model because an agent does it for them.

Managers stop understanding the detail behind reports because they simply ask Copilot for a summary.

Salespeople become reliant on agents to prepare customer proposals. Project managers delegate planning and reporting to autonomous systems.

Employees become increasingly skilled at instructing technology but potentially less capable of carrying out the underlying work themselves.

  • What happens when the agent gets it wrong?

  • What happens when the technology is unavailable? (Can anyone say outage?)

And what happens when the business wants to move to another platform?

Does the organization still have the skills and knowledge to operate independently?

There’s a risk that we create businesses that are more productive in the short term but less capable in the long term.

There’s a risk that we create businesses that are more productive in the short term but less capable in the long term.

— Dominic Kent

3. What Happens When an Agent Gets It Wrong?

There’s a fundamental difference between an AI assistant producing an incorrect answer and an autonomous agent taking an incorrect action.

An assistant might give you a poor recommendation. You can ignore it.

An agent might send an email, update a customer record, approve a transaction, change a financial forecast, or trigger an automated workflow.

And it might do all of those things without an employee reviewing every individual action.

The risk isn’t simply that AI makes mistakes. It’s that those mistakes can be acted upon, repeated, and potentially propagated across multiple business systems before anyone notices.

Consider what happens when an agent has access to sensitive information, financial processes, customer records, and other connected applications.

A mistake that might once have affected one employee could now affect an entire business process.

The more autonomy we give agents, the more important it becomes to control what they can access, what they’re allowed to do, and where human approval is required.

4. Who Is Actually Accountable?

This is where things get particularly interesting.

If an employee makes a mistake, we generally know where accountability sits.

But what happens when an agent makes a decision?

  • Is it the employee who instructed it?

  • The manager who approved its deployment?

  • The IT department that configured it?

  • The business owner who designed the process?

  • Or the technology provider?

Microsoft is clearly aware of this challenge.

Its approach includes giving agents their own identities, assigning accountable human owners, and providing administrative controls.

At Ignite 2026, Microsoft announced further developments around agent identities and governance, including Agentic Users in Teams. Agents can have their own identities and owners, and become identifiable participants in team channels and meetings.

Rob Scott, in his LinkedIn commentary and reporting for UC Today, highlighted the significance of this development.

Rob Scott LinkedIn post on agents in Microsoft Teams getting their own identity at Ignite 2026

Rather than being anonymous background processes, agents become identifiable participants in the organization.

Microsoft is also developing wider governance capabilities through Agent 365, Microsoft Entra, Defender, and Purview.

These provide mechanisms to:

  • Give agents their own identities.

  • Assign a responsible human owner.

  • Control what information and applications they can access.

  • Monitor and audit their actions.

  • Restrict or revoke access when necessary.

This is the right direction.

But there’s an important distinction between assigning an agent an owner and establishing genuine accountability for everything it does.

A named owner doesn’t necessarily know what an agent has done, why it made a particular decision, or whether its actions were appropriate.

Microsoft can provide the controls. Businesses still need to establish the policies, processes, and human oversight to make them meaningful.

Microsoft can provide the controls. Businesses still need to establish the policies, processes, and human oversight to make them meaningful.

— Dominic Kent

5. What Happens When the Economics Don’t Stack Up?

There’s another consideration that could become increasingly important as organizations scale their use of agents.

The economics of AI.

Introducing Copilot to a handful of employees is one thing. Building an organization that relies on hundreds or thousands of agents is something else entirely.

Businesses need to consider:

  • Copilot and agent licensing.

  • AI consumption and usage charges.

  • Development and integration costs.

  • Governance and security overheads.

  • Ongoing monitoring and maintenance.

  • The cost of human oversight and intervention.

An agent that saves an employee 30 minutes a day sounds attractive.

  • But what if it takes 20 minutes of human intervention to check its work?

  • What if it requires significant development, ongoing maintenance, and additional licensing?

  • What if the cost of running agents at scale exceeds the productivity benefits?

The important metric isn’t how many agents you’ve deployed or how many tasks they’ve completed.

It’s whether they’ve actually improved the business.

6. What Happens When Everything Depends on Agents?

There’s another risk that perhaps hasn’t received enough attention.

Operational resilience.

We’ve spent years trying to make businesses less dependent on individual applications, systems, and infrastructure.

Now we’re potentially moving toward a world where an increasing proportion of business activity depends on autonomous agents operating across those systems.

  • What happens when those agents stop working?

  • What happens when the underlying AI service becomes unavailable?

  • What happens when Microsoft 365 has an outage?

Rob has also raised the importance of considering what happens when the agentic workforce goes dark, rather than simply thinking about the availability of individual applications.

It’s a valid concern.

If employees have become accustomed to delegating work to agents, and those agents suddenly become unavailable, can the business continue operating?

If agents are responsible for managing customer inquiries, updating systems, coordinating workflows, or preparing critical information, what is the fallback?

The more we automate, the more important resilience becomes.

Businesses need to know what happens when the automation fails, not just how much time it saves when everything works.

7. What Happens if Microsoft Changes Direction?

Perhaps the most fundamental risk is that Microsoft doesn’t stand still.

Its products evolve. Its licensing changes. Its preferred architectures change. New capabilities are introduced, and others are retired.

That’s part of the reason Microsoft has been so successful. It continues to innovate and adapt.

But it also means businesses need to be careful about building long-term strategies around individual product capabilities.

Imagine investing millions in an agent ecosystem built around a particular Microsoft framework.

  • Then the underlying architecture changes.

  • Or the licensing model becomes less attractive.

  • Or a new AI provider introduces a significantly better model or way of working.

  • Or employees simply prefer another interface.

What happens to the investment? What happens to the processes you’ve rebuilt?

What happens to the integrations and skills you’ve developed?

This isn’t a reason to avoid Microsoft. It’s a reason to avoid unnecessary dependency on any single vendor’s vision of the future.

8. Are We Solving Business Problems or Adopting Technology for Its Own Sake?

This is perhaps the biggest question of all.

  • Does your customer care whether their inquiry was handled by an agent?

  • Do they care whether your employees accessed their information through Copilot or directly through your CRM?

  • Do they want to interact with an AI agent when they could have spoken to a knowledgeable person?

Businesses risk becoming so focused on implementing the next generation of workplace technology that they lose sight of why they exist.

The objective should be to improve customer experience, increase productivity, reduce costs, and make better decisions.

If agents help achieve those objectives, brilliant.

If Copilot becomes the most effective way for employees to interact with their applications, embrace it.

But the technology should serve the business. The business shouldn’t exist to demonstrate the technology.

So, Should Businesses Be Cautious About Going All In on Copilot?

Absolutely not. But they should be cautious about going all in on any single vision of the future.

Microsoft has made some extraordinary innovations and I believe AI and autonomous agents will fundamentally change how businesses operate.

There are opportunities here that would have been difficult to imagine only a few years ago.

But we’ve been here before.

  • The metaverse wasn’t necessarily a bad idea.

  • Virtual reality wasn’t necessarily a bad idea.

  • Avatars weren’t necessarily a bad idea.

They simply didn’t become the future of everyday business that many people predicted.

And that’s the point.

What if Microsoft has got it wrong?

  • What if employees still prefer working directly in applications?

  • What if agents prove useful for specific tasks but unreliable as autonomous operators?

  • What if the cost of running agents outweighs the productivity benefits?

And perhaps the biggest question:

What happens to the businesses that have spent millions transforming themselves around a vision that never materializes?

I’m not suggesting businesses should ignore AI. Quite the opposite.

They should experiment, innovate, and find ways to use it to improve how they operate.

But they should also preserve flexibility, maintain human capability, establish proper governance, and avoid making irreversible decisions based on a single vendor’s prediction of how work will happen.

Perhaps the biggest mistake a business can make isn’t failing to adopt AI.

It’s becoming so committed to one particular vision of AI that it loses the ability to adapt when that vision changes.

Don’t build a business around the assumption that the future of work will look exactly like the future Microsoft is trying to sell you.

Dominic Kent is an independent writer who specializes in unified communications and contact center technology, working closely with vendors like Nextiva, Cisco, and other collaboration providers. He runs UC Marketing Ltd, a consultancy dedicated to helping technology companies translate complex technology products into compelling stories and educational content.

rate this story
helps rank stories across uc today
Join the conversation

Does this reflect your experience?

opening the room…