VBO365 - Disable Basic Auth in M365 per Oct. 1, 2022



Show first post

28 comments

Hi,

 

I upgraded Veeam O365 from v5. to the latest version 6.1.0254 last week. And now i got the assignment to make sure we are on Modern Authentication or if not, make a change with the steps to get there.

 

I know i created a new App Registration with Microsoft Graph User.Read rights during the upgrade of Veeam.

I also noticed in the Sign-in Logs in Azure AD we still get Legacy Authentication Clients logins from Veeam. They are comming from the Veeam Auxiliary accounts we are using for spreading the load (i have been told).

2 Questions:

What should i do? Or where can i find how to do this?

How can i make us Modern Authentication-proof? And please some steps from the point of using Veeam o365 already and not from a new Veeam o365 installation

If you check the help here - Adding Organizations with Modern App-Only Authentication - Veeam Backup for Microsoft 365 Guide

This outlines adding Modern Auth to a new tenant but all you need to do is edit your existing Tenant(s) and change the authentication method.  Hopefully this helps.

Hi Chris,

 

Thank you very much, and not to be ungratefull but that is what i already found in this topic, but it is exactly that " … all you need to do is edit your existing tenant and change the authentication method.” what is making me unsure, because what needs to be edit when you have an existing situation and what is only for new situations? I can't risk having it goes wrong because i didn't filter it the right way. I don't understand why there is no manual for changing an existing situation and how it should look like in the end. That is where i need a little help.

Also on the Veeam Auxiliary accounts, where it looks like they make use of the basic Authentication. How do i change that?

 

Userlevel 7
Badge +8

Hi,

 

I upgraded Veeam O365 from v5. to the latest version 6.1.0254 last week. And now i got the assignment to make sure we are on Modern Authentication or if not, make a change with the steps to get there.

 

I know i created a new App Registration with Microsoft Graph User.Read rights during the upgrade of Veeam.

I also noticed in the Sign-in Logs in Azure AD we still get Legacy Authentication Clients logins from Veeam. They are comming from the Veeam Auxiliary accounts we are using for spreading the load (i have been told).

2 Questions:

What should i do? Or where can i find how to do this?

How can i make us Modern Authentication-proof? And please some steps from the point of using Veeam o365 already and not from a new Veeam o365 installation

If you check the help here - Adding Organizations with Modern App-Only Authentication - Veeam Backup for Microsoft 365 Guide

This outlines adding Modern Auth to a new tenant but all you need to do is edit your existing Tenant(s) and change the authentication method.  Hopefully this helps.

Hi Chris,

 

Thank you very much, and not to be ungratefull but that is what i already found in this topic, but it is exactly that " … all you need to do is edit your existing tenant and change the authentication method.” what is making me unsure, because what needs to be edit when you have an existing situation and what is only for new situations? I can't risk having it goes wrong because i didn't filter it the right way. I don't understand why there is no manual for changing an existing situation and how it should look like in the end. That is where i need a little help.

Also on the Veeam Auxiliary accounts, where it looks like they make use of the basic Authentication. How do i change that?

 

If you have a new Organization - you simply select Modern Authentication when setting it up in VBM365.

If you have an existing Organization - you edit the properties of that ORG and you can then change the authentication method to Modern from Basic.  This will then proceed to use the Modern Authentication method.

The Auxiliary accounts question - you need to determine which Organization you set those up with and that will tell you where the Basic Authentication is being used.  You can then modify it to Modern Auth.

Hope this helps and feel free to post back with further questions. 👍🏼

Userlevel 7
Badge +8

Here we are! 1st October.

 

I want to remind everyone that this now needs to be part of your troubleshooting workflows. Microsoft have published this for guidance around troubleshooting:

https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-email-applications-stopped-signing-in-or-keep/ba-p/3641943

Comment