Engage Center API returns HTTP 403 – Personal Microsoft Account Cannot Access Support for Business Workspace

Rahim Zulfiqar Ali 0 Reputation points MVP
2026-11-11T08:56:17.9533333+00:00

Hello Microsoft Support Team,

I am unable to access Microsoft Credentials Support through Microsoft Engage Center.

I successfully authenticate using my personal Microsoft account and can select the Support for Business (SFB) workspace. However, the workspace never loads and displays an indefinite loading animation.

I investigated the issue using Google Chrome Developer Tools and identified the following errors:

  1. The API request to gateway.engagehub.azure.com/sp/space repeatedly returns HTTP 403 Forbidden.

The Engage Center application reports: fetchSpaceDetails failed.

The application reports: Unable to build navigation using spaceId from engagehubScope.

React reports a failed request with status code 403.

Troubleshooting already completed:

Successfully authenticated using the Microsoft Personal Users tenant.

Selected Support for Business workspace.

Tested Microsoft Edge and Google Chrome.

Tested private/incognito browser sessions.

Tried the direct Credentials Support links.

Request:

Please investigate my personal Microsoft account's authorization and provisioning for the Support for Business workspace.

I also request that this issue be escalated to the Microsoft Engage Center engineering team or that an alternative method be provided to submit my Microsoft Credentials Support request.

I can provide screenshots and diagnostic information privately.

Thank you for your assistance.Subject: Engage Center API returns HTTP 403 – Personal Microsoft Account Cannot Access Support for Business Workspace

Hello Microsoft Support Team,

I am unable to access Microsoft Credentials Support through Microsoft Engage Center.

I successfully authenticate using my personal Microsoft account and can select the Support for Business (SFB) workspace. However, the workspace never loads and displays an indefinite loading animation.

I investigated the issue using Google Chrome Developer Tools and identified the following errors:

The API request to gateway.engagehub.azure.com/sp/space repeatedly returns HTTP 403 Forbidden.

The Engage Center application reports: fetchSpaceDetails failed.

The application reports: Unable to build navigation using spaceId from engagehubScope.

React reports a failed request with status code 403.

Troubleshooting already completed:

Successfully authenticated using the Microsoft Personal Users tenant.

Selected Support for Business workspace.

Tested Microsoft Edge and Google Chrome.

Tested private/incognito browser sessions.

Tried the direct Credentials Support links.

Request:

Please investigate my personal Microsoft account's authorization and provisioning for the Support for Business workspace.

I also request that this issue be escalated to the Microsoft Engage Center engineering team or that an alternative method be provided to submit my Microsoft Credentials Support request.

I can provide screenshots and diagnostic information privately.

Thank you for your assistance.

System Center Service Manager
0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.