Issue with Microsoft Groups not syncing for SharePoint Site

I hit a strange issue this week but today had that massive buzz of solving it. Sometimes it is the simple things that you've missed but other times (like this one), it is something very odd. The problem was that I had a set of around 1000 migrated sites that had come from SharePoint 2010 and should have been set up as Modern sites. They appeared to be but the SharePoint Groups had retained the old names, i.e.

  • Site Owners
  • Site Members
  • Site Visitors

I was expecting the groups to have the name of the site in there, i.e. if my site was called "My New Site" then the groups would be:

  • My New Site Owners
  • My New Site Members
  • My New Site Visitors

As I was investigating, I noticed that some of the sites had started to get the new names. At this point, I thought I was going mad but as I had taken notes, I knew that something had changed and it wasn't just my goldfish level memory. I eventually realised that if I browsed to Site Permissions from a Modern Home page then something happened along the way that triggered the correction.

My next step was to check PnP PowerShell to see if the sites needed Groupifying but running the command Add-PnPMicrosoft365GroupToSite told me that they were already associated with a Group.

Finally, I got developer-y and opened up the Chredge Dev Console to look at which REST calls the page made when it hit the Site Permissions page. This is when I discovered a POST call to /_api/GroupService/SyncGroupProperties and this sounded promising. I fired up Invoke-PnPSPRestMethod and made a call to a site that happened been manually fixed yet and by magic, it worked! This certainly saved a very dull day of manually clicking several hundred site permission links.

I should say that I cannot find this API documented anywhere so this does not appear to be a fully supported API but if this post saves someone a day or several days of clicking on sites then I'll be a happy person.

Photo courtesy of Toa Heftiba via Unsplash

Next post

Do you need a standalone device for Teams? - Evaluating the Lenovo ThinkSmart View

Lenovo Think Smart View

A few weeks back, I was lucky enough to have been given the opportunity to try out the Lenovo ThinkSmart View, a standalone device dedicated to Microsoft Teams. Many of you may be thinking "erm, why would you want that?" and the simple answer (which I'll expand on in a minute) is performance. Too many times has Teams rendered my machine unusable and I spend a large chunk of my day in meetings. Would this improve my experience?


Previous post

Sharing the etiquette of Microsoft 365


Last week, myself and my fellow co-hosts of GreyHatBeard were joined by Luise Freese, Vesa Nopanen and Karoliina Kettukari at Collab Days Munich/Vienna as we shared our thoughts on the etiquette of Microsoft 365. It was a fun format with plenty of chance to laugh at the same time as attendees picking up some great ideas as we ran through three questions that each person had 90 seconds to answer.