From 110fde119b8b867ef4377208971302d7724a28f0 Mon Sep 17 00:00:00 2001 From: jcaparas Date: Wed, 8 Mar 2017 21:53:25 -0800 Subject: [PATCH] flow --- .../generic-api-windows-defender-advanced-threat-protection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/keep-secure/generic-api-windows-defender-advanced-threat-protection.md b/windows/keep-secure/generic-api-windows-defender-advanced-threat-protection.md index acfa5409fc..cbe762aee8 100644 --- a/windows/keep-secure/generic-api-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/generic-api-windows-defender-advanced-threat-protection.md @@ -23,7 +23,7 @@ localizationpriority: high Windows Defender ATP uses the OAuth 2.0 protocol with the Azure Active Directory (AAD) as the authorization server to obtain limited access, so that alerts can be consumed by supported security information and event management (SIEM) tools (such as Splunk and HP ArcSight) and generic APIs. -In general, the OAuth 2.0 protocol supports four types of authentication flows: +In general, the OAuth 2.0 protocol supports four types of flows: - Authorization code flow - Implicit flow - Client credentials flow