For production instances, Yes.
If you are trying it on sub-prod instance here is a work-around.
Open "subscribe teams chat" scheduled job and check the underlined code below.
Please execute this scheduled job once again.
There are more steps below you can check after the script is executed.
You should have a Chat profile created with your record like below
and the Collab user reference record should refer to your sys_user record like below.
Yes indeed, for the moment I'm making a pock so I can present this set-up.
So no implementation on a production environment.
On the following screenshot, you can see that the message adding the application to the chat works:
In the following table: sys_cs_collab_provider_user_profile I have all the users present in the AD.
For this table: sys_cs_collab_user I have a few teams users linked to their Servicenow user for testing purposes.
However, I'm back to the same problem of :
1 - On the SOW, I open an incident.
2- On the Sidebar in the Collaborate tab, I open a chat with a teams user.
3- I send a message.
4- The chat opens on the Teams side with the application and the user(s) added to the chat.
5- The message is present.
6- One of the users on the Teams side sends a message => Nothing received on the ServiceNow chat side.
Is this normal because I don't have any subscriptions on the Azure side, so billing can't be performed and the API doesn't launch any requests?
