Quick summary
Shifts is a schedule app: a manager places the shifts and the team sees them in Teams. Chrona Workforce Scheduler is a scheduling engine: Auto Schedule, a constraint solver, builds the roster for you, and you review it before you publish.
- Choose Microsoft Shifts if a manager can place every shift by hand and your teams already work in Teams.
- Choose Chrona Workforce Scheduler if you want the whole roster auto scheduled in one run, without breaking any Must rule, and fairness, preferences and wages weighed across the period.
- Both give workers open shifts, swaps and time-off requests on their phone.
Who builds the roster
In Shifts, the roster is what a manager makes it. Shifts publishes, swaps and records shifts. Microsoft’s pages describe no automatic scheduling, and for business rules they point to a separate workforce management system.
In Chrona Workforce Scheduler, Auto Schedule is a constraint solver built on Timefold. Your rules become constraints. Must rules, such as required skills, rest between shifts and maximum hours, are never broken. Should rules and the goals you rank, such as fair shares of nights and weekends, preferences, contracted hours and wages, are weighed against each other. The solver searches the possible assignments for the whole roster period at once and keeps the best roster it finds.
This is mathematical optimization, not generative AI. Every assignment follows from your rules, and the result arrives as a proposal that you review before anything is published.
- workers in one run
- 2,000
- shifts in one run
- 14,400
- Must rules broken
- 0
How constraint-based scheduling works
Pricing
| Product | Price |
|---|---|
| Microsoft Shifts | No separate price: users need a Teams license. |
| Chrona Workforce Scheduler | The first 5 workers each month are free, then US$10 a worker a month, with no base fee. 14-day trial, no card. |
Chrona Workforce Scheduler also needs Microsoft licenses: Power Apps for the people who plan, and Power Pages for the workers who sign in to Chrona Workforce Mobile. Check both vendors’ current pages before you decide.
Where they differ
The biggest difference is the first row: Chrona Workforce Scheduler builds the roster with a constraint solver, where Microsoft’s Shifts documentation describes building it by hand. Team messages are where Shifts is ahead, because it sits inside Teams. Every row is in All features below.
| Feature | Microsoft Shifts | Chrona Workforce Scheduler |
|---|---|---|
| Automatic scheduling | Not described | YesAuto Schedule: a constraint solver built on Timefold |
| Automatic call-out for open shifts | Not described | YesStarts on publish; levels open on their own |
| Working-time rules (rest, hours, days off) | Not described | YesKept by Auto Schedule |
| Fair share of hours, nights and weekends | Not described | YesPer site, over the periods you set |
| Schedule kept in Dataverse | NoIts own Microsoft 365 service | YesA managed solution in your own Dataverse |
| Team messages next to the schedule | YesTeams chat | No |
All features
Every row, by area, from Microsoft’s documentation for Shifts and from our own pages for Chrona Workforce Scheduler.
Building the roster
| Feature | Microsoft Shifts | Chrona Workforce Scheduler |
|---|---|---|
| Automatic scheduling | Not described | YesAuto Schedule: a constraint solver built on Timefold |
| Automatic call-out for open shifts | Not described | YesStarts on publish; levels open on their own |
| Working-time rules (rest, hours, days off) | Not described | YesKept by Auto Schedule |
| Award and agreement rules per worker | Not described | YesEach rule names its clause |
| Skills checked on every shift | Not described | YesMust and Should skills |
| Skill and license expiry dates | Not described | YesAn expired skill blocks the role |
| Role pairing on a shift | Not described | YesRequired, preferred or prohibited partner roles |
| Preferred and prohibited workers per shift | Not described | YesPreferred, unpreferred, prohibited; risk factors |
| Goals you rank | Not described | YesPresets such as Lowest cost and Happiest team |
| Fair share of hours, nights and weekends | Not described | YesPer site, over the periods you set |
| Public holidays by region | Not described | YesEach site picks its region |
| Shifts made from staffing demand | Not described | YesCoverage and staffing standards |
| Staffing ratios, such as hours per resident | Not described | YesHours per resident, guest or order; rounding as your rules require |
| Shifts made in bulk | YesExcel import, copy and paste | YesGenerate makes each period’s shifts |
| What-if scenarios | Not described | YesThree strategies or one what-if change |
Data and platform
| Feature | Microsoft Shifts | Chrona Workforce Scheduler |
|---|---|---|
| Schedule kept in Dataverse | NoIts own Microsoft 365 service | YesA managed solution in your own Dataverse |
| Planners work in Power Apps | NoRuns in Microsoft Teams | YesA model-driven app |
| Power Automate flows | YesShifts connector | YesOn your own Dataverse tables |
| Set up by your AI agent | Not described | YesCopilot Studio or any MCP agent |
Mobile app
| Feature | Microsoft Shifts | Chrona Workforce Scheduler |
|---|---|---|
| Mobile app for workers | YesInside Teams | YesChrona Workforce Mobile, included |
| Own and team schedule | YesOwn and team schedule | YesToday, the week ahead, the team |
| Share the shift calendar with others | Not described | YesA calendar link that stays up to date |
| Pick up open shifts | YesOwn team; other locations in preview | YesSaved from demand nobody covers |
| Accept offers from a text or email link | Not described | YesNo sign-in needed |
| Swap shifts | YesWith a coworker on the same team | Yes |
| Pick shifts before the roster | Not described | YesPicks and stars in a pick window |
| Leave and sick reports | YesTime-off requests | YesLeave and sick reports |
| Availability from the phone | YesRecurring days and up to 10 dates | YesPattern changes and one-off times, approved |
| Work preferences | Not described | YesTimes and shift types they prefer |
| Time recorded on the phone | YesClock in and out of shifts and breaks | YesTimesheets with hours beside each shift |
| Notifications to workers | Not described | YesIn the app, by email and by text |
| Sign in without a Microsoft work account | NoUsers need a Teams license; no guests | YesGoogle sign-in, no Microsoft account |
| Your logo and colors | Not described | YesLight and dark mode |
| Team messages next to the schedule | YesTeams chat | No |
Time and payroll
| Feature | Microsoft Shifts | Chrona Workforce Scheduler |
|---|---|---|
| Hours exported to payroll in your codes | YesSchedules and time clock data to Excel | YesIntegration Studio: formats, code maps, corrections |
| Reports on your own data | YesTime sheet reports | YesPower BI and Power Platform on your Dataverse |
| Hours against guaranteed hours | Not described | YesPlanners and workers see it |
| Staffing reports (CMS PBJ, PpUGV) | Not described | Yes |
Yes means the vendor’s own documentation describes the feature. A dash means it does not.
Area by area
Building the roster
Microsoft Shifts. A manager creates shifts one by one, or in bulk from an Excel import or by copy and paste, then assigns and publishes them. Microsoft’s Shifts pages describe no skills matching or working-time rules.
Chrona Workforce Scheduler. Generate makes the shifts each period needs from your shift types, coverage and staffing standards, such as each role’s hours per resident. Auto Schedule then assigns them with the constraint solver, against every skill, availability, leave and working-time rule at once, and ranks the result by the goals you set. The rules come from your award or agreement, each naming its clause; a skill or license past its expiry date blocks the role; role pairing keeps a required partner on the shift; each site gets its region’s public holidays; and Auto Schedule shares hours, nights and weekends fairly.
Data and platform
Microsoft Shifts. It keeps its schedules in its own Microsoft 365 service, in your Teams data region, not in Dataverse. The Shifts connector for Power Automate and the Microsoft Graph API move data between Shifts and your other apps.
Chrona Workforce Scheduler. It is a managed solution in your own Dataverse. Shifts, workers, skills and rules are Dataverse rows next to your sites, contracts and residents, and your security roles decide who sees and edits what. Your AI agent can set it up, in Copilot Studio or any agent with Model Context Protocol (MCP) tools.
Mobile app
Microsoft Shifts. It runs inside Teams, so staff use an app they may already have. They see their own and their team’s schedule, request open shifts, swap or offer a shift to a coworker on the same team, request time off, set their availability on the phone and clock in and out of shifts and breaks. Managers can message one person or the whole team.
Chrona Workforce Scheduler. Workers use Chrona Workforce Mobile, a Power Pages app in your own Dataverse with your logo and colors, in light or dark mode. They see today, the week ahead and the team schedule; pick up open shifts and accept short-notice offers from a text or email link; swap shifts; pick and star shifts before each roster; ask for leave and report sick; change their availability and say what they prefer; and send timesheets with their hours beside each shift. They share their shift calendar with others, and with their own calendar app, through a link that stays up to date. They sign in with a work account or with Google, in eight languages.
Time and payroll
Microsoft Shifts. It gives managers time sheet reports and totals of hours worked and time off, and exports schedules and time clock data to Excel.
Chrona Workforce Scheduler. It keeps each worker’s hours against their guaranteed hours, and workers see their balance on the phone. Integration Studio maps approved hours to your payroll codes and prepares CMS PBJ and PpUGV staffing files, and you report on your own Dataverse with Power BI and the Power Platform. Your payroll system still pays.
Which to choose
Choose Microsoft Shifts if
- A manager can place every shift by hand
- Your teams already work in Microsoft Teams
- Shifts carry no skills, rest or hours rules to check
- You want nothing beyond your Teams licenses
Choose Chrona Workforce Scheduler if
- You want the whole roster auto scheduled in one run, without breaking any Must rule
- Open shifts go out by automatic call-out, best fits first
- Fairness, preferences and wages should be weighed, not guessed
- The roster belongs in Dataverse, next to your other data
- Workers need picks, offers, leave and timesheets on the phone
Questions
Is Microsoft Shifts free?
Shifts has no separate price. Microsoft says users need a Teams license to use it, and it is on by default for Teams users.
Can Shifts schedule workers automatically?
Microsoft’s Shifts documentation describes no automatic scheduling. Managers build the schedule by hand or import it from Excel, and organizations that need business rules connect Shifts to a workforce management system. In Chrona Workforce Scheduler, Auto Schedule is a constraint solver built on Timefold: it builds the whole roster period against your rules, never breaks a Must rule, and returns the best roster it finds as a proposal for review.
Does Microsoft Shifts keep its data in Dataverse?
No. Shifts stores its data in its own Microsoft 365 service, in your Teams data region. Chrona Workforce Scheduler keeps every shift in your own Dataverse.
Which licenses does each one need?
Shifts needs a Teams license for each user. Chrona Workforce Scheduler needs Power Apps for the people who plan, and Power Pages for the workers who sign in to Chrona Workforce Mobile. The first 5 workers Auto Schedule schedules each month are free, then US$10 a worker a month.
How we compared
We build Chrona, so read this page with that in mind. Facts about the other product come only from its vendor’s public pages, listed below. We have not scored either product. If something here is out of date, tell us and we will correct it. Tell us
