Microsoft 團隊的管理快速入門Governance quick start for Microsoft Teams

下列活動將會同時發生,而且它們可能會涉及全部或部分重要小組。The following activities will happen simultaneously, and they may involve all or part of your key team. 最佳做法是,在您使用團隊完成初次實驗之後,推遲大型規模的管理和安全性交談。As a best practice, defer large-scale governance and security conversations for after you have completed your initial experimentation with Teams. 瞭解管轄性決定可能會如何影響最終使用者體驗,並將簡化您在該日後所需作出的決策。It is important to understand how governance decisions may impact the end-user experience and will simplify the decisions you will need to make at that later date. 在此階段中,需要進行一些決策。For this phase there are some decisions that need to be made. 若要成功進行,您必須先回答下列問題:To successfully make them you will first need to answer the following questions:

  • 您先前評等的風險承擔者很適合參與此有限的商務用電腦?Which stakeholder from your earlier assessment is a good candidate to participate in this limited business onboarding?
  • 有這個個別 (或一組人員) 建議的使用案例,適合這個階段嗎?Has this individual (or group of individuals) suggested use cases that would be good candidates for this phase?
  • 他們是否有足夠的興趣,讓組織中的員工能成為早期的人員,並提供有意義且週期性意見反應?Do they have enough interest from employees in their organization to be early adopters and give you meaningful and regular feedback?

若要深入瞭解,請閱讀 小組中的管轄方案 ,並 規劃團隊中的週期管理To learn more, read Plan for governance in Teams and Plan for lifecycle management in Teams.

代表決策點的圖示判斷Decisions

進行下列決策 (此時,這些決策只適用于階段 2) :Make the following decisions (at this point, these decisions apply only to Phase 2):

決策1:可以建立團隊的人員Decision 1: Who can create teams

針對此階段的用途,您可以限制誰能夠建立小組,除了您的核心專案小組以外。For the purposes of this phase you can restrict who is able to create teams to the early adopter population in addition to your core project team. 這可讓您的早期採納者視需要建立其他團隊。This will allow your early adopters to create additional teams if needed. 監控此行為會為您的廣泛部署提供重要資訊。Monitoring this behavior will give you key information for your broad deployment.

決策2:團隊命名慣例Decision 2: Teams naming conventions

您可能會想要針對大量的小組部署執行一些命名慣例,並檢查重複的名稱。You will likely want to implement some naming conventions for your broad deployment of Teams, and check for duplicate names. 在階段2中,我們建議您只為初始專案實現手動命名慣例。In Phase 2 we suggest that you implement a manual naming convention for your initial projects only. 此做法的最佳做法是向先期消費者專案團隊進行互動式加入,並允許他們選取自己的名稱。The best practice for this is to conduct an interactive onboarding with the early adopter project team and allow them to select their own name. 這可讓您深入瞭解員工如何思考其工作,並在日後建立較大的規模命名慣例。This will give you insight into how employees think about their work and will be essential in creating a larger scale naming convention at a later time. 本指南稍後會顯示有關互動式加入的元素 (其他資訊。 ) (Additional information on the elements of an interactive onboarding will appear later in this guide.)

決策3:來賓存取Decision 3: Guest access

根據您專案的範圍與類型和行業的性質,啟用與合作夥伴或供應商的安全共同作業可能是您想要測試的重要功能。Depending on the scope and type of your project and the nature of your industry, enabling secure collaboration with partners or vendors may be an essential capability you want to test. 您可以使用適當的租使用者控制項,限制哪些人可以將客人新增給小組,並使用敏感度標籤限制哪些團隊開啟給來賓。You can limit who can add guests to teams by using the appropriate tenant controls, and limit which teams are open to guests by using sensitivity labels. 您也可以確保來賓遵守組織的安全性需求,例如使用多重要素驗證 (MFA) 。You can additionally ensure that guests adhere to organizational security requirements such as the use of Multi-Factor Authentication (MFA).

決策4:已核准的 appDecision 4: Approved apps

