Finally, its out! We were able to present our prototype app for the open source technology Fluid Framework at the @Microsoft Build Conference. What it means to work behind the scenes at the cutting edge of #technology, I share here: https://t.co/8D0wnCWuXA
@SchauDK@Office365Health Okay, yes we are seeing that as well. But no issues with the old SharePoint App Only apps registered via appregnew.aspx. So the 503 only goes for Azure AD App.
@mikaelsvenson@baskb Ticket has been created. Since you are close to the "source" maybe you can speed up things a little bit ;) So here is the ticket number:18845862 (Although of course we all love collecting fiddler traces ;) )
@mikaelsvenson Here is a question for you: In SPO I am the owner of a group. In the group connected site, I create a listitem and only grant read permissions to the SharePoint (associated) owner group for that item. Why can't I find that item via search in SharePoint? 1/2
@mikaelsvenson@baskb At least the security trimming within SharePoint works perfectly right. I can see everything as expected. So I guess the claim is stored on them, it is just search not handling things correctly.
@mikaelsvenson@baskb Yes true, the problem is not just with a simple item though. If you want to add a library to your site that is only visible for the owners of that site, all items in that library are not visible in search as well. And that is quite a commen scenario in the real world...
@mikaelsvenson Just so I did understand that correctly: If the user/claim has IsHiddenInUI flag set in SharePoint, search will not pick that up and the security trimming of search is not working in the expected way? That sounds like a bug to me, because technically I am allowed to see the item
@mikaelsvenson@mikaelsvenson could it be because the owner claim of the o365 group is hidden where as the member claim is not? So basically the sharepoint owner group looks empty. If I add myself to the sharepoint owner group it is working as expected. DM me if I should show you the issue.
@mikaelsvenson And it does not matter if the group is private or public. I could reproduce that on multiple tenants. I have 3 more items in there. One that inherits permissions, one where sp member group has read permissions and one where owner and member have read access. All show up in search
@mikaelsvenson The list itself is inheriting permissions. But permissions are broken on a single list item. All permissions on the item were removed and then I added the sharepoint owner group (containing the owner claim of the o365 group) with read access to that item. That's all.
The Future is Fluid
https://t.co/J19a1cZZFt
Seamless collaboration coming across Office, Outlook, Teams, SharePoint . . . the Fluid protocol connects to nextgen SharePoint storage and uses the #SPFX toolchain
#MSIgnite#Microsoft365#SharePoint#OneDrive
Great buzz and excitement at Fluid #SPFx DevKitchen while attendees start building their own solutions. Already invaluable input from attendees towards our designs.