After the previous How-to about receiving a message from an Azure Queue (Servicebus), I will now talk about sending a message to an Azure Queue.

We will work further with the Application from the other how-to. So we have a “full” flow. You only need the “Send Port” part for sending a message. ! :)

Create in the “Azure.Queue” application a new “One-way Send Port”

As Transport Type we choose for “SB-Messaging”

Click on the Configure button. So we can configure our “Send Port”.
On the general tab, we need to fill in our queue

Fill in your queue “sb://.servicebus.windows.net/
After that we go to the authentication tab.


Just choose the “Shared Access Signature” option. We only nee write permissions to write to this queue.
So i created a “Shared Policy Signature” on the queue in Azure with only write permissions. If you need the read permission.
Just create a new policy.

Now we will add a filter on this “Send Port” just to show if it works.
So we created in the previous blog post the Receive Port “ReceivePort_AzureQueue”.
Create the filter on our new “Send Port”

When we now receive a message. We will see it on our Send Port, and it will be written to our queue defined on the Send Port.
So we send a message to our First Queue with the tool like in my other BlogPost.
1 Remark on that, remove the CreateQueue part. Otherwise you need to change the policy key every time. (Just create your queue in the portal). Or you can use other tools like the “Azure Management Studio”
Then we receive it in BizTalk on our Receive Port (see BlogPost ), due to the Filter on the Send Port, we have the message available on that Port.
And then we see the message in our destination queue.

TIP: If you receive the following error in BizTalk
*System.InvalidOperationException: This client is not supported for a partitioned entity. The client version should be greater or equal than version ‘2013-10′. 1d2f9b96-6fab-4f89-9f4c-a29a087557f2G0 —> System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: This client is not supported for a partitioned entity. The client version should be greater or equal than version ‘2013-10′. 1d2f9b96-6fab-4f89-9f4c-a29a087557f2G0
*
Read this excellent post… Service Bus Queue/Topic Partitioning Not Supported in BizTalk Services

Any questions? Please comment on this post…