https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyOTQ2IiwiaGFzaCI6IjVlZjFmM2EyLTMzYzgtNDdlNy05MjA4LTE4MDExZGU3OTc1YyJ9
1-800-691-1991 | 9am - 8pm ET
EN

Service plan is not found when adding Office 365 organization

Challenge

Connecting to the Office 365 organization fails with the “Check Exchange plan: No Exchange plan found” or “Check SharePoint plan: No SharePoint plan found” error.
 

Cause

Some of the Office 365 Exchange or SharePoint service plans assigned to the Office 365 organization cannot be automatically identified as valid by Veeam Backup for Microsoft Office 365. This happens because assigned Office 365 plans are missing from the list of valid ones.

Solution

To resolve this issue, add missing Plans IDs to the list:

  1. Get the current Office 365 plan IDs assigned for the organization. You can do this via ‘MSOnline’ AzureAD module and the following PowerShell One-Liners: *

    Note: This script is provided as is as a courtesy for Gathering Plan IDs from MSOnline. Please be aware that the commands and parameters may be altered by Microsoft in the future, which may cause the script to function incorrectly. There is no support provided for this script, and should it fail, we ask that you please contact Microsoft support. This script may be updated in the future to reflect changes to the Office 365 Powershell Environment

    • To call "get-msolaccountsku" (use the CMDLET), call "Connect-MsolService" first. This requires the following modules to be installed and activated:

      install-module AzureAD
      install-module AzureADPreview
      install-module MSOnline
    • To get the list of Exchange Online service plans IDs:

      (get-msolaccountsku).servicestatus.serviceplan | where {$_.ServiceType -match "Exchange"} | ft ServiceName,ServicePlanId
    • To get the list of SharePoint Online service plans IDs:

      (get-msolaccountsku).servicestatus.serviceplan | where {$_.ServiceType -match "SharePoint"} | ft ServiceName,ServicePlanId
  2. Make sure that no backup jobs or restore sessions are running.
  3. Stop the Veeam.Archiver.Service and Veeam.Archiver.Proxy services.
  4. Navigate to the C:\ProgramData\Veeam\Backup365 directory on the VBO365 server, create a backup of the Congif.xml file by copying it to another location, then (Only after making the pre-edit copy) edit the Config.xml file by adding the following lines between <Archiver> tags:

    <Options>
    <O365Plans AdditionalExchangePlans="your-Exchange-plans-IDs" AdditionalSharePointPlans="your-SharePoint-plans-IDs" />
    </Options>
     

    If you do not have any sharepoint plans, do not add the AdditionalSharePointPlans to the line mentioned

    NOTE: You will have to add the Plans as the examples shown in the following screenshot. The GUIDs are entered in Coma Separated Value within the Quotation after each of the key values in the <O365Plans line.

    User-added image

    (Click image to view a larger version)

  5. Start the Veeam.Archiver.Service and the Veeam.Archiver.Proxy services.
  6. Open ‘Add organization’ wizard and retry the procedure.

More information

In case the issue persists after these changes, please, contact Veeam Support.

KB ID:
2946
Product:
Veeam Backup for Microsoft Office 365
Version:
any
Published:
2019-05-08
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.