You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if there was a way to hook to this tool from a chat client, so that I could tag a bot with the message to post. For example, chat input = "@ChatBotForAZDBanner Post this message on my AZD banner" . I realize this solution goes beyond your extension alone, and would require the chat client to have capabilities for calling the Azure REST API. But assuming the client was capable, could this extension expose an API method within AZD?
Also, I've noticed there are already a few Azure Devops plugins for MS TEAMS, but they use web hooks to simply recieve info from AZD, not push anything. In fact, it looks like there is no current capability in MS Teams for any type of connections (bots) that push data out to external endpoints - at least as far as I can tell. Any idea if "ChatOps" is something Microsoft has on the roadmap?
The text was updated successfully, but these errors were encountered:
It would be great if there was a way to hook to this tool from a chat client, so that I could tag a bot with the message to post. For example, chat input = "@ChatBotForAZDBanner Post this message on my AZD banner" . I realize this solution goes beyond your extension alone, and would require the chat client to have capabilities for calling the Azure REST API. But assuming the client was capable, could this extension expose an API method within AZD?
Also, I've noticed there are already a few Azure Devops plugins for MS TEAMS, but they use web hooks to simply recieve info from AZD, not push anything. In fact, it looks like there is no current capability in MS Teams for any type of connections (bots) that push data out to external endpoints - at least as far as I can tell. Any idea if "ChatOps" is something Microsoft has on the roadmap?
The text was updated successfully, but these errors were encountered: