Dynamics 365 CRM: API integration + change-control repo

Microsoft Dynamics 365 CRM

Claude can now manage the Authgnosis CRM directly through the Dataverse API, with every future change tracked, auditable, and reversible through a new change-control repo wired into the daily close-out workflow. Stood up programmatic access to the Authgnosis CRM (Dynamics 365 Sales Professional). Claude now works the CRM through the Microsoft Dataverse API using a […]

In this series · Part 1 of 27

1Dynamics 365 CRM: API integration + change-control repo2Dynamics 365 CRM: Last Contact Engagement tracking on Accounts3Turning a sales-intelligence export into a clean CRM data model4Dynamics 365 CRM: contacts inherit their company’s website, and emails timestamp by send time5Your SEO health now lives as a dashboard inside the CRM6Contact form duplicate detection now reads the request, not just the address7Marketing list members now show engagement and account fit8Campaign responses now create leads behind a confirmation step9Three CRM automations passed their tests without running the code that had just changed10A signature defect that three mailboxes agreed was not there11Why a corrected email signature kept sending the old one12A read-only CRM endpoint for scoring outside the desktop13Choosing what runs the AI layer in the CRM sales process14Asking whether a partner is involved, instead of inferring it15An email step in the sales process can now be excused, not only sent16The rehearsal that guards every process change had been failing silently17A one to one email from a lead left the engagement record blank18Two local dependencies, and only one was obvious19Filing a generated document to the record automatically20One meeting that served two process steps, recorded as two21A setting that stored correctly, read back correctly, and was never in force22Generating a product catalogue from one canonical file23Three date fields that existed on every row, and had never once been written24Unused, unreferenced, and still not safe to delete25A measure that could not record early26A sales automation that runs as itself, not as an administrator27A stage change that was refused, and reported as a success

On this page

Free Revenue Lifecycle Assessment

Connect with Marissa Wright to receive a free Revenue Lifecycle Assessment Report on your own business.

Book a consult →

Claude can now manage the Authgnosis CRM directly through the Dataverse API, with every future change tracked, auditable, and reversible through a new change-control repo wired into the daily close-out workflow.

  • Stood up programmatic access to the Authgnosis CRM (Dynamics 365 Sales Professional). Claude now works the CRM through the Microsoft Dataverse API using a service principal instead of via Claude's CoWork screen control.
  • Debugged a chain of integration obstacles along the way: a missing Microsoft first-party service principal, a Claude/Microsoft Entra OAuth incompatibility, and a broken official MCP proxy. Resolved with the community mcp-dataverse server (79 tools).
  • Established a change-control repo in GitHub to mirror change-control for other Authgnosis projects: backlog, per-change audit trail, before/after snapshots, and documented rollback paths.
  • Wired the repo into the daily close-out workflow, including this Activity Feed publisher hook.

Other Posts