Skip to content

Commit 2fe7d98

Browse files
authored
Merge pull request #190343 from MarkusVi/rec05
rec05
2 parents e325345 + dc8b0e3 commit 2fe7d98

File tree

2 files changed

+63
-0
lines changed

2 files changed

+63
-0
lines changed
Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
title: Azure Active Directory recommendation - Migrate to Microsoft authenticator | Microsoft Docs
3+
description: Learn why you should migrate your users to the Microsoft authenticator app in Azure AD.
4+
services: active-directory
5+
documentationcenter: ''
6+
author: MarkusVi
7+
manager: karenhoran
8+
editor: ''
9+
10+
ms.assetid: 9b88958d-94a2-4f4b-a18c-616f0617a24e
11+
ms.service: active-directory
12+
ms.topic: reference
13+
ms.tgt_pltfrm: na
14+
ms.workload: identity
15+
ms.subservice: report-monitor
16+
ms.date: 03/02/2022
17+
ms.author: markvi
18+
ms.reviewer: hafowler
19+
20+
ms.collection: M365-identity-device-management
21+
---
22+
23+
# Azure AD recommendation: Migrate to Microsoft authenticator
24+
25+
[Azure AD recommendations](overview-recommendations.md) is a feature that provides you with personalized insights and actionable guidance to align your tenant with recommended best practices.
26+
27+
This article covers the recommendation to migrate users to authenticator.
28+
29+
30+
## Description
31+
32+
Multi-factor authentication (MFA) is a key component to improve the security posture of your Azure AD tenant. However, while keeping your tenant safe is important, you should also keep an eye on keeping the security related overhead as little as possible on your users.
33+
34+
One possibility to accomplish this goal is to migrate users using SMS or voice call for MFA to use the Microsoft authenticator app.
35+
36+
37+
## Logic
38+
39+
If Azure AD detects that your tenant has users authenticating using SMS or voice in the past week instead of the authenticator app, this recommendation shows up.
40+
41+
## Value
42+
43+
- Push notifications through the Microsoft authenticator app provide the least intrusive MFA experience for users. This is the most reliable and secure option because it relies on a data connection rather than telephony.
44+
- Verification code option using Microsoft authenticator app enables MFA even in isolated environments without data or cellular signals where SMS and Voice calls would not work.
45+
- The Microsoft authenticator app is available for Android and iOS.
46+
- Pathway to passwordless: Authenticator can be a traditional MFA factor (one-time passcodes, push notification) and when your organization is ready for Password-less, the authenticator app can be used sign-into Azure AD without a password.
47+
48+
## Action plan
49+
50+
1. Ensure that notification through mobile app and/or verification code from mobile app are available to users as authentication methods. How to Configure Verification Options
51+
52+
2. Educate users on how to add a work or school account.
53+
54+
55+
56+
57+
58+
## Next steps
59+
60+
- [Tutorials for integrating SaaS applications with Azure Active Directory](../saas-apps/tutorial-list.md)
61+
- [Azure AD reports overview](overview-reports.md)

articles/active-directory/reports-monitoring/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -136,3 +136,5 @@
136136
items:
137137
- name: Integrate your third party apps
138138
href: recommendation-integrate-third-party-apps.md
139+
- name: Migrate to Microsoft authenticator
140+
href: recommendation-migrate-to-authenticator.md

0 commit comments

Comments
 (0)