- Skills that read the CRM only ran on the machine holding the CRM connection, because that connection is a local process rather than an account level integration. A scoring skill therefore could not run in a browser session or on a schedule, whatever else was available to it.
- The obvious control, allowing only named skills to call the endpoint, is not available. The protocol carries no skill identity: a server sees tool calls and not what invoked them. So the restriction had to come from the operations on offer. The endpoint exposes a single account lookup rather than a general query interface, because a read-only credential answering arbitrary queries is still answering arbitrary queries.
- Read-only was verified by attempting a write and having it refused, rather than by reading the permission definition back. Those are different claims: one describes what the credential can do, the other describes what someone intended.
- Revenue figures are returned with their currency attached, because the scoring bands are set in Canadian dollars and a figure in another currency places a company a full band too high. The currency travels with the number so it cannot be dropped in transit.
A read-only CRM endpoint for scoring outside the desktop
Skills that read the CRM only ran on the machine holding the CRM connection, because that connection is a local process rather than an account level integration. A scoring skill therefore could not run in a browser session or on a schedule, whatever else was available to it. The obvious control, allowing only named skills […]
In this series · Part 13 of 22
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 there11Choosing what runs the AI layer in the CRM sales process12Why a corrected email signature kept sending the old one13A read-only CRM endpoint for scoring outside the desktop14Asking 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 file
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 →Other Posts