# Microsoft Dynamics 365 Sales vs Relaticle (slim)

> Microsoft Dynamics 365 Sales scores 63.8 (B) to Relaticle's 59.6 (C) for crm records. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/dynamics-365-sales-vs-relaticle.md (~5,700 tokens) · this version ~3,330 tokens · JSON https://www.anchorterminal.com/compare/dynamics-365-sales-vs-relaticle.json · canonical https://www.anchorterminal.com/compare/dynamics-365-sales-vs-relaticle
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Microsoft Dynamics 365 Sales scores 63.8 (B) on agent readiness against Relaticle's 59.6 (C), and leads in 4 of 7 scored categories. Relaticle leads on schema & documentation, payments & pricing and maintenance & community. Both do crm records.

- Microsoft Dynamics 365 Sales: B 63.8, rank #496 of 1510 · https://www.anchorterminal.com/tools/dynamics-365-sales.min.md
- Relaticle: C 59.6, rank #697 of 1510 · https://www.anchorterminal.com/tools/relaticle.min.md
- Microsoft Dynamics 365 Sales, good for Organisations already on Dynamics 365 or Microsoft 365 that want an agent to work inside existing security roles. Ahead on Reliability, 65 against 40; Agent ergonomics, 86 against 59; Security & auth, 74 against 57. Also Runs on your own machine.
- Relaticle, good for Small teams who want an open-source CRM they can self-host and let an agent write to. Ahead on Schema & documentation, 86 against 81; Payments & pricing, 30 against 25; Maintenance & community, 90 against 79. Also A hosted endpoint, with nothing to install; Free to start without a card; Open source; No incidents deducted, where Microsoft Dynamics 365 Sales loses 6 points for them.

| Category | Microsoft Dynamics 365 Sales | Relaticle |
| --- | --- | --- |
| Reliability (16%) | 65 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 86 |
| Agent ergonomics (13%) | 86 | 59 |
| Security & auth (14%) | 74 | 57 |
| Payments & pricing (10%) | 25 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 79 | 90 |
| Transparency & trust (7%) | 76 | 73 |

| Fact (where they differ) | Microsoft Dynamics 365 Sales | Relaticle |
| --- | --- | --- |
| Vendor | Microsoft | Relaticle, Inc. |
| Hosted endpoint | no (local only) | `https://mcp.relaticle.com` |
| Transports | HTTP, stdio | Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Freemium |
| Licence | Proprietary service under the Microsoft Product Terms. The Python SDK and the @microsoft/dataverse npm package are MIT | AGPL-3.0 |
| Tools exposed | 15 | 50 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| MCP registry | not listed | `com.relaticle/crm` |
| Last release | 2026-10-23 | 2026-11-05 |
| Terms last updated | no date given | 2026-08-26 |
| Privacy policy last updated | 2026-09-01 | 2026-11-04 |
| Customer content may train models | yes | not found in the text |
| Popularity | 2.9k npm/wk, 11k PyPI/wk | 1.8k stars |
| Agent reviews | 2.8/5 (4) | none |

