MC916866 – (Updated) Microsoft Teams: Shifts Graph APIs in beta moved to production (v1.0)

Product:

Microsoft Graph, Teams, Teams Shifts

Platform:

Developer, Online, US Instances, Web, World tenant

Status:

Launched

Change type:

Admin impact, Feature update, Updated message, User impact

Links:

422813

Details:

Summary:
The Shifts Graph APIs for Microsoft Teams are moving from beta to production, enhancing stability and reliability. Rollout starts mid-February 2025 and ends late February 2025. Organizations should migrate to the production endpoints and update their API calls from beta to v1.0. This update is associated with Microsoft 365 Roadmap ID 422813.

Details:
Updated December 20, 2024: We have updated the rollout timeline below. Thank you for your patience.
The Shifts Graph APIs will transition from beta to production. This change brings enhanced stability and reliability to the APIs, ensuring a seamless experience for developers and users.

This message is associated with Microsoft 365 Roadmap ID 422813.
[When this will happen:]
General Availability (Worldwide and GCC): We will begin rolling out mid-February 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January).

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:
General Availability

Created:
2024-10-24

updated:
2024-12-21

Task Type

XXXXXXX ... free basic plan only

Docu to Check

XXXXXXX ... free basic plan only

MS How does it affect me

XXXXXXX ... free basic plan only

MS Preperations

XXXXXXX ... free basic plan only

MS Urgency

XXXXXXX ... free basic plan only

MS workload name

XXXXXXX ... free basic plan only

linked item details

XXXXXXX ... free basic plan only

summary for non-techies**

XXXXXXX ... free basic plan only

Direct effects for Operations**

API Migration Impact
Failure to migrate API calls from beta to production may lead to application failures or degraded performance, affecting user access to shift management features.
   - roles: Developers, IT Administrators
   - references: https://learn.microsoft.com/graph/api/overview?view=graph-rest-1.0, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=422813

Compatibility Issues
Incompatibility between beta and production APIs could result in unexpected behavior or errors in applications, negatively impacting user experience.
   - roles: Developers, End Users
   - references: https://learn.microsoft.com/graph/api/overview?view=graph-rest-1.0, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=422813

Documentation Updates
Lack of updated documentation regarding the API changes may lead to confusion and improper usage of the new endpoints, affecting user operations.
   - roles: Developers, IT Support
   - references: https://learn.microsoft.com/graph/api/overview?view=graph-rest-1.0, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=422813

Configutation Options**

XXXXXXX ... paid membership only

Opportunities**

Enhanced API Stability and Reliability
Migrating to the production endpoints of the Shifts Graph APIs will enhance the stability and reliability of applications using these APIs. This is crucial for applications that depend on real-time data and user interactions, reducing downtime and improving overall user experience.
   - next-steps: Plan a migration strategy for all applications using the beta endpoints to ensure they transition smoothly to the production endpoints. Conduct thorough testing of applications post-migration to confirm compatibility and functionality.
   - roles: Developers, IT Administrators, Product Managers
   - references: https://learn.microsoft.com/graph/api/overview?view=graph-rest-1.0, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=422813

Improved User Experience
With the move to production, users can expect a more stable and reliable experience when using applications that integrate with the Shifts Graph APIs. This can lead to increased user satisfaction and productivity as users face fewer interruptions and issues.
   - next-steps: Gather feedback from users regarding their experience with the current beta APIs and address any pain points. After migration, continue to monitor user feedback to ensure that the production APIs meet their needs effectively.
   - roles: End Users, User Experience Designers, Support Teams
   - references: https://learn.microsoft.com/graph/api/overview?view=graph-rest-1.0, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=422813

Documentation and Training Updates
As the API transitions from beta to production, it is essential to update all related documentation and provide training to relevant staff on the new features and changes. This will ensure that all users and developers are aware of the best practices and any new functionalities available in the production version.
   - next-steps: Create a comprehensive update plan for documentation and training materials. Schedule training sessions for developers and users to familiarize them with the new API version and its capabilities.
   - roles: Technical Writers, Training Coordinators, Developers
   - references: https://learn.microsoft.com/graph/api/overview?view=graph-rest-1.0, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=422813

Potentional Risks**

XXXXXXX ... paid membership only

IT Security**

XXXXXXX ... paid membership only

explanation for non-techies**

XXXXXXX ... free basic plan only