Microsoft Teams Shifts for frontline workers

Shifts is the schedule-management app built into Microsoft Teams, aimed at frontline and shift-based workers — retail associates, healthcare staff, hospitality, manufacturing, field services. It gives managers a tool for building schedules and workers a phone-friendly view of when and where they're working.

Shifts pairs with Walkie Talkie in the frontline toolkit, is licensed through the F1 and F3 plans, and runs on shared devices managed per Intune Android Enterprise; the integration story connects to Power Automate for schedule automation.

What managers do

Managers use the Shifts app (in Teams, or via the Teams admin center) to:

• Build a weekly or monthly schedule for a team, with shifts, time-off, and open shifts.
• Assign shifts to individual members of the team.
• Publish the schedule, which notifies workers via Teams on mobile.
• Approve swap and offer requests when workers want to trade shifts.
• Track time-off balances and approvals.
• See clock-in / clock-out records if Time Clock is enabled.

What workers do

Workers see their schedule on the Shifts tab in Teams. They can:

• See upcoming shifts.
• Swap shifts with eligible colleagues.
• Offer shifts to others.
• Request time off.
• Clock in / out (with optional geofencing — only allow clock-in within X metres of the workplace).
• Mark themselves available or unavailable.

Integration with the rest of Teams

Shifts builds on the Teams frontline experience:

• A frontline manager policy sets the right Teams app layout for that role.
• Walkie Talkie gives push-to-talk over Wi-Fi or cellular.
• Approvals, Tasks by Planner, and Praise complement Shifts for day-to-day shift work.
• Microsoft 365 F1 / F3 plans license frontline-worker users at lower cost than knowledge-worker plans.

Integration with workforce-management systems

For organisations running enterprise WFM tools (Blue Yonder JDA, Kronos / UKG Dimensions, Reflexis, Zebra Reflexis), Shifts has a WFM connector model that syncs schedules between the source system and Teams. This is the right approach when the source of truth lives in WFM — managers keep their existing tooling, but workers see the schedule in Teams on mobile.

Where Shifts fits

Shifts isn't a replacement for full workforce management — it doesn't do labour forecasting, demand modelling, or complex compliance. It's a "good enough" scheduler for organisations that didn't have one, and a clean phone interface for organisations that did but couldn't get workers to install yet another app.

Licensing frontline devices, not just people

Shifts is licensed through Microsoft 365 F1 or F3, but a frontline rollout is rarely just a licensing decision for the person — the shared device the schedule is viewed on matters just as much. A retail floor with one tablet per department, used by whoever's on shift, needs shared device mode (a single Entra ID device identity multiple staff sign in and out of quickly, rather than one device per employee) and an Intune Android Enterprise or Windows shared-device configuration to match — buying F3 licences for every frontline worker without also solving the shared-device sign-in experience typically produces a rollout that looks fully licensed on paper but that workers avoid using because signing in and out is too slow for a five-minute break.

Frequently asked questions

Can Shifts replace a dedicated workforce-management system entirely? For simple scheduling needs, often yes; for organisations with real labour-forecasting, demand-modelling, or complex union-rule compliance requirements, Shifts is deliberately not trying to compete with dedicated WFM platforms — the connector model exists specifically so those organisations can keep their WFM system as the source of truth while still giving workers the Teams mobile experience.

Does Time Clock in Shifts integrate with payroll systems? Time Clock captures clock-in/out events and makes them available for export or via Graph API integration, but it isn't itself a payroll system — organisations typically feed that data into their existing payroll or WFM platform rather than treating Shifts as a standalone payroll source.