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

workflows/operate-and-update/operate-and-update.md

Operate and Update Azure Local

Use this workflow for Azure Local inventory, health, monitoring, lifecycle management, updates, and update troubleshooting.

Intake

Identify:

  • Azure Local version/release and support window.
  • Subscription, resource group, Azure Local instance, and custom location.
  • Connectivity model, including limited connectivity or disconnected operation.
  • Monitoring configuration, Log Analytics workspace, Azure Monitor/Insights status, Defender/Policy onboarding, and alerting requirements.
  • Update target: assessment only, import/discover, schedule, install, troubleshoot, or post-update validation.

Operation flow

  1. Start read-only - Inventory Azure Local, Arc, resource bridge, custom location, and workload resources with resource-types.
  2. Check health - Review Azure resource status, Arc machine connectivity, Azure Local instance status, extension status, and recent activity logs.
  3. Check monitoring - Verify Azure Monitor/Log Analytics or Insights configuration before querying logs.
  4. Assess lifecycle - Compare current release to the Azure Local release information and support window. Fetch current release notes through docs-map.
  5. Plan updates - Use the Azure Local update docs for prerequisites, phases, supported interfaces, expected reboots, maintenance windows, and workload impact.
  6. Apply updates only after confirmation - Installing updates may reboot hosts or affect workloads. Ask for explicit confirmation before scheduling or installing.
  7. Validate after changes - Confirm update state, cluster health, Arc connectivity, resource bridge health, workload health, and monitoring alerts.

Supported update guidance

Azure Local updates are orchestrated as a solution update for the OS, agents/services, and solution extension content. Use documented Azure Local update paths:

| Need | Use | | --- | --- | | Learn update model and cadence | Azure Local update overview | | Understand phases | Update phases docs | | Command-line update | Azure Local PowerShell update docs | | Portal update | Azure Update Manager for Azure Local docs | | Limited connectivity | Import/discover updates offline docs | | Failure investigation | Update troubleshooting docs |

Avoid unsupported update paths

Do not recommend out-of-band updates for Azure Local components. Avoid unsupported interfaces such as manual Cluster-Aware Updating, Windows Admin Center update flows, SConfig, or update panes for individual Arc machines unless Microsoft Learn explicitly documents the scenario for the user's version.

Monitoring and inventory patterns

Use Azure control-plane discovery first:

Resources
| where type =~ 'microsoft.azurestackhci/clusters'
| project name, resourceGroup, location, properties

Then expand to associated Arc resource bridge, custom locations, Arc machines, workload resources, extensions, and activity logs. See resource-types.

Handoff

Related references