Forum Discussion
Whiteboard - Can't Sign-in/Sync with Work Account. Authenticator Keeps Popping Up.
- DeletedJun 07, 2020
jespasan I solved my problem, but I don't know exactly why it solves it. I had to install the management certificates from the Company Portal app (bascially Microsoft Intune). That's the thing that lets your company set policies like password length, remote wipe on your behalf, etc. After that, no more problems with Authenticator. Whiteboard then works.
Not sure if this will be helpful for folks or not but I was finally able to figure out a way to get signed in. Here's my setup:
I have two "work" accounts (one personal, one actual work). Steps to reproduce/solve:
- Completely uninstall the app.
- Re-download and install
- Open the app
- Select 'work' when prompted to sign in.
- Received the error I previously posted.
- Downloaded the MS Authenticator app (but didn't actually do anything with it)
- Re-opened Whiteboard
- Was prompted to sign in
- Selected 'work' and proceeded.
- Received a totally different error stating that the user I was attempting to sign in with did not belong to the tenant. For some reason my personal "work" tenant was already associated to Whiteboard and my actual work user of course does not exist there.
- Decided to try logging in with my personal "work" user --> SUCCESS
- "Signed out" of personal "work" user
- Was taken to a new screen that listed AD accounts where I saw my personal 'work' user.
- Selected the '+' option and was prompted to sign in with a work account.
- Signed in with my actual work account --> SUCCESS
Very odd and roundabout flow but it finally worked.
Yes this is it!
You need to install the MS auhenticator app (just install) and the login process to the work account works again.....
Bug.
- jespasanSep 04, 2020Copper Contributor
To update on this, the way I solved it for my corporate account scenario was
a) I removed from Authenticator my personal O365 credentials, leaving just AzureAD from my employer's account.
b) Activated and added to the Ipad the MFA (before, it had only the AzureAD) so authenticator has now two entries from my employer O365. I.e. I used the portal to generate the QR code and added it.
This fixed the issue fully, I could enter, create a whiteboard and send invitations
c) I added my personal authenticator credential and all seemed to keep working fine.
We did NOT uninstall, de-register/re-register or otherwise touch anything else.
The IT support colleague thinks it was just the lack of MFA account in the device.
Seems accurate, but I think I shouldn't need to register my BYOD ipad as an extra MFA device, every other MS app works fine with azureAD and where needed, they would ask for approval to my work iphone's authenticator. Why WB should be different? no idea.
Anyhow, now at least works.