SharePoint Hub Navigation Does Not Update on Associated Sites: What Site Owners Should Check

When you update the global navigation on a SharePoint hub site, the changes should automatically appear on all associated sites. Many site owners report that the navigation does not update, showing old links or missing new items. This problem usually occurs because the hub navigation caching system or synchronization settings are not refreshing as expected. This article explains why hub navigation can fail to update and provides the specific checks and fixes site owners can apply.

Why Hub Navigation Does Not Update Automatically

SharePoint hub navigation is stored in a central location on the hub site. When you add, remove, or reorder a navigation link, the change is saved to the hub site database. Associated sites read this navigation data from the hub site, not from their own local settings. The system uses a cache to reduce load on the hub site. This cache refreshes every 15 to 30 minutes by default. If you check an associated site immediately after making a change, the cache may still hold the old navigation data.

Another root cause is permission mismatch. The user who edits the hub navigation must be a site owner on the hub site, but the hub navigation will only appear on associated sites if those sites have the correct association. If an associated site was manually disassociated or if the hub site association was removed, the navigation will not update. The hub site itself must also be active and accessible. If the hub site is deleted or its site collection is locked, no associated site can read the navigation.

Cache Refresh Mechanism

The hub navigation cache is a server-side cache that stores the last known navigation structure. This cache is refreshed when a user visits the hub site directly or when a timer job runs. The timer job runs every 15 minutes. You cannot manually trigger this cache refresh from the SharePoint admin center. The only way to force a refresh is to make a subsequent change to the hub navigation, which resets the 15-minute timer.

Permission and Association Requirements

For hub navigation to appear on a site, that site must be associated with the hub. Site owners can verify this in Site Settings under Hub site settings. The user who updates the hub navigation must have at least edit rights on the hub site. The navigation will then be visible to all users who have access to the associated sites. If a user does not have permission to view the hub site itself, they will still see the navigation on the associated site because the navigation is read from the hub site database, not the site content.

Steps to Force Hub Navigation to Update

1. Clear the browser cache on the associated site
   Open the associated site in a private or incognito browser window. If the navigation appears correctly in this mode, the browser cache was holding the old version. Instruct all site visitors to clear their browser cache or use Ctrl+F5 to force a full page refresh.
2. Make a dummy change to the hub navigation
   Go to the hub site. Select Settings > Navigation. Add a temporary link, then save. Wait 15 minutes. Remove the temporary link and save again. This resets the cache timer and forces a refresh within the next 15 minutes.
3. Reassociate the site with the hub
   On the associated site, go to Site Settings > Hub site settings. Note the current hub URL. Remove the association by selecting Remove from hub. Wait 5 minutes. Reassociate the site with the same hub URL. This clears the local association data and forces the site to fetch navigation from the hub.
4. Check the hub site navigation node count
   SharePoint allows a maximum of 500 navigation nodes per hub. Count all nodes in the hub navigation, including subnodes. If you exceed 500, delete some nodes. Then repeat the dummy change step. The navigation will not update if the limit is exceeded.
5. Verify the hub site is active
   Go to the SharePoint admin center > Active sites. Find the hub site. Confirm its status is Active and its site collection is not locked. If the site is locked or deleted, the hub navigation will not propagate. You must designate a new hub site and reassociate all sites.

If the Navigation Still Does Not Update

Users see old navigation on one specific associated site

This often indicates a local association issue. Remove the site from the hub and reassociate it using the steps above. If the problem persists, the site may have custom navigation settings that override the hub navigation. Check Site Settings > Navigation. If Custom navigation is selected, change it to Inherit from hub site. Save and refresh the page.

Navigation appears on some sites but not others

The hub site association may not be set on the missing sites. In the SharePoint admin center, go to Active sites. Select the site that is missing the navigation. In the panel, look for Hub site settings. If no hub is listed, click Edit and select the correct hub. This can also happen if the site was created after the hub navigation was last updated. Reassociating the site will pull the latest navigation.

Navigation updates appear after 24 hours

This is a symptom of a stuck cache timer job. The SharePoint timer job that refreshes the hub navigation cache may be delayed. You can force a refresh by running the following PowerShell command: Set-SPOHubSite -Identity -RerunNavigationSync. This command is available only in SharePoint Online Management Shell. After running, navigation should update within 15 minutes.

Issue	Likely Cause	Quick Fix
Navigation not updating on any site	Cache not refreshed	Make a dummy change to hub navigation and wait 15 minutes
Navigation missing on one site	Site not associated with hub	Reassociate the site in Site Settings or SharePoint admin center
Navigation shows old links	Exceeded 500 node limit	Delete unused navigation nodes
Navigation appears after 24 hours	Stuck timer job	Run Set-SPOHubSite -RerunNavigationSync in PowerShell

You can now diagnose and fix hub navigation update failures on associated sites. Start by clearing the browser cache and making a dummy change to the hub navigation. If the problem persists, check the hub site association and the 500-node limit. For advanced cases, use the SharePoint Online Management Shell to force a navigation sync. This approach resolves the vast majority of hub navigation update issues without requiring Microsoft Support intervention.