Dynamics 365 for financial services
By Emil Björk · Microsoft business apps consultant, Gothenburg
How Dynamics 365 fits banking, insurance, and wealth management — Microsoft Cloud for Financial Services, regulatory and compliance considerations.
On this page (8)
Financial services — retail banking, commercial banking, insurance, wealth management, capital markets — is one of Microsoft's strategic industries with a dedicated Microsoft Cloud for Financial Services offering. Dynamics 365 plays specific roles in the architecture; specialist platforms cover others; understanding the boundary is essential.
Where Dynamics 365 fits in financial services.
- Customer engagement and onboarding — Sales for relationship management, Customer Service for service interactions, Customer Insights for unified customer view across products and channels.
- Advisor / banker productivity — Outlook + Teams integration with Copilot for Sales surfacing customer data inside the banker's daily workflow.
- Marketing — Customer Insights – Journeys for compliance-aware customer outreach.
- Operations — operational workflows, claims-handling for insurance, KYC / KYB onboarding orchestration.
- Compliance and audit — Microsoft Purview for governance, Dataverse audit trails.
Where Dynamics 365 doesn't fit
Core banking systems (FIS, Temenos, Finastra), core insurance policy administration (Guidewire, Duck Creek), trading systems, ledger-of-record financial systems are not replaced by Dynamics 365. These specialist platforms remain; Dynamics 365 integrates with them.
Microsoft Cloud for Financial Services
Provides:
- Data models aligned with banking and insurance data standards.
- Onboarding accelerators for KYC, KYB, anti-money-laundering workflow.
- Customer 360 — unified view across products, channels, interactions.
- Banker / advisor desktop — integrated workspace combining Outlook, Teams, and Dynamics 365.
- Customer-facing experiences — Power Pages portals for customer self-service.
- AI accelerators — Copilot agents for common financial-services tasks.
Regulatory considerations.
- GDPR — EU customer-data protection.
- PCI-DSS — for any service handling cardholder data.
- SOX — US public-company financial reporting.
- MiFID II — EU investment-services regulation requiring detailed interaction recording.
- Basel / Solvency II — capital regulations affecting reporting requirements.
- FCA / PRA / SEC — country-specific financial conduct regulators.
- HIPAA-equivalent for health-insurance lines.
Microsoft's compliance pages document certifications applicable to financial services. The customer's responsibility is configuring Dynamics 365 in line with regulatory requirements — audit trails, retention, encryption, access controls.
KYC and AML
Customer onboarding for financial products requires Know Your Customer (identity verification) and Anti-Money-Laundering (transaction screening) checks. Dynamics 365 + Power Automate orchestrates the workflow — capture documents, call screening services (LexisNexis, Refinitiv, Dow Jones), surface results to underwriters, audit-trail every decision. The screening calls go to specialist providers, not Microsoft.
Claims handling (insurance)
Dynamics 365 Customer Service customised for insurance claims:
- Claim intake from policyholders via portal, phone, mobile app.
- Triage and assignment to adjusters.
- Investigation, evidence gathering, photo upload, expert involvement.
- Approval workflow with payment processing.
- Fraud detection alerts integrated into the workflow.
- Customer-facing status updates.
Wealth management
For advisors managing client portfolios:
- Client relationship and household management in Dynamics 365 Sales.
- Portfolio data sourced from specialist platforms; aggregated views in Customer Insights.
- Compliance-recorded client communications (MiFID II requires interaction recording).
- Suitability assessments captured as structured forms.
Common architecture pattern
Most financial services customers run:
- Core banking / policy / trading platform — the system of record for financial transactions.
- Dynamics 365 for customer relationship and operations — overlays the core with engagement and workflow.
- Microsoft Fabric — for analytics combining customer and financial data.
- Microsoft Purview — for compliance governance.
- Azure for the broader integration tier.
Operational reality
Financial services implementations are heavy on compliance, integration, and validation. Budget realistically and engage Microsoft's industry-cloud accelerators rather than building from scratch — they exist for good reason.
Where to go next
Microsoft's packaging is Microsoft Cloud for Financial Services; the onboarding process is in KYC onboarding. Sub-sector guides: banking and insurance. The identity controls regulators ask about are in conditional access. Real estate financing and lease accounting is close enough in regulatory shape to be worth a look: Dynamics 365 for real estate.
Frequently asked questions
Does Dynamics 365 replace a bank's core banking system?
- No. Core banking (FIS, Temenos, Finastra), core insurance policy administration (Guidewire, Duck Creek), trading systems, and ledger-of-record financial systems remain in place as the system of record — Dynamics 365 overlays them with customer engagement and operational workflow, and integrates rather than replaces.
How does KYC and AML screening work with Dynamics 365?
- Dynamics 365 plus Power Automate orchestrates the workflow — capturing documents, calling screening services, surfacing results to underwriters, and audit-trailing every decision — but the screening itself is performed by specialist providers such as LexisNexis, Refinitiv, or Dow Jones, not by Microsoft.
What does Microsoft Cloud for Financial Services add on top of Dynamics 365?
- Data models aligned with banking and insurance standards, onboarding accelerators for KYC/KYB and AML workflow, a unified Customer 360 view, an integrated banker/advisor desktop combining Outlook, Teams, and Dynamics 365, Power Pages customer self-service portals, and Copilot AI accelerators for common financial-services tasks.
What regulations does a financial services Dynamics 365 deployment need to account for?
- GDPR, PCI-DSS for cardholder data, SOX for US public-company reporting, MiFID II's interaction-recording requirement, Basel/Solvency II capital-reporting effects, and country-specific conduct regulators such as the FCA, PRA, or SEC — configuring audit trails, retention, encryption, and access controls to match them is the customer's responsibility.
Related guides
- Dynamics 365 for professional servicesHow Dynamics 365 fits professional services — Project Operations, Sales, time/expense, billing, and the integration with Business Central or Finance.
- KYC and client onboarding workflows on Dynamics 365How banks, wealth managers, and fintechs run know-your-customer onboarding on Dynamics 365 — the onboarding case model, business process flow stages.
- Dynamics 365 for constructionHow Dynamics 365 fits construction — project accounting, job costing, equipment management, payroll integration.
- Dynamics 365 for educationHow Dynamics 365 fits higher education and K-12 — student lifecycle, alumni relations, fundraising, and Microsoft's Industry Cloud accelerators.
- Dynamics 365 for government contractingHow Dynamics 365 fits government contractors — DCAA / FAR compliance, project accounting, indirect rates, and the specifics of selling to government customers.
Browse every guide in Industries.
Was this helpful?
Signals which guides land and which need work. No account, no comment box — corrections go through the contact page.
Spot something wrong or want a topic covered? Send a correction or a topic request — both are welcome.