You can set multi-factor authentication within your applications and different platforms. Our applications are on the cloud, and we provide authentication to different user bases so that only particular groups and URLs can be accessed by certain users. The users get notifications to verify and validate their identity during the sign-on process when they log into the applications from the web. We have an on-premises and hybrid deployment model. Microsoft and AWS are our cloud providers. Microsoft Authenticator is deployed across multiple geographic locations including the Asia-Pacific region and EMEA.
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.
Jr. System Admin at a tech services company with 5,001-10,000 employees
MSP
2022-09-21T07:13:00Z
Sep 21, 2022
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.
Microsoft Teams Senior Engineer at a financial services firm with 10,001+ employees
Real User
2022-09-03T20:37:00Z
Sep 3, 2022
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.
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.
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.
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.
Microsoft Entra ID is used for extending on-premises Active Directory to the cloud, managing application access, enabling multi-factor authentication, and single sign-on. It facilitates policy enforcement and secure access, ensuring centralized identity management across cloud and on-premises resources.
Organizations utilize Microsoft Entra ID for robust user and group management, identity synchronization, and conditional access. Its seamless integration with third-party apps,...
You can set multi-factor authentication within your applications and different platforms. Our applications are on the cloud, and we provide authentication to different user bases so that only particular groups and URLs can be accessed by certain users. The users get notifications to verify and validate their identity during the sign-on process when they log into the applications from the web. We have an on-premises and hybrid deployment model. Microsoft and AWS are our cloud providers. Microsoft Authenticator is deployed across multiple geographic locations including the Asia-Pacific region and EMEA.
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.
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.
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.
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.
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.
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.
I use Authenticator across my company for controlling access to our platforms and data.
My primary use case is to access our company resources. I'm a solution architect and we are customers of Authenticator.
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.