xMatters Teams Integration broken in last week?

Not Yet Reviewed

Had anybody noticed that the the xMatters bot is now asking for users to log in when they open the bot?  I know that xMatters can now send a message to a person with a Teams device (I've used it, it's nice!) but it seems to have broken the "system" login that allows users to simply look up who's on call.  When they go into xMatters, they are now presented with a log in request.  When they try to login, they get a system denied, then an option to login in at the bottom of the screen.  If they click login, SAML logs them in, and the normal xMatters window appears.   If the user closes this out, and tries again, they are presented with the "Allow xMatters to access your Teams" prompt.   

Some users can click allow, some cannot.  I assume this is based on the role they have in xMatters.  

However, what happned to the "system login" that was setup when we first installed the bot.  I logged in with the generic account that we created in xMatters when we first set this up.   


Is anybody else having this issue?  Thought I'd check here before opening a standard support case. 



1 comment
Date Votes

Please sign in to leave a comment.

  • Hi Jason,

    The xMatters App for Microsoft Teams has 2 concepts of connections to xMatters.

    1. The global connection that is used when any user interacts with bot commands like the "find", "on-call" and "invite" commands that have been a mainstay in the bot's use for years.

    2. A Personal connection that was introduced recently to allow users to configure receiving notifications through Microsoft Teams and interact with incidents via the xMatters message extension and Meeting Tabs.

    While users will be prompted to login when interacting with the xMatters App's home tab, the existing bot commands should continue to function with the original "Global" connection across your Teams channels and in Personal Chats with the bot.

    Let me know if you're seeing the bot commands working differently after the update, but the recent changes should not have changed your existing global connection, just given you more options for interacting with xMatters from within Microsoft Teams. 


Didn't find what you were looking for?

New post