Skip to content
DoctorDODemo data
Signed in as Alex Morgan, alex.morgan@contosoai.example, Admin.

Demo data: ContosoAI (fictitious). Nothing here is a real company, device or person.

Estate · demo data

Overview

46,000 devices reporting across 42 sites.

Delivery efficiency
49%
peers and cache, of all bytesBelow the company goal · goal 60%
Served by peers and cache
328.5 TB
instead of the CDN, of 664.1 TB downloaded (51% still from the CDN)328.5 TB kept off the WAN (LAN peers and cache).
Critical findings
2
8,783 critical issues on individual devices5 warning, 3 info
Underlying issues
9
1 critical. Most widespread: Connected Cache host unreachableAll issues and the devices behind them

Efficiency and policy changes

5 policy changes in 30 days: 1 improved, 0 regressed, 4 no clear change, 0 too recent.

44%46%48%50%52%49%1–2–3▲4–5–12 Sept11 Oct

Improved after a changeNo clear change, too recent to judge, or no change

Compares the 7 days either side of each change, and only calls a movement a change when it exceeds ordinary day-to-day variation. It shows association, not cause: content releases and patch weeks move efficiency too.

Fix these first

All 10 recommendations
Highest severity first. Evidence, the change and the Intune policy for each are under Recommendations.
  1. 1

    critical

  2. 2

    critical

  3. 3

    No foreground delay before falling back to the CDN

    Organisation · All 46,000 devices

    warning

Site efficiency

Lowest first. Bars run from 0 to 100%. Source mix, goal and cohesion for each are on Sites.

0% at 6 sites: Boston, Chicago, Frankfurt, Hamburg, Osaka and Remote workers (VPN) take every byte from the CDN, nothing from peers or a cache, so they have no bar below.

  1. Pune18%
  2. Perth19%
  3. Chennai20%
  4. Fukuoka20%
  5. Atlanta20%
  6. Belfast21%
  7. Melbourne23%
  8. Bengaluru24%
  9. Vancouver24%
  10. Montreal24%
  11. Edinburgh25%
  12. Madrid25%
  13. Hyderabad27%
  14. Denver27%
  15. Seattle28%
  16. Toulouse28%
  17. Sydney30%
  18. Toronto34%
  19. Berlin34%
  20. Austin34%
  21. Manchester36%
  22. Lyon36%
  23. San Francisco68%
  24. London68%
  25. New York68%
  26. Singapore68%
  27. Amsterdam69%
  28. Dublin HQ69%
  29. Paris69%
  30. Tokyo69%
  31. Cork70%
  32. Munich70%
  33. Stockholm80%
  34. Oslo80%
  35. Copenhagen81%
  36. Helsinki81%
The mark is the estate, 49%: peers and cache, of all bytes.

Source mix

Where 664 TB came from, by source and peer type.
LAN peers share a network; Group peers share a Group ID; Internet peers are anywhere else.

Download modes

1,300 devices are in a mode that never peers.
HTTP only (0), Simple (99) and Bypass (100) never peer. Group IDs apply only in Group (2). Sample data: each site’s devices are counted under its mode.

Estate topology

Top sites by
Open full view
All 42 sites reach the Microsoft CDN through the one internet breakout, at Dublin HQ. Each site’s devices and where their bytes came from: line weight follows bytes, and the moving bits show where content flows. The top sites are drawn here; the full view draws all 42 with zoom and pan.
  • Microsoft CDN (HTTP)
  • Connected Cache
  • LAN · Group · Internet peers
  • No bytes
  • Policy
  • Blocked
  • Line weight follows bytes
