Solutions · Azure · Integration Services

Connect the factory floor, the ERP, and the customer · Azure Integration.

Azure Integration Services is the Microsoft enterprise integration stack · Logic Apps for visual workflows, API Management for governed APIs, Service Bus for reliable messaging, Event Grid for real-time pub-sub eventing, Azure Functions for serverless integration logic, and the on-premises data gateway that bridges shop-floor PLC and SCADA into the cloud. Daxonet wires the stack across Malaysian and ASEAN plants · PLC and SCADA on the line, AutoCount and D365 in the back office, Power Pages and D365 Customer Service for the customer, AI Frontier on top. One stack, one partner, one accountable rollout.

Book a 90-min architecture review → WhatsApp the integration team

5 services in one stack LLogic Apps AAPI Management SService Bus EEvent Grid FFunctions

The 60-second answer

Azure Integration Services is Microsoft's umbrella for the Azure platform's enterprise integration stack · Azure Logic Apps for visual workflow automation across more than 1000 connectors, Azure API Management (APIM) to publish, secure, throttle and monetise REST APIs for internal and external consumers, Azure Service Bus as the enterprise message broker for reliable asynchronous messaging between systems, Azure Event Grid for real-time pub-sub eventing that fans out IIoT and business events in milliseconds, Azure Functions for serverless compute that hosts custom integration logic such as transformations and validations, and the on-premises data gateway that bridges cloud Logic Apps and APIs into shop-floor PLC, SCADA, ERP and file-share systems behind the firewall. The stack runs as a managed service on the Microsoft Cloud · consumption-based billing for Logic Apps, Functions and Service Bus, fixed plus consumption for APIM and Event Grid, all in the Singapore (Southeast Asia) region for Malaysian data residency or in the new Malaysia region as it lights up. Daxonet is a Microsoft Solutions Partner that wires the stack across the cross-stack Daxonet portfolio · PLC and SCADA and arc.ops MES on the shop floor connect through the on-premises data gateway, the back-office layer (Microsoft Dynamics 365 Finance and Supply Chain, AutoCount Accounting and AutoCount Cloud) connects through Logic Apps and Service Bus, the customer-facing layer (Power Pages portals, D365 Customer Service, Power Apps) consumes governed APIs through APIM, and AI services (AI Frontier, AI Machine Vision Inspection, AI Predictive Maintenance) subscribe to Event Grid topics for real-time enrichment. A typical first rollout lights up two integrations in 4 to 6 weeks, with Application Insights monitoring, RBAC, managed identities, private endpoints and PDPA-compliant consent built in from day one.

The integration tax

Why does the factory IT manager stay back on Saturday running FTP file transfers?

Three pains keep showing up in the customer-audit notes for Mr. Tan-style plants. Azure Integration Services is built to retire each one.

240 vs 218 Units · 22-unit gap

PLC says 240 units, ERP says 218 units, customer says where is my shipment.

Three systems, three numbers, three explanations. The shop-floor counter, the work-order receipt and the customer portal each tell a different story · the planner reconciles by hand at 18:30. Daxonet connects the three through Service Bus and Logic Apps so the same number lands everywhere.

12 hrs Saturday · per week

Saturday overtime running FTP file transfers between SAP and the new MES.

Twelve scheduled FTP jobs, three of which fail every weekend with a header mismatch. The IT lead opens the laptop after Subuh and rebuilds the file by hand. Azure Logic Apps replaces the FTP scripts with a managed connector that retries, alerts and logs · the engineer keeps her Saturday.

0 APIs Customer asked · 0 delivered

The customer wants a real-time stock API · we do not have one to give them.

The MNC customer scoping the new contract asked for a REST API to query stock and shipping status. The current answer is a daily Excel email. API Management on Azure publishes a governed stock API with OAuth, throttling and an SLA the procurement team will sign · the contract goes through.

5 services in one stack

What are the five Azure services Daxonet wires for the plant and the back office?

Pick the right tool for each integration. Daxonet maps the five services to your systems in the design phase · no over-engineering, no missed pattern.

L Logic Apps

Visual workflow automation across 1000+ connectors.

The integration engine 90% of business workflows live in. Drag-and-drop, declarative, readable by an operations engineer. Connectors for D365, AutoCount, SAP, Oracle, SharePoint, Teams, Salesforce, ServiceNow and most enterprise systems · plus custom connectors for anything else. Standard tier runs in your VNET, Consumption tier for elastic workloads.

1000+ connectorsvisual designerVNET-readyB2B + EDI

A API Management

Publish, secure and throttle APIs for every consumer.

The single front door to every internal and external API. OAuth, JWT, mutual TLS, rate-limiting, quotas, transformations, caching, WAF · before the request hits the backend.

OAuth 2.0throttlingdeveloper portal

S Service Bus

