Overview
Azure operations covering VMs, App Service, Functions, AKS, Cosmos DB, and Azure AD for identity management.
Capabilities
- Virtual Machine management
- App Service web hosting
- Azure Functions serverless
- AKS Kubernetes clusters
- Cosmos DB multi-model
- Azure AD identity
- ARM/Bicep templates
When to Use
Trigger phrases:
"azure ops"
"Azure operations — Virtual Machines, App Service, Azure Functions, AKS, Cosmos D"
Azure cloud management
Enterprise identity with Azure AD
.NET application hosting
Hybrid cloud scenarios
When NOT to Use
- Task is outside your authorization scope
- You need to implement controls (use implementing-* skills)
- Task is about analysis, not action (use analyzing-* skills)
- You don't have access to target systems
- Task requires compliance expertise (consult professionals)
- Task is about defense, not offense (use defensive skills)
Pseudo Code
The azure-ops workflow follows a standard pipeline pattern.
Core flow:
# azure-ops primary flow
input = prepare(raw_data)
result = process(input, config={azure, cosmos, functions, machines, operations})
validate(result)
deliver(result)
Error handling:
on error:
log(error_details)
retry_with_backoff(max=3)
if still_failing: alert_and_escalate()
Azure CLI Deploy
az webapp create -g MyRG -p MyPlan -n MyApp --runtime "NODE:18-lts"
az functionapp create -g MyRG -p MyPlan -n MyFunc --runtime node
Common Patterns
- Managed identities over secrets
- Azure Policy for compliance
- Resource locks for production
- Reserved instances for savings
How to Use
- Define infrastructure as code (Terraform, CloudFormation, Pulumi)
- Review changes through PR process before applying
- Configure monitoring and alerting for critical paths
- Set up secrets management (Vault, AWS Secrets Manager, etc.)
- Document runbooks for deployment, rollback, and incident response
- Test disaster recovery procedures regularly
Red Flags
- Infrastructure changes without review: Unreviewed changes cause outages — use PRs for infra code
- No rollback strategy: Every deployment needs a tested rollback plan before it runs
- Secrets in configuration files: Secrets in YAML/JSON get committed to version control
- Missing monitoring and alerting: Without monitoring, outages go undetected until users report them
- No documentation for runbooks: Without runbooks, on-call engineers waste time re-discovering procedures
Verification
Process
- Analyze the task requirements
- Apply domain expertise
- Verify output quality
Anti-Rationalization Table
| Rationalization |
Reality |
| "Manual deployments are fine" |
Manual deployments are error-prone and不可 repeatable. Automate. |
| "We do not need monitoring" |
Without monitoring, you are flying blind. Add observability from day one. |
| "Infrastructure as code is overkill" |
IaC enables reproducibility, version control, and disaster recovery. |
1---2name: azure-ops3description: Use when azure operations — Virtual Machines, App Service, Azure Functions,4 AKS, Cosmos DB, Azure AD. Use when working with azure ops.5domain: devops6author: oyi777license: Apache-2.08subdomain: devops9tags:10- azure11- ci-cd12- devops13- infrastructure14- ops15version: 1.0.016category: devops17metadata:18 source: https://skillmd.com/skills/oyi77/azure-ops19---20212223## Overview2425Azure operations covering VMs, App Service, Functions, AKS, Cosmos DB, and Azure AD for identity management.2627## Capabilities2829- Virtual Machine management30- App Service web hosting31- Azure Functions serverless32- AKS Kubernetes clusters33- Cosmos DB multi-model34- Azure AD identity35- ARM/Bicep templates3637## When to Use38**Trigger phrases:**39- "azure ops"40- "Azure operations — Virtual Machines, App Service, Azure Functions, AKS, Cosmos D"414243- Azure cloud management44- Enterprise identity with Azure AD45- .NET application hosting46- Hybrid cloud scenarios4748## When NOT to Use4950- Task is outside your authorization scope51- You need to implement controls (use implementing-* skills)52- Task is about analysis, not action (use analyzing-* skills)53- You don't have access to target systems54- Task requires compliance expertise (consult professionals)55- Task is about defense, not offense (use defensive skills)565758## Pseudo Code5960The azure-ops workflow follows a standard pipeline pattern.6162Core flow:63```64# azure-ops primary flow65input = prepare(raw_data)66result = process(input, config={azure, cosmos, functions, machines, operations})67validate(result)68deliver(result)69```7071Error handling:72```73on error:74 log(error_details)75 retry_with_backoff(max=3)76 if still_failing: alert_and_escalate()77```787980### Azure CLI Deploy81```bash82az webapp create -g MyRG -p MyPlan -n MyApp --runtime "NODE:18-lts"83az functionapp create -g MyRG -p MyPlan -n MyFunc --runtime node84```8586## Common Patterns8788- Managed identities over secrets89- Azure Policy for compliance90- Resource locks for production91- Reserved instances for savings9293## How to Use94951. Define infrastructure as code (Terraform, CloudFormation, Pulumi)962. Review changes through PR process before applying973. Configure monitoring and alerting for critical paths984. Set up secrets management (Vault, AWS Secrets Manager, etc.)995. Document runbooks for deployment, rollback, and incident response1006. Test disaster recovery procedures regularly101102## Red Flags103104- **Infrastructure changes without review**: Unreviewed changes cause outages — use PRs for infra code105- **No rollback strategy**: Every deployment needs a tested rollback plan before it runs106- **Secrets in configuration files**: Secrets in YAML/JSON get committed to version control107- **Missing monitoring and alerting**: Without monitoring, outages go undetected until users report them108- **No documentation for runbooks**: Without runbooks, on-call engineers waste time re-discovering procedures109110## Verification111112- [ ] Skill output matches expected behavior113114## Process1151161. Analyze the task requirements1172. Apply domain expertise1183. Verify output quality119120## Anti-Rationalization Table121122| Rationalization | Reality |123|---|---|124| "Manual deployments are fine" | Manual deployments are error-prone and不可 repeatable. Automate. |125| "We do not need monitoring" | Without monitoring, you are flying blind. Add observability from day one. |126| "Infrastructure as code is overkill" | IaC enables reproducibility, version control, and disaster recovery. |