What Microsoft's EWS Retirement Means for Your Veeam Backups

KB ID: 4820
Product: Veeam Data Cloud for Microsoft 365
Veeam Backup for Microsoft 365
Published: 2026-03-25
Last Modified: 2026-09-17
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.

Updated September 2026

This article has been revised to reflect:

  • Microsoft's October 1, 2026 enforcement timeline.
  • The introduction of the EWSAllowedAppIDs allow list.
  • The current status of Veeam's transition to Microsoft Graph.

Customers who have previously read this article are advised to review Steps 1 and 2 closely.

Challenge

Microsoft is retiring Exchange Web Services (EWS) in Exchange Online. EWS is the protocol Veeam currently uses to back up Exchange Online mailboxes.

Key dates:

  • October 1, 2026 — Microsoft begins disabling EWS tenant by tenant. Tenants that have not explicitly enabled EWS will be blocked automatically as the rollout proceeds.
  • April 1, 2027 — EWS is fully and permanently shut down for all tenants.

If you take no action before October 1, your Exchange Online mailbox backups will fail.

Veeam's transition to Microsoft Graph

Veeam is actively transitioning Exchange backup functionality from EWS to the Microsoft Graph API. This requires additional Microsoft Graph permissions. However, Microsoft has not yet completed all the Graph API capabilities required — specifically, delta sync support needed for incremental backups.

Veeam is working closely with Microsoft to close this gap. Until it is resolved, EWS must remain accessible for Exchange Online backups to continue. See Microsoft's parity gap roadmap for the latest status.

Solution

Step 1: Keep EWS enabled in your tenant

EWS access in Exchange Online is controlled by the EwsEnabled setting in your organization's configuration. Most tenants are currently at the default value of $null, and you will need to change this to $true before October 1, 2026.

What happens to each setting value starting October 1, 2026
If EwsEnabled Value Is: This will happen starting October 1, 2026:
$null
(default — most tenants)
Microsoft automatically changes this to $false. EWS is blocked for all apps.  You can re-enable it afterward, but that change can take time to propagate, and you will then need a validated App ID allow list (see Step 2) before EWS access is restored.
$true Microsoft honors an explicitly configured $true value and does not change it to $false during the rollout. However, the setting alone no longer determines access. If the App ID allow list is empty, all EWS access will be blocked. If the list is populated, only the applications on it can use EWS, which is already true before this date (see Step 2).
$false EWS remains blocked.
Swipe to show more of the table
Action required: Explicitly set EwsEnabled to $true now

Run the following PowerShell command against the Exchange Online tenant to check the current value first:

Get-OrganizationConfig | Format-List EwsEnabled

If the current value is anything other than $true, run the following command to set the value to $true:

Set-OrganizationConfig -EwsEnabled $true

Setting this explicitly to $true before October 1 protects your tenant from the automatic $null$false conversion and gives you control over the transition timeline.

Step 2: Manage your EWS App ID allow list

Microsoft has introduced EWSAllowedAppIDs, an allow list that controls which Entra ID app registrations are permitted to use EWS. The allow list takes effect as soon as it contains at least one entry. When EwsEnabled is set to $true and the list is populated, only the applications on that list can make EWS calls.

What changes starting October 1, 2026? An empty EWSAllowedAppIDs list will cause all EWS access to be blocked, even if EwsEnabled is set to $true.

Veeam's App IDs must therefore be included the first time the allow list is populated. Populating the list without them will block Veeam backups immediately, before October 1, 2026.

Will Microsoft populate this list for me?

Yes — Microsoft will automatically pre-populate the EWSAllowedAppIDs allow list based on each tenant's observed EWS usage, but only for tenants where the list has not already been configured. Note that this applies whether your current EwsEnabled value is $null or $true.

However, Microsoft recommends that admins create and validate their own list rather than relying on automatic population. The automatically populated list may include apps you are no longer aware of or wish to permit, and you, the admin, are responsible for ensuring the list is correct.

Microsoft's guidance: “Configure or validate the EWSAllowedAppIDs allow list (remember, we said we would populate this for tenants who have not done so, but the admin owns ensuring it's correct).”

