Merge pull request #293215 from eak13/main

Updates to remove preview for BYOSA

Author: prmerger-automator[bot]

articles/operator-nexus/howto-baremetal-run-data-extract.md

@@ -5,7 +5,7 @@ author: eak13
 ms.author: ekarandjeff
 ms.service: azure-operator-nexus
 ms.topic: how-to
-ms.date: 10/16/2024
+ms.date: 1/17/2025
 ms.custom: template-how-to, devx-track-azurecli
 ---
 
@@ -22,23 +22,7 @@ The command produces an output file containing the results of the data extract.
 - The syntax for these commands is based on the 0.3.0+ version of the `az networkcloud` CLI.
 - Get the Cluster Managed Resource group name (cluster_MRG) that you created for Cluster resource.
 
-## Verify access to the Cluster Manager storage account
-
-> [!NOTE]
-> The Cluster Manager storage account output method will be deprecated in the future once Cluster on-boarding to Trusted Services is complete and the user managed storage option is fully supported.
-
-If using the Cluster Manager storage method, verify you have access to the Cluster Manager's storage account:
-
-1. From Azure portal, navigate to Cluster Manager's Storage account.
-1. In the Storage account details, select **Storage browser** from the navigation menu on the left side.
-1. In the Storage browser details, select on **Blob containers**.
-1. If you encounter a `403 This request is not authorized to perform this operation.` while accessing the storage account, storage account’s firewall settings need to be updated to include the public IP address.
-1. Request access by creating a support ticket via Portal on the Cluster Manager resource. Provide the public IP address that requires access.
-
-## **PREVIEW:** Send command output to a user specified storage account
-
-> [!IMPORTANT]
-> Please note that this method of specifying a user storage account for command output is in preview. **This method should only be used with user storage accounts that do not have firewall enabled.** If your environment requires the storage account firewall be enabled, use the existing Cluster Manager output method.
+## Send command output to a user specified storage account
 
 ### Create and configure storage resources
 
@@ -156,12 +140,25 @@ User-assigned identity example:
     },
 ```
 
+## DEPRECATED METHOD: Verify access to the Cluster Manager storage account
+
+> [!IMPORTANT]
+> The Cluster Manager storage account is targeted for removal in April 2025 at the latest. If you're using this method today for command output, consider converting to using a user provided storage account.
+
+If using the Cluster Manager storage method, verify you have access to the Cluster Manager's storage account:
+
+1. From Azure portal, navigate to Cluster Manager's Storage account.
+1. In the Storage account details, select **Storage browser** from the navigation menu on the left side.
+1. In the Storage browser details, select on **Blob containers**.
+1. If you encounter a `403 This request is not authorized to perform this operation.` while accessing the storage account, storage account’s firewall settings need to be updated to include the public IP address.
+1. Request access by creating a support ticket via Portal on the Cluster Manager resource. Provide the public IP address that requires access.
+
 ## Execute a run-data-extract command
 
 The run data extract command executes one or more predefined scripts to extract data from a bare metal machine.
 
 > [!WARNING]
-> Microsoft does not provide or support any Operator Nexus API calls that expect plaintext username and/or password to be supplied. Please note any values sent will be logged and are considered exposed secrets, which should be rotated and revoked. The Microsoft documented method for securely using secrets is to store them in an Azure Key Vault, if you have specific questions or concerns please submit a request via the Azure Portal.
+> Microsoft doesn't provide or support any Operator Nexus API calls that expect plaintext username and/or password to be supplied. Note any values sent are logged and are considered exposed secrets, which should be rotated and revoked. The Microsoft documented method for securely using secrets is to store them in an Azure Key Vault. If you have specific questions or concerns, submit a request via the Azure portal.
 
 The current list of supported commands are
 
@@ -192,7 +189,6 @@ The current list of supported commands are
 - [Collect Helm Releases](#collect-helm-releases)\
   Command Name: `collect-helm-releases`\
   Arguments: None
-  
 - [Collect `systemctl status` Output](#collect-systemctl-status-output)\
   Command Name: `platform-services-status`\
   Arguments: None
@@ -455,7 +451,7 @@ Vulnerability data is collected with the `cluster-cve-report` command and format
 This example executes the `cluster-cve-report` command without arguments.
 
 > [!NOTE]
-> The target machine must be a control-plane node or the action will not execute.
+> The target machine must be a control-plane node or the action doesn't execute.
 
 ```azurecli
 az networkcloud baremetalmachine run-data-extract --name "bareMetalMachineName" \
