Automation Account Powershell - The request was aborted: Could not create SSL/TLS secure channel.

Ray 20

An Azure automation account PowerShell script began failing suddenly with the

error = The request was aborted: Could not create SSL/TLS secure channel.

The below code was added but the issue persists, is there some way to set this property or update the modules on the automation account?

Faced the same issue on my PC but upgrading the .net version fixed the issue.

[System.Net.WebRequest]::DefaultWebProxy.Credentials = [System.Net.CredentialCache]::DefaultCredentials
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

Rahul Podila 1,485 Reputation points Microsoft Vendor

2025-01-22T01:18:21.7866667+00:00

Hi @Ray

Thanks for posting your query and using Microsoft Q&A Forum,

We are checking with our internal team to get more information related to your query and will get back to you as soon as once we have an update.
Naveena Patlolla 5 Reputation points Microsoft Vendor

2025-01-22T04:12:06.7233333+00:00

Hi @Ray

Yes, as you mentioned, this issue is related to the TLS/SSL security problem. Adding the two lines on your PC resolved the issue because your system is managed by you. However, the automation account runs on a server managed by Microsoft, so I’m currently exploring how to execute these commands on that server. Please allow me some time to work on a solution from my end.
Ray 20 Reputation points

2025-01-22T05:02:27.45+00:00

Thank You all,
Just to clarify adding those 2 lines did not resolve the issue on my local pc but updating the .net version did resolve it.

Postman and other services are able to communicate with the server only the automation account started having an issue since about a week.
Naveena Patlolla 5 Reputation points Microsoft Vendor

2025-01-22T07:02:48.8933333+00:00
Hi @Ray,

Thanks for sharing your inputs,

I agree with you that the issue is occurring Most likely due to TLS, and the steps you have performed are correct.

The script works on your local machine because you have full control over your laptop's environment. However, in the Azure Automation account, it is failing even after adding:

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

This happens because the script is running on one of Azure's build servers, where we may not have full control over the runtime environment.

To confirm whether this issue is specific to all Azure services you are accessing or only to a particular service, could you please try the following two solutions and share the output?

Solution 1:
Create a New Runbook: -

Use Runtime version 7.2 for the runbook if you are using 5.1 Version or if you are using 7.2 version Run with 5.1 version try doing with both ways.

Refer below screenshot: -

Run your script in this environment by adding line and check if it resolves the issue.

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

If the First Solution Fails, follow second

Solution 2:

Create another runbook with Runtime version 7.2.

Try to execute the following command to retrieve VM details:

Add this code to the Runbook followed by your Login Method

Get-AzVM -ResourceGroupName "YourRGName" -Name "YourVMName"

Please let me know the results of these tests so we can proceed further!

Thankyou
Ray 20 Reputation points

2025-01-22T07:36:08.48+00:00
FYI the below in 5.1 Version of PowerShell runtime
The below does not work, it cant set Tls13 as thats the one the server is using
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls13
Error =
Exception setting "SecurityProtocol": "Cannot convert null to type "System.Net.SecurityProtocolType" due to enumeration values that are not valid. Specify one of the following enumeration values and try again. The possible enumeration values are "SystemDefault,Ssl3,Tls,Tls11,Tls12"." At line:3 char:1 + [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.Secu ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], SetValueInvocationException + FullyQualifiedErrorId : ExceptionWhenSetting

2)

Selected 7.2 Version of PowerShell runtime

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 added

it gave the error The SSL connection could not be established, see inner exception.

and same for tls3

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls13

added

error = The SSL connection could not be established, see inner exception.

Invoke-RestMethod: Line | 21 | … $response = Invoke-RestMethod $login_API -Method 'POST' -Headers $hea … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion'.

4)..The server i am trying to connect to is using tls3

5)... For solution 2 I am not using Hybrid Worker so not sure what to put in VM name
Naveena Patlolla 5 Reputation points Microsoft Vendor

2025-01-22T14:49:59.8066667+00:00

Hi @Ray,

Thanks for sharing your information.

Also please consider the below points and let me know how it goes:

1.We have tried all possible ways and found that Automation Account Managed by Azure will have limited scope for TLS version1.3.

2.We don’t have full control over Automation Account Managed by Azure.

3.As per the Microsoft, the recommended approach is to use a Hybrid Runbook Worker, as it provides full control, and this will fix your problem.

Let us know if you have any further queries. I’m happy to assist you further.

Please refer the below Microsoft links which will guide you to the right path

Refer: https://learn.microsoft.com/en-us/azure/automation/automation-hybrid-runbook-worker

https://learn.microsoft.com/en-us/system-center/scom/plan-security-tls12-config?view=sc-om-2025#configure-windows-operating-system-to-only-use-tls-12-protocol
Naveena Patlolla 5 Reputation points Microsoft Vendor

2025-01-23T13:36:44.9966667+00:00

Hi @Ray,
Just want to check if the above Comment worked for you or else please let us know if any help, we are always here to help whenever you need us.

If the comment is helpful, please click "Upvote it"

Thankyou
Naveena Patlolla 5 Reputation points Microsoft Vendor

2025-01-24T05:26:19.94+00:00

Hi @Ray,
Just want to check if the above Comment worked for you or else please let us know if any help, we are always here to help whenever you need us.

If the comment is helpful, please click "Upvote it"

Thankyou
Ray 20 Reputation points

2025-01-24T10:00:34.9733333+00:00

Thank you very much Naveena for your response,

The reason I choose the Automation Account over a Hybrid Worker setup is due to its simplicity and resource independence.

Since no VMs are available for me, leveraging an Automation Account avoids the need for additional infrastructure and gives a straightforward approach to executing automation tasks, and these tasks can be triggered directly without the overhead of managing other resources.
Ray 20 Reputation points

2025-01-24T10:00:41.5+00:00

Hi Naveena, all,

Thank You for assistance and guidance on the issue.

After raising a ticket to Microsoft they Confirmed the tls3 issues on all Ps runtime versions and suggested I use runtime version 7.4 since I cant use the hybrid worker option.

And using 7.4 Version resolved the issue.

Accepted answer

Rahul Podila 1,485 Reputation points Microsoft Vendor

2025-01-24T16:16:22.37+00:00

Hi @Ray

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

Issue:

Automation Account Powershell - The request was aborted: Could not create SSL/TLS secure channel.

Solution:

Due to TLS 3 issues with all PS runtime versions and the inability to use the hybrid worker option, switching to runtime version 7.4 resolved the issue.

If you have any other questions or are still running into more issues, please let me know. Thank you again for your time and patience throughout this issue.

Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

https://learn.microsoft.com/en-us/answers/support/accept-answer#why-only-one-accepted-answer
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Automation Account Powershell - The request was aborted: Could not create SSL/TLS secure channel.

0 additional answers

Your answer