What you need to do
  1. Review EWS usage in your tenant.
    • For Veeam Backup for Microsoft 365, open the Organizations view, right-click the Microsoft 365 organization, and select Edit Organization. The Application ID is listed in the application settings. For details, review Using Existing Microsoft Entra Application.
      • As an alternative, the following PowerShell command can be used to pull the current Application ID for a given organization:
        $org = Get-VBOOrganization -Name "Org_Name"
        $org.Office365ExchangeConnectionSettings.ApplicationId
        
    • For Veeam Data Cloud for Microsoft 365 use the EWS Usage Reports in Microsoft 365 Admin Center to identify App IDs currently making EWS calls.
    Note: For Veeam Data Cloud for Microsoft 365 customers, an automated way to enable EWS access is available. See Step 3.
  2. Ensure Veeam's App IDs are on the allow list. Veeam app registrations must be included so that backups can continue using EWS during the period before the Microsoft Graph transition is complete.
  3. Review and remove any app IDs you no longer need. This is a good opportunity to clean up stale registrations.

The allow list is configured in Exchange Online and is documented by Microsoft. Before making any changes, review Introducing EWSAllowedAppIDs: Preparing for the Final Phase of EWS Retirement, which provides the commands for viewing and setting the list, how to add an entry without discarding the entries already there, and how long a change takes to apply.

Step 3: Take action in your Veeam product

Veeam Data Cloud for Microsoft 365

Both actions below are performed in the Veeam Data Cloud portal. Completing either action requires authenticating against Microsoft 365 with an account that has the Global Administrator role.

  1. On the Microsoft 365 page, click the name of the tenant you want to manage.
  2. Select Settings.
  3. Go to the Microsoft 365 tab.
  4. In the EWS Access section, click Enable EWS access. For details, review Enabling EWS Access.
  5. In the Reauthorize Veeam Data Cloud section, click Reauthorize existing app registration. This grants the Microsoft Graph permissions needed for the transition. For details, review Reauthorizing Veeam Data Cloud for Microsoft 365.
  6. Repeat these steps for each Microsoft 365 tenant protected by Veeam Data Cloud.
Veeam Backup for Microsoft 365

Ensure the required Microsoft Graph permissions are assigned to your Veeam app registrations in Microsoft Entra ID:

Ensure EWS access is enabled, as described in Step 1: Keep EWS enabled in your tenant and Step 2: Manage your EWS App ID allow list.

An updated product release supporting the full EWS-to-Graph transition is in development. You will need to upgrade to that release when it becomes available.

Summary Checklist

Action Veeam Data Cloud for M365 Veeam Backup for M365
Manually configure access
Set EwsEnabled = $true in PowerShell Do now Do now
Review Veeam App IDs and validate App ID allow list Before Oct 1 Before Oct 1
Add Veeam App IDs to EWSAllowedAppIDs Before Oct 1 Before Oct 1
Add Microsoft Graph permissions in Entra ID Not applicable Do now
Upgrade to updated product release Not applicable When available
Automatically configure access
Reauthorize app in Veeam Data Cloud portal Do now Not applicable
Enable EWS access in VDC portal When available Not applicable
Swipe to show more of the table

More Information

Restoring access

If EWS is turned off for your tenant before you have completed the steps above, whether because your EWSEnabled was $null at the October 1 cutover, or for any other reason, you can restore access manually:

Set-OrganizationConfig -EwsEnabled $true

After re-enabling, ensure your Veeam App IDs are included in the EWSAllowedAppIDs allow list before backups will resume successfully. See also KB4796 for guidance on EWS access control at the organization and mailbox level.

Impact on backups

Once EWS access is blocked for your tenant, Exchange Online mailbox backups will fail. You can still restore access and add the required permissions, and backups will then resume, but:

  • The first backup job will perform a full sync, which is slower than a normal incremental run but uses the same amount of storage.
  • Any mailboxes not backed up during the gap will have a missing coverage window in their restore history.

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.