updates

Author: lucciz01

support/power-platform/power-automate/desktop-flows/could-not-establish-trust-relationship-ssl-tls-secure-channel.md

@@ -2,7 +2,7 @@
 title: Could Not Establish Trust Relationship for the SSL or TLS Secure Channel
 description: Provides a workaround to allow users with invalid certificates to use certain actions in Power Automate for desktop.
 ms.reviewer: nimoutzo
-ms.date: 05/13/2025
+ms.date: 05/15/2025
 ms.custom: sap:Desktop flows\PAD Runtime - Action execution (not browser or UI)
 ---
 # "Could not establish trust relationship for the SSL/TLS secure channel" error
@@ -17,7 +17,7 @@ Actions in Power Automate for desktop, like [Invoke web service](/power-automate
 
 > System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
 
-In certain cases, a network traffic inspection tool, such as Fiddler, might be installed on the computer.
+In some cases, the issue might occur when a network traffic inspection tool, such as Fiddler, is installed on the computer.
 
 ## Cause
 
@@ -27,8 +27,8 @@ Power Automate for desktop validates the status of HTTPS certificates to check t
 
 2. Companies that use package inspection to audit their network infrastructure might not allow users to sign in, as their Certificate Revocation List (CRL) might not have been defined or is unreachable.
 
-3. Tools like Fiddler might install a self-signed certificate on the system with an **Unknown** revocation status. Therefore, when the registry key is set to **Comprehensive**, the error might occur.
+3. Tools like Fiddler might install a self-signed certificate on the system with an Unknown revocation status. In such cases, if the [CertificateRevocationCheck](/power-automate/desktop-flows/governance#configure-power-automate-for-desktop-to-check-for-revoked-certificates) registry key is set to **Comprehensive**, Power Automate for desktop will reject the certificate and the error will be generated.
 
 ## Workaround
 
-Administrators can enable actions for users with invalid certificates by following the steps in [Configure Power Automate for desktop to check for revoked certificates](/power-automate/desktop-flows/governance#configure-power-automate-for-desktop-to-check-for-revoked-certificates).
+Administrators can allow users with invalid certificates to use these actions by following the steps in [Configure Power Automate for desktop to check for revoked certificates](/power-automate/desktop-flows/governance#configure-power-automate-for-desktop-to-check-for-revoked-certificates).