Business Central | Business Central Integration | Live Data Streaming | Azure Functions | Azure SignalR
Introduction
Microsoft Dynamics 365 Business Central has become the foundation of digital operations for thousands of businesses worldwide. As organisations continue extending Business Central beyond traditional ERP workflows, the demand for real-time integrations, live operational dashboards, AI assistants, customer portals, and connected business applications continues to grow. While Business Central provides robust APIs and integration capabilities, many organisations discover that streaming live business data to external applications requires a different architectural approach.
However, one question frequently comes up during digital transformation projects:
“Can Microsoft Dynamics 365 Business Central stream live data to my application?”
The answer is both yes and no.
Business Central provides powerful REST APIs, OData endpoints, API Pages, and Web Services that allow external systems to securely access business data. What it does not provide is native, persistent live data streaming where applications remain connected and instantly receive every business event as it happens.
For many businesses, this isn’t a problem.
A finance report that refreshes every hour or a Power BI dashboard updated every fifteen minutes is perfectly acceptable.
But today’s businesses are building far more than reports.
They are building warehouse applications, customer portals, AI assistants, mobile applications, executive dashboards, manufacturing systems, and operational monitoring platforms that rely on data changing in near real time.
Polling Business Central every few seconds quickly becomes inefficient, introduces unnecessary API traffic, and creates architectural challenges as more applications begin consuming the same business data.
Fortunately, there are proven architectural patterns that allow Business Central to communicate with external applications within seconds while keeping Business Central as the single source of truth.
In this article, we’ll explore where near real-time data streaming becomes valuable, why Business Central doesn’t provide it natively, and the architecture Smetric recommends for organizations looking to build scalable, maintainable, and enterprise-ready integrations.
Why Would You Need Live Data Streaming?
Not every Business Central implementation requires live data streaming.
In fact, most traditional ERP processes operate perfectly well using scheduled synchronization.
The requirement appears when Business Central becomes part of a larger digital ecosystem.
Let’s look at a few common examples.
Warehouse Operations
A warehouse operator scans the final pallet before shipment.
The warehouse supervisor’s dashboard should immediately reflect the reduced inventory.
At the same time, another application may begin preparing shipping labels while a transportation management system schedules the outbound shipment.
Waiting several minutes for synchronization can create duplicate work, inaccurate stock visibility, and delayed dispatch decisions.
Field Sales Teams
Imagine a sales representative standing in front of a customer.
Before confirming delivery, they need accurate inventory information directly from Business Central.
If inventory synchronization is delayed, the customer may be promised products that have already been allocated elsewhere.
Near real-time communication helps eliminate these situations.
Customer Self-Service Portals
Customers increasingly expect order status updates to happen automatically.
When an order moves from Released to Picked, Packed, or Shipped inside Business Central, they don’t expect to refresh their browser every few minutes.
They expect immediate visibility.
Executive Dashboards
Senior management often monitors operational KPIs throughout the day.
Sales orders.
Cash collections.
Inventory movements.
Warehouse performance.
Although these dashboards don’t require millisecond latency, receiving business events within a few seconds provides significantly better operational visibility than traditional scheduled synchronization.
AI Assistants
Artificial Intelligence has become another major consumer of Business Central data.
Whether an AI assistant is checking inventory, recommending substitute products, tracking purchase orders, or assisting customer support representatives, the quality of its responses depends entirely on the freshness of the information it receives.
An intelligent assistant using outdated ERP data quickly loses credibility.
Why Business Central Doesn’t Support Native Live Streaming
This is one of the most common misconceptions around Business Central integrations.
Many developers expect Business Central to behave like a messaging platform or a real-time event broker.
That was never its purpose.
Business Central is an enterprise ERP system.
Its responsibility is to process business transactions securely, enforce business rules, maintain data integrity, and expose supported interfaces for integration.
Maintaining thousands of persistent WebSocket connections falls outside that responsibility.
Instead, Microsoft provides APIs, Web Services, API Pages, and integration capabilities that allow other services to process and distribute business events.
This architectural separation is intentional.
Business Central remains responsible for business operations.
Specialized integration services become responsible for distributing business events to connected applications.
This design provides better scalability, improved security, and significantly more flexibility when multiple applications consume the same business data.
Why Polling Isn’t the Best Long-Term Strategy
At Smetric, we’ve found that many organisations initially attempt to solve this challenge with increasingly frequent API polling. While this approach works for smaller implementations, it often becomes difficult to maintain as more applications begin consuming Business Central data simultaneously.
Every application simply calls the Business Central API every few seconds looking for changes.
Initially, this works.
As the business grows, however, the architecture begins showing its limitations.
Every application repeatedly requests data even when nothing has changed.
API consumption increases.
Infrastructure costs increase.
Network traffic increases.
As more systems begin integrating with Business Central, organizations also need to consider service protection limits, retry mechanisms, API throttling, authentication overhead, and integration platform limitations such as Dataverse service protection limits.
Instead of applications reacting only when business events occur, they spend most of their time asking whether anything has changed.
That’s an inefficient use of resources.
When designing Business Central integrations, Smetric evaluates scalability, operational complexity, security, and long-term ownership costs not just the initial implementation effort.
A modern event-driven architecture reverses that model.
Instead of continuously asking Business Central for updates, applications simply wait until a business event occurs.
Only then is information distributed.
Traditional Polling vs Event-Driven Architecture
| Traditional Polling | Event-Driven Architecture |
|---|---|
| Continuous API requests | Events processed only when data changes |
| Higher API consumption | Lower API usage |
| Increased infrastructure load | More efficient resource utilization |
| Delayed synchronization | Near real-time updates |
| Difficult to scale across multiple applications | Easily scalable |
| Greater chance of API throttling | Reduced unnecessary API traffic |
| Multiple synchronization jobs | Centralized event processing |
For organizations planning long-term Business Central integrations, event-driven architectures typically provide better scalability, lower operational overhead, and a cleaner integration strategy.
Smetric’s Recommended Architecture
There are several technically valid ways to enable near real-time communication from Microsoft Dynamics 365 Business Central.
Some organizations choose self-hosted WebSocket servers.
Others implement custom event brokers or open-source messaging platforms.
These solutions can certainly work.
However, they also introduce responsibilities that are frequently underestimated during the planning phase.
Maintaining virtual machines.
Monitoring application health.
Managing security updates.
Configuring high availability.
Handling failover.
Planning scalability.
Monitoring message delivery.
Maintaining the middleware itself.
While these approaches may appear less expensive initially, the long-term operational costs often outweigh the initial savings.
For organizations already operating within the Microsoft ecosystem, Smetric generally recommends an architecture built around Azure Functions and Azure SignalR Service.
This recommendation isn’t based solely on the fact that they’re Microsoft services.
It’s based on operational simplicity.
Azure Functions provide a serverless event-processing layer capable of validating, transforming, enriching, and routing business events without requiring dedicated infrastructure.
Azure SignalR Service then securely distributes those events to every connected application.
Instead of managing WebSocket infrastructure, organizations can focus on building business applications while Azure manages scalability, availability, and connection management.
In our experience, this approach provides a better balance between scalability, security, operational simplicity, and long-term total cost of ownership for Business Central implementations.
Recommended Architecture
This is the reference architecture Smetric commonly recommends for organisations already operating within the Microsoft ecosystem.
Microsoft Dynamics 365
Business Central
│
Business Events / APIs
│
Azure Functions
(Validation • Business Logic • Routing)
│
Azure SignalR Service
│
┌─────────────┬──────────────┬──────────────┬──────────────┐
│ │ │ │ │
Web Portal Mobile App Power BI AI Assistant Dashboard
│ │ │ │ │
└─────────────┴──────────────┴──────────────┴──────────────┘
Near Real-Time Business Data DistributionBusiness Central continues to function as the authoritative system of record.
Azure Functions process business events while Azure SignalR securely distributes those events to connected applications in near real time.
The result is an architecture that remains scalable, maintainable, and capable of supporting multiple downstream systems without placing unnecessary load on Business Central.
Where This Architecture Delivers Business Value
Near real-time Business Central integrations are particularly valuable for:
- Warehouse Management Systems
- Customer Self-Service Portals
- Mobile Field Sales Applications
- AI Assistants
- Manufacturing Execution Systems
- Live Inventory Dashboards
- Executive KPI Dashboards
- Operational Monitoring Platforms
- Power BI Streaming Dashboards
- Third-Party Business Applications
- Custom Web and Mobile Applications
Rather than treating Business Central as an isolated ERP, organizations can transform it into the operational backbone of their entire digital ecosystem.
Final Thoughts
Microsoft Dynamics 365 Business Central was never intended to function as a real-time messaging platform.
Its purpose is far more important.
It provides a secure, reliable, and scalable foundation for business operations.
When organizations require near real-time communication with external applications, the objective shouldn’t be to force Business Central into becoming something it isn’t.
Instead, the right approach is to introduce an event-processing architecture that extends Business Central while preserving its role as the system of record.
There are multiple ways to accomplish this.
Every Business Central implementation is different, and so are its integration requirements. Some organisations need live warehouse visibility, others require AI-powered business applications, while many simply want operational dashboards that update the moment data changes.
At Smetric, we help organisations design Business Central integration architectures that remain scalable, secure, and maintainable long after deployment. Rather than forcing Business Central to become a real-time messaging platform, we build architectures that extend its capabilities while preserving its reliability as the system of record.
If your organisation is planning customer portals, warehouse applications, AI assistants, executive dashboards, or any solution that depends on near real-time Business Central data, we’d be happy to help you implement the right architecture.