Azure Service Bus Account
In this article
Overview
You can use this account type to connect Azure Service Bus Snaps with data sources that use an Azure Service Bus account.
Prerequisites
None.
Limitations and Known Issues
None.
Account Settings
Asterisk ( * ): Indicates a mandatory field.
Suggestion icon (): Indicates a list that is dynamically populated based on the configuration.
Expression icon ( ): Indicates whether the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.
Add icon ( ): Indicates that you can add fields in the fieldset.
Remove icon ( ): Indicates that you can remove fields from the fieldset.
Field Name | Field Type | Field Dependency | Description |
---|---|---|---|
Label*
Default Value: None | String | N/A | Specify a unique label for the account.
|
Connection String Source
Default Value: User Provided | Dropdown list | Includes a dependent field for User Provided field. | Choose the source of the connection string. The available options are:
|
Connection String
Default Value: N/A | String/Expression | Enabled on selecting User Provided for Connection String Source. | Specify the connection string of the namespace generated in the Azure Service Bus portal.
|
Namespace*
Default Value: N/A | String/Expression | Enabled on selecting Snap Generated for Connection String Source. | Specify the name of the Namespace that you created on the Azure portal.
|
Shared Access Key Name
Default Value: RootSharedAccessKey | String/Expression | Enabled on selecting Snap Generated for Connection String Source. | Specify the shared access key name of the keys for Azure Service Bus in Azure portal. If the Connection String Source is Snap Generated, you must have a Shared Access Policy; you can provide a different name for your policy.
|
Shared Access Key*
Default Value: N/A | String/Expression | Enabled on selecting Snap Generated for Connection String Source. | Specify the primary key from the connection string for Azure Service Bus.
|
Snap Pack History
Related Links
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.