在 Microsoft 團隊中建立小組時規劃 Microsoft 365 群組Plan for Microsoft 365 Groups when creating teams in Microsoft Teams

在考慮使用 Microsoft 365 群組或建立小組時,請考慮該小組將用於哪些人員、誰應該擁有存取權,以及小組預期會達到哪些結果。When considering the use of Microsoft 365 Groups or when creating teams, consider what the team will be used for, who should have access, and what outcome the team will expect to achieve. 特別注意的是,您所建立的頻道數量會隨著內容散佈太多的頻道而逐漸遭到溢出 () 。Pay special attention to the number of channels you create as people can quickly become overrun by content spread too thin (across too many channels).

有兩種情況可在規劃 Microsoft 365 群組及其對 (或) Microsoft 團隊的影響時,提供相關討論:There are two scenarios that warrant some discussion around planning of Microsoft 365 Groups and their impact on (or by) Microsoft Teams:

  • 首先,由於客戶可以在群組中使用現有投資,因此我們目前支援公用和私人群組(針對目前支援的成員數量),請參閱 Microsoft 團隊的限制與規格First, since customers could have existing investments in Groups, we currently support both Public and Private groups, for the number of members currently supported, please see Limits and specifications for Microsoft Teams. 如先前所述,您想要使用團隊用戶端(而非 Microsoft 365 系統管理中心),管理人員至團隊的成員資格。As mentioned previously, you want to manage the membership of people to a team using the Teams client rather than the Microsoft 365 admin center. 在此案例中,如果使用者是用來在 Microsoft 365 群組中進行執行緒交談,則值得注意的是,群組交談實質上是電子郵件,而不是團隊頻道中的聊天訊息。Given this scenario, if people are used to threaded conversations in Microsoft 365 Groups, it is worthwhile noting that a Groups conversation is essentially email and not the same as a chat message in a Teams channel. 在小組中教育您的人員,並建議他們採用更具彈性的聊天訊息格式,而不是使用 Outlook 或 OWA 以電子郵件傳送群組。Educate your people about this difference and suggest they adopt the more flexible chat message format in Teams versus emailing the Group using Outlook or OWA.

  • 其次,對於沒有 Microsoft 365 中定義之現有群組的客戶,您可以使用 Microsoft 365 系統管理中心、團隊網頁或桌面用戶端來建立它們。Second, for customers who don't have existing Groups defined in Microsoft 365, you can either create them using the Microsoft 365 admin center, the Teams web, or desktop clients. 如先前所述,您可以使用團隊用戶端管理所有未來的成員資格至 Microsoft 365 群組。As mentioned previously, manage all future membership to the Microsoft 365 group using the Teams client. 因為成員資格成為小組,所以也定義了 Microsoft 365 群組的成員資格,所以您應該為人員準備此變更。Since membership to a team is also defining membership to Microsoft 365 Groups, you should prepare people for this change.

團隊會尊重私人預覽版中的 Microsoft 365 群組命名原則 () Teams respects Microsoft 365 Groups naming policy (in private preview)

當使用者建立或編輯團隊名稱時,系統會在團隊中套用任何由您的系統管理員設定的 Microsoft 365 群組命名原則。Any Microsoft 365 Groups naming policy that has been set by your admin will be applied in Teams when users create or edit team names. 這包括強制性首碼或尾碼之類的內容,以及不含禁止的字。This includes things like mandatory prefixes or suffixes and excluding banned words.

注意

這項功能是私人預覽,這表示如果您不是此預覽的一部分,小組還不會遵守此 Microsoft 365 群組命名原則。This feature is in private preview, which means that if you're not part of this preview, Teams doesn't yet adhere to this Microsoft 365 Groups naming policy.

若要深入瞭解,請參閱 小組中的 Microsoft 365 群組命名原則To learn more, read Microsoft 365 Groups naming policy in Teams.

下列文章是尋找 Microsoft 365 群組的準備就緒與採納內容的好地方:The following articles are a good place to find readiness and adoption content for your Microsoft 365 Groups: