SDS V1 CSV File Format

You can use CSV (comma-separated value) files in the SDS V1 format to sync your School Information System (SIS) with Office 365. Using the SDS V1 CSV file format to ingest the data categories below enables you to light up core SDS capabilities for provisioning. It also helps you enhance experiences for the Microsoft 365 products and features.

If you're using the SDS V1 format, the files must be appropriately formatted. Upload the files, named exactly as detailed below. Column headers are case-sensitive. CSV files must be in UTF-8 format and RFC compliant. Also we don't accept line breaks in incoming data. To review and download sample set of SDS V1 CSV files, see the SDS GitHub Repository.

Required: The three files listed below must be selected before you can progress. If you're only managing users and not classes, you only need to supply these files.

• school.csv

• student.csv

• teacher.csv

Optional / Required: Not required if you're only managing users. If you're also managing classes and class enrollments, you need to provide the three files listed below, along with the three files above. If you're not, don't select any files with these names.

• section.csv

• studentenrollment.csv

• teacherroster.csv

Optional: These aren't required to proceed but may enhance experiences. If one of the files below is selected the other must also be selected to proceed.

• user.csv

• guardianrelationship.csv (Requires user and student record to build contact association.)

Each CSV file must contain data for the fields noted 'Yes' under 'Required', the fields noted 'No' are 'Optional' data. The field headers marked as 'Required' must exist in the supplied files or they won't be accepted. The field headers marked as "Optional' aren't required to be present in the files if not passing the corresponding optional data.

The fields with defined enumerated values as marked in the 'Data Types' column have a specific set of values they support. The supported set of default values for Enum fields see Default List of Values.

school.csv

• All organizations listed will be set to the organization type 'school'.

student.csv

• Requires a reference to the associated school using the 'School SIS ID' field. This produces a dependency on the school.csv file.
• All users listed will be set to the role type 'student'.
• Expect date values to be supplied in ISO8601 format.
• Leading zeros ‘0’ missing on incoming value for Grade Level ENUM, for example ‘1’, will match defined List of Value (ENUM) ‘01’ and will be stored as ‘01’.

teacher.csv

• Requires a reference to the associated school using the 'School SIS ID' field. This produces a dependency on the school.csv file.
• All users listed will be set to the role type 'teacher'.
• Leading zeros ‘0’ missing on incoming value for Grade Level ENUM, for example ‘1’, will match defined List of Value (ENUM) ‘01’ and will be stored as ‘01’.

section.csv

• Requires a reference to the associated school using the 'School SIS ID' field. This produces a dependency on the school.csv file.
• If Term information is needed recommend moving to SDS v2.1 CSV format and also providing academicSessions.csv file.

studentenrollment.csv

• This requires a reference to the associated section using the 'Section SIS ID' field. This produces a dependency on the section.csv file.
• This requires a reference to the associated user using the 'SIS ID' field. This produces a dependency on the student.csv file.

teacherroster.csv

• This requires a reference to the associated section using the 'Section SIS ID' field. This produces a dependency on the section.csv file.
• This requires a reference to the associated user using the 'SIS ID' field. This produces a dependency on the teacher.csv file.

user.csv

• If you're also syncing Contact Relationships (guardians), you must include a record for them in the user.csv.
• Expect phone field to be formatted based on the E.164 standard where the plus character is used and succeeded by the phone number, or rather the plus character followed by country code, area code, telephone prefix, and line number.

guardianrelationship.csv

• If you're also syncing Contact Relationships (guardians), you must include a record for them in the user.csv.
• This requires a reference to the associated user using the 'Email' field. This produces a dependency on the user.csv file.
• This requires a reference to the associated user using the 'SIS ID' field. This produces a dependency on the student.csv file.
• If Role value isn't supplied the relationship value defaults to 'userContact'.