Skip to content

Commit 92ba34e

Browse files
add version number when actionState fields were introduced
1 parent c37b903 commit 92ba34e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/operator-nexus/howto-bare-metal-best-practices.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Best practices for Bare Metal Machine operations
33
description: Steps that should be taken before executing any Bare Metal Machine replace, or reimage actions. Highlight essential prerequisites and common pitfalls to avoid.
4-
ms.date: 04/23/2025
4+
ms.date: 05/22/2025
55
ms.topic: how-to
66
ms.service: azure-operator-nexus
77
ms.custom: template-how-to, best-practices
@@ -127,7 +127,7 @@ Percent Complete=[100]
127127

128128
#### Monitor progress using `run-read-command`
129129

130-
You can monitor the progress of long running Bare Metal Machine actions using a `run-read-command`.
130+
In version 2506.2 and above, you can monitor the progress of long running Bare Metal Machine actions using a `run-read-command`.
131131

132132
- Some long running actions such as `Replace` or `Reimage` are composed of multiple steps, for example, `Hardware Validation`, `Deprovisioning`, or `Provisioning`.
133133
- The following `run-read-command` shows how to view the different steps in each action, and the progress or status of each step including any potential errors.

0 commit comments

Comments
 (0)