Microsoft School Data Sync and OneRoster API

Joshua Townley
Joshua Townley
Facilitator 1 Kudos 1 First Anniversary
in Education Management APIs

Hello,

We've set up a connection for Microsoft SDS using the API, however, each sync shows a bunch of warnings due to the phone numbers being formatted incorrectly. Microsoft requires the E.164 format including the plus symbol and country code, but the OneRoster export doesn't include it unless we were to explicitly put it in Core. And having phone number validation on in the User Profiles seems to remove it anyway.

Is there a way to do this without a manual intermediate transformation step prior to loading into SDS? Just wanted to check!

Answers

  • Crystal Bruce
    Crystal Bruce admin
    Tenth Anniversary Kudos 5 Commented in Discussion First Reply

    Hey @Joshua Townley I moved this over to Education Management APIs. I'll also check with my team to see if we can help!

  • Stephen Boyle
    Stephen Boyle Blackbaud Employee
    Tenth Anniversary Kudos 5 First Reply Name Dropper

    The introduction of an error for phone formatting conflicts is new to the SDS/OneRoster integration. There haven't been any communications from Microsoft about changing their requirements - to my knowledge. So, this may be an unintended result from some other change.

    When we worked with Microsoft on the SDS compatibility, this was not an issue. And Blackbaud is compliant with the requirements specified by the OneRoster spec. I will connect with MS's SDS team to see what changed and if it's intended.

  • Joshua Townley
    Joshua Townley
    Facilitator 1 Kudos 1 First Anniversary

    Thanks Stephen!

  • Stephen Boyle
    Stephen Boyle Blackbaud Employee
    Tenth Anniversary Kudos 5 First Reply Name Dropper
    edited March 25

    It looks like School Data Sync service has made some changes, including dropping support for the API and integrating via the CSV file exports only. This phone format change must have come through at the same time. I'll see how we can update the setup for OneRoster to accommodate this formatting requirement. I do not have a time frame for this work, but I will get it in front of the team.

Categories