Dynamics 365 CRM: API integration + change-control repo

Published July 2, 2026

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 34

1Dynamics 365 CRM: API integration + change-control repo 2Dynamics 365 CRM: Last Contact Engagement tracking on Accounts 3Turning a sales-intelligence export into a clean CRM data model 4Dynamics 365 CRM: contacts inherit their company’s website, and emails timestamp by send time 5Your SEO health now lives as a dashboard inside the CRM 6Contact form duplicate detection now reads the request, not just the address 7Marketing list members now show engagement and account fit 8Campaign responses now create leads behind a confirmation step 9Three CRM automations passed their tests without running the code that had just changed 10A signature defect that three mailboxes agreed was not there 11Asking whether a partner is involved, instead of inferring it 12Choosing what runs the AI layer in the CRM sales process 13A read-only CRM endpoint for scoring outside the desktop 14Why a corrected email signature kept sending the old one 15Two local dependencies, and only one was obvious 16Filing a generated document to the record automatically 17The rehearsal that guards every process change had been failing silently 18An email step in the sales process can now be excused, not only sent 19A one to one email from a lead left the engagement record blank 20One meeting that served two process steps, recorded as two 21A setting that stored correctly, read back correctly, and was never in force 22Generating a product catalogue from one canonical file 23Three date fields that existed on every row, and had never once been written 24Unused, unreferenced, and still not safe to delete 25A measure that could not record early 26A sales automation that runs as itself, not as an administrator 27A stage change that was refused, and reported as a success 28An Email Validation Gate for Campaign Sends in the Authgnosis CRM 29Marketing List Membership and Campaign Frequency Caps in the Authgnosis CRM 30A Send Guardrail for Unsubscribe Links in the Authgnosis CRM 31Automated Bounce Handling for Campaign Email 32Nurturing Cadence Automation and an Email Send Gate in the Authgnosis CRM 33A Hard Stop on Calendar Invites from AI Agents in the CRM 34Bounced Campaign Email Now Updates the CRM on Its Own

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 →

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.