Estate topology: where each site’s bytes came fromREMOTE WORKERS (VPN)DUBLIN HQLONDONBENGALURU38 MORE SITESMicrosoft CDN336 TBInternet breakoutat Dublin HQ · 320 TB1,300 devices0%9 criticalPeersSimple (99) mode5,600 devices69%38 criticalPeers9.1 TBGroup (2) mode3,000 devices68%19 criticalPeers4.0 TBGroup (2) mode2,700 devices24%1,856 criticalPeers3.9 TBGroup (2) mode33,40048%6,861 criticalPeers67.4 TBGroup (2) modepeering off10 Gbps1 Gbps1 Gbps
Across 42 sites and 46,000 devices, 336 TB came from the Microsoft CDN, 244 TB from Connected Cache and 84.5 TB from peers in the period. The company has one internet breakout, at Dublin HQ: 320 TB of the Microsoft CDN bytes cross the WAN to it, and each site on the WAN reaches the CDN through it. 71 sharing flags are marked on the sites. Open a site, or a source above, to see how its devices share content, down to each subnet and device.
Estate topology: where each site’s bytes came fromREMOTE WORKERS (VPN)DUBLIN HQLONDONBENGALURUSAN FRANCISCOMUNICHPARIS35 MORE SITESMicrosoft CDN336 TBInternet breakoutat Dublin HQ · 320 TB1,300 devices0%9 criticalPeersSimple (99) mode5,600 devices69%38 criticalPeers9.1 TBGroup (2) mode3,000 devices68%19 criticalPeers4.0 TBGroup (2) mode2,700 devices24%1,856 criticalPeers3.9 TBGroup (2) mode2,500 devices68%15 criticalPeers3.4 TBGroup (2) mode2,000 devices70%7 criticalPeers3.7 TBGroup (2) mode1,900 devices69%5 criticalPeers2.9 TBGroup (2) mode27,00043%6,834 criticalPeers57.4 TBGroup (2) modepeering off10 Gbps1 Gbps1 Gbps1 Gbps1 Gbps1 Gbps
Across 42 sites and 46,000 devices, 336 TB came from the Microsoft CDN, 244 TB from Connected Cache and 84.5 TB from peers in the period. The company has one internet breakout, at Dublin HQ: 320 TB of the Microsoft CDN bytes cross the WAN to it, and each site on the WAN reaches the CDN through it. 71 sharing flags are marked on the sites. Open a site, or a source above, to see how its devices share content, down to each subnet and device.
Describe this diagram

Across 42 sites and 46,000 devices, 336 TB came from the Microsoft CDN, 244 TB from Connected Cache and 84.5 TB from peers in the period. The company has one internet breakout, at Dublin HQ: 320 TB of the Microsoft CDN bytes cross the WAN to it, and each site on the WAN reaches the CDN through it. 71 sharing flags are marked on the sites. Open a site, or a source above, to see how its devices share content, down to each subnet and device.