Reliable message broker for async system-to-system messaging.

Queues for command messages, topics for fan-out with subscription filters. Receiver offline, peak load, ordered delivery, dead-letter handling · Service Bus carries it.

queues + topicsFIFODLQ

E Event Grid

Real-time pub-sub eventing for IIoT and business events.

Fan out a single event to dozens of subscribers in milliseconds with at-least-once delivery. Machine downtime, AI prediction, order shipped · every interested system gets the notification at the same moment.

millisecond fan-outevent filteringCloudEvents

F Azure Functions

Serverless compute for custom integration logic.

Payload transformations, validations, custom routing, lightweight REST APIs · written in C#, Python, Node.js, Java. Consumption tier scales to zero · most integration workloads stay inside the free tier.

scale to zeroPython · C# · Nodedurable functions

Daxonet engineer reviewing the on-premises data gateway in a Selangor electronics factory bridging shop-floor SCADA into Azure Logic Apps

Gateway · 4 sites

TLS-encrypted · HA cluster

Capability 01 · Hybrid

Hybrid · cloud meets factory floor through the on-premises data gateway.

The on-premises data gateway bridges Logic Apps and APIs into shop-floor SCADA, ERP databases and file servers behind the firewall · outbound TLS only, no inbound port. Pair it with arc.ops MES as the line-side broker · the PLC speaks OPC-UA or Modbus to arc.ops, arc.ops publishes business events to Event Grid, downstream subscribers (D365, AutoCount, AI Frontier) consume those events. The pattern keeps PLC traffic off the cloud while making the data accessible. Daxonet runs the gateway in a 2 to 3 node high-availability cluster per plant for groups that cannot tolerate a Saturday outage.

✓Outbound TLS only · gateway opens TCP 443 to Service Bus relay · no inbound firewall rule, no public surface on the factory IT subnet.
✓SAP, Oracle, IBM i, file shares · the gateway carries the connector traffic for SAP ECC and S/4HANA, Oracle DB, IBM Db2 and iSeries, SharePoint on-prem and SMB shares.
✓Paired with arc.ops MES · PLC traffic stays line-side, arc.ops publishes business events to Event Grid for D365, AutoCount and AI subscribers · audit-clean separation.

Capability 02 · Event-driven

Event-driven architecture · IIoT events fan out in milliseconds.

Event Grid is the pub-sub backbone for real-time business events. A machine drops below 60 cycles per minute · an event fires on the topic. Subscribers (the SCM planner in D365, the OEE dashboard on Power BI, the AI Predictive Maintenance model, the WhatsApp on-call group) all receive the event in milliseconds with at-least-once delivery. No polling. No daily batch. The event schema is CloudEvents-compliant so customer systems and partner integrations can subscribe without a custom contract per consumer. Daxonet writes the event taxonomy (which events fire, which fields, which version, which retention) as part of the design phase.

✓Up to 12 thousand events per second per topic · enough headroom for IIoT sensor fan-out across 10+ lines and 50+ machines.
✓CloudEvents schema · standard event envelope so customer and partner systems can subscribe without a custom contract per consumer.
✓Subscription filters and dead-letter · downstream subscribers filter by event type, payload field or routing key · failed deliveries land in DLQ for replay.

Event Grid

12k events / sec · live

Common architecture patterns

Which integration patterns does Daxonet wire most often in Malaysian plants?

Four patterns cover roughly 80% of the integrations on a typical mid-market rollout. The right pattern keeps the bill low and the audit clean.

Pattern 01 · Pub-sub IIoT

Machine event fans out to many subscribers

Use case · machine downtime, predicted quality escape, order shipped. Many subscribers, sub-second fan-out, at-least-once delivery. Service · Event Grid plus Logic Apps subscribers.

Pattern 02 · Sync API

Customer calls a governed REST API in real time

Use case · partner queries stock, customer downloads invoice PDF, mobile app fetches order status. Service · API Management plus Functions or Logic Apps backend.

Pattern 03 · Async broker

Message survives if the receiver is offline

Use case · post invoices from D365 to AutoCount, send a work order to the floor when the planner is offline, handle 4x peak load on month-end close. Service · Service Bus queues plus Logic Apps consumer.

Pattern 04 · Hybrid VPN

Cloud reaches behind-the-firewall systems securely

Use case · cloud Logic App reads from SAP ECC behind the firewall, file drop into a SMB share, query a SCADA historian. Service · on-premises data gateway plus Logic Apps connector. No inbound port required.

What does Azure connect on Daxonet's stack?

One central integration backbone reaches every system Daxonet implements · MES, ERP, accounting, customer portal, BI and AI · under one Malaysian partner.

D365

Power Apps

Power Automate

Azure

SharePoint

Teams

SQL · arc.ops

The 4-phase rollout

How long does Daxonet take to light up the first 2 integrations?

