Add support for installing Azurite via winget

[asilverman]

Request:
Please add support for installing Azurite using winget, the Windows Package Manager.

Justification:

• Easier installation: Many developers use Windows and expect to be able to install development tools and emulators using winget, which streamlines onboarding and setup.
• Consistency: Other popular developer tools and emulators are available on winget, making Azurite easier to include in scripts, CI setups, and documentation for new contributors.
• Discoverability: Listing Azurite in winget will make it more visible to the Windows developer community.
• Lower friction for new users: One-line install (e.g., winget install Azure.Azurite) removes friction for new users unfamiliar with npm or other package managers.

Suggested Action:

• Submit Azurite to the Microsoft Community Package Manifest Repository to make it available via winget.
• Document the winget installation method in the Azurite README.

Thank you for considering this enhancement!

[blueww]

Ariel Silverman (@asilverman)

Thanks for contact us!
I will check inside team for your suggestion.

[asilverman]

Hi Wei Wei (@blueww), any update on this?

[blueww]

Ariel Silverman (@asilverman)

Azurite currently support install from npm, VScode extension, and docker.
We don't receive other customer requests on winget.

Besides that, we have very limited resource, and has other high priority requests and security items, so might won't take winget as our priority recently.

[asilverman]

Wei Wei (@blueww) thanks for the response — I appreciate the context.

I do want to clarify that I am a customer as well, and this request is coming from real-world usage. It’s a bit surprising to me that although winget is Microsoft’s package manager, installing Azurite via winget isn’t supported.

From a developer-experience standpoint, winget support would meaningfully reduce friction. It enables clean, repeatable setup scripts (e.g., init.ps1) for dev environments and CI/devcontainers, which is much harder when installation requires npm, VS Code extensions, or Docker—each of which adds dependencies and manual steps.

I completely understand resource constraints and prioritization. That said, from the outside it seems like the effort to distribute via winget is relatively small compared to the DX gains.

What would it take for this to be reconsidered in the future?
For example:
• Would a community-contributed winget manifest be acceptable?
• Is there a specific bar (usage signal, internal dependency, security concern) that would need to be met?

Happy to help move this forward if there’s a path that works for the team.

[IanKemp]

It's important to consider exactly what it means, when an employee from a company that is one of the wealthiest that's ever existed, claim that resources are limited.

[gabbsmo]

I thought it worth mentioning that the Azure Functions Core Tools is available on winget. Being able to install both Azurite and Functions Tools through a first party package manager would be a win for ISVs since we would avoid the conversation about third party package managers on their servers, e.g. npm.