Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Push Notifications don't work properly O365 #30680

Closed
dwatsonit opened this issue May 6, 2019 — with docs.microsoft.com · 9 comments

Comments

Copy link

commented May 6, 2019 — with docs.microsoft.com

Note: I've attempted several times to work with Office 365 support unsuccessfully to resolve this.

If I use passwordless logon with outlook.com (microsoft account) when an auth is required, there is a push notification on the device paired (in my testing either an iPhone XSMax (with and without a paired Apple Watch 2 with the authenticator app) and iPad Pro) with that account. You click on it and must unlock said device and you are then prompted to select the proper code.

When attempting to do the same with a corporate account (O365) there is no push. Rather no real notification. However if you unlock said paired device and open the Authenticator app, you will get a list of the codes to choose from, but it takes a few extra seconds or in some cases requires a pulldown refresh.

I've tried unregistering devices, turning off MFA on the account and turning it back on as well as disabling the tenant and reenabling it and setting up MFA and converting it to passwordless.

I'd love to find the right team to work with to figure out if there is some error or if this is a bug of some sort. I can provide much more detail if I find the right avenue.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@shashishailaj

This comment has been minimized.

Copy link
Contributor

commented May 7, 2019

@dwatsonit Thank you for your query. We will investigate and update further on this.

@MarileeTurscak-MSFT

This comment has been minimized.

Copy link
Contributor

commented May 9, 2019

Do you get the notifications when you select "check for notifications"?
image

@dwatsonit

This comment has been minimized.

Copy link
Author

commented May 9, 2019

@MarileeTurscak-MSFT

This comment has been minimized.

Copy link
Contributor

commented May 9, 2019

Hi @dwatsonit,

If you send me an email at AzCommunity@microsoft.com I can open a support case. I am uncertain if this is a bug and since I don't have a testing environment for this can't confirm.

@MarileeTurscak-MSFT

This comment has been minimized.

Copy link
Contributor

commented May 10, 2019

Closing this out as moving to email/support. I will update the thread when we have a resolution.

@rviljoen

This comment has been minimized.

Copy link

commented Jul 11, 2019

@dwatsonit @MarileeTurscak-MSFT I am seeing the exact same behaviour in my tenant. Did you find a solution to this yet?

@dwatsonit

This comment has been minimized.

Copy link
Author

commented Jul 12, 2019

@rviljoen I forwarded all the information to MSFT outside of this thread but have not heard anything more regarding a solution as of yet.

This comment has been minimized.

Copy link

commented Jul 29, 2019 — with docs.microsoft.com

Seeing the same behaviour here, going to raise this with support as well.

@PRMerger6 PRMerger6 added the Pri1 label Jul 29, 2019

@michaelrnz

This comment has been minimized.

Copy link

commented Jul 31, 2019

Just in case someone else finds this, I resolved this issue by going into the Microsoft Authenticator app, choosing to "Disable phone sign-in" for my AAD Work Account, and then enabling it again right after. This updated the icon in the https://myprofile.microsoft.com portal from a normal MS Authenticator padlock icon, to a phone sign-in icon like you see in the app itself. After about half a day, the push notifications then started working for the passwordless sign-in flow.

My assumption is that because I had enabled phone sign-in on my app for my AAD account, before I could actually use the flow.. that the correct type of app registration was not in place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.