Four phases, each one signed off as an architecture-spec deliverable. Most groups light up 6 to 10 integrations in the first 12 weeks.

Phase 01 · week 1

Discover · current-state map

DSC-01

An on-site current-state map of every system in scope · ERP, MES, SCADA, file shares, customer portals, partner APIs. Daxonet catalogues the existing integrations (FTP scripts, SQL jobs, manual exports, scheduled emails), measures throughput and latency, lists the regulatory triggers (MyInvois, customer audits, PDPA) and writes the integration-count baseline. The deliverable is the Discover Spec · a versioned document the customer IT team signs off before design.

Phase 02 · week 2 to 3

Design · target-state architecture

ARCH-02

The target-state architecture · which integrations move to Logic Apps, which APIs go through APIM, which messages run on Service Bus, which events fire on Event Grid, which custom logic lands in Functions. The Service Bus topic plan, the API catalogue, the event taxonomy, the security model (RBAC, managed identities, private endpoints, key rotation), the monitoring plan (Application Insights, Log Analytics) and the run-rate cost estimate are all signed off in the Design Spec.

Phase 03 · week 4 to 5

Pilot · first 2 integrations live

PLT-03

The on-premises data gateway is deployed on the factory IT subnet. The first 2 integrations are wired end-to-end · typically the highest-pain pair (D365 to AutoCount invoice posting and a customer-stock REST API). Application Insights is switched on, the alert routing is tested with a forced failure, the security review (RBAC, managed identities, private endpoints) is signed off and the customer IT team runs the smoke test. The Pilot Spec captures the actual run-rate, the actual latency P95 and the actual error rate against the design assumptions.

Phase 04 · week 6 onwards

Scale · fortnightly integration cadence

SCL-04

Additional integrations land on a fortnightly cadence · sequenced against the customer's release calendar so MyInvois deadlines, customer audits and product go-lives drive the schedule. Each integration follows the same flow · Design diff, build, smoke test, security review, go-live. Daxonet hands the customer a monthly health report covering throughput, error rate, latency P95, cost run-rate and capacity headroom. Most groups light up 6 to 10 integrations in the first 12 weeks.

Why Daxonet for Azure Integration

Why is Daxonet the only Malaysian partner with the full integration stack in-house?

Five connected expertise tiles around one Malaysian delivery hub · MES, ERP, AI and integration under one accountable team.

Daxonet integration team during a Malaysian customer architecture review

Cross-stack delivery

MES · ERP · AI · Integration · one Malaysian partner.

Most ASEAN integrators stop at one layer. Daxonet runs MES into the ERP, the ERP into the customer portal and the AI services on top · with Azure Integration as the spine.

Microsoft

Microsoft Solutions Partner

Azure, D365, Power Platform · the integration stack and the systems it connects, both in-house.

D365

10+ years D365 implementation

Finance, Supply Chain, Sales, Customer Service · we know the ERP side of the integration as well as the broker side.

AutoCount

Authorised AutoCount Dealer

SME-to-mid-market accounting integration through Service Bus and Logic Apps · MyInvois e-Invoice ready.

Arcstone

arc.ops MES Implementation Partner

PLC, SCADA and IIoT bridged through arc.ops to Event Grid · audit-clean separation of line-side and cloud traffic.

Daxonet AI Frontier methodology

AI services subscribe to Event Grid for real-time enrichment · Predictive Maintenance, Machine Vision, AI WMS.

FAQ

Questions Malaysian IT and ops leaders ask before signing on Azure Integration.

How is Azure Integration Services priced and what does a typical Malaysian SME or mid-market plant pay each month?

Pricing is scoped to your size, modules and integrations. Daxonet quotes fixed-price after a short scoping call so there are no surprises. Most clients reach payback within the same project window.

Where is the data hosted and is the deployment Malaysia-PDPA acceptable?

Daxonet defaults to the Singapore region (Southeast Asia) for Malaysian deployments because it is the lowest-latency Azure region with full Integration Services availability today. The new Malaysia Central region (announced) is on the roadmap and Daxonet migrates customer workloads as services light up there. Both regions are PDPA-acceptable when configured with the right consent flows. Personal data inside payloads is logged with redaction by default, RBAC restricts access to integration logs, managed identities replace stored credentials, and private endpoints keep traffic off the public internet. The data-flow diagram is signed off with the customer IT team before go-live and Daxonet writes the PDPA Article 7 consent matrix as part of the deliverable.

What hardware does the on-premises data gateway need and where is it installed in the factory?

