From a860c55b8247275da6ba645d21a42b54f096eddc Mon Sep 17 00:00:00 2001
From: Chris Black <28607803+cblackuk@users.noreply.github.com>
Date: Fri, 9 Jan 2026 05:00:18 -0600
Subject: [PATCH] Fix WMI cmdlet as otherwise it does not work

---
 azure-local/deploy/deployment-local-identity-with-key-vault.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/azure-local/deploy/deployment-local-identity-with-key-vault.md b/azure-local/deploy/deployment-local-identity-with-key-vault.md
index 50dd7b876f..eb7b4bae10 100644
--- a/azure-local/deploy/deployment-local-identity-with-key-vault.md
+++ b/azure-local/deploy/deployment-local-identity-with-key-vault.md
@@ -140,7 +140,7 @@ After deploying the system, confirm the deployment was without AD (AD-less) and
 1. Confirm the node isn't joined to an AD domain by running the following command. If the output shows `WORKGROUP`, the node isn't domain-joined.
 
     ```powershell
-    Get-WmiObject Win32_ComputerSystem.Domain
+    Get-WmiObject (Win32_ComputerSystem).Domain
     ```
     
     Here's a sample output: