The document discusses exposing BizTalk to the world, highlighting the importance of consuming on-premises resources through Azure services such as Azure Relay and Logic Apps. It outlines various methods for unlocking BizTalk endpoints, security considerations, and integration with API management. Additionally, it provides takeaways and references for implementing these solutions effectively.

1. Exposing BizTalk
to the World

2. About me • Principal Integration Architect
• Microsoft Azure MVP
• MCA Cloud Platform
• ACSUG co-organizer
wsilveiranz
wagner.silveira@theta.co.nz
https://notetoself.tech

3. Agenda
•Exposing BizTalk to the World
•Unlocking BizTalk Endpoints
•Demos
•Take aways

4. Exposing BizTalk
to the World

5. Why we want to do that?
• Consuming on-premises resources
• Single gateway
• Extend cloud workflows

6. How can we do this?
• Message Exchange
• Queues/Topics
• Files
• Email
• Expose HTTP Endpoints

7. Unlocking
BizTalk
Endpoints

8. There is an Azure Service
for that…

9. Azure Relay Services
• Securely expose on-premises services
• No infrastructure (firewall) changes
• Bi-directional socket channel
• Two features
• Hybrid Connections
• WCF Relays

10. BizTalk and Azure Relays
• WCF Relays (out of the box)
• WCF-HTTPBasicRelay binding
• XML format (WCF)
• Security
• Configuration time (SAS/ACS)
• Runtime (Anon/RelayAccessToken)
• Extend using pipeline components

11. Scenarios & Considerations
• Expose XML based endpoints
• Fast and reliable implementation
• Consider security implications
• Shared secret can be an option

12. Logic Apps
• Integration Platform as a Service (iPaaS)
• Extend workflows to on-premises
• HTTP trigger
• On-premises access with OPDG

13. BizTalk and Logic Apps
• Out of the box
• BizTalk Adapter for Logic Apps
• Logic Apps BizTalk Connectors
• Custom Connectors
• SOAP and REST
• Security
• Logic Apps to BizTalk  Windows or
Anonymous
• User to Logic Apps  SAS Keys

14. Scenarios & Considerations
• Extend cloud workflows
• Leverage on-premises connectors
• XML or JSON formats required
• Think about security implications
• Can leverage from OPDG

15. Azure Function Proxy
• API Composition tool
• Basic functionality
• SOAP and REST (pass through)
• On premises access with Hybrid
connections

16. BizTalk and Function
Proxies
• No out of the box configuration
• Requires an existing Receive Location
• Configuration via Function App UI
• Consumption Plan don’t support
Hybrid Connection

17. Scenarios & Considerations
• Expose endpoints as a single API
• Pass through is ok
• Not using consumption plan is ok
• Alternative is firewall changes
• Set of IPs to whitelist

18. API Management
• Turnkey solution
• API Composition, API Gateway, Developer
Portal
• Comprehensive functionality
• SOAP, REST, REST to SOAP
• VNET Integration

19. BizTalk and API
Management
• Wizard based config
• From API Management (FP 1)
• From BizTalk (FP 2)
• Publishes Basic HTTP Binding Receive
Locations
• SOAP and REST to SOAP
• Requires VNET integration or firewall
changes

20. Scenarios & Considerations
• Expose endpoints as a single API
• Modernize solution
• Caching and Throtling
• VNET integration requires premium
• Alternative is firewall changes
• Single IP to whitelist

21. Hands on Time?

22. Take aways

23. Choices, choices, choices

24. Identify
your needs

25. Find the balance

26. References
Implementing Azure Service Bus Relays in BizTalk Server
2013 and R2 (via Mark Brimble)
https://www.connected-pawns.com/2016/03/29/azure-
service-bus-relays-sas-tokens-and-biztalk-server/