Home

Azure MFA "Activation Failed" error with Microsoft Authenticator App

%3CLINGO-SUB%20id%3D%22lingo-sub-177675%22%20slang%3D%22en-US%22%3EAzure%20MFA%20%22Activation%20Failed%22%20error%20with%20Microsoft%20Authenticator%20App%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-177675%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20opened%20a%20premier%20ticket%2C%20but%20has%20anyone%20in%20the%20community%20seen%20this%20error%20before%3F%26nbsp%3B%20We've%20got%20a%20few%20users%20that%20can't%20set%20up%20the%20Microsoft%20Authenticator%20app%2C%20and%20nothing%20we%20do%20is%20working.%26nbsp%3B%20This%20is%20rolling%20out%20to%20all%20of%20our%20users%20overnight%20tonight%2C%20and%20none%20of%20our%20global%20testing%20has%20run%20into%20anything%20like%20this.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20563px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F31240iD13F7B151AC22069%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22iphoneQRerror.png%22%20title%3D%22iphoneQRerror.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-177675%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAuthentication%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIdentity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-637136%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20MFA%20%22Activation%20Failed%22%20error%20with%20Microsoft%20Authenticator%20App%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-637136%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F637%22%20target%3D%22_blank%22%3E%40Brent%20Ellis%3C%2FA%3E%26nbsp%3BI%20know%20it's%20an%20old%20post%2C%20but%20I'm%20just%20looking%20into%20the%20same%20error%20now%2C%20so%20am%20curious%20if%20anything%20ever%20came%20of%20this%20one%3F%26nbsp%3B%20I've%20got%20one%20user%20who%20has%20an%20older%20phone%20(iPhone%205)%20and%20we're%20getting%20the%20same%20error%20message.%26nbsp%3B%20Have%20checked%20push%20notifications%20on%20the%20device%20too.%26nbsp%3B%20Reinstalled%20the%20Authenticator%20app%20and%20still%20no%20dice%20(hence%20hitting%20the%20forums%20now).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-637389%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20MFA%20%22Activation%20Failed%22%20error%20with%20Microsoft%20Authenticator%20App%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-637389%22%20slang%3D%22en-US%22%3E%3CP%3EI%20already%20posted%20a%20separate%20reply%2C%20but%20in%20the%20time%20since...%26nbsp%3B%20I%20may%20have%20found%20a%20solution.%26nbsp%3B%20I%20don't%20like%20coming%20across%20posts%20without%20%3CEM%3Esomething%3C%2FEM%3E%20to%20try%2C%20so%20wanted%20to%20add%20my%20steps%20here%20(you%20never%20know%20when%20someone%20else%20is%20looking%20for%20it).%26nbsp%3B%20Again%20though%20(here%20comes%20the%20disclaimer)%2C%20this%20is%20an%20old%20post%20(no%20further%20info%20from%20the%20original%20case%2C%20so%20it%20could%20be%20that%20we're%20dealing%20with%202%20different%20issues).%26nbsp%3B%20Whilst%20my%20error%20message%20matched%20exactly%20that%20shared%20in%20the%20original%20post%2C%20from%20the%20research%20I%20did%20it%20looks%20like%20there%20may%20be%20other%20error%20messages%20that%20could%20be%20the%20same%2Fsimilar%20issue%20(and%20don't%20mention%20'push%20notifications'%20in%20the%20error).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20be%20clear%2C%20we%20were%20seeing%20this%20error%20for%20one%20user%20at%20the%20point%20of%20scanning%20a%20QR%20code%20in%20the%20Microsoft%20Authenticator%20app%20to%20add%20an%20account%20(Office%20365%20account%20where%20we%20had%20just%20enabled%20the%20user's%20MFA).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFirst%2C%20probably%20worth%20sharing%20the%20first%20few%20basic%20things%20we%20tried%3B%3C%2FP%3E%3CP%3E-%20Try%20again%3C%2FP%3E%3CP%3E-%20Try%20manually%20with%20code%20and%20URL%3C%2FP%3E%3CP%3E-%20Try%20configuring%20MFA%20through%20an%20incognito%2Fprivate%20window%3C%2FP%3E%3CP%3E-%20Check%20device%20push%20notifications%3C%2FP%3E%3CP%3E-%20Check%20device%20permissions%3C%2FP%3E%3CP%3E-%20Check%20device%20for%20latest%20OS%20and%20app%20updates%3C%2FP%3E%3CP%3E-%20Deleted%20and%20reinstalled%20the%20MS%20Authenticator%20app%3C%2FP%3E%3CP%3E-%20Disable%20and%20re-enable%20user's%20MFA%20(requires%20admin)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20found%20a%20link%20in%20a%20separate%20Microsoft%20Support%20article%20(which%20may%20still%20be%20useful...%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-gb%2Fhelp%2F3120908%2Factivation-failed-error-when-you-try-to-set-up-azure-multi-factor-auth%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-gb%2Fhelp%2F3120908%2Factivation-failed-error-when-you-try-to-set-up-azure-multi-factor-auth%3C%2FA%3E).%26nbsp%3B%20Link%20within%20the%20article%20didn't%20work%20for%20me%2C%20but%20am%20assuming%20that%20could%20be%20our%20Azure%20subscription%20or%20the%20age%20of%20the%20link%20(article%20is%202016).%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EEssentially%2C%20we're%20trying%20to%20%3CSTRONG%3Echeck%20if%20the%20user's%20MFA%20has%20been%20blocked%3C%2FSTRONG%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhilst%20the%20link%20contained%20within%20the%20above%20article%20did%20not%20work%2C%20this%20did%20(as%20a%20global%20admin)%3B%3C%2FP%3E%3CP%3E-%20Go%20to%20Azure%20portal%3C%2FP%3E%3CP%3E-%20Go%20to%20Azure%20Active%20Directory%3C%2FP%3E%3CP%3E-%20Go%20to%20MFA%3C%2FP%3E%3CP%3E-%20Go%20to%20Block%2Funblock%20users%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20problem%20user%20was%20listed%20there.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Press%20Unblock%3C%2FP%3E%3CP%3E-%20Provide%20Reason%3C%2FP%3E%3CP%3E-%20Press%20OK%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20that%20remains%20now%20is%20to%20know%20%3CU%3E%3CSTRONG%3Ewhy%3C%2FSTRONG%3E%3C%2FU%3E%20they%20got%20blocked%20in%20the%20first%20place%20(parking%20that%20for%20a%20rainy%20day...%26nbsp%3B%20or%20someone%20else)%3C%2FP%3E%3C%2FLINGO-BODY%3E
Brent Ellis
Valued Contributor

