AI · 19 November 2026
Microsoft Adds Serverless HorizonDB to Fabric for Agent Apps
Microsoft has launched a serverless version of HorizonDB in public preview within Fabric, aimed at intermittent applications built by developers, business teams and AI agents. It was announced at the ongoing Ignite conference, according to InfoWorld.
What happened
Microsoft has added a serverless version of HorizonDB to Fabric, its data and analytics platform, aimed at applications that run only intermittently. The new Fabric HorizonDB entered public preview at the ongoing Ignite conference, according to InfoWorld.
The offering is designed for developers, business teams and AI agents that build applications to automate business workflows or support agent-driven tasks. Many of these applications do not need database infrastructure running continuously, and the serverless option is intended to remove that requirement.
The Fabric version builds on HorizonDB for Azure, which Microsoft first unveiled at Ignite in November 2025. That product is positioned as a PostgreSQL-compatible database for demanding enterprise workloads, including mission-critical applications that need high performance and scalability. Microsoft says its architecture combines shared storage with elastic, scale-out compute. The Fabric variant, by contrast, targets smaller workloads and provides a managed backend.
Why it matters
The significance lies in how the database layer is being reshaped around the way software is now built. Agents and workflow automations generate many small, sporadic data needs. Making a database available on demand, without keeping infrastructure running, lowers the cost and effort of experimenting with agent-driven applications. It also widens the group who can build, since business teams are named alongside developers as intended users.
For leaders in digital transformation, the practical shift is architectural. Offering one database mode for sustained enterprise load and another for intermittent work lets organisations match infrastructure to demand. The effect on customers and employees follows: internal tools and service automations can be stood up faster, provided governance and ownership keep pace with the speed of creation.
By the numbers
- November 2025 is when Microsoft first unveiled HorizonDB for Azure at its Ignite conference.
- Public preview is the stage at which Fabric HorizonDB was launched during the current Ignite conference.
The Renascence take
Most coverage will read this as a database feature. The more useful reading is about who can act on data, and how quickly. When building becomes cheap, the bottleneck shifts from engineering capacity to workflow ownership, review and accountability.
Easy provisioning will not improve customer experience on its own; it will multiply the number of small, automated workflows that touch customers without anyone clearly owning the outcome. The behavioural principle at work is that lower friction changes default behaviour, so teams will build more often than they govern. A customer-obsessed operator should treat agent-built applications as a service portfolio, with a named owner, a defined customer journey and experience measures for each one before it scales. The question to ask is not whether a database can spin up in seconds, but whether anyone is responsible for how the resulting workflow feels to the person on the other end.
Sources
This briefing was written by our Newsdesk, synthesising reporting from the outlets below. Follow the links for the original coverage.
FAQ
Questions we get on this topic
More in AI
Stay ahead of CX
Get the signal, not the noise.
The stories shaping customer experience — plus the Journal and Experience Loom — in your inbox.


