Hello!
We are in the process of Implementing Major Incident Management with the Teams with the Notify connector plugins to create the Teams meeting/Call and run the MI event. From the MI Workbench, Collaborate tab, we "Initiate" a Teams Call from the ICT Task. Add the participants and start the call. All of the participants receive a "Teams call" to join the meeting on their PC and/or Mobile device. We would like to turn this off or give the Users the ability to turn off this particular notification, but there is a catch, which I will explain...
Through some investigation work, we identified that the users are being added as Participants to the call and that is why they are receiving the Teams call on their respective device(s). By default, all participants would see something like this Teams for MI events, regardless of if they joined the call or not.
The "ICTnnnnnnn..." channels are for the chats that took place during the MI meeting/call.
We made an update and only added the person initiating the call as the sole participant. While this prevented all the other users invited to the call from receiving the Teams call on their device there was some fall out. Because they were not defined as a "Participant", they do not see the respective "ICTnnnnnnn..." channel for that MI meeting/call until they join. And then they are limited to only seeing the Chat content from when they join, not the history. If they do not join at all then they do not see the channel at all. More often than not we have users who are invited to an MI Teams call but can't make it, however, need to be able to go back and review the Chat history from within the Teams app.
So, in theory, that means they need to be added as a participant to the meeting. Which means they would receive the Teams call on their device, and we need to bypass this part.
We have tried to remove the "Calls.InitiateGroupCall.All" from the app in Azure, but that broke the process, as expected. We also tried to apply a "Call restriction" Policy to the Service User account in Teams, but that didn't stop the call from going out.
Please let me know if you need any additional clarification. Any assistance or guidance would be greatly appreciated.
Regards,
Jeremy
