Merge pull request #245283 from omondiatieno/enforce-signed-sam

reviewed article for freshness-enforce signed SAML signature verification

Author: prmerger-automator[bot]

articles/active-directory/manage-apps/howto-enforce-signed-saml-authentication.md

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.subservice: app-mgmt 
 ms.workload: identity 
 ms.topic: conceptual 
-ms.date: 06/29/2022 
+ms.date: 07/18/2023
 ms.author: jomondi
 ms.reviewer: alamaral
 ms.collection: M365-identity-device-management
@@ -24,11 +24,11 @@ If enabled Azure Active Directory will validate the requests against the public
 
 - Protocol not allowed for signed requests. Only SAML protocol is supported.  
 - Request not signed, but verification is enabled.  
-- No verification certificate configured for SAML request signature verification.  
+- No verification certificate configured for SAML request signature verification. For more information about the certificate requirements, see [Certificate signing options](certificate-signing-options.md).
 - Signature verification failed.  
 - Key identifier in request is missing and two most recently added certificates don't match with the request signature.  
 - Request signed but algorithm missing.  
-- No certificate matching with provided key identifier.  
+- No certificate matching with provided key identifier.
 - Signature algorithm not allowed. Only RSA-SHA256 is supported.
 
 > [!NOTE]