Deploying Azure Local as Disaggregated SAN with Dell Automation Platform and Dell Private Cloud

Automation Automobile Factory Concept with 3D Rendering RobotsBanner Format

For most of its life, Azure Local (and Azure Stack HCI before it) meant one thing: hyperconverged. Compute and storage lived in the same box, and Storage Spaces Direct (S2D) glued it together. That model works, but if you need more capacity you buy more nodes, whether you need the CPU and memory or not.

That has changed. Azure Local now supports disaggregated deployments, where the cluster nodes run compute only and storage comes from an external SAN over Fibre Channel or iSCSI. On the Dell side, Dell Private Cloud can now deploy Azure Local on PowerEdge compute with PowerStore storage, orchestrated by the Dell Automation Platform. I spend most of my days in Azure Local validation on Dell PowerEdge hardware, so in this post I want to walk through how the pieces fit, what you need before you start, and how I validate the results with PowerShell.

Azure Local Updates Are Changing: What 2610 and Patch Tuesday Security Updates Mean for Your Update Runbook

Security Chip

If you’ve been around Azure Local (formerly Azure Stack HCI) for any length of time, you know updates are where a lot of the real-world pain lives. The October 2026 release of Azure Local (2610, solution version 12.2610.1004.50) and the changes landing in November move the update story forward in some meaningful ways, so I wanted to pull them together in one place along with how I’d adjust an update runbook.

Registering Azure Local with Azure Arc using a Service Principal

Registering Azure Local (formerly known as Azure Stack HCI) with Azure has come leaps and bounds from the early days that I remember all too well. The process has now been simplified to a one-liner that will prompt you for Azure authentication (via Device Code) and will then start registering the node with Azure Arc to your desired resource group on your Azure subscription. Although that is great, the one thing I’m constantly asked for is guidance on how to do this via a Service Principal (app registration), or SPN for short, with the required permissions.

There are many reasons why someone would want to do this. Some of the common reasons have to deal with a company’s Azure security policy preventing them from using a device code to authenticate to Azure from an unmanaged host. Another reason may be simply because they are wanting to automate end-to-end a deployment of an Azure Local cluster (or multiple clusters).

If you find yourself in that scenario, the below will aim to provide you with some helpful code blocks that my team leverages to perform end-to-end Azure Local deployments for our validation efforts.

Simplifying and Understanding Dell’s Patch and Update Process for Azure Stack Hub (14G)

Introduction

When it comes to Dell’s Integrated System for Microsoft Azure Stack Hub, I often hear from customers that the Patch and Update process is confusing and difficult. This leads to customers to being up to date with their Microsoft Azure Stack Hub software updates and hotfixes while falling behind on their OEM hardware-vendor-provided updates. To help with this issue, I will attempt to break down, demystify, and provide clarity to the patch and update process for the Dell Integrated System for Microsoft Azure Stack Hub 14G.

To fully understand the Dell Patch and Update process for Azure Stack Hub, we must first identify all of the pieces involved in the process and how they are used. Here are the various packages and tools involved in this process:

  • Customer Toolkit zip file
  • Just Enough Administration (JEA) Registration zip file
  • OEM Extension Package zip file
  • Dell Patch and Update Tool
  • Azure Stack Hub software updates
  • Azure Stack Hub hotfixes

Network ATC – Overview

Introduction

Network ATC is an intent-based approach to network configuration that was introduced with Azure Stack HCI OS (21H2) and is the preferred network configuration method to use when deploying your Azure Stack HCI cluster.

Network ATC assists with the following:

Whether you are wanting to deploy a Non-Converged, Fully Converged, or Switchless network topology for your Azure Stack HCI cluster, Network ATC can be leveraged.

The following sections will help guide you through an Azure Stack HCI network deployment leveraging Network ATC while covering some of the parameters and configuration overrides you may need depending on your environment.