check before: 2025-12-08
Product:
Microsoft 365 for the web, Microsoft Graph, Teams, Windows
Platform:
Android, Developer, Online, Web, World tenant
Status:
Change type:
User impact, Admin impact, Retirement
Links:
Details:
Summary:
The TeamworkDevice (beta) API in Microsoft Graph will be retired starting December 8, 2025. Organizations should transition to managing Teams Rooms on Windows via the Teams Rooms Pro Management Portal (PMP), which will consolidate management for all Teams device types. No admin action is required for retirement.
Details:
[Introduction]
We're retiring the TeamworkDevice (beta) API from Microsoft Graph starting December 8, 2025.
Instead, we recommend using the Teams Rooms Pro Management Portal (PMP) to manage Teams Rooms on Windows devices, where we will continue to invest in secure, reliable, and supported device management capabilities.
When this will happen:
The retirement will begin gradually on December 8, 2025.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2025-11-06
updated:
2025-11-06
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
summary for non-techies**
XXXXXXX ... free basic plan only
Direct effects for Operations**
Disruption of Applications
Applications or integrations relying on the TeamworkDevice (beta) API will cease to function, leading to potential disruptions in workflows and processes.
- roles: Application Developers, IT Administrators
- references: https://learn.microsoft.com/microsoftteams/rooms/rooms-pro-management
User Experience Degradation
Users may experience a decline in service quality as applications fail, leading to frustration and decreased productivity.
- roles: End Users, Support Staff
- references: https://learn.microsoft.com/microsoftteams/rooms/rooms-pro-management
Increased Support Requests
The retirement may lead to an increase in support requests as users encounter issues with applications that depend on the deprecated API.
- roles: Help Desk Technicians, IT Support Managers
- references: https://learn.microsoft.com/microsoftteams/rooms/rooms-pro-management
Need for Documentation Updates
Organizations will need to update internal documentation to reflect the changes in API usage and management processes, which can be time-consuming.
- roles: Technical Writers, IT Administrators
- references: https://learn.microsoft.com/microsoftteams/rooms/rooms-pro-management
Stakeholder Communication Challenges
Failure to notify stakeholders about the change may lead to miscommunication and unpreparedness, impacting project timelines.
- roles: Project Managers, Business Analysts
- references: https://learn.microsoft.com/microsoftteams/rooms/rooms-pro-management
Configutation Options**
XXXXXXX ... paid membership only
Potentional Risks**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
explanation for non-techies**
The retirement of the TeamworkDevice (beta) API in Microsoft Graph is akin to a company deciding to phase out an old tool or process that was once useful but is now being replaced by something more efficient and comprehensive. Imagine you have been using a specific type of office software to manage your tasks and schedules. Over time, a new, more advanced software comes along that not only does what the old one did but also offers additional features that can help streamline your work even further. The company decides to retire the old software, encouraging everyone to transition to the new one.
In this case, Microsoft is retiring the TeamworkDevice (beta) API, which was used to manage Teams Rooms on Windows devices. They are shifting to the Teams Rooms Pro Management Portal (PMP), which will serve as a one-stop shop for managing all Teams device types. This is similar to consolidating various tools into a single, more powerful tool that can handle multiple tasks at once, reducing the need to juggle between different systems.
For organizations that have been using the TeamworkDevice (beta) API, this means reviewing any current applications or scripts that rely on it and preparing to transition to the new system. Just like when a company updates its internal processes, it’s important to inform all relevant team members and partners about the change to ensure a smooth transition. No immediate action is required, as the change will happen gradually, but being aware and prepared will help avoid any disruptions.
Overall, this transition is about moving towards a more integrated and efficient way of managing Teams devices, similar to upgrading from an old tool to a new, all-encompassing one that offers better support and reliability.
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
Last updated 2 months ago ago
