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.

Design · demo data

Network design

Describe your sites, subnets and links, or start from the network as devices report it today, and DoctorDO designs Delivery Optimization for them: the download mode, the peer groups and Group IDs, the Intune profiles and how to target them, and what it could save. Everything stays in this browser.

Step 1 of 5

Organisation

Where to start

Your sites as they are today: their devices and subnets, the download mode and the Connected Cache servers devices are configured with. Then plan on top of it: add sites, add or move caches, and see what changes. In this demo that is ContosoAI, a fictitious company.

One empty site, to describe a network from the beginning, such as one no collector reports from yet.

How devices are managed and named

These decide how devices can be told which peer group they are in.

Estimate assumptions

The savings estimate rests on these. They are DoctorDO’s round figures, not measurements; change them to match what you know.

Quality and feature updates, apps, Microsoft 365 Apps, Defender.

Share of a peer group online while new content arrives.

Of the bytes still bound for the CDN at a site with a cache.

A quality update with the month’s app updates, for Connected Cache placement. About 4 models a feature update.

Optional: the cost of a gigabyte over the WAN or internet, for a money figure.

Your network

Redrawn as you edit. Analyse to add the peering DoctorDO recommends.

Add a site in step 2 and it appears here.