Azure Integration Services L1 Context Diagram Example
This Azure context diagram is the L1 view of the Azure Integration Services example set. It keeps the same Order-to-Cash business landscape as the BizTalk L1 Context example and replaces the integration hub with Azure Integration Services (Logic Apps, API Management, and Service Bus). Because the surrounding systems stay unchanged, the architectural comparison is effortless.
To try it in Nodinite, copy the C4Context markup below and follow Import Your First C4 Diagram to create a C4 Diagram Set, import the markup, and bind each node to a System in your Repository Model. See C4 Diagrams for the concepts.

The L1 Context diagram after importing the Mermaid markup on this page: Azure Integration Services sits between the business systems and the external parties.
Example Diagram
| Preview | Mermaid Code |
|---|---|
|
C4Context
title Azure Integration Services Order-to-Cash - Context
Person_Ext(customer_user, "Customer", "Places orders and tracks delivery")
Person_Ext(supplier_user, "Supplier", "Sends product and invoice events")
Person_Ext(logistics_user, "Logistics Partner", "Sends shipment milestones")
System(portal, "Portal", "Receives orders and returns confirmations")
System(erp, "ERP", "Order and inventory management")
System(erp_finance, "ERP-Finance", "Invoice generation and finance processing")
System(wms, "Warehouse Management System", "Fulfillment execution")
System_Ext(payment_gateway, "Payment Gateway", "External payment processor")
System_Ext(tax_authority, "Tax Authority Portal", "External e-invoice authority")
SystemDb_Ext(carrier_tracking, "Carrier Tracking DB", "External delivery confirmation store")
SystemQueue_Ext(edi_gateway, "EDI Gateway", "External B2B queue for partner exchange")
System(azure_integration_services, "Azure Integration Services", "Logic Apps, API Management, and Service Bus integration layer")
Rel(customer_user, portal, "Submit order and query status", "HTTPS / JSON")
Rel(portal, azure_integration_services, "Forward order and confirmation flow", "HTTPS / REST")
Rel(supplier_user, azure_integration_services, "Send invoice and product updates", "SFTP / REST")
Rel(logistics_user, azure_integration_services, "Send shipment updates", "REST / Event")
Rel(azure_integration_services, erp, "Create/update order", "REST / SOAP")
Rel(azure_integration_services, erp_finance, "Post invoice and settlement status", "REST / Event")
Rel(azure_integration_services, wms, "Create fulfillment request", "REST")
Rel(azure_integration_services, payment_gateway, "Authorize payment", "REST")
Rel(azure_integration_services, tax_authority, "Submit e-invoice", "REST")
Rel(azure_integration_services, carrier_tracking, "Read delivery status", "REST")
BiRel(azure_integration_services, edi_gateway, "Exchange order and invoice documents", "AS2")
|
|
Component Type Highlights
- Integration Service: Azure Integration Services
- Business Systems: Portal, ERP, ERP-Finance, Warehouse Management System
- External Parties: Customer, Supplier, Logistics Partner
Import-Friendly Notes
- Reuses the same system names as BizTalk and Migration sets for better cross-diagram matching.
- Uses explicit
Person_ExtandSystemmacros for cleaner actor/system differentiation.