- Organisation
- Bajaj Finserv
- Predecessor
- dedicated SQL pools in Azure Synapse Analytics with existing Azure Data Lake Storage
- Destination
- Microsoft Fabric Data Warehouse and OneLake
- Workload
- enterprise analytics, governed batch and streaming data, audit and compliance analysis, and Power BI consumption
- Stage
- Migrated and operational
- Retirement status
- The dedicated SQL-pool workloads moved, but OneLake shortcuts mean some underlying ADLS data remains in place.
- Confidence
- High
- Next trigger
- A dated cutover, formal retirement statement or material later implementation milestone.
Programme context
Bajaj Finserv migrated enterprise analytics workloads from dedicated SQL pools in Azure Synapse Analytics to Fabric Data Warehouse, using OneLake shortcuts to govern existing Azure Data Lake Storage without claiming every asset was physically moved.
Why this matters: This record identifies a named organisation, a source and destination platform, an affected workload and an evidence-bounded operational stage.
Migration timeline
| Date or stage | Milestone | What changed | Evidence status |
|---|---|---|---|
| Migration programme | Migration stage | Enterprise analytics workloads moved from Synapse dedicated SQL pools. | Source-stated migration |
| Operational state | Current state | Fabric Data Warehouse and OneLake support governed analytics and Power BI. | Source-stated current state |
| 16 Mar 2026 | Dated source | Microsoft published the customer account. | Dated primary evidence |
Workload migration matrix
| Workload | Predecessor | Destination | Status by 24 Jul 2026 |
|---|---|---|---|
| enterprise analytics, governed batch and streaming data, audit and compliance analysis, and Power BI consumption | dedicated SQL pools in Azure Synapse Analytics with existing Azure Data Lake Storage | Microsoft Fabric Data Warehouse and OneLake | Migrated and operational |
Implementation and architecture
- Fabric Data Warehouse replaced the named dedicated SQL-pool workload.
- Most existing T-SQL stored procedures were reused during migration.
- OneLake shortcuts govern existing Azure Data Lake Storage without duplicating every asset.
Known unknowns and contradictions
- The exact production cutover date.
- The complete list of Synapse pools and workloads retired.
- Which data assets remain physically stored in Azure Data Lake Storage.
No missing fact is inferred to broaden the source-supported migration claim.
PlatformTrace analysis
The source supports migration of enterprise analytics workloads from Synapse dedicated SQL pools to Fabric Data Warehouse. It does not prove physical migration or retirement of every ADLS asset.
Performance, cost, uptime and operational outcomes remain attributed source claims unless independently stated otherwise.
Evidence ledger
- Bajaj Finserv first-party vendor customer story, 16 March 2026
Microsoft’s dated customer story explicitly states the source and destination analytics platforms and explains the OneLake-shortcut boundary.
Approval: Issue #47 standing-authority queue and Austin Lambe’s 24 July 2026 publication instruction.
Corrections and updates
24 July 2026 — Initial long-form Verified dossier published from the complete five-lane intake and reconciled central filter. Later milestones will be appended rather than silently replacing this state.