Microsoft opens Dataverse to outside coding tools

On 6 July 2026 Microsoft made its Dataverse plugin available in the Claude Cursor and GitHub Copilot marketplaces. The same update added the MCP catalog to Copilot Studio, Azure AI Foundry, and Microsoft 365 Copilot. Sixty-plus servers now sit in the catalog. A new certification program lets independent software vendors submit connectors for review. Companies can also add their own internal MCP servers. The changes require Partner Center registration and specific manifest details for any certified connector.
Before this update, Dataverse data stayed inside Microsoft tools and any external agent had to be built or approved by developers who understood the platform. Knowledge workers could assume their data stayed within the Microsoft 365 boundary unless an admin explicitly opened it. Now third-party agents can request access through a published standard, and certified connectors will carry an official stamp. The decision about which systems can read or write Dataverse records will move from IT policy to a marketplace approval process that most teams have not yet reviewed.
Analysis
Ignore the marketplace noise for now and write down the three Dataverse tables your team actually touches in daily work. Then ask your admin which of those tables should remain off-limits to any external agent before the first certified MCP appears in your tenant.
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Microsoft opens Dataverse to outside coding tools", Collab365 Spaces. 1 source referenced.