Microsoft Copilot plugs Power BI, Dynamics
- Microsoft’s new Copilot Cowork preview added plugins for Dynamics 365 and Fabric IQ, plus partner integrations like LSEG and Miro, so agents can act across work apps. - The Power BI side comes through Fabric IQ, which can query datasets and generate reports, while Dynamics plugins can manage cases, leads, pipeline, finance, and supply-chain workflows. - The shift matters because Copilot is moving from chat to execution — but only in Frontier preview, with admin approval, permissions, and connector governance doing the safety work.
Microsoft is pushing Copilot into a more agent-like phase. The point is no longer just asking a bot to summarize a document or draft an email. The point is letting that bot reach into the systems where work actually lives — CRM, analytics, planning boards, even licensed market data — and do something useful there. That is the real news behind Microsoft’s new Copilot Cowork plugin rollout in early May 2026. ### What did Microsoft actually launch? Microsoft said on May 5 that Copilot Cowork is getting new capabilities through its Frontier preview program, including plugins that connect Cowork to more business tools. The official plugin list now includes Microsoft’s own Dynamics 365 integrations and Fabric IQ, plus partner offerings that pull in outside platforms and data. Cowork itself is framed as the step from “chat” to “execution” — a system that can plan, act, and produce outcomes across apps instead of staying inside a prompt box. (microsoft.com) ### Where do Power BI and Dynamics fit? Power BI shows up through Fabric IQ. That plugin brings Microsoft Fabric and Power BI data into Cowork workflows so the agent can query datasets, generate reports, and surface business-intelligence insights from a Fabric workspace. Dynamics comes in through separate plugins for Sales, Customer Service, and ERP, which means Cowork can work with leads, opportunities, support cases, financial data, supply-chain information, and operations workflows. (microsoft.com) ### What are “skills” here? Microsoft’s language is a little slippery, but basically a plugin can include connectors, skills, or both. Connectors are the pipes — they link Cowork to outside services and data sources. Skills are the packaged abilities on top — the domain-specific know-how that lets Cowork do things like financial analysis, legal research, or HR workflows without you rebuilding the logic every time. That is why admins care about this rollout: it turns repeatable tasks into reusable building blocks. (learn.microsoft.com) ### Why does LSEG matter so much? LSEG is the clearest sign Microsoft wants Copilot inside high-value professional workflows, not just general office work. LSEG and Microsoft said in October 2025 that agents built in Copilot Studio and deployed in Microsoft 365 Copilot could be enabled with licensed LSEG financial data through an MCP server. LSEG said its AI-ready content spans more than 33 petabytes, which gives you a sense of the scale and why this matters for banks, traders, and analysts. (learn.microsoft.com) ### And what’s the Miro angle? Miro is less about transactions and more about shared context. Microsoft’s connector lets Copilot index Miro boards so users can find board content, retrieve action items, and use that material inside Microsoft 365 experiences and custom agents. The connector keeps Miro’s permission model in place, but it also widens the set of places where board content can surface. That is great for workflow continuity — and exactly why governance teams get nervous. (lseg.com) ### So is this broadly available? Not yet. The big catch is that Cowork plugins are part of the Frontier preview program, and Microsoft’s own docs repeatedly flag them as prerelease features that may change. Plugins come through the Microsoft 365 App Store or admin deployment, and some may require organizational approval before users even see them. In other words, this is real product movement, but it is still controlled rollout, not blanket availability. (learn.microsoft.com) ### Where does the risk actually sit? The risk is not some sci-fi “AI goes rogue” thing. It is the old enterprise problem — permissions, connectors, and scope — now wrapped in a much more capable interface. Microsoft leans hard on existing permissions, Entra ID authentication, and governance controls. But once a copilot can read across CRM records, BI datasets, board content, and third-party financial feeds, a bad configuration matters more because the assistant can stitch those sources together for a user in one place. That is the tradeoff. (learn.microsoft.com) ### Bottom line? This is Microsoft trying to make Copilot useful where enterprise work actually happens. Power BI, Dynamics, LSEG, and Miro are not random logos — they are the systems that hold revenue data, customer state, planning context, and market intelligence. If the connectors and permissions hold up, Copilot starts to look less like a writing assistant and more like an operating layer for business software. (microsoft.com) (learn.microsoft.com)