How to Connect Microsoft Dynamics 365 to Claude for AI-Powered CRM Insights

You connect Microsoft Dynamics 365 to Claude by linking your Dynamics 365 account to Windsor.ai, then adding the Windsor.ai connector inside Claude. Once both are connected, Claude can query your live Dynamics 365 data directly, no CSV exports, no custom code, and no Dynamics report builder.

Here’s the problem it solves: Dynamics 365’s native views are built for fixed questions, an opportunity pipeline view, a lead list, an account aging report. The moment you have a follow-up question, like which opportunities above 70% close probability haven’t moved stage in two weeks, you’re back in the view builder assembling a new report from scratch.

Cross-module questions are harder still. Which lead source produces the highest-value opportunities, not just the most leads? Which top-rated accounts are carrying an overdue balance? Answering either one usually means pulling data from the Opportunity, Lead, Campaign, and Account entities separately and reconciling the numbers by hand.

With Windsor MCP, your Dynamics 365 data streams directly into Claude, structured and ready to query, so you can ask about your pipeline, leads, campaigns, or accounts in plain language and get an answer in seconds.

🚀 Automate your Microsoft Dynamics 365 analysis in Claude with Windsor MCP. Get started free, no credit card required.

2 steps to connect Microsoft Dynamics 365 to Claude

The setup takes about a minute and doesn’t require any code.

📖 Full walkthrough: windsor.ai/documentation/windsor-mcp/how-to-integrate-data-into-claude/.

Prerequisites

Before you begin, make sure you have access to:

A Windsor.ai account (free forever plan, no credit card, or paid plans from $19/month)
A Microsoft Dynamics 365 account with at least one Account record set up
A Claude account with access to Connectors

Step 1. Connect Microsoft Dynamics 365 to Windsor.ai

Go to onboard.windsor.ai/app/dynamics365 and select Microsoft Dynamics 365 from the list of data sources.
Sign in to your Microsoft account and authorize Windsor.ai to access your Dynamics 365 data.
Connect additional Dynamics 365 environments the same way if you manage more than one, useful for agencies handling several client accounts.

Once connected, Windsor pulls your CRM data directly from the Dynamics 365 API and structures it into a clean, LLM-ready format, normalizing opportunity stages, lead statuses, and account fields so Claude can reason across them accurately.

Step 2. Add the Windsor.ai connector in Claude

In Claude, open Customize, then Connectors, and search for “Windsor.” Click Add to install it, this is a native one-click install, there is no URL to paste and no custom connector setup. Sign in to Windsor.ai when prompted, then pick your Microsoft Dynamics 365 connector to finish.

💡 Quick tip: Set permissions to “Always allow” so your Dynamics 365 data is available in every Claude conversation without reauthorizing.

Now verify the connection. Start a new chat in Claude and try this prompt:

List the data sources connected to my Windsor account. Do you see Dynamics 365 there?

If Dynamics 365 shows up in the list, you’re set. You can now ask Claude about your Dynamics 365 data in plain language.

The metrics that matter for Microsoft Dynamics 365

Windsor exposes thousands of fields for Dynamics 365, centered on the Account entity. Here are the ones that come up most often in sales and RevOps conversations.

Metric	What it tells you
Opportunity – Estimated Value	The projected value of an open deal before it closes, the number sales forecasts are usually built on.
Opportunity – Actual Value	The confirmed revenue amount once a deal is marked won, your real bookings figure.
Opportunity – Sales Stage	Which stage of your sales process a deal currently sits in, from qualify through close.
Opportunity – Close Probability	The likelihood, as a percentage, that an open deal will close successfully.
Opportunity – Estimated Close Date	When a rep expects a deal to close, the date forecasts and pipeline reviews get built around.
Lead – Lead Source Code	Which channel or campaign originally generated a given lead, the starting point for channel-level tracking.
Lead – Estimated Value	The projected deal value tied to a lead, before it’s qualified into a full opportunity.
Lead – Status Code	A lead’s current qualification status: open, qualified, or disqualified.
Campaign – Expected Revenue	The revenue a marketing campaign was projected to generate when it was planned.
Campaign – Total Actual Cost	What a campaign actually cost to run, the number you weigh against expected revenue to judge ROI.
Account – Aging90	How much of an account’s balance is more than 90 days overdue, a key signal of collection risk.
Account – Account Rating Code	The internal rating your team has assigned an account, for example how strategically important it is.

What to ask Claude about your Microsoft Dynamics 365 data: prompt ideas

Pipeline and opportunity performance

Show me all open opportunities by sales stage, with estimated value and close probability, sorted by estimated close date.

Which opportunities have a close probability above 70% and an estimated close date in the next 30 days?

Campaign activity tracking

Compare actual cost against expected revenue for each campaign and flag any campaign that ran over budget.

Account and lead conversion

Break down my leads by lead source code and status code, and show the total estimated value tied to each source.

List accounts with an aging90 balance above zero alongside their account rating code, so I can see which top-rated accounts have overdue balances.

The Dynamics 365 connection through Windsor is read-only: Windsor’s write actions currently cover Meta Ads, Google Ads, TikTok Ads, LinkedIn Ads, Microsoft Ads, Instagram, Google Business Profile, Klaviyo, and Amazon Seller Central, and Dynamics 365 isn’t on that list, so use it to analyze and report on your CRM data rather than to edit records.

Bonus: analyze Microsoft Dynamics 365 alongside your full stack

Windsor connects 350+ marketing and business data sources, so Microsoft Dynamics 365 doesn’t have to live in its own silo. A few realistic blends:

True sales-qualified CAC. Blend closed-won opportunity value from Dynamics 365 with spend from Google Ads and Facebook Ads to see what you’re really paying to acquire an account that turns into revenue, not just a click or a lead.
Lead-source-to-close tracking. Pair Dynamics 365 lead source and opportunity stage data with GA4 session data to trace which marketing channels actually produce leads that turn into closed deals, not just traffic.
Full-funnel marketing view. Combine Dynamics 365 campaign and lead data with your email marketing platform to see the whole funnel, from first touch to qualified lead to closed opportunity, in one conversation.

Other ways to connect Microsoft Dynamics 365 to Claude

Manual CSV export

You can export Account views from Dynamics 365 to CSV or Excel and upload the file into a Claude conversation. That works for a one-off question, but it’s a static snapshot the moment you download it, so every follow-up question needs a fresh export.

Zapier or Make

Zapier and Make can move Dynamics 365 records into another tool as part of a still-maintained workflow, which works if you already have automations built around them. Neither gives Claude a live view of your Dynamics 365 data the way the direct Windsor connector does.

Conclusion

Dynamics 365 already holds the full record of your pipeline, every opportunity stage change, every lead source, every account balance. What’s been missing is a fast way to turn that record into an answer, without building a new view every time the question changes.

Windsor MCP gives Claude live access to your Microsoft Dynamics 365 data. Instead of exporting reports or reconciling numbers across entities by hand, you can ask a direct question and get a structured answer in the time it takes to type it.

🚀 Connect your Microsoft Dynamics 365 data to Claude with Windsor MCP in about a minute. Get started free: onboard.windsor.ai/app/dynamics365.