Recommended paths

Start from the problem, then read the right notes.

These paths group existing articles around common operational questions: diagnose, secure, expose, automate or control a technical system without reading the archive by date.

Cloud 18 notes

Diagnose an Application Gateway 502

When a private backend fails behind Application Gateway, isolate DNS, TLS, routing, WAF/APIM handoff, private ingress and health probe causes before changing the application.

  1. 01
    Azure Application Gateway: diagnose 502 errors without mixing DNS, TLS and backend health

    A diagnostic method for Azure Application Gateway 502 errors that separates DNS resolution, probes, backend settings, TLS, hostnames, certificates and real application behavior.

  2. 02
    Azure Private Endpoint: build a validation matrix before production

    Prepare an Azure Private Endpoint production rollout with a validation matrix that separates DNS, routing, public access closure, TLS, application dependencies and tests from Azure and on premises.

  3. 03
    Azure hybrid DNS: when to use Private Resolver, on-premises forwarders and private zones

    Compare the roles of Azure DNS Private Resolver, on-premises DNS forwarders, Azure private zones and forwarding rulesets to build readable hybrid name resolution.

  4. 04
    Azure Private Endpoint: detect Terraform, DNS, and network drift before incident

    Build an operational drift reading across Terraform, Private Endpoint, private DNS, CI runners, and validation evidence before a private Azure path breaks in production.

  5. 05
    Azure: make private paths verifiable with synthetic probes

    Build useful synthetic probes for DNS, TLS, Application Gateway, WAF and Private Endpoint so private Azure paths fail with evidence before production incidents.

  6. 06
    KQL snippet: track synthetic probes for an Azure private path

    A short query to track synthetic probe failures and separate DNS, TLS, WAF or Application Gateway symptoms on an Azure private path.

  7. 07
    Azure internal APIM: diagnose a private API before changing policies

    Qualify a failure across Application Gateway, WAF, internal APIM and a private backend by separating DNS, routing, policy, identity and logs before any fix.

  8. 08
    KQL snippet: correlate WAF and APIM on an Azure private API

    A short query to see whether a private API request is blocked by Application Gateway WAF, received by APIM or missing from the expected path.

  9. 09
    Azure Container Apps: diagnose private ingress before changing revisions

    Build an operational runbook for Azure Container Apps private ingress failures by separating DNS, ingress mode, revision routing, application logs and rollback evidence.

  10. 10
    KQL snippet: diagnose Container Apps private ingress and revisions

    A short query to correlate Azure Container Apps system and console logs when private ingress, probes or revision traffic fail.

  11. 11
    Azure AKS: diagnose private ingress before changing deployments

    Build an operational runbook for AKS private ingress failures by separating DNS, Application Gateway, ingress controller, Kubernetes service endpoints, pod readiness and rollback evidence.

  12. 12
    KQL snippet: correlate AKS private ingress and application logs

    A short query to read ingress controller and application logs together when a private AKS route returns 502, timeouts or no endpoints.

  13. 13
    Azure Functions: diagnose a private HTTP endpoint before changing code

    Build an operational runbook for private Azure Functions failures by separating DNS, Private Endpoint, access restrictions, private storage, Application Insights logs and rollback evidence.

  14. 14
    KQL snippet: correlate an Azure Functions private HTTP endpoint

    A short query to separate DNS, private access, Functions runtime and application exceptions during a private HTTP incident.

  15. 15
    Azure App Service: diagnose a private endpoint before redeploying

    Build an operational runbook for App Service private access failures by separating DNS, Private Endpoint, access restrictions, Application Gateway, application logs and rollback evidence.

  16. 16
    KQL snippet: correlate private App Service and Application Gateway

    A short query to separate WAF, gateway, private DNS, access restrictions and App Service logs during a private access incident.

  17. 17
    Azure Storage: diagnose a private endpoint without opening the account

    An operational runbook for Azure Storage private access failures by separating DNS, Private Endpoint, firewall, identity, logs and rollback evidence.

  18. 18
    KQL snippet: isolate Azure Storage 403 on a private endpoint

    A short query to separate identity, firewall, public endpoint and wrong subresource when private Azure Storage access is denied.

