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)

Microsoft Teams logging details

There are three types of log files automatically produced by the client that can be leveraged to assist in troubleshooting Microsoft Teams.
·         Desktop logs
·         Debug logs
·         Media logs

Desktop logs

Desktop logs, also known as bootstrapper logs, contains log data that occurs between the desktop client and the browser.

To open the client log (logs.txt in the Teams cache), click the Teams icon in the system tray and then Get Logs from the menu. Notepad loads the file and you can browse it to your heart’s content before giving up and sending it to Microsoft.
1.    Right-click the Microsoft Teams icon in your application tray, select Get Logs

Diagnostic Log

 The CTRL-Shift-Alt-1 key combination generates a diagnostic log file on Windows workstations, while Command + Option + Shift + 1 generates the file on a Mac. Teams creates the diagnostics log in the Downloads folder on the workstation and creates a name by combining MSTeams Diagnostics Log with the current timestamp.
%downloads%\MSTeams Diagnostics Log <timestamp>.txt
Debug logs show the following data flows:
·         Login
·         Connection requests to middle tier services
·         Call/conversation

Media Logs

Media logs contain diagnostic data about audio, video and screen sharing. They are required for support cases only upon request and can only be inspected by Microsoft. The following table outlines the log location.

Network Traces

Microsoft might ask for a network trace to help resolve some support requests. use Fiddler or Charles Proxy

Note: As some blog says Teams is not a Sip client so cannot use Snooper kind of tools for diagnostics. 

Microsoft Teams Training

End user training for Microsoft Teams

Use these training resources to help users in your organization get the most out of Teams.

·         Watch Teams training videos


Use these teams training resources to help users in your organization get the most out of Teams.

Manage team collaboration with Microsoft Teams

Free course from Microsoft Learn
Manage team collaboration with Microsoft Teams introduces you to the features and capabilities of Microsoft Teams, the central hub for team collaboration in Microsoft 365. 
Find the free course for  Manage team collaboration with Microsoft Teams