Your Business Is Probably Wasting 27% of Its Cloud Budget

The average organization wastes 27% of its cloud spending. Flexera’s 2024 State of the Cloud Report puts the number at 28%, and most IT leaders surveyed said the real figure is probably higher. For an SMB spending $15,000 per month across Microsoft 365 licenses, Azure resources, and SaaS subscriptions, that is roughly $48,600 per year going to services nobody uses.

The waste is not malicious. It accumulates slowly. An employee leaves and their M365 license keeps billing. A developer spins up an Azure VM for a migration project and never decommissions it. Someone signs up for a project management tool during a busy quarter and the team quietly abandons it six months later. None of these individually look like budget problems. Together, they add up fast.

With Microsoft raising M365 prices in July 2026, now is the right time to audit what you are actually paying for, before every unused license gets more expensive.

Where Cloud Budget Waste Hides

Most cloud waste falls into four categories. Knowing where to look makes the audit manageable instead of overwhelming.

Unused Microsoft 365 licenses. This is the single largest source of waste for most SMBs. Employees leave, get reassigned, or switch roles, but their licenses stay active. A company with 200 employees typically has 15 to 30 licenses assigned to inactive accounts, former contractors, or shared mailboxes that do not need a full E3 or E5 license. At $36 per user per month for E3, that is $6,480 to $12,960 per year in unused licenses alone.

Orphaned Azure resources. Test environments that outlived their projects. Storage accounts with data nobody has accessed in months. Public IP addresses attached to nothing. Virtual machines running 24/7 for workloads that only operate during business hours. Azure’s consumption model means you pay for these resources every hour they exist, whether anyone uses them or not.

Redundant SaaS subscriptions. Most SMBs use well over 100 SaaS applications, and significant overlap is common. Two project management tools because different teams chose different vendors. A standalone file-sharing service alongside OneDrive. A paid Zoom subscription when Microsoft Teams already covers video conferencing. These subscriptions often bill to individual credit cards or department budgets, making them invisible at the company level.

Overprovisioned virtual machines. A VM provisioned with 8 cores and 32 GB of RAM for a workload that consistently uses 2 cores and 4 GB is burning money every minute. Overprovisioning is common because developers and IT teams default to larger instances to avoid performance complaints, then never revisit the sizing once the workload stabilizes.

Running a Quarterly Cloud Cost Audit

You do not need a dedicated FinOps team to find waste. A quarterly audit using tools you already have access to will catch the majority of unnecessary spending.

Microsoft 365 License Review

Sign into the Microsoft 365 admin center and navigate to Billing > Licenses. This page shows every license type in your tenant and how many are assigned versus available.

Start with these checks:

• Inactive users. Go to Users > Active Users and sort by last sign-in date. Any user who has not signed in within 90 days is a candidate for license removal or downgrade. Cross-reference this list with HR to confirm whether these employees are still active. This step alone typically recovers 5 to 15% of licensing costs.
• Overassigned license tiers. Not every employee needs an E3 or E5 license. Frontline workers, warehouse staff, and reception desks often need only an F1 or F3 license at $2.25 to $8 per user per month instead. Compare actual feature usage against what each license tier includes.
• Shared mailbox licenses. Shared mailboxes in Exchange Online do not require a paid license unless they need an archive or exceed 50 GB. If you are paying for licenses on shared mailboxes, you are overpaying.
• Departed employees. Verify that offboarding procedures include license removal. Recent M365 changes mean lapsed licenses now suspend access immediately, but licenses that remain assigned to inactive accounts still bill normally.

Azure Cost Management

If your company uses Azure for any workload, open the Azure Cost Management blade in the Azure portal.

Focus on three areas:

• Idle resources. Use the Azure Advisor recommendations tab. Azure Advisor automatically flags underutilized VMs (below 5% CPU for 14+ days), unattached disks, and idle public IP addresses. Acting on Advisor recommendations typically saves 10 to 20% on Azure spend with minimal effort.
• Right-sizing. For VMs that are running but oversized, compare allocated resources against actual usage metrics. Azure Monitor shows CPU, memory, and disk utilization over time. A VM consistently running at 15% CPU can likely move to a smaller instance size without affecting performance.
• Reserved Instances vs. pay-as-you-go. If you have VMs that run 24/7 and will continue to for the next year, Azure Reserved Instances offer 30 to 60% savings over pay-as-you-go pricing. Many SMBs pay on-demand rates for stable workloads simply because nobody set up reservations.

