This guide covers creating a Microsoft 365 backup set: the prerequisites, the Microsoft EWS retirement that started on 1 October 2026, authorising against your tenant, choosing what to back up, destinations, encryption, and what can and cannot be restored afterwards.
Contents
Before you start
Software version
Use version 10.3.2 or later of the backup software. Earlier versions do not have the Microsoft Graph changes needed after the EWS retirement described below. After upgrading, re-run Authorise on any existing Microsoft 365 backup set so the additional Microsoft Graph API permissions are granted.
Microsoft 365 account permissions
The account used to authorise the backup set needs one of the following:
- Global Administrator, or
- all four of Application Administrator, Exchange Administrator, SharePoint Administrator and Teams Administrator, if Global Administrator cannot be granted.
In addition:
- Term Store Administrator may be needed to back up and restore some SharePoint items. Add it in the SharePoint admin centre under Content services > Term store.
- The account should be a member of the Discovery Management role group in the Exchange admin centre, with the Legal Hold, Mailbox Import Export and Mailbox Search roles assigned to that group.
- Public Folders can only be selected by a licensed Exchange administrator, or a licensed user with Public Folder permission.
Microsoft 365 licences on the tenant side
The account you restore data into needs a matching Microsoft licence: an Exchange Online licence to restore Outlook items, and a SharePoint Online licence to restore OneDrive or Personal Site items.
Users on Exchange Online Kiosk, Microsoft 365 F1 or F3 licences are affected by the EWS changes below — read that section if you back up frontline users.
How backup licences are counted
- Each Microsoft 365 user selected for backup uses one Microsoft 365 backup licence, whether or not the user is licensed by Microsoft. The same user in several backup sets under one backup account counts once.
- Each shared, room or equipment mailbox selected for backup also uses one licence.
- A backup set containing only SharePoint Site Collections uses no licences, but at least one licence must be available for the backup to start.
- When a user is removed from the backup source, their data moves to the retention area and keeps using a licence until retention clean-up permanently deletes it.
Microsoft EWS retirement (October 2026)
Microsoft has begun retiring Exchange Web Services (EWS) in Exchange Online. From 1 October 2026 it is being switched off tenant by tenant, and on 1 April 2027 it is turned off permanently for every tenant, with no exceptions or extensions. This is a Microsoft change and affects every Microsoft 365 backup vendor.
Most Microsoft 365 data has already moved to Microsoft Graph and is not affected: Outlook mailboxes (mail, calendar, contacts), OneDrive, Personal Sites, SharePoint, Group Sites, Teams Chat and Teams Channels.
Three data types still depend on EWS, because Microsoft Graph does not yet support them:
| Data type | Until 1 April 2027 | After 1 April 2027 |
|---|---|---|
| Outlook (Archive) | Backs up only if EWS is enabled on the tenant (see below) | Stops. Microsoft has committed to Graph access for archive mailboxes, targeted for late 2026; we will update this article when the backup software supports it. |
| Group Mail (Teams / Microsoft 365 Group mailboxes) | Backs up only if EWS is enabled on the tenant | Stops. Microsoft has confirmed general Graph access to Group mailboxes will not be added. |
| Public Folders | Backs up only if EWS is enabled on the tenant | Stops. Microsoft has confirmed Public Folders will not be supported in Graph. Microsoft’s recommendation is to migrate Public Folder content to shared mailboxes or Microsoft 365 Groups, which are backed up normally. |
Keeping archive, Group Mail and Public Folder backups running until April 2027
If a customer relies on any of those three, EWS must be enabled on their tenant, with the backup software on the tenant’s EWS application allow list. A tenant left at the default setting was switched off on or after 1 October. Check the setting in Exchange Online PowerShell:
Get-OrganizationConfig | Select EwsEnabled, EwsApplicationAccessPolicy
If EwsEnabled is False or blank, enable it:
Set-OrganizationConfig -EwsEnabled $true
Then make sure the backup software’s application is on the tenant’s EWS allow list. Enabling EWS without an allow list entry does not work after 1 October 2026. The application appears under Enterprise applications in the Microsoft Entra admin centre once the backup set has been authorised; contact us if you need its Application ID. EWS can be re-enabled at any point before 1 April 2027, including after backups have started failing, and backups resume on the next run.
Treat this as a bridge, not a fix. Plan for archive, Group Mail and Public Folder backups to stop on 1 April 2027.
Kiosk, F1 and F3 licensed users
Separately, Microsoft blocks EWS for mailboxes licensed only as Exchange Online Kiosk, Microsoft 365 / Office 365 F1 or F3, returning an HTTP 403 error. The tenant setting above does not override this. For these users, Outlook (Archive) and any other EWS-dependent backup fails. To keep it working, assign a licence that includes EWS rights, such as Exchange Online Plan 1 or 2, or Microsoft 365 E3/E5.
What happens to data already backed up
Archive, Group Mail and Public Folder data already in your backup stays restorable for as long as your retention policy keeps it. It simply stops being updated once EWS is unavailable to the tenant.
Creating the backup set
-
Log in to the backup software.
-
In the main interface, click Backup Sets.

