In my most recent blog post, Unified data platform and data virtualization through PolyBase: Part Two, I provided a demo of data virtualization through PolyBase.
As I mentioned in the introduction in Part one, the end goal is to demonstrate how to control inbound access based on IP address restrictions to one of my two websites running on the Windows® virtual machine (VM). Part two of the series laid the foundation with the the Application Gateway configuration. Now, in this final post of the series, I walk thorough the Web Application Firewall (WAF) policy creation and test the custom rule. I will restrict access to site2.hiteshvadgama.co.uk.
In Part one of this three-part series, I introduced the concept of the per-site web application firewall (WAF) Policy with IP address rule restrictions and set the stage for this demonstration. Part one also lays out the assumptions for the implementation walkthrough. In this post, I present the Application Gateway configuration.
I recently worked with a client who had multiple public-facing Internet Information Services (IIS) websites hosted on an Azure® virtual machine (VM). The client wanted to restrict inbound internet access to one specific website by specifying a set of allowed external IP addresses and leave the traffic flow for the other websites unaffected.
Hello, everyone. I am here with a very simple but great topic that helps improve our database (DB) in a few ways—Stretch Database!!
Microsoft® and Oracle® have worked together to enable customers to deploy Oracle applications such as Oracle E-Business Suite®, JD Edwards® EnterpriseOne, and PeopleSoft® in the cloud.
With the release of Sitecore® version 10, Kubernetes® is now a supported option. This opens up some great benefits, such as better resource utilization, version-controlled images, and overall operations ease. While building out an automated pipeline, I came across an error during the Kubernetes job step. Let’s dive in and see the fix I used to get successful deployments.