Copilot Is Now in Every M365 SKU: What Changes July 1

Microsoft announced on May 28 that Copilot will be built directly into Microsoft 365 Business Standard and Business Premium starting July 1, 2026. The separate $30/user/month Copilot add-on for enterprise tiers is going away for Business SKUs. Instead, every Business Standard and Business Premium subscription will include Copilot by default under new SKU names.

This is a bigger shift than a price adjustment. The per-user add-on pricing that made many SMBs hesitate is no longer the model. If you’re on a Microsoft 365 Business plan, AI is now part of your baseline productivity suite whether you planned for it or not. That means your licensing decisions, security policies, and employee readiness all need to catch up before the switch date.

What the New SKUs Actually Look Like

Microsoft is renaming and restructuring the Business-tier plans into two new SKUs, both available July 1:

• Microsoft 365 Business Standard with Copilot replaces the current Business Standard plan
• Microsoft 365 Business Premium with Copilot replaces the current Business Premium plan

The key change: Copilot capabilities that previously required a separate add-on purchase are now included in the base subscription. Word drafting, Excel formula generation, PowerPoint slide creation, Outlook email assistance, and Teams meeting summaries all come standard.

Microsoft has also confirmed that existing Business Standard and Business Premium customers will transition to the new SKUs automatically. You don’t need to purchase a new plan or re-provision licenses. Your renewal price will reflect the updated SKU pricing, which incorporates the Copilot capabilities into the plan cost rather than charging them separately.

If you were already paying for Copilot as a standalone add-on, contact your Microsoft partner or reseller before July 1 to confirm the add-on charge drops off your next invoice. Duplicate billing during SKU transitions is a common issue that won’t fix itself automatically.

Work IQ: Copilot Now Understands Your Business Context

The bundling announcement came alongside a new capability called Work IQ. This is worth understanding separately from the licensing change because it fundamentally changes what Copilot can do.

Previously, Copilot in Word only knew about the document you were editing. Copilot in Outlook only knew about the email thread in front of you. Each app operated in its own silo. Work IQ connects Copilot to your broader M365 environment, giving it awareness of projects, deadlines, decisions, and conversations happening across SharePoint, Teams, OneDrive, Planner, and email.

In practical terms, that means Copilot can now:

• Surface project context without being asked. When you’re drafting a proposal, Copilot can pull in relevant data from a SharePoint project folder, recent Teams discussions about the client, and timeline commitments from Planner.
• Track decisions across channels. If your team agreed on a budget number in a Teams meeting last Tuesday and someone referenced it in an email thread on Thursday, Work IQ connects those data points so Copilot can reference the decision when you’re building a forecast.
• Flag deadlines and dependencies. Copilot can proactively surface upcoming commitments based on Planner tasks, calendar events, and email promises across your organization.

This is a meaningful upgrade for companies that live inside M365 for most of their work. It also means Copilot is now reaching across more of your organizational data, which makes the security question more important.

Security Boundaries You Should Verify Before July 1

Microsoft has stated that Copilot operates within your existing M365 security and compliance boundaries. It respects the same permission model as the rest of your tenant: users can only access data through Copilot that they could already access through normal M365 applications.

That’s the right architecture, but it exposes a problem many SMBs have been ignoring. If your SharePoint permissions are too broad, if former employees’ OneDrive content is accessible to current staff, or if sensitive financial data sits in a Teams channel that half the company can read, Copilot will happily surface that information to anyone who asks it the right question.

With Work IQ expanding Copilot’s reach across your entire M365 environment, permission gaps that were low-risk when employees had to manually dig through folders become higher-risk when Copilot can surface that content in seconds.

Before July 1, audit these areas:

• SharePoint site permissions. Check which sites use broad “Everyone except external users” access versus targeted security groups. Tighten permissions on finance, HR, and executive content.
• OneDrive sharing defaults. Verify that the default sharing scope is set to “Specific people” rather than “Anyone with the link” or “People in your organization.”
• Teams channel membership. Review private versus public channels, especially for channels containing client data, financial information, or strategic planning discussions.
• Sensitivity labels. If you’re on Business Premium, you already have Microsoft Purview Information Protection. Apply sensitivity labels to confidential documents so Copilot respects classification boundaries.

