建立具有學校資料同步處理的類別團隊Creating Class Teams with School Data Sync

[學校資料同步處理(SDS)] 一次提供選項來建立同步處理的每個類別的 M365 群組和類別小組!!School Data Sync (SDS) once again provides the option to create both the M365 Group and Class Team for each class synced!! 在2020年3月的部署中,該功能已從 SDS 中移除,但在 COVID 期間部署為空前的程度,我們現在已將其新增回來。The feature was removed from SDS in March 2020 due to unprecedented levels of deployment during to COVID, and we’ve now added it back. 下列文章說明 SDS 用來建立類別群組的處理常式,以及當系統管理員選擇從 SDS 建立類別群組和類別群組,以及選擇只建立 M365 群組時,所產生的最終使用者經驗。The article below describes the process SDS uses to create Class Teams, and the resultant end user experience if admins choose to create both Class Groups and Class Teams from SDS vs choosing to create just the M365 Groups.

SDS 如何建立類別小組How SDS creates Class Teams

下列程式說明 SDS 如何在同步處理類別和名冊時建立類別小組。The process below describes how SDS creates class teams when classes and rosters are synced.

步驟1:資料攝取Step 1: Data Ingestion

SDS 支援使用 OneRoster API 連接器或透過其中一個支援的 SDS 格式傳送 CSV 檔案的 ingesting 資料。SDS supports ingesting data using OneRoster API connectors or by sending CSV files in one of the supported SDS formats. 若要建立類別小組,SDS 需要您至少提供使用者、類別和名單資料,以協助後續步驟中所述的 E2E 布建程式。To create Class Teams, SDS requires you to provide user, class, and roster data at a minimum, to facilitate the E2E provisioning process described in subsequent steps. 在此資料攝取過程中,SDS 會執行一系列的資料驗證檢查,以確保來源系統 APIs 可供存取、CSV 標頭的格式正確,且類別和使用者之間的名單識別碼對應正確。During this data ingestion process, SDS performs a series of data validation checks to ensure source system APIs are accessible, CSV headers are properly formatted, and the roster ID mappings between the classes and users is correct. 驗證資料後,錯誤的資料將會在 [錯誤] 區段中捨棄並加以報告,而剩下的「正確資料」會送出以進行處理,並同步處理至 Office 365。Once data is validated, erroneous data will be discarded and reported within the errors section, and the remaining “good data” is submitted for processing and synchronization to Office 365.

步驟2:同步使用者Step 2: Sync Users

在 SDS 可以建立群組並新增成員資格之前,必須先同步處理來源系統中的所有使用者,並將其對應至 Azure AD 中其對應的使用者帳戶。Before SDS can create groups and add memberships, it must first synchronize all the users from the source system and map them to their corresponding user account in Azure AD. 如果您是已存在的使用者,且您在 [同步處理設定檔設定] 嚮導中選取 [同步現有的使用者] 選項,SDS 會使用稱為身分識別的處理常式,將來源系統屬性對應至 Azure AD 使用者屬性。If you are users already exist and you select the Sync Existing Users option in the sync profile setup wizard, SDS uses a process called Identity Matching to map source system attributes to Azure AD user attributes. 一旦對應,每一位使用者便會在 Azure AD 中取得錨定識別碼擴充屬性,其中包括來源系統的唯一和持續 SIS 識別碼。Once mapped, each user gets an Anchor ID extension attribute in Azure AD, which includes the unique and persistent SIS ID from the source system. 如果您在同步處理設定檔中選取 [建立新使用者] 選項,則 SDS 會根據提供的資料建立使用者帳戶,並在 [同步處理設定檔設定] 嚮導內指派對應的授權集。If you select the create new user option in the sync profile, SDS will create the user accounts based on the data provided and assign the corresponding license set within the sync profile setup wizard. 同步處理使用者是 SDS 中每個後續的布建功能和步驟的基礎步驟。Syncing users is foundational step for every follow-on provisioning feature and step within SDS. 如果有任何使用者因錯誤而無法符合身分識別或同步處理,SDS 將無法將該使用者的成員資格新增至類別群組或類別小組。If any user fails to match identities or sync due to errors, SDS will not be able to add the memberships for that user to the Class Group or Class Team.

步驟3:在 Azure AD 中建立類別群組Step 3: Create Class Groups in Azure AD

在同步處理所有使用者之後,SDS 可以在 Azure AD 內建立 M365 群組。Once all the users are synced, SDS can create the M365 Groups within Azure AD. SDS 所建立的群組不同于使用者所建立的 M365 群組,或使用 M365 系統管理入口網站或 PowerShell 時由系統管理員所建立的群組。The groups created by SDS are not the same as M365 groups created by end users or those created by an Admin when using the M365 Admin portal or PowerShell. 主要差異包括:Key differences include:

  1. 將 Visibility 選項設定為隱藏成員資格Visibility option set to hidden membership
  2. 自訂建立選項Custom Creation Options
  3. 自訂資源行為選項Custom Resource Behavior Options
  4. 來來源資料的自訂副檔名屬性Custom extension attributes from the source data

步驟4:新增群組擁有者和成員Step 4: Add Group Owners and Members