小組的最佳使用方式包括將其他 app 整合至體驗中。The best case use of Teams includes the integration of other apps into the experience. 您最少的技術小組應該在您的小組體驗中啟用第一方和主要 app。At a minimum your technical team should enable the first party and featured apps in your Teams experience. 視您的使用案例和貴組織中使用的其他應用程式而定,您可以加入宣告其他 app 作為您控制的實驗的一部分。Depending on your use case and other apps used in your organization, you may opt to include additional apps as a part of your controlled experiment. 請務必 vet 任何協力廠商應用程式,以確保它們符合貴組織的安全性和合規性需求。Be sure to vet any third party apps to ensure they adhere to your organization’s security and compliance requirements.

決策5:您的測試中是否包含會議?Decision 5: Are meetings included in your test?

[團隊會議體驗] 是高品質、支援視頻聊天,且能讓員工更有效率。The Teams meeting experience is high quality, supports video chatting, and brings your employees together to be more effective. 諮詢您的技術小組,確認您的環境已準備好加入簡單的 VoIP 會議。Consult with your technical team to make sure that your environment is ready to include simple VoIP meetings. 啟用音訊會議或語音服務,將會在您的實驗中排除此階段;不過,這取決於您的核心專案小組、您的技術準備,以及貴組織中其他語音/會議服務的狀態。Enabling audio conferencing or voice services would normally be excluded from this phase of your experimentation; however, that depends on your core project team, your technical readiness, and the state of other voice/meeting services in your organization. 技術就緒應包括會議室設備、使用者裝置和附屬件等專案,以及網路。Technical readiness should include things such as meeting room equipment, end-user devices and accessories, and the network. 我們建議您在實驗中包含影片聊天和 VoIP 會議,以從您的小組實施中取得更大的價值。We recommend including video chats and VoIP meetings in your experimentation to gain more value from your Teams implementation.

決策6:內容管理與結構Decision 6: Content management and structure

當使用者在平臺內進行端對端工作時,最適合使用團隊,而不是要求他們連續切換回舊版系統和服務,並提供與使用者熟悉的方式不同的新方法。Teams works best when users work end-to-end within the platform - instead of requiring them to continually switch back to legacy systems and services - and offers new ways of working that differ from how users are accustomed. 在您的實驗中,請與您的參與者共同考慮在團隊中採用多種模式方式的小組結構和頻道,避免直接複製現有的資料夾和儲存結構。As part of your experiment, work with your participants to consider team structures and channels that embrace the multi-modal ways of collaborating within Teams, and avoid simply replicating existing folder and storage structures. 此外,請考慮任何儲存在現有支援系統(例如記錄管理或備份系統)之外之內容的合規性需求。Additionally, consider any compliance requirements for content stored outside of existing supported systems such as records management or backup systems.

決策7:資料安全性Decision 7: Data security

為您廣泛的部署準備,您可以選擇使用 [安全標籤] 來將您環境中的小組類型分類。In preparation for your broad deployment you may opt to use security labels to classify the types of teams in your environment. 針對本次實驗的目的,我們建議您參考 小組中的管轄規劃 ,並確保已針對 Microsoft 365 中的小組資料設定基本的保留原則。For the purposes of this experiment we recommend that you refer to Plan for Governance in Teams and ensure that a basic retention policy has been set on Teams data in your Microsoft 365. 您可能需要將此工作與技術小組協調,因為需要 Microsoft 365 系統管理員許可權才能完成此作業。You may need to coordinate this work with your technical team because Microsoft 365 administrator rights are required to complete this work.

決策8:實驗的長度Decision 8: Length of your experiment

成功的團隊實現會以良好的速度進行,以確保適當的動量、焦點及學習專案。A successful Teams implementation proceeds at a healthy pace to ensure appropriate momentum, focus, and learnings. 我們建議您專案的這個階段為60天,以確保您的早期消費者能完成足夠的商務週期。We recommend that this phase of your project be 60 days in length to ensure that your early adopters complete sufficient business cycles. 延長太長時間的實驗會增加變更計畫失敗的風險;不過,這次會因每個組織而異。Extending experimentation for too lengthy a time increases the risk of a failed change program; however, this time will vary for every organization.

代表下一個步驟的圖示 定義使用案例An icon representing the next step Next: Define usage scenarios