<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>azure-app-services on bramstoop.com</title>
    <link>https://www.bramstoop.com/tags/azure-app-services/</link>
    <description>Recent content in azure-app-services on bramstoop.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 27 Mar 2018 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.bramstoop.com/tags/azure-app-services/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Appsettings not present after ARM deployment</title>
      <link>https://www.bramstoop.com/posts/2018/03/2018-03-27-appsettings-not-present-after-arm-deployment/</link>
      <pubDate>Tue, 27 Mar 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/03/2018-03-27-appsettings-not-present-after-arm-deployment/</guid>
      <description>BACK TO BLOG OVERVIEW
  Within the config section of an App Service you are able to define multiple sections. In this example we are using three sections : web, appsettings and logs.
Since we noticed that sometimes the expected settings were not configured/missing after a deployment we figured out some missing dependsOn settings need to be set.
Please note that in the ARM snippet below the appsettings depend on the web settings to be processed.</description>
    </item>
    
    <item>
      <title>Sitecore hardening using Azure App Authentication</title>
      <link>https://www.bramstoop.com/posts/2017/08/2017-08-11-sitecore-hardening-using-azure-app-authentication/</link>
      <pubDate>Fri, 11 Aug 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2017/08/2017-08-11-sitecore-hardening-using-azure-app-authentication/</guid>
      <description>BACK TO BLOG OVERVIEW
  With Azure App Authentication it is easy to secure your app with an identity provider. The steps to take are described at the following page: https://docs.microsoft.com/en-us/azure/app-service-mobile/app-service-mobile-how-to-configure-active-directory-authentication .
For securing certain url paths it is required to set Action to take when request is not authenticated to Allow request (no action).
When you have followed the instructions above, the next step is to create a authorization.</description>
    </item>
    
    <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>