Review Microsoft troubleshooting activity

When Microsoft performs supported command-based troubleshooting actions on your Azure Operator Nexus instance, the commands and their output go to your configured storage account. You can review these records alongside the corresponding execution events in Azure Activity Log.

What's recorded

Troubleshooting records contain the commands that you submitted, their output, and execution details such as the target resource, timestamps, and outcome. These records provide visibility into supported troubleshooting actions.

Important

Troubleshooting records can contain sensitive operational information. Restrict access to the storage container and manage retention according to your organization's policies.

Find the records in your storage account

Records are saved to the default container configured in the Cluster's commandOutputSettings.containerUrl, using its associated managed identity. No additional storage account or managed identity is required for this capability. For configuration details, see Cluster support for managed identities and user-provided resources.

To access the output of a command, users need the appropriate access to the storage blob. They need to have the necessary Azure role assignments and ensure that any networking restrictions are properly configured.

A user must have the following role assignments on the blob container or its storage account:

• A data access role, such as Storage Blob Data Reader or Storage Blob Data Contributor
• The Azure Resource Manager Reader role (at a minimum)

To learn how to assign roles to storage accounts, see Assign an Azure role for access to blob data.

If the storage account allows public endpoint access via a firewall, you must configure the firewall with a networking rule to allow that user's IP address. If it allows only private endpoint access, a user must be part of a network that has access to the private endpoint.

Learn more about how to allow access through the storage account firewall by using networking rules or private endpoints.

1. In the Azure portal, open the storage account configured for your Cluster's command output.

2. Select Storage browser, then Blob containers.

3. Open the container specified in commandOutputSettings.containerUrl.

4. Find the troubleshooting record by its filename:

   cluster-execute-<support-ticket-number>-YYYYMMDDTHHMMSSZ.json
   

   The filename contains the support ticket number and a UTC timestamp, with a literal T between the date and time and a trailing Z. For example: cluster-execute-123-20261013T142345Z.json.

5. Select the record and download it to review its JSON contents.

Review the troubleshooting activity

Review the commands, their output, and the execution outcome in the downloaded record. Use its correlationId to associate it with the corresponding event in your Cluster's Azure Activity Log.

A record with a Started outcome might not yet contain the final results. Don't interpret it as proof that the commands didn't run. If an expected record or final result is missing, contact Microsoft support to investigate.