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.
Some scenarios:
- 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
Olivier Jacques
shared this idea
We have a solution for this ask and have moved this on our backlog! Keep watching here for updates as we get closer to completing this work.
54 comments
-
Dmitry Kolpakoff
commented
Any updates? We started to rolling Teams and on-premises bots will be very useful.
-
Ron Izraeli
commented
Hi Alex, any updates?
-
Daniel Berber
commented
Hi Alex, also looking for an update on this?
-
Justin
commented
@alex - It has been 4 months since your comment. Any news?
-
Alfian Ramadhan
commented
Would be great to hear the latest update for this uservoice
-
Vijayakumar Ramdoss
commented
Thanks
-
John Smith
commented
This would be great
-
Anonymous
commented
Guys this is the reason why we would choose slack over teams
-
Chris G. Williams
commented
This would be fantastic.
-
Justin
commented
This! The Microsoft view of bots and chatops is very off the mark. In order for Teams to be taken seriously by orgs that have already (or are ready to) implemented Chatops, Teams needs to be able to compatible with existing on-prem bot technologies and develop on-prem bot/chatop tech within the MS ecosphere via PoSH and Graph. MS needs to stop assuming that everyone is a dev and has no issue with writing their own bot from scratch.
-
Dan
commented
I would be interested in seeing this added as a feature as it would assist us with the adoption & overall usefulness of Teams.
-
Marcinius Turelles
commented
This is a must. I mean even Discord and Slack has this ability.
-
Anonymous
commented
Without this feature adoption would be very limited and fragmented in our organisation. Large corporates tend to have more than one solution through aquisitions and multiple dev teams, please consider this when evaluating priority.
-
Anonymous
commented
Major customer here -- looking to get ChatOps going for Teams --- it is a key developer experience requirement. Please prioritise.
-
Stephen Mandeville
commented
Guys please answer this come on
-
Stefano Lanzavecchia
commented
Over the months the rank of this issue has been going down and down and down. I don't think it's because of a lack of interest, but because those who needed the feature could not wait any more and went for another solution instead (*cough* slack *cough*). I am still hoping this will see the light of day one day...
-
J. Warwick
commented
For my company, it may not be as "critical" as it apparently is for others, but I can say that it would help drive adoption of Teams, and would allow us to deliver some internal services and get some more extensive integration with the MS business suite. We definitely have specific use cases where this would be a viable, maybe preferred UI.
-
Anonymous
commented
Come on Microsoft. This is a serious deficiency when competing with Slack.
-
Anonymous
commented
We need on-premises connectivity to bots to make Teams a ChatOps replacement for Hipchat. We are being forced to look at spending several hundred thousand dollars for Slack because Teams lacks a basic ChatOps feature. This is money we won't have to spend on other Microsoft services. Is there anything that can be done quickly utilizing Azure Application Proxies?
-
Anonymous
commented
Chat is for chatops. If I can't do this where I need to host a boy, there's no way this tool will become effective. Utterly necessary and a required feature. Please put this into the backlog and prioritize it!