Azure Service Bus: Required Firewall Rules – ‘watchdog….’

So you’ve got an on-premise WCF Service and you’re going to expose the endpoint to the Cloud via ServiceBus.

I’m with a client excited about the prospect of Azure and using ServiceBus for connectivity
for our local WCF Services.

Remember ServiceBus is touted as the firewall friend communications mechanism.

Should be pretty easy right? – just follow an article like – http://msdn.microsoft.com/en-us/library/ee732535.aspx

If you are on a Secure Server – i.e. one that doesn’t have default open slather
access to the internet by default you will fall well short.
(nb: the Azure ServiceBus documentation is a little thin here also. ie no mention
whatsoever)

You will get ‘can’t contact watchdog.servicebus.windows.net’ and many others….So….

After much head banging Scotty sat down
one rainy day and looked at the full conversation to establish a connection to the
cloud via Service Bus

NB: XXXX is your ServiceBus endpoint name you configured in the Azure Management Portal
earlier. This endpoint lives in the Azure Singapore Data Center

Hopefully you won’t get caught out at a client site asking for firewall changes, one
at a time as you discover them.

Enjoy,

Mick + big thanks Scotty for the details.

Blog Post by: Mick Badran