Dynamics 365 data to Fabric analytics: three ways in, one lakehouse

Flow

1Business Central → Extract function (API v2.0)
2Sales and Customer Service → Dataverse (tables)
3Finance and Operations → Dataverse tables (entities)
4Extract function → Open mirrored database (landing zone)
5Dataverse → Dataverse lakehouse (Link to Fabric)
5Dataverse tables → Dataverse lakehouse (Link to Fabric)
6Open mirrored database → Silver lakehouse (mirror)
6Dataverse lakehouse → Silver lakehouse (shortcut)
6Pipeline or copy job → Silver lakehouse (load)
7Silver lakehouse → Gold warehouse (model)
8Gold warehouse → Semantic model (Direct Lake)
9Semantic model → Power BI (report)
9Semantic model → Fabric data agent (ground)

Cost estimate eastus · price list as of 2026-10-02 · indicative — some usage is assumed

$0.00per month

$0.00per year

1/14components priced

13not priced (see below)

Public pay-as-you-go list prices from the Azure Retail Prices API (USD). Excludes taxes, support plans, Reservations, Savings Plans, Spot and enterprise or EA discounts, and data transfer unless a node sets egressGbPerMonth. Free grants are included where the meter has a free tier. Monthly = 730 hours. Not a quote: confirm with the Azure Pricing Calculator.

Show monthly cost on the diagram

By category

Compute$0.00 · NaN%

By component click a row to highlight it on the diagram

Component	Service	Status	$ / month	Line items

Not priced

Business Central — not-estimated: No cost model for Dynamics 365 Business Central yet. Supply `usage.monthlyUsd` on the node to include it.
Sales and Customer Service — not-estimated: No cost model for Dynamics 365 Sales yet. Supply `usage.monthlyUsd` on the node to include it.
Finance and Operations — not-estimated: No cost model for Dynamics 365 Finance and Operations yet. Supply `usage.monthlyUsd` on the node to include it.
Extract function — estimated: Consumption plan; the monthly free grant is included in the tiered meters.
Dataverse — not-estimated: No cost model for Dataverse yet. Supply `usage.monthlyUsd` on the node to include it.
Dataverse tables — not-estimated: No cost model for Dataverse yet. Supply `usage.monthlyUsd` on the node to include it.
Open mirrored database — not-estimated: No cost model for Fabric Mirrored Generic Database yet. Supply `usage.monthlyUsd` on the node to include it.
Dataverse lakehouse — not-estimated: No cost model for Fabric Lakehouse yet. Supply `usage.monthlyUsd` on the node to include it.
Pipeline or copy job — not-estimated: No cost model for Fabric Pipeline yet. Supply `usage.monthlyUsd` on the node to include it.
Silver lakehouse — not-estimated: No cost model for Fabric Lakehouse yet. Supply `usage.monthlyUsd` on the node to include it.
Gold warehouse — not-estimated: No cost model for Fabric Data Warehouse yet. Supply `usage.monthlyUsd` on the node to include it.
Semantic model — not-estimated: No cost model for Fabric Semantic Model yet. Supply `usage.monthlyUsd` on the node to include it.
Power BI — not-estimated: No cost model for Fabric Power BI yet. Supply `usage.monthlyUsd` on the node to include it.
Fabric data agent — not-estimated: No cost model for Fabric Data Agent yet. Supply `usage.monthlyUsd` on the node to include it.

Assumptions 4 defaulted — replace them with your own numbers in each node's `usage`

Component	Assumption	Value	Source
Extract function	plan	consumption	assumed
Extract function	requestsPerMonth	1000000	assumed
Extract function	avgDurationMs	200	assumed
Extract function	memoryMb	512	assumed

Sensitivity & what-if

$0.00at 1× traffic

$0.40at 3× traffic

$11.40at 10× traffic

No what-if options apply to these services.

Price list provenance

Retrieved 2026-10-02T10:01:47.868Z from the public Azure Retail Prices API. Latest price effective dates per service:

Functions 2024-12-01

Only public pay-as-you-go list prices are used. This is not a quote — confirm in the Azure Pricing Calculator.

Well-Architected review Dynamics 365 data to Fabric analytics: three ways in, one lakehouse · 2026-10-02 · mode full

Coverage audit

