Support Statement - Exchange Online Basic Authentication Deprecation

KB ID: 4365
Product: Veeam Backup for Microsoft 365 Community Edition
Veeam Backup for Microsoft 365
Published: 2022-09-30
Last Modified: 2022-10-19
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Purpose

This article provides information on actions that must be taken to ensure Veeam Backup for Microsoft 365 will continue to function after the Basic Authentication Deprecation in Exchange Online.
Associated Error Messages

The following errors may be shown in Veeam Backup for Microsoft 365 configurations that were not updated to account for Microsoft's depreciation of Basic Authentication:

  • Warning: The request failed with HTTP status 401

Required Actions

Organizations added to Veeam Backup for Microsoft 365 using either Basic Authentication or Modern Authentication with Legacy Protocols, must be switched to Modern App-Only Authentication.
The two configurations shown in the screenshots below will no longer function after Basic Authentication is deprecated.
Basic Authentication
Basic Authentication
Modern Auth with Allow Legacy Protocols enabled
Modern Authentication with Allow Legacy Protocols enabled
Switch to Modern App-Only Authentication

To continue protecting the Organization's Microsoft 365 environment after Basic Authentication is deprecated, the authentication method used by Veeam Backup for Microsoft 365 to connect to the environment must be set to Modern authentication.

To change the organization's authentication within Veeam Backup for Microsoft 365:
  1. Select the Organization and Click Edit
  2. On the "Microsoft 365 connection settings" page of the wizard, select the option for "Modern authentication"
    Do not select the option labeled "Allow for using legacy authentication protocols"
  3. Proceed through the rest of the wizard steps.
    Reference: Select Azure Region and Authentication Method

 

Required Permissions
SharePoint/OneDrive Sites

When using Modern App-Only Authentication, Veeam Backup for Microsoft 365 utilizes custom scripting to process web parts of SharePoint/OneDrive sites. To prevent issues processing WebParts, review and implement the solution documented in KB4091.

Limitations

As documented in KB3146: Veeam Backup for Microsoft 365 Modern App-Only Authentication Limitations, it is not possible to back up public folders using Modern App-Only Authentication. As an alternative to Public Folders, Microsoft recommends using Microsoft 365 Groups. Information about migrating can be found in Migrate your public folders to Microsoft 365 Groups in Exchange Online.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.