Skip to main content
Solved

Veeam m365 backup to Azure blob storage jobs all suddenly failing

  • November 7, 2025
  • 4 comments
  • 43 views

  • New Here
  • 1 comment

Since yesterday all our existing configured backup jobs to Azure Blob storage are failing and attempts to create new object storage repository are failing on Validating Credentials.  Error: Unable to access object storage (reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (xstorageaccountnamex.blob.core.windows.net:443))

Any ideas?  I’ve tried rotating the access key in Azure and updating that in the Cloud account in Veeam m365 backup.  This has started to occur a week after upgrading to v8 which was ok initially.

Best answer by Chris.Childerhose

What version as you using for VB365 as there is some new patches out recently?  Did you check the logs here C:\ProgramData\Veeam\Backup365

The logs are here and you may need to open a case with support.

4 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 9587 comments
  • Answer
  • November 7, 2025

What version as you using for VB365 as there is some new patches out recently?  Did you check the logs here C:\ProgramData\Veeam\Backup365

The logs are here and you may need to open a case with support.


regnor
Forum|alt.badge.img+14
  • Veeam MVP
  • 1387 comments
  • November 7, 2025

Hi ​@DomR!

As the connection to the block storages times out, I would suggest to start with basic troubleshooting. Are you able to access the internet from your VB365 server/proxy?

Make sure there’s no firewall or proxy preventing or intercepting the connection to the storage account. 

Also try to access it via a web browser and check if you’re seeing any errors; especially certificate or connection errors.

 


  • Author
  • New Here
  • 1 comment
  • November 10, 2025

Thanks for the pointers guys.  Despite only upgrading the server to the latest Veeam version 8.2.0.2008 a week prior, I updated again to 8.2.0.2202 re-applied the license rebooted the entire server again and we seem to have success (so far!).


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 9587 comments
  • November 10, 2025

Great!  Glad to hear you are working again.