Forum Discussion

SPUser1's avatar
SPUser1
Copper Contributor
Sep 08, 2026

Hub Site association approval request fails with 403 Forbidden (previously working, regression)

Sites configured to require approval before joining our Hub Site are failing the association request with an HTTP 403 Forbidden error[browser DevTools Network tab}. This same workflow was functioning correctly as of [early August 2026]. Hub sites that do not require join approval continue to associate successfully — the failure is isolated specifically to the approval-required path.

Steps to Reproduce

  1. As a site owner, go to Site Settings → Site Information (or Site Contents → hub association) on a site that is not yet associated with the hub.
  2. Attempt to associate it with [Hub Site URL], which has RequiresJoinApproval set to $true.
  3. Observe that the request fails immediately (or fails when the approver attempts to approve it — specify which point in the workflow fails).
  4. Repeat the same steps against a hub site that does not require approval — association succeeds without error.

Expected Behavior
The association request should be submitted and routed to the configured approver(s) for review, consistent with behavior observed as recently.

Actual Behavior
Request fails with HTTP 403 Forbidden. [browser DevTools Network tab - attached the HAR file for reference]

Error Details

  • HTTP Status: 403 Forbidden [browser DevTools Network tab - JoinHubSite(@v1)?@v1]

     

Troubleshooting Already Performed

  • Confirmed association without approval works (isolates the issue to the approval workflow specifically)
Microsoft365
SharePoint Online

2 Replies

  • M365_Architect_Vance's avatar
    M365_Architect_Vance
    Copper Contributor
    Sep 17, 2026

    This HTTP 403 Forbidden regression loop on approval-required paths is heavily disrupting multi-hub enterprise environments. While waiting for platform-level path remediation, managing sprawling global directories requires absolute structural architecture command over your canvas layout slots.

     

    A reliable method to keep separate team and communication workspaces beautifully aligned despite native tenant configuration regressions is to use a global UI overwrite engine. By decoupling your primary corporate aesthetic, expandable global footers, and accordion right sidebars from erratic native settings, your administrators can toggle uniform branding elements tenant-wide natively using simple folder name changes ("On"/"Off") requiring 0 ongoing IT helpdesk tickets.

     

    If you are looking to stabilize adoption layouts across your hubs during platform regressions, you can step through a fully isolated, production-ready framework on the Enterprise UI Overwrite Suite Showcase: 

    https://sharepointpackages.com/sharepoint-online-m365-c-1_31/m365-ui-overwrite-suite-p-67.html