From 7183c615911842a6dd96b8a45b1f1030c3691f25 Mon Sep 17 00:00:00 2001
From: alons8 <61512160+alons8@users.noreply.github.com>
Date: Thu, 26 Nov 2020 14:55:45 +0200
Subject: [PATCH] Update indicator-certificates.md

Adjusting the requirements for specific encoding based certificates types.
---
 .../microsoft-defender-atp/indicator-certificates.md            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/threat-protection/microsoft-defender-atp/indicator-certificates.md b/windows/security/threat-protection/microsoft-defender-atp/indicator-certificates.md
index feab52dd1a..6948f7a392 100644
--- a/windows/security/threat-protection/microsoft-defender-atp/indicator-certificates.md
+++ b/windows/security/threat-protection/microsoft-defender-atp/indicator-certificates.md
@@ -43,7 +43,7 @@ It's important to understand the following requirements prior to creating indica
 - The Antimalware client version must be  4.18.1901.x or later.
 - Supported on machines on Windows 10, version 1703 or later, Windows server 2016 and 2019.
 - The virus and threat protection definitions must be up-to-date.
-- This feature currently supports entering .CER or .PEM file extensions.
+- This feature currently supports entering .CER or .PEM (Base64 ASCII) encoding based certificates.
 
 >[!IMPORTANT]
 > - A valid leaf certificate is a signing certificate that has a valid certification path and must be chained to the Root Certificate Authority (CA) trusted by Microsoft.  Alternatively, a custom (self-signed) certificate can be used as long as it's trusted by the client (Root CA certificate is installed under the Local Machine 'Trusted Root Certification Authorities').