MS Teams bot not able to capture all the participants from the bridge meeting

AmanK7272718100
Tera Contributor

When initiating a bridge , people/groups who are part of initial window are captured in the 'notify_participant' table, but if a user joins using the bridge link later, the details are not getting captured in 'notify_participant' table. 

What I understand is that, MS teams should be polling at a certain frequency and ideally should be able to capture all participant records, however Service now folks said that the Azure user mapping table (sn_now_azure_user.LIST) is populated only during the initial bridge creation process.
As a result, users who join the meeting later through the bridge link, particularly external users, cannot be automatically mapped to sys_user records.

 

Can anyone help, This looks to be incomplete solution or Am I missing something?

4 REPLIES 4

Tanushree Maiti
Tera Patron

Hi @AmanK7272718100 

 

Is notify Connector installed in your instance?

Use Notify connector for Microsoft Teams with a major incident 

https://www.servicenow.com/docs/r/washingtondc/servicenow-platform/notify/r_NotifyTables.html

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

Hi Tanushree, Yes we have notify Connector installed. Now, the record gets created in notify_participant table... but active flag never turns true if I join using the bridge link from INC form itself. 

 

AmanK7272718100_0-1782808536370.png

 

Any idea why this is happening?

Hi @AmanK7272718100 

 

Could you validate corresponding OOB BR. Is it active? customized?

 

https://www.servicenow.com/docs/r/zurich/servicenow-platform/notify/r_NotifyBusinessRules.html

 

 

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

Apparently, the azure ID is also not getting populated 

 

AmanK7272718100_1-1782808841271.png