Start this path
Cloud 7 notes

Diagnose private Azure data and messaging access

When Storage, SQL or Service Bus behind Private Endpoint fails, separate DNS, private endpoint state, firewall or public access, runtime identity, logs and rollback before opening access or changing code.

  1. 01
    Azure Storage: diagnose a private endpoint without opening the account

    An operational runbook for Azure Storage private access failures by separating DNS, Private Endpoint, firewall, identity, logs and rollback evidence.

  2. 02
    KQL snippet: isolate Azure Storage 403 on a private endpoint

    A short query to separate identity, firewall, public endpoint and wrong subresource when private Azure Storage access is denied.

  3. 03
    Azure SQL: diagnose a private endpoint before changing the database

    An operational runbook for Azure SQL private access failures by separating DNS, Private Endpoint, firewall, identity, SQL logs and rollback evidence.

  4. 04
    KQL snippet: isolate Azure SQL private endpoint errors

    A short query to separate firewall, authentication, public endpoint and missing connection evidence during a private Azure SQL incident.

  5. 05
    Azure Service Bus: diagnose a private endpoint before touching queues

    An operational runbook for Azure Service Bus private access incidents by separating DNS, Private Endpoint, identity, firewall, metrics, logs and rollback.

  6. 06
    KQL snippet: isolate Service Bus private endpoint errors

    A short query to separate missing connection evidence, identity denial, expired SAS and processing errors during a private Service Bus incident.

  7. 07
    Azure Private Endpoint: detect Terraform, DNS, and network drift before incident

    Build an operational drift reading across Terraform, Private Endpoint, private DNS, CI runners, and validation evidence before a private Azure path breaks in production.

Start this path
Automation 2 notes

Secure a Terraform Azure backend

Move Terraform state toward identity-based access, controlled network paths, explicit locking and recoverable bootstrap.

  1. 01
    Terraform Azure: secure a private state backend without breaking CI

    Design an Azure Terraform backend based on a private Storage Account with CI identity, controlled network access, locking, separate bootstrap, and a diagnostic runbook when init or plan fails.

  2. 02
    Azure Private Endpoint: detect Terraform, DNS, and network drift before incident

    Build an operational drift reading across Terraform, Private Endpoint, private DNS, CI runners, and validation evidence before a private Azure path breaks in production.

Start this path
Cloud 5 notes

Diagnose Azure outbound egress

When an Azure workload cannot reach dependencies, separate VNet Integration, DNS, route tables, NAT Gateway, firewall evidence and rollback before changing code.

  1. 01
    Azure VNet Integration: diagnose outbound networking before changing the application

    An operational runbook for qualifying Azure App Service or Functions outbound failures by separating VNet Integration, DNS, UDR, NSG, NAT, logs and rollback.

  2. 02
    Azure NAT Gateway: diagnose SNAT exhaustion and outbound IP drift

    An operational runbook for qualifying Azure outbound incidents involving NAT Gateway, SNAT ports, UDR, NSG, firewalls, allowlists and rollback.

  3. 03
    Azure Container Apps: diagnose outbound egress before changing code

    A production runbook for qualifying Azure Container Apps outbound failures by separating DNS, UDR, NSG, NAT Gateway, firewall, identity, logs and rollback before changing the application.

  4. 04
    Azure Firewall DNS proxy: diagnose egress before opening rules

    A production runbook for qualifying an Azure egress failure with Firewall DNS proxy, FQDN resolution, UDRs, application rules, logs, validation and rollback before broadening traffic.

  5. 05
    Azure Network Watcher: validate Flow Logs before opening an NSG rule

    A production runbook for qualifying a blocked Azure flow with Network Watcher, NSG Flow Logs, effective security rules, routes, firewall, KQL evidence, validation and rollback before opening a broad rule.

