diff --git a/windows/deployment/do/mcc-isp-overview.md b/windows/deployment/do/mcc-isp-overview.md index 60b248f3ae..6335796712 100644 --- a/windows/deployment/do/mcc-isp-overview.md +++ b/windows/deployment/do/mcc-isp-overview.md @@ -71,3 +71,15 @@ The following steps describe how MCC is provisioned and used: 1. Subsequent requests from end-user devices for content will be served from cache. 1. If the MCC node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers. +## __Are you already peering with 8075?__ + +MCC complements peering by offloading static content that is served off of multiple CDNs such as Akamai, Lumen, Edgecast. Static content such as OS updates, Apps, Software installs etc. cannot be served via 8075. So, even if you are peering with Microsoft, you can benefit from installing MCC. + +## ![mcc-isp-peeringvsmcc](media/mcc-isp-overview/mcc-isp-peeringvsmcc.png) + +__Hardware recommendation__ + +Below are the hardware recommendations based on traffic ranges. + +![mcc-isp-hardwarerec](media/mcc-isp-overview/mcc-isp-hardwarerec1.png) + diff --git a/windows/deployment/do/media/mcc-isp-overview/mcc-isp-hardwarerec.png b/windows/deployment/do/media/mcc-isp-overview/mcc-isp-hardwarerec.png new file mode 100644 index 0000000000..73e1d5cfb0 Binary files /dev/null and b/windows/deployment/do/media/mcc-isp-overview/mcc-isp-hardwarerec.png differ diff --git a/windows/deployment/do/media/mcc-isp-overview/mcc-isp-hardwarerec1.png b/windows/deployment/do/media/mcc-isp-overview/mcc-isp-hardwarerec1.png new file mode 100644 index 0000000000..b3977259dc Binary files /dev/null and b/windows/deployment/do/media/mcc-isp-overview/mcc-isp-hardwarerec1.png differ diff --git a/windows/deployment/do/media/mcc-isp-overview/mcc-isp-peeringvsmcc.png b/windows/deployment/do/media/mcc-isp-overview/mcc-isp-peeringvsmcc.png new file mode 100644 index 0000000000..de0852f52e Binary files /dev/null and b/windows/deployment/do/media/mcc-isp-overview/mcc-isp-peeringvsmcc.png differ