What Microsoft announced
Microsoft's Azure Updates feed posted an entry on November 17, 2026, titled "Generally Available: Azure Policy support for Azure HorizonDB." Its status label is "Launched." The feed defines that label as fully released, production-ready and available to all Azure customers.
The entry as retrieved did not list policy definitions, effects, parameters or regional caveats. This article therefore describes the governance significance and does not claim any particular control is new.
The same-day HorizonDB news
Microsoft's PostgreSQL team said at Ignite on November 17, 2026 that Azure HorizonDB is generally available, alongside a public preview of Microsoft Fabric HorizonDB. The service is generally available in 13 Azure regions across the Americas, Europe and Asia Pacific, with more coming. The same post says HorizonDB integrates with Azure security controls for identity, networking, and data protection.
HorizonDB's product page already pitched governance. It describes built-in governance controls: auditing, plus Azure Policy to help keep resources aligned with organizational requirements. The GA of policy support fits that pitch. Governance tooling that works with a database service is what lets a platform team approve it for production.
Documentation is out of step
Microsoft's documentation does not agree with itself yet. The HorizonDB overview page on Microsoft Learn, in the version retrieved, still says the service is in preview in its limitations section. It also lists several features as unavailable, including:
- Read pools
- Custom maintenance windows
- Long-term backup retention
- Virtual network injection (Private Link is supported)
The page was marked as updated on November 17, 2026, so it is likely mid-refresh. Third-party write-ups from earlier in 2026 also describe the service as preview. Treat the Ignite announcements as the current position and check the limitations list before committing a workload.
The one HorizonDB policy definition I could confirm
Microsoft's built-in Azure Policy catalog lists a HorizonDB-specific definition. It is titled "[Preview]: Deploy Diagnostic Settings for Azure HorizonDB clusters to Log Analytics workspace." It deploys diagnostic settings to a Log Analytics workspace when a cluster is created or updated without them. Its listed effects are DeployIfNotExists and Disabled, and its version is 1.0.0-preview.
That catalog entry still carries a preview label. The GA announcement does not name it, so I can't say whether the label has been or will be removed. Don't assume this definition is the thing that went GA.
What this means for administrators
Azure Policy works at management group, subscription and resource group scope. Supporting a resource type means HorizonDB clusters can be evaluated and governed like other Azure resources, and not left outside the policy estate. In general, Azure Policy supports Audit, Deny and DeployIfNotExists effects, but which of those apply to HorizonDB depends on the definitions Microsoft has published.
A cautious rollout looks like this:
- Open the built-in definitions in the Azure portal and search for HorizonDB. Note each definition's version and whether it is labelled preview.
- Read the effect options and parameters. DeployIfNotExists definitions need a managed identity and permissions to remediate.
- Assign at a narrow scope, such as a test resource group, with the effect set to audit or the assignment in non-enforcing mode.
- Review the compliance results, then widen the scope. Move to enforcement only once the results match what you expect.
- For custom needs, check whether the HorizonDB resource properties you care about can be used in a custom definition. I did not verify which properties are available.
These steps are standard Azure Policy practice and are not taken from the HorizonDB announcement.
Analysis
Policy support is rarely the headline, but it often decides whether a new database service gets approved in a regulated shop. Diagnostic logging, network exposure and tagging are the usual first requirements. HorizonDB's documentation shows public network access with firewall rules (none allowed by default) and Private Link, which are the kinds of settings governance teams usually want to audit.
Microsoft's feed entry is brief, so the breadth of coverage is the open question. A list of supported definitions and effects, and a preview-to-GA change on the diagnostic-settings policy, would answer it.
Bottom line
- Microsoft announced on November 17, 2026 that Azure Policy support for HorizonDB is generally available.
- HorizonDB itself was announced generally available the same day, though some Learn pages still say preview.
- The only HorizonDB-specific built-in policy I could confirm is a diagnostic-settings definition that the catalog still labels preview.
- Test any HorizonDB policy at a limited scope before enforcing it.
References
- (Launched) Generally Available: Azure Policy support for Azure HorizonDB Azure Updates · 2026-11-17T20:00:32Z
- Azure HorizonDB azure.microsoft.com
- List of built-in policy definitions - Azure Policy | Microsoft Learn learn.microsoft.com