Start this path
Cloud 8 notes

Operate Azure WAF with evidence

Turn a blocked request into a defensible decision: qualify the false positive, choose an exclusion or custom rule, then validate the scope.

  1. 01
    Azure WAF: read Application Gateway blocks with KQL without chasing every layer

    Build useful KQL queries to identify requests blocked by Azure Web Application Firewall on Application Gateway, with action, ruleId, URI, client IP, hostname and time window.

  2. 02
    WAF and KQL: identify a false positive before creating an exclusion

    A KQL analysis method to qualify an Azure WAF block, distinguish attack, noise and application false positive, then document the decision before any exclusion.

  3. 03
    Azure WAF: add an OWASP/CRS exclusion without weakening all protection

    Move from a qualified WAF block to a targeted OWASP/CRS exclusion in an Azure Application Gateway policy, with scope, variable, rule, validation and rollback.

  4. 04
    Azure WAF: when to use custom rules before managed OWASP rules

    Know when to add an Azure WAF custom rule to block or allow precise traffic before managed OWASP/CRS rules, without hiding useful security signals.

  5. 05
    Azure WAF: frame an emergency custom rule without losing evidence

    Apply a temporary Azure WAF custom rule with priority, KQL evidence, business validation and rollback, without permanently hiding managed-rule signals.

  6. 06
    Azure WAF: move a policy from Detection to Prevention without breaking traffic

    A production runbook for qualifying an Azure WAF policy before switching to Prevention with KQL evidence, change scope, application validation, rollback window and an operable decision.

  7. 07
    Azure WAF: prepare an evidence pack before a policy PR

    A production runbook for documenting an Azure WAF change with KQL evidence, policy diff, application probes, security validation, merge decision and rollback.

  8. 08
    Azure snippet: audit WAF custom rule priorities

    A short command to list custom rules in an Azure WAF policy with priority, action and type before an urgent change.

Start this path
Infrastructure 4 notes

Diagnose an alert storm after deployment

When Azure Monitor fires at scale after a deployment, separate real impact, noisy dimensions, action group behavior and rollback before changing thresholds or silencing notifications.

  1. 01
    Monitoring: turn an alert into an actionable operations runbook

    Build useful alerts by connecting signal, diagnosis, scope, decision and rollback path instead of accumulating noisy notifications.

  2. 02
    Azure Monitor: diagnose an alert storm after deployment

    A production runbook for qualifying an Azure Monitor alert storm after deployment by separating real signal, noise, regression, threshold drift, action group behavior and rollback.

  3. 03
    Azure Monitor and KQL: decide a deployment rollback without silencing alerts

    A production runbook for deciding an Azure rollback after deployment with Azure Monitor, KQL, impact correlation, regression evidence, validation and controlled recovery.

  4. 04
    Azure Managed Grafana: diagnose a dashboard or alert before changing KQL

    A production runbook for qualifying an Azure Managed Grafana dashboard or alert with Azure Monitor datasource, managed identity, Log Analytics permissions, variables, traces, validation and rollback before changing KQL queries.

Start this path
Automation 4 notes

Expose AWX operations safely

Use AWX as an operational interface with explicit inputs, bounded templates, reviewable repository structure and controlled reruns after failure.

  1. 01
    AWX: design job templates that do not become a dangerous remote console

    Turn AWX into a controlled operations tool with bounded job templates, limited variables, separated credentials, explicit inventories and post-action validation.

  2. 02
    Ansible in production: structure an operations repository before exposing it in AWX

    Organize an Ansible repository used by AWX with bounded playbooks, reusable roles, separated inventories, readable variables, versioned collections and operations documentation.

  3. 03
    AWX: rerun a failed job without replaying a partial action

    A production runbook for qualifying a failed AWX job with Ansible events, changed tasks, affected hosts, variables, limited rerun, validation and rollback.

  4. 04
    AWX snippet: capture failed job evidence before rerun

    A short sequence to collect status, variables, affected host and error events before rerunning an AWX job.

