Skip to main content

Anonymized engagement summary: Azure Synapse and Data Factory to Microsoft Fabric for a multi-location specialty retailer (2026)

Anonymized engagement summaryMulti-location specialty retailer · 2026

Opening answer. In 2026 EPC Group retired a multi-location specialty retailer's Azure Synapse and Data Factory estate and rebuilt it in Microsoft Fabric, against live production. The estate was assessed, rebuilt in Fabric and tested in parallel against production before any switch; cutover was staged across three controlled events, and the legacy Synapse resources were paused after review.

This is an anonymized engagement summary published under EPC Group's anonymized-engagement rule: the client is not named, no commercial terms are published, and every statement is EPC-reported. Named, documented engagements are in the Evidence Center.

Problem and scope

ItemScope
OrganizationA multi-location specialty retailer
Starting estateAzure Synapse and Azure Data Factory, feeding a data warehouse from the retailer's point-of-sale platform and an integration with its HR and payroll platform
Target stateThe same workloads rebuilt in Microsoft Fabric, with the Synapse and Data Factory estate retired
ConstraintExecuted against live production; the business could not be interrupted
CutoverThree staged, controlled events: the HR/payroll integration, then the point-of-sale data pipelines, then the point-of-sale data warehouse
Legacy shutdownSynapse resources paused after review, ending the duplicated run-rate

Not reported: data volumes, the Fabric capacity SKU, query or refresh timings before and after, and the run-rate saving from pausing Synapse. None is claimed.

Approach and artifacts

Assess, rebuild, test in parallel, then cut over. The legacy estate was assessed, rebuilt in Fabric, and run in parallel against production before any switch. Cutover was split into three events by workload so that each could be checked before the next.

Platform constraints resolved in design. Three Fabric behaviours broke the legacy code, and each was resolved in design without regression to production:

  • Fabric's isolation model broke the metadata update procedure.
  • Fabric's case sensitivity broke the dimension and fact procedures.
  • The Synapse orchestration did not carry over unchanged, so the orchestration logic was reworked for Fabric pipelines, which run parallel stored-procedure calls through a ForEach activity with Sequential turned off (Microsoft Learn, ForEach Activity - Microsoft Fabric).

HR/payroll integration. Seven PySpark notebooks were migrated with Azure Key Vault configuration, and the Data Factory pipeline estate was replicated under a single controlling pipeline.

Point-of-sale warehouse and replication. Additional point-of-sale tables were brought into replication, with stored-procedure development and validation, and accepted by the client.

Production incidents resolved during the period (from EPC Group's incident log):

PhaseIncidentResolution
Before cutoverHR/payroll endpoint failure: a superseded endpoint still in useEndpoint updated, pipeline re-triggered
Before cutoverHR/payroll failure: duplicate departments on the vendor sideDuplicates cleared, integration restored
Before cutoverHR/payroll failure: duplicate employee property short nameRecord corrected, pipeline restarted
Before cutoverWarehouse replication fault reported by the clientDeadlock condition identified and cleared
After cutoverTwo-hour point-of-sale pipeline fault after cutoverMissing item identified and restored
After cutoverHR/payroll failure on Fabric: the vendor changed its API hostname without notice (confirmed by the client)Diagnosed and corrected
After cutoverHR/payroll daily full-fetch failureHost URL updated
After cutoverPipeline failures from an incorrect Key Vault credentialCredential corrected, pipelines restored

What EPC Group delivered and what is not claimed

ClaimBasisStatus
The Synapse and Data Factory estate was rebuilt in Fabric and cut over in three staged eventsEPC delivery recordDelivered (EPC-reported)
There was no interruption to the businessEPC delivery recordEPC-reported
Legacy Synapse resources were paused after reviewEPC delivery recordDelivered (EPC-reported)
The client accepted the replication additionsEPC delivery recordAccepted (EPC-reported)
Performance, cost or capacity outcomesNot reportedNot claimed

Related services

Microsoft Fabric consulting · All case studies · Talk to a senior architect

Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group

Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published October 25, 2026 · Project alias EPC-2026-ANON-RETAIL-FABRIC · Published under the anonymized-engagement rule.

AI assistant — not a human