User Profile
pieterheemeryck
Brass Contributor
Joined Sep 07, 2016
User Widgets
Recent Discussions
Private channel creation in a multi geo tenant
Consider this: we create an O365 group via the Graph API (application permissions) where the geo location of the user creating the group is taken into account (e.g. Europe is the central location, North America is the satellite location). See the docs on https://docs.microsoft.com/en-us/microsoft-365/enterprise/microsoft-365-multi-geo?view=o365-worldwide. We then make a MS Team out of this O365 Group. When we create a private channel using the Graph API (application permissions), a new SharePoint site collection (SC) is created. Will this new SC be created in the same location as the SC of the Team the private channel was created in ? I'm assuming it is as it makes the most sense. I'm also hoping it is as it is a customer requirement, but hard to verify for me personally. Is there someone who can share their knowledge on this ?Solved1.2KViews0likes2CommentsAndroid SharePoint mobile app - localStorage is reused when switching accounts
Hi, I've verified that when you switch accounts, the localStorage is reused. I have a simple SPFx component on a SP page that uses localStorage. It shows cached data from the previous user after switching accounts. The expected behaviour would be that there is a localStorage for each account you log in for. For example, on the desktop Chrome browser, you will have the same localStorage data available for a site if you login with different web logins, but once you switch to a different persona or Google account, the localStorage points to a different folder on your device, effectively keeping the localStorage separated for multiple accounts. To me, it seems that switching accounts on the SharePoint mobile app should also make sure you are not reusing the other account's localStorage... Any thoughts on this?620Views0likes0CommentsTeams custom personal app (SPFx) - slow authentication startup in desktop app
Hi We've implemented quite some Teams personal apps at clients now and the custom Teams apps in the (Teams desktop app) sometimes have load times ranging from 4s - 10s before our custom code even begins. The Teams web app handles auth in a different way, so never any issue there. It appears to have something to do with the way authentication is done in the desktop app (acquire OBO token call...). With a trick, you can also get the console & network tab to show in the desktop app. That way we can verify when our React is loaded & starting + when our backend api calls are done. Clients are complaining about the response times and rightfully so. The response times before our code hits also varies greatly between tenants as mentioned. Has anyone had the same experience? Is there a magic wonder solution out there that I don't know of yet (e.g. simple AAD authentication setting) ?2.3KViews0likes2CommentsCannot add certain apps in non public Teams created by Graph API
We found a very strange issue at several tenants, regarding Teams creation via the Graph API: when a new Team is create with the Graph API, which has Visibility != "Public", in the created Team you cannot add the Flow app (and possibly other apps will have the same issue...). When a new Team is set to Public, the issue does not occur. When creating Teams via the default user interface, the issue does not occur, neither for Public nor Private Teams. What I've tried so far (and still gives the issue): Creating a Group OOTB and extending it with a Team Using PUT /beta/groups/.../team to extend with a Team Using POST /beta/teams to create the Team directly, instead of extending a group Cloning an OOTB Team using the Graph API ... It seems that anything that's being done with Graph API which creates / changes to a non public Team has the issue. Also: https://github.com/microsoftgraph/microsoft-graph-docs/issues/7567981Views0likes0Comments
Recent Blog Articles
No content to show