Error 403 access denied

[robnicholsonmalt]

I'm currently evaluating VOB with the latest version for a small client (<10 users). It's been working fine but I returned to the lab today and when I re-ran the job, it failed with access denied. All I'm backing up at the moment are some of the users. When I go through the connection again to check the password is right, it's reporting this:



The other checks verifying configuration and organization parameters pass okay except Check LegacyAuthProtocols:



I've run Get-SpoTenant and that reports this is enabled:



Some tenant level changes have been made recently: password expiry was enabled and MFA was turned on - but not for the global admin account been used for VOB. And the password works fine as the other checks would fail. The service account is a global administrator.

Any ideas?

[nielsengelen]

Hi, did you install the latest CP (available via https://www.veeam.com/kb4135)? If not, can u install it and see if the issue persists?

[rsardinha]

Hi, I had the same problem (started on 7th of May) and KB4135 worked for me.
Thanks.

[robnicholsonmalt]

Ahh... here's me thinking I'd broken something

[robnicholsonmalt]

Thanks sorted! How do you find out about these patches? I can't find a route/list to them on the Downloads area on the website?

[m.novelli]

I had the same issue on about 10 customers since about 7 May, KB4135 solved the issue
Thanks, ciao

[robnicholsonmalt]

Is there a mailing list for hotfixes? I'm doing a proof of concept so it was "just" an hour of my time wasted because I assume I'd broken it. If this had been a production system, it was potentially more embarrassing although we'd probably be on on a paid version and maybe you get more on that service. I do get the impression that VOB and M365 APIs are a bit of a moving target. My main client uses Veeam through iLand hosting and it's often breaking. Not blaming Veeam at all here but they do need to make sure that breaking changes are publicised.

[Mike Resseler]

There is not a mailing list at this point in time, but we do have an official KB on it:

See here: https://www.veeam.com/kb4106

[robnicholsonmalt]

Thanks - bookmarked!!

[zaickone]

KB4135 solved the issue
Thanks