Tool Sprawl Is a Governance Problem. Microsoft 365 Is Not the Solution — Until You Fix That First.

Why digital workplace consolidation keeps failing — and what needs to happen before Microsoft 365 can deliver on its promise

Most enterprise IT leaders know the number. The average large organization runs well over 100 SaaS applications. In enterprises with more than 5,000 employees, that number regularly exceeds 130, and in some tenants, it climbs past 300.

These tools were not all bought by IT. They were bought by marketing, HR, finance, individual teams, project managers, and people who just needed to get something done and found a tool that worked.

The result is a digital workplace that nobody designed. And the cost of that undesigned landscape is now showing up in three places simultaneously: the budget, the security posture, and the productivity reports.

Most organizations respond by announcing a consolidation initiative. Many of those initiatives stall, scale back, or quietly fail within 18 months. The tools they were meant to retire are still running. New ones have appeared to fill gaps the consolidation left behind.

At Impactory, we have worked with enough enterprises navigating this to know why consolidation fails — and what has to happen first before any consolidation platform, including Microsoft 365, can actually deliver on its promise.

The Sprawl Nobody Planned For

Tool sprawl is not the result of poor decisions. It is the natural outcome of decentralized buying, rapid scaling, and a decade of SaaS vendors making it easier than ever to start a free trial, add a seat, and expense a subscription.

The pandemic accelerated it sharply. Between 2020 and 2022, organizations adopted collaboration, project management, video, document, and workflow tools at a pace that IT governance could not match. Teams needed solutions immediately. Procurement cycles were too slow. So people bought what worked.

By the time budgets tightened and the post-pandemic normalization set in, the landscape was already fragmented. The typical enterprise digital workplace now looks something like this:

• Multiple communication tools running simultaneously — Teams, Slack, Zoom, and email, each used by different teams for overlapping purposes.
• Document and knowledge management split across SharePoint, Confluence, Notion, Google Drive, and shared network drives.
• Project coordination happening in Jira, Asana, Monday.com, Planner, and email threads — often within the same organization.
• Desk and room booking managed through standalone tools, spreadsheets, or informal chat threads — while Microsoft Places sits unleveraged in the license.
• Intranet and internal comms fragmented across a custom intranet, SharePoint pages nobody maintains, and a mix of newsletters and announcement channels.

Nearly half of enterprise applications today are shadow IT — tools that IT neither approved, tracks, nor secures. The average enterprise underestimates its SaaS spend by more than 300 percent.

What Tool Sprawl Actually Costs

The budget line is the most visible cost, but rarely the largest one.

The Direct Cost: Licenses Nobody Uses

Industry estimates consistently show that between 30 and 50 percent of SaaS licenses go unused or underutilized for 90 days or more. For an enterprise with 1,000 employees carrying an average SaaS spend of $9,000 to $17,000 per employee per year, that is a significant and largely invisible waste.

The organizations that have conducted formal audits regularly discover tools they forgot they subscribed to, duplicate capabilities they are paying for twice, and Microsoft 365 features already included in their existing license that they are purchasing separately from third-party vendors.

The Indirect Cost: Security Exposure and IT Overhead

Every unmanaged tool is a potential entry point. Shadow IT accounts for a significant share of enterprise security incidents — not because the tools themselves are malicious, but because they operate outside the data governance, access controls, and compliance frameworks the organization has built around its sanctioned platforms.

Data is stored in places IT cannot see, shared with external parties through channels IT did not approve, and accessed on devices that do not meet policy requirements.

The operational overhead is compounding as well. IT teams now spend roughly twice as long managing SaaS licenses as they did five years ago — time that is not spent on strategic initiatives like AI readiness, security hardening, or digital workplace improvement.

The Strategic Cost: Paying for M365 While Underusing It

This is the cost that matters most for this conversation. Microsoft 365 is now the most widely deployed enterprise productivity platform in the world, with over 345 million commercial paid users and adoption across 75 percent of Fortune 500 companies.

Most enterprises running at E3 or E5 level are paying for capabilities they have not enabled, configured, or adopted — while simultaneously paying separate vendors for those same capabilities.

The typical enterprise M365 tenant has Teams, SharePoint, OneDrive, Viva, Purview, Planner, Places, and Copilot capabilities either already included or available as an add-on. The question is not whether M365 covers the need. The question is whether the organization has done the work to make it do so.

Why Consolidation Initiatives Keep Failing

The boardroom case for consolidation is usually compelling. Fewer tools, lower spend, reduced security surface, better adoption of what you already own. CIOs present the business case, secure the budget, and announce the initiative. Then, somewhere between the announcement and the target state, momentum stalls.

The reasons are remarkably consistent across organizations.

The Technology-First Trap

The most common mistake is treating consolidation as a migration project rather than a governance project. The initiative is defined in terms of tools to retire and platforms to adopt. A timeline is set. Change management is planned.

