Forum Discussion
Microsoft Whiteboard app on IOS Unable to log in with work or school account option.
Afternoon all,
I have a couple of employees that want to use the whiteboard app on there iPad pro's, but for some reason they are not able to log in with there work account. It seams to be stuck on the " Taking you to your organization sing-in page" once you select the work or school option. Has any one else seen this or have a solution to this?
- Try downloading Microsoft Authenticator, opening it up , then try again.
- Can you use it? Assuming it's already enabled in the tenant?
- Pieter JoubertCopper Contributor
Yea, i confirmed in the our portal that it is enable for organization. I also downloaded the app on my windows 10 laptop and was able to log in with no problem.
- Pieter JoubertCopper ContributorJust tried on my iPhone and got the same results, stuck on the Taking you to your organization sing-in page.
- Todd BlevinsCopper Contributor
Are others still having this issue? I am and have been unable to find a solution. BTW, I have confirmed with my admin that we are authorized, it works on my iPhone but not ipad and I use the Authenticator application. Appreciate the help!
- No reason it shouldn't work on ipad if it works on the iphone, it can't be an account issue, has to be a wrong version of software, wrong authentication, needs update etc. I would make sure you have Microsoft authentication, it's setup and you see your account in there for your domain. and Also update the white board app.
- Robin NilssonBronze ContributorOur issues still haven't been fixed from early December. Desktops work fine, anything wifi/cell (basically, from outside) don't work. I'm pretty sure it's something that's blocked on our network but it used to work last October and they haven't done anything obvious lately on the network. Does seem to be an authentication issue, though, somethings not getting through (even with Authenticator app). Frustrating because I can see some good applications for our content folks to use this on their laptops.
- Todd BlevinsCopper Contributor
Thanks Robin. Still an issue here as well. The odd thing for me is that it works on my iPhone but not my iPad. I have the same MS Authenticator app and Azure profile on both devices as well. All other Office365 apps work on both. Again, thanks for weighing in and please let me know if you hear of a resolution.
Todd
- Todd BlevinsCopper Contributor
I was finally able to solve it by completely deleting the Whiteboard and Authenticator app from my device. I reinstalled the authentication app first and set it up using the scanned QR code from my https://account.activedirectory.windowsazure.com/securityinfo#/register?view=LandingPage
Then I reinstalled the Whiteboard app and signed in successfully via the authenticator app. Candidly I thought I had done this before and still not been able to get the app to work but for some reason it worked this time. Hope this helps others.
- Robin NilssonBronze Contributor
Thanks for the info - I'm glad you got it to work. I've tried that a bunch of times and tried it again just now.
When I re-install the Authenticator app, it comes up with all my accounts already there. I can't do anything with them - there is no 'setup' options using QR codes or anything else.
And then Whiteboard just acts the same way - plain box asking for 'work or school' or 'personal', then spins awhile and the 'we couldnt sign you in'.
There's something really goofy with that Authenticator app, If you look at 'help' it says it 'helps you sign in to your accounts if you use two-factor authentication'.
We don't. And my account signins are fine everywhere else and in all other applications.
So I've deleted Authenticator again. There must be some setting somewhere that's been corrupted.
- Robin NilssonBronze Contributor
Well, wonder of wonders, there was an update to iOS Whiteboard yesterday (version 1.19101103) - just downloaded it today. I can now access whiteboard with work account. Description of change had 'We've addressed a bug that occasionally caused a loading issue at start-up for certain devices' - maybe that was it.
I'm happy!