Chat now with support
Chat with Support

NetVault Plug-in for Microsoft 365 13.2.5 - Release Notes

Quest® NetVault® Plug-in for Microsoft 365 13.2.5

Quest® NetVault® Plug‑in for Microsoft 365 13.2.5
These release notes provide information about the Quest® NetVault® Plug‑in for Microsoft 365 release.

About this release

Quest NetVault (NetVault) Plug‑in for Microsoft 365 (Plug‑in for Microsoft 365) 13.2.5 is a minor release. For complete product documentation, visit

New features

New features in NetVault Plug‑in for Microsoft 365 13.2.5:
NOTE: New permissions are required for Synthetic Backup of Teams. For more information, see Using the Microsoft 365 admin portal to obtain configuration details in NetVault Plug-in for Microsoft 365 Users Guide.

Known issues

If you perform a granular restore of Outlook or OneDrive, selecting the primary node — OneDrive or Outlook — and clearing any individual user nodes behaves correctly. However, if you select a user node and clear any subnodes, the plug-in restores all items for the selected user. That is, the plug-in ignores the cleared subnodes that are marked with a red X.

DNPO365-253, DNPO365-277

As designed, if a User/Group/SP is deleted and restored with one ID, and you attempt to restore it again, the plug-in must restore it with a new ID as the first ID exists.

Workaround: Delete the previously restored object, and then perform the new restore.


Restoring a user’s OneDrive data fails with the error “User’s mysite not found.”

Workaround: Complete the following steps:


When restoring Azure AD content and the default password “nvbu123*#$” is used in the Set password for user(s) on the Restore Option screen, the restore job completes with the error “The specified password does not comply with password complexity requirements.

Workaround: If the Azure AD user restore fails with aforementioned error, even though the password meets the complexity requirements, provide the same password in the config file under the “:Azure AD User Password” stanza and perform the restore again.


When restoring a modern SharePoint Online team site — which has an associated Office 365 Group that was automatically generated upon site creation — to a a nonexistent site, a new site is created but the associated Office 365 Group is not created or associated with the restored site.


Web parts of classic SharePoint Online sites do not restore, because they use a specific template.


When relocating the backup of a SharePoint Online site to a nonexistent site, a new site is created, but any custom permission levels that were created are not restored because the scope of the permission level is limited to the original site and its subsites.


If a SharePoint Online site contains a OneNote notebook, the notebook is not backed up and restored. The remainder of the site contents are restored.


Due to a limitation of the Microsoft Graph API, events of type Appointment are restored as type Event in the calendar.


If you restore a backup of Teams that includes a Team that was deleted for any reason, the restore does not include all App tabs for the deleted Team. Because a backup job for Teams does not include separate backups for App tabs, some App tabs, including OneNote, Planner, Forms, and Streams, are excluded from the restored Team.


Due to a limitation of the Microsoft Graph API, restoring a Teams backup does not include the Channel settings. It does restore the Team, its Channel, and Team settings.


When restoring a tenant’s Azure Active Directory, the owners and user members of the service principal do not restore.


The contents of a wiki app within a Teams channel do not restore.


When a previous version of Plug‑in for Microsoft 365 that contains a saveset with default options is removed and the latest 13.1 version is installed, then clicking the + button next to plug-in options in the Create Backup Job window causes an unexpected pop-up to hang and the UI to become unresponsive,

Workaround: To prevent a pop-up from appearing and causing the WebUI to be unresponsive, before creating the new plug-in set, click Edit and save the existing default plug-in options, and then click the + icon.

DNPO365-1247, NV-1544

Users cannot edit restored site pages and create a new site page after restoring a SharePoint site.

Workaround: To resolve this issue, add a content type to the Page library and then change the button order and default content type by completing the following steps.

From the Select site content types from drop-down list, select All Groups.
In the Available Site Content Types box, select Site Page, and then click Add.
The Site Page content type moves to the Content types to add box.
Under Content Types, select Change new button order and default content type.


Existing files before renaming the folder are restored to the original folder (i.e. folder location before renaming it) and files uploaded to the folder after renaming are restored to renamed folder.



Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating