Cross-cloud scaling with Azure Functions

Azure Functions
Azure Stack
Azure Traffic Manager

Solution ideas

This article is a solution idea. If you'd like us to expand the content with more information, such as potential use cases, alternative services, implementation considerations, or pricing guidance, let us know by providing GitHub feedback.

This solution idea helps you understand how to improve cross-cloud scalability with solution architecture that includes Azure Stack.


Architecture diagram that shows how to improve cross-cloud scalability with solution architecture that includes Azure Stack.

Download a Visio file of this architecture.


  1. A large number of users attempt to access a web app.
  2. Traffic manager returns the Azure Stack DNS name.
  3. Users access the Azure Stack web app.
  4. Once a threshold is reached, a function starts the Azure Web App and enables the Azure Traffic Manager route.
  5. Traffic is routed to Azure, which can automatically scale App Service.


  • Traffic Manager: Route incoming traffic for high performance and availability
  • Azure Functions: Process events with serverless code
  • Azure Stack: Build and run innovative hybrid applications across cloud boundaries

Scenario details

Modern software is increasingly connected and distributed. The consistency of Azure Stack with Azure infrastructure and platform services enable you to scale resources cross cloud to meet increased load as needed, and decrease resources as demand drops. Optimize cost and maximize resource efficiency while remaining compliant with cross cloud architecture.

Potential use cases

This solution applies to the following scenarios:

  • Implement continuous integration and continuous delivery (CI/CD) practices across an Azure Stack Hub implementation and the public cloud.
  • Consolidate the CI/CD pipeline across cloud and on-premises environments.
  • Develop apps by using both cloud and on-premises services.

Next steps