BizTalk Services tasks in Azure Classic Portal
Important
Microsoft Azure BizTalk Services (MABS) is being retired, and replaced with Azure Logic Apps. If you currently use MABS, then Move from BizTalk Services to Logic Appsprovides some guidance on moving your integration solutions to Logic Apps.
If you're brand new to Logic Apps, then we suggest getting started here:
-
Create your first logic app, or quickly get started using a pre-built template
-
View all the available connectors you can use in your logic apps
This topic explains the BizTalk Services tasks in the Azure classic portal.
There are two portals: Azure classic portal and the BizTalk Services portal. This topic focuses on the Azure classic portal tasks specific to BizTalk Services.
One of the first steps in using Microsoft Azure BizTalk Services is to determine your application needs. For example:
Will your business transactions grow over time?
Are there peak times when your business needs more processing resources? Are there times when your business needs less processing resources?
Do you have multiple EDI partners and require multiple agreements with these partners?
Does your application get or put data in an on-premises system, like SQL Server or Oracle?
The answers to these questions and more determine which BizTalk Services edition is right for you. Relevant link:
BizTalk Services: Editions Chart
After you determine your application needs, you create the BizTalk Service in the Azure classic portal. This BizTalk Service hosts and runs your deployed applications (created in Visual Studio). You can have one BizTalk Service or many BizTalk Services; the choice depends on your design needs and wants. Many users have multiple BizTalk Services. Relevant link:
Create a BizTalk Service using Azure classic portal
When the BizTalk Service is created, a deployment URL and security-related user/key pairs are created. This deployment URL is your online link to your BizTalk Service on Microsoft Azure. There are two sets of User/Key pairs:
Access Control issuer name and issuer key
Service Bus issuer name and issuer key
You share the deployment URL and these user/key pairs with your developer to deploy the BizTalk Services project. Relevant link:
BizTalk Services: Issuer Name and Issuer Key
After the project is deployed and running on Microsoft Azure, you can monitor the status and performance of the BizTalk Service. For example, you can:
Determine if the BizTalk Service is started or stopped.
See how many messages are sent or received.
Create a backup of the BizTalk Service.
View the properties of your BizTalk Service, including the deployment URL and the user/key pairs.
Relevant link:
BizTalk Services: Dashboard, Monitor, Scale, Configure, and Hybrid Connection tabs