Operational excellence pillar in Azure - Step-by-Step Execution

Process Flow - Operational excellence pillar

Define business goals

↓

Design processes & policies

↓

Implement monitoring & automation

↓

Review & improve continuously

↓

Achieve operational excellence

This flow shows how operational excellence starts with goals, then designs processes, implements monitoring and automation, and continuously improves.

Execution Sample

Azure

1. Define goals
2. Create Azure Monitor alerts
3. Automate with Azure Logic Apps
4. Review logs and metrics
5. Adjust processes

This sequence shows steps to achieve operational excellence using Azure services.

Process Table

Step	Action	Azure Service	Result
1	Define business goals	None	Clear objectives for operations
2	Set up monitoring alerts	Azure Monitor	Alerts notify on issues
3	Automate responses	Azure Logic Apps	Automatic fixes or notifications
4	Review logs and metrics	Azure Monitor Logs	Insights on system health
5	Adjust processes	None	Improved operational procedures
6	Repeat review cycle	None	Continuous improvement

💡 Process repeats continuously to maintain and improve operational excellence

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
Business Goals	Undefined	Defined	Defined	Defined	Defined	Defined
Monitoring Alerts	None	Configured	Configured	Configured	Configured	Configured
Automation	None	None	Implemented	Implemented	Implemented	Implemented
Logs & Metrics	None	None	None	Collected	Collected	Collected
Processes	Undefined	Undefined	Undefined	Undefined	Adjusted	Adjusted

Key Moments - 3 Insights

Why do we need to define business goals first before setting up monitoring?

Defining goals guides what to monitor and automate, as shown in execution_table step 1 and 2 where goals are set before alerts.

How does automation help in operational excellence?

Automation (step 3) reduces manual work and speeds up responses, improving reliability and efficiency.

Why is continuous review important?

Continuous review (step 6) ensures processes improve over time, preventing stagnation and adapting to changes.

Visual Quiz - 3 Questions

Look at the execution_table, what Azure service is used to automate responses?

A Azure Functions

B Azure Monitor Logs

C Azure Logic Apps

D Azure DevOps

💡 Hint

Check step 3 in execution_table where automation is implemented

At which step do we start collecting logs and metrics?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look at execution_table step 4 for logs and metrics collection

If business goals were not defined, what would likely happen to monitoring alerts?

A Alerts might be misconfigured or irrelevant

B Automation would still work perfectly

C Alerts would be well targeted

D Processes would adjust automatically

💡 Hint

Refer to key_moments about importance of defining goals before monitoring

Concept Snapshot

Operational Excellence Pillar in Azure:
- Start by defining clear business goals
- Use Azure Monitor to set alerts and collect logs
- Automate responses with Azure Logic Apps
- Continuously review and improve processes
- Repeat cycle for ongoing operational excellence

Full Transcript

Operational excellence in Azure means running your cloud systems smoothly and improving them over time. First, you set clear business goals to know what success looks like. Then, you use Azure Monitor to watch your systems and get alerts if something goes wrong. Next, you automate fixes or notifications with Azure Logic Apps to save time and reduce errors. You regularly check logs and metrics to understand system health. Finally, you adjust your processes based on what you learn and keep repeating this cycle to get better and better.

Practice

1. What is the main goal of the Operational excellence pillar in Azure cloud?

easy

A. To run cloud systems smoothly and improve them continuously

B. To reduce cloud costs by shutting down services

C. To secure cloud data with encryption only

D. To build new cloud applications from scratch

Solution

1. Step 1: Understand the definition of operational excellence

   Operational excellence focuses on running cloud systems smoothly and improving them over time.

2. Step 2: Compare options with this definition

   Only To run cloud systems smoothly and improve them continuously matches this goal. Other options focus on cost, security, or development, which are different pillars.

3. Final Answer:

   To run cloud systems smoothly and improve them continuously -> Option A

4. Quick Check:

   Operational excellence = smooth running and improvement [OK]

Hint: Operational excellence means smooth running and improvement [OK]

Common Mistakes:

• Confusing operational excellence with security or cost management
• Thinking it only means fixing problems, not improving
• Assuming it is about building new apps

2. Which Azure service is primarily used for monitoring and alerting to support operational excellence?

easy

A. Azure DevOps

B. Azure Monitor

C. Azure Blob Storage

D. Azure Functions

Solution

