Include a Service Bus Topic Destination

 

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:

• What are logic apps

• 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

Add a Service Bus topic as a destination to a BizTalk Service project.

Important

In a BizTalk Service project, you can represent Service Bus topic destinations that have still not been created. However, representing a non-existent Service Bus topic on a BizTalk Service project designer surface does not create the topic.

To add a Service Bus topic to a BizTalk Service project

1. Create a BizTalk Service project, as described in Get started with a Visual Studio project.

2. Right-click anywhere on the BizTalk Service project design area, select Properties. For the BizTalk Service URL property, enter your BizTalk Services URL.

3. From the Toolbox, drag and drop the Service Bus Topic Destination component to the BizTalk Service project design area.

4. Right-click the Service Bus Topic component, and then select Properties. Enter the following properties:

   Property Name	Description
   Associated Project Item	This is a read-only field and provides the name of the associated .config file. If you change the name of the component on the BizTalk Service project design area by changing the Entity Name property, the name of the .config file also changes.
   Authentication	Specify how you want to authenticate with the Service Bus Topic. Select the ellipsis (…) against the Authentication property and the select a value from the Token Provider drop-down. Select Shared Secret, and then provide the issuer name and issuer key. Select Shared Access Signature (SAS), and then provide the key name and key value associated with the SAS.
   Endpoint Configuration Name	Name of the client endpoint configuration in the .config file that defines which encoding to use. The available options are TextEncodedMessageBody and BinaryEncodedSoapEnvelope. Use TextEncodedMessageBody when the receiver is a thick client or REST-based. Use BinaryEncodedSoapEnvelope if the receiver is a WCF service.
   Entity Name	The name of the Topic component on the BizTalk Service project design area. This name should be unique for a BizTalk Service project. Important The entity name for a Service Bus Topic must only contain alphanumeric characters.
   Runtime Address	The public runtime endpoint URL where the Service Bus Topic is deployed. Update this field to include your Service Bus namespace.

   5. Select Save.

   See Also

   Add a Message Destination to the bridge