Support Statement — Microsoft 365 Changes to Throttling Enforcement

KB ID: 4821
Product: Veeam Data Cloud for Microsoft 365
Veeam Backup for Microsoft 365
Published: 2026-02-24
Last Modified: 2026-02-24
mailbox
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.

Support Statement

This article documents upcoming changes Microsoft is making to application throttling enforcement in Microsoft 365 environments and its potential impact on customers using Veeam Backup for Microsoft 365 and Veeam Data Cloud for Microsoft 365.

What's changing?

Microsoft has announced that, starting on March 1st, 2026, it will update its approach to application throttling enforcement for SharePoint Online and OneDrive. Teams may also be affected, as some of its data resides there.

What's behind this change?

Microsoft imposes connection limits per application within a tenant, based on the number of licenses. Functionally, each application registration has its own threshold before throttling kicks in. Once that limit is reached, Microsoft services such as SharePoint Online will return HTTP status code 429 ("Too many requests") or 503 ("Server Too Busy"), and the requests will fail. When this occurs, the application must wait before new requests can be made, slowing backups. To work around this and improve backup performance, many backup vendors have suggested deploying multiple applications.

However, according to Microsoft's terms of use and product documentation, creating separate application registrations when those applications essentially perform the same operations, such as backup, is not permitted. As of March 1st, 2026, Microsoft will enforce those terms of use for everyone who has configured multiple application registrations. It is important to note that this is not specific to Veeam's products; it affects all third-party backup vendors that use multiple application registrations to optimize backup performance.

What action should Veeam customers take?

There is no need for immediate action, as Microsoft will enforce throttling as documented. App registration limits are applied based on their usage terms, so only one application should be deployed per use case, and multiple applications running on the same tenant share the same resource bucket. However, if your environment uses multiple backup application registrations, backups may take longer to complete.

Which tenants/organizations are impacted?

Note: Only a small portion of Veeam Backup for Microsoft 365 and Veeam Data Cloud for Microsoft 365 customers use multiple application registrations. If you are not using multiple application registrations, you will not be impacted.

While terms of use apply to all customers, those who use multiple backup application registrations for Veeam’s backup solutions for Microsoft 365 may experience throttling, as Microsoft now throttles connections across similar applications within an organization.

How can I identify if my organization has multiple application registrations?

Check if your instance uses additional application registrations:

  • Veeam Backup for Microsoft 365
    • Additional backup applications can be found by right-clicking on the organization within Veeam Backup for Microsoft 365 and selecting "Managed backup applications." Additional backup applications will be listed in the Backup Applications Manager window.
    • You can remove additional backup applications, as they will no longer improve performance.
The Veeam Backup for Microsoft 365 interface shows the "Home" tab selected. In the "Organizations" section, a context menu is open for an organization. The highlighted option is "Manage backup applications..."
  • Veeam Data Cloud for Microsoft 365
    Note: It was uncommon for Veeam Data Cloud customers to have multiple backup applications deployed.
    No action is required from Veeam Data Cloud customers, as any extra backup applications created for the few customers who had them will be automatically removed.

How is Veeam addressing this change?

Veeam is making improvements to reduce the number of API calls required for backups, which will improve backup performance.

For customers operating self-managed backups using Veeam Backup for Microsoft 365, we strongly encourage installing the latest version. Each release includes improvements that enhance backup performance.

Veeam Backup for Microsoft 365 version 8.4 will be released soon, and all customers are encouraged to update to it as soon as possible.

For Veeam Data Cloud for Microsoft 365 customers, the latest updates are always automatically deployed as soon as they are available.

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

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

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

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.
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.