AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-local

Plan, deploy, operate, and troubleshoot Azure Local (formerly Azure Stack HCI): sizing and prerequisites, Arc registration, lifecycle updates, workloads (Azure Local VMs, AKS on Azure Local, images, disks, logical networks), SDN and network security, and failure triage — starting read-only and confirming before risky changes. WHEN: Azure Local, Azure Stack HCI, Arc resource bridge, custom location, Azure Local VM, Arc VM, AKS on Azure Local, AKS hybrid, SDN, Lifecycle Manager, Azure Local update, disconnected site.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-local at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 10

references/safety-rules.md

Azure Local Safety Rules

Azure Local changes can affect physical hosts, storage networks, Azure Arc connectivity, and local workloads. Default to assessment and reversible actions.

Always ask before

  • Installing, scheduling, importing, or retrying updates that can reboot hosts or affect workloads.
  • Upgrading Azure Local or changing feature releases.
  • Deleting, recreating, or repairing Azure Arc resource bridge.
  • Deleting custom locations.
  • Decommissioning, reimaging, or unregistering Azure Local machines.
  • Changing physical network settings, VLANs, IP pools, DNS, gateways, proxy, Arc gateway, private endpoints, SDN infrastructure, NSGs, load balancers, gateways, or firewall policy.
  • Creating, deleting, resizing, stopping, restarting, or migrating Azure Local VMs.
  • Deleting disks, NICs, VM images, logical networks, storage paths, AKS clusters, SQL deployments, or backup/disaster-recovery resources.
  • Disabling security baseline controls, Defender, Policy, monitoring, or auditing.

Critical components

| Component | Rule | | --- | --- | | Azure Arc resource bridge | Do not delete unless following confirmed reimage/decommission guidance after dependent workload resources are removed. | | Custom location | Do not delete until dependent workloads are removed and resource bridge decommission guidance allows it. | | Infrastructure logical network | Treat as required infrastructure for Azure Local VM management. | | VM management extension | Check health before VM remediation; do not remove as a generic fix. | | SDN infrastructure | Treat certificate, controller, load balancer, and gateway changes as high risk. |

Safe default sequence

  1. Read-only inventory.
  2. Health and activity log review.
  3. Documentation lookup for the user's version.
  4. Impact analysis and rollback plan.
  5. User confirmation.
  6. Scoped change.
  7. Post-change validation.

Response requirements

When recommending a risky change, include:

  • The specific resource(s) affected.
  • Why the change is needed.
  • Expected workload/control-plane impact.
  • Validation steps.
  • Rollback or recovery notes when available.