Microsoft Authenticator OverviewUNIXBusinessApplication

Microsoft Authenticator is the #3 ranked solution in top Authentication Systems. PeerSpot users give Microsoft Authenticator an average rating of 8.8 out of 10. Microsoft Authenticator is most commonly compared to Duo Security: Microsoft Authenticator vs Duo Security. Microsoft Authenticator is popular among the large enterprise segment, accounting for 58% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 17% of all views.
Microsoft Authenticator Buyer's Guide

Download the Microsoft Authenticator Buyer's Guide including reviews and more. Updated: November 2022

What is Microsoft Authenticator?

Microsoft Authenticator is a multifactor app for mobile devices that gives employees easy, secure access to online accounts, providing multi-factor authentication for an extra layer of security.

Passwords can be forgotten, stolen, or compromised. With Authenticator, your phone provides an extra layer of security on top of your PIN or fingerprint.

Protect all of your accounts with two-step verification. The app also helps you secure all of your online accounts by using the industry standard time-based OTP (one-time password) codes.

Microsoft Authenticator was previously known as PhoneFactor, MS Authenticator.

Microsoft Authenticator Customers

Insight Enterprises, South Wales Police, Gwent Police, and Dyfed-Powys, Integrit, Turkiye Finans, Winnebago Industries, Globosat Programadora Ltda

Microsoft Authenticator Video

Microsoft Authenticator Pricing Advice

