The CoreView Zone

Picture, if you will, a global transport and distribution organisation, a towering titan of logistics, with a Microsoft 365 tenant to match, both in terms of scale and success. But not even the most well-fortified tower is immune to disaster – and the taller the tower, the more calamitous the consequences when it eventually falls.

How long does it take to rebuild a tower built from over a million bricks? This was the question this organisation sought to answer when they tested how long it would take to rebuild their tenant – and the answer was sobering. In an industry where a single day, even a few hours, can be pivotal in avoiding massive financial and reputational damage, this colossal tenant, with all its unique configurations, would take 28 days to rebuild.

A harrowing tale, but one that brings us neatly to the next pathway we’ll be exploring on our journey into the CoreView Zone: disaster recovery. No one wants to think too hard about the worst-case scenario, but planning out how your organisation can recover if the worst were to happen is a necessity, nonetheless.

Likewise, Microsoft 365 configurations are unlikely to be the first thing that comes to mind when an organisation starts to map out a disaster recovery plan, but they are the bricks and mortar of an organisation’s IT infrastructure – vitally important, and ultimately the part that can be the biggest time sink when it comes to rebuilding.

Let’s return to our transport organisation, and their eyewatering 28-day rebuild time following a hypothetical disaster. In the logistics world, even a single day’s interruption can spell millions in knock-on damage from revenue loss, disruptions in service, and of course the brand damage that can occur as a result – the cost of 28 days of downtime could add up to something crippling, from which it might even be impossible for many organisations to recover.

“Come on,” I hear you cry as you throw up your hands in anguish (I won’t lie – you’re quite melodramatic in my internal narrative), “there must be some small nugget of good news in all of this, mustn’t there?”

To answer that question, let’s take another look at those Microsoft 365 configurations – the bricks and mortar of IT infrastructure, but also the bread and butter of CoreView (side note: that’s an absolute atrocity of a mixed metaphor – don’t try to eat bricks, mortar, or indeed M365 configurations). When the transport organisation in question tested CoreView, they found that their disaster recovery time reduced from 28 days to a mere 21 hours.

It’s a stark – and hopefully telling – contrast. No one likes to think about how long recovery could take, but a matter of hours is infinitely preferable to a matter of weeks. If you’re curious to see how much CoreView could cut down your organisation’s disaster recovery time, make sure to learn more and book a demo below:

CoreView – Kite Distribution

When next we venture into the CoreView Zone, we’ll be taking a look at a topic that has almost certainly caused many a sleepless night for admin teams worldwide: manual onboarding.