Microsoft Teams HR Onboarding: An IT Admin's Setup Guide

Onboarding in Microsoft Teams is a pipeline of four layers: Microsoft Entra Lifecycle Workflows handle identity and day-one access, a Teams template builds the workspace, SharePoint and Lists carry the content and checklist, and Viva Insights measures the result. When HR asks you for “onboarding in Teams”, this is the set of pieces you actually deliver.

Quick fix: Start with the identity layer. Confirm your HR system populates employeeHireDate and the manager attribute in Microsoft Entra ID, check that you hold Entra ID Governance or Entra Suite licenses, then pilot the built-in “Onboard new hire employee” workflow on one test user before you touch the Teams workspace.

The stakes are well documented. Gallup reported in 2021 that “only 12% of U.S. employees say their company does a good job of onboarding”, and that only 29% of new hires feel fully prepared and supported to excel in their role. Gallup also found that 70% of employees who had exceptional onboarding experiences say they have “the best possible job”. Dave Haspas, an HR data analyst at Microsoft, said in 2018: “We found that people who have bad onboarding experiences also have higher attrition rates within the first year.”

This guide is for IT admins and governance owners who receive that request from HR. For the people-and-process side, see onboarding new employees with Microsoft Teams.

What is a Microsoft Teams onboarding setup made of?

Five layers, each owned by a different Microsoft tool:

Layer	Microsoft tool	What it handles	License or role needed
Identity and access	Microsoft Entra Lifecycle Workflows	Welcome emails, Temporary Access Pass, licenses, groups, teams	Entra ID Governance or Entra Suite
Workspace	Teams template (Teams admin center)	Channels, tabs and apps for the new team	Teams admin permissions
Content and checklist	SharePoint site template, Microsoft Lists	Onboarding home page and task list	Site-creation permissions
Learning	Viva Learning	LinkedIn Learning and Microsoft Learn content in Teams	Teams, SharePoint or Knowledge admin roles
Measurement	Viva Insights, Microsoft Forms	Manager 1:1s, learning time, network growth, surveys	Insights Analyst role, Power BI Desktop

How do you automate day-one access with Entra Lifecycle Workflows?

Microsoft Entra Lifecycle Workflows follow a joiner, mover and leaver model, and the licensing line in Microsoft’s documentation is explicit: “Using this feature requires Microsoft Entra ID Governance or Microsoft Entra Suite licenses.” You can have up to 100 workflows. Configure them in the Microsoft Entra admin center.

Prerequisites come first, per the deployment plan:

• HR-driven inbound provisioning, for example from Workday, SuccessFactors, Microsoft Entra Connect or cloud sync.
• employeeHireDate populated, because the built-in workflows are scheduled around it. Involve an HR representative early to agree where that attribute comes from.
• The manager attribute, which the Temporary Access Pass task needs in order to send the pass to the manager.

The built-in templates map directly onto an onboarding timeline:

Template	Timing	Tasks
Onboard pre-hire employee	7 days before hire date	Generate TAP and send email
Onboard new hire employee	Day 0	Add user to group, enable user account, send welcome email
Post-Onboarding of an employee	7 days after hire date	Add user to group, add user to selected teams

The task list also includes assigning licenses, requesting an access package assignment, updating user attributes and running a custom task extension, which is where Logic Apps come in for anything custom. The “Add user to teams” task adds the user to an existing static team by its team ID, so the workspace has to exist first.

By default workflows run every 3 hours, configurable from 1 to 24, and offsets range from -180 to 180 days. Pilot on a single test user or a small group. The on-demand run covers up to 10 users, and the workflow history shows what happened.

What does the prebuilt “Onboard Employees” template give you?

Not much to build, which is the point. In the Teams admin center, go to Teams > Team templates. The Onboard Employees template includes General, Announcements, Employee Chat and Training channels, with apps such as Lists (the onboarding checklist), Milestones, Power Automate, SharePoint pages, Planner and Viva Engage. It is a Microsoft 365 connected template, so the SharePoint template is applied to the site and its pages and lists are pinned as tabs in General.

The key constraints, from Microsoft’s template documentation:

