Partilhar via

Registering and Updating a BizTalk Service Deployment on the BizTalk Services Portal

  • Artigo

 

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:

When you ‘register’ a BizTalk Service, you are associating your BizTalk Service (and its Issuer Name and Issuer Key) with your project deployments in the BizTalk Services portal.

This topic lists your registration options and the steps to register your BizTalk Service in the BizTalk Services.

Before you Begin

  • When registration occurs, the BizTalk Service deployment is automatically associated with the Organization account or Microsoft Account you are logged in as. When this association is done, only an organization account or Microsoft account has access to the BizTalk Services deployment. It cannot be changed.

    Example: You are logged in as user@contoso.com (an organizational account) when the BizTalk Services deployment is registered. If user@live.com logs in, this user cannot access the BizTalk Services deployment. Only users within the same organization (@contoso.com) can view and manage the BizTalk Services deployment.

    Example: The same for Microsoft accounts (@live.com, @hotmail.com, and @outlook.com). For example, you are logged in as user@live.com (a Microsoft account) when the BizTalk Services deployment is registered. If user@outlook.com (a Microsoft account) logs in, this user can access and manage the BizTalk Services deployment. If user@contoso.com (an organizational account) logs in, this user cannot access the BizTalk Services deployment. Only users with a Microsoft account can view and manage the BizTalk Services deployment.

    Important

    Users (user@live.com or user@contoso.com) can be added as guests in an Azure Active Directory (user@fabrikam.com). These Guests cannot access the BizTalk Services deployment.

  • The schemas that conform to the X12 4010 and 5010 standards are available at https://go.microsoft.com/fwlink/?LinkId=235057.

  • If messages will be signed and encrypted, a private certificate (.pfx) and a public certificate (.cer) are needed. For information on importing certificates, see APPENDIX: BizTalk Services Certificates Overview.

  • If you are using bridges and transforms as part of your solution, you must also install the BizTalk Services SDK. You can use the SDK to create these artifacts that might be required while configuring agreements. For more information, see Install Azure BizTalk Services SDK.

Register with the Portal

Important

If you registered a BizTalk Services subscription with the BizTalk Services Portal for the Preview release of BizTalk Services, you must re-register the subscription for the current release. Note that the artifacts, partners, agreements, etc. that you created or deployed in the Preview registration will be preserved in the new registration as well.

When the BizTalk Service is ‘registered’, you are proving ownership to the BizTalk Service by providing the Access Control Issuer Name and Issuer Key.

There are two options to register your BizTalk Service:

OPTION 1: Automatically register by clicking “Manage”

When you create a BizTalk Service in the Azure classic portal and you then select Manage for the first time, your BizTalk Service (and its Issuer Name and Issuer Key) is automatically registered in the BizTalk Services portal.

If access to your deployments uses Organizational accounts, then log into the Azure classic portal as your organizational account, create the BizTalk Service, and then click Manage to automatically register. If access to your deployments uses Microsoft accounts, then log into the Azure classic portal as your Microsoft account, create the BizTalk Service, and then click Manage to automatically register.

OPTION 2: Automatically register using the BizTalk Service portal

You create a BizTalk Service in the Azure classic portal and you do not select Manage. To automatically register the BizTalk Service, log in to the BizTalk Services portal ( HYPERLINK "https://YourBizTalkServiceName.portal.biztalk.windows.net/" https://YourBizTalkServiceName.portal.biztalk.windows.net/) using the same account (Microsoft or Organizational) that created the BizTalk Service. Logging in with this same account automatically registers the BizTalk Service.

If access to your deployments uses Organizational accounts, then log into the BizTalk Services portal as the organizational account to automatically register. If access to your deployments uses Microsoft accounts, then log into the BizTalk Services portal as the Microsoft account to automatically register.

Additional

When you log into the Azure classic portal to provision a BizTalk Services, you are logged in with a specific Microsoft or Organizational account. You can add additional accounts to manage the BizTalk Services subscription. You can also associate a single Microsoft or Organizational account with multiple BizTalk Services subscriptions. To achieve this many-to-many association, see Associating Multiple Login IDs with a BizTalk Services Deployment.

Create a BizTalk Service using Azure classic portal

Next

Associating Multiple Login IDs with a BizTalk Services Deployment

Manage Partners and Profiles in Azure BizTalk Services

Create Agreements in Azure BizTalk Services

See Also

Configuring EDI, AS2, and EDIFACT on BizTalk Services Portal