If your organization hasn’t done a data governance review recently, the Copilot transition is a strong reason to schedule one. The AI capabilities are more useful when they have access to well-organized data, and less risky when permissions are set correctly.

What This Means If You Already Pay for Copilot

Companies that invested in the standalone Copilot add-on over the past year have a licensing cleanup to handle. The specifics depend on your current setup:

If you bought Copilot for select users. Under the old model, you could license Copilot for your 15 heaviest users and skip it for everyone else. With the new bundled SKUs, every user on Business Standard or Premium gets Copilot included. Your selective licensing strategy goes away, which means the cost optimization we described in our ROI assessment needs a fresh look.

If you bought Copilot company-wide. You were paying base subscription plus $30/user/month (enterprise) or $18-21/user/month (business). Confirm with your reseller that the add-on charge is removed when your subscription transitions to the new SKU. Run the numbers on your new effective per-user cost and compare it to what you’ve been paying.

If you locked in the promotional pricing. Microsoft offered a 15% discount on standalone Copilot Business through June 30. That promotional pricing becomes moot once the bundled SKUs take effect. Verify with your licensing partner how the transition affects any committed-term pricing you locked in.

In all three cases, the action is the same: pull your current Microsoft 365 invoice, identify every Copilot-related line item, and confirm with your reseller or M365 consulting partner that nothing carries over as a duplicate charge after July 1.

Building an Adoption Plan When Everyone Gets Copilot

The biggest operational change isn’t the licensing, it’s that Copilot is about to be on by default for every user in your organization. The adoption data we covered recently showed that only 35.8% of users with Copilot access use it regularly, and the accuracy NPS sits at -19.8. Those numbers came from organizations that intentionally chose to deploy Copilot. When it’s bundled into every license, adoption without training is almost guaranteed.

Untrained users will try Copilot, get poor results, and either ignore it entirely (wasting the capability you’re paying for) or trust inaccurate outputs (creating business risk). Neither outcome is acceptable when the tool is now available to your entire workforce.

A practical rollout before or shortly after July 1:

1. Identify your high-value roles first. Finance, operations, and administrative staff who spend significant time in Excel, Word, and Teams will see the fastest productivity gains. Start training and change management with these groups.
2. Set internal usage guidelines. Define which workflows are appropriate for Copilot assistance and which require human-only work. Client-facing deliverables, legal documents, and financial filings should have clear review requirements before Copilot-generated content goes out.
3. Designate internal champions. Pick 3 to 5 employees who are comfortable with AI tools and give them time to build department-specific prompts and workflows. Peer-driven adoption consistently outperforms top-down mandates.
4. Establish a feedback loop. Collect structured feedback from users at 30, 60, and 90 days. Track which tasks Copilot accelerates, which it doesn’t help with, and where accuracy is a concern. Use that data to refine training and expand to additional roles.
5. Review AI governance policies. If your company has an AI governance framework, update it to reflect that Copilot is now a default tool rather than an opt-in one. If you don’t have AI policies yet, the July 1 transition is a hard deadline to create them.

Your Action Items Before July 1

You have about four weeks. Here’s what to prioritize:

• Audit your current M365 licensing. Pull your invoice, identify every SKU and add-on, and confirm how the July 1 transition affects your billing.
• Review data permissions. Tighten SharePoint, OneDrive, and Teams access controls before Copilot starts surfacing content across your environment.
• Talk to your MSP or Microsoft partner. Confirm the transition timeline, verify there are no duplicate charges, and discuss training and rollout support.
• Draft internal AI usage guidelines. Every employee will have access to Copilot. Define expectations before they start experimenting on their own.
• Plan training for high-value roles. Don’t wait until after July 1 to figure out who benefits most and how to get them started.

The companies that treated the original Copilot launch as “buy licenses and hope for the best” ended up with 3% adoption and negative accuracy scores. The bundled model gives you a second chance at a structured rollout, but only if you use the next four weeks to prepare.