- Home
- Resources
- Integrations
- Microsoft Dataverse
Claude Microsoft Dataverse connectorWhat Claude can do in your Microsoft Dataverse account.
The Claude Microsoft Dataverse connector lists 11 tools. 2 read your data, 6 write rows or tables, and 3 are names Microsoft says it retired. Here: what Claude can query and change, the two deletions that wait for you, and why the directory and Microsoft disagree.
Verified Trustpilot reviews · AI, automation & growth agency
Why your Power Platform team would plug Dataverse into Claude
You describe what you need in plain English and Claude works directly in your Dataverse tables: it runs a SELECT query, adds or corrects a row, even drafts a new table. No form to open, no app to build for a one-off fix. The flip side is real power over your data, so it pays to know which tools write and which ones wait for your go-ahead.
Answer a data question on the spot. A sales lead wants to know how many open opportunities sit with one region. Claude writes a Dataverse SQL SELECT and runs it with read_query, then explains the result instead of handing you a grid.
Fix records without a form. A customer changed address: update_record edits the existing row, and create_record inserts a new one when the contact is missing, returning the ID of the new row.
Prototype a table in the conversation. A project needs a small tracking table. create_table builds it from a schema you agree on with Claude, and update_table adjusts the schema or metadata later.
Now what to keep in mind. Deleting a row or a whole table only happens after your explicit approval, according to Microsoft. An administrator has to enable the Dataverse MCP server and allowed clients for your environment first. The directory lists this connector for Claude Desktop, Claude Code and the API, not for Claude on the web. And nothing runs by itself: no tool reacts when a record changes. That kind of event-driven flow belongs to an automation tool, a different job; our Integrations hub covers that side.
Five words before you start
The vocabulary you will see while connecting Dataverse to Claude.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude chooses the ones it needs by itself; the directory lists them by name.
- Authorization
- The Microsoft sign-in screen where you hand Claude the access it will use. Granted once per person, and you can revoke it later.
- Approval
- The confirmation Claude waits for before it goes through with a change to your data, shown in the conversation at that moment.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Dataverse.
Plug Microsoft Dataverse into Claude in three steps
- 01
Find Dataverse in Claude
In Claude's settings, open Customize, then Connectors, and look for Microsoft Dataverse. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in with your Microsoft account in the window Microsoft opens. If the link breaks later, Disconnect and connect again.
- 03
Read the authorization screen
Read Microsoft's consent screen before you accept. It belongs to Microsoft, not to Claude, and it sets what the access covers. The access can also be withdrawn later from the Microsoft side.
The 11 tools, grouped by what they do
Microsoft Dataverse gives Claude 11 tools: 2 that read your account, 6 that change something in it, and 3 no official source describes.
Two read, six write, and three are names that no source documents any more. Tool names stay as Claude shows them, in English.
- 2 read
- 6 write
- 3 not documented
Tools index
What Claude reads (2)
2 toolsTwo tools that look at your Dataverse data or its structure without touching it.
read_query
Runs a supported Dataverse SQL SELECT query and brings the rows back into the chat, where Claude reads and summarizes them for you.
search
Searches table schemas and business skills by keyword: the structure of your environment, not the rows inside it.
What Claude changes (6)
6 toolsSix tools that add, edit or delete rows and tables. Microsoft says the two deletions need your explicit approval; for the others, the general rule below applies.
create_record
Approval: see the ruleInserts a new row into a Dataverse table and hands back the identifier (GUID) of that row.
update_record
Approval: see the ruleEdits an existing row in a Dataverse table without going through the app's form.
create_table
Approval: see the ruleBuilds a brand-new table in Dataverse from a schema you specify, columns and types included.
update_table
Approval: see the ruleChanges the schema or metadata of a table that already exists, for instance to add a column the team now needs.
delete_table
Asks you firstRemoves an entire table from Dataverse, its structure along with what it holds.
delete_record
Asks you firstTakes a single row out of a Dataverse table, the narrowest kind of deletion this connector offers.
Retired names (3)
3 toolsThe directory still lists these three names. No source describes what they do, and Microsoft says they were removed from the server.
describe_table
No source describes this tool. Microsoft names it among the tools removed from the Dataverse MCP server and points to a newer replacement, even though the directory sheet still lists it. Whatever it may do, the general approval rule applies to it.
list_tables
Nothing in the documentation explains this one any more: Microsoft's page lists it as retired and replaced, and the directory keeps only its name on the sheet. Check the tool list Claude shows after connecting before counting on it; the general approval rule covers it.
fetch
No source documents what this name does today. Microsoft's page counts it among the retired tools, replaced by a newer one, while the directory sheet still shows it. The general approval rule below applies regardless of what it turns out to be.
What Claude asks you before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. On Dataverse, Microsoft adds its own rule for the two deletion tools.
On Team and Enterprise, workspace owners decide whether a member can let some actions through without being asked again. They can also cap what a connector may do for the whole organization, keeping reads open and closing writes, and nobody bypasses that from their own account. Claude also works with your rights and nothing more: a table your Microsoft account cannot reach stays closed to Claude. The official per-tool label (read-only versus write and delete) only exists in a connected account's settings.
Which plans it works on
None of the 819 sheets in the official directory shows plan availability. The connector-by-connector answer is published nowhere: it is a real gap in the catalog.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organization before each member can connect. Microsoft's own billing for the Dataverse side is a separate matter, covered in the limits below. For this connector's current state, check its sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a row is created or a field changes.
Only Microsoft documents this connector; no Claude help page covers it. The partner badge is not a security audit, and Anthropic says on every sheet that it does not pick the tools a publisher exposes or vouch for how they behave. Here the two official sources even disagree on the tool list itself, as the box below shows. Connect what comes from a publisher you trust. Every directory connector has its own page with us, for example the Claude affinity connector.
Which tools does the Dataverse connector expose today?
- Claude directory sheet ↗October 2026Out of dateEleven tools, including describe_table, list_tables, fetch and a search tool.
- Microsoft Learn, Dataverse MCP page ↗June 2026describe_table, list_tables and fetch were removed in favor of a new tool, and the old data search was renamed; search now covers metadata.
What this page followsWe follow Microsoft for the state of the server: its page names the retired tools explicitly, while the directory still carries the earlier list. Neither tells you what your own environment exposes, so check the tool list Claude displays once you are connected.
Need help connecting Microsoft Dataverse to Claude?
A person reads every message.