When designing a new solution you need to know your limits! Wether you are designing a building, a new gadget or a communication- and collaboration solution using Microsoft Teams: “You need to know your limits”.
Question you need to ask yourself
- What kind of privileges are available? (3 – owner, member (and guest member))
- What is the number of teams a user can create (250)
- What is the number of members in a team (2.500)
- What is the number of teams a global admin can create (Unlimited)
- What is the number of teams an Office 365 tenant can have (500.000)
- What is the number of channels per team (200)
Limit types
You also need to take into account the type of limit. Basically Microsoft limits can be split into three area’s (allthough in Office 365 most of them are boundaries) :
- Boundaries: Static limits that cannot be exceeded by design
- Thresholds: Configurable limits that can be exceeded to accommodate specific requirements
- Supported limits: Configurable limits that have been set by default to a tested value
Architecture
We are talking about Microsoft Teams which is part of Office 365. Microsoft Teams connects several services together. So you need to know the architecture to know the limits of the connected services.
In my book: doesn’t matter what you are designing – always acknowledge the limits!
Keep current!
To keep current on all Microsoft Teams limits and specifications you can use this link: https://docs.microsoft.com/en-us/microsoftteams/limits-specifications-teams