Azure Well-Architected Framework — 5 pillars, 59 recommendations, from the live documentation index, snapshot 2026-10-02 (0 days old).
Assessed 59 recommendations: 7 with diagram evidence, 51 cannot be determined.
Evidence sources: architecture diagram (services, boundaries, relationships); cost estimate from the Azure Retail Prices API.
Corpus read from a committed snapshot of the live documentation index (not re-fetched during this review). Re-read it with `archify-azure wa corpus --refresh`. Statuses reflect what the diagram and spec show. Process, configuration and runtime evidence are not observable here, so those recommendations are 'Cannot Determine' rather than guessed.

Executive summary

This Azure Well-Architected Framework review of Dynamics 365 data to Fabric analytics: three ways in, one lakehouse (standard criticality) assessed the architecture diagram only. 7 of 59 framework recommendations have diagram evidence; the rest are Cannot Determine because process, configuration and runtime evidence is not in the diagram. It found 0 critical, 0 high, 1 medium and 0 low risk. Estimated run cost is $0.00/month (indicative).

0Critical

0High

1Medium

0Low

3.7provisional maturity (1–5)

7 of 59 recommendations have diagram evidence (12%); among those, 2 implemented, 1 partial, 4 not implemented. Provisional: scores cover evidenced practices only.

Strengths. IaC / delivery pipeline shown.

Architecture overview

The reviewed architecture is the Diagram tab (14 components, dataflow diagram). Hover a finding to highlight the components involved.

Pillar scorecard

Pillar	Score (1–5)	Evidenced recommendations	I · P · N · NA · CD	Strongest area	Main gap
Reliability	—	1/10 (10%)	0 0 1 1 8	—	No gaps evidenced in the diagram
Security	—	1/12 (8.3%)	0 0 1 0 11	—	No gaps evidenced in the diagram
Cost Optimization	—	1/14 (7.1%)	0 1 0 0 13	—	No gaps evidenced in the diagram
Operational Excellence	3.7	3/11 (27.3%)	2 0 1 0 8	IaC / delivery pipeline shown	No monitoring / observability shown
Performance Efficiency	—	1/12 (8.3%)	0 0 1 0 11	—	No gaps evidenced in the diagram

Score = 1 + 4 × (implemented + ½ partial) ÷ evidenced recommendations; shown only when ≥ 3 recommendations are evidenced. It reflects evidenced practices, not the whole pillar.

Recommendation ledger 59 recommendations — nothing truncated

