I did have a case open on this Case #07924348, but ultimately its a office setting that I believe is messing us up and hoping someone here on the forums has dealt with it and has a solution.
Our company requires 2FA and I think that requirement is making Veeam unable to complete the connection, as my global admin isn't able to add the sign in as an exclusion for some reason for the azure CLI sign in. Any sign in attempts throws an error: AADSTS900561: The endpoint only accepts POST requests. Received a GET request.
-
techK
- Influencer
- Posts: 14
- Liked: 1 time
- Joined: Mar 30, 2022 1:39 am
- Contact:
-
MarkBoothmaa
- Service Provider
- Posts: 232
- Liked: 72 times
- Joined: Mar 22, 2017 11:10 am
- Full Name: Mark Boothman
- Location: Darlington, United Kingdom
- Contact:
Re: Can't connect veeam 365 to our organization
We have found that excluding the account from the devicecode CAP works. You have to wait for it to replicate.
-
techK
- Influencer
- Posts: 14
- Liked: 1 time
- Joined: Mar 30, 2022 1:39 am
- Contact:
Re: Can't connect veeam 365 to our organization
@markBoothmaa
So I would go into entra and into conditional access and make a new policy to target the global account account to approve the sign in? As I don't think editing any current policies work for our environment.
So I would go into entra and into conditional access and make a new policy to target the global account account to approve the sign in? As I don't think editing any current policies work for our environment.
Who is online
Users browsing this forum: No registered users and 22 guests