Ship deep Dynamics 365 integrations in days

Dynamics 365 spans more than 1,000 tables across Sales, Customer Service, Field Service, and Dataverse, behind Microsoft Entra ID and the OData Web API. With Ampersand, you can get this integration live for your customers in days.

Schedule a demo See Dynamics 365 guide

Build a custom data model to handle complex configurations

No two Dynamics 365 environments are the same. Every customer licenses different modules and adds custom tables and columns. AI agents need infrastructure that understands Dynamics 365 at the per-tenant level.

3 / 4 customers

3 / 8 customers
  • Customer A: Contact (standard), Opportunity (standard), Invoice (custom)
  • Customer B: Lead (standard), Quote (standard), Account (standard)
  • Customer C: Account (standard), Sales Order (standard), Project (custom)

Enable software and agents to take bi-directional action

With Ampersand, your engineers don’t need to learn OData queries or the Dataverse Web API. Simply declare the actions you want your agents to take: read, write, proxy.

Example. Write: “Mark the opportunity won when the contract is signed.”

  1. Ampersand refreshes the token for this customer’s instance.
  2. Ampersand writes to the fields this customer mapped.
  3. Ampersand updates the opportunity through the Dataverse Web API.
  4. Ampersand confirms the write to your product.

Ensure your Dynamics 365 integration is always available

  • Managed auth

    Fully offload Microsoft Entra ID OAuth, refresh tokens, and each customer’s instance URL, so customers don’t have to sign in again.

  • Full historic backfill

    Load each customer’s history when they install, then keep it current with scheduled reads on the cadence you choose.

  • Schema drift detection

    Get notified when fields are created, deleted, or changed in any customer’s Dynamics 365, before the change breaks your integration.

Jeson Patel CTO at @11x
“If you have ever integrated with a CRM, you know how complicated that is. It is actually the number one source of issues that we run into with our customer integrations. And Ampersand removes a lot of that complexity. I want my teams to be focused on building the product, and not having to focus on complex CRM integrations.”
11x See full case study
Jeson Patel

Not all Dynamics 365 integrations are created equal

Dynamics 365 is the CRM of choice for Microsoft-first enterprises. With Ampersand, your developers can create a best-in-class Dynamics 365 integration.

In-House DIY Build Unified APIs Embedded iPaaS Ampersand
Data schema that works for all customers Lots of switch statements and special casesOnly access standard objects and fieldsBuild customer-specific workflows Flexible model with mappings
Table coverage Write and maintain OData queries for every table you needOnly common models and their standard fieldsLimited to the tables its prebuilt actions cover Every table in Sales, Customer Service, Field Service, and Dataverse
Schema drift protection Manual incident debuggingNot supportedNot supported Get notified about schema changes
OAuth token custody You own the tokens, but you also have to manage refreshesVendor lock-inVendor lock-in Export at any time via API
Integration workflow Imperative custom codeSingle API clientDrag-and-drop, not integrated with Git Declarative manifest you can version control
Build vs. Buy Unified API vs. Ampersand

The Dynamics 365 tables your agents can read and write

Ampersand covers more than 1,000 tables across the Sales, Customer Service, and Field Service modules, plus every core Dataverse table.

Objects What’s included Read Write
Sales
  • Contacts
  • Leads
  • Opportunities
  • Quotes
  • Sales orders
  • Products
  • Discounts
  • Goals
  • Marketing lists
  • Every table in the Sales reference
Supported Supported
Customer Service
  • Every table in the Customer Service reference
Supported Supported
Field Service
  • Every table in the Field Service reference
Supported Supported
Dataverse (In every environment)
  • Every table in the Dataverse tables reference
Supported Supported

Each scheduled read is a full read of the table, because the connector does not support incremental reads yet.

See every table in the docs

Questions people ask before they book a demo

  • Which Dynamics 365 tables can I read and write?

    Every available table in the Sales, Customer Service, and Field Service modules, plus every table in the Dataverse tables reference. That includes contacts, leads, opportunities, quotes, products, and sales orders.

  • How do my customers connect their Dynamics 365?

    You register one app in Microsoft Entra ID and add its client ID and secret to Ampersand. Your customers then sign in with OAuth, and Ampersand adds their instance URL to the scopes and refreshes their tokens.

  • Can I get real-time updates from Dynamics 365?

    Not today. Ampersand backfills each customer’s full history and then runs scheduled reads at the cadence you set. Each scheduled read does a full read, because the connector does not support incremental reads yet.

  • Does Ampersand offer a unified API?

    Ampersand doesn’t offer a unified API. It works with Dynamics 365’s own objects and fields as each customer sets them up, which differs from how a unified API works. We also give you the primitives to build your own unified data model.