1. Step 1: Identify the service for monitoring and alerting

   Azure Monitor is designed to collect, analyze, and act on telemetry data from cloud resources.

2. Step 2: Eliminate other options

   Azure DevOps is for development pipelines, Blob Storage is for data storage, and Functions is for serverless compute, so they don't focus on monitoring.

3. Final Answer:

   Azure Monitor -> Option B

4. Quick Check:

   Monitoring and alerting = Azure Monitor [OK]

Hint: Monitoring and alerting in Azure? Think Azure Monitor [OK]

Common Mistakes:

• Choosing Azure DevOps for monitoring
• Confusing storage services with monitoring
• Selecting compute services instead of monitoring tools

3. Consider this Azure CLI command to create an alert rule:

az monitor metrics alert create --name HighCPUAlert --resource-group MyGroup --scopes /subscriptions/123/resourceGroups/MyGroup/providers/Microsoft.Compute/virtualMachines/MyVM --condition "avg Percentage CPU > 80" --description "Alert when CPU is high"

What will happen when the average CPU usage goes above 80%?

medium

A. The CPU usage will be throttled to 80%

B. The virtual machine will automatically shut down

C. An alert named HighCPUAlert will trigger notifying the user

D. Nothing happens because the command syntax is incorrect

Solution

1. Step 1: Understand the alert creation command

   The command creates a metric alert named HighCPUAlert that triggers when average CPU usage exceeds 80% on the specified VM.

2. Step 2: Analyze the effect of the alert

   Alerts notify users or systems but do not automatically shut down or throttle resources. The command syntax is correct.

3. Final Answer:

   An alert named HighCPUAlert will trigger notifying the user -> Option C

4. Quick Check:

   Metric alert triggers notification, not shutdown [OK]

Hint: Alerts notify; they don't auto-shutdown or throttle [OK]

Common Mistakes:

• Thinking alerts auto-shutdown resources
• Assuming alerts change resource behavior automatically
• Believing the command has syntax errors

4. You wrote this Azure Resource Manager (ARM) template snippet to enable diagnostics:

{
  "type": "Microsoft.Insights/diagnosticSettings",
  "name": "myDiagnostics",
  "properties": {
    "logs": [
      { "category": "AuditLogs", "enabled": true }
    ],
    "metrics": [
      { "category": "AllMetrics", "enabled": true }
    ]
  }
}

But diagnostics are not enabled after deployment. What is the likely error?

medium

A. The type should be Microsoft.Compute/diagnosticSettings

B. The name property must be omitted

C. The enabled fields should be false to activate diagnostics

D. Missing the scope property to specify the resource to monitor

Solution

1. Step 1: Check required properties for diagnosticSettings

   The scope property is required to specify which resource the diagnostics apply to.

2. Step 2: Validate other properties

   Name is required, enabled should be true to activate, and type is correctly set to Microsoft.Insights/diagnosticSettings.

3. Final Answer:

   Missing the scope property to specify the resource to monitor -> Option D

4. Quick Check:

   Diagnostics need scope property to work [OK]

Hint: Diagnostics require scope property to target resource [OK]

Common Mistakes:

• Forgetting to add scope property
• Setting enabled to false by mistake
• Changing the resource type incorrectly

5. You want to improve operational excellence by automating recovery when a web app becomes unhealthy. Which Azure feature combination best supports this goal?

hard

A. Azure Monitor alerts + Azure Logic Apps to restart the web app automatically

B. Azure Blob Storage + Azure Functions to store logs

C. Azure DevOps pipelines + Azure Key Vault for deployment security

D. Azure Virtual Machines + Azure Backup for manual recovery

Solution

1. Step 1: Identify automation for recovery

   Azure Monitor alerts detect unhealthy states, and Azure Logic Apps can automate actions like restarting the web app.

2. Step 2: Evaluate other options

   Blob Storage and Functions store logs but don't automate recovery; DevOps and Key Vault focus on deployment security; VMs and Backup support manual recovery, not automated.

3. Final Answer:

   Azure Monitor alerts + Azure Logic Apps to restart the web app automatically -> Option A

4. Quick Check:

   Alerts + automation = automated recovery [OK]

Hint: Combine alerts with automation for recovery [OK]

Common Mistakes:

• Choosing storage or deployment tools for recovery automation
• Confusing manual backup with automated recovery
• Ignoring the need for alert-triggered automation