Considerations

How I differed from what Brandon was doing

My bot is specifically not built to handle unprompted responses. It's a notification bot only with the ability to take action on some of those notifications. As such, you won't see any slash commands, etc. built into my manifest.
If you need to proactively message individual users, you'll likely need to create a database to store the tenant IDs and conversation IDs. That is best accomplished somewhere in Azure Tables or SQL and is outside of the scope of what I'm doing.
For now, these notifications are only going to the MSP tenant, so I haven't had need to maintain any kind of table of tenant, team, and channel IDs but that is being considered for future improvements as the bot can be used for all kinds of notifications to our clients.
The RPA that I use is Rewst. If you don't use Rewst, you may need to modify how some of your setup is completed to account for how your platform handles responses, etc.
The primary reason why I wanted to do this is to be able to build Adaptive Cards that people could take action on, and the action buttons would disappear once someone did so. The idea is that this should prevent duplication of efforts.
Verify that your base URL for sending messages to Teams is the same as what I have in my sub-workflows if you copy them to your environment. So far, I haven't had a need to turn those into variables.

Last updated 1 year ago

How I differed from what Brandon was doing

My bot is specifically not built to handle unprompted responses. It's a notification bot only with the ability to take action on some of those notifications. As such, you won't see any slash commands, etc. built into my manifest.
If you need to proactively message individual users, you'll likely need to create a database to store the tenant IDs and conversation IDs. That is best accomplished somewhere in Azure Tables or SQL and is outside of the scope of what I'm doing.
For now, these notifications are only going to the MSP tenant, so I haven't had need to maintain any kind of table of tenant, team, and channel IDs but that is being considered for future improvements as the bot can be used for all kinds of notifications to our clients.
The RPA that I use is Rewst. If you don't use Rewst, you may need to modify how some of your setup is completed to account for how your platform handles responses, etc.
The primary reason why I wanted to do this is to be able to build Adaptive Cards that people could take action on, and the action buttons would disappear once someone did so. The idea is that this should prevent duplication of efforts.
Verify that your base URL for sending messages to Teams is the same as what I have in my sub-workflows if you copy them to your environment. So far, I haven't had a need to turn those into variables.

Last updated 1 year ago