Modify the system.webServer section in your web role’s Web.config file to add a list of IP addresses that are granted access, as shown in the following example:.Add the startup task to the ServiceDefinition.csdef file.
%windir%\system32\inetsrv\AppCmd.exe unlock config -section:system.webServer/security/ipSecurity Powershell -ExecutionPolicy Unrestricted -command "Install-WindowsFeature Unlocking configuration for "IPv4 Address and Domain Restrictions" feature Add following commands in your startup.cmd Installing "IPv4 Address and Domain Restrictions" feature.Add this file to your Visual Studio project and set the properties to Copy Always to ensure that it is included in your package. To do unlock the ipSecurity section of the nfig file, create a command file named startup.cmd that runs at role start.Using a command file which unlocks the ipSecurity section of the nfig file. You can restrict an Azure web role access to a set of specified IP addresses by modifying your IIS web.config file. Using the "IP and Domain Restrictions" feature on cloud services web role via a startup task: Implementing NSG rule by placing the cloud service in a VNET.Adding a firewall rule to block access to an IP address via the below command in the startup task.Using the "IP and Domain Restrictions" feature on cloud services web role via a startup task.For certain scenario, the application / website hosted in Azure Cloud Services needs more secure without anonymous access, this blog will introduce below four ways to specify IP address (or a range of IP addresses) could be blocked / allowed from accessing applications running on Azure Cloud Services:
0 kommentar(er)
