<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ip-whitelisting on bramstoop.com</title>
    <link>https://www.bramstoop.com/tags/ip-whitelisting/</link>
    <description>Recent content in ip-whitelisting on bramstoop.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 16 Jul 2017 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.bramstoop.com/tags/ip-whitelisting/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>ipSecurityRestrictions on Azure App Services</title>
      <link>https://www.bramstoop.com/posts/2017/07/2017-07-16-ipsecurityrestrictions-on-azure-app-services/</link>
      <pubDate>Sun, 16 Jul 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2017/07/2017-07-16-ipsecurityrestrictions-on-azure-app-services/</guid>
      <description>BACK TO BLOG OVERVIEW
  With the powershell scripts underneath you can easily close and open traffic towards your azure app services. Note: by adjusting the resource name variable you can add appsettings to your staging slot as well.
 [expander_maker id=&amp;quot;1&amp;rdquo; more=&amp;quot;Script: open to the world&amp;rdquo; less=&amp;quot;Collapse&amp;rdquo;] ### Open to the world ### Write-Host &amp;ldquo;Open all traffic to app service&amp;rdquo; $resourceGroupName = &amp;lsquo;TOBEFILLED&amp;rsquo; $resourceName = &amp;lsquo;YOURAPPNAMEHERE&amp;rsquo; + &amp;lsquo;/web&amp;rsquo; $r = Get-AzureRmResource -ResourceGroupName $resourceGroupName -ResourceType Microsoft.</description>
    </item>
    
  </channel>
</rss>