Published: July 12, 2024
Updated: August 9, 2024
Thank you very much for using Acall.
We would like to inform you that the Teams Webhook deprecation announced by Microsoft will affect the Teams integration function of Acall Reception.
Teams Webhook Deprecation
Microsoft has announced the deprecation of Teams Webhook.
Retirement of Office 365 connectors within Microsoft Teams
https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/
August 15, 2024 - New Webhook URLs cannot be createdOctober 1, 2024 - Existing Webhook URLs will stop functioning
December, 2025 - Existing Webhook URLs will stop functioning ※ URL must be updated by December 31, 2024
※ On July 23, 2024, Microsoft announced the postponement of the deprecation timeline.
Impact on Teams Integration
Teams integration function will continue to be provided.
There will be no change in the content of notifications or in the operation of receiving and responding to notifications. You will still receive visitor notification messages in Teams.
On the other hand, the method of setting up integration with Teams will be changed.
Until now, Teams Incoming Webhooks have been set to issue Webhook URLs for Teams channels.
From now on, the Microsoft Power Automate flow will be used to issue the Webhook URL and notify Teams.
There will be no change to the setup method on Acall Portal, but a new Power Automate setup will be required.
As a result, Microsoft's Power Automate is required for the Teams integration function.
The Power Automate license is included in the Microsoft 365 subscription.
Power Automate References
- https://www.microsoft.com/en-us/power-platform/products/power-automate
- https://learn.microsoft.com/en-us/power-automate/
Steps for switching to the new integration method (Power Automate)
Please follow the steps below.
1. Create Power Automate flow and issue Webhook URL
Please refer to the following help articles for setting up the flow
- Receive Visitor Notifications via Microsoft Teams
- Download the Power Automate package for Acall Visitor Notification
- Create a Power Automate flow for Acall visitor notification
2. Reconfigure service integration with Teams
Please follow the steps below to reconfigure the service integration.
- Click [Integration] > [Chat] in the side menu of Acall Portal and click [DISCONNECT] for Microsoft Teams.
- When [CONNECT] button is displayed, click the button and enter the Webhook URL issued in the Power Automate flow.
- If you see [DISCONNECT], the service integration has been completed.
* Teams will not receive visitor notifications until they are reconnected after disconnecting.
3. Reconfigure Webhook URLs for workers
Delete the existing Teams Webhook URLs set for workers and set the Webhook URL issued in the Power Automate flow.
Batch settings can be made via CSV.
4. Reconfigure Webhook URLs for groups
Delete the existing Teams Webhook URLs set for groups and set the Webhook URL issued in the Power Automate flow.
Batch settings can be made via CSV.
Additional Notes
URLs from the new method (PowerAutomate's Webhook) and the old method (Teams Channel Connector's Webhook) can coexist.
You can use your existing Webhooks for the time being, and use PowerAutomate's Webhooks only for newly created Teams channels for now.
Please check Microsoft's instructions and follow the above steps to fully migrate to PowerAutomate before the existing Webhooks are completely abolished.
Steps 2 through 4 do not have to be completed all at once. For example, you can complete Step 2 but not Steps 3 and 4 without any problems.
We apologize for any temporary inconvenience this may cause and appreciate your understanding and cooperation.
If you have any questions or concerns, please feel free to contact our support team.
https://help.workstyleos.com/hc/en-us/requests/new