Use the Microsoft 365 admin center to manage your Shifts connection to Blue Yonder Workforce Management


The Microsoft Teams Shifts connector for Blue Yonder enables you to integrate the Shifts app in Microsoft Teams with Blue Yonder Workforce Management (Blue Yonder WFM). After you set up a connection, your frontline workers can seamlessly view and manage their schedules in Blue Yonder WFM from within Shifts.

You can use the Shifts connector wizard in the Microsoft 365 admin center or PowerShell to create a connection. After a connection is set up, you can manage it in the Microsoft 365 admin center. The Connector Management page lists each connection that you've set up, along with information such as health status and sync interval details. You can also access the wizard to create a new connection or make changes to any of your existing connections. For example, you can update sync settings and team mappings.


You can also use PowerShell to manage a connection. For example, you can view an error report, change connection settings, and disable sync. To learn more, see Use PowerShell to manage your Shifts connection to Blue Yonder Workforce Management.

Manage your connection

  1. In the left navigation of the Microsoft 365 admin center, choose Setup, and then under Featured collections, select Frontline workers.

  2. Select Manage Shifts connectors, and then choose Manage. Keep in mind that this option is available only if you've set up at least one connection, either using the wizard or PowerShell.

    Here, you'll see a list of all the connections you've set up through the wizard or PowerShell, along with information about each one.

    Screenshot of the Connector Management page in the Microsoft 365 admin center, showing a list of connections.

    • To create a new connection, select Add connector at the top of the page to start the wizard.

    • To view more details about a connection, click the connection name. On the details page, you'll see health information, including mapping and account authorization errors and warnings (if any), the list of mappings (if any), and more. You can also choose Edit to update connection settings in the wizard.

      Screenshot of the details page for a connection, showing connector health and mappings information.

      For a complete list of error messages and how to resolve them, see List of error messages later in this article.

    • To make changes to a connection, choose Edit next to the connection. You'll be taken to the wizard, where you can update the settings that you want.


You can also go directly to the Connector Management page when you select the Connector Management button on the last page of the wizard during connection setup.

List of error messages

Here's the list of error messages that you may encounter and information to help you resolve them.

Error type Error details Resolution
Unable to authenticate workforce management system. The workforce management system account credentials you've provided are invalid or this account doesn't have the required permissions. Update your WFM service account credentials in the connection settings. To do this, do one of the following:
Unable to authenticate Graph. Authentication failed. Ensure that you've entered valid credentials for the designated actor and have the required permissions. Make sure that your Microsoft 365 system account (also known as designated actor) is added as a team owner.
Or, update your Microsoft 365 system account credentials in the connection settings.
Some users have failed to map correctly Mapping failed for some users: <X> succeeded, <X> failed AAD user(s) and <X> failed workforce management system user(s). Use the Get-CsTeamsShiftsConnectionSyncResult cmdlet or this PowerShell script to identify the users for whom the mapping failed. Make sure that the users in the mapped team match the users in the WFM instance.
Unable to map a team or teams in this batch. This designated actor profile doesn't have team ownership privileges. Make sure your Microsoft 365 system account (also known as designated actor) is added as a team owner.
If you’ve changed your Microsoft 365 system account, add that account as a team owner, and update the connection settings to use that account.
This team is already mapped to an existing connector instance. Unmap the team from the existing connection by using the Remove-CsTeamsShiftsConnectionTeamMap cmdlet. Or, create a new connection to remap the team.
This timezone is invalid. The timezone passed in is not using tz database format. Make sure that the time zone is correct, and then remap the team.
We can't find this connector instance. Map the team to an existing connection.
This AAD team couldn't be found. Make sure that the team exists or create a new team.