@@ -677,7 +673,7 @@ Helm release data is collected with the `collect-helm-releases` command and form
 This example executes the `collect-helm-releases` command without arguments.
 
 > [!NOTE]
-> The target machine must be a control-plane node or the action will not execute.
+> The target machine must be a control-plane node or the action doesn't execute.
 
 ```azurecli
 az networkcloud baremetalmachine run-data-extract --name "bareMetalMachineName" \
@@ -786,7 +782,7 @@ https://cmcr5xp3mbn7st.blob.core.windows.net/bmm-run-command-output/a29dcbdb-552
 ### Collect Systemctl Status Output
 
 Service status is collected with the `platform-services-status` command. The output is in plain text format and
-returns an overview of the status of the services on the host as well as the `systemctl status` for each found service.
+returns an overview of the status of the services on the host and the `systemctl status` for each found service.
 
 This example executes the `platform-services-status` command without arguments.
 
@@ -843,7 +839,7 @@ TriggeredBy: ● atop-rotate.timer
 The command provides a link (if using cluster manager storage) or another command (if using user provided storage) to download the full output. The tar.gz file also contains the zipped extract command file outputs. Download the output file from the storage blob to a local directory by specifying the directory path in the optional argument `--output-directory`.
 
 > [!WARNING]
-> Using the `--output-directory` argument will overwrite any files in the local directory that have the same name as the new files being created.
+> Using the `--output-directory` argument overwrites any files in the local directory that have the same name as the new files being created.
 
 > [!NOTE]
-> Storage Account could be locked resulting in `403 This request is not authorized to perform this operation.` due to networking or firewall restrictions. Refer to the [cluster manager storage](#verify-access-to-the-cluster-manager-storage-account) or the [user managed storage](#create-and-configure-storage-resources) sections for procedures to verify access.
+> Storage Account could be locked resulting in `403 This request is not authorized to perform this operation.` due to networking or firewall restrictions. Refer to the [cluster manager storage](#deprecated-method-verify-access-to-the-cluster-manager-storage-account) or the [user managed storage](#create-and-configure-storage-resources) sections for procedures to verify access.

articles/operator-nexus/howto-baremetal-run-read.md

@@ -1,11 +1,11 @@
 ---
 title: Troubleshoot bare metal machine issues using the `az networkcloud baremetalmachine run-read-command` for Operator Nexus
 description: Step by step guide on using the `az networkcloud baremetalmachine run-read-command` to run diagnostic commands on a BMM.
-author: matternst7258
-ms.author: matthewernst
+author: eak13
+ms.author: ekarandjeff
 ms.service: azure-operator-nexus
 ms.topic: how-to
-ms.date: 10/24/2024
+ms.date: 1/17/2025
 ms.custom: template-how-to
 ---
 
@@ -22,23 +22,7 @@ The command produces an output file containing the results of the run-read comma
 1. Ensure that the target BMM must have its `poweredState` set to `On` and have its `readyState` set to `True`
 1. Get the Managed Resource group name (cluster_MRG) that you created for `Cluster` resource
 
-## Verify access to the Cluster Manager storage account
-
-> [!NOTE]
-> The Cluster Manager storage account output method will be deprecated in the future once Cluster on-boarding to Trusted Services is complete and the user managed storage option is fully supported.
-
-If using the Cluster Manager storage method, verify you have access to the Cluster Manager's storage account:
-
-1. From Azure portal, navigate to Cluster Manager's Storage account.
-1. In the Storage account details, select **Storage browser** from the navigation menu on the left side.
-1. In the Storage browser details, select on **Blob containers**.
-1. If you encounter a `403 This request is not authorized to perform this operation.` while accessing the storage account, storage account’s firewall settings need to be updated to include the public IP address.
-1. Request access by creating a support ticket via Portal on the Cluster Manager resource. Provide the public IP address that requires access.
-
-## **PREVIEW:** Send command output to a user specified storage account
-
-> [!IMPORTANT]
-> Please note that this method of specifying a user storage account for command output is in preview. **This method should only be used with user storage accounts that do not have firewall enabled.** If your environment requires the storage account firewall be enabled, use the existing Cluster Manager output method.
+## Send command output to a user specified storage account
 
 ### Create and configure storage resources
 
@@ -156,6 +140,19 @@ User-assigned identity example:
     },
 ```
 
