Forum Discussion
User In Owner Role - No Search Results
MicrosoftI just tried creating a new private teamsite from sharepoint home/portal. Added an extra user as owner in the creation process. But searching with the extra user added as additional owner worked in the private modern team site.
Am I doing this wrong, could you provide some additional steps on how you added the extra user only as owner of the group?
This problem occurs when I add a user to the Owners role of the Office group in either, the O365 Admin Center Group page or in Azure AD Group management page. By using these tools, the account does not get assigned automatically to the Member Role also.
- Geir-Magnus Pettersen
I am seeing the same behavior as you describe. The question is if this behavior is by design because of some unknown reason for private groups. Did you have a support case going for this? If not I can dig up with provisioning teams on if there is a good reason for this behavior.
Queries to search does not complain about errors as far as I can see, but there are not returned any results for the private group owner.
Yes, i do have a support ticket open. The engineer is insisting that it is by design, but when SP shows a user has full control, they should be getting search results, SP has worked like this for 15 years. The Privacy setting should only affect external system access and should not have any affect on searching when conducted within the site.
Hi,
I can also confirm this behavior. I discovered this issue when creating a hub site. The News Web Part on the Hub site home page was not delivering results from all associated sites as expected. Please see my discussion on this issue: https://techcommunity.microsoft.com/t5/SharePoint/Strange-behavior-in-Hub-site-permissions/m-p/214457.
After re-adding the user to the site, the search result is appearing as expected.
And I agree with Dean. If the user has been granted Owner role on the site, search results should be delivered accordingly.
If the users added to the new Group site through other tools than within SharePoint itself results in this behavior, then for me this sounds like a bug, and not by design.