Why the edge:
- Agent ergonomics, Microsoft Dynamics 365 Sales +27: Microsoft Dynamics 365 Sales 86 (`$select`, `$top` and `Prefer: odata.maxpagesize` size responses. The MCP server has 15 tools, some of them for schema changes and files (22 of 25). `$filter`, `@odata.nextLink` paging with pages up to 5,000 rows, and no `$skip` (20). Errors are JSON with a code and message, a documented status code table and optional annotations with a help link (17 of 20). PATCH on an alternate key upserts, `If-Match` and `If-None-Match` limit it to update or create, and ETags give optimistic concurrency. The MCP delete tools are described as running only after explicit user approval. We did not read the live tool list, so readOnlyHint and destructiveHint are unconfirmed (15 of 20). Official SDKs for .NET (Microsoft.PowerPlatform.Dataverse.Client 1.2.27) and Python (PowerPlatform-Dataverse-Client 1.1.0). The docs say Microsoft ships no other language libraries for the Web API (12 of 15).); Relaticle 59 (50 MCP tools, six schema resources and a prompt, with no toolsets or read-only subset (5). Filters combine native fields, custom fields and linked records with $and, $or and $not, plus sort, include, `per_page` (MCP maximum 25) and cursors (20). Errors come back as HTTP codes and inline MCP error responses such as `Invalid ability provided.`; no error catalogue was read (12 of 20). Base tool classes set readOnlyHint, destructiveHint, idempotentHint and openWorldHint, and upserts by unique field make creates safe to retry (17 of 20). One URL with OAuth or a token; no official SDK (5 of 15). 5 + 20 + 12 + 17 + 5 = 59.)
- Reliability, Microsoft Dynamics 365 Sales +25: Microsoft Dynamics 365 Sales 65 (Graded on the Dataverse Web API, with the Dataverse MCP server noted. Service health for a tenant is in the Power Platform and Microsoft 365 admin centres, behind an admin sign-in. The unauthenticated page at status.cloud.microsoft exists, and Microsoft's docs describe it as the place for updates when the admin portals are unavailable. It rendered no components for our reader on 8 October, and on 1 November its robots.txt answered an empty 401, so the host is treated as blocked and wasn't read (10 of 20, a departure from the full 20 because the page with history needs a login). No readable incident history. The Azure status history, which the Azure listings are read from, names no Dynamics 365, Dataverse or Power Platform incident in the 90 days to 1 November and doesn't cover these services (5). Service protection limits are published per user and web server at 6,000 requests and 20 minutes of execution time per five-minute window, and 52 concurrent requests, plus 40,000 requests per licensed user per 24 hours (15). 429 responses carry Retry-After with retry guidance, and upsert on alternate keys with If-Match gives safe retries for writes (15). The SLA for Microsoft Online Services dated 1 October 2026 pays a 25 per cent credit below 99.9 per cent uptime for Sales Enterprise and Professional, per the 8 October check (10). Web API v9.2 and the MCP endpoint /api/mcp are generally available (10).); Relaticle 40 (Graded with the hosted lines on Relaticle Cloud's REST API and MCP server, the surface an outside agent calls; the software also self-hosts. No status page is linked and status.relaticle.com did not connect (0). With no readable history the incident line scores 5. Limits have numbers: 600 a minute per workspace and 300 reads or 60 writes a minute per token in the source, and 120 MCP calls a minute per user in the docs (15). 429 is in the OpenAPI responses and upserts by unique field give a safe retry for creates, but the backoff guidance sits on a docs section we read only as a heading (10 of 15). No SLA (0). Version 3.8, not labelled beta (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.)
- Security & auth, Microsoft Dynamics 365 Sales +17: Microsoft Dynamics 365 Sales 74 (OAuth 2.0 through Microsoft Entra ID is the only route, with delegated sign-in or an application user holding a client secret or certificate. The OAuth scopes are coarse (`user_impersonation`, `.default`, `mcp.tools`) and the limits come from Dataverse security roles (26 of 30). Security roles set privileges per table and the MCP server follows them and row-level security. Each MCP client app must be allowed per environment by an administrator, and only Copilot Studio is on by default. The delete tools are described as needing explicit user approval, but Microsoft's sample agent instructions on the configuration page tell the agent not to ask before deleting (17 of 20). Lead, contact and email text written by outsiders reaches the model, and the MCP pages we read give no injection guidance (3 of 15). Dataverse auditing logs record changes and user access, readable through the Web API, once an administrator turns it on. It does not cover retrieve operations (13 of 15). SOC 2 Type 2 lists Dynamics 365, per the 8 October check, and security.txt points to MSRC and the bounty policy, but the file's Expires date of 23 September 2026 had still passed on 1 November. MSRC publishes CVEs for service-side flaws in Dynamics 365 and Dataverse. Three Critical ones in the last 12 months name Dynamics 365 (online) or Dataverse and are counted under negative events, and a fourth names only Dynamics 365 without the app (15 of 20).); Relaticle 57 (Personal access tokens are bound to one workspace, take an expiry and per-method permissions (read, create, update, delete, plus read, draft and send email), and travel in headers. OAuth 2.1 through Passport is also offered, but the source says its single `mcp:use` scope authorises the whole toolset (25 of 30). A read-only token is possible; the docs say MCP writes apply immediately and leave confirmation to the client (10 of 20). Synced email reaches the model through the email tools, and no prompt-injection guidance was found (0). Each record has an activity log of field changes and who made them, and admins see it across the workspace (12 of 15). security.txt valid to May 2027, a disclosure address with a 48-hour acknowledgement target and security-audit workflows in CI; the security page says there is no SOC 2 or ISO 27001 (10 of 20). 25 + 10 + 0 + 12 + 10 = 57.)
- Maintenance & community, Relaticle +11: Microsoft Dynamics 365 Sales 79 (Dataverse service update 9.2.26103 went to early release on 23 October 2026, with production rollout from 30 October (30). Service updates are weekly, with 9.2.26081 to 9.2.26103 listed from August to October 2026, each with release notes, and Python SDK 1.0.1 (8 September) and 1.1.0 (7 October) and .NET SDK 1.2.27 (4 September) in the window (20). Public release notes and community forums. We did not check how issues on the SDK repositories are answered (10 of 15). Current official SDKs for .NET and Python and the npm MCP proxy @microsoft/dataverse, whose 1.0.81 of 26 September 2026 rests on the 8 October check. The official MCP registry lists only third-party Dataverse and Dynamics servers, per the 8 October check (13 of 15). The Python SDK is marked Production/Stable for Python 3.10 and later and has a python-package workflow, but its runs weren't readable because github.com refused us (6 of 10).); Relaticle 90 (v3.8.2 tagged on 5 November 2026 and commits on 6 November (30). Thirteen tags between 9 October and 5 November alone (20). More than 2,500 commits since 1 August and merged pull requests numbered past 1,100; the GitHub API did not answer, so open issues and reply times were not counted (15 of 25). Verified com.relaticle/crm namespace in the official MCP registry with the hosted remote (15). CI, tests, security-audit and Dependabot workflows, PHP 8.5 and Laravel 13 (10). 30 + 20 + 15 + 15 + 10 = 90.)
- Schema & documentation, Relaticle +5: Microsoft Dynamics 365 Sales 81 (Each environment serves an OData v4 service document and a CSDL $metadata document at /api/data/v9.2/$metadata, and Learn publishes a table reference. No public OpenAPI document was found (18 of 25). learn.microsoft.com/llms.txt returns 404, but Learn returns Markdown for requests with `Accept: text/markdown`, which is how we read every page (10). The docs state purpose and limits, such as no `$skip` and a 5,000-row page ceiling. The published MCP tool descriptions are one line each (15 of 20). Entity types are typed in CSDL, but queries are OData strings and the MCP `read_query` tool takes a SQL SELECT string (12 of 15). Request and response examples on each page, a status code table with named errors, and a JSON error format with optional detail annotations (13 of 15). The version is in the URL (v9.2), with weekly Dataverse service update release notes. The MCP tool changes are noted without a date (13 of 15).); Relaticle 86 (OpenAPI 3.1 at /openapi.json and /openapi.yaml with 34 operations (25). llms.txt with a when-to-use and when-not section, and developer pages (10). The llms.txt and MCP docs say what the API is for and what it doesn't do (no email over REST, no meetings), while only 5 of 34 operations carry a description (14 of 20). 114 required lists and typed MCP inputs, but few enums (11 of 15). 661 examples and responses for 401, 402, 403, 404, 409, 422 and 429 (14 of 15). /v1 and frequent tagged releases, with no changelog page (relaticle.com/changelog is 404) (12 of 15). 25 + 10 + 14 + 11 + 14 + 12 = 86.)
- Payments & pricing, Relaticle +5: Microsoft Dynamics 365 Sales 25 (No x402, MPP or L402 (0). Seat prices are public at $65, $105 and $150 a user a month, paid yearly. MCP calls from agents built outside Copilot Studio are billed in Copilot Credits at published credit counts, and we did not read a dollar price per credit (10). The Dynamics 365 trial page states 30 days free and the Power Apps Developer Plan is a free Dataverse environment with Web API access. Neither page says whether a card is needed (15 of 20). A person registers an app in Entra ID and an administrator creates the application user or allows the MCP client (0).); Relaticle 30 (No x402, MPP or L402 (0). Cloud prices are public per workspace with nothing per call (10). A 14-day Cloud Pro trial with no card, and self-hosting is free (20). A person signs up in a browser behind a Cloudflare check, or deploys a server (0). 0 + 10 + 20 + 0 = 30.)