From f4eeda69f9d43d9d6f033ec0221a4d41e6ce6ce6 Mon Sep 17 00:00:00 2001 From: Ben Alfasi Date: Tue, 12 Mar 2019 11:19:17 +0200 Subject: [PATCH] s --- .../threat-protection/windows-defender-atp/apis-intro.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/security/threat-protection/windows-defender-atp/apis-intro.md b/windows/security/threat-protection/windows-defender-atp/apis-intro.md index 653bfa951a..e2e8feec5d 100644 --- a/windows/security/threat-protection/windows-defender-atp/apis-intro.md +++ b/windows/security/threat-protection/windows-defender-atp/apis-intro.md @@ -39,12 +39,14 @@ You can access Windows Defender ATP API with **Application Context** or **User C - **Application Context:**
Used by apps that run without a signed-in user present. for example, apps that run as background services or daemons. + Steps that needs to be taken to access Windows Defender ATP API with application context: 1) Create AAD Web-Application. 2) Assign the desired permission to the application, e.g 'Read Alerts', 'Isolate Machines' etc. 3) Create a key for this Application. 4) Get token using the application with its key. 5) Use the token to access Windows Defender ATP API + See - [Get access with application context](exposed-apis-create-app-webapp.md).