Retirement of the TeamworkDevice (beta) API in Microsoft Graph
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. 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. How this affects your organization: Who is affected: Organizations using applications or integrations that rely on the TeamworkDevice (beta) API in Microsoft Graph. What will happen: Applications or integrations using the /beta/TeamworkDevice endpoints will stop working. There are no plans to support Graph APIs for Teams Devices. Teams Rooms on Windows should be managed through the Teams Rooms Pro Management Portal (PMP). PMP is being consolidated as the single portal for managing all Teams device types, including Teams Rooms on Android, Teams Phones, and Teams Panels. Additional updates on this consolidation effort will be shared in the coming months. What you can do to prepare: This change will happen automatically and gradually, starting December 8, 2025. No admin action is required to complete retirement. If your organization has dependencies on the TeamworkDevice (beta) API, we recommend: Review any applications, scripts, or integrations that use /beta/TeamworkDevice endpoints. Update internal documentation. Notify relevant stakeholders or partners about this upcoming change. Compliance considerations: Learn more: Microsoft Teams Rooms Pro Management No compliance considerations identified, review as appropriate for your organization. Message ID: MC1183294
The post Retirement of the TeamworkDevice (beta) API in Microsoft Graph appeared first on M365 Admin.
Published on:
Learn moreWe can help you with Retirement of the TeamworkDevice (beta) API in Microsoft Graph
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
Microsoft Copilot (Microsoft 365): Local inferencing
Local inferencing expands Microsoft Copilot’s sovereign controls by enabling AI inferencing for supported Copilot interactions to occur within...
Dynamics 365 Customer Service: Quality evaluation supports knowledge source in criteria
Criteria questions can now use knowledge sources to help evaluate customer interactions. This allows organizations to ground evaluation criter...
Microsoft Viva: Ability for leaders to publish Power BI reports
Microsoft Viva Insights is extending its report publishing capabilities from analysts to leader personas such as Chief Officers, Managers and ...
Dynamics 365 Customer Service: Detailed quality evaluation score breakdown
Evaluation details now include a scoring breakdown at the overall, section, and question level. Users can see how the final evaluation score w...
Dynamics 365 Customer Service: Support Not Applicable answer option for quality evaluation criteria
Criteria questions now support a Not Applicable answer option. When a question is marked as not applicable, it is excluded from scoring instea...
Dynamics 365 Customer Service: Inactivate quality evaluation records
Quality managers can now inactivate evaluation records that should no longer contribute to scoring or reporting. Inactive evaluations are pres...
Microsoft Teams: Granular Conditional Access for Teams meetings
Granular Conditional Access for Teams meetings gives organizations greater control over access to sensitive meetings. Administrators can apply...
Customized PowerBI reports behavior after major report updates
Microsoft Viva Insights customized Power BI reports will remain tied to their original report versions and won’t auto-update with major report...
Microsoft SharePoint: Changes to the FAQ web part authoring experience
The SharePoint FAQ web part will shift AI-assisted FAQ creation to Copilot in SharePoint, while retaining manual FAQ editing in the web part. ...
Microsoft 365 Copilot: Federated Copilot connectors support create, update, and delete actions
Microsoft 365 Copilot’s federated connectors will support create, update, and delete actions in third-party services starting October 20...