-
Click the + icon before “Add new backup set”.

-
Enter a Name for your backup set and select Microsoft 365 Backup as the backup set type.

Select the Backup Scope and Region. Tick Access the Internet through proxy if needed, then click Test.

-
Click Authorise to start the authentication process.

Sign in to your Microsoft account.

If the account is required to use MFA — through Security Defaults, a Conditional Access policy or per-user MFA — complete the verification with whichever method the account is registered for, such as the Microsoft Authenticator app, a text or a call. The screenshots below show the text and call options.

If Call was selected, answer the call and follow the instructions to complete the verification.

If Text was selected, enter the code and click Verify.

Note: verification is only requested if MFA is required for the account signing in.
Copy the authorisation code.

Go back to the backup software, paste the authorisation code and click OK.

If the backup scope selected is Entire organisation but the account used to sign in is a personal account, this error message is displayed.

Change the backup scope to This Microsoft 365 user only — only a business account can be used to sign in when the scope is Entire organisation.
“Test completed successfully” is shown when the validation succeeds. Click Next to continue.

Backup source
-
The Backup Source window that appears depends on the backup scope you selected — Entire organisation or This Microsoft 365 user only.
If Entire organisation is selected
Select the users and data types to back up.

To select specific users, click Select.

Users can be sorted alphabetically or by user group. Sorted alphabetically:

Sorted by user group:

The list of users can be displayed three ways: Show all, Selected only and No longer available.

You can search for a user by entering a name or email address in the search box; matching names and addresses are listed automatically. Click Check All Current Items to select every listed user.

Select specific users by ticking the checkbox beside each one.

To display only the users you have selected, choose Selected only.

Click OK once done with the selection.
Tick Auto-exclude any Microsoft 365 unlicensed user during backup if you do not want unlicensed users included.

An unlicensed user is shown with a yellow warning tag on the icon.

Select the data types to include in the backup: Outlook, Outlook (Archive), OneDrive, Personal Site and Teams Chat. Ticking a checkbox backs up all of that type — ticking Outlook, for example, backs up the mailboxes of the selected users. For Teams Chat you do not need to select the other user accounts involved in a chat to back up the conversation.
Note: Outlook (Archive) depends on Microsoft EWS. It only backs up if EWS is enabled on the tenant, and stops entirely on 1 April 2027. See Microsoft EWS retirement.

Select whether to back up Teams, SharePoint Sites and Public Folders. To back up a specific group in Teams, tick Select Specific, then click Select.

You can search for a group by entering its name in the Search Groups field. Groups can also be displayed as Show all, Selected only or No longer available. Click OK once done, and choose whether Group Mail, Group Site and Teams Channel are included.

Note: to back up shared attachments on certain Teams Channel posts, OneDrive and Group Site must both be selected as source.
Note: Group Mail and Public Folders depend on Microsoft EWS. They only back up if EWS is enabled on the tenant, and stop entirely on 1 April 2027. See Microsoft EWS retirement.
To back up a specific site in SharePoint Sites, tick Select Specific, then click Select. Searching and listing sites works the same way as for users.


To back up a specific public folder, tick Select Specific, then click Select. Searching and listing public folders works the same way.


If This Microsoft 365 user only is selected
The window shown depends on the type of account used for authentication. For a business account:

Note: this message appears if OneDrive is not selected but Teams Channel and/or Teams Chat are.

For a personal account:

Note: for instructions on using the Filter, refer to the Backup Source Filter section.
Schedule
-
In the Schedule window, configure a backup schedule so backup jobs run automatically at your specified intervals.

Slide the on/off button to turn the feature on, then click + Add new schedule and configure the settings in the New Backup Schedule window.

Destination
-
In the Destination window, select a backup destination for the backup data. Click the + icon before “Add new storage destination”.

Select the storage destination.

You can choose destinations such as Local / Mapped Drive / Network Drive / Removable Drive or cloud storage. Click OK when you are done with the settings.
- If you chose Local / Mapped Drive / Network Drive / Removable Drive, select the Type. Click Change to browse to a directory path where backup data will be stored, or enter the path manually. Tick This share requires access credentials if credentials are needed. Click Test to validate the path; “Test completed successfully” is shown when validation is done.

- If you chose cloud storage, click Test to log in to the corresponding cloud storage service.

You can add multiple storage destinations. Backup data is uploaded to all of them, in the order you added them. Use the up and down icons to change the order. Click Next to proceed.

