Allow on premise bots
By allowing bots which are hosted "on premise" (behind a company firewall), one allow to access systems from that company.
This is the situation for many companies where the infrastructure or services which need to be reachable by bots is not on the public internet.
- A bot is running behind a company firewall
- The bot connects to MS teams, joins a channel, and "listens" to conversations (outbound connection to the internet)
This enables interactions like:
- @bot, list defects (from an in-house issue tracker)
- @bot, add capacity to applicationx (after an authorization phase, on-prem application gets more servers for more capacity)
- [bot]> caution! applicationx experiences a 20% performance hit
The feature team is still investigating this item and a decision has not been made yet.
Karl Dietz commented
Now that Teams is being offered for free and promoted as Slack alternative (at least in german press) can support for on-premise bots be revisited?
Kevin Stevenard commented
@Warren, any update on this topic?
Olivier Jacques commented
@Warren, having team chat and other Microsoft Teams capabilities without this is totally missing the ChatOps train. Should we look at hosting a mattermost or something equivalent in parallel for ChatOps use cases because MS Teams does not support websockets to allow on-premise bots?
There has been some discussions and even an Hubot adapter: https://github.com/Microsoft/BotFramework-Hubot
But this only support bots on the public cloud.
We are looking for guidance.
Ryan Lancial commented
We own Teams, and I’ve played around with pushing notifications via webhooks. Cool, but missing the websocket option and, by extension, ease of extensibility to support modern bot frameworks (thanks Brandon) has held me back in pushing more usage of the platform within the organization. There is so much that Teams does really well, this is the area I feel needs improvement.
Josh King commented
I could have sworn that I'd left a comment on this a *long* time ago, ah well better late than never.
This is the ONE thing stopping our IT dept (and by extension our entire org) from adopting Teams as opposed to Slack. I've stood up a ChatOps POC in Slack and my team (no pun intended) is really keen to jump in full force but I'm putting the breaks on as I really want the platform we end up settling on being Teams... I mean it's part of what we're paying for after all.
At the moment we're at a cross roads, but I can't keep pumping the breaks on this for long. Eventually I'm going to have to give in and make a move. My fear is that this will end up being a move to Slack and at that stage we'll become entrenched on that service and it'll be a hard sell to transition over to Teams when it finally "catches up."
Appreciate the updates, and understand the technical hurdles. As an end user on the outside it's just frustrating that Teams didn't launch with feature parity compared to your biggest and most direct (imho) competitor.
Andrew Pla commented
Yeah, this is a pretty big deterrent for us fully moving to Teams. I'd like to be able to fully embrace Teams and bots really enables us to adopt the product.
Warren F commented
Same as Rob - Teams is a no go until websocket support or something comparable is in place.
Brandon Olin commented
Thanks for the update Warren. Can you share any information about priority for this item?
Rob Steenwyk commented
Definitely interested in this at my org, one of the things preventing a couple of our teams from switching from Slack.
Aaron Smith commented
Is there any update on this?
WALEED ABU YAHIA commented
I hope i can see this soon, honestly many industries and companies has a lot of regulations to host anything in cloud, like banking, nuclear, power. I think it is not a good idea from Microsoft to support only the cloud version, it looks like forcing people to use Azure. also If we take a look for other Bot framework they all support both. in my case i am stuck now and searching for other alternative rather than Microsoft Bot framework which I like a lot because of my company regulations which does not allow cloud computing. I hope if MS can specify a date when it will do it or if it will do it.
Nick Ellson commented
Would also like to see a simplified web socket / RealTimeMessage connection available to code bots against. Where might this be?
Stephan Hoermann commented
@Bill any update on this? Really interested to know when this might be available.
Bill Bliss commented
Sorry for the lack of response to this question - I just learned about it today. I head up the developer ecosystem for MS Teams.
We have some ideas on this that I will raise with you offline since I don't know how many of you check UserVoice regularly.
James McLachlan commented
Can anyone at Microsoft comment on whether there are any plans for this feature? One of the main potential blockers for us for Teams adoption is how we can integrate with our on-premise systems without the security concerns of allowing incoming connections via public URLs. I'm sure the various features available in Slack must have been looked at and considered as part of Microsoft's Teams planning so be great to hear their thoughts.
Brandon Olin commented
With Slack, this is accomplished with a websocket connection. This allows the bot to passively "listen" to conversations and trigger on certain messages. If that was an option in Teams, it would be pretty trivial to build bots against. Right now there is a fair amount of hoops to jump through to get a bot working. This makes it hard for companies interested in ChatOps to get an effort off the ground.
In my own project (PoshBot) (https://github.com/poshbotio/PoshBot) there is interest in supporting Teams as a backend. ChatOps bots are most useful when they act as an extension of your team and commonly require access to on-prem resources to do so.
Any update for this? No comments since July. To me the current model is little bit of a security hole. You have to have public facing interface that can be probed and must be maintained for security issues.
What is blocking this feature ? Is it a possible flood problem or lack of authorization ?
One solution I see for now is to have an authentication layer after publishing the bot, but not the best way obviously. Any communication on this? Is this even being considered?
Yes, please, on-prem bots are really necessary. I'd like to be able to have my bot talk to my jenkins server.