title: Azure Front Door Backend Pool pointing to Azure Load Balancer Public IP not resolving
body: <p>I have an <code>Azure Load Balancer</code> which is configured with an internet facing public IP. I can confirm I can access this public IP from my browser.</p>
  
  <p><strong>My end goal</strong> is to configure <code>Azure Front Door</code> CDN so that it uses the IP from the Load Balancer and at the end of the day I would want to access my load balancer through the Front Door DNS. </p>
  
  <p>I have created the Front Door, I configured a Backend Pool with selecting the option <code>Public IP Address</code> as the type, I locate the Load Balancer <code>Public IP</code> name from the drop-down, leave everything else to default. I then configure the HTTP and HTTPS routing rules.</p>
  
  <p>I check everything is enabled and then I hit the <code>Azure Front Door DNS</code> entry. </p>
  
  <p>According to the FAQ <a href="https://docs.microsoft.com/en-us/azure/frontdoor/front-door-faq#can-we-deploy-azure-load-balancer-behind-front-door" rel="nofollow noreferrer">it should work</a> . I keep getting the following error:</p>
  
  <pre><code>Our services aren't available right now
  We're working to restore all services as soon as possible. Please check back soon.
  </code></pre>
  
  <p>However, if I use a separate DNS entry that points to the same IP and with SSL enabled - and then put that DNS entry in Azure Front Door(instead of the IP) - then accessing the web app through FrontDoor works.</p>
  
  <p>Any insight appreciated - thanks.</p>