Office 365 networking principles

Copper Contributor

Jun 20, 2021

Is access to the SharePoint front door service better when your trace route include answers from spo-msedge.net?

Example output:

1167-ipv4e.clump.prod.aa-rt.sharepoint.com. 60 IN CNAME 19899-ipv4e.farm.prod.aa-rt.sharepoint.com.
19899-ipv4e.farm.prod.aa-rt.sharepoint.com. 60 IN CNAME 19899-ipv4e.farm.prod.sharepointonline.com.akadns.net.
19899-ipv4e.farm.prod.sharepointonline.com.akadns.net. 300 IN CNAME 19899-ipv4.farm.prod.aa-rt.sharepoint.com.spo-0004.spo-msedge.net.
19899-ipv4.farm.prod.aa-rt.sharepoint.com.spo-0004.spo-msedge.net. 240 IN CNAME spo-0004.spo-msedge.net.
spo-0004.spo-msedge.net. 240    IN      A       13.107.136.9

I have noticed when spo-msedge.net is not involved, other IPs such as 40.108.195.53 is returned, which is further hops to reach inside the MS network.

Tracing route to 13.107.136.9 over a maximum of 30 hops

  1   148 ms   165 ms   146 ms  10.29.0.1
  2   198 ms   199 ms   174 ms  162.253.68.126
  3   186 ms   183 ms   156 ms  vl62.br02.lax03.as46562.net [184.170.244.8]
  4   174 ms   186 ms   187 ms  184.170.244.0
  5   202 ms   200 ms   202 ms  8075-lax.msn.net [206.223.123.17]
  6   207 ms   183 ms     *     ae27-0.ear01.lax30.ntwk.msn.net [104.44.41.74] <<<<< Entry point in MS network
  7   197 ms   173 ms   246 ms  ae30-0.lax-96cbe-1b.ntwk.msn.net [104.44.40.152]
  8   161 ms   170 ms   161 ms  13.104.141.87
  9     *        *        *     Request timed out.
 10   151 ms   167 ms   171 ms  13.107.136.9

Tracing route to 40.108.195.53 over a maximum of 30 hops

  1   155 ms   166 ms   160 ms  10.29.0.1
  2   189 ms   181 ms   154 ms  162.253.68.126
  3   163 ms   179 ms   174 ms  184.170.244.6
  4   173 ms   162 ms   155 ms  8075-lax.msn.net [206.223.123.17]
  5   145 ms   153 ms     *     ae23-0.ear01.lax31.ntwk.msn.net [104.44.41.107]
  6   313 ms   364 ms   293 ms  be-20-0.ibr01.lax31.ntwk.msn.net [104.44.32.15]
  7   329 ms   313 ms   321 ms  be-9-0.ibr03.cys04.ntwk.msn.net [104.44.16.227]
  8   327 ms   315 ms   345 ms  be-3-0.ibr03.dsm05.ntwk.msn.net [104.44.17.165]
  9   341 ms     *      316 ms  be-2-0.ibr02.dsm05.ntwk.msn.net [104.44.17.31]
 10   300 ms   315 ms   331 ms  be-6-0.ibr02.ch2.ntwk.msn.net [104.44.18.216]
 11   300 ms   368 ms   533 ms  be-3-0.ibr02.cle02.ntwk.msn.net [104.44.29.252]
 12   319 ms   310 ms   330 ms  be-6-0.ibr04.bl20.ntwk.msn.net [104.44.30.5]
 13   322 ms   303 ms   313 ms  be-9-0.ibr02.nyc30.ntwk.msn.net [104.44.28.54]
 14   291 ms   341 ms   311 ms  be-7-0.ibr02.lon22.ntwk.msn.net [104.44.18.155]
 15   351 ms   308 ms   317 ms  be-1-0.ibr02.lon24.ntwk.msn.net [104.44.16.56]
 16   295 ms   306 ms   300 ms  be-14-0.ibr02.ams21.ntwk.msn.net [104.44.30.111]
 17   310 ms   296 ms   290 ms  ae126-0.icr04.ams21.ntwk.msn.net [104.44.23.247]
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23   303 ms   310 ms   311 ms  40.108.195.53

Trace complete.

Blog Post

Getting the best connectivity and performance in Office 365

Share