And then reality arrives: the teams using the tools to be retired have legitimate workflows that the replacement platform does not yet support — not because the capability does not exist in M365, but because M365 has not been configured, trained, or governed to provide it.

The result is either a forced migration that generates resistance and workarounds, or a stalled project that quietly collapses as stakeholders lose confidence.

The “Just Turn It Off” Mistake

A related failure mode is treating decommissioning as the goal rather than the outcome. Turning off a tool before a capable, trusted alternative is in place does not consolidate the digital workplace.

It creates a vacuum that employees fill with whatever is available — which is often a new tool that IT does not manage, purchased by the team that just lost the one they relied on.

This is how consolidation initiatives produce new sprawl within 12 to 18 months.

The Root Cause: Sprawl Is a Symptom, Not the Problem

Tool proliferation is the visible symptom of an underlying governance deficit. When there is no shared framework for which tools are approved, no lifecycle process for reviewing and retiring software, no clarity on what M365 is the authoritative platform for, and no ownership model that holds someone accountable for the digital workplace as a whole — tools multiply.

They multiply because people need to get work done, and the path of least resistance is a new SaaS subscription.

Consolidation without governance redesign does not solve this. It temporarily reduces the symptom while leaving the cause untouched. Within 18 months, the landscape looks similar to where it started.

Governance First — What That Actually Means

When we say governance first, we do not mean bureaucracy or approval committees. We mean three things that any successful consolidation requires before a single tool is retired.

Ownership: Who Decides and Who Is Accountable

Every tool in the enterprise should have an owner. Not a vendor contact or a license administrator, but a business or IT owner who is accountable for whether that tool delivers value, whether it overlaps with something else, and when it should be retired.

In most organizations, this ownership is either absent or deeply unclear. Nobody is tracking the full landscape, because no single role has been given that responsibility.

Establishing ownership requires defining: who approves new tool adoption requests, who reviews the existing portfolio on a defined cycle, who has authority to initiate decommissioning, and how disputes between business units and IT are resolved when a team wants to keep a tool IT wants to retire.

Policy: What M365 Is For, and What Lives Outside It

M365 cannot be the default answer for everything. There are legitimate cases where a specialized tool outperforms what M365 provides — certain CRM integrations, industry-specific workflows, design and creative tools, developer environments.

The governance failure is not using those tools. It is using them without a policy framework that makes the boundaries explicit.

A functional digital workplace policy answers: what is M365 the authoritative platform for — communication, document management, intranet, hybrid coordination, AI — what categories can live outside M365 with approval, and what requires a formal exception and periodic review.

Without this, every team makes its own call, and every call is a potential new tool in the landscape.

Lifecycle: How Tools Get Added, Reviewed, and Retired

The single most effective anti-sprawl mechanism is a lightweight but enforced tool lifecycle process.

New tools require a request and approval step that checks for M365 overlap. Existing tools are reviewed annually against usage data and cost. Tools that fail the review enter a decommissioning track with a defined timeline.

This does not need to be complex — but it does need to exist, and it does need teeth.

Organizations that have implemented this consistently find it easier to maintain the gains from consolidation than those that treat consolidation as a one-time project.

Then: Microsoft 365 as the Consolidation Platform

Once governance foundations are in place, the case for Microsoft 365 as the consolidation destination becomes both compelling and achievable. Microsoft has deliberately built M365 to cover the core digital workplace use cases that most organizations are currently buying separately.

What M365 Already Covers

Teams covers the unified communication and collaboration use case that organizations are often also running Slack, Zoom, or Webex alongside. With 360 million monthly active users, Teams is not a niche alternative — it is the most widely used enterprise collaboration platform in the world. The question is whether it has been configured and adopted deeply enough to replace the alternatives, not whether it is capable.

SharePoint covers the intranet and document management need that organizations often supplement with Confluence, Notion, or legacy intranet platforms. The gap is almost never capability — it is information architecture, metadata governance, and content ownership. Fix those, and SharePoint replaces the alternatives reliably.

Microsoft Places covers desk and room booking, office coordination, and space analytics — functionality organizations are often purchasing from standalone workplace management vendors. From April 2026, Places is included in most standard M365 licenses at no additional cost.

Viva covers employee communications, engagement, and learning use cases that organizations often address through separate intranet products, newsletter tools, or standalone LMS platforms.

Purview covers compliance, data classification, and information protection needs that organizations sometimes address through third-party DLP and governance tools.

The “Good Enough, Deeply Integrated” Strategic Advantage

Microsoft’s strategy is deliberate and well-documented: deliver capabilities that are good enough for most enterprise use cases, and make them deeply integrated with everything else the organization already uses.

A room booking tool that lives inside Teams and Outlook is more likely to be adopted than a standalone booking application, even if the standalone tool has better features. A project management tool inside M365 does not require a separate login, a separate data silo, or a separate governance conversation.

For CIOs evaluating consolidation, this integration advantage compounds over time. Every tool retired in favor of an M365 capability reduces the number of identity integrations to manage, security policies to maintain, data silos to govern, and license renewals to track.

