some changes

Author: lucciz01

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

@@ -1,30 +1,34 @@
 ---
-title: Cannot establish trust relationship for the SSL/TLS secure channel
-description: Provides a resolution for the error in Power Automate for desktop, stating that you can't establish a trust relationship for the SSL/TLS secure channel.
+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/05/2025
-ms.custom: sap:Desktop flows\Power Automate for desktop errors
+ms.date: 05/06/2025
+ms.custom: sap:Desktop flows\PAD Runtime - Action execution (not browser or UI)
 ---
-# Cannot establish trust relationship for the SSL/TLS secure channel
+# "Could not establish trust relationship for the SSL/TLS secure channel" error
 
-This article provides a resolution for the error in Power Automate for desktop, stating that you can't establish a trust relationship for the SSL/TLS secure channel.
+This article provides a workaround for resolving the "Could not establish trust relationship for the SSL/TLS secure channel" error in Power Automate for desktop.
 
-_Applies to:_   Power Automate  
+_Applies to:_   Power Automate for desktop version 2.35 or later  
 
 ## Symptoms
-- An action in Power Automate for desktop, such as 'Invoke web service' or 'Get password from CyberArk', fails at runtime with the following error:
-  - "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 some cases, it is observed that a tool to inspect network traffic (e.g., Fiddler) may be installed on the computer.
 
-## Applies to
-PAD v2.35 or higher
+Actions in Power Automate for desktop, like [Invoke web service](/power-automate/desktop-flows/actions-reference/web#invokewebservicebase), or [Get password from CyberArk](/power-automate/desktop-flows/actions-reference/cyberark#getpasswordbase), might fail during runtime with the following error:
+
+  > 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.
 
 ## Cause
-Power Automate for desktop (PAD) checks whether "https" certificates are revoked or invalid. If a certificate in the chain is revoked or invalid, an error message appears. 
 
-Companies that use package inspection to audit their network infrastructure may not allow users to sign in, as their Certificate Revocation List (CRL) may not have been defined or is unreachable. 
+Power Automate for desktop validates the status of HTTPS certificates to check their validity, including whether they're revoked or invalid. This error might occur under the following conditions:
+
+1. A certificate in the chain has been revoked or marked as invalid.
 
-If Fiddler or a similar tool is installed, it may also install a self-signed certificate whose revocation status is "Unknown". Therefore, the error message is displayed if the relevant registry key is set to "Comprehensive".
+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, which displays a revocation status of **Unknown**. Therefore, when the registry key is set to **Comprehensive**, the error might occur.
 
 ## Workaround
-To allow users with invalid certificates to use that action, follow the instructions [here.](https://learn.microsoft.com/power-automate/desktop-flows/governance#configure-power-automate-for-desktop-to-check-for-revoked-certificates)
+
+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).

support/power-platform/power-automate/toc.yml

@@ -130,8 +130,8 @@
       href: desktop-flows/enable-webview-pad-login.md
     - name: Can't access the parent flow
       href: desktop-flows/cannot-access-parent-flow.md
-    - name: Can't establish trust relationship for the SSL/TLS secure channel
-      href: desktop-flows/cannot-establishing-trust-relationship-SSL-TLS.md
+    - name: '"Could not establish trust relationship for the SSL/TLS secure channel" error'
+      href: desktop-flows/could-not-establish-trust-relationship-ssl-tls-secure-channel.md
     - name: Can't interact with desktop application without an error
       href: desktop-flows/cannot-interact-with-desktop-application.md
     - name: Can't create, edit, save, or view desktop flows