---
title: "Microsoft Dataverse connector for agents — authorization and setup — AgentSky"
description: "Add grounded enterprise data and make your copilots actionable with Microsoft Dataverse, the enterprise data platform for Copilot. Connect Microsoft Dataverse to AgentSky with managed OAuth."
url: https://agentsky.dev/connectors/microsoft_dataverse
---

# Microsoft Dataverse

Add grounded enterprise data and make your copilots actionable with Microsoft Dataverse, the enterprise data platform for Copilot. Connect your account through managed OAuth to use the available operations in an agent task.

[Repo](https://agentsky.dev/auth/start?returnTo=%2Fconnectors%2Fmicrosoft_dataverse%3Fresume%3D1)

Connect Microsoft Dataverse using the Connectors control before sending. Authorization opens separately and your draft stays here.

Setup

## Connect Microsoft Dataverse with an explicit scope.

You need an AgentSky account and authority to connect the application account. Start with a read-only task before allowing changes.

01

### Find the application

Open connector settings and search for Microsoft Dataverse. If the catalog is unavailable, retry its load; an unavailable list is not proof the app is unsupported.

02

### Review authorization

Review the Microsoft Dataverse account, workspace and permissions on the authorization screen. Your organization's policies or administrator approval may limit which resources the connection can access.

03

### Verify a bounded task

Name one Microsoft Dataverse resource you can already access and ask the agent to check whether a read operation is available. If it is, retrieve and summarize that resource without changing it. If it is not, ask the agent to explain the missing operation or permission.

Verify access and results

## A connected account is the start of the workflow.

Open the same resource in Microsoft Dataverse and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.

- Access troubleshooting If Microsoft Dataverse access fails, check the connected identity, resource sharing and requested permissions. Reconnect an expired or revoked account in connector settings. If the connection is healthy but an operation is unavailable, changing accounts may not resolve it.
- Available actions The runtime discovers the connector's current operations and input requirements. Do not assume every feature in the application's website is available as an agent action.
- Authorize changes explicitly For writes, specify the target and the allowed change. An instruction to draft or analyze is not permission to publish, send or delete.

## Microsoft Dataverse connector questions

## Related resources

[Claude Code + Microsoft DataverseUse Microsoft Dataverse with Claude Code in the shared Composer.](https://agentsky.dev/agents/claude-code/connectors/microsoft_dataverse) [Codex + Microsoft DataverseUse Microsoft Dataverse with Codex in the shared Composer.](https://agentsky.dev/agents/codex/connectors/microsoft_dataverse) [OpenClaw + Microsoft DataverseUse Microsoft Dataverse with OpenClaw in the shared Composer.](https://agentsky.dev/agents/openclaw/connectors/microsoft_dataverse) [OpenCode + Microsoft DataverseUse Microsoft Dataverse with OpenCode in the shared Composer.](https://agentsky.dev/agents/opencode/connectors/microsoft_dataverse) [Hermes + Microsoft DataverseUse Microsoft Dataverse with Hermes in the shared Composer.](https://agentsky.dev/agents/hermes/connectors/microsoft_dataverse) [Kimi Code + Microsoft DataverseUse Microsoft Dataverse with Kimi Code in the shared Composer.](https://agentsky.dev/agents/kimi-code/connectors/microsoft_dataverse) [DeepSeek Harness + Microsoft DataverseUse Microsoft Dataverse with DeepSeek Harness in the shared Composer.](https://agentsky.dev/agents/dsh/connectors/microsoft_dataverse) [pi + Microsoft DataverseUse Microsoft Dataverse with pi in the shared Composer.](https://agentsky.dev/agents/pi/connectors/microsoft_dataverse) [All connectorsUnderstand managed application access.](https://agentsky.dev/connectors) [ChannelsChoose where the agent conversation happens.](https://agentsky.dev/channels) [PricingReview charges before running work.](https://agentsky.dev/pricing)

## Connect the right Microsoft Dataverse account.

[Open connector settings](https://agentsky.dev/connectors)

## Frequently asked questions

### How do I connect Microsoft Dataverse to AgentSky?

Sign in to AgentSky, open Connectors in the Composer and search for Microsoft Dataverse. Choose Connect, complete the provider's authorization flow, and return to your draft. Check that the intended account appears as connected before sending.

### Do I need a Microsoft Dataverse API key?

This listing uses managed OAuth. Authorize the account in the provider's flow; do not paste a password or API key into the Composer. Any account, plan or administrator requirements are determined by Microsoft Dataverse.

### What can my agent do in Microsoft Dataverse?

The runtime discovers current operations and their required inputs. A catalog listing does not promise every feature of Microsoft Dataverse. Start by asking which operation supports your task, and specify the resources and changes you authorize.

### Does connecting Microsoft Dataverse make agent tasks free?

No. Account authorization and task usage are separate. AgentSky bills compute and model usage according to its pricing. Any Microsoft Dataverse subscription, API quota or provider charge remains separate; review those limits before running a task.

---

Markdown copy of https://agentsky.dev/connectors/microsoft_dataverse. Every agentsky.dev page has one: add `.md` to its address or send `Accept: text/markdown`. Start from https://agentsky.dev/llms.txt.
