Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Working with Dynamics 365 Data in LINQPad
Execute LINQ queries to Dynamics 365 data in LINQPad.
The CData ADO.NET Provider for Dynamics 365 enables you to use standard ADO.NET interfaces like LINQ and the Entity Framework to work with Dynamics 365 data. This article will demonstrate the process of establishing a connection from LINQPad and executing LINQ queries.
About Dynamics 365 Data Integration
CData simplifies access and integration of live Microsoft Dynamics 365 data. Our customers leverage CData connectivity to:
- Read and write data in the full Dynamics 365 ecosystem: Sales, Customer Service, Finance & Operations, Marketing, and more.
- Extend the native features of Dynamics CRM with customizable caching and intelligent query aggregation and separation.
- Authenticate securely with Dynamics 365 in a variety of ways, including Azure Active Directory, Azure Managed Service Identity credentials, and Azure Service Principal using either a client secret or a certificate.
- Use SQL stored procedures to manage their Dynamics 365 entities - listing, creating, and removing associations between entities.
CData customers use our Dynamics 365 connectivity solutions for a variety of reasons, whether they're looking to replicate their data into a data warehouse (alongside other data sources)or analyze live Dynamics 365 data from their preferred data tools inside the Microsoft ecosystem (Power BI, Excel, etc.) or with external tools (Tableau, Looker, etc.).
Getting Started
Create the Data Model
After downloading and installing both the provider and LINQPad, create a new class library project within Visual Studio.
See the help documentation for a guide to setting up an EF 6 project to use the provider.
Right-click your project and click Add -> New Item -> ADO.NET Entity Data Model. In the resulting dialog, select Code First from database. Click New Connection and specify the connection string options in the resulting wizard.
Edition and OrganizationUrl are required connection properties. The Dynamics 365 connector supports connecting to the following editions: CustomerService, FieldService, FinOpsOnline, FinOpsOnPremise, HumanResources, Marketing, ProjectOperations and Sales.
For Dynamics 365 Business Central, use the separate Dynamics 365 Business Central driver.
OrganizationUrl is the URL to your Dynamics 365 organization. For instance, https://orgcb42e1d0.crm.dynamics.com
Below is a typical connection string:
OrganizationUrl=https://myaccount.operations.dynamics.com/;Edition=Sales;
Select the desired tables and views and click Finish to create the data model.
- Build the project. The generated files can be used to create the Dynamics 365 connection in LINQPad.
Connect to Dynamics 365 Data in LINQPad
After you have obtained the required connection properties and created the data model assembly, follow the steps below to start using the data model in LINQPad.
Open LINQPad and click Add Connection.
Select the "Use a typed data context from your own assembly" option.
Select Entity Framework DbContext.
Click Browse next to the Path to Custom Assembly box and browse to your project folder. Browse to the .dll or .exe under the bin folder.
- Select the name of the DbContext.
- If you saved your connection string in App.Config, specify the path to the App.config.

You can now query Dynamics 365 data through LINQPad. For examples of the supported LINQ queries, see the "LINQ and Entity Framework" chapter in the help documentation.
