Microsoft School Data Sync in higher education: where colleges outgrow it

Microsoft School Data Sync (SDS) is often the first thing a Microsoft 365 administrator tries when a college asks for class teams generated from the student information system. It is free, it is built by Microsoft, and for many schools it does exactly what is needed.

Questions usually start in the second or third term. A registrar asks why one cross-listed course has three teams, the help desk is flooded during add/drop, or the privacy officer asks who changed a team's membership and why. This article is a fair look at where SDS fits in higher education, where it stops, and how to decide what your institution needs.

What does Microsoft School Data Sync do?

SDS is a service included with Microsoft 365 Education. It reads roster data from your SIS, either as CSV files or through connections offered by supported SIS providers, and uses it to create and update users, groups and classes in Microsoft Entra ID and Microsoft 365. Those classes become the class teams teachers and students see in Microsoft Teams, with Class Notebook, Assignments and Grades available inside.

SDS was designed around the K-12 model: a school year, a class taught by one teacher, a fairly stable list of students and a district-level SIS. Within that model it is a solid, low-cost foundation, and it is Microsoft's recommended starting point for schools on Microsoft 365 Education.

Microsoft updates SDS regularly, so check its current documentation for the file formats and connectors it supports. The principles in this article hold whatever the version.

Where does SDS fit well?

SDS is a good choice when your situation looks like most of the rows below.

If that describes your institution, SDS may be all you need, and paying for something else would be hard to justify. The considerations that differ between schools and higher education are also covered on the Teams for schools page.

Why do colleges and universities outgrow SDS?

Higher education adds structure that the K-12 model does not carry. The gaps tend to show up in six places.

• SIS connectivity. Omnivox, Clara and COBA in Quebec, and Banner, PeopleSoft Campus Solutions, Workday Student and Jenzabar elsewhere, rarely produce SDS-ready files out of the box. Someone has to extract, transform and validate the data before each sync.
• Cross-listed and multi-section courses. SDS treats each class as its own team and has no built-in way to merge five sections taught by one instructor into a single class team. The problem is detailed in cross-listed sections in Microsoft Teams.
• Add/drop churn. Colleges see heavy enrollment changes during the first weeks of every term, two or three times a year, plus continuing-education cohorts that start on other dates. Sync frequency and the handling of removals matter more than at a school with one school year.
• Roles beyond teacher and student. Co-instructors, teaching assistants, lab supervisors and course coordinators need different rights, and the rules often vary by department.
• End-of-term policies. Institutions want to archive, hide or keep teams by term and by program, in line with their retention rules, rather than run a single cleanup step.
• Audit trails for privacy law. Under Quebec's Law 25 or the GDPR, institutions must be able to show who changed a team's membership, when and why. The general Microsoft 365 audit log records what changed and which account made the change, but it does not link that change to the SIS event that justified it, and its retention depends on your license.

None of these points is a flaw in SDS. They are simply outside the problem it was designed to solve.

What does stretching SDS cost?

When an institution keeps SDS and works around these gaps, the work does not disappear. It moves to people:

• IT maintains transformation scripts that turn SIS exports into SDS files, and adapts them whenever the SIS changes.
• Teachers build their own merged teams for multi-section courses, which then drift away from the official rosters.
• The help desk absorbs add/drop tickets between sync runs.
• Term-end cleanup is done by hand, or not at all, and old teams accumulate.
• Audit evidence is assembled manually when someone asks for it.

The license is free; the people time is not. It is worth estimating that time honestly, using your own section counts and ticket volumes, before deciding either way.

What doesn't work

Some workarounds look reasonable but create new problems.

• Pre-merging sections in the import files. Combining sections into one class before import gives one team, but the team no longer knows which student belongs to which section, and every enrollment change has to be merged again.
• Running two sync engines on the same teams. SDS plus a script, or SDS plus another tool, editing the same class team means each one overwrites the other's changes.
• Asking teachers to fix membership. Manual adds and join codes bypass the SIS, are rarely reversed when a student drops, and leave no record of why.
• Waiting for the next full import. Nightly or weekly re-imports leave gaps during add/drop, exactly when students and teachers need accurate rosters.

How to decide: a checklist

Answer these questions for your institution. The more of them you answer with yes, the more work SDS will leave to your team.

1. Does your SIS need custom transformation to produce the files or connection SDS expects?
2. Do instructors teach several sections, or cross-listed courses, that should share one team?
3. Do enrollments change heavily during add/drop, more than once a year?
4. Do you need roles beyond teacher and student, set by department?
5. Do you need different end-of-term rules by program or by term?
6. Must you show, for any membership change, whether it came from the SIS or from a person?
7. Does your IT team already maintain scripts around SDS?

If you answered yes to several, compare the options side by side:

How Teameo extends what SDS started

Teameo is built as the higher-education extension of what SDS does for K-12. It uses the same building blocks, Microsoft Entra ID accounts and Teams for Education class teams with Class Notebook, Assignments and Grades, so teachers and students keep working in the Teams they already know.

What changes is the layer between the SIS and Teams. Teameo connects natively to the higher-education SIS platforms listed on the Teams SIS integration page, syncs enrollments in real time or on a schedule, merges cross-listed sections into one class team, and applies your end-of-term policy: soft archive, hard archive or hide. Every provisioning, enrollment and archive action is timestamped and tagged with its actor, to support Law 25 and GDPR accountability.

During a transition, SDS and Teameo can run side by side as long as each class team is managed by only one of them. Most institutions then let Teameo take over class provisioning entirely. The feature-by-feature comparison is on the School Data Sync alternative page, the step-by-step setup is in how to sync your SIS with Microsoft Teams, and the full product is described on Microsoft Teams for Education.