New Copilot with Home, Code and Autopilot: what it means for partners

Microsoft's latest Copilot announcement is more than a feature refresh. It changes where work starts, who gets to build software inside a tenant, and how customers pay for AI. For Microsoft partners, each of those shifts has a commercial consequence, from how ISVs get discovered to how CSPs quote and forecast.

If you sell into Microsoft 365 customers in Australia or across APAC, this is a good moment to revisit your positioning before the noise from Microsoft Ignite arrives in November.

What Microsoft announced

Microsoft says the Copilot app is being reorganised around three new capabilities, plus a set of platform and pricing changes:

• Home brings Chat and Cowork together as the starting point for work, with Word, Excel and PowerPoint built into the experience through what Microsoft calls Office in Copilot.
• Code lets non-developers describe an app, dashboard or automation in plain language and have Copilot build it. Microsoft says it uses the same underlying technology as GitHub Copilot, runs in a sandbox and can be hosted within the customer's tenant.
• Autopilot, previously known as Scout, is a persistent agent with its own identity and memory that works on goals over days, not just prompts.
• Copilot Managed Runtime is a preview hosting layer for apps built in Cowork, Code and Copilot Studio, which Microsoft is opening to third-party and pro-code developers.
• A plugin registry brings Microsoft, partner and custom plugins into one catalog that IT can govern.
• Copilot is now grounded in Dynamics 365 and Power Platform data and workflows (public preview over the next month), and Fabric IQ brings in context from Power BI semantic models.
• Pricing splits into a user subscription license for everyday AI and usage-based billing for agentic work, backed by new FinOps for AI controls in Agent 365.

Microsoft says Home and Code begin rolling out through its Frontier program in the coming weeks, with Autopilot moving to private preview at the end of the month.

Why it matters for Microsoft partners

The plugin registry is the headline for ISVs. A governed, central catalog inside Copilot is effectively a new storefront, and one IT admins will actually browse because it sits inside the tool their users already have. Being absent from it will be noticed by customers who are trying to standardise on Copilot.

The pricing split matters just as much. Once agentic work is metered, every Cowork task and Autopilot run has a cost attached. Customers will want help setting spending policies, deciding which teams get which models, and proving value. That is services revenue for CSPs and MSPs that did not exist in a flat per-seat world.

Grounding in Dynamics 365 and Power Platform also raises the stakes on data quality. Copilot pulling deal history into a proposal is only impressive if the CRM is accurate. Dynamics partners have a fresh reason to sell data readiness and clean-up work.

Finally, Code and Copilot Managed Runtime blur the line between business users and developers. Partners with Power Platform or app modernisation practices should expect customers to ask how to govern a wave of citizen-built apps.

What partners should do next

1. Plan your plugin strategy now. ISVs should scope which product capabilities make sense as a Copilot plugin, then align that roadmap with existing Microsoft Marketplace listings so the story is consistent wherever a buyer finds you.
2. Package a FinOps for AI offer. CSPs and MSPs can build a fixed-scope engagement around usage-based billing: policy design, model access by user group, and monthly value reporting. Name it clearly and put it on your website before customers start asking.
3. Refresh your co-sell narrative. Update solution briefs to reference Home, Code or Autopilot where your offer genuinely connects. Microsoft sellers will be talking about these capabilities, and co-sell works best when your story matches theirs.
4. Lead with data readiness. Dynamics and Power Platform partners can run campaigns on preparing CRM and ERP data for Copilot grounding, using a short assessment as the call to action.
5. Build content for answer engines. Buyers will search for plain-language explanations of USL versus usage-based billing. Clear FAQ-style pages help you show up in AI answers as well as search, which is the core of answer engine optimisation (AEO).
6. Use Ignite as a campaign hook. Plan a local briefing or webinar after Ignite that translates the announcements for Australian customers, and check whether MDF can fund it.

How UBE can help

UBE works with Microsoft ISVs, CSPs and MSPs to turn announcements like this into positioning, campaigns and co-sell-ready content. Our Microsoft partner marketing team can help you package a plugin or FinOps offer and take it to market, or you can get in touch to talk through your Copilot go-to-market plan.