The Connectivity Journey tab is located on the User Experience page for an individual user and represents the full network path a user takes while connecting to Microsoft Teams or Outlook.
What is the Connectivity Journey:
Users have different ways of connecting to Microsoft depending on their network type and time of day. A managed network may direct a user to the nearest entry point at MSFT while an unmanaged one could take a completely different route. The Internet Service Provider can also make a significant difference. On the Connectivity Journey tab, you can see the exact route that a user takes while connecting to Microsoft Teams. Open the tab and select a date and a time you would like to see the connectivity journey for. This will open a visual representation of the connectivity journey as well as a complete list of all hops for that time & date.
What is meant with Partial or incomplete results?
The connectivity journey table will show you all measurements that were taken, regardless of their completeness. A partial (incomplete) scan can happen, if too few ISP Hops or Microsoft Hops have been detected. This means that some hops are missing, and the connectivity journey is likely not complete or accurate. There are several reasons for this like network providers who sometimes hide or block certain traceroute data or parts of the network path. TCP Traceroute being blocked or CGNAT at the ISP level are common examples of this. If we detect this, we will indicate that scan results are potentially partial or inaccurate by placing a yellow exclamation mark icon next to the time column in the connectiviy journey scan result list and on the visualization itself. The results will still be listed with all hops we do detect.
Using the Connectivity Journey
The tab, when opened, will by default show you a list of available scans for the period selected.
The table has several columns:
- Scan time: When the measurement was done.
- Device IP Address: The IP address that the End-User device used at that time.
- User Network IP: Shows a managed Network IP subnet or "Unmanaged" if the user was on an unmanaged network (e.g. HomeOffice).
- User Network Type: Shows either Ethernet or Wireless
- First ISP: Which was the first ISP detected?
- Last ISP: Which was the last ISP detected before the data entered Microsoft?
- RTT columns: What was the time it took for data to go back and forth on the Internal Network vs, ISP vs Microsoft
When you select an individual scan (by clicking on it), the subsequent page will show you further details in the form of a graphical overview of the journey and the time it takes to move through the three parts of the journey:
- Internal Network
- Internet Provider
- Microsoft
This allows you to see in which part of the journey delays are taking place. It also shows you information like the DNS server used, and the Microsoft data center the user connected to.
Below the graphical interface, a table shows each of the hops along the journey with details for each hop and the jitter encountered on each hop.
Navigation
To go to another scan or to return to the scan table, use the buttons in the top of the tab.