What users are saying about Microsoft Authenticator pricing:
  • "I'm not totally aware of the pricing and licensing, but I do know that the pricing and licensing must be quite balanced. We are a pretty old client of Microsoft, and MSA is just one of the services we use from Microsoft. There's a whole Microsoft 365 suite that's implemented as well. I'm sure it is something that is acceptable to both parties."
  • "I don't pay for it. Going by how I feel, I see the prices for any MFA solution going down because the more different alternatives there are, the cheaper things should be. Microsoft Authenticator app would be the preferred application, but there are too many ways to implement MFA. I don't know how much it cost, but the price should go down."
  • "Microsoft Authenticator is a free product."
  • "I would advise implementing the solution to VIPs and admins; it's affordable, effective, and efficient. I would say training staff on properly using the tool is also essential."
  • "I am not involved in the pricing or licensing, so I can't speak to that."
  • "It comes free with the Microsoft account. We have a yearly agreement, and all products are covered under it."
  • Microsoft Authenticator Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    Prateek Walia - PeerSpot reviewer
    Change and Communications Manager at a retailer with 10,001+ employees
    Real User
    Provides easy authentication and high security and works absolutely fine even when you switch organizations
    Pros and Cons
    • "Being able to easily authenticate yourself on the MSA app is valuable. It is easy to use. Rather than receiving a code in an SMS, you can just verify that it is you. You don't have to punch in any password or any six-digit code. That's the feature that I like the most."
    • "They can improve how people manage their accounts. They can simplify and provide more information about adding or updating a phone number or email id in the MSA account. A lot of time users do get confused about where to go. For example, if I've changed my mobile number, where do I go and change my mobile number in the MSA account? A lot of time, employees think if they change the phone number in the HR database, it'll automatically get changed on the MSA account, which is not the case. Microsoft can simplify that and add these questions in the FAQ documents as well."

    What is our primary use case?

    I use it to access my work applications. When I install Microsoft Teams or Outlook, or I want to access my work applications, I authenticate myself using Microsoft Authenticator.

    How has it helped my organization?

    During the pandemic, one of the challenges for organizations was how to secure their IT networks. People were working remotely, and some of them were working from the remotest locations. It gave confidence to the organization that only the right person was getting access to work applications.

    It also improves your customer experience or employee experience. You don't have to rely much on servers. 

    What is most valuable?

    Being able to easily authenticate yourself on the MSA app is valuable. It is easy to use. Rather than receiving a code in an SMS, you can just verify that it is you. You don't have to punch in any password or any six-digit code. That's the feature that I like the most.

    It does give you the confidence that no one else can access your details or can have access to your account because it does add a second layer of security. Even if someone hacks the server where my details are stored, unless and until I authenticate myself on MSA, even hackers won't be able to get into my account.

    It works absolutely fine from the login perspective. You can also configure it on third-party devices, and it works pretty well. I haven't faced any issues from the login point of view.

    What needs improvement?

    They can improve how people manage their accounts. They can simplify and provide more information about adding or updating a phone number or email id in the MSA account. A lot of time users do get confused about where to go. For example, if I've changed my mobile number, where do I go and change my mobile number in the MSA account? A lot of time, employees think if they change the phone number in the HR database, it'll automatically get changed on the MSA account, which is not the case. Microsoft can simplify that and add these questions in the FAQ documents as well. They can provide more clarity about how it is different from your organization's database.

    Voice recognition could be added going forward. With a smartphone, such as iPhone, as well as with Windows Hello for business, you already have facial recognition. Voice recognition is something that could be added going forward, especially for people with special needs.

    Buyer's Guide
    Microsoft Authenticator
    November 2022
    Learn what your peers think about Microsoft Authenticator. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
    653,757 professionals have used our research since 2012.

    For how long have I used the solution?

    I have been using it for a year.

    What do I think about the stability of the solution?

    It is quite stable. Coming from Microsoft, you don't question the stability factor at all. I have Microsoft Authenticator installed on my phone, and even when I switched organizations, I could simply add my new workplace email id, and it worked absolutely fine. It is quite stable, and it gives you a good user experience.

    What do I think about the scalability of the solution?

    Scalability-wise, it is quite good. We were rolling it out to 150,000 people across the globe and different geographies. One of the good things is that Microsoft doesn't need any introduction anywhere. In terms of user experience, it is right up there. It is also right up there in terms of how different work applications align with it. I would rate it quite high.

    How are customer service and support?

    Technical support was good. We didn't have to rely on Microsoft's technical support big time because the solution worked very well overall. We had our third-party technical support team involved as well.

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    Before Microsoft Authenticator, we used Okta Multi-Factor, and prior to Okta, we were totally relying on passwords, which was obviously very risky. 

    We switched to Microsoft Authenticator because when you implement the whole Microsoft 365 suite, especially in a large organization, all the work applications sync pretty well with Microsoft, and you already have a good relationship with the vendor. 

    How was the initial setup?

    It was initially on-prem, but later on, we shifted it to the cloud. When I joined the organization, it was already on-prem, and I helped to shift all the data from on-prem to Azure cloud. The process was a little complex. We had a few on-prem issues, and we had to redo the capability testing to check if those issues will arise on the Azure Cloud as well. It was complex because we were again asking some of the users who had changed their phone numbers to go and re-add their phone numbers. If they had the same phone number, it would have worked fine, but if they had changed the phone number, once it is shifted from on-prem to Azure Cloud, it wouldn’t have worked anymore. So, they had to re-add their phone number. The challenge was to identify those users and convince them to redo the activity. This switchover took about two quarters or six months.

    What about the implementation team?

    We had a team of about 7 to 10 people from project management, change management, IT, and global IT teams. We are a massive organization. It was being rolled out to 150,000 people across the globe.

    We did pilot testing across different functions and across different geographies. That's the standard practice that we follow in our organization.

    What was our ROI?

    We have seen an ROI. We were able to secure our IT networks by more than 80%. More than 80% of the audience did subscribe to MSA and used it for logging into their work accounts.

    It took us two to three months to realize its benefits from the time of deployment. We did run a pilot batch. We were trying to customize the solution according to our network. Within a quarter, we were able to identify its benefits.

    What's my experience with pricing, setup cost, and licensing?

    I'm not totally aware of the pricing and licensing, but I do know that the pricing and licensing must be quite balanced. We are a pretty old client of Microsoft, and MSA is just one of the services we use from Microsoft. There's a whole Microsoft 365 suite that's implemented as well. I'm sure it is something that is acceptable to both parties.

    Which other solutions did I evaluate?

    We were totally relying on Microsoft. We didn't evaluate any other vendor.

    What other advice do I have?

    To those looking to evaluate this solution, I would advise doing proper pilot testing to iron out any hurdles later on. It is important to take a call on whether you want to adopt the on-prem model or the cloud model. Obviously, the on-prem model is not sustainable if you're trying to secure your IT networks. The cloud model is more sustainable in that sense. I would advise taking that call right in the beginning.

    I would also advise considering how to secure third-party devices. There might be third-party contractors who don't have the company laptops, but they do have company email ids to log into the company accounts from their own devices. You should work out how you are going to add those devices to the secure cloud.

    I would rate it a nine out of ten. In the next version, if they can come up with voice recognition, especially for people with special needs, it will be helpful.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Microsoft Azure
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Microsoft Teams Senior Engineer at a financial services firm with 10,001+ employees
    Real User
    Top 20
    Enhances security, especially for unregistered devices, and is straightforward to set up for the admins
    Pros and Cons
    • "It enhances security, especially for unregistered devices. It 1000% has security features that help to improve our security posture. It could be irritating at times, but improving the security posture is exactly what the Authenticator app does."
    • "For the end users, it can be confusing if they have worked for another company that had the Authenticator app. It is tricky if they have already had the Authenticator app and then work somewhere else. If they have to download it again and use it again on their phone, it is something that gets complicated. I know how to get through it. They just need to uninstall and reinstall the application, but for them, sometimes, it is confusing."

    What is our primary use case?

    Identity verification would be the number one use case. It also factors into mobile device management for devices that aren't registered to the company. We use MFA, and the Authenticator app is a component for multifactor authentication. So, that's why we use it.

    How has it helped my organization?

    You can set policies to specify where users will have to use the Authenticator app to log into particular applications. 

    It makes all junior users accountable. There is no excuse for someone else logging into anything because of the multifactor authentication and Authenticator app. You have to verify your identity to log in to specific applications that contain confidential information, especially in a HIPAA-compliant environment.

    What is most valuable?

    It enhances security, especially for unregistered devices. It 1000% has security features that help to improve our security posture. It could be irritating at times, but improving the security posture is exactly what the Authenticator app does.

    What needs improvement?

    For the end users, it can be confusing if they have worked for another company that had the Authenticator app. It is tricky if they have already had the Authenticator app and then work somewhere else. If they have to download it again and use it again on their phone, it is something that gets complicated. I know how to get through it. They just need to uninstall and reinstall the application, but for them, sometimes, it is confusing. You can have the Authenticator app for multiple services on your phone, and that's what drives them crazy. They get a code and say "I'm using the code for the Authenticator app, but I can't get in." I tell them that it is because they already had it in, but it is for something else. They now have to add. They don't like that at all. You could be on the phone for 45 minutes trying to figure out what their problem is because they don't.

    Instead of authenticating by getting a passcode or answering the phone, fingerprint identification should be added to the Authenticator app. Currently, with the Authenticator app, you have to reply to the email, enter a code, or answer the phone. It can just call my phone and then I just press the button to verify that this is me.

    For how long have I used the solution?

    I have been using this solution for at least six years. 

    What do I think about the stability of the solution?

    It is very stable. If the Authenticator app is set up, you're not going to get into anything without it. It definitely works.

    I'm not aware of any bugs or glitches. We usually run updates for the whole environment at a time. I'm not familiar with having run into specific bugs with the Authenticator app. I haven't had any problems over the years.

    What do I think about the scalability of the solution?

    I've managed over a hundred thousand users in total, but right now, there are about 10,000 users. We are HIPAA compliant. So, everybody has to use it for everything. They have to use it to log into everything under the Office 365 environment, but in other companies or other places where I worked, it was only for specific applications. So, that's based on company needs.

    How are customer service and support?

    I never had to call technical support for this.

    Which solution did I use previously and why did I switch?

    We were using normal MFA, which is similar. The Authenticator app is for mobile devices per se, but normal multifactor authentication doesn't have to focus on mobile devices. You can try and log in to, for example, SharePoint Online, and if MFA is activated, you would have to just scroll to your email and click, "Hey. Yeah, this is me." The Authenticator app is just for mobile devices in my eyes.

    How was the initial setup?

    It is straightforward for the admins, but end users hate it. On the admin side, it takes 20 minutes at the most.

    The Authenticator app wants you to have all your prerequisites designed for whatever environment you want. If you're going through Azure, you can pick the particular applications on which you want this. You can also pick the users for whom you want it to be effective. You can pick the type of ways they authenticate through the Authenticator app. Those are the simple steps.

    One person is enough for its deployment and maintenance. I do that. That's not even a role. It depends on who you are, but that's not a role. That's not something for which I would employ a person. I wouldn't employ an IT person or an administrator just to focus on this.

    What's my experience with pricing, setup cost, and licensing?

    I don't pay for it. Going by how I feel, I see the prices for any MFA solution going down because the more different alternatives there are, the cheaper things should be. Microsoft Authenticator app would be the preferred application, but there are too many ways to implement MFA. I don't know how much it cost, but the price should go down.

    What other advice do I have?

    It is pretty seamless for the end users, besides the end users having an issue setting up at times.

    It is a seamless transition. It is straightforward on the admin side to set up. As a consultant, my advice to any company is that when it comes to big changes, manage end-user pain or frustration. Communicate with the end users and let them know what's going to happen. Explain to them that they're going to be frustrated, but explain why this exists. 

    I understand why it exists. So, it doesn't bother me, but our end users just hate it. I understand that they don't like it. Nobody likes it, but it is needed. You are never going to meet an end user who likes any type of MFA, but you need to be more clear about its purpose.

    I would rate it an eight out of ten.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Microsoft Azure
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Buyer's Guide
    Microsoft Authenticator
    November 2022
    Learn what your peers think about Microsoft Authenticator. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
    653,757 professionals have used our research since 2012.
    Tom Kost - PeerSpot reviewer
    ICT Project & Solution Manager at Kanton BS
    Real User
    Top 10
    Free to use with a good user interface and good performance
    Pros and Cons
    • "The solution is free to use and you can use it for every service."
    • "Adding a new account can be tricky."

    What is our primary use case?

    The Authenticator app is a client application on your smartphone, usually, and you configure your profile in the cloud. I use it with my Android smartphone. 

    This is a Microsoft standalone application, which the user installs usually on a mobile device, either iOS-based or in my case, Android-based. Then you add your enterprise accounts into the Microsoft Authenticator app, your work account from Microsoft 365, or your whatever on-premise account, which makes uses the Azure or whatever IDP, identity provider so that you can do single sign-on or multi-factor sign-ins.

    How has it helped my organization?

    It's an authenticator. How it's used really depends on the use case that it is configured with. If you are using your Microsoft 365 work account, if your organization requires you to do multi-factor authentication, not just with the username and password, with an additional factor like the Microsoft Authenticator app, then it simply offers that extra level of protection and security.

    You can manage locally additional pathways or passwords. You can collect your credit card information or whatever secret notices in the authenticate app. This is something that got the addition the last couple of years.

    What is most valuable?

    You could use it for different use cases. 

    The Azure AD-integrated single sign-on scenarios are the most useful due to the fact that, if you are in a cloud application that you have on your smartphone, the Authenticator just requests you to allow or deny the access as a factor. Other applications require a token where you have to enter in an additional pin. Having the single sign-on or the multi-factor way with just allowing the application with one tap to authenticate is really smart.

    The solution is free to use and you can use it for every service.

    They recently redid the user interface a few months ago and it looks good.

    I've found the solution to be stable and scalable. 

    What needs improvement?

    Adding a new account can be tricky. I do it a lot and therefore am used to it, however, if you don't you tend to forget the process. If you had a bottom menu and the settings menu, for example, be added to the bottom menu instead of a different place, the top right corner, it might be more intuitive.

    One area of improvement is always with global offerings from large companies where we have a lot of users that require help. Users need videos, et cetera, in their own language, and in German, there is not much from Microsoft. These are products that have a very, very fast life cycle. They upgrade the services and applications in a very high rhythm every couple of months, and even Microsoft does not have the resources to offer the learning material in all the regions, however, they offer their services.

    We have then to add some additional use via manuals of how to set up, et cetera, as we have users that are not willing or cannot understand videos in English that come from Microsoft.

    For how long have I used the solution?

    I've been using the solution for two to three years. It might even be longer than that.

    What do I think about the stability of the solution?

    The solution is stable. I haven't had any problems so far. 

    What do I think about the scalability of the solution?

    The product scales well. 

    The goal is to have everyone using it. We are in the rollout phase, and in my organization of about 1,500 users, after a couple of weeks, we have maybe a third of the population starting to use the application. 

    This is like this every rollout. It takes a couple of weeks to a month. In the end, we will have around 7,500 users using Microsoft Authenticator or the Microsoft multi-factor authenticator service that allows you to choose different factors. We have a lot of things using the Authenticator app. 

    How are customer service and support?

    We have central support organizations and I don't access Microsoft support myself. Therefore, I can't speak to their level of service.

    Which solution did I use previously and why did I switch?

    I've used many authenticator applications. I used already Microsoft Authenticator when it came out, maybe five, six, or seven years ago. Then I used Google Authenticator and other authenticator applications. You can, however, use these all in parallel. For example, if you mix your private and your work accounts in the same applications, or if your smartphone is managed by your company and you want to separate your private accounts from any corporate policy that can delete your smartphone, you can use different authenticators for different purposes. Right now, I have the Authenticator app in front of me, and I have seven accounts configured, and this is a mix of private and corporate or work accounts.

    How was the initial setup?

    The initial setup is easy. You just download it and start using it. 

    We don't need to worry about maintenance. This is a service from Microsoft.

    What's my experience with pricing, setup cost, and licensing?

    The solution doesn't cost anything to use.

    Which other solutions did I evaluate?

    I'm the Chief Security officer of our organization. I always have to do some research on these topics.

    What other advice do I have?

    I'm a Microsoft customer.

    I'd advise any user to use MFA these days. There's not just war in Ukraine. There's also war in this kind of space and a multi-factor authentication method is a must just to make your cyber life a little bit safer at least.

    I'd rate the product eight out of ten.

    Which deployment model are you using for this solution?

    Public Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Prateek Agarwal - PeerSpot reviewer
    Manager at NISG
    Real User
    Top 5Leaderboard
    Straightforward to use with a simple UI, and is stable and reliable
    Pros and Cons
    • "What I like about Microsoft Authenticator is that it has good features. I also like that the tool is straightforward to use. Microsoft Authenticator also has a good UI that's very simple to use. I also like that I didn't find any limitations or negative aspects from the features of the tool because Microsoft Authenticator is not an extensive application. It has a two-factor based authentication which validates the user through the password, then it approves authentication."
    • "Microsoft Authenticator can improve their notifications because sometimes, my team doesn't receive notifications about app updates and authentication failures."

    What is our primary use case?

    My company is using Microsoft Authenticator for two-factor authentication for apps and services. The tool is deployed in various geographic locations globally. It is used by product development, product engineers, consulting teams, and some senior-level stakeholders within the organization.

    How has it helped my organization?

    Authentication and security are the primary concerns in our organization. Through Microsoft Authenticator, we provide authorization to the right people so that only eligible people can access an application. We can verify that all users using each application are valid and verified through the two-factor authentication provided by Microsoft Authenticator. We have some Azure cloud-based applications where users log in, and we need to ensure that the right people are authenticated and have the right roles in our organization. These are the ways Microsoft Authenticator benefits our organization and serves our organization's purposes.

    What is most valuable?

    What I like about Microsoft Authenticator is that it has good features. I also like that the tool is straightforward to use. Microsoft Authenticator also has a good UI that's very simple to use.

    I also like that I didn't find any limitations or negative aspects from the features of the tool because Microsoft Authenticator is not an extensive application. It has a two-factor based authentication which validates the user through the password, then it approves authentication.

    What needs improvement?

    Microsoft Authenticator can improve their notifications because sometimes, my team doesn't receive notifications about app updates and authentication failures.

    For how long have I used the solution?

    I've been using Microsoft Authenticator for more than two years.

    What do I think about the stability of the solution?

    Microsoft Authenticator is a stable and reliable tool. My company has used it for more than two years, so I can say it's highly reliable. As the tool is used for solving security issues, it's a secure solution, and I didn't see any problems, security-wise.

    What do I think about the scalability of the solution?

    My company hasn't scaled up Microsoft Authenticator because it's just for two-factor authentication. You just approve or disapprove authentication on your enterprise applications. You'll only be required to scale Microsoft Authenticator when you simultaneously have at least one hundred to two hundred applications and multiple authentication requests come in.

    How are customer service and support?

    Support for Microsoft Authenticator was very helpful. Support is available 24x7, and I didn't find any issues with support. I'd rate the support a nine out of ten.

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    We used Google Authenticator and switched to Microsoft Authenticator because we migrated our applications to Microsoft Azure. We also have some Microsoft Office 365 applications and other Microsoft workspace and Office solutions, so we wanted our products under the same Microsoft umbrella. Microsoft Authenticator, a Microsoft product, was our first choice, and it was a good fit for authentication purposes.

    How was the initial setup?

    I'm a user, administrator, and contract negotiator for Microsoft Authenticator. I'm also part of the implementation team, and I found the initial setup for this tool straightforward. It doesn't require an advanced level of technical knowledge, and it took around three to four days for the complete implementation and deployment of Microsoft Authenticator.

    What about the implementation team?

    Microsoft Authenticator was implemented in-house.

    What's my experience with pricing, setup cost, and licensing?

    Microsoft Authenticator is a free product.

    What other advice do I have?

    Microsoft Authenticator doesn't require any maintenance. Microsoft takes care of upgrades and version changes.

    My advice to others looking into implementing Microsoft Authenticator is to go ahead. I highly recommend Microsoft Authenticator to prospective buyers, especially those using Microsoft products. Microsoft Authenticator is the perfect solution for two-factor authentication.

    My rating for Microsoft Authenticator is ten out of ten.

    My company is a customer of Microsoft.

    Which deployment model are you using for this solution?

    Public Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Carlos Brandao - PeerSpot reviewer
    CEO at Intelliway
    Reseller
    Top 10
    Robust security, excellent integration with other Microsoft products, in an affordable, scalable, and stable solution
    Pros and Cons
    • "We have a history of all our authentications and excellent integration with the Microsoft solutions we use at our company. It runs smoothly in Windows and macOS."
    • "I want to see more features to improve security, such as integrated user behavior analysis."

    What is our primary use case?

    We use the Authenticator app on our mobile phones and to authenticate for Office 365. We also provide consulting services and recommend Microsoft Authenticator to clients looking for an MFA solution.

    How has it helped my organization?

    The solution improved our and our clients' security; end users are more confident knowing that their information is confidential. Strategic users, VIPs, and admins are protected from potential attacks because their authentication goes through Microsoft Authenticator.

    The product has significantly increased our security maturity and gives us comfort knowing we have security in a good, affordable solution.

    What is most valuable?

    We have a history of all our authentications and excellent integration with the Microsoft solutions we use at our company. It runs smoothly in Windows and macOS.

    What needs improvement?

    I want to see more features to improve security, such as integrated user behavior analysis.

    For how long have I used the solution?

    We have been using the solution for two years. 

    What do I think about the stability of the solution?

    The tool is stable, we haven't had any issues regarding stability. 

    What do I think about the scalability of the solution?

    Scaling is easy as the product is hosted in the cloud; it's a robust and trustworthy solution.

    Currently, we have 100 end users in our company, and we have some clients with around 1000 end users of Microsoft Authenticator.

    How are customer service and support?

    We never needed to contact technical support as we have never had any problems, so I can't comment on that.

    Which solution did I use previously and why did I switch?

    We previously used JumpCloud before migrating to Microsoft Authenticator, and we did that because it's more affordable and has better integration with Office 365 and the other Microsoft products we implement.

    How was the initial setup?

    The setup was straightforward. We made an implementation plan and transitioned from using MFA via email and SMS messages to using Microsoft Authenticator.

    Our security team is responsible for all our security solutions, and they take care of the maintenance, which I understand to be relatively light.

    We have a Security Operation Center in our company. Another company using the same solution without a team like ours may require several hours a month to manage the solution.

    What about the implementation team?

    We implemented it in-house since we are a consulting services company.

    What was our ROI?

    We think the solution is excellent and provides a return on our investment.

    What's my experience with pricing, setup cost, and licensing?

    I would advise implementing the solution to VIPs and admins; it's affordable, effective, and efficient. I would say training staff on properly using the tool is also essential.

    Which other solutions did I evaluate?

    We decided to go straight for the Microsoft offering since we use Office 365.

    What other advice do I have?

    I would rate this solution a nine out of ten.

    When we deployed Microsoft Authenticator for our clients, we initially had some requests for training. We delivered the training, and the end users could adapt to it; the transition was smooth.

    The solution is extensively used within our organization.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Microsoft Azure
    Disclosure: My company has a business relationship with this vendor other than being a customer: MSSP
    Flag as inappropriate
    PeerSpot user
    Rajorshi Roy - PeerSpot reviewer
    Jr. System Admin at a tech services company with 5,001-10,000 employees
    MSP
    Top 10
    Offers an additional layer of security with MFA, multiple authentication methods, and excellent technical support
    Pros and Cons
    • "The two-factor authentication provides an additional layer of security for our organizational data, so Microsoft Authenticator plays a crucial role in making our confidential data more secure."
    • "Our users sometimes experience issues from having multiple Microsoft accounts, which can cause some confusion and hassle."

    What is our primary use case?

    We primarily use the solution for MFA; to access apps such as Teams or Outlook, two-factor authentication with our mobile phones is required.

    We also use Authenticator to assist our clients with re-enrolling, moving, and adding new devices. 

    How has it helped my organization?

    The solution helps us keep our data secure and prevents security breaches, malware, etc. The app also provides us with options regarding our authentication preferences.

    What is most valuable?

    The two-factor authentication provides an additional layer of security for our organizational data, so Microsoft Authenticator plays a crucial role in making our confidential data more secure.

    The solution offers multiple authentication methods via text, call, or the app. This gives us many options and flexibility when it comes to MFA.

    What needs improvement?

    Our users sometimes experience issues from having multiple Microsoft accounts, which can cause some confusion and hassle.

    It would be good to see the incorporation of fingerprints and Face IDs as authentication options. This would simplify the authentication process for end users, especially those who aren't as tech-savvy. It is also a consideration for visually impaired people, for example.

    For how long have I used the solution?

    We have been using the solution for about one and a half years. 

    What do I think about the stability of the solution?

    Microsoft Authenticator is a very stable application; our only issue is that we run into the occasional bug.

    What do I think about the scalability of the solution?

    The solution is highly scalable. Many organizations use it around the world. 

    How are customer service and support?

    The technical support is very good. 

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    I used PingID when working for another organization, which is slightly different from Microsoft Authenticator.

    How was the initial setup?

    I wasn't involved in the initial setup, but the solution is straightforward to use once installed. 

    The solution requires a little maintenance, as we sometimes encounter bugs where the app doesn't recognize a user account, for example.

    What's my experience with pricing, setup cost, and licensing?

    I am not involved in the pricing or licensing, so I can't speak to that. 

    What other advice do I have?

    I would rate the solution a 10 out of 10.

    I would advise potential users to familiarize themselves with the basics of the solution; how to set up an account, how to use the app etc. It's always a good idea to have a clear reason for using a particular solution, how it functions, and what role it fulfills.

    Which deployment model are you using for this solution?

    Hybrid Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Joao Carraca - PeerSpot reviewer
    Responsible Systems at Fnac
    Real User
    Top 20
    Easy to install, quick to deploy, and secure
    Pros and Cons
    • "It offers good Microsoft integration capabilities."
    • "The pricing is okay, however, it could always be better in the future."

    What is our primary use case?

    Microsoft Authenticator is the tool provided to assure that we are using the Microsoft product in the correct way, from the Microsoft point of view.

    What is most valuable?

    It's two-factor authentication. I personally use several of them, from Google to Microsoft Authenticator to others. It's a solution that works.

    The solution is stable. 

    The product is easy to install and quick to deploy.

    The solution is secure.

    It offers good Microsoft integration capabilities. 

    What needs improvement?

    For the moment, I don't have any complaints. 

    The pricing is okay, however, it could always be better in the future.

    What do I think about the stability of the solution?

    It is a stable, reliable product. There are no bugs or glitches. It doesn't crash or freeze. 

    What do I think about the scalability of the solution?

    In terms of scalability, we don't have complaints about this from the users of this kind of solution.

    Several people in our company use the product. I am unsure of the exact number. 

    How are customer service and support?

    When we have problems, we don't go to Microsoft; we complain internally to a group that is responsible for keeping this working. I can't speak to how Microsoft's support is. I've never directly interacted with them.

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    I also use Google Authenticator.

    I need to use different services to log on. Microsoft promotes its own solutions. For my bank, for instance, I have a solution imposed by my bank. For Google, I have Google Authenticator. For Microsoft Plus. I have Microsoft Authenticator. For our VPN, we use FortiGate, the authenticator.

    How was the initial setup?

    The installation is easy. You can do the installation on mobile phones and it can be installed on the web. It's not a problem.

    The deployment is fast and only takes about two minutes. It's supposed to be done by the end-user.

    What about the implementation team?

    I have done the implementation myself. I did not need the assistance of any integrators or consultants.

    What's my experience with pricing, setup cost, and licensing?

    I don't pay a separate licensing fee. It's already included in the service we buy from Microsoft.

    I'd rate the solution an eight out of ten.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Senior IT Manager at Excelra
    Real User
    Top 5Leaderboard
    Stable, easy to set up, and useful for people who travel a lot
    Pros and Cons
    • "It has been stable, and we haven't had any issues since we started to use it."
    • "Microsoft Authenticator is as easy as Google Authenticator, but it is not open to all types of applications. Google Authenticator is integrated with other third-party platforms and applications, whereas Microsoft Authenticator is not. It should have more integration with third-party platforms and applications."

    What is our primary use case?

    We use Microsoft Authenticator as well as Microsoft SMS Authenticator. Normally, we enable MFA for all users who have email access and application access. Users can choose which authenticator they want to use. Based on their convenience, they enable Microsoft Authenticator or Microsoft SMS Authenticator. Almost 80% to 90% of users use Microsoft SMS Authenticator. Users who travel a lot choose Microsoft Authenticator. 

    We are using the latest version. It is updated by default, and we don't have to update the application. It is also automatically updated on mobile.

    What is most valuable?

    It has been stable, and we haven't had any issues since we started to use it. 

    What needs improvement?

    Microsoft Authenticator is as easy as Google Authenticator, but it is not open to all types of applications. Google Authenticator is integrated with other third-party platforms and applications, whereas Microsoft Authenticator is not. It should have more integration with third-party platforms and applications.

    For how long have I used the solution?

    I have been using this solution for the last two years.

    What do I think about the stability of the solution?

    It is stable.

    How are customer service and technical support?

    We didn't have any issues or concerns. Therefore, we have never raised a ticket for Microsoft Authenticator.

    How was the initial setup?

    The initial setup is very easy. You have to enable MFA on the portal for a user, and you have to put the user's phone number. The user can then log in with Azure ID. The user is redirected to the second level of code authenticator and receives an SMS on the mobile. The user needs to enter the OTP.

    What's my experience with pricing, setup cost, and licensing?

    It comes free with the Microsoft account. We have a yearly agreement, and all products are covered under it.

    What other advice do I have?

    We will keep using Microsoft Authenticator as a secondary solution. We prefer Microsoft SMS Authenticator over Microsoft Authenticator. 

    I would recommend this solution to others. I would rate Microsoft Authenticator a nine out of ten.

    Which deployment model are you using for this solution?

    Private Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Buyer's Guide
    Download our free Microsoft Authenticator Report and get advice and tips from experienced pros sharing their opinions.
    Updated: November 2022
    Product Categories
    Authentication Systems
    Buyer's Guide
    Download our free Microsoft Authenticator Report and get advice and tips from experienced pros sharing their opinions.