cancel
Showing results for 
Search instead for 
Did you mean: 

11.5 compatibility to Microsoft Teams

Rob_Gonzalez
05 Base Camper

11.5 compatibility to Microsoft Teams

Is Prognosis 11.5 compatible with 'Microsoft Teams' ?  We now use Skype for Business for our IM, conference and screen share capabilities but we are looking to upgrade to Microsoft Teams in 2019.  We are on now on 11.1 but will be upgrading to 11.5 in 2019 as well.  If 'Teams' is not monitorable by Prognosis this may affect our decision.  Please advise.

 

Rob with CSAA Insuance Group

4 REPLIES 4
SCOTT_BALDWIN
Expert

Re: 11.5 compatibility to Microsoft Teams

Hello Rob,

 

As of Prognosis 11.5, Microsoft Teams can not be monitored by Prognosis.

 

IR Development has discussed adding Microsoft Teams monitoring to Prognosis at some point in the future, but it is not yet part of Prognosis.

 

With the above stated, Microsoft Teams relies on several components currently part of Prognosis monitoring capabilities. A discussion with your Account Manager about the monitoring needs of the environment would be a good next step.

 

Thank you for the question,

Scott Baldwin

 

Rob_Gonzalez
05 Base Camper

Re: 11.5 compatibility to Microsoft Teams

Thanks for the info!!

 

~Rob Gonzalez

MichaelMessner
05 Base Camper

Re: 11.5 compatibility to Microsoft Teams

Hi,

I would like to ask if in the mean time IR Prognosis is usable also with TEAMS ? we have also a SFB on prmise enviroment and are evaluating if we migrate all to Microsoft Teams.

 

Regards

Michael

SCOTT_BALDWIN
Expert

Re: 11.5 compatibility to Microsoft Teams

Hello Michael,

 

As of 2020-02-03 the latest Prognosis version is 11.7. Prognosis 11.7 still supports Microsoft Skype for Business (SfB), but Microsoft Teams monitoring is targeted for a future Prognosis release.

 

IR Development is aware SfB will be phased out by Microsoft and replaced by MS Teams. Adding MS Teams monitoring is on the Prognosis Feature Roadmap and adding MS Teams monitoring to core Prognosis is a priority for IR Development.

 

Thank you,
Scott Baldwin