slug: microsoft-dynamics-365
provider: Microsoft Dynamics 365
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Banking & Capital Markets
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 3
edges:
- tag: Opportunities
  spec_file: microsoft-dynamics-365-opportunities-api-openapi.yml
  capability_id: BC-410.30
  capability_id_l1: BC-410
  capability_name: Opportunity & Pipeline Management
  confidence: 0.9
  evidence: POST /opportunities createOpportunity; GET /opportunities listOpportunities
  reason: CRM opportunity lifecycle CRUD is squarely opportunity & pipeline management in sales.
- tag: Contacts
  spec_file: microsoft-dynamics-365-contacts-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.8
  evidence: GET /contacts listContacts ... POST /contacts createContact; "core CRM entities including
    accounts, contacts, and opportunities"
  reason: CRUD over CRM contact records in Dataverse — maintenance of customer/contact master data, i.e.
    customer data management.
- tag: Accounts
  spec_file: microsoft-dynamics-365-accounts-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.78
  evidence: '"This specification covers core CRM entities including accounts, contacts, and opportunities";
    "createAccount  Create an account"'
  reason: CRUD over the Dataverse CRM account entity — the customer master record. 'Account' here is a
    customer organisation record, not a bank deposit account nor a login account; mapped to customer data
    management rather than sales account management as the surface is pure record maintenance.