An API that connects multiple Microsoft services, enabling data access and automation across platforms
Teams Shifts workforceIntegration callback not triggered by “Share with team”
Hi Microsoft Support,
We are integrating with Microsoft Teams Shifts using Microsoft Graph workforceIntegration and synchronous change notifications.
We have observed different callback behavior between sharing an individual shift and using the schedule-level "Share with team" action.
Scenario 1: Individual Shift -> Share
When a manager edits an individual shift and clicks Share, our workforceIntegration callback URL receives the expected synchronous change notification for the shift.
Scenario 2: Schedule -> Share with team
When a manager makes a draft shift change and then uses Share with team from the main Shifts schedule page, our workforceIntegration callback URL does not receive any notification.
However, we confirmed through Microsoft Graph that the underlying shift resource does change.
Before "Share with team":
{
"draftShift": {
"startDateTime": "...",
"endDateTime": "..."
},
"sharedShift": null
}
After "Share with team":
{
"draftShift": null,
"sharedShift": {
"startDateTime": "...",
"endDateTime": "..."
}
}
The workforceIntegration is active, associated with the schedule, and configured to support the shift entity. Since individual shift sharing successfully triggers the callback, the callback endpoint itself appears to be functioning correctly.
Could you please clarify:
- Is the schedule-level "Share with team" operation expected to trigger workforceIntegration synchronous change notifications for affected shifts?
- If not, is this behavior by design or a current limitation of workforceIntegration?
- Is there a supported Microsoft Graph mechanism for detecting when draft shifts are published through "Share with team"?
- If workforceIntegration is expected to receive these notifications, could this be a bug in Teams Shifts?
Thank you.