Restoring Navigation Settings

Restore applies one selected backup version to one SharePoint site. It is a write operation and requires both M365Suite restore permission and SharePoint Sites.Manage.All application permission.

Before you restore

A restore changes the live site navigation. Review the selected site and version first. If you need an extra checkpoint, create a current backup before restoring.

You can export a version from its history when you need an external copy for review.

Restore a version

1. Open Recovery Center.
2. Select the site whose navigation you want to restore.
3. Open the version history for that site.
4. Select the version you intend to use.
5. Review the available preview or version details.
6. Choose the restore action and review the readiness summary in the confirmation prompt.
7. Wait for the result message, then review the site in SharePoint.

What restore writes

The current restore implementation writes captured structural top navigation and quick launch nodes for the selected site.

Before sending the request, the confirmation identifies structural surfaces that will be written, menu-state surfaces that will be skipped, inherited hub navigation that is evidence only, and legacy capture sources that should be reviewed after restore.

What restore does not write

The current restore implementation does not restore:

• Page content or list content
• SharePoint permissions
• Themes
• Hub membership or hub associations
• Web design settings such as header, footer, logo, or mega-menu configuration
• Navigation data that was captured only through a managed or inherited menu-state fallback

Some of this information can still appear in a backup for reference. Captured does not always mean restorable.

Who can restore

• Admins can restore tenant-wide.
• Hub Managers can restore sites inside assigned hub scopes.
• Site Managers can restore assigned site URLs.
• Type Managers can restore sites matching assigned site types.
• Viewers and Guests cannot restore.

The server validates tenant, role, and scope for every restore request. UI visibility is not the authorization boundary.