Azure Integration Services:
Other Azure Services:
Functions Running arbitrary code
Event Hubs Ingesting/streaming/replaying events
Service Bus
Robust async messaging with sessions,
transactions, de-duplication, etc.
API Management
Publishing, security, discovery,
monitoring & monetization of APIs
Event Grid
Intelligent routing for event-driven
reactive integration solutions
Logic Apps
Workflow/Orchestration, Azure & SaaS
connectivity, and hybrid connections
iPaaS Offerings
Azure Integration Services:
Other Azure Services:
Functions Running arbitrary code
Event Hubs Ingesting/streaming/replaying events
Service Bus
Robust async messaging with sessions,
transactions, de-duplication, etc
API Management
Publishing, security, discovery,
monitoring & monetization of APIs
Event Grid
Intelligent routing for event-driven
reactive integration solutions
Logic Apps
Workflow/Orchestration, Azure & SaaS
connectivity, and hybrid connections
iPaaS Offerings w/VNET Integration
Premium Tier
Premium Tier
via Storage Queues
Premium Plan
Standard/Dedicated Tiers
?
Azure Integration Services:
Other Azure Services:
Functions Run arbitrary code
Event Hubs Stream/replay events
Service Bus
Robust async messaging with sessions,
transactions, de-duplication, etc
API Management
Publishing, security, discovery,
monitoring & monetization of APIs
Event Grid
Intelligent routing for event-driven
reactive integration solutions
Logic Apps
Workflow/Orchestration, Azure & SaaS
connectivity, and hybrid connections
iPaaS Offerings w/VNET Integration
Premium Tier
Premium Tier
via Storage Queues
Premium Plan
Standard/Dedicated Tiers
ISE!!
Similar to App Service Environment…
On Prem
Azure
Virtual Network
App Service
Environment
Web Apps
API Apps
ILB
App GW
Internet
ExpressRoute (or Site 2 Site VPN)
SQL DB
Service Bus
Storage Queues
API
Management
…is an Integration Service Environment
Azure
Virtual Network
On Prem
Integration
Service
Environment
Logic Apps
Integration Account
API
Management
Internet
ExpressRoute (or Site 2 Site VPN)
SQL DB
Service Bus
Storage Queues
App GW
What’s so great about VNET integration?
Security / Isolation
Connectivity to resources within a VNET
Improved hybrid integration over OPDG:
https://www.serverless360.com/blog/consumption-vs-dedicated-billing-models
Scenario #1:
Private Static Outbound IP Addresses
You get your own private outbound IPs for ISE
connectors. With consumptionLogic Apps, you
also get a set of fixed outbound IPs … but they are
shared across that region.
Scenario #2:
Predictable Performance
ISE gives you the ability to explicitly control
scaling (as well as set auto-scaling). It also
provides predictable performance and eliminates
the “noisy neighbour” impact.
Scenario #3:
Support for Additional Hybrid Connections
Your application requires hybrid connectivity that is not
supported OOTB via the On-Prem Data Gateway.
Scenario #3:
Support for Additional Hybrid Connections
Your application requires hybrid connectivity that is not
supported OOTB via the On-Prem Data Gateway.
ISE includes on-prem connectors that don’t exist
with OPDG, such as:
SFTP / FTP
SMTP
IBM 3270
HTTP Action
Securing Logic App Endpoints and Run History
https://aka.ms/integration-service-environment
With ISE:
All of the above, plus:
Can use Network Security Groups (NSG)
… but need certain ports opened for ISE to function!
VNET Requirements
VNET must be in the same region & subscription
where you want your ISE
Requires four empty subnets with a minimum of 32
addresses
NOTE: If VNET does not appear in the ISE creation drop-down, shut down browser and re-open:
https://aka.ms/integration-service-environment
Pricing Considerations
Fixed cost vs. consumption-based cost
Volume of use (# actions per month)
Use of an integration account
Need for isolated environment
Use of Enterprise Connectors
https://www.serverless360.com/blog/consumption-vs-dedicated-billing-models
Key Takeaways
ISE provides VNET integration for Logic Apps
ISE allows your entire integration solution to be
contained and controlled within a private network
ISE enables predictable and consistent performance
References
Connect to Azure virtual networks from Azure Logic Apps by using an integration service environment (ISE)
https://aka.ms/integration-service-environment
Access to Azure Virtual Network resources from Azure Logic Apps by using integration service environments (ISEs)
https://docs.microsoft.com/en-us/azure/logic-apps/connect-virtual-network-vnet-isolated-environment-overview
ExpressRoute Overview
https://docs.microsoft.com/en-us/azure/expressroute/expressroute-introduction
Secure access in Azure Logic Apps
https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-securing-a-logic-app#restrict-incoming-ip-
addresses
Introducing Azure Logic Apps Integration Service Environment (ISE)
https://www.serverless360.com/blog/azure-logic-apps-integration-service-environment
Logic App Pricing
https://azure.microsoft.com/en-au/pricing/details/logic-apps/
App Service environments (ASEs) are appropriate for application workloads that require:
Very high scale.
Isolation and secure network access.
High memory utilization.
4x throughput improvement vs OPDG (on Jon’s machine)
From 2MB to 200MB!
Logic Apps RPReads the workflow definition and breaks down into a composition of tasks with dependencies
Logic Apps RuntimeDistributed compute/workers are coordinated to complete tasks on-demand
Connection ManagerManages connection configuration, credentials and token refreshment
Connector RuntimeAPI abstraction via Open API descriptions
ISE is injected into a VNET within the same region and subscription
Runtime components are provisioned – but not management components
Core connectors live in the runtime subnet, ISE connectors in the runtime connectors subnet
We can add connectivity to other resources in the same VNET or via VNET peering
We can reach on-prem resources connected via VPN / ExpressRoute
We can connect to other Azure services which expose service endpoints
DEMO:
Show where these IP addresses are specified.
Demonstrate sending FTP messages to self-hosted FTP server on an on-prem machine
Show the IP address used on the incoming messages
DEMO: Show how scaling is performed in ISE (but don’t actually execute the scaling!)