ID	Pillar	Best practice	Status	Evidence
RE:01	Reliability	Focus your workload design on simplicity and efficiency.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
RE:02	Reliability	Identify and rate user and system flows.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
RE:03	Reliability	Use failure mode analysis (FMA) to identify potential failures in your workload.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
RE:04	Reliability	Define reliability and recovery targets	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
RE:05	Reliability	Add redundancy at different levels, especially for critical flows	Not Applicable	No on-premises or private-link connectivity is drawn.
RE:06	Reliability	Implement a timely and reliable scaling strategy at the application, data, and infrastructure levels	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
RE:07	Reliability	Strengthen the resiliency of your workload by implementing self-preservation and self-healing measures	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
RE:08	Reliability	Test for resiliency and availability scenarios by applying the principles of chaos engineering.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
RE:09	Reliability	Implement structured, tested, and documented disaster recovery (DR) plans	Cannot Determine	Not observable from the architecture diagram; needs process or organizational evidence.
RE:10	Reliability	Continuously measure and track system health using uptime and reliability indicators	Not Implemented	Diagram: No monitoring / observability shown. Collect metrics, logs and traces with Azure Monitor, Application Insights and Log Analytics, and define alerts tied to business outcomes.
SE:01	Security	Establish a security baseline	Cannot Determine	Diagram: No threat detection or posture management shown. Enable Microsoft Defender for Cloud and Microsoft Sentinel (and Azure Policy) for posture management, threat detection and response; send activity logs to a central workspace.
SE:02	Security	Align secure development lifecycle (SDL) throughout the software development lifecycle	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
SE:03	Security	Classify and consistently apply sensitivity and information type labels	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
SE:04	Security	Create intentional segmentation and perimeters	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
SE:05	Security	Implement strict, conditional, and auditable identity and access management (IAM)	Cannot Determine	Not observable from the architecture diagram; needs IaC or configuration evidence.
SE:06	Security	Isolate, filter, and control network traffic	Cannot Determine	Not observable from the architecture diagram; needs IaC or configuration evidence.
SE:07	Security	Encrypt data by using modern, industry-standard methods	Cannot Determine	Not observable from the architecture diagram; needs IaC or configuration evidence.
SE:08	Security	Harden all workload components	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
SE:09	Security	Protect application secrets	Cannot Determine	Not observable from the architecture diagram; needs IaC or configuration evidence.
SE:10	Security	Implement a holistic monitoring strategy	Not Implemented	Diagram: No threat detection or posture management shown. Enable Microsoft Defender for Cloud and Microsoft Sentinel (and Azure Policy) for posture management, threat detection and response; send activity logs to a central workspace. Diagram: No monitoring / observability shown. Collect metrics, logs and traces with Azure Monitor, Application Insights and Log Analytics, and define alerts tied to business outcomes.
SE:11	Security	Establish a comprehensive testing regimen	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
SE:12	Security	Define and test effective incident response procedures	Cannot Determine	Not observable from the architecture diagram; needs process or organizational evidence.
CO:01	Cost Optimization	Create a culture of financial responsibility.	Cannot Determine	Diagram: No cost visibility shown. Tag resources, set Microsoft Cost Management budgets and alerts so spend maps to workloads and owners.
CO:02	Cost Optimization	Create and maintain a cost model.	Partially Implemented	A design-time cost model was generated from the Azure Retail Prices API: 1 of 14 billable components priced, $0.00/month pay-as-you-go (indicative; volumes partly assumed).
CO:03	Cost Optimization	Collect and review cost data.	Cannot Determine	Diagram: No cost visibility shown. Tag resources, set Microsoft Cost Management budgets and alerts so spend maps to workloads and owners.
CO:04	Cost Optimization	Set spending guardrails.	Cannot Determine	Diagram: No cost visibility shown. Tag resources, set Microsoft Cost Management budgets and alerts so spend maps to workloads and owners.
CO:05	Cost Optimization	Get the best rates from providers.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
CO:06	Cost Optimization	Align usage to billing increments.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
CO:07	Cost Optimization	Optimize component costs.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
CO:08	Cost Optimization	Optimize environment costs.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
CO:09	Cost Optimization	Optimize flow costs.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
CO:10	Cost Optimization	Optimize data costs.	Cannot Determine	Data transfer (bandwidth) is excluded from the estimate because no node sets egressGbPerMonth; model it before launch.
CO:11	Cost Optimization	Optimize code costs.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
CO:12	Cost Optimization	Optimize scaling costs.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
CO:13	Cost Optimization	Optimize personnel time.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
CO:14	Cost Optimization	Consolidate resources and responsibility.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
OE:01	Operational Excellence	Define your standard practices to develop and operate your workload.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
OE:02	Operational Excellence	Use standardization as a way to make routine, ad-hoc, and emergency operations consistent and predictable.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
OE:03	Operational Excellence	Formalize processes across the full software development lifecycle, from ideation to delivery, and make them transparent to the team and stakeholders.	Cannot Determine	Not observable from the architecture diagram; needs process or organizational evidence.
OE:04	Operational Excellence	Enhance software development and quality assurance	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
OE:05	Operational Excellence	Use a standardized infrastructure as code (IaC) approach to prepare resources and configurations.	Implemented	Diagram: IaC / delivery pipeline shown. Define infrastructure as code (Bicep or Terraform) and deploy through a pipeline (GitHub Actions or Azure Pipelines) with small, reversible changes and safe deployment practices.
OE:06	Operational Excellence	Build a workload supply chain that drives changes	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
OE:07	Operational Excellence	Design a monitoring stack	Not Implemented	Diagram: No monitoring / observability shown. Collect metrics, logs and traces with Azure Monitor, Application Insights and Log Analytics, and define alerts tied to business outcomes.
OE:08	Operational Excellence	Establish a clear, structured incident management process	Cannot Determine	Not observable from the architecture diagram; needs process or organizational evidence.
OE:09	Operational Excellence	Enhance the quality of your workload	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
OE:10	Operational Excellence	Design automation to be reliable, secure, and maintainable	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
OE:11	Operational Excellence	Clearly define your workload's safe deployment practices.	Implemented	Diagram: IaC / delivery pipeline shown. Define infrastructure as code (Bicep or Terraform) and deploy through a pipeline (GitHub Actions or Azure Pipelines) with small, reversible changes and safe deployment practices.
PE:01	Performance Efficiency	Define performance targets.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
PE:02	Performance Efficiency	Conduct capacity planning.	Cannot Determine	Not observable from the architecture diagram; needs process or organizational evidence.
PE:03	Performance Efficiency	Select the right services.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
PE:04	Performance Efficiency	Establish consistent performance measurement	Not Implemented	Diagram: No monitoring / observability shown. Collect metrics, logs and traces with Azure Monitor, Application Insights and Log Analytics, and define alerts tied to business outcomes.
PE:05	Performance Efficiency	Optimize scaling and partitioning.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
PE:06	Performance Efficiency	Optimize your workload's performance by regularly testing in a production-like environment	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
PE:07	Performance Efficiency	Optimize code and infrastructure.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
PE:08	Performance Efficiency	Optimize data usage.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
PE:09	Performance Efficiency	Prioritize the performance of critical flows.	Cannot Determine	Not observable from the architecture diagram; needs process or organizational evidence.
PE:10	Performance Efficiency	Optimize operational tasks.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
PE:11	Performance Efficiency	Respond to live performance issues.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.
PE:12	Performance Efficiency	Continuously optimize performance.	Cannot Determine	Not observable from the architecture diagram; needs runtime or operational evidence.

