Veeam Agent notifications TLS 1.2 Support for Office365

[Luther T]

I currently have a couple of Veeam Agent for windows performing some basic backups an sending a notification of results using SMTP to a ofifce365 account. This is working just fine however when checking ofifce365 mail flow, I see that it is using TLS 1.0 exclusively.

Microsoft will be disable support of TLS 1.0 and 1.1 in June of 2020 so any communication that does not support TLS 1.2 will fail after that date.
My question here is does the Agent for Microsoft windows support TLS 1.2? I do not see any GUI controls that specify one TLS version of another and have not been able to find any reference to this yet.

Here are my current settings for reference:
SMTP SERVER: smtp.office365.com
Port: 587
Use secure connection (SSL/TLS) is checked

I am trying to verify functionality before they disable the older versions.

[Dima P.]

Hello Luther,

Can you please raise a support case and share the case ID with me. I'll ask QA folks to investigate it. Thank you in advance!

[Luther T]

Case #04073488

[HannesK]

Hello,
we use .NET version 4.5 which support TLS 1.2. So we do not expect any issues when Microsoft deactivates TLS 1.0 and 1.1

Best regards,
Hannes

[cielostarNA]

Hey all, I am trying to move our entire environment to TLS 1.2 and Veeam cannot get updates or send backup notifications from within Veeam Agent for Windows ver. 3 and 4 with TLS 1.0 turned off in Client and Server registry settings. Any idea how to force it to work?

Running in a Server 2012 R2 VM .NET 4.8 and all MS updates current as of today.

[Dima P.]

Hello Gregory,

We are currently investigating this issue, can you please raise a support ticket and share the logs with us? Thank you!

[cielostarNA]

Hello,

Sorry for the delay!
Case #04106794 created.
I do not have any logs to show you that I could find, so I included in the ticket a couple of images showing Nartac settings with the failure screen for update and the email test error on one of the Server 2012 R2 VM machines.

[Dima P.]

Gregory,

Thanks for sharing the case - passed it to the QA folks for the investigation!

[cielostarNA]

Hello,

I received a notification at 2:40pm today that my Case #04106794 was closed. The reason within the email notification stated as follows "This is Veeam Support with a system generated courtesy notification. Unfortunately, due to high Support Team load we were unable to process your request and it has been archived automatically."

Can you verify please if this is still being worked on and if there is any news on when it will be resolved?

[Dima P.]

Gregory,

QA team is still investigating the issue and I've asked support team to check your case and re-open it if needed. Cheers!

[Luther T]

it looks like MSFT has delayed its plans to decommission TLS 1.0/1.1 until after the covid situation.

https://docs.microsoft.com/en-us/office ... office-365


I note my case has been ignored for some time now but it appears this is being worked on elsewhere. I will keep my eye on this foum with the hopes that some info will appear here before it becomes an issue again.

thanks.

[cielostarNA]

Posting this here in case it helps anyone. I was contacted by a different rep working on my support ticket and they recommended the article below. I have implemented the registry changes, with my TLS settings set to 1.2 for both Client and Server communications, and it looks like this fixed things. I am now able to have Veeam check for updates and send out mail notifications once more.
https://www.veeam.com/kb2853