Start this path
Infrastructure 5 notes

Operate service and managed identities safely

Before revoking an old secret or changing managed identity permissions, identify consumers, prove the real execution identity, watch authentication errors and keep rollback bounded.

  1. 01
    Service identity and secret rotation: a production runbook, not an isolated task

    Build operable rotation for secrets, certificates, and application identities with dependency inventory, evidence, change windows, monitoring, and rollback.

  2. 02
    KQL snippet: detect authentication errors after secret rotation

    A short query to watch 401, 403, and 500 errors after rotating an application secret or service identity.

  3. 03
    Azure managed identity: diagnose private access before changing permissions

    Build a runbook for Key Vault, Storage or private API access failures with managed identity, RBAC, private DNS, logs and real execution evidence.

  4. 04
    KQL snippet: diagnose Key Vault denial with managed identity

    A short query to separate identity denial, network path and source address when an Azure workload can no longer access Key Vault.

  5. 05
    Azure Workload Identity Federation: diagnose CI authentication before bringing back a secret

    A production runbook for qualifying an Azure OIDC authentication failure in a CI pipeline with federated credentials, claims, roles, logs, validation and rollback.

Start this path
AI 11 notes

Control a private AI agent

Define sources, identities, tool boundaries, logs and human validation before an internal agent acts in a private network.

  1. 01
    Private-network AI agent: which controls to keep around data, actions and logs

    Design a private AI agent with technical guardrails around internal sources, triggered actions, identities, logs, human validation and network boundaries.

  2. 02
    AgentOps: diagnose an AI agent that calls the wrong tool

    A production runbook for qualifying an AI agent that selects the wrong tool, acts without evidence or hides an action behind a plausible answer.

  3. 03
    AgentOps: expose MCP tools without losing control of production actions

    A production runbook for exposing MCP tools to an AI agent while keeping action scope, approvals, identities, logs, evaluation and rollback under control.

  4. 04
    AgentOps: diagnose MCP server drift before a production action

    A production runbook for qualifying MCP server drift with tool manifests, schemas, identity, secrets, network path, traces, evaluations, validation and rollback before reauthorizing an AI agent.

  5. 05
    Microsoft Foundry: evaluate an agent before giving it a production action

    A runbook for validating an AI agent before real action by separating sources, tools, identity, evaluation cases, human approvals, logs and rollback.

  6. 06
    AgentOps: validate an agent tool before it can change production

    A production runbook for qualifying a new AI agent tool with contract review, scoped identity, dry run, traces, approvals, evaluation cases and rollback before enabling real actions.

  7. 07
    AgentOps: validate the Foundry automation handoff before a production action

    A production runbook for qualifying the handoff from a Microsoft Foundry agent to Azure Automation, AWX, Azure DevOps or an MCP tool with contract, identity, traces, dry run, human validation and rollback.

  8. 08
    AgentOps: validate tool output before a production write

    A production runbook for qualifying structured AI agent tool output with schema, sources, diff, idempotence, policy, traces, human validation and rollback before writing to production.

  9. 09
    AgentOps: bound MCP tool timeouts, retries and circuit breakers before production

    A production runbook for defining latency budgets, idempotency, retries, circuit breakers, traces and rollback for an MCP tool called by an AI agent.

  10. 10
    AgentOps: contain an AI agent consumption runaway before shutting down production

    A production runbook for attributing token and tool-call growth, isolating amplification, enforcing an execution budget, and validating or rolling back an AI agent release.

  11. 11
    AgentOps: shadow a prompt or model change before production cutover

    A production runbook for comparing a candidate agent with the active runtime on the same requests without duplicating actions, then deciding promotion, canary or rollback.

Start this path