forked from joostdenijs/azure-content
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #28277 from Ja-Dunn/connectors-create-api-servicebus
edit pass: connectors-create-api-service-bus
- Loading branch information
Showing
4 changed files
with
100 additions
and
111 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,18 +1,16 @@ | ||
| Now that you have added a trigger, its time to do something interesting with the data that's generated by the trigger. Follow these steps to add a the **Service Bus - Send message** action. This action will send a message to Service Bus. | ||
| Now that you have added a trigger, it's time to do something interesting with the data that's generated by the trigger. Follow these steps to add the **Service Bus - Send message** action. This action sends a message to Service Bus. | ||
|
|
||
| Follow these steps to create the send message action: | ||
|
|
||
| 1. Select **+ New step** to add the action. | ||
| - Select **Add an action** link. This opens the search box where you can search for any action you would like to take. For this example, Service Bus actions are of interest. | ||
| - Select **Add an action**. This opens a search box, where you can search for any action you would like to take. For this example, Service Bus actions are of interest. | ||
|  | ||
| - Enter *service bus* to search for actions related to Service Bus. | ||
| - Enter *service bus*. | ||
| - Select **Service Bus - Send message** as the action to take. | ||
|  | ||
| - Enter the content for the message. This is required. | ||
| - Enter the queue or topic name to which the message will be sent. This is also required. | ||
| - Optionally, you can provide other details about the message. | ||
| - Provide other details about the message. This is optional. | ||
|  | ||
| - Save the changes to your workflow | ||
| - Save the changes to your workflow. | ||
|  | ||
|
|
||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,12 +1,12 @@ | ||
| In this example, I will show you how to use the **Service Bus - When a message is received in a queue** trigger to initiate a logic app workflow when a new item is to a Service Bus queue. | ||
| Here's how to use the **Service Bus - When a message is received in a queue** trigger to initiate a logic app workflow when a new item is sent to a Service Bus queue. | ||
|
|
||
| >[AZURE.NOTE]You will get prompted to sign with your Service Bus connection string if you have not already created a *connection* to Service Bus. | ||
| >[AZURE.NOTE]You will be prompted to sign in with your Service Bus connection string if you have not already created a connection to Service Bus. | ||
| 1. Enter *service bus* in the search box on the logic apps designer then select the **Service Bus - When a message is received in a queue** trigger. | ||
| 1. In the search box on the logic apps designer, enter **service bus**. Then select the **Service Bus - When a message is received in a queue** trigger. | ||
|  | ||
| - The **When a message is received in a queue** control is displayed. | ||
| - The **When a message is received in a queue** dialog box is displayed. | ||
|  | ||
| - Enter the name of the Service Bus queue you would like the trigger to monitor. | ||
|  | ||
|
|
||
| At this point, your logic app has been configured with a trigger that will begin a run of the other triggers and actions in the workflow when a new item is received in the queue you selected. | ||
| At this point, your logic app has been configured with a trigger. When a new item is received in the queue you selected, the trigger will begin a run of the other triggers and actions in the workflow. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,20 +1,19 @@ | ||
| ### Prerequisites | ||
|
|
||
| - A [ServiceBus](https://azure.microsoft.com/services/service-bus/) account | ||
| You must have a [Service Bus](https://azure.microsoft.com/services/service-bus/) account. | ||
|
|
||
| Before you can use your Azure Service Bus account in a logic app, you must authorize the logic app to connect to your service bus account. Fortunately, you can do this easily from within your logic app on the Azure portal. | ||
|
|
||
| Before you can use your Azure Service Bus account in a logic app, you must authorize the logic app to connect to your service bus account. Fortunately, you can do this easily from within your logic app on the Azure Portal. | ||
| Here are the steps to authorize your logic app to connect to your Service Bus account: | ||
|
|
||
| Here are the steps to authorize your logic app to connect to your service bus account: | ||
| 1. To create a connection to Service Bus, in the logic app designer, select **Show Microsoft managed APIs** in the drop-down list. Then enter **service bus** in the search box. Select the trigger or action you want to use. | ||
|  | ||
|
|
||
| 1. To create a connection to service bus, in the logic app designer, select **Show Microsoft managed APIs** in the drop down list then enter *service bus* in the search box.Select the trigger or action you'll like to use: | ||
|  | ||
|
|
||
| 2. If you haven't created any connections to service bus before, you'll get prompted to provide your service bus credentials. These credentials will be used to authorize your logic app to connect to, and access your service bus account's data. The service bus connector needs the connection string for the service bus namespace - and it also requires **Manage** permissions. A good way to know if your connection string is for the namespace or a specific entity is if it contains the `EntityPath` parameter, it is not the right connection string for a logic app. | ||
|  | ||
| 2. If you haven't created any connections to Service Bus before, you'll be prompted to provide your Service Bus credentials. These credentials are used to authorize your logic app to connect to and access your Service Bus account's data. The Service Bus connector needs the connection string for the Service Bus namespace. It also requires **Manage** permissions. A good way to know if your connection string is for the namespace or a specific entity is if it contains the `EntityPath` parameter. If it does, it is not the right connection string for a logic app. | ||
|  | ||
|
|
||
| 1. Once you have received the connection string for the namespace, you can use it for the API Connection in Logic Apps. | ||
|  | ||
| 1. After you have received the connection string for the namespace, you can use it for the API connection in Logic Apps. | ||
|  | ||
|
|
||
| 3. Notice the connection has been created and you are now free to proceed with the other steps in your logic app: | ||
|  | ||
| 3. Notice the connection has been created, and you are now free to proceed with the other steps in your logic app. | ||
|  |