Dext AI Connector for Microsoft Copilot: Setup, Permissions and Accounting Data Security

What Dext launched​

The connector gives AI assistants a way to pull information from a practice's existing Dext account. Partners can ask plain-language questions about clients, workflows, data health and team performance. Dext's examples include finding the clients with the lowest data health scores, finding which client took the most time last month, and checking a client's cash position before a meeting.

Dext's pitch is that a general-purpose chatbot doesn't know a practice's real numbers. Dext's CEO, Sabby Gill, says the connector grounds answers in the practice's own data rather than a guess. Fintech.ca ties the launch to a Dext survey of 500 Canadian accountants and bookkeepers. In that survey, half knew of businesses that lost money after acting on wrong AI-generated advice. Of those who had met AI mistakes, 44 per cent spent up to three hours a month correcting them. Those are vendor-commissioned survey figures. They say nothing about how well the connector performs.

Who can use it​

Eligibility is narrower than "Advanced partners" suggests. Dext's help material says the connector is for Practice accounts and isn't available to Business accounts yet. It requires a Practice Advanced account. Dext also describes parts of the rollout as an early preview. The help pages are inconsistent on status. The current capability guide says "early preview", while a search snippet of the connection article still shows an older "closed Beta" label. Check your own account's status before planning around it.

Claude and ChatGPT connect through their directories. For Copilot, Dext's guide tells users to contact their account manager or Dext support.

What it can and can't retrieve​

Dext's capability guide is more detailed than the press release. Highlights:

• Client and practice lists: You can filter by status, plan, accounting integration, bookkeeping cadence and active modules. Results come back 50 clients per page, so large practices may need several pages for totals.
• Users and access: You can look up roles, last logins, client access and account managers. Access, time-tracking and account-manager queries are admin-only.
• Time tracking: You can query by client, by colleague, or by both, with a default window of the last 30 days. It's admin-only, and there's no data from before a practice started tracking time in Dext.
• Financial snapshots: These cover revenue, expenses, profit and cash-flow indicators, with bulk comparisons capped at 20 clients. If a client isn't connected to an accounting integration, you get connection guidance instead of figures.
• Aged debtors and creditors: These use buckets of 0–30, 31–60, 61–90 and over 90 days. They work one client at a time, with no single cross-client roll-up.
• UK tax helpers: These cover Corporation Tax estimates, VAT summaries, Annual Investment Allowance flags and P11D checks. Dext says they're for sense checks, not filing. The Corporation Tax estimate skips capital allowances, depreciation add-backs and entertainment disallowances. The tools aren't meaningful for non-UK clients.
• Other data: Invoices, journals, fixed asset registers, workflow checks and Data Health insight catalogues are covered. Live bank balances come only from Xero.

Many of these functions need the client to have the Data Health & Insights add-on, formerly called Precision.

Some things are out of scope. The connector doesn't expose document images or PDFs, email or notifications, or subscription and billing data. It also can't create, post, amend or submit anything. It can't file returns.

Setting it up in Copilot​

The setup splits into an admin step and a user step.

Admin step. Dext's workspace guide says you need admin rights in Claude, ChatGPT or Copilot, plus a Dext practice account enabled for the connector. For Copilot, an admin goes to the Microsoft 365 admin centre, then Copilot connectors, then Your connections. Microsoft-published federated connectors are on by default, but partner connectors like Dext need admin approval before anyone can use them. Each Dext practice account can authenticate only one workspace, so choose the right one. Once approved, Dext shows up under Tools, then MCP Connectors, for the workspace.

User step in Copilot Studio. Dext documents these steps:

1. Open Copilot Studio and select Agents.
2. Choose New Agent, or pick an existing one.
3. Select Tools, then the + button.
4. Search for Dext and filter to Model Context Protocol (MCP).
5. Next to Connection, choose Create new connection. A display name is optional.
6. Choose your practice and authorise access. Copilot shows the practice you're currently logged into Dext with.
7. Tick the consent box and select Allow.

You have to add the Dext connector through the Tools menu for every new agent you create. To check it works, ask "List my clients in Dext." If you see your client list, you're connected.

The credentials setting to check​

If you publish a Copilot Studio agent for colleagues, Dext says to confirm the tool uses end-user credentials rather than the creator's. The path is Tools, then Additional details, then Credentials to use. Dext says this is the default, but verify it. Otherwise a colleague with fewer Dext permissions could see data the agent's creator can access. "Read-only" doesn't protect against that kind of over-sharing. It only means the connector can't change records.

Microsoft's own documentation adds relevant context. MCP servers reach Copilot Studio through connector infrastructure, so they can use enterprise controls such as Virtual Network integration, Data Loss Prevention controls and multiple authentication methods. Whether those controls cover a given Dext deployment depends on your tenant's configuration. Dext's pages don't describe it, so I'm not assuming it.

Common failure points​

• "Dext wasn't connected" in Claude: This usually means you signed in with a Business account. Business Admins can't connect either, and changing your role doesn't help.
• "Access to app.dext.com was denied": Check you're logged into the correct practice if you have access to more than one.
• Connector missing in Claude or ChatGPT: Either your IT admin hasn't added it, or you're on a personal account. Dext access is set at workspace level, so personal accounts won't see it.
• Chat started before connecting (ChatGPT): Refresh the page or start a new chat.
• Unexpected empty answers: Check the client has an accounting integration and, where needed, the Data Health & Insights add-on.

Data handling: what the security claims cover​

Dext says authentication runs through the user's Dext account and the connector only retrieves data that user may already see. These are Dext's product claims, not the result of an independent audit.

The more important point for compliance teams is where the data goes. Dext's launch FAQ says only the specific data needed to answer a question is retrieved. That response is then processed by whichever provider the partner connected, OpenAI, Anthropic or Microsoft. That provider's data policies apply to the exchange. Dext recommends reviewing each provider's enterprise data policies. It notes that many offer options where data isn't used for training. Financial data about clients will be passed to a third-party model, whatever the connector's read-only status.

Dext's own guide also says the AI tool writes the answer, and that results can be incomplete or wrong. It calls the tools a fast first look rather than a substitute for review.

Practical checklist for IT and practice leads​

• Confirm the practice is on Practice Advanced, not a Business account.
• Have a Microsoft 365 admin review and approve the partner connector before staff try to use it.
• Check that Copilot Studio agents shared with colleagues use end-user credentials.
• Review the chosen AI provider's retention and training settings for your account tier. Dext's materials don't establish those settings.
• Keep a human review step for anything client-facing, especially tax estimates.

Bottom line​

This is a bounded, read-only retrieval layer, not an autonomous accounting agent. It's useful for triage questions like "who's behind?" and "where did the hours go?" The rough edges are the preview status, the narrow account eligibility, and the add-on dependencies. The thing to get right is credentials and provider data policy, not the connector itself.