Sunday, September 29, 2019

TEAMS Sign in process flow

TEAMS Sign in process flow to identity what's expected and act accordingly. In this article, we will focus mainly on TEAMS Client login.

How does Sign IN work?

The client reaches and start the bootstrap. Under JSON we should be able to view all features are enabled or not enabled:
·         The page will present a sign in page with a frame from and follow an OAUTH authentication.
· - will return where the OAUTH auth will happen.
·         A token will be generated and the client and can be verified on the 302 message from
·         Token expires_in=3599 (1h)
·         From this point the client execute all the requests with the access token on the HTTP header:

How does the client identify where to register?
·         The client will always attempt to register to that is the URL of the service.
·         Once registered, the client will POST to that will reply with a JSON with the services the client have to register:
·         Client do authenticated requests to the ams, chat service, middleTier, msImageService and search services on respective geographical region.

How does Sign IN work in SSO?

Web logs

·       Press (CTRL+ALT+SHFT+1) in client to download logs (Electron Logs)
Note - be sure to use the 1 on top of keyboard and not 1 from number pad as that maps to a different key
·       %downloads%\MSTeams Diagnostics Log <timestamp>.txt
Desktop logs
·       %appdata%\Microsoft\Teams\logs.txt
Contains framework and bootstrapping info
App Bootstrap process
Plugin initialization
Update Management
Some SSO info when using SSO builds (Desktop Auth)


  1. It’s very informative and you are obviously very knowledgeable in this area. You have opened my eyes to varying views on this topic with interesting and solid content. musterverfahrensdokumentation gobd datev

  2. Cool stuff you have got and you keep update all of us. buy instagram likes best