What Copilot in 30 actually offers
Copilot in 30 is Microsoft's biggest SMB Copilot push through the channel this year. According to Sherweb's partner guidance, it is a limited-time, CSP partner-led trial of Microsoft 365 Copilot Business. Customers on Microsoft 365 business SKUs with fewer than 300 licenses get 25 users on Copilot Business for 30 days at no cost. The offer runs through December 31, 2026, and Sherweb called it the most important Microsoft announcement for MSPs in its September 2026 roundup. Microsoft pairs the seats with the Copilot Success Planner that comes with the trial. The planner generates weekly guidance for trial users and a roadmap for the customer's sponsor, covering setup, checkpoints and an end-of-trial value review.
The intent is clear from how partners describe it. Sherweb says the trial addresses "the most common objection in SMB Copilot conversations," which is that customers can't picture how Copilot would help them. The recommended way to measure a trial reflects that: did users activate, did they come back across multiple weeks, which scenarios got faster, and does the customer have enough evidence to decide who gets a paid license.
The scenarios Microsoft and its distributors describe are almost entirely inside Microsoft 365: drafting in Word, summarizing in Teams, triaging in Outlook, analyzing in Excel. That is a reasonable place to start, but it is not where most SMBs spend their day.
Where an SMB's work actually lives
Take a 40-person HVAC contractor, a 25-person accounting firm or a 60-person distributor. Email and documents matter, but the questions employees ask all day are things like "Which jobs are behind schedule?", "What did this customer order last quarter?", "Which invoices are more than 60 days overdue?" and "What's the history on this ticket?" The answers live in QuickBooks or Xero, a field-service or practice-management app, a CRM, an e-commerce platform or a PSA. Copilot running over Outlook and SharePoint can help write the email about the overdue invoice. It can't tell you which invoices are overdue.
Microsoft's own documentation is direct about this boundary. Microsoft 365 Copilot connectors exist to "extend the reach" of Copilot by connecting to data beyond Microsoft 365. Without them, Copilot reasons over mail, files, chats and calendars. With them, a user can ask for "a summary of the Contoso deal" and get an answer drawn from a connected Salesforce record, with a citation.
A Copilot trial that only touches email and documents shows an SMB owner a better writing assistant. A trial that can answer questions from their accounting system or job board shows them a better business.Why Copilot pilots were already stalling
The industry has seen this before at larger scale. In a Gartner survey of 132 IT leaders reported by Computerworld, 60% had started Microsoft 365 Copilot pilots, but only 6% had finished and were actively planning large-scale deployments, and only 1% had rolled Copilot out to all eligible workers. Enthusiasm was not the problem: 98% said employees were excited to use it. What stalled rollouts was fit and trust. 72% said employees struggled to integrate Copilot into their daily routines, 57% said engagement dropped quickly after rollout, and only 3% said Copilot provided "significant" value at that stage. Governance was the other brake: 64% said information governance and security risks took significant time and resources, and 40% delayed rollouts by three months or more over oversharing concerns.
Those numbers came mostly from large enterprises, and Microsoft has shipped a great deal since. Still, the pattern maps directly onto a 30-day SMB trial. A trial is exactly the window in which "struggle to integrate it into daily routines" decides the outcome. If the routine runs through a line-of-business app Copilot can't see, week-three usage is likely to decline no matter how good the prompts in the success planner are. That's the same governance and data-readiness gap Ngentix has covered on the MSP side, now showing up in the sales motion.
What Copilot connectors can and can't do for an SMB trial
Microsoft offers two kinds of connectors, and the difference matters for a short trial:
- Synced connectors crawl and index external content into Microsoft Graph, so it shows up in Copilot and Microsoft Search alongside Microsoft 365 content. They respect source-system permissions, support SaaS and on-premises sources, and can be custom-built.
- Federated connectors use Model Context Protocol (MCP) to fetch data live, without indexing it into Microsoft 365. Microsoft positions them for sensitive or fast-changing data. They are currently read-only, and Microsoft's documentation notes write actions arrive starting in early October 2026. Custom federated connectors are not supported.
Microsoft lists more than 100 prebuilt connectors, including Salesforce, ServiceNow, Dynamics 365, SAP, Workday, Zendesk, Jira and SQL and Oracle databases. That is a strong list for the mid-market and enterprise. It is thinner for the long tail of SMB software: the regional accounting package, the vertical practice-management tool, the field-service app with its own API. For those, Microsoft's guidance is to build a custom connector with the Microsoft 365 Agents Toolkit or the Graph connectors API. That work requires a developer to define a schema, register the connection in Microsoft Entra ID and write code to pull and push data. Microsoft's docs add a caveat MSPs should take seriously: custom connectors "require maintenance."
That caveat is the real cost. A connector built during a 30-day trial is not a one-off project. It's a dependency that has to keep working as the source app changes its API, renames fields or adds a required parameter. Across a book of SMB clients, each running a slightly different stack, those dependencies multiply. It's the same maintenance burden that makes an AI agent built once still break differently at every client.
Why the stakes go up after the trial
On September 25, 2026, Microsoft introduced a unified Copilot app that brings Chat, the Cowork agent, a redesigned Code environment and the persistent Autopilot agent into one experience, backed by Work IQ and Fabric IQ for enterprise context. Computerworld's coverage notes that Cowork, Code and Autopilot move to usage-based billing, while Chat and Copilot across Microsoft 365 stay on the per-user license. One analyst quoted in that piece warned that if employees regularly have to undo an agent's work, it can point to "stale context, poor business rules or an unreliable data foundation."
For MSPs, that changes the math. A Copilot Business seat is a predictable per-user line item. Agentic work billed by usage, running against client data, is a margin line that grows with every wrong answer that someone has to redo. We've written about how AI quietly becomes an MSP margin leak when data isn't ready. Copilot in 30 is the entry point, and the data foundation you build during the trial is what the paid seats, and later the agents, will rely on.
A data-first playbook for running Copilot in 30
None of this argues against running the trial. It argues for scoping it differently. A practical approach for MSPs building their first cohort:
- Pick one scenario that crosses the Microsoft 365 boundary. Alongside the standard Outlook and Teams scenarios, choose one question the customer asks every week that depends on a line-of-business system, such as overdue receivables, open jobs or ticket history.
- Inventory the stack before day one. List the three to five systems the trial users touch daily and check each against Microsoft's connector gallery. Note which ones have no prebuilt connector.
- Choose synced or federated on purpose. Indexed data is searchable alongside Microsoft 365 content. Live, federated access keeps sensitive or fast-changing data in the source system. Financial data often belongs in the second category.
- Verify permissions travel with the data. Connectors enforce source-system permissions, but only if those permissions are right in the source. The oversharing problem Gartner flagged in SharePoint applies equally to a CRM that everyone has admin rights to.
- Decide who owns the connection on day 31. If the trial converts, someone has to keep the integration healthy. Price it into the managed service rather than absorbing it as unbilled engineering time.
That last step is the part MSPs can turn into recurring revenue. The connection layer between an SMB's line-of-business systems and Copilot is the durable service. Licenses are easy to resell. Keeping client data connected, consistent and correct as those systems change is where an MSP adds value. This is the layer Ngentix is built for: a semantic model of the data moving between systems and a self-healing runtime that re-maps connections when an upstream API or field changes. That way a custom integration built for one client's trial doesn't turn into a maintenance ticket every time a vendor ships an update.