Places

  • Remote workers (VPN) (warning: 1,300 devices download but cannot upload to peers): Devices in Remote workers (VPN), Peers in Remote workers (VPN)
  • Dublin HQ (warning: Peers are offered but not reached on 10.10.128.0/20: client isolation suspected): Devices in Dublin HQ, Peers in Dublin HQ
  • London (warning: Peers are offered but not reached on 10.12.128.0/20: client isolation suspected): Devices in London, Peers in London
  • Bengaluru (critical: Peers are offered but not reached on 10.36.128.0/20: client isolation suspected; Peers are refused on 10.36.2.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation)): Devices in Bengaluru, Peers in Bengaluru
  • San Francisco (warning: Peers are offered but not reached on 10.25.128.0/20: client isolation suspected): Devices in San Francisco, Peers in San Francisco
  • Munich (warning: Peers are offered but not reached on 10.16.128.0/20: client isolation suspected): Devices in Munich, Peers in Munich
  • Paris (warning: Peers are offered but not reached on 10.20.128.0/20: client isolation suspected): Devices in Paris, Peers in Paris
  • 35 more sites (New York, Seattle, Stockholm, Toronto, Hyderabad, Amsterdam, Manchester, Singapore, Tokyo, Austin, Berlin, Cork, Copenhagen, Sydney, Frankfurt, Boston, Oslo, Chicago, Madrid, Helsinki, Lyon, Vancouver, Melbourne, Edinburgh, Osaka, Pune, Montreal, Belfast, Hamburg, Denver, Toulouse, Chennai, Atlanta, Perth, Fukuoka) (critical: Peers are offered but not reached on 10.27.128.0/20: client isolation suspected; Peers are offered but not reached on 10.26.128.0/20: client isolation suspected; Peers are refused on 10.26.2.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are offered but not reached on 10.47.128.0/20: client isolation suspected; Peers are offered but not reached on 10.33.128.0/20: client isolation suspected; Peers are offered but not reached on 10.37.128.0/20: client isolation suspected; Peers are offered but not reached on 10.23.128.0/20: client isolation suspected; Peers are offered but not reached on 10.13.128.0/20: client isolation suspected; Peers are offered but not reached on 10.40.128.0/20: client isolation suspected; Peers are offered but not reached on 10.44.128.0/20: client isolation suspected; Peers are offered but not reached on 10.28.128.0/20: client isolation suspected; Peers are offered but not reached on 10.17.128.0/20: client isolation suspected; Peers are offered but not reached on 10.11.128.0/20: client isolation suspected; Peers are offered but not reached on 10.48.128.0/20: client isolation suspected; Peers are offered but not reached on 10.41.128.0/20: client isolation suspected; Peers are offered but not reached on 10.18.128.0/20: client isolation suspected; Peers are refused on 10.18.1.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are refused on 10.18.2.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are refused on 10.18.3.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are offered but not reached on 10.29.128.0/20: client isolation suspected; Peers are refused on 10.29.1.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are refused on 10.29.2.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are offered but not reached on 10.49.128.0/20: client isolation suspected; Peers are offered but not reached on 10.30.128.0/20: client isolation suspected; Peers are refused on 10.30.1.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are refused on 10.30.2.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are offered but not reached on 10.24.128.0/20: client isolation suspected; Peers are offered but not reached on 10.50.128.0/20: client isolation suspected; Peers are offered but not reached on 10.21.128.0/20: client isolation suspected; Peers are offered but not reached on 10.34.128.0/20: client isolation suspected; Peers are offered but not reached on 10.42.128.0/20: client isolation suspected; Peers are offered but not reached on 10.14.128.0/20: client isolation suspected; Peers are offered but not reached on 10.45.128.0/20: client isolation suspected; Peers are refused on 10.45.1.0/24 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are offered but not reached on 10.38.128.0/20: client isolation suspected; Peers are offered but not reached on 10.35.128.0/20: client isolation suspected; Peers are offered but not reached on 10.15.128.0/20: client isolation suspected; DOMinFileSizeToCache is below Microsoft's table for a peer group of 84; Peers are refused on 10.19.1.0/25 because inbound TCP 7680 is blocked on the devices (not client isolation); Peers are offered but not reached on 10.19.128.0/20: client isolation suspected; DOMinFileSizeToCache is below Microsoft's table for a peer group of 83; DOMinFileSizeToCache is below Microsoft's table for a peer group of 77; Peers are offered but not reached on 10.31.128.0/20: client isolation suspected; DOMinFileSizeToCache is below Microsoft's table for a peer group of 70; DOMinFileSizeToCache is below Microsoft's table for a peer group of 70; Peers are offered but not reached on 10.22.128.0/20: client isolation suspected; One device carries 70% of what its peer group shares; DOMinFileSizeToCache is below Microsoft's table for a peer group of 67; DOMinFileSizeToCache is below Microsoft's table for a peer group of 53; Peers are offered but not reached on 10.39.128.0/20: client isolation suspected; One device carries 79% of what its peer group shares; DOMinFileSizeToCache is below Microsoft's table for a peer group of 46; DOMinFileSizeToCache is below Microsoft's table for a peer group of 59; Peers are offered but not reached on 10.32.128.0/20: client isolation suspected; One device carries 79% of what its peer group shares; DOMinFileSizeToCache is below Microsoft's table for a peer group of 46; DOMinFileSizeToCache is below Microsoft's table for a peer group of 59; Peers are offered but not reached on 10.43.128.0/20: client isolation suspected; DOMinFileSizeToCache is below Microsoft's table for a peer group of 40; DOMinFileSizeToCache is below Microsoft's table for a peer group of 50; Peers are offered but not reached on 10.46.128.0/20: client isolation suspected; DOMinFileSizeToCache is below Microsoft's table for a peer group of 35; DOMinFileSizeToCache is below Microsoft's table for a peer group of 45): Devices in 35 more sites, Peers in 35 more sites

Parts

  • Microsoft CDN (internet source): 336 TB in the period
  • Internet breakout: 320 TB in the period
  • Devices in Remote workers (VPN): 1,300 devices, 0% efficiency, download mode Simple (99), 260 issues, 9 critical
  • Peers in Remote workers (VPN): no peer bytes
  • Devices in Dublin HQ: 5,600 devices, 69% efficiency, download mode Group (2), 431 issues, 38 critical
  • Peers in Dublin HQ: 9.1 TB from peers
  • Devices in London: 3,000 devices, 68% efficiency, download mode Group (2), 246 issues, 19 critical
  • Peers in London: 4.0 TB from peers
  • Devices in Bengaluru: 2,700 devices, 24% efficiency, download mode Group (2), 2,745 issues, 1,856 critical
  • Peers in Bengaluru: 3.9 TB from peers
  • Devices in San Francisco: 2,500 devices, 68% efficiency, download mode Group (2), 218 issues, 15 critical
  • Peers in San Francisco: 3.4 TB from peers
  • Devices in Munich: 2,000 devices, 70% efficiency, download mode Group (2), 148 issues, 7 critical
  • Peers in Munich: 3.7 TB from peers
  • Devices in Paris: 1,900 devices, 69% efficiency, download mode Group (2), 133 issues, 5 critical
  • Peers in Paris: 2.9 TB from peers
  • Devices in 35 more sites: 27,000 devices, 43% efficiency, download mode Group (2), 10,987 issues, 6,834 critical
  • Peers in 35 more sites: 57.4 TB from peers

Connections

  • Microsoft CDN → Devices in Remote workers (VPN): HTTP download, active (16.0 TB)
  • Peers in Remote workers (VPN) → Devices in Remote workers (VPN): LAN peering, idle (no bytes) (Simple (99) never peers)
  • Internet breakout → Devices in Dublin HQ: HTTP download, active (10 Gbps Datacentre, 25.6 TB)
  • Peers in Dublin HQ → Devices in Dublin HQ: Group peering, active (9.1 TB)
  • Internet breakout → Devices in London: HTTP download, active (1 Gbps Metro Ethernet, 13.9 TB)
  • Peers in London → Devices in London: Group peering, active (4.0 TB)
  • Internet breakout → Devices in Bengaluru: HTTP download, active (1 Gbps Metro Ethernet, 28.6 TB)
  • Peers in Bengaluru → Devices in Bengaluru: Group peering, active (3.9 TB)
  • Internet breakout → Devices in San Francisco: HTTP download, active (1 Gbps Metro Ethernet, 11.7 TB)
  • Peers in San Francisco → Devices in San Francisco: Group peering, active (3.4 TB)
  • Internet breakout → Devices in Munich: HTTP download, active (1 Gbps Metro Ethernet, 9.1 TB)
  • Peers in Munich → Devices in Munich: Group peering, active (3.7 TB)
  • Internet breakout → Devices in Paris: HTTP download, active (1 Gbps Metro Ethernet, 8.6 TB)
  • Peers in Paris → Devices in Paris: Group peering, active (2.9 TB)
  • Internet breakout → Devices in 35 more sites: HTTP download, active (222 TB)
  • Peers in 35 more sites → Devices in 35 more sites: Group peering, active (57.4 TB)
  • Microsoft CDN → Internet breakout: HTTP download, active (320 TB)