From 8735a59010cc2fccf0d21ffcccd0a3ba61c1eeff Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Thu, 16 Mar 2017 15:18:00 -0700 Subject: [PATCH] fix link --- ...ment-custom-ti-windows-defender-advanced-threat-protection.md | 1 + 1 file changed, 1 insertion(+) diff --git a/windows/keep-secure/experiment-custom-ti-windows-defender-advanced-threat-protection.md b/windows/keep-secure/experiment-custom-ti-windows-defender-advanced-threat-protection.md index 2aa8d53372..ff7fa5b330 100644 --- a/windows/keep-secure/experiment-custom-ti-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/experiment-custom-ti-windows-defender-advanced-threat-protection.md @@ -45,6 +45,7 @@ This step will guide you in creating an alert definition and an IOC for a malici >[!NOTE] >Make sure you replace the `authUrl`, `clientID`, and `clientSecret` values with your details which you saved in when you enabled the threat intelligence application. + [!code[ExampleScript](./code/example-script.ps1#L1-L60)] 3. Run the script and verify that the operation succeeded in the results the window. Wait up to 20 minutes until the new or updated alert definition propagates to the detection engines.