在 Azure AD 中建立群組之後,SDS 可以根據攝取階段中提供的類別註冊資料,新增擁有者和成員。After the groups are created in Azure AD, SDS can add the owners and members based on the class enrollment data provided during the ingestion phase. 如果使用 OneRoster API 進行同步處理、PowerSchool API、SDS V1 CSV 或聰明 CSV 格式,SDS 會在每個 M365 群組上新增教師做為擁有者。If syncing using OneRoster API, PowerSchool API, SDS V1 CSV, or Clever CSV format, SDS will add the teachers as an owner on each of their M365 Groups. 如果使用新的 SDS V2 格式進行同步處理,SDS 會新增每個類別的任何教職員工角色,如 enrollments.csv 檔案中所述,做為群組擁有者。If syncing using the new SDS V2 format, SDS add any staff roles for each class, as detailed in the enrollments.csv file, as group owners. 學生永遠新增為群組成員。Students are always added as group members. 群組中的擁有者和成員角色會決定每位使用者在群組和連結的小組中所擁有的許可權。The owner and member roles within the Group will determine the permissions each users has within the Group and linked Team.

步驟5:從類別群組建立類別小組Step 5: Create Class Teams from Class Groups

將所有擁有者和成員新增至 Azure AD 中的 M365 群組之後,SDS 即可開始建立類別小組。Once all the owners and members are added to the M365 Group in Azure AD, SDS can begin Class Team creation. 建立小組時,會從 M365 群組建立小組,擁有者和成員將會反映包含在 M365 群組上的群組。When creating Teams, they are created from the M365 Group, and owners and members will mirror those included on the M365 Group. 若要建立小組,SDS 會將建立小組以非標準的基本範本張貼至 MS GRAPH APITo create the Team, SDS posts the Create team with a non-standard base template to MS Graph API. 這是公開提供的 API,供自訂布建應用程式和 PowerShell 腳本使用。This is a publicly available API, for use by custom provisioning apps and PowerShell scripts.

當部署以 COVID 的 led 學校的形式增加至遠端教學部署時,SDS 傳送至此小組 API 的要求量會變大,而且會導致移除 SDS 中的「Teamify」功能。When deployments increased globally as COVID led Schools to Remote Learning deployments, the volume of requests SDS was sending to this Teams API was overwhelming and led to the removal of the “Teamify” feature in SDS. Microsoft 已開始對 API 產生顯著的效能與可靠性改進功能,讓 SDS 將小組建立重新加入產品中。Microsoft has since made significant performance and reliability improvements to the API, allowing SDS to add Team creation back into the product. SDS 包含各種功能,例如限制回退、會話穩定性,以及使用 PowerShell 腳本無法輕易複寫的錯誤處理方式。SDS includes a variety of features like throttling backoff, session stability, and error handling which are not easily replicated using PowerShell scripts. 如此一來,Microsoft 建議您在部署類別小組時使用 SDS,以確保一致、可性能且可靠的結果。As such, Microsoft recommends using SDS when deploying Class Team to ensure a consistent, performant, and reliable outcome.

根據預設,SDS 會針對每個類別和區段建立類別小組,但是同步處理設定檔設定中有一個可用的選項,可讓您略過此步驟。By default, SDS will create Class Teams for each Class and Section synced, however there is an option available within the Sync Profile setup that allows for this step to be skipped. 如果您選擇只建立 M365 群組,而不同時建立群組和小組,則教師可以遵循講師指導小組建立流程,以從 SDS 建立的 M365 群組手動建立其團隊。If you choose to only create the M365 Groups and not create both the Group and Teams, Educators may follow the Educator-Led Team Creation flow to manually create their Teams from the SDS created M365 Groups.

步驟6:啟動類別小組Step 6: Activate Class Teams

建立類別小組後,小組擁有者就必須啟用類別。Once Class Teams are created, the Classes will need to be activated by the Team Owner. 團隊內部的啟用程式可讓 Azure AD 中所儲存之 M365 群組內的所有學生成員與類別小組同步處理。This activation process within Teams allows all student members within the M365 group stored in Azure AD to sync to the Class Team. 此程式可讓類別小組出現在學生的小組清單及儀表板內,也可以開始使用類別小組。This process allows the Class Team to appear within the student’s Team list and dashboard, and they may begin using the Class Team. 在啟動之前,學員會在非使用中的類別小組的教育版視圖中顯示為擱置中的使用者,而且在準備好要提供他們存取權的情況下,才能夠查看或與類別小組互動。Before activation occurs, students will be shown as pending users within the Educators view of the inactive Class Team, and wont be able to see or interact with the Class Teams until the educators are ready to provide them access. 一旦啟用,SDS 將繼續更新及管理 Azure AD 中的 M365 群組內的成員資格。Once activated, SDS will continue to update and manage memberships within the M365 Group in Azure AD. 在 Azure AD 中對 M365 群組成員資格所做的所有成員資格變更都會透過名為「轉寄同步處理」的處理常式與連結的類別小組同步處理,而這會針對 Office 365 內的所有群組和小組All membership changes to M365 group membership in Azure AD are synchronized to the linked Class Teams through a process called Forward Sync, which occurs for all Groups and Teams within Office 365. 這種轉寄同步處理常式不是由 School Data Sync 所建立及管理的群組所獨有,也不是 School Data Sync 產品的一部分,但是它是一種在端對端小組布建過程中所需的功能。This forward sync process is not unique for Groups created and managed by School Data Sync, and it is not part of School Data Sync product, however it is a required capability within the end to end Teams provisioning process.