![]() ![]() I think it might be a configuration issue on our end but just wanted to say thank you and that this worked as a permanent solution once we were able to pull up that prompt and log in. After the user authenticates, it says that the machine is now registered to the user and they can use company resources. I did your workaround, we got a prompt from our corporate O365 portal asking the user to authenticate. It seems there was a prompt that was trying to come up but didn't come up. For example, if your mailbox is homed on Microsoft Exchange Server 2013, you will be unable to connect to. These are public folders stored on a version of Exchange that is earlier than the version on which your current mailbox is stored. I was racking my brain for weeks and I can't believe this actually worked. In Microsoft Outlook 2016 for Mac and Outlook for Mac 2011, you cannot connect to legacy public folders. To our VPN and everything went back to working as desired. ![]() For what little it is worth, having my user disconnect from our VPN, reverting her connection back to just her home internet, allowed the O365 authentication window to fully show up the next time we launched Outlook.
0 Comments
Leave a Reply. |