The standard on-premises data gateway runs on Windows Server 2016, 2019 or 2022 and needs 8 GB RAM, 4 vCPU and 50 GB disk · a small VM on the existing factory IT cluster is enough. Daxonet installs the gateway on the factory IT subnet with read-only paths to the SCADA historian, the ERP database and shared file servers. Outbound TCP 443 to Azure Service Bus relay is the only firewall rule needed · no inbound port. For multi-site groups the gateway runs in a high-availability cluster of 2 to 3 nodes per plant. The gateway is monitored from Azure Monitor with on-call alerts to the Daxonet helpdesk.

Does Azure Integration Services connect to legacy SAP, Oracle, IBM iSeries (AS400) and serial PLC environments?

Yes. The stack ships native connectors for SAP ECC and S/4HANA (BAPI, IDOC, RFC), Oracle Database, IBM Db2 and IBM i (iSeries / AS400) via the on-premises data gateway, plus connectors for Salesforce, ServiceNow, SharePoint, Teams and 1000+ other systems. For serial PLC and OPC-UA traffic Daxonet pairs the gateway with arc.ops MES as the line-side broker · the PLC speaks OPC-UA or Modbus to arc.ops, arc.ops publishes business events to Event Grid, downstream subscribers (D365, AutoCount, AI Frontier) consume those events. The pattern keeps PLC traffic off the cloud while making the data accessible.

How is the integration stack monitored, alerted and audited in production?

Application Insights captures every Logic Apps run, every API call through APIM, every Service Bus message and every Function execution · with full payload tracing for failed runs (PDPA-redacted by default). Log Analytics correlates the events across services so a failure in a Service Bus message can be traced back to the originating Logic App, the customer API call and the PLC tag. Azure Monitor alerts route to email, SMS, Teams or PagerDuty · Daxonet's helpdesk receives the same alerts on Gold and Platinum SLA contracts. RBAC, managed identities, key rotation and audit logs (90-day retention by default, 1-year on Premium) cover the audit trail. Daxonet hands the customer a monthly health report covering throughput, error rate, latency P95, cost run-rate and capacity headroom.

What are the security controls for APIs published through API Management?

APIM enforces OAuth 2.0 (Azure AD, identity providers), JWT validation, mutual TLS, IP allow-listing, rate limiting per consumer, quota enforcement, request transformation and response caching at the gateway · before the request ever reaches the backend. Subscription keys per consumer (one per partner) make it easy to revoke a single integration without disrupting others. Backend services sit on private endpoints inside a VNET so APIM is the only public surface. WAF (Web Application Firewall) sits in front of APIM on the Premium tier for groups that need OWASP-rule protection. Daxonet writes the API governance policy (versioning, deprecation windows, partner onboarding flow) as part of the implementation.

How long does Daxonet take to deliver the first 2 integrations and what is the rollout sequence?

A typical Malaysian rollout runs Discover (week 1, current-state map of every system, integration count, data flow), Design (week 2 to 3, target-state architecture, connector list, Service Bus topic plan, APIM API catalogue, security model), Pilot (week 4 to 5, first 2 integrations live, on-premises data gateway deployed, monitoring switched on), and Scale (week 6 onwards, additional integrations on a fortnightly cadence). Most groups light up 6 to 10 integrations in the first 12 weeks. The cost moves through Daxonet's fixed-scope tiers · Starter for 2 integrations, Plant for 6 to 10, Multi-system for 15+ across plants and back-office. Daxonet sequences the integrations against the customer's release calendar so MyInvois deadlines, audits and customer go-lives drive the schedule.

When should we use Logic Apps vs Azure Functions vs Service Bus vs Event Grid?

Use Logic Apps for visual, declarative integration flows that an operations engineer can read · 90% of typical business integrations (post the invoice from D365 to AutoCount, sync the customer record between Salesforce and D365 Sales, drop a CSV into SharePoint when a SAP IDOC arrives). Use Azure Functions for custom code that does not fit a connector · payload transformation between proprietary XML and JSON, validation rules, custom routing logic, REST API backends. Use Service Bus when the receiver might be offline, the order matters, the message must not be lost, or the throughput is high (queues for command messages, topics for fan-out with subscription filters). Use Event Grid for real-time pub-sub of business events that many systems subscribe to (machine downtime fires, AI predicts a quality escape, an order is shipped) · subscribers process the event in milliseconds with at-least-once delivery. Most integrations use 2 or 3 of the four · Daxonet maps the right tool to each integration in the design phase.

Where ASEAN IT and ops leaders go next on daxonet.com.

D365 Finance D365 Supply Chain arc.ops MES Power Automate Microsoft Fabric Implementation Services

Ready for an Azure Integration architecture review for your Malaysian plant or back office?

Daxonet runs a 90-minute architecture review · current-state integration map, target-state Azure design, run-rate cost, security and PDPA review. Walk out with a fixed-price first-2-integrations proposal.

Book a 90-min architecture review → WhatsApp the integration team →

Build your own copilots — no code required.

From shop-floor to finance — one connected system.

From experiment to operations — in 90 days.