VERIFYBASE PROTOCOL · CONTINUOUS AUDIT LEDGER
Grounded in VerifyBase Protocol · About this registry
Verified Entity Benchmark / VerifyBase

Microsoft Dynamics 365

Category: CRM  ·  Tier: Listed

Microsoft Dynamics 365

Data Status: SOURCE_LINKED Automated extraction only
Pipeline: Initial Scrape API Validation Conflict Resolution Final Review

Pricing data as of 2026-04-24 ·  Type: SoftwareApplication

Integrity: Hash 50b1f276…de12 source-verified

Core Metrics

Metric Value Source Captured
Pricing Tier $65/user/mo (Sales Professional) · $95/user/mo (Sales Enterprise) —
Market Presence Tier 1 — Microsoft Azure Ecosystem — Enterprise CRM Incumbent —
Core Methodology Unified Data Model (UDM) — Sales, Service, Finance, Operations on a single platform —
Data Architecture Single-Tenant Isolated or Shared SaaS (region-configurable, 50+ Azure regions) —
API Maturity Index 91.2/100 (Dataverse REST API + OData v4, OAuth 2.0 / Azure AD) —

About this data: Values come from the company's official pages or are supplied by the company, and each is checked against its official source (see the source links and dates on this page).

Pricing History — Change Log

Status: Daily Monitoring Active
1 snapshot captured · Tracking since 2026-04-24
◉ Baseline Captured 2026-04-24

Baseline pricing data captured. Monitoring for changes.

◌ No pricing changes detected yet. This section will update automatically when plan prices, additions, or removals are detected by the daily scraper.

Pricing telemetry · Microsoft Dynamics 365 · 1 snapshot

Data Integrity Fingerprint

Cryptographic proof chain for this entity's data. The canonical hash is computed from a deterministic RFC 8785 (JCS) representation of the snapshot payload, signed with Ed25519, and submitted to the Sigstore Rekor public transparency log. Anyone can independently verify this data without trusting the frontend.

Canonical Hash SHA-256 · RFC 8785 JCS · canon_version: jcs-1
50b1f2766cb5025c1136c6bb0ddee70e4a63fc0c3aa2eb8e2c94194aaacade12

Captured:

Signature pending — will be applied on next deploy
Transparency log pending — will be submitted on next deploy

How to verify independently:

  1. 1. Fetch canonical JSON: curl https://verifybase.org/api/v1/snapshots/50b1f2766cb5025c1136c6bb0ddee70e4a63fc0c3aa2eb8e2c94194aaacade12
  2. 2. Run the verify endpoint: curl https://verifybase.org/api/v1/snapshots/50b1f2766cb5025c1136c6bb0ddee70e4a63fc0c3aa2eb8e2c94194aaacade12/verify
  3. 3. Fetch public key: curl https://verifybase.org/api/v1/trust/keys
  4. 4. Verify Ed25519 sig with openssl: echo -n "<hash>" | openssl pkeyutl -verify -pubin -inkey pubkey.pem

Data Conflict Resolution Log

No entity-specific conflict events recorded

This entity's data passed all verification checks without requiring manual intervention. System-wide resolution history is maintained in the Conflict Resolution Ledger.

Related Entities

Related entities in the VerifyBase registry, ranked by category proximity.

Same Category Copper CRM CRM View Report
Same Category Freshsales CRM View Report
Same Category HubSpot CRM View Report

This record is checked against primary vendor documentation and cross-referenced with the VerifyBase open data protocol. All data points link to their primary source URL for independent verification.