People Search REST API 401 Response

[kristen-argent]

Target SharePoint environment

SharePoint Online

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

SharePoint REST API

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

Hitting the API in any way

Describe the bug / error

We have developed an application that makes use of the rest search API - until Tuesday 6th of May this was working well in all environments.

Since then it has ceased working in some environments (Australian) and is now returning a 401 Unauthorized response.
It continues to work in two of our tenants (US based)

We use sourceId=B09A7990-05EA-4AF9-81EF-EDFAB16C4E31.

The query is being run by the application entra id, not using a user token.
Hitting search api without the source id filter also works correctly.

Steps to reproduce

Request URL with app token.

https://___.sharepoint.com/_api/search/query?sourceid='B09A7990-05EA-4AF9-81EF-EDFAB16C4E31'&querytext='*'

Expected behavior

Search results to return

Refer to closed ticket:
#10246

[Ashlesha-MSFT]

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

[Ashlesha-MSFT]

@kristen-argent,
We are unable to reproduce the issue.
It’s possible that the fix is still propagating across all regions and tenants. I recommend allowing some time for it to fully roll out to your specific environment.

[kristen-argent]

@Ashlesha-MSFT - referring to the information I provided in my earlier ticket #10246 - this issue definitely has not been resolved.

It is an issue in only some of our tenants - earlier this week in that issue you stated it had been raised as a bug in the engineering team, did they roll out a fix for it?
It’s affecting us and also a client and based on the comments on the other ticket I don’t think a fix has been pushed through?

[kristen-argent]

@Ashlesha-MSFT all of our tenants are now impacted by this issue

[f0oster]

Facing this same issue, authenticating with certificate (no user context - app auth) and also using SourceID b09a7990-05ea-4af9-81ef-edfab16c4e31.

Issue first discovered May 10th at 19:07 GMT +11) when a weekly maintenance script failed to run.

Our tenant location and data location is Australia / Australian data centers.

[DmitriyVdE]

Hi,

I'm also facing this issue on a customer's tenant, and can reproduce this on our test tenant.
Specifically when using the Result Source ID 'b09a7990-05ea-4af9-81ef-edfab16c4e31' the API returns a 401 error.
When running the same query without a Result Source ID the query runs fine, but of course doesn't return any results.

Both tenants run in West Europe.

[f0oster]

@Ashlesha-MSFT has there been any progress on this issue?

[kristen-argent]

@Ashlesha-MSFT has there been any progress on this issue?

An update would be great, its been broken for a month now and the first ticket I opened was closed even though it was confirmed as a bug. We have tickets open directly with Microsoft but they aren't much help at all unfortunately.

[Ashlesha-MSFT]

@f0oster, @kristen-argent,
Thanks for following up. There’s no new update from the engineering team yet. We understand how frustrating this ongoing issue is, especially given the previous ticket closure.

We’re actively tracking it and will share any progress as soon as we hear back. Appreciate your patience in the meantime.