The BlackBerry "Key" versions (Key 1 and Key 2) are Android-based phones who continue to make use of the BlackBerry Hub application to coordinate all inbound messages across several different platforms. The solution to this problem is scattered across a number of different MSFT sites, so I'll briefly recap here how we solved it to help anyone else who runs into this.
You could click the " Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Going there to then assign that app to that user fixes the first step. doing this made the BlackBerry Hub+ appear in the users Azure app area. The user ends up being prompted for an Azure admin to log in. The solution was to have the BlackBerry on site and have the user try to add the O365 account into the Hub. Your device won't be able to synchronize with the server via Exchange ActiveSync because of an access policy defined on the server.ĭevice ID: androidc# ĭevice user agent: Android-BBF100-2/8.1.0 Subject: Your mobile device has been denied access to the server because of server policies. After working through getting the BlackBerry Hub+ app enabled and assigned to him in Azure, he received the following message via email on his laptop. We are not trying to turn this into a managed device. He has no problem using the device on other O365 servers, but trying to get his email account to be accessible on his device. I have a user with a BlackBerry Key2 running Android 8.1 (like all later BlackBerries use). and according to the scenario introduced here: Answering your own questions on Microsoft Q&A, I would make a brief summary of this thread: They can only accept answers by others.". Great to know that you've already thought of a solution and really appreciate it for your sharing!īy the way, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. It didn't show up as a quarantined phone, but adding "Android" to the device access rules page in the Exchange admin area solved the problem. The phone was still blocked via some policy. After that was taken care of, the thread here outlines the issue.
0 kommentar(er)
