title: How do I get Azure Traffic Manager to work as a failover for two Web Apps?
body: <p>I set up two web apps in Azure.  I'm just using this to test out Traffic Manager for now before I do anything in production, so I created two "fake" apps to try it out.</p>
  
  <p>I added a Traffic Manager to the portal at the following URL:</p>
  
  <p><a href="http://mbfakesite.trafficmanager.net" rel="nofollow noreferrer">http://mbfakesite.trafficmanager.net</a></p>
  
  <p>I listed endpoint 1 as the first web app, and endpoint 2 as the second, and I am using the Priority method.</p>
  
  <p>When I stop the first web app in Azure, and go to the trafficmanager URL, I get a 403 error page.  What I want to happen is it to default to the second endpoint.</p>
  
  <p>The end goal is to have an MVC app running on a different server than the production website.  And when, the production servers are down (backups and all) it should default to this "failsafe" app running on a separate server, like a worst-case scenario type of thing.</p>
  
  <p>If it makes a different, both web apps for testing are hosted at azurewebsites.net and in Traffic Manager, one is listed as an Azure Endpoint (the first one) and the other is listed as an External Endpoint.</p>
  
  <p>I also tried adding  to the web.config, as someone suggested on another post I found, but it changed nothing.</p>
  
  <p>Anyone have any ideas, or alternatives to Traffic Manager we could use for this?</p>
  
  <p>Thank you!</p>