+## DEPRECATED METHOD: Verify access to the Cluster Manager storage account
+
+> [!IMPORTANT]
+> The Cluster Manager storage account is targeted for removal in April 2025 at the latest. If you're using this method today for command output, consider converting to using a user provided storage account.
+
+If using the Cluster Manager storage method, verify you have access to the Cluster Manager's storage account:
+
+1. From Azure portal, navigate to Cluster Manager's Storage account.
+1. In the Storage account details, select **Storage browser** from the navigation menu on the left side.
+1. In the Storage browser details, select on **Blob containers**.
+1. If you encounter a `403 This request is not authorized to perform this operation.` while accessing the storage account, storage account’s firewall settings need to be updated to include the public IP address.
+1. Request access by creating a support ticket via Portal on the Cluster Manager resource. Provide the public IP address that requires access.
+
 ## Execute a run-read command
 
 The run-read command lets you run a command on the BMM that doesn't change anything. Some commands have more
@@ -174,7 +171,7 @@ An example of run-read commands that require specific arguments is the allowed M
 which requires the `query` argument be provided to enforce read-only.
 
 > [!WARNING]
-> Microsoft does not provide or support any Operator Nexus API calls that expect plaintext username and/or password to be supplied. Please note any values sent will be logged and are considered exposed secrets, which should be rotated and revoked. The Microsoft documented method for securely using secrets is to store them in an Azure Key Vault, if you have specific questions or concerns please submit a request via the Azure Portal.
+> Microsoft doesn't provide or support any Operator Nexus API calls that expect plaintext username and/or password to be supplied. Note any values sent are logged and are considered exposed secrets, which should be rotated and revoked. The Microsoft documented method for securely using secrets is to store them in an Azure Key Vault. If you have specific questions or concerns, submit a request via the Azure portal.
 
 This list shows the commands you can use. Commands in `*italics*` can't have `arguments`; the rest can.
 
@@ -363,7 +360,7 @@ This command runs synchronously. If you wish to skip waiting for the command to
 When an optional argument `--output-directory` is provided, the output result is downloaded and extracted to the local directory.
 
 > [!WARNING]
-> Using the `--output-directory` argument will overwrite any files in the local directory that have the same name as the new files being created.
+> Using the `--output-directory` argument overwrites any files in the local directory that have the same name as the new files being created.
 
 ### This example executes a 'kubectl get pods'
 
@@ -407,7 +404,7 @@ This guide walks you through accessing the output file that is created in the Cl
 
 1. Select the baremetal-run-command-output blob container.
 
-1. Storage Account could be locked resulting in `403 This request is not authorized to perform this operation.` due to networking or firewall restrictions. Refer to the [cluster manager storage](#verify-access-to-the-cluster-manager-storage-account) or the [customer-managed storage](#create-and-configure-storage-resources) sections for procedures to verify access.
+1. Storage Account could be locked resulting in `403 This request is not authorized to perform this operation.` due to networking or firewall restrictions. Refer to the [cluster manager storage](#deprecated-method-verify-access-to-the-cluster-manager-storage-account) or the [customer-managed storage](#create-and-configure-storage-resources) sections for procedures to verify access.
 
 1. Select the output file from the run-read command. The file name can be identified from the `az rest --method get` command. Additionally, the **Last modified** timestamp aligns with when the command was executed.