Our Exchange 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 ourdomain.com over SSL, ever since we moved to Office 365 last week, our web server has been receiving large numbers of requests forhttps://ourdomain.com/autodiscover/autodiscover.xml, which, of course, does not exist there. 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 forhttps://ourdomain.com/autodiscover/autodiscover.xml by responding with a simple 301 HTTP response status code (permanent redirect) tohttps://autodiscover.ourdomain.com/autodiscover/autodiscover.xml
Will this work or cause problems?
Our web server is a Ubuntu VPS with Apache proxying all requests to Tomcat, the web app being written in Java, so IIS-specific features won't help us, but at first glance, its Application Request Routing feature would be equivalent to what I want to do and I imagine there are more admins here who have dealt with Exchange than there are in the Ubuntu forums :-) Moreover, a Microsoft support rep suggested I consult these forums for advice (see:http://community.office365.com/en-us/forums/160/t/82051.aspx )
Has anyone else here successfully implemented anything to deal with Autodiscover requests being sent to their web server? Basically, all I want to acheive is to make Outlook etc. go straight to consulting autodiscover.ourdomain.com without generating thousands of errors first on our web server. Any other suggestions are welcome.
Thanks in advance, and apologies for being slightly off-topic :-)
Joe