Fix Power Automate 403 Access Denied When Joining a SharePoint Hub Site
Question details
The user needs to resolve a 403 Access Denied response when a Power Automate flow calls the SharePoint JoinHubSite API.
- Product
- Microsoft Power Automate and Microsoft SharePoint
- Device & OS
- not provided
- Scenario
- A flow attempts to associate a SharePoint site with a hub site.
- Observed behavior
- The JoinHubSite request returns 403 Access Denied, indicating a possible permission or connection-account issue.
Open the failed flow run and identify the SharePoint action, target site URL, hub site ID, and connection account. Have a SharePoint administrator available to verify site access and hub association permissions.
Verify the flow account's site and hub association permissions
Start here when the account used by the SharePoint action may lack permission to associate the site with the hub.
In Power Automate, open My flows, select the flow, and choose Edit. Inspect the SharePoint action that calls JoinHubSite and its selected connection; do not assume it uses the account that started the flow.
Sign in to SharePoint with the connection account and open the target site URL. Ask the site owner or SharePoint administrator to confirm that this account has the permissions required to manage the site's hub association, not just view its contents.
Ask a SharePoint administrator to open the SharePoint admin center, go to Active sites, select the hub site, and review its hub association settings. If association is restricted to specified users or groups, confirm that the connection account is permitted.
Using the same account, open the target SharePoint site and go to Settings > Site information. If the Hub site association option is available, check whether the intended hub can be selected. If the option or hub is unavailable, ask the administrator to review permissions before retrying the flow.
Repair or replace the SharePoint connection used by the flow
Use this when the flow references the wrong account or its SharePoint connection needs authentication.
Request specialized help for a persistent JoinHubSite error
Use this when verified permissions and a valid connection do not resolve the 403 response.
Use WPS Office for Documents While Troubleshooting SharePoint
WPS Office is a free, lightweight alternative for everyday document work, with a familiar interface and Microsoft Office format compatibility for easy migration. It does not repair Power Automate connections or change SharePoint hub permissions, but it can help you prepare troubleshooting notes and reports.

Frequently Asked Questions
Why does JoinHubSite return 403 even though I can open the SharePoint site?
Viewing a site and managing its hub association require different permissions. Check the account selected in the flow's SharePoint action, then ask an administrator to verify its site-management permissions and the hub's allowed association users or groups.
Does the flow always use the permissions of the person who starts it?
No. The SharePoint action uses its configured connection, which may belong to another account. Open the flow in Edit mode and inspect the action's connection; for instant flows, also review any run-only user connection settings.
Will creating a new SharePoint connection fix the error?
Only if the problem is an invalid connection or the wrong connection account. In Power Automate, open Connections to repair or replace it. A new connection does not grant the account permission to associate a site with a hub.
What should I include when asking the Power Automate Community for help?
Include the sanitized failed-action error, API path, request method, connection type, and permissions already checked. State whether manual association works with the same account, and remove credentials and authentication tokens.
Can WPS Office fix SharePoint hub association permissions?
No. SharePoint permissions must be managed in SharePoint, and the flow connection must be configured in Power Automate. WPS Office can edit supporting documents, but it cannot change these service permissions.




