Windows - Software Lifecycle - Update Microsoft Azure Storage Explorer with Notifications

What the Azure Storage Explorer Updater does

This Automox Worklet™ detects outdated installations of Microsoft Azure Storage Explorer and updates them to the latest release. The Worklet queries the Microsoft GitHub repository API to determine the current version, then compares it against the installed version using the Automox Windows Detection Kit (WDK).

When an update is available, the Worklet sends a customizable notification to the logged-in user asking permission to close Azure Storage Explorer. If the user approves, the application closes gracefully, the existing version is uninstalled, and the latest version downloads directly from GitHub and installs. If the user declines or the notification times out, the Worklet exits without making changes.

The Worklet handles both system-wide and per-user installations. When updating a user-space installation, it standardizes on the system-wide installation for better manageability. This approach simplifies future updates and provides consistent application availability across all user profiles on the endpoint.

Why update Azure Storage Explorer through Automox

Microsoft Azure Storage Explorer is a critical tool for teams managing Azure Blob storage, Data Lake, queues, tables, and Cosmos DB. Outdated versions may lack security patches, performance improvements, or compatibility with newer Azure features. Keeping the application current prevents connectivity issues and security vulnerabilities.

The notification-based approach respects user workflows by giving them control over when the update occurs. Users actively working with Azure Storage can defer the update, while still receiving visibility that an update is pending. This balance between security and productivity reduces help desk tickets from interrupted work.

Automating version checks against the GitHub API means you always target the latest official release without manually tracking Microsoft release announcements or updating Worklet variables for each new version.

How Azure Storage Explorer updates work

1. Evaluation phase: The Worklet queries https://api.github.com/repos/microsoft/AzureStorageExplorer/releases/latest to get the current version. It then uses Get-Win32App to detect installed Azure Storage Explorer versions (both system and user scope). If the installed version is older than the latest release, the endpoint is flagged for remediation. Endpoints without Azure Storage Explorer exit as not applicable.

2. Remediation phase: The Worklet sends a Yes/No notification to the active user with customizable title, message, and timeout (default 60 seconds). If the user clicks Yes, the Worklet stops StorageExplorer processes, uninstalls the current version (using user-context or system-context uninstall as appropriate), downloads the latest installer from GitHub to the Automox cache, and runs a silent installation with /VERYSILENT /ALLUSERS flags.

Azure Storage Explorer update requirements

• Windows workstations or servers with Microsoft Azure Storage Explorer installed

• Internet connectivity to reach api.github.com and download the installer

• TLS 1.2 enabled for secure download connections

• User must be logged in to receive and respond to the notification

• Configurable parameters: notification title, message, and timeout (default 60 seconds)

• .NET Framework dependency may be required depending on Azure Storage Explorer version

Expected state after Azure Storage Explorer update

After successful remediation, Microsoft Azure Storage Explorer runs the latest version from the official Microsoft release. The application installs system-wide regardless of the original installation scope, making it available to all users on the endpoint. Users can immediately launch the updated application and connect to their Azure storage accounts. You can verify this change through the Automox Activity Log or by checking the endpoint configuration directly.

If the user declines the notification or the timeout expires, no changes are made. The Worklet exits cleanly and can be re-run at a more convenient time. If installation fails, error details appear in the Automox activity log with specific exit codes to aid troubleshooting.

How to validate update microsoft azure storage explorer with notifications changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for update microsoft azure storage explorer with notifications.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Invoke-RestMethod, User-Agent, Write-Output.

4. Validate remediation effects from script operations such as Invoke-RestMethod, User-Agent, Where-Object, then rerun evaluation for compliance.