Findings

Medium risk (1)

F-001 Medium No monitoring / observability shown · Operational Excellence · OE:07, RE:10, PE:04, SE:10

Evidence. Diagram: No monitoring / observability shown. Collect metrics, logs and traces with Azure Monitor, Application Insights and Log Analytics, and define alerts tied to business outcomes.

Impact × likelihood. Moderate × Medium → Medium. Status: Not Implemented.

Recommendation. Collect metrics, logs and traces with Azure Monitor, Application Insights and Log Analytics, and define alerts tied to business outcomes.

Priority. Delegate · effort Low · owner DevOps / SRE

To confirm not drawn, so not counted as gaps

No threat detection or posture management shown SE:10, SE:01 — Enable Microsoft Defender for Cloud and Microsoft Sentinel, assign Azure Policy initiatives for the baseline, and send activity and diagnostic logs to a central, access-restricted Log Analytics workspace.
No cost visibility shown CO:03, CO:04, CO:01 — Set Microsoft Cost Management budgets with alert thresholds and enforce cost-allocation tags (Azure Policy) so spend maps to this workload.

Eisenhower prioritization

Do First

None

Plan

None

Delegate

F-001 No monitoring / observability shown

Defer

None

Prioritized remediation plan

ID	Risk	Quadrant	SMART goal	Owner
F-001	Medium	Delegate	By 2026-10-16 (2 weeks): Collect metrics, logs and traces with Azure Monitor, Application Insights and Log Analytics, and define alerts tied to business outcomes. Success measure: Dashboards and alerts for every tier; mean time to detect < 5 minutes	DevOps / SRE

Next steps

Add the missing process, configuration and runtime evidence to turn Cannot Determine practices into assessed ones.
Re-run the review after changes, and when the architecture or documentation changes.

Impact × Likelihood matrix from the AWS well-architected-review skill, applied to the Azure Well-Architected Framework (Severe+High = Critical; Severe+Medium/Low or Moderate+High = High; Moderate+Medium/Low or Minor+High = Medium; otherwise Low).

Flow

Cost estimate eastus · price list as of 2026-10-02 · indicative — some usage is assumed

By category

By component click a row to highlight it on the diagram

Not priced

Assumptions 4 defaulted — replace them with your own numbers in each node's usage

Sensitivity & what-if

Price list provenance

Well-Architected review Dynamics 365 data to Fabric analytics: three ways in, one lakehouse · 2026-10-02 · mode full

Coverage audit

Executive summary

Architecture overview

Pillar scorecard

Recommendation ledger 59 recommendations — nothing truncated

Findings

Medium risk (1)

To confirm not drawn, so not counted as gaps

Eisenhower prioritization

Do First

Plan

Delegate

Defer

Prioritized remediation plan

Next steps

Assumptions 4 defaulted — replace them with your own numbers in each node's `usage`