Teams is usually included in the licenses a company buys for its mail migration, and there is pressure to turn it on for everyone at once. That can work. It can also mean users get a new chat tool, a new phone system and a new file store in the same week their email changed, and the helpdesk absorbs the confusion.
This post covers what Teams depends on in Exchange Online, the governance settings to lock down before the first team exists, and a rollout order that keeps the two projects from colliding.
What Teams needs from the mail migration
Teams stores chat in a hidden mailbox folder, uses the Exchange Online calendar for meetings, and relies on Exchange for the group mailbox behind every team. If a user's mailbox is still on-prem, Teams chat works, but the calendar tab may be missing, the Outlook meeting add-in may not appear, and some features that write to the mailbox are unavailable unless the on-prem Exchange is a supported version with OAuth configured through hybrid.
The practical rule: a user gets the full Teams experience when their mailbox is in Exchange Online. That makes the mailbox batch the natural moment to enable Teams for that user, rather than a separate date.
Connect-MicrosoftTeams
Get-CsOnlineUser -Identity user@domain.com | Select DisplayName, InterpretedUserType, TeamsUpgradeEffectiveMode, HostedVoiceMail
Get-CsTeamsClientConfiguration | Format-List AllowGuestUser, AllowEmailIntoChannelGovernance before the first team
By default, every user can create a team, and every team creates a Microsoft 365 group with a SharePoint site, a mailbox and a calendar. Within a month you will have Marketing, marketing-team, Marketing 2 and a team called test. Settle the rules before the client is installed.
Decide who can create teams, whether there is a naming policy, what the expiration policy is for inactive groups, whether guests are allowed and from which domains, and which external organizations users can chat with. These live across the Teams admin center and Entra ID group settings, and most are a few minutes each.
- Group creation restricted to a security group of team owners, or left open with an expiration policy of one year.
- Naming policy with a department prefix or a blocked words list.
- Guest access on or off per your data rules, with sensitivity labels if you have Business Premium or E3 and above.
- External access limited to specific domains, or open with a review after three months.
- Meeting policies: who can bypass the lobby, whether recording and transcription are on.
- Retention policy for chat and channel messages, decided with whoever owns compliance.
Connect-MgGraph -Scopes "Directory.ReadWrite.All"
$s = Get-MgGroupSetting | Where-Object { $_.DisplayName -eq "Group.Unified" }
$s.Values | Select Name, Value
# Restrict creation to a group: set EnableGroupCreation false and GroupCreationAllowedGroupId to the group's object idA rollout order that works
Run Teams a half step behind mail. Users in the pilot mailbox batch get Teams first and become the people who answer questions later. Production batches get Teams enabled as their mailbox moves, with a short guide that explains chat, meetings and where files live. Phone system, if you are replacing a PBX, comes after everyone is on Exchange Online and the client is familiar.
Install the client through Intune or the Microsoft 365 apps installer so it is present before the user is enabled. The new Teams client is the only one, and it is deployed with the Teams bootstrapper on managed Windows devices.
- Week of the pilot batch: enable Teams for pilot users, create two or three real teams with owners.
- Each production batch: Teams enabled with the mailbox move, one-page guide sent the day before.
- After the last batch: open team creation to the approved owners group, run a short session on channels versus chat.
- One month later: review inactive teams, guest access reports, and any request for Teams Phone.
teamsbootstrapper.exe -p
# or with a local MSIX
teamsbootstrapper.exe -p -o "C:\Deploy\MSTeams-x64.msix"Files, channels and the file server question
Every team channel has a folder in the team's SharePoint site, and the Files tab is that folder. This is where the file server migration and the Teams rollout meet. If a department's share is going to become a team, migrate the share into that team's site so the files show up in the channel, rather than into a separate site that users then have to find.
Private and shared channels create their own separate sites, which surprises people who look for the files in the main team site. Keep channel design simple at the start: a handful of standard channels, private channels only where a real confidentiality boundary exists.
The support load
Most Teams tickets in the first month are not technical. They are about notifications, how to find a file, why someone is showing as away, and whether to use chat or email. A short FAQ written in your own words handles most of it. The technical ones are usually audio devices, meeting add-in missing from Outlook because the mailbox is still on-prem, and calendars not showing for users whose mailbox move has not completed. All three point back to the mail migration order, which is the reason to keep the two projects in step.
Frequently asked questions
Can we use Teams before the mailboxes are migrated?
Chat and basic meetings work with an on-prem mailbox, but calendar integration and the Outlook add-in depend on Exchange Online or a supported hybrid with OAuth. Enable Teams per user as their mailbox moves for the least confusion.
Should we restrict who can create teams?
For most companies, yes, at least at first. Restrict creation to a group of owners, or leave it open with an expiration policy and naming rules. Reopening later is easier than cleaning up.
When should Teams Phone come in?
After the mail migration is complete and users are comfortable with the client. Porting numbers and replacing desk phones is its own project with its own cutover.
Takeaway
Teams works best when it follows the mailbox, so enable it per batch instead of on a separate day. Set group creation, naming, guest and retention rules before the first team exists, keep channel design simple, and hold Teams Phone until the mail migration is finished. If you want help sequencing the two, RackLedge plans them together as one project.