Merge pull request #9049 from craxal/dev/cralvord/cli-requirement

AB#6149: Add mention of command line restrictions

Author: AmandaAZ

support/azure/azure-storage/blobs/alerts/storage-explorer-troubleshooting.md

@@ -6,8 +6,8 @@ author: jinglouMSFT
 ms.author: jinglou
 ms.service: azure-storage
 ms.custom: sap:Alerts, Metrics, Logging and Monitoring, linux-related-content
-ms.date: 12/23/2024
-ms.reviewer: cralvord,richardgao
+ms.date: 06/13/2025
+ms.reviewer: cralvord, richardgao
 ---
 
 # Azure Storage Explorer troubleshooting guide
@@ -478,6 +478,9 @@ If you accidentally attached by using an invalid shared access signature URL and
 
 Storage Explorer comes packaged with all dependencies it needs to run on Windows.
 
+> [!NOTE]
+> Some components need command line access. If it's restricted, Storage Explorer might not work as expected. If you encounter issues, contact your system administrator.
+
 ## [macOS](#tab/macOS)
 
 Storage Explorer comes packaged with all dependencies it needs to run on macOS.
@@ -498,7 +501,7 @@ snap connect storage-explorer:password-manager-service :password-manager-service
 
 You can also download the application as a *.tar.gz* file, but you have to install dependencies manually.
 
-Storage Explorer requires the [.NET 6 runtime](/dotnet/core/install/linux) to be installed on your system. The ASP.NET runtime isn't required.
+Storage Explorer requires the [.NET 8 runtime](/dotnet/core/install/linux) to be installed on your system. The ASP.NET runtime isn't required.
 
 > [!NOTE]
 > Older versions of Storage Explorer might require a different version of .NET or .NET Core. To determine the required version, refer to the release notes or in-app error messages.
@@ -676,7 +679,7 @@ AzCopy logs can be found easily via two different methods:
 For some issues, you need to provide logs of the network calls made by Storage Explorer. On Windows, you can get network logs by using Fiddler.
 
 > [!NOTE]
-> Fiddler traces might contain passwords you entered or sent in your browser during the gathering of the trace. Make sure to read the instructions on how to sanitize a Fiddler trace. Don't upload Fiddler traces to GitHub. You'll be told where you can securely send your Fiddler trace.
+> Fiddler traces might contain passwords you entered or sent in your browser during the gathering of the trace. Make sure to read the instructions on how to sanitize a Fiddler trace. Don't upload Fiddler traces to GitHub. Wait for instructions on how to securely send your Fiddler trace.
 
 #### Part 1: Install and configure Fiddler