An Azure promotional graphic depicts migrating PostgreSQL to Azure HorizonDB via a testing and validation service.
Microsoft has put a new migration route to Azure HorizonDB into public preview. It runs through Azure Database Migration Service (DMS) and starts from Azure Database for PostgreSQL. The details Microsoft has published about it so far are thin, and the preview label matters a lot for anyone planning a move. This article covers what is confirmed, what isn't, and how to evaluate it.

An Azure promotional graphic depicts migrating PostgreSQL to Azure HorizonDB via a testing and validation service. What Microsoft announced​

The Azure Updates entry for this item is titled "Public Preview: Migrate Azure Database for PostgreSQL to Azure HorizonDB with Azure Database Migration Service (DMS)." It is labeled "In preview" and was published on November 17, 2026. The Azure Updates page defines that label as available to all Azure customers for non-production use and testing. In other words, this is not a production-ready path yet.

The update page I could retrieve contained only the title and the status legend. It had no steps, version matrix, or limits. So I'm treating the headline facts as confirmed and everything below that as context or open questions.

The destination and the migration path have different statuses​

The service and the route to it are at different maturity levels, and that is easy to miss.

  • HorizonDB itself: Microsoft's Ignite announcement says Azure HorizonDB is now generally available and Microsoft Fabric HorizonDB is in public preview. The Azure blog describes HorizonDB as a fully managed, PostgreSQL-compatible database with millisecond latency and built-in vector indexing. These are Microsoft's own claims, not independent benchmarks.
  • This DMS route: It is public preview, which means non-production use and testing.
  • Older documentation: Some Microsoft Learn pages still carry preview wording for HorizonDB. For a story dated November 17, the Ignite announcement is the better guide to the service's current status.

The practical conclusion is that you can run a production HorizonDB database. You shouldn't plan a production cutover with this specific DMS path until Microsoft says it has launched.

What the wider Ignite coverage adds​

Microsoft's Tech Community Ignite post describes a broader "new Azure Database Migration Service" for HorizonDB. It says the service moves PostgreSQL databases from AWS, Google Cloud, on-premises, and Azure virtual machines to HorizonDB, with online migration of schema and data plus built-in validation and monitoring. That is Microsoft's description of the wider service.

I could not confirm that the same capabilities apply to the Azure-to-HorizonDB preview in this update. In particular, I can't confirm online or low-downtime migration, supported PostgreSQL versions, or regional availability for this exact route.

A separate Microsoft post covers the Oracle route. It says the Oracle route in Azure DMS, now in Public Preview, supports offline migration from Oracle 19c and later to both Azure Database for PostgreSQL flexible server and Azure HorizonDB. A related Ignite post says that for Oracle data, offline migration is now in preview, and online migration is coming soon. This is a different source engine from the one in this update. It does show that Microsoft is rolling out HorizonDB migration in stages, and that preview routes can be offline-only at first.

How this compares with existing options​

Microsoft's current DMS documentation lists a Migration Service for Azure Database for PostgreSQL covering several PostgreSQL sources. These include on-premises PostgreSQL, Amazon RDS, Amazon Aurora and Google Cloud SQL. The destination shown in that tools matrix is Azure Database for PostgreSQL flexible server, not HorizonDB. Don't assume those existing source-to-Flexible-Server paths now work for HorizonDB.

There is also a documented manual option. Microsoft Learn describes a preview dump-and-restore method for HorizonDB using standard PostgreSQL tools. Two points from that guide matter for any plan:

  • Tooling: It uses pg_dump to export, then psql or pg_restore to load, depending on the dump format. The commands are written for bash terminals, including Windows Subsystem for Linux and Azure Cloud Shell. Windows admins can run them from WSL.
  • Version rule: The utilities should be the same major version as, or newer than, the database server involved. If the target has a higher major version, the utilities should match or exceed the target.
  • One database at a time: pg_dump exports a single database per run.
  • Roles: pg_dump skips roles and users. The guide says to use pg_dumpall -r. On HorizonDB you must add --no-role-passwords, because users can't read the pg_authid table. It also advises cleaning up the roles file before restoring it.

The guide also notes that the Azure portal Connect page for HorizonDB offers preconfigured dump and restore commands. Those are manual steps. Nothing confirms that DMS uses the same mechanism.

What to verify before you try it​

Because Microsoft hasn't published the preview's specifics in the material I could verify, treat these as questions to answer in a test environment:

  1. Which source Azure Database for PostgreSQL versions and tiers are supported?
  2. Is the migration offline, online, or both?
  3. What are the target requirements, such as HorizonDB region, network access and permissions?
  4. How are roles, extensions and large objects handled?
  5. What validation and monitoring does DMS provide, and how do you cut over safely?
  6. What limitations or known issues does the preview carry?

A sensible approach is to use a non-production copy, record timings and any errors, and keep the dump-and-restore route as a fallback. Compare the results against your application's downtime tolerance.

Why this matters​

Microsoft now describes PostgreSQL as having two homes: Azure HorizonDB for mission-critical scale and Fabric HorizonDB for analytics and AI integration. A managed route from Azure Database for PostgreSQL to HorizonDB would lower the barrier for existing Azure customers who outgrow their current tier. Earlier Microsoft material said that moving up to HorizonDB later would be quick and easy. This preview is the first step toward that, but it is not yet a finished, documented, production-grade path.

The takeaway is simple. HorizonDB is generally available, but this migration route is still in public preview. Test it now, and wait for the launched status before relying on it for production.

 

References

  1. (In preview) Public Preview: Migrate Azure Database for PostgreSQL to Azure HorizonDB with Azure Database Migration Service (DMS) Azure Updates 2026-11-17T20:00:32Z
  2. Your Privacy Choices Opt-Out Icon azure.microsoft.com
  3. HorizonDB: PostgreSQL for enterprises, developers, and agents on Azure and Fabric techcommunity.microsoft.com