Hi,

it’s recommended to use modern auth but you can use modern or basic auth. Basic auth requires a teams license to back it up.

Modern auth doesn’t quite support everything that basic auth does, the list of restrictions is here: https://www.veeam.com/kb3146

Basic auth is being retired by Microsoft this year so unless you really need a basic auth based feature, use modern auth.

Hi @MicoolPaul 

please confirm can we use 0365 globle admin with read only premission to take backup for whole 0365 backup.

False, you don’t need Global admin, read this:

https://helpcenter.veeam.com/docs/vbo365/guide/permissions_veeam_backup_account.html?ver=60

Hi @MicoolPaul 

i have add the permission on user as mention the documentation but still facing problem.

https://helpcenter.veeam.com/docs/vbo365/guide/ad_app_permissions_legacy.html?ver=60

What’s the error? Will help point out where it’s going

permission on azure portal-

That top error looks like your auth settings are wrong.

Did you choose Modern Auth or Modern auth with legacy auth?

its second one-

Modern auth with legacy auth

That second options requires a client application to already exist, did you create one manually? If not run through the modern auth only option and let it create your application, then swap to modern + legacy.

i already create one app permission and give the all required rights as per documentations 

Your application certificate or credentials look wrong based on the error in the screenshot, now you’ve given me all that detail I suggest checking your application ID & secret are correct

ok--

Veeam app
Application (client) ID: APPIDXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX 

secret-SECRETXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

Hi @Gopal Singh I wouldn’t recommend publishing that information, @Kseniya could help redacting this information hopefully.

But I mean you need to review if that information is correct as it’s specific to YOUR environment. The error you got AADSTS7000215 means invalid secret provided. So either your secret is incorrect or your Application ID is wrong.

If these are correct you may have some form of policy on your Azure AD preventing authentication and you’d have to explore those logs.

Hi @MicoolPaul  - which information you would like me to redact? please, advise - I am happy to help 

I think @Gopal Singh ‘s application id and secret in the topic above

@Kseniya could we modify to the above please. Gets the idea across without accidental data leakage. Thank you as always!

Ah, I missed this somehow! Modified 

thanks all for your support.

one more qus while restoring my mail contacts