The Azure Toolkit for JetBrains Rider is an open-source project that helps .NET developers easily create, develop, configure, test, manage and deploy highly available and scalable web apps to Azure.
The plugin can be downloaded and installed in JetBrains Rider and is available from the JetBrains plugins repository.
- Sign in to an Azure account
- Manage one or multiple subscriptions
- Basic management of container hosts (create/delete, start/stop, view details)
- List container registries
- Basic management of Redis caches (create/delete, start/stop, view details, list keys/values)
- Basic management of storage accounts (create/delete, list/create/delete blob container, list/upload/download/delete blobs)
- Basic management of virtual machines (create/delete, start/stop, view details)
- Basic management of web apps (create/delete, start/stop, view details, edit settings)
- Run configuration to deploy ASP.NET web apps (can also provision SQL database)
- ASP.NET Core web apps (any platform)
- .NET framework web apps (Windows)
Feature requests can be logged in our issue tracker, we also welcome contributions.
History and differences with Microsoft Azure Toolkit for IntelliJ
Microsoft's Azure Toolkit for IntelliJ provides similar functionality to the Azure plugin for JetBrains Rider, however focus on the Java/JVM ecosystem and development flows. JetBrains decided to fork the original plugin, and split base functionality (such as browsing Azure resources) from Java/JVM-specific features (such as deploying a
.war file to the HDInsight service).
The Azure Toolkit for JetBrains Rider is released with several notable differences:
- No telemetry or usage data is collected and sent to Microsoft
- Icons have been replaced by custom icons, as the original icons are not open-source
- Java/JVM-specific functionality was removed
- .NET-specific functionality, such as deploying an ASP.NET web application, has been added
JetBrains opened a pull request to Microsoft's Azure Toolkit for IntelliJ as well, which would contribute this effort back to the original plugin, and open up the original plugin to various other ecosystems.
Please see the contribution instructions if you wish to build the plugin from source.