SaaS Subscription Inventory

This is the hardest category to audit because SaaS purchases happen across the organization: IT procurement, individual departments, even personal credit cards expensed back to the company.

Build a complete list by checking these sources:

• Accounting records. Pull a 12-month report of all recurring software charges from your accounting system or expense reports. Sort by vendor and look for duplicates.
• SSO and identity provider logs. If you use Microsoft Entra ID for single sign-on, the enterprise applications list shows every SaaS tool your users authenticate into. Applications with zero logins in the past 90 days are immediate candidates for cancellation.
• Endpoint telemetry. Endpoint management tools can report which applications employees actually open. The gap between “tools we pay for” and “tools people use” is often significant.

Once you have the list, look for three things: tools with zero or near-zero usage, tools that duplicate functionality already included in M365, and tools where you are paying for more seats than you have active users.

The July 2026 Price Increase Changes the Math

Microsoft has announced price increases effective July 2026 across multiple M365 SKUs. If you are paying for licenses you do not need, every one of those unused seats gets more expensive next month.

Running a license audit before the increase takes effect means you stop paying for waste at current rates instead of elevated ones. If your audit reveals that 20 out of 200 E3 licenses are unused, removing them before July saves you both the current monthly cost and the upcoming increase, permanently.

This is also a natural time to evaluate whether your current license mix is right. Some organizations discover during an audit that they are paying for E5 features they do not use when E3 would suffice, or that a portion of their workforce would be better served by Frontline Worker licenses at a fraction of the cost. The new E7 bundle is also worth understanding before making licensing decisions, even if most SMBs will not need it.

When to Handle This Yourself vs. Bring In Help

Some parts of a cloud cost audit are straightforward enough for any office manager or IT administrator to handle. Checking M365 license assignments, identifying departed employees with active licenses, and canceling unused SaaS subscriptions do not require specialized expertise. If you have access to the admin portals and an afternoon to spare, you can recover meaningful savings on your own.

Azure cost optimization is more complex. Right-sizing VMs, configuring auto-shutdown schedules, purchasing reserved instances, and setting up cost alerts require Azure administration knowledge. Misconfiguring a VM resize can cause application downtime. Purchasing a reservation for a workload you end up decommissioning locks you into a year of payments.

A managed IT provider adds value in three specific ways. First, continuous monitoring: a one-time audit finds today’s waste, but new waste accumulates every month as employees join, leave, and adopt new tools. MSPs build license reconciliation into regular operations, catching waste before it compounds. Second, cross-tenant expertise: an MSP that manages dozens of M365 tenants knows the common waste patterns and can spot issues faster than someone auditing their own environment for the first time. Third, Azure infrastructure management: your cloud consulting partner should be reviewing Azure Advisor recommendations, implementing reserved instances, and right-sizing resources as part of ongoing management, not waiting for you to ask.

The decision is not all-or-nothing. Run the M365 license audit yourself this quarter. If you find significant waste in Azure or realize that nobody in your organization has a clear view of total SaaS spending, that is a good signal to bring in help.

Your Quarterly Audit Checklist

Use this as a starting point for a recurring quarterly review:

• [ ] Pull the M365 license utilization report and identify inactive users
• [ ] Cross-reference license assignments against the current employee roster
• [ ] Downgrade licenses for users who do not need full E3/E5 features
• [ ] Remove licenses from shared mailboxes that do not require them
• [ ] Review Azure Advisor recommendations for idle and underutilized resources
• [ ] Check Azure VM sizing against actual CPU, memory, and disk usage
• [ ] Evaluate reserved instances for stable, always-on workloads
• [ ] Inventory all SaaS subscriptions from accounting records and SSO logs
• [ ] Cancel tools with zero usage or functionality already covered by M365
• [ ] Document findings and savings for leadership review