Our Autodiscover is configured correctly and working fine for us, but because of the way the Autodiscover feature works (see the answer to this forum discussion: http://community.office365.com/en-us/forums/162/p/42734/145157.aspx#145157) and the fact that our web server responds to both ourdomain.com over SSL, ever since we moved to Office 365 last week, our web server has been receiving large numbers of requests for https://ourdomain.com/autodiscover/autodiscover.xml, which, of course, does not exist. The small amount of additional load on the webserver is not an issue, but we monitor our web app with New Relic, and we keep getting elevated error level alerts because of the high number of 404 (page not found) errors caused by the Autodiscover mechanism checking ourdomain.com first as our potential default SMTP server (which it isn't).
I've suggested the following solution to our lead developer but want to check first whether it could break Autodiscover for us: we can add a controller and route to our web app to handle requests for https://ourdomain.com/autodiscover/autodiscover.xml by responding with a simple 301 HTTP response status code (permanent redirect) to https://autodiscover.ourdomain.com/autodiscover/autodiscover.xml
Will this work or cause problems?
