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:

In development

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 begins mid-January 2025 and ends late January 2025. Organizations should migrate to the production endpoints and update their applications accordingly. This is detailed under Microsoft 365 Roadmap ID 422813.

Details:
Updated October 24, 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-January 2025 (previously mid-November) and expect to complete by late January 2025 (previously late November).

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:
General Availability

Created:
2024-10-24

updated:
2024-10-25

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 to the production endpoints 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

User Experience Degradation
If applications are not updated to the production API, users may experience disruptions or inconsistencies in shift management functionalities, leading to frustration.
   - roles: End Users, Team Managers
   - 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 Gaps
Inadequate preparation for the API transition may result in outdated documentation and insufficient training for users, hindering effective use of the new features.
   - roles: Training Coordinators, Support Staff
   - 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**

XXXXXXX ... free basic plan only

Potentional Risks**

XXXXXXX ... paid membership only

IT Security**

XXXXXXX ... paid membership only

explanation for non-techies**

Microsoft is transitioning the Shifts Graph APIs for Microsoft Teams from a beta version to a production version. This change is similar to moving a product from a prototype stage to a full-fledged, market-ready product. Just like how a car model goes through various tests and improvements before it is released to the public, these APIs have been tested and refined in the beta stage. Now, they are ready for wider use with improved stability and reliability.

For organizations using these APIs, this means it's time to switch from the beta version to the production version. Think of it like upgrading from a trial version of software to the full version. The trial version might have some limitations or bugs, but the full version is more polished and dependable. To make this transition, organizations need to update their applications to use the new production endpoints. This is akin to updating your address book when a friend moves to a new house; you need to make sure you're sending your messages to the right place.

The rollout of this update will start in mid-January 2025 and finish by the end of January 2025. While it's possible to continue using the beta version for now, it's recommended to switch to the production version to take advantage of the improvements. Just like how you would eventually want to move from a test drive to owning the car itself for a better experience.

To make this switch, organizations should change their API calls from the beta endpoint to the v1.0 endpoint. It's important to test applications thoroughly to ensure they work well with the new version, similar to how you would test a new software update on your phone to make sure all your apps still function correctly. Checking for any differences between the beta and production versions and updating any relevant documentation is also crucial, much like updating a user manual when a new feature is added to a product.