The Prerequisite: M365 Must Be Ready to Replace, Not Just Licensed

This is the critical point that consolidation initiatives miss. Announcing Teams as the communication platform while SharePoint governance is fragmented, metadata is inconsistent, and intranet content is not AI-ready does not consolidate the digital workplace. It adds M365 adoption pressure on top of an already fragile foundation.

M365 must be configured, governed, and adopted well enough to genuinely replace what it is meant to replace. That requires the governance work described above — and in many cases, it requires targeted remediation of the M365 foundations before any decommissioning begins.

What Impactory Addresses Before Recommending Any Consolidation

When organizations come to us with a tool sprawl problem, we do not start by recommending which tools to retire. We start by understanding why the sprawl exists — and whether the proposed consolidation platform is ready to hold the weight of what it is meant to replace.

Tool Inventory and Overlap Mapping

The first step is an honest inventory: what tools exist across the organization, who uses them, how actively, and what specific workflows they support.

This is almost always more complex than IT’s records suggest — shadow IT, team-level subscriptions, and tools procured through expense reports rather than formal procurement are frequently invisible to the central view.

Against that inventory, we map M365 capabilities: where does a direct replacement already exist, where does it exist but require configuration or governance work to be viable, and where is a specialized tool genuinely providing something M365 cannot match?

Governance Design Before Migration

Before any tool is retired, we work with IT, Facilities, HR, and business stakeholders to establish the ownership model, define the policy framework, and put the lifecycle process in place.

This is not a slow process — but it is a necessary one. Without it, the consolidation creates a governance vacuum that refills with new sprawl.

M365 Adoption Readiness

We assess whether M365 is in a state where it can genuinely replace the tools being decommissioned.

This means reviewing information architecture in SharePoint, metadata governance, Teams adoption patterns, permissions models, and the readiness of M365 features that the organization is currently buying elsewhere.

In many cases, targeted foundation work in M365 is the prerequisite for successful consolidation — not a post-consolidation task.

Only once these three pieces are in place do we recommend a sequenced decommissioning plan — with clear success criteria, a user communication approach, and a monitoring framework for adoption.

Questions CIOs and CFOs Should Ask Before Starting

Before commissioning a consolidation initiative, the following questions will tell you more than any tool audit about whether your organization is ready to make it stick.

Governance & Ownership

• Do we have a named owner for our digital workplace portfolio — someone accountable for tool approval, review, and retirement?
• Is there a policy that defines what M365 is the authoritative platform for — and what lives outside it with explicit approval?
• Do we have a tool lifecycle process, or does every adoption decision happen in isolation?
• Can we identify, today, every active SaaS subscription in our organization — including those procured outside IT?

M365 Readiness

• Are we confident that Microsoft 365 is configured and governed well enough to replace the tools we want to retire — not just licensed to do so?
• Do we have consistent Teams adoption, governed SharePoint, and an information architecture that supports reliable search and AI?
• Have we identified the M365 features we are already paying for that we are currently purchasing from third-party vendors?

Consolidation Sequencing

• Do we have a sequenced plan that addresses governance first, M365 readiness second, and decommissioning third?
• Can we identify the two or three tool categories where consolidation would deliver the most value fastest — and start there?
• Do we have a communication and change management approach that explains to employees not just what is changing, but why the replacement is genuinely better?

If these questions surface significant uncertainty, the consolidation initiative is not ready to launch. It is ready to be scoped properly.

The Platform Is Ready. The Governance Usually Is Not.

Microsoft 365 is a capable consolidation platform. It covers the core digital workplace use cases that most enterprises are currently distributing across a fragmented and expensive SaaS landscape. It is integrated, governed within a single identity and compliance framework, and becoming more capable every quarter as Microsoft embeds AI across the entire product surface.

The organizations that successfully consolidate are not the ones that announce M365 as the standard and immediately start retiring tools. They are the ones that fix their governance model first, ensure M365 is configured to genuinely replace what it is meant to replace, and then execute consolidation in a sequence that builds trust rather than generating resistance.

Tool sprawl did not happen because people made bad decisions. It happened because there was no framework to make the right decision consistently. The consolidation initiative that lasts is the one that installs that framework — and lets M365 do the rest.

Ready to assess where your organization stands?

At Impactory, we work with enterprise IT and leadership teams to map tool landscapes, assess M365 readiness, and design governance frameworks that make consolidation stick — not just get announced.

→ Download the Readiness Checklist

Our structured Copilot & SharePoint Readiness Diagnostic applies directly to consolidation readiness. Fill in your details to access the checklist your IT team can use to assess whether M365 is ready to replace what you are currently buying elsewhere.

→ Book a Consultation with Impactory

If you want to go further: our team can walk through your specific tool landscape, map it against your M365 capabilities, identify the governance gaps, and help you build a consolidation roadmap that is grounded in your actual environment — not a generic playbook.