During implementation of the concept in Part 1 I discovered that Traffic Manager probes were not accurately reporting outages of the web app’s and would still route traffic to improperly functioning web apps. This article corrects that oversight, and combined with Part 1 is a complete solution to enable the usage of Traffic Manager, Web Application Firewall, and Web App’s together.
Thank you to everyone that attended my talk yesterday at Global Azure Day Milwaukee. Let me know if any questions didn’t get answered. Attached are the slides and a link to the demo. Expect blog posts in the next couple weeks that cover some of the details that I glossed over to fit in my hour time slot:
What lead me down this path is my desire to use PAAS whenever possible and avoid IAAS unless its absolutely necessary. Often the number one security requirement for a deployment is to put your services behind a WAF (Web Application Firewall) to offer a first line of defense against many different types of attacks.
At work I’ve been doing some research into private cloud options. We hope to launch a private cloud (focused on development, not production) to host our build servers, test systems, tools like TFS and Git, and anything else we think of. Digging into Microsoft’s Private Cloud offering turned out to be challenging. There are many articles and videos explaining how to use it once it is up and running, but I could not find a single guide on how to create one from scratch, so I thought I would document what I have done to save someone else the trouble.