Outlook 2016 and O365 Connectivity Issues RRS feed

  • Question

  • I ask a question. Why doesn't Microsoft test their products before releasing them to the public and have us be the guinea pigs? I have never seen quality control reach it's lowest point since I started in this industry 42 years ago. My recommendation "Don't release products to the public until their ready!!". If your going to offer Office 2016 via the O365 subscription, then you better make sure it works. Having issues with autodiscovery and connectivity. We ran an on-premise Exchange 2010 server for years and never had any issues. Decided to move to O365 since we are a Microsoft partner and wanted to start reselling this service. This has been the biggest fiasco since we started our migration on Monday. Keep in mind I've personally performed dozens of Exchange migrations over the years, so I'm no newbie in this environment. I have so many support calls open with the Microsoft Online team, I can't keep track. So I've tried Outlook 2010 and have no issues. Having issues with Outlook 2013 and 2016. I've tried a clean install and removal and upgrade. Doesn't matter. I've been asked by support whether these machines are part of a AD domain or not. Why should that matter at all. What, you don't support corporate environments? Also, this has wasted many hours of troubleshooting a Microsoft issue.  It's not my problem but now it is my problem. I should send my consulting bill to Microsoft for payment!

    • Edited by Gio Stefani Friday, October 2, 2015 2:36 PM
    Friday, October 2, 2015 2:33 PM