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

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

×