Microsoft 365 School Data Sync (SDS) doesn't create Class SharePoint sites automatically

[AGA]

We've been using the Microsoft 365 School Data Sync for a number of years to sync our classes from SIMS to Teams via the csv uploads.

This works well, but we've noticed that when a team is created for each class, the connected SharePoint site for each team isn't created automatically.
 

Because of this, when the teacher activates the class they are unable to start setting up the class notebook.
It shows the message "We're still setting up your class. Please check back soon."
This is presumably because it needs to be saved into the connected SharePoint site.
 

Another symptom is that the class's home page will show the tenant home page instead of the class's.

 

The method we have found that triggers the SharePoint site's creation, is to click on the 'files' tab of the team's general channel.

An error message will be displayed at first (because the SharePoint site doesn't exist yet), but after clicking away to another tab and back again, the site will have been created.

This is confirmed when looking under 'active sites' in the SharePoint admin centre. It will appear.

Once this has been done it allows the class notebook to be setup as expected and the site's own homepage is displayed.

 

My question is if anyone else has encountered this?

And if so, does anyone know how it might be possible to trigger this for all our classes in bulk? Possibly using PowerShell?
We have raised it with Microsoft, but we all know how fruitless that is.

 

Thanks

Edited September 5, 2025 by AGA

[lparry]

We haven't had that exact issue but this year has been painful. Your best bet is probably to wait for Microsoft as they acknowledged to us they are aware of the issues of class teams and how the process failed due to the amount of demand and was able to provide a PowerShell script to resolve.

 

In our case, the sharepoint site existed however the permissions on any of the default apps (EDU assignments etc.) hadn't been assigned so each team needed them resetting.

 

I sadly don't have the script to share but I did modify this one as a test for a single team and it appeared to work but YMMV. 

[AGA]

Thanks. We aren't using the PowerShell method, so our case is slightly different from most in that thread.

I had a look through the scripts used and couldn't identify a specific part that would align with our needs without concern that it'd break something else or involve starting from scratch.

Noted though that this replier has had the same 'fix' that we stumbled across given to them by MS Support, but it's far from ideal.