Documented requirements
| Profile | Download | Published upload | Planning upload | Evidence |
|---|---|---|---|---|
| Teams meeting, recommended | 4 Mbps | 2.5 Mbps | Same as published | OFFICIAL |
Official values come directly from the cited service. Derived values combine official service requirements. Planning values are labeled separately and are not presented as vendor minimums. Check the full category database.
Household scenarios
| Scenario | Delivered need | Shopping target | What is included |
|---|---|---|---|
| One Teams meeting | 8 Mbps down / 4 Mbps up | 25 Mbps down / 5 Mbps up | One active endpoint using the recommended profile. |
| Two Teams meetings | 15 Mbps down / 8 Mbps up | 25 Mbps down / 10 Mbps up | Two simultaneous endpoints. |
| Four Teams meetings | 30 Mbps down / 15 Mbps up | 50 Mbps down / 20 Mbps up | A call-heavy household example. |
SITE CALCULATION These examples use the current locked engine, including simultaneous-activity totals, background traffic, utilization targets, and shopping-tier rounding. Change the tool above for your own home.
Read the directions from the user's connection
Upload carries your camera and audio out; download carries the other participants and shared content in. The table preserves that orientation. Choose Microsoft Teams under Improve my result to replace the general call preset.
Sources: Microsoft (S05)Check network quality separately
Microsoft also documents real-time media quality examples for round-trip time, jitter, and packet loss. Those measures are separate from bandwidth, so buying more Mbps does not automatically correct a weak or unstable connection.
Sources: Microsoft (S19)