title: Azure Front Door configured site is returning "Services not available"
body: <p>I've got an Azure resource group with two App Service web applications in separate locations deployed and working as expected. I also have a Front Door configuration setup. This is responding as expected when accessed via the <code>azurefd.net</code> address.</p>
  
  <p>I want to add a custom domain to this configuration.  First, I created a <code>CNAME</code> in my DNS for a <code>www</code> address.  </p>
  
  <p>I then added a simple custom domain configuration (via an ARM template), passing the fully qualified custom domain name as a parameter.  </p>
  
  <p>The frontend section looks like this when deployed via the template:</p>
  
  <pre><code>                "frontendEndpoints": [
                  {
                      "name": "frontendEndpoint1",
                      "properties": {
                          "hostName": "[concat(parameters('frontDoorName'), '.azurefd.net')]",
                          "sessionAffinityEnabledState": "Enabled",
                          "sessionAffinityTtlSeconds": 0
                      }
                  },
                  {
                      "name": "frontendEndpoint2",
                      "properties": {
                          "hostName": "[parameters('customDomainName')]",
                          "sessionAffinityEnabledState": "Enabled",
                          "sessionAffinityTtlSeconds": 0
                      }
                  }
              ],
  </code></pre>
  
  <p>The frontend is deployed as expected and I can still access the <code>azurefd.net</code> address.</p>
  
  <p>However, when I try and access the <code>www</code> address, I receive an error in the browser with the message:</p>
  
  <blockquote>
    <p>Our services aren't available right now.  We're working to restore all
    services as soon as possible. Please check back soon.
    0tEdHXAAAAAADUxvBayGtQLDTjRthnz9XTE9OMjFFREdFMDMyMQBFZGdl</p>
  </blockquote>
  
  <p>I have waited more than half an hour for any DNS changes to roll out, but it still doesn't work.</p>
  
  <p>What could the problem be? What's a easy way of troubleshooting such errors? To be clear, I haven't yet added any HTTPS certificates to this configuration.  The web applications do respond to both HTTP and HTTPS, so hopefully that isn't the issue.</p>