We've opened a premier ticket, but has anyone in the community seen this error before?  We've got a few users that can't set up the Microsoft Authenticator app, and nothing we do is working.  This is rolling out to all of our users overnight tonight, and none of our global testing has run into anything like this.

 

iphoneQRerror.png

2 Replies

@Brent Ellis I know it's an old post, but I'm just looking into the same error now, so am curious if anything ever came of this one?  I've got one user who has an older phone (iPhone 5) and we're getting the same error message.  Have checked push notifications on the device too.  Reinstalled the Authenticator app and still no dice (hence hitting the forums now).

I already posted a separate reply, but in the time since...  I may have found a solution.  I don't like coming across posts without something to try, so wanted to add my steps here (you never know when someone else is looking for it).  Again though (here comes the disclaimer), this is an old post (no further info from the original case, so it could be that we're dealing with 2 different issues).  Whilst my error message matched exactly that shared in the original post, from the research I did it looks like there may be other error messages that could be the same/similar issue (and don't mention 'push notifications' in the error).

 

To be clear, we were seeing this error for one user at the point of scanning a QR code in the Microsoft Authenticator app to add an account (Office 365 account where we had just enabled the user's MFA).

 

First, probably worth sharing the first few basic things we tried;

- Try again

- Try manually with code and URL

- Try configuring MFA through an incognito/private window

- Check device push notifications

- Check device permissions

- Check device for latest OS and app updates

- Deleted and reinstalled the MS Authenticator app

- Disable and re-enable user's MFA (requires admin)

 

I found a link in a separate Microsoft Support article (which may still be useful...  https://support.microsoft.com/en-gb/help/3120908/activation-failed-error-when-you-try-to-set-up-azur...).  Link within the article didn't work for me, but am assuming that could be our Azure subscription or the age of the link (article is 2016).


Essentially, we're trying to check if the user's MFA has been blocked.

 

Whilst the link contained within the above article did not work, this did (as a global admin);

- Go to Azure portal

- Go to Azure Active Directory

- Go to MFA

- Go to Block/unblock users

 

My problem user was listed there.

 

- Press Unblock

- Provide Reason

- Press OK

 

All that remains now is to know why they got blocked in the first place (parking that for a rainy day...  or someone else)

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
50 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
32 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
15 Replies
Discussion - Updating our interface with Fluent touches
Elliot Kirk in Discussions on
102 Replies