Skip to content

SPHttpClient in multi-geo #9779

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2 of 9 tasks
svermaak opened this issue Jun 27, 2024 · 2 comments
Open
2 of 9 tasks

SPHttpClient in multi-geo #9779

svermaak opened this issue Jun 27, 2024 · 2 comments
Assignees
Labels
Needs: Author Feedback Awaiting response from the original poster of the issue. Marked as stale if no activity for 7 days. Needs: Triage 🔍 Awaiting categorization and initial review. sharepoint-developer-support sharepoint-developer-support type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.

Comments

@svermaak
Copy link

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

Windows

What browser(s) / client(s) have you tested

  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)

Additional environment details

  • browser version
  • SPFx version
  • Node.js version
  • etc

Describe the bug / error

Using SPHttpClient in a multi-geo setting fails to get successfully retrieve"/_api/web/AllProperties" from site in TenantB on a site in Tenant A.

Steps to reproduce

This line in SPFx, running in webpart on site in TenantA
const response: SPHttpClientResponse = await spHttpClient.get(${siteUrl}/_api/web/AllProperties, SPHttpClient.configurations.v1);

Executed with site url that is a site in TenantB

Expected behavior

Properties successfully retrieved irrespective on cross tenant execution

@svermaak svermaak added the type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs. label Jun 27, 2024
@VesaJuvonen VesaJuvonen added the Needs: Triage 🔍 Awaiting categorization and initial review. label Jul 29, 2024
@Ashlesha-MSFT
Copy link

Hello @svermaak,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

@Ashlesha-MSFT
Copy link

@svermaak,
I’ve tested the same scenario in a multi-geo SharePoint Online setup using SPFx, and I was able to successfully retrieve:
/_api/web/AllProperties
from a site in Tenant B, while running the SPFx web part in a site from Tenant A, using SPHttpClient.

Just to better understand the issue — could you please share if you're seeing a specific error message or HTTP status code when the call fails?

@Ashlesha-MSFT Ashlesha-MSFT self-assigned this Jun 12, 2025
@Ashlesha-MSFT Ashlesha-MSFT added sharepoint-developer-support sharepoint-developer-support Needs: Author Feedback Awaiting response from the original poster of the issue. Marked as stale if no activity for 7 days. labels Jun 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Author Feedback Awaiting response from the original poster of the issue. Marked as stale if no activity for 7 days. Needs: Triage 🔍 Awaiting categorization and initial review. sharepoint-developer-support sharepoint-developer-support type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
Projects
None yet
Development

No branches or pull requests

3 participants