Across every business, there exist a small number of workloads that are too important to fail. These workloads are considered mission critical. When those workloads experience outages or performance degradation, the adverse impact on revenue and profitability can be felt across the entire company.
At the other end of the spectrum, some workloads can go months at a time without being used. Poor performance or outages for those workloads is not desirable, but the impact is isolated and limited.
Understanding the criticality of each workload in the IT portfolio is the first step toward establishing mutual commitments to cloud management.
The following diagram illustrates a common alignment between the criticality scale to follow and the standard commitments made by the business. The first step in any business criticality alignment effort is to create a criticality scale.
The following table presents a sample scale to be used as a reference, or template, for creating your own scale. It's common for businesses to include additional criticality classifications that are specific to their industry, vertical, or specific business processes. Examples of additional classifications include:. Later in the cloud-adoption process, the cloud management team will use this classification to determine the amount of effort required to meet aligned levels of criticality.
To come back to our valuable SMC customer. This customer has an environment of about 25, users, was new to Azure Active Directory and ultimately was in the process of exploring as many new features as possible. Historically they had to deal with various Security incidents in their environment , which resulted in Identity compromise, phishing, malware attacks etc.
They had challenges to Protect, Detect and Respond proactively to these varying levels of compromise. Being part of the Microsoft Solution team, we always go above and beyond to support our customers. The first step is always to quickly resolve the reactive issue, subsequently identify the Root Cause, and finally through our Proactive Delivery Methodology making sure this does not happen again.
Below you will now find the chronological flow of our approach to fix some of the issues over a period. Each topic described will have a separate blog as all these Individual topics require in depth discussion.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in. Products 72 Special Topics 41 Video Hub Most Active Hubs Microsoft Teams. Security, Compliance and Identity. Microsoft Edge Insider. Additional services to extend outcomes. Proactive Services Select from a wide range of short-term support services aligned to your IT lifecycle and existing standards.
Follow Microsoft. Download this information as a datasheet Download datasheet. Ready to experience it for yourself? Contact your local Microsoft Account Representative to get started. Are you looking for support coverage for a single Microsoft products Azure support Microsoft support Dynamics support. Escalation Management. For Critical Business System Down issues, resource assigned after minutes for Azure, or 1-hour for all other products For Critical Business System Degraded issues, resource assigned after 1- hour for all products.
IT Health.
0コメント