Page History
...
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
...
"Certain Segments/Portions of the scan cannot be verified"?
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.
...
The tab, when opened, will by default show you a list of available scans for the period selected. In the top left, you can select between Teams and Outlook to look at the individual scans per service. Scans are available for up to 90 days back.
The table has several columns:
...