You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/azure/azure-storage/blobs/alerts/storage-explorer-troubleshooting.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,8 @@ author: jinglouMSFT
6
6
ms.author: jinglou
7
7
ms.service: azure-storage
8
8
ms.custom: sap:Alerts, Metrics, Logging and Monitoring, linux-related-content
9
-
ms.date: 12/23/2024
10
-
ms.reviewer: cralvord,richardgao
9
+
ms.date: 06/13/2025
10
+
ms.reviewer: cralvord,richardgao
11
11
---
12
12
13
13
# Azure Storage Explorer troubleshooting guide
@@ -479,7 +479,7 @@ If you accidentally attached by using an invalid shared access signature URL and
479
479
Storage Explorer comes packaged with all dependencies it needs to run on Windows.
480
480
481
481
> [!NOTE]
482
-
> Some components require access to the command line. If access to the command line is restricted, Storage Explorer might not work as expected. If you encounter issues, contact your system administrator.
482
+
> 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.
483
483
484
484
## [macOS](#tab/macOS)
485
485
@@ -679,7 +679,7 @@ AzCopy logs can be found easily via two different methods:
679
679
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.
680
680
681
681
> [!NOTE]
682
-
> 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 you can securely send your Fiddler trace.
682
+
> 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.
0 commit comments