• You can duplicate prebuilt templates but you can’t edit them.
• Limits are 15 channels, 20 tabs per channel and 50 apps per template.
• Private and shared channels, team membership, files and content are not supported in templates.
• The template also lists a Wiki app. Microsoft announced Wikis would be retired from Teams from January 2024, so use Notes, Lists or SharePoint pages instead.

Control who sees which template with templates policies under Teams > Templates policies. New templates are visible by default, policies can’t be assigned by group membership (assign to users or use PowerShell batch assignment), and a change can take up to 24 hours.

If your onboarding teams need private channels, files and members from day one, plus governance on top, nBold workspace templates can provision what native templates can’t carry. Our onboarding template guide covers the full build, including Power Automate.

Where do the checklist and onboarding content live?

Keep the checklist out of chat. Three Microsoft-native pieces cover it:

• Microsoft Lists for the task list with owner and due date. The Onboard Employees template already uses a List for its checklist.
• The SharePoint “New employee onboarding” site template, described in Microsoft’s support article. It is a communication site that works as an internal HR home page, with Getting Started, Onboarding Checklist, Who We Are, Our leadership, Our priorities and Help and Support pages, plus a new-employee introduction news post. You need site-creation permissions to add it.
• The SharePoint app in Teams (formerly Viva Connections), which surfaces that home site inside Teams. With an E, F or A license you get one experience; two or more require the Viva Suite or Viva Communications and Communities license for every user.

For training, Viva Learning is the learning hub in Teams, with LinkedIn Learning and Microsoft Learn content. Teams, SharePoint and Knowledge admins manage it.

How do you run first-week sessions now that live events are gone?

Teams live events retired on June 30, 2026. Events scheduled before that date remain supported through February 28, 2027, and Microsoft recommends the unified Teams events experience, which includes town halls and templates. For a company-wide welcome session, schedule a town hall. For smaller cohorts, a regular Teams meeting with the manager and a recorded session is enough. Any older onboarding documentation that mentions live events and Office 365 E1, E3 or E5 licenses needs updating.

How do you measure onboarding in Teams?

Start with what does not work. The Teams admin center under Analytics & reports offers usage reports for Teams usage, user activity, device usage and app usage. They show activity, and none of them measures onboarding. Teams administrators and Global readers can see them, and user data is anonymized by default.

What does exist:

• The Viva Insights “Onboarding and development” report. It is a Power BI template in Viva Insights advanced insights, so it is not a Teams feature. You need the Insights Analyst role, Power BI Desktop and HireDate uploaded in your organizational data. It covers manager 1:1s (a recommended minimum of 50 minutes per month), time spent learning and new-hire network growth.
• Microsoft Forms check-in surveys at the end of week one and around days 30, 60 and 90. This is your own data, so treat it as an option rather than a Teams metric.

The manager 1:1 metric has a source: a Viva Insights study of about 3,000 new hires found that those who met their manager one-to-one in week one had a 12% larger internal network within 90 days.

Can Copilot help with onboarding?

Microsoft’s Copilot scenario for onboarding lists Microsoft 365 Copilot as the required offering, with Loop, Copilot Chat, Word and PowerPoint. The documented uses are manual prompting: drafting an onboarding plan and checklist, summarizing policies and writing 60-day check-in emails. HR and managers prompt it and review the output. It does not run onboarding on its own, so keep it out of the identity and provisioning layers.

What governance guardrails does onboarding need?

• Templates policies to show only approved onboarding templates to the people who create teams.
• Workflow history in Entra as your audit trail for who got what and when.
• Offboarding symmetry. The leaver templates include a “Remove user from all Teams” task. If you add people to teams automatically, remove them automatically too.
• Least access on day one. Use the Temporary Access Pass and the pre-hire timing so the account is ready without sharing credentials early.

Onboarding setup checklist

1. Confirm employeeHireDate and manager are populated from your HR source.
2. Confirm Entra ID Governance or Entra Suite licenses.
3. Pilot the pre-hire and new-hire workflows on a test user with an on-demand run.
4. Duplicate Onboard Employees, adjust the copy and set a templates policy.
5. Add the SharePoint onboarding site and the Lists checklist.
6. Schedule a town hall for the first-week welcome.
7. Set up the Viva Insights report and your Forms check-ins.
8. Add the “Remove user from all Teams” step to your leaver workflow.

For HR system connections, see our HRMS integration guide.