Encryption
-
In the Encryption window, Encrypt Backup Data is enabled by default with an encryption key preset by the system, which provides the most secure protection. Click Next when you are done.

-
If you enabled the encryption key feature in the previous step, the following pop-up window is shown, whichever encryption type you selected.

- Unmask encryption key — the key is masked by default; click to show it.
- Copy to clipboard — copies the encryption key so you can paste it somewhere of your choice.
- Confirm — exits the pop-up and proceeds to the next step.

Important: write the encryption key down and keep it somewhere safe. Without it your backup data cannot be restored, and we cannot recover it for you.
Finishing up
-
This screen is displayed when the new Microsoft 365 backup set is created successfully. Click Backup now to back up your data, or Close to return to the main screen.

-
We strongly recommend changing the Temporary Directory to a location with sufficient free disk space other than drive C. Go to Others > Temporary Directory and click Change to browse to another location.

-
Optional: select your preferred compression type. By default the compression is Fast with optimisation for local. Go to Others > Compressions, then choose from No Compression, Normal, Fast (compressed size larger than normal) or Fast with optimisation for local.

Click Save to apply the changes.
What can be restored
For the restore walkthrough itself, see Microsoft 365 Restore. This section covers what you get back.
Most Microsoft 365 data restores as it was backed up. A few things are limited by what Microsoft’s APIs allow, rather than by the backup software, so it is worth agreeing expectations before they are tested.
| Data | Restores as backed up? | Notes |
|---|---|---|
| Outlook mail, calendar and contacts | Yes | Messages, folder structure and attachments. Can be restored to the original mailbox or an alternate one. |
| Outlook (Archive) | Yes, while EWS is available to the tenant | The archive mailbox is a separate backup source — it must be selected explicitly or it is not backed up at all. Backup and restore depend on Microsoft EWS, which ends on 1 April 2027 — see Microsoft EWS retirement. |
| OneDrive files | Yes | File content restores intact. |
| SharePoint and Group Site documents | Partly | Document libraries, list items and their default column types restore. Most site and list settings, site logos, web parts, workflows and customisations are not recreated — treat this as document recovery, not site recovery. See What is not backed up. |
| File share links | Partly | Share links on OneDrive and SharePoint documents are backed up and restored, but only when restoring to the same Microsoft 365 organisation. Restoring to a different organisation brings files back without their sharing. |
| File version history | Yes, for OneDrive and SharePoint documents | At restore you choose Restore all versions or Restore latest version only. Applies to OneDrive, Personal Site, Group Site and Site Collections, except .aspx pages. Not applicable to mail. |
| Teams Chat and Channel messages | No — not back into Teams | Microsoft’s Teams Export API is read-only: there is no supported way to write messages back into Teams. Conversations are recoverable as readable exported content, not as live chats. This is a Microsoft limitation and applies to every backup vendor. |
| Group Mail | Yes, while EWS is available to the tenant | Depends on Microsoft EWS, which ends on 1 April 2027. Microsoft will not add Graph access for Group mailbox items. |
| Public Folders | Yes, while EWS is available to the tenant | Depends on Microsoft EWS, which ends on 1 April 2027. Microsoft will not add Graph support for Public Folders. Restoring to a mailbox or Group is the practical route afterwards. |
| Links to restored items | No | Restored items are assigned new IDs, so existing links, bookmarks and embeds pointing at the originals will not resolve. |
Restoring after a user is deleted
Microsoft keeps a deleted user recoverable for 30 days under Users > Deleted users in the Microsoft 365 admin centre. Within that window, restoring the user is quicker than restoring their data, and brings back the mailbox and OneDrive with it.
After 30 days the account is gone. Data cannot be restored into an account that does not exist, so you would recreate the user — which requires a licence — and restore into it, or restore the data to a different existing account if it only needs to be readable.
Note: Microsoft 365 retention, litigation hold and the recycle bin are not backups. They are time-limited, they can be cleared by an administrator, and they do not survive the tenant itself being lost. The backup set described in this guide is held separately from your tenant, which is the point of it.
What is not backed up
The backup software connects to Microsoft 365 using modern authentication and Microsoft’s current APIs, mainly Microsoft Graph. Basic authentication has been switched off by Microsoft, and some things the older APIs could reach are not available through the modern ones. The items below are skipped or only partly handled. Most appear in the backup log as a warning, not an error — the rest of the job completes normally.
| Area | Not backed up or not restored |
|---|---|
| SharePoint external content types | Not backed up. Lists linked to an external content type (Business Connectivity Services) log Skipping external content type. Reason=Web service request is not supported under modern mode. The data lives in the external system, not SharePoint, so protect it there. |
| SharePoint site and list settings | Site feature settings, most site-level and list-level settings (including list views), site logos, survey list options and user-defined workflow templates are not restored. Web parts and metadata are only partly supported. Expect to revisit settings, column order and visibility after a restore. |
| SharePoint lists | Customised apps and SharePoint App Store apps are not backed up. Some list types, such as Microfeed on classic team sites, are skipped at restore. |
| SharePoint news | Restored news items on modern team sites are not republished to the home page. Post each one again from Site contents > Site Pages. |
| Recycle bin | SharePoint and OneDrive recycle bin contents are not backed up. |
| Teams | Chats with external (guest or federated) users, attachments to system messages such as meeting recordings, and tabs and pins in chats or channels are not backed up. Chat and channel messages cannot be restored back into Teams. |
| Teams Chat attachments | Files shared in a chat live in the sender’s OneDrive. They are only captured if that sender is selected for backup with OneDrive ticked. |
| Outlook (Archive), Group Mail, Public Folders | Depend on Microsoft EWS, which ends on 1 April 2027. See Microsoft EWS retirement. |
| Region | Modern authentication is only supported for tenants registered in Microsoft’s Global region, with the backup set also set to Global. |
Troubleshooting
| Symptom | Cause and fix |
|---|---|
| An error appears when Entire organisation is selected | The account used to sign in is a personal account. Only a business account can authorise an organisation-wide backup. Either sign in with a business account, or change the scope to This Microsoft 365 user only. |
| A verification code is requested unexpectedly | MFA is required for the account being used to authorise. Complete the verification with the method the account is registered for. If the account is a service account, check whether a conditional access policy is forcing MFA on it. |
| Shared attachments missing from Teams Channel posts | Both OneDrive and Group Site must be selected as backup sources for those attachments to be captured. |
| A warning appears when selecting Teams Chat or Teams Channel | OneDrive is not selected. Teams content depends on it, so add OneDrive to the backup source. |
| Unlicensed users cause backup failures | Tick Auto-exclude any Microsoft 365 unlicensed user during backup. Unlicensed users are shown with a yellow warning tag. |
| Backups fail with insufficient disk space | The temporary directory is still on drive C. See the final step above. |
| Outlook (Archive), Group Mail or Public Folder backups fail or stop updating from October 2026 | EWS has been switched off on the tenant. Enable it and add the backup application to the EWS allow list — see Microsoft EWS retirement. This only works until 1 April 2027. |
| HTTP 403 errors on some users’ archive mailboxes | The user is licensed as Exchange Online Kiosk, F1 or F3, which Microsoft blocks from EWS regardless of tenant settings. Assign a licence with EWS rights, such as Exchange Online Plan 1 or 2, or Microsoft 365 E3/E5. |
| Permission or access errors during authorisation or backup | The authorising account is missing a required role. Check it has Global Administrator (or the four alternative admin roles), membership of Discovery Management with the Legal Hold, Mailbox Import Export and Mailbox Search roles, and Term Store Administrator if SharePoint items fail. See Before you start. |
| Backups fail after upgrading to version 10.3.2 or later | The additional Microsoft Graph permissions have not been granted. Re-run Authorise on the backup set. |
| Backup licence count higher than the number of current users | Shared, room and equipment mailboxes each use a licence, and removed users keep using one until their data is purged by retention clean-up. See How backup licences are counted. |
| Log warning: Skipping external content type. Reason=Web service request is not supported under modern mode. | A SharePoint list is linked to an external content type, which cannot be read under modern authentication. Harmless — the rest of the site backs up. To clear the warning, remove the unused external list or External Data column, or deselect that list from the backup source. Back up the external system directly if its data matters. |
| Access denied when expanding or backing up a SharePoint site collection | The authorising account is not Global Administrator and is not a site admin of that site collection. Being site admin of the root site does not cover site collections beneath it — add the account as site admin of each one, or authorise with a Global Administrator. |
| A mail item shows red in the backup source after a restore | Restoring with overwrite to the original mailbox gives the message a new ID. Deselect the red item and tick the new copy, otherwise later backups will warn about it. |
| Files missing from backed-up Teams chats | The files are in the OneDrive of a user who is not selected. Select every chat participant whose files you need, with OneDrive ticked. |
| Backups slow down or report throttling after raising the thread count | Microsoft throttles requests per tenant. Four concurrent backup threads is the recommended setting; more threads use more memory and increase throttling without making the job faster. |
| Restoring SharePoint files to a Windows computer fails for some items | The file or folder name contains a character Windows does not allow (/ \ | * : " < >). Restore those items back into Microsoft 365 instead, or rename them at source. |
| Authorisation stops working after a period | The stored token has expired or been revoked — commonly after a password change, an MFA reset or a conditional access change. Re-run the authorisation on the backup set. |
For restoring from one of these backup sets, see Microsoft 365 Restore.
If you need a hand with any of the above, contact us at support@bobcloud.net.