
In Short: What Is Fabric HorizonDB?
Fabric HorizonDB is a serverless PostgreSQL database that runs inside Microsoft Fabric. Microsoft announced it in public preview at Microsoft Ignite 2026 on 17 November, alongside the general availability of Azure HorizonDB, a fully managed PostgreSQL-compatible service in Azure.
The point of putting PostgreSQL in Fabric is to keep operational data and analytical data together. HorizonDB tables are copied into OneLake as Delta tables by default, so an app can write records in PostgreSQL and a Power BI report can read the same data minutes later without a separate pipeline.
- Azure HorizonDB: generally available, in 13 Azure regions
- Fabric HorizonDB: public preview, across Fabric regions
- Mirroring Azure HorizonDB into Fabric: preview
- Pricing: not yet published for either
Two Products With One Name
Microsoft used the HorizonDB name for two related things, and it is worth keeping them apart.
Azure HorizonDB (generally available)
Azure HorizonDB is a fully managed, PostgreSQL-compatible database service for mission-critical and AI applications, with built-in vector search and AI capabilities. According to the HorizonDB announcement, it is generally available in 13 Azure regions across the Americas, Europe and Asia Pacific.
Several related features arrived in preview at the same time:
- Mirroring Azure HorizonDB into Microsoft Fabric, so operational data lands in OneLake for analytics
- Built-in AI model management
- Migration from Azure Database for PostgreSQL to HorizonDB with Azure Database Migration Service
- Offline Oracle-to-PostgreSQL migration, with online migration "coming soon"
Fabric HorizonDB (public preview)
Fabric HorizonDB is the Fabric-native version. You create it in a Fabric workspace like any other item. Microsoft describes it as provisioning in seconds, with compute that pauses after five minutes of inactivity and resumes on the next query. The Azure Ignite blog puts it "alongside SQL database in Fabric and Cosmos DB in Fabric", which makes it Fabric's third operational database.
What Makes It Different From a Normal PostgreSQL Server
Three features are specific to the Fabric version.
Tables are mirrored into OneLake by default. Microsoft's announcement says Fabric HorizonDB tables are "replicated into OneLake by default and are automatically converted to Delta format". That is the same pattern as mirroring, but switched on from the start, so there is no separate setup.
PostgreSQL queries can reach the warehouse. Queries can be pushed down to Fabric Data Warehouse to join live HorizonDB tables with data already in OneLake. An app can read a customer's open orders from PostgreSQL and their lifetime value from the warehouse in one query.
Synced Tables send data back. Microsoft calls this reverse ETL: tables from the warehouse are synced back into HorizonDB so an app can read curated analytical data at operational speed.
Together these make HorizonDB what Microsoft calls translytical: one database serving both the app and the analytics, with OneLake as the bridge.
HorizonDB and Fabric Apps
The biggest reason most Fabric customers will meet HorizonDB is Fabric apps, which also became generally available at Ignite. Microsoft says Fabric HorizonDB is the default database for Fabric apps, and the Rayfin SDK lets developers choose between Microsoft SQL database and HorizonDB as the app backend.
For Power BI Pro users who build apps on Microsoft-managed capacity, the app database is PostgreSQL with a maximum size of 1 GB. That suits planning inputs, approvals, trackers and small data-collection apps. It is not designed for large transactional systems.
HorizonDB vs SQL Database in Fabric
Both are operational databases inside Fabric, both feed OneLake, and both can back a Fabric app. The deciding factors are practical:
- Engine and skills. HorizonDB is PostgreSQL. SQL database in Fabric is SQL Server's engine with T-SQL. Pick the one your developers and existing code already use.
- Maturity. SQL database in Fabric is out of preview. Fabric HorizonDB is in public preview, so treat it as something to test, not to run payroll on.
- Idle cost behaviour. HorizonDB's compute pauses after five minutes without queries, which suits apps with bursty or office-hours usage.
- Ecosystem. PostgreSQL brings its extension ecosystem and open-source tooling. Microsoft also made its PostgreSQL extension for VS Code generally available at Ignite.
If you already run Azure Database for PostgreSQL, the more immediate question is whether to move to Azure HorizonDB, and whether to mirror it into Fabric once that feature leaves preview.
What It Costs
Microsoft has not published HorizonDB pricing in any of its Ignite announcements, for either the Azure or the Fabric version. Other Fabric workloads consume capacity units (CUs) from the workspace's capacity, and Fabric apps on F SKUs consume CUs for every database and API operation. Expect Fabric HorizonDB to follow the same model, but do not budget on it until Microsoft documents the meter. Our Fabric pricing guide will be updated when it does.
Should You Use It Now?
Try it now if:
- You are building Fabric apps and want to understand the default database before you commit
- Your developers are PostgreSQL people and have avoided Fabric because it felt T-SQL only
- You run a PostgreSQL app and want its data in Power BI without building and maintaining pipelines
Wait if:
- The workload is production-critical. Fabric HorizonDB is preview, with no published SLA or pricing
- Your team is happy with SQL database in Fabric. There is no reason to switch engines for its own sake
- You need cost certainty for a business case this quarter
The sensible first step is a small proof of concept: a single Fabric app or a copy of one existing PostgreSQL database, with a Power BI report reading the mirrored OneLake tables. That shows whether the translytical pattern actually removes a pipeline for you.
Sources and Further Reading
- Microsoft Ignite 2026 Book of News
- HorizonDB: PostgreSQL for enterprises, developers and agents on Azure and Fabric
- What's new in databases at Microsoft Ignite 2026
- Microsoft Ignite 2026: what's new in Azure
- Related: Database Hub in Microsoft Fabric, What is Rayfin?, Ignite 2026 announcements for Fabric
Frequently asked
Fabric HorizonDB is a serverless, PostgreSQL-compatible database that runs inside Microsoft Fabric. Its tables are replicated into OneLake as Delta tables by default, so the same data can be used by apps and by Power BI and other Fabric analytics. It was announced in public preview at Microsoft Ignite 2026.
Azure HorizonDB is a fully managed PostgreSQL-compatible service in Azure for mission-critical and AI applications, generally available in 13 Azure regions since Ignite 2026. Fabric HorizonDB is the Fabric-native, serverless version that lives in a Fabric workspace and is in public preview. Azure HorizonDB can also be mirrored into Fabric, which is in preview.
No. As of 18 November 2026 Fabric HorizonDB is in public preview across Fabric regions. Azure HorizonDB, the Azure service, is generally available. Preview features can change and are not recommended for production workloads.
Microsoft has not published pricing for Fabric HorizonDB or Azure HorizonDB in its Ignite 2026 announcements. Other Fabric databases consume capacity units from the workspace capacity, but Microsoft has not yet documented how HorizonDB is metered, so check the Fabric pricing pages before planning a budget.
Choose by engine and skills. If your team or application is built on PostgreSQL, or you are building Fabric apps where HorizonDB is the default database, HorizonDB fits. If your team works in T-SQL and SQL Server tooling, SQL database in Fabric is the more familiar choice and is not in preview.
Yes. Microsoft says Fabric HorizonDB is the default database for Fabric apps, and the Rayfin SDK lets developers choose between Microsoft SQL database and Fabric HorizonDB. Fabric apps created with a Power BI Pro licence use a PostgreSQL app database with a maximum size of 1 GB.


