Dynamics 365 Business Central and customer engagement apps: operational data to Microsoft Fabric analytics

Flow

1An extract function reads changed Business Central records through the API v2.0 (filtered by last modified time) using a service principal
2The function writes initial and incremental change files to the open mirroring landing zone; Fabric applies them to Delta tables
3Dynamics 365 Sales → Dataverse (tables)
4Link to Microsoft Fabric creates a lakehouse with read-only shortcuts to Dataverse tables; data stays in Dataverse and refreshes within about an hour
5Open mirrored database → Curated lakehouse (shortcut / SQL)
5Dataverse lakehouse → Curated lakehouse (shortcut)
6Curated lakehouse → Semantic model (Direct Lake)
7Semantic model → Power BI (report)
8Semantic model → Fabric data agent (ground)
9Sales and service teams → Dynamics 365 Sales (work)
9Finance and operations → Business Central (post)

Cost estimate eastus · price list as of 2026-10-02 · from stated usage

$8.80per month

$106per year

2/17components priced

12not 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.

Usage basis. Illustrative: 20 million Business Central API rows per month through one Functions consumption extractor. Dynamics 365 licences, Dataverse storage and Fabric capacity are not in the Azure Retail Prices API and are not priced.

Show monthly cost on the diagram

By category

Compute$8.20 · 93%

Security and operations$0.60 · 7%

By component click a row to highlight it on the diagram

Component	Service	Status	$ / month	Line items
Extract function	Function Apps	estimated	$8.20	2 lines Executions: 200,000 10 × $0.00 (tiered) = $0.20 Execution time (GB-seconds): 900,000 1 GB Second × $0.00 (tiered) = $8.00 Consumption plan; the monthly free grant is included in the tiered meters.
Key Vault	Key Vaults	estimated	$0.60	1 line Secret and key operations: 20 10K × $0.03 = $0.60 Standard tier software-protected keys; HSM keys and certificates are not modelled.

Not priced

Business Central — not-estimated: No cost model for Dynamics 365 Business Central yet. Supply `usage.monthlyUsd` on the node to include it.
Dynamics 365 Sales — not-estimated: No cost model for Dynamics 365 Sales yet. Supply `usage.monthlyUsd` on the node to include it.
Customer Service — not-estimated: No cost model for Dynamics 365 Customer Service yet. Supply `usage.monthlyUsd` on the node to include it.
Field Service — not-estimated: No cost model for Dynamics 365 Field Service yet. Supply `usage.monthlyUsd` on the node to include it.
Dataverse — not-estimated: No cost model for Dataverse yet. Supply `usage.monthlyUsd` on the node to include it.
Microsoft Entra ID — no-charge: Entra ID Protection has no direct charge.
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.
Curated lakehouse — not-estimated: No cost model for Fabric Lakehouse yet. Supply `usage.monthlyUsd` on the node to include it.
Notebooks — not-estimated: No cost model for Fabric Notebook 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 0 defaulted — replace them with your own numbers in each node's `usage`

Component	Assumption	Value	Source
Extract function	plan	consumption	from spec
Extract function	requestsPerMonth	2000000	from spec
Extract function	avgDurationMs	900	from spec
Extract function	memoryMb	512	from spec
Key Vault	operationsPerMonth	200000	from spec

Sensitivity & what-if

$8.80at 1× traffic

$39.60at 3× traffic

$147at 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 · Key Vault 2022-03-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 Business Central and customer engagement apps: operational data to Microsoft Fabric analytics · 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: 6 with diagram evidence, 52 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 Business Central and customer engagement apps: operational data to Microsoft Fabric analytics (standard criticality) assessed the architecture diagram only. 6 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 $8.80/month (usage-based).

0Critical

0High

1Medium

0Low

Strengths. Identity service shown.

Architecture overview

The reviewed architecture is the Diagram tab (17 components, architecture 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	—	2/12 (16.7%)	1 0 1 0 10	Identity service shown	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	—	1/11 (9.1%)	0 0 1 0 10	—	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	Diagram: No private endpoints shown for PaaS data services. Disable public network access on PaaS data services and reach them through Azure Private Link private endpoints inside your virtual network.
SE:05	Security	Implement strict, conditional, and auditable identity and access management (IAM)	Implemented	Diagram: Identity service shown. Nodes: idp. Authenticate and authorize every request with Microsoft Entra ID (conditional access, RBAC) and use managed identities instead of stored credentials.
SE:06	Security	Isolate, filter, and control network traffic	Cannot Determine	Diagram: No private endpoints shown for PaaS data services. Disable public network access on PaaS data services and reach them through Azure Private Link private endpoints inside your virtual network.
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: 2 of 14 billable components priced, $8.80/month pay-as-you-go (usage-based; volumes supplied).
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	Compute and database capacity is $8.20/month at pay-as-you-go rates (93% of the estimate); whether Reservations or Savings Plans apply is not shown. Evaluate with Azure Advisor recommendations after 30+ days of steady usage.
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.	Cannot Determine	Diagram: No infrastructure-as-code or CI/CD 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.	Cannot Determine	Diagram: No infrastructure-as-code or CI/CD 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 private endpoints shown for PaaS data services SE:06, SE:04 — Disable public network access on PaaS data services (Storage, SQL, Cosmos DB, Key Vault) and connect through Azure Private Link private endpoints with private DNS zones.
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 infrastructure-as-code or CI/CD shown OE:05, OE:11 — Define infrastructure as code (Bicep or Terraform) and deploy through a pipeline with small, reversible changes, environment promotion and automated rollback.
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 · from stated usage

By category

By component click a row to highlight it on the diagram

Not priced

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

Sensitivity & what-if

Price list provenance

Well-Architected review Dynamics 365 Business Central and customer engagement apps: operational data to Microsoft Fabric analytics · 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 0 defaulted — replace them with your own numbers in each node's `usage`