Microsoft has deprecated Incoming Webhooks for Microsoft Teams. As a result, Poly Lens Microsoft Teams notifications now use Power Automate Workflows as the supported replacement. For more information on this retirement notice, please visit Microsoft Dev Blogs.
To continue receiving Poly Lens notifications in Microsoft Teams channels, administrators must manually create a Power Automate workflow and update the Teams notification configuration in Poly Lens with the generated HTTP endpoint. This change ensures continued compatibility with Microsoft Teams and aligns with Microsoft’s supported automation and security model going forward.
Required Action: Create a Power Automate Workflow
Follow the steps here in Poly Lens Help to create a Power Automate Workflows that replaces the deprecated Teams webhook.
What’s Changing
- Incoming Webhooks for Microsoft Teams are retired (Microsoft managed change).
- Poly Lens no longer supports direct webhook-based Teams notifications.
- Power Automate workflows are now the required integration method for delivering Lens notifications to Teams channels.
Important: This is a manual, one-time setup per Teams channel.
What’s Not Changing
- Notification types supported in Poly Lens remain the same:
- Software Updates Available
- Devices Offline
- Licenses Expiring
- Notifications are still delivered directly into Microsoft Teams channels
Who Needs to Take Action
- Poly Lens administrators
- Admins currently using Poly Lens Notification with Microsoft Teams Incoming Webhooks
Known Limitations & Notes
- Power Automate Premium licensing is required and governed by your Microsoft licensing and tenant policies
- Each Teams channel requires its own Power Automate workflow
- Workflow creation must be done by a Teams user with appropriate permissions
- This process replaces all Incoming Webhook based integrations
We appreciate your cooperation in ensuring a seamless transition. Visit Notification Center - Teams Notifications for more information.