Dataracity
Telecommunications · USA · Microsoft Fabric

Modernizing legacy reporting by moving on-prem SQL workloads into Microsoft Fabric

A reliable Fabric platform delivering real-time insight and client-facing analytics — built without adding load to the production systems it replaced.

IndustryTelecommunications
Company51–200 employees
CountryUnited States
FrameworkSTEAM
Results
Workloads off on-premReporting fully shifted into the cloud, strain removed from legacy systems
Billing and usage governedOne centralized model for accuracy and transparency
Manual extracts retiredAutomated pipelines and stable dashboards in their place
Client-facing analytics livePerformant, secure Power BI delivered to customers
Key technologies
Microsoft FabricAnalytics platformAzure Data LakeStoragePower BIReporting layerSQL Server (on-prem)Source systems
Related services
The migration, move by move

Off the on-prem estate, onto a platform that scales.

Seven moves took billing and usage reporting from a strained SQL environment to a governed Fabric platform — and out to the client's own customers. Follow the pipe.

Scroll to run the migration
Where it startedOn-prem SQL Server
01
01The challenge · Load on legacy systems

Heavy billing and usage reports were running on aging infrastructure.

The on-prem SQL environment carried heavy billing and usage reports for internal teams and external customers alike. Over time that workload placed significant strain on aging infrastructure, and reporting turned slow and unpredictable.

Large reporting workloads on aging on-prem systemsLong refresh times, inconsistent performanceReports served customers as well as internal teams
Before · load on on-prem SQLUnder strain
Billing reports
Usage reports
Customer-facing extracts
On-prem · agingSQL Server estate
Reporting loadHeavy

Billing and usage reports ran against the same estate as operations. Refresh times grew, performance drifted.

02
02The context · Manual and unscalable

Every report needed a developer, and nothing could grow.

Reporting required significant developer involvement every cycle, and there was no scalable foundation for customer-facing analytics — nor a clean way to prepare data for billing accuracy and usage-based insight.

Manual processes tied up developer timeNo scalable foundation for client-facing analyticsBilling and usage data hard to prepare reliably
Before · how reporting got madeManual
Developer involvement per refreshevery run
Refresh durationlong
Foundation for client-facing analyticsnone
Data prep for billing accuracydifficult

Every cycle drew on developer time, and none of it could scale to customers.

03
03The approach · Ingest and transform

On-prem SQL data ingested straight into Fabric.

Analytical workloads moved into Microsoft Fabric — on-prem SQL ingested and transformed in the cloud rather than against production, shifting reporting load fully off the legacy estate.

On-prem SQL ingested directly into FabricTransformation runs in the cloud, not on productionReporting load lifted off the legacy estate
Approach · ingestion into FabricCloud-side
01On-prem SQLBilling and usage source data
02IngestInto Fabric, scheduled
03TransformCloud compute, not production
04ServePower BI, client-facing
Legacy estate offloaded
Workloads run in the cloud

Transformation moved to Fabric, so production no longer pays for reporting.

04
04The approach · Scalable architecture

A medallion architecture sized for billing, usage, and operations.

The environment was re-architected around our STEAM framework: a scalable medallion architecture on Azure Data Lake, designed to carry billing, usage, and operational insight side by side — and to expand.

Bronze, Silver, Gold on Azure Data LakeDesigned for billing, usage, and operational insightBuilt to expand into advanced analytics and AI
Approach · medallion on Azure Data LakeSTEAM-aligned
Bronze
Raw landingSource-faithful billing and usage extracts
Silver
ConformedCleaned, joined, usage logic applied
Gold
ServingReporting-ready for Power BI
Headroom built in for advanced analytics and AI

Layered by design, so billing, usage, and operational insight scale together.

05
05The approach · Centralized logic

Business rules moved out of reports and into one model.

Joins, business rules, and usage calculations were consolidated into one centralized semantic model instead of living inside individual reports — so billing figures are defined once and every dashboard agrees.

Joins and business rules centralizedUsage calculations defined onceConsistent billing figures across reports
Approach · centralized semantic modelDefined once
Joins
CentralizedRelationships modelled once, not per report
Rules
SharedBusiness rules out of individual reports
Usage
ConsistentUsage and billing calculations agreed

Logic lives in the model, not in the reports. Every dashboard agrees by construction.

06
06The approach · Governance and monitoring

Logging, lineage, and run statistics on every pipeline.

Transparency was built in — pipeline logging, lineage, and run statistics, plus operational alerting on pipeline health, alongside best practices for governance, validation, and cost efficiency.

Logging, lineage, and run statisticsOperational alerting on pipeline healthValidation and cost-efficiency practices applied
Approach · transparency and controlMonitored
Pipeline logging and run statisticson
Data lineage across the platformtracked
Operational alerting on pipeline healthalerted
Governance, validation, cost efficiencyapplied

Pipeline health is visible, and the team is told before anyone else notices.

07
07The solution · Delivered to customers

Power BI dashboards the client could put in front of customers.

The reporting layer was rebuilt as client-facing Power BI dashboards — performant, reliable, and secure — replacing manual extracts and the developer workload behind them.

Performant, secure client-facing dashboardsManual extracts retiredSingle governed view of usage and billing
Solution · client-facing Power BIDelivered
Fast
PerformantBuilt on the Gold serving layer
Safe
SecureGoverned access for external users
Steady
ReliableAutomated refresh, no manual extracts
Improved customer visibility and satisfaction

Reporting became a product the client could put in front of its own customers.

Where it landedMicrosoft Fabric
We engaged Dataracity to lead the design and recommendation phase of one of our client's enterprise data architecture projects on the Microsoft platform. From the outset their expertise was evident — they introduced us to Microsoft Fabric and provided a robust framework rooted in industry best practices. Beyond high-level strategy, they delivered tangible assets including detailed system architecture diagrams, data flow charts, and comprehensive price modeling. Their technical execution is just as impressive as their strategic planning. I highly recommend Dataracity for any organisation looking to modernise their data stack with precision and clarity.
Shelly JantzenShelly JantzenFounder · E2 Consulting
The people who built it

Team responsible.

A small delivery team, named and accountable from kickoff to go-live.

  • Luke Matthews, Co-Founder, Head of Project Delivery & Data Architecture at Dataracity

    Luke Matthews

    Co-Founder, Head of Project Delivery & Data Architecture

  • Amanda Buthelezi, Co-Founder, Project Lead (BI & Data Strategy) at Dataracity

    Amanda Buthelezi

    Co-Founder, Project Lead (BI & Data Strategy)

How the STEAM framework shapes a buildOur delivery framework, end to end
Same strain, different estate?

Your reporting can come off the on-prem estate too.

Bring us your source systems and the reports that hurt. We'll map the Fabric architecture, the semantic model, and the path to client-facing analytics in one conversation.

30 minutes No obligation Microsoft Fabric partners