Skip to content

Commit a04012c

Browse files
author
Markus Vilcinskas
committed
wblegauth03
1 parent c6bf630 commit a04012c

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/active-directory/reports-monitoring/workbook-legacy authentication.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -97,8 +97,7 @@ This workbook supports multiple filters:
9797

9898
- Many email protocols that once relied on legacy authentication now support more secure modern authentication methods. If you see legacy email authentication protocols in this workbook, consider migrating to modern authentication for email instead. For more information, see [Deprecation of Basic authentication in Exchange Online](https://docs.microsoft.com/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online).
9999

100-
101-
100+
- Some clients can use both legacy authentication or modern authentication depending on client configuration. If you see “modern mobile/desktop client” or “browser” for a client in the Azure AD logs, it is using modern authentication. If it has a specific client or protocol name, such as “Exchange ActiveSync”, it is using legacy authentication to connect to Azure AD. The client types in conditional access, and the Azure AD reporting page in the Azure Portal demarcate modern authentication clients and legacy authentication clients for you, and only legacy authentication is captured in this workbook.
102101

103102

104103
## Next steps

0 commit comments

Comments
 (0)