Custom Response or Limit Response to MS Teams Integration

[Steven Young]

Good Morning everyone,

I'm working on understanding the SN to MS Teams integration for virtual agent/bot communication.
We've got the bot setup in Azure/O365 and setup in ServiceNow.  It's communicating as anticipated.

That is great news, but also part of my problem.  See, in Azure, we have everyone in the organization together, so we cant really limit who can see the bot within MS Teams.  However, within ServiceNow, we have them organized into different companies, Org Codes, Sections, whatever.  

What we are looking to do is limit who's allowed to use the bot by criteria within ServiceNow.  So here is what i'm trying to do.

1. Not mess with the OOB Flow stuff for the integration.
2. Not mess with the OOB SN to Teams Integrations stuff.

3. If user A is allowed to use the bot, then everything works.

4. If user B is not allowed to use the bot, they get a custom response to include a url to a different place.

If anyone has any foresight about #4 here, i'm all ears.

Currently, this works, but is not ideal.   I created a Business Rule on the "sys_cs_conversation" table that is before insert, and it had criteria that says if user belongs to org code xxxx,  abort insert.
This prevents the record from being created from the teams integration, and ultimately, doesn't run anything.

I'm still looking at other options, just wanted to see if anyone else has done something like this?