Forum Discussion
Search API with Application Permissions returns no results, Delegated permissions do
As if SharePoint Search simply started running dry (I reckon because of crawling started returning nothing, from time to time, with no results anymore in the end?)
I've tried Free Microsoft Support, but they only support out-of-the-box issues (fi not being able to log in to SharePoint, or something like that).
I've tried creating a Pay-Per-Incident, but I'm unable to add a subscription over there.
Leading all support to a dead end.
- butchersoft585Sep 13, 2022Copper Contributor
We have as you would expect raised it with Microsoft Support but it will take days to escalated this to a level where someone will actually understand the issue.
Microsoft appear tp have been having issues with Search for the last few months and the SLA of 25QPS per tenant is actually more like 5QPS and now appears to have been switched off completely. I read that it was something to do with the OneDrive content also bein queries as part of the same index and this was the cause. To this effect I believe they have now added a Site.Selected as an new permission level.
Today,
- delegated search as a user works
- App registration via Azure AD returns 0 results
- SharePoint Admin App Registration returns 0 results
- Site.Selected registration (add a list of sites) yet to be tested
We are going to try remove MFA today for a group of users and run each search through the pool of users cycling through the list to ensure we don't get throttled. A lot of work for something that the is no documentation to day its broke.
In the mean time today as I know it works as a delegated user I will create a pool of users
- butchersoft585Sep 13, 2022Copper ContributorProbably worth mentioning that the problem exists with (all tested and failed)
- Microsoft.SharePoint.Client.dll
- Pnp.Search
- REST API directly
All user the same endpoint at the end of the day.- StevenDeRooverSep 13, 2022Brass Contributor
I also created a . NET core console application to test an HTTP call directly to the API (to test without packages, like Pnp), with both GET and POST.
Both HTTP verbs have the same results in respect of application and delegated permissions.
In other words: switching to POST instead of GET does not solve the issue.