MS Teams - Webex Calling client Issue

[derek-hartman]

Ok, I am not 100% sure on the best way of doing this but just trying to give better functionality to our end users.

Scenario: User is using MS teams and to make sure everything works as expected Webex Calling is installed and signed in. Well after 60 days the token expired and Webex Calling is logged out of teams. 

The Issue: Now that the user is no longer signed in then functionality for our systems break down. 

Resolution ideas

Idea 1: Which I think is the most feasible - SCCM baseline script to check that Teams - Webex calling is not active send a toast alert in windows saying they are not logged in and should login.

Question: I have been digging through teams logging but I can't find anything about webex calling - like event viewer of .log files. Does the webex calling app have any kind of local logs or something so that I can see that the user is no longer signed in. 

Idea 2: Idk if its even possible - have SCCM baseline call a script every day to auth in the background as the auth is desktop SSOd so it refreshes the auth token everyday. 

[Jonathan Schulenberg]

Is this happening for everyone or only the users that don’t click on the Webex Calling app/tab within MS Teams as least once every 60 days?

What are your token policies in Control Hub - and is the refresh token allowed to auto extend?

[derek-hartman]

Ok, yes, I found the documentation on the refresh token so that should keep the users from being logged out. But management is still worried that the continue/login button will be missed by the end users. I don't know if you'll know what the command would be but I been looking at MS Teams deeplinks. 

This will launch the app - start msteams:/l/app/0924e969-85d8-4acb-8687-faacd6abd228

And with fiddler I found that the button reaches out to msteams-calling.webex.com I just haven't pieced together yet how to auto launch the login programmatically.

Thanks!