WAF-as-a-Service sits between your application’s users and your application servers, blocking out attacks and malicious traffic. The closer WAF-as-a-Service is deployed to your application servers, the faster it will be able to pass requests to your application servers; meaning better performance for your application’s users.

To that end, today we announced that WAF-as-a-Service can now be deployed in any Microsoft Azure region. This means there are now over 50 locations where you can deploy your WAF-as-a-Service protection, meaning increased performance.

On the Endpoints page, you will see a new “Deployment Location” pane that allows you to edit each application’s deployment location. The closest location will automatically be chosen for you during application setup, based on the location of your application servers; however, if your servers have moved, or you have other requirements, you may edit this manually.

Another change you will note is that instead of changing your DNS A records during application setup, you will now be required to create CNAME records. This allows Barracuda to intelligently load balance your traffic between primary and backup regions, and optimize performance, without requiring changes from you.

These changes will be reflected in accounts created starting today. Existing accounts will not be affected for now. If you’d like your account to be migrated to Azure, contact support and we’ll be happy to move it for you.

For more information, read our press release.