If you use Microsoft Teams for work or group communication, you've probably noticed that members may be joining from different parts of the country—or the world. Time zones matter. A meeting scheduled for "2 p.m." means something very different depending on where you are. Here's how Teams handles time zones and what you can do about them.
Teams automatically detects your time zone based on your device settings and your Microsoft account profile. When you set up your account or update your computer's location, Teams pulls that information and applies it to how the app displays meeting times, scheduled events, and calendar notifications.
This detection works silently in the background—you don't usually need to do anything. But because it depends on your device and account settings being correct, mismatches can happen. If your computer thinks you're in Eastern Time but you've actually moved to Pacific Time, Teams will display times in the wrong zone until you update your settings.
Time zone adjustments happen in a few places:
On your device: Your operating system (Windows, Mac, or phone) has its own time zone setting. Teams respects this as the primary source of truth. If you change your device time zone, Teams will reflect that change automatically.
In your Microsoft account profile: Your Microsoft 365 account has a separate time zone setting. You can update this through your account settings, and it influences how Teams displays times in calendar invitations and scheduled events across Microsoft 365 services.
In individual meeting invitations: When someone creates a Teams meeting and invites you, they can specify a time zone for that meeting. Teams will show you that time in your local zone for clarity, but the meeting invitation itself anchors to the organizer's stated zone.
Understanding what changes when your time zone updates helps prevent confusion:
What doesn't automatically adjust: the actual meeting time itself. If a meeting is scheduled for 3 p.m. Eastern, it's still 3 p.m. Eastern—the conversion only affects how you see it on your end.
Hybrid and remote teams: If your team spans regions, a single meeting time can mean 8 a.m. for someone on the West Coast and 11 a.m. for someone on the East Coast. Teams displays these correctly on each person's calendar, but confusion still happens if people don't check their local time before joining.
Daylight saving time transitions: When regions shift between standard time and daylight saving time on different dates (some places don't observe it at all), recurring meetings can show the wrong time for a week or two. This is because Teams respects your device's time zone, and the changeover is built into your operating system—it's not a Teams issue, but it affects Teams display.
International teams: When you have people across multiple countries, even a "universal" meeting time (like UTC/GMT) can be unclear if not everyone knows their offset from that standard. Teams can't solve this confusion on its own; it relies on clear communication about which time zone is being used.
If you suspect your time zone is wrong or you've moved locations:
Check your device settings first. On Windows, search "time zone" in Settings. On Mac, go to System Preferences > Date & Time. On a phone, check the main Settings app. Make sure the location and time zone are accurate.
Verify your Microsoft account settings. Sign into your Microsoft 365 account online, go to your profile settings, and look for language and regional preferences. Update the time zone there as well.
Test it in Teams. Create a test event or check an upcoming meeting. Does the displayed time match your local time? If not, revisit steps 1 and 2.
Whether time zone issues will affect you depends on:
Teams time zones work best when both your device and account settings are accurate, and when your team is clear about which time zone anchor they're using for scheduling. Beyond that, it's about awareness and communication.
