Integration architecture design

Azure API Management
Azure Data Factory
Azure Event Grid
Azure Functions
Azure Logic Apps

The purpose of integration is to connect applications, data, services, and devices, often in complex ways. Through integration, organizations bring workflows together so they're consistent and scalable. Businesses connect applications, data, and processes in a fast, efficient, and automated manner.

Connections can run between on-premises, cloud, and edge systems. They can bring together enterprise, partner, third-party, and legacy technologies.

For data, integration provides solutions for gathering and processing information from multiple sources, in multiple formats.

To integrate applications, sometimes direct API calls are suitable. But sometimes technologies need to communicate asynchronously, through messaging or events. All integration processes need orchestration—a straightforward way to define and run the workflow's logic.

Diagram that shows four technologies that integration uses: orchestration, messaging, events, and A P Is.

Azure provides a wide range of integration tools and capabilities, including these services:

  • Azure API Management. Securely publish your APIs for internal and external developers to use when connecting to back-end systems.
  • Azure Logic Apps. Create workflows to connect hundreds of services in the cloud and on-premises.
  • Azure Service Bus. Connect on-premises and cloud-based applications and services to implement highly secure messaging workflows.
  • Azure Event Grid. Connect supported Azure and third-party services while simplifying event-based app development.
  • Azure Functions. Simplify complex orchestration problems with an event-driven serverless compute platform.
  • Azure Data Factory. Visually integrate data sources to accelerate data transformation and support enterprise workflows.

For information about more Azure integration services, see Integration Services.

Apache®, Apache NiFi®, and NiFi® are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries. No endorsement by The Apache Software Foundation is implied by the use of these marks.

Introduction to integration on Azure

If you're new to integration, the best place to start is Microsoft Learn. This free online platform offers videos, tutorials, and hands-on training for various products and services.

The following resources can help you learn the core concepts of integration:

Path to production

After you've covered the fundamentals of integration, the next step is to design your solution.

Design patterns

To explore patterns to incorporate into your design, consult resources in the following areas.

Hybrid systems

  • [Tiered data for analytics][Tiered data for analytics]: Use Azure Stack Hub to collect, process, store, and distribute local and remote data.
  • Cross-cloud scaling—on-premises data: See a hybrid app that spans Azure and Azure Stack Hub and uses a single on-premises data source, which is a compliance requirement for some organizations.
  • Cross-cloud scaling with Traffic Manager: Use Azure Traffic Manager to extend a local app by connecting it to public cloud resources.

Microservice architectures

Serverless solutions

Share location in real time using low-cost serverless Azure services: Set up a real-time messaging service to share live locations.

Mainframe migration

  • Integrate IBM mainframe and midrange message queues with Azure: Use a data-first technique that provides a way for IBM mainframe and midrange message queues to work with Azure services.
  • [Rehost mainframe applications to Azure with Raincode compilers][Refactor mainframe applications to Azure with Raincode compilers]: Use the Raincode COBOL compiler to modernize mainframe legacy applications without changing code.
  • Mainframe access to Azure databases: Give IBM mainframe and midrange applications access to remote Azure databases.

Service selectors

The following resources can also help you design your application. Besides providing general information about an integration mechanism or process, each article helps you select an Azure service that best meets your need for that area.

Specific implementations

To learn about scenario-specific architectures, see the solutions in the following areas.




Internal business solutions

Architecture, engineering, and construction (AEC)

Azure digital twins builder: Use building information modeling data from Autodesk Forge to automate the creation of an Azure Digital Twins foundational dataset.


Geospatial data processing and analytics: Make large volumes of geospatial data available for analytics.


Health data consortium: Share data among members of a healthcare consortium.

High-performance computing

HPC risk analysis template: Use Azure CycleCloud in a risk analysis application to expand on-premises TIBCO GridServer compute to Azure.

Best practices

These resources can help you spot-check your design against current recommended best practices:

Suite of baseline implementations

These reference architectures provide baseline implementations for various scenarios:

Operations guide

Deploying your workload is a significant milestone. After your integration processes are running, your focus can turn to operations. The following materials provide recommendations and reference information to help you continue to meet customer and regulatory demands:

Stay current with integration

Azure integration receives improvements on an ongoing basis. To stay on top of recent developments, see Azure updates.

Additional resources

The following resources provide practical recommendations and information for specific scenarios.

Information for Amazon Web Services (AWS)

Information for Google Cloud professionals