This being said, however, I do suggest that you configure and (if possible) use Outlook Anywhere as it will make your life easier down the road (e.g. Of course, this might – depending on your environment – be a little challenging. All Microsoft Office 365 suite users connect to Microsoft. The solution is as simple as the problem itself: re-enable Outlook Anywhere for the user and you would be fine. Microsoft Outlook Anywhere is a software feature that allows end users with Microsoft Office Outlook 2010, Outlook 2007 or Outlook 2003 to access corporate email and calendars over the Internet from outside the corporate domain without having to log into a virtual private network ( VPN ). To make a long story short, if Outlook Anywhere is disabled at the user level, Autodiscover does not return the External EWS URL which is required to make the Free/Busy call. ![]() As this relates to Hybrid Exchange, I was – of course – intrigued and remembered that I (once) encountered a similar scenario, but could not remember how I resolved the problem back then.Īfter some digging, I came across the following KB article which describes the behavior of Free/Busy requests and why they might fail of Outlook Anywhere is disabled (blocked) on the user-level: ![]() Recently, I bumped into Jaap Wesselius’ article about an issue he encountered about Hybrid Free/Busy lookups failing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |