Azure Toolkit for Rider v4.0 preview - Try it out and give your feedback!

[maartenba]

👋 Hey folks!

We have just published the Azure Toolkit for Rider v4.0 preview, compatible with Rider 2024.1. The v4.0 version can be considered a rewrite of the plugin, which is why we are releasing it as a preview to gather your feedback.

Some background…

When we first released the Azure Toolkit for Rider, it was based on the 3.x version of Microsoft’s Azure Toolkit for IntelliJ. Microsoft’s toolkit was focused on the needs of folks in the Java ecosystem, working with Microsoft Azure, and we created a fork with .NET-specific functionality.

For Rider, we added Cloud Shell support, Azurite, Azure Functions, and support for working with storage accounts and SQL Databases. Over the years, both plugins have diverged quite a bit, and when Microsoft made changes to the authentication libraries used to work with the Azure APIs, our fork for Rider stopped supporting some of the newer functionality such as logging in with az cli, to name one (but there are more).

We have tried a number of times to rebase and merge our fork with the upstream plugin, without success. This rebase became even more difficult after a number of big architectural changes in the Azure Toolkit for IntelliJ, focusing on modularization. However, we found that replaying some of our Rider customizations on this new architecture would be easier than our attempts to rebase – so we did!

Welcome, Azure Toolkit for Rider v4.0 preview

The Azure Toolkit for Rider v4.0 preview is now available from the JetBrains Marketplace.

What’s currently supported:

• Sign in using the Azure CLI tools (az cli), device login, …
• Azure Explorer with the ability to favorite certain services and resources, browse and manage Azure Functions, Azure Web Apps, and Resource Groups
• Development support for:
  • Azure Functions (running, debugging, project templates, item templates, deployment, …)
  • Azure Web Apps (deployment)

For the final v4.0 release, we also want to add Azure Cloud Shell support, and bring Azurite support over from the current version of the plugin. These are not yet in the current preview.

Installing Azure Toolkit for Rider v4.0 preview

The Azure Toolkit for Rider v4.0 preview can be installed by adding a preview plugin repository URL to your Rider 2023.3.x configuration.

• Open settings/preferences and navigate to Plugins
• Click the cogwheel, and Manage Plugin Repositories…
• Add https://plugins.jetbrains.com/plugins/preview/list and click OK
  
• The Installed tab should now list an update to the v4.0 preview of the Azure Toolkit for Rider.
  

Note that we do not yet support the Rider 2024.1 EAPs.

(If you want to revert to the current, stable version of the plugin, remove the custom plugin repository, uninstall the preview version, and re-install the stable version from the Marketplace tab.)

We’re looking for feedback!

We are looking for folks to try out the plugin and give us some feedback!

• Feedback on the v4.0 preview - does the existing functionality work as expected?
• What features would you like to see prioritized afterwards? (e.g. Container Registry / Container Service, Cosmos DB, SQL Database, MySQL, PostgreSQL, Event Hubs, Key Vault, Redis, Service Bus, Storage, ...)

Many thanks!

P.S.: New releases in the v4.0 branch will be announced automatically, similar to #775

[arleth]

Just tested out the connection part - works like a charm with the cli option

[Saphirim]

Which versions of Azure CLI and Rider itself did you use? See my post below, I didn't even get a "Azure Service Authentication" Option with the new plugin :(

[rafaelldi]

Azure Service Authentication isn't implemented yet.

[JensSchadron]

I've been toying around with the v4 (4.0.0-preview.1) of the plugin for the past few days, and the only thing that I noticed so far is that the "Show Properties" option from the context menu (when right clicking an Azure Function app) doesn't seem to do anything despite not being disabled. (not sure whether it isn't implemented altogether and should've been disabled, or whether it's actually broken)

As for features I'd like to see prioritized:

• CosmosDb, Key Vault and Redis (in no particular order)
• And in a lesser degree Service bus and storage :)

Regardless of all this, I'm really happy to see major development going on with this plugin again 😄

Also given that the plugin isn't available on EAP just yet, I feel like I'm currently in a funny situation where I'm running the stable plugin on Rider EAP and the EAP version on stable Rider 😅

[rafaelldi]

Thank you very much for the response! Show Properties action is planned #767

[Saphirim]

Since we were also affected by the Azure CLI login problem, I wanted to give the preview build of Azure Tools a chance.
Unfortunately, with the preview version there is no Authentication Service entry in the plugin settings.

Only "Functions" is displayed as Menu entry when navigating to Settings -> Tools -> Azure

At the moment the preview is not usable for us under Rider 2023.3.

Edit:
Using the following versions:
Rider: 2023.3.3 - Build 233.14015.60
Azure Tools Plugin: 4.0.0-preview.1
Azure CLI: azure-cli 2.56.0
core 2.56.0
telemetry 1.1.0
Dependencies:
msal 1.24.0b2
azure-mgmt-resource 23.1.0b2

[sander1095]

Installing the az cli on mac (with zsh and homebrew) did not work; the az cli login did not appear and using DefaultAzureCredential did not work.

I installed Azure Powershell and added this to my path in ~/.bash_profile: "/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/opt/homebrew/bin/az"

Then using DefaultAzureCredential worked and I saw the azure CLI option in the azure sign in popup in rider.

So, I got my things to work locally. However, this process took several hours of debugging.

Improvements could be made by letting the azure plugin in rider prompt users to install azure cli/powershell and to ensure the path is setup correctly.

The experience should be as easy as using visual studio with azure services

[DanWillman]

@sander1095 is this still working for you or have you pivoted to a different approach? I think we're having the exact same issue, I can't get the cli option or DefaultAzureCredential to work locally on my mac either, even with this setup. Hoping you might have pivoted to something you could share?

[sander1095]

Things work for me by installing Azure Powershell and messing around with the path, like I said in my comments. You might want to try installing the jetbrains azure sdk preview and see if that helps you out?

[DanWillman]

Thanks, I did grab the preview and installed powershell, so likely my problem is in my PATH. Good to know it's working for you still at least

[DanWillman]

Foolish me didn't log in to azure powershell, once I did that DefaultAzureCredential is working for me again. Thanks a ton @sander1095 for posting this, and @maartenba for the preview version!

[ThijmenDam]

@rafaelldi thanks a lot. CLI login is required by the company I work for, meaning I cannot use Rider without this 4.0 Azure preview. Awesome work.

[ThijmenDam]

I have tested the plugin on the project I'm currently working on (a couple of Azure Functions, nothing fancy). Unfortunately, I receive the following message when I try to build and run the project:

unable to find valid certification path to requested target

Building and running the same project in Visual Studio 2022 Enterprise works. Did I perhaps miss a configuration step?

EDIT: I think I indeed missed a configuration step. When I open the Azure settings in JetBrains, there are some input fields related to an SSL certificate. Those are empty in my project. Not sure yet what those have to be, but once I figure it out I'll update this comment.

[rafaelldi]

I think it may be connected to this documentation. This error doesn't come from the plugin itself.

[ThijmenDam]

@rafaelldi I understand what you're saying, and after reading through the documentation you mentioned that's what I thought as well. However... after carefully performing all steps mentioned in the documentation, the error persists, even after confirming my self-signed SSL certificate works. Thing is, if I downgrade Azure Tools to V3 again, I am able to run my Azure function locally again, albeit partially because I cannot sign-in using V3 and my Azure Function tries to connect to a Key Vault.

[rafaelldi]

Thank you for the response, I'll check it out.

[ThijmenDam]

Let me know if I can be of help by providing any information. Thank you!

[rafaelldi]

Thank you. I've created a separate issue for this #788. Could you please describe your scenario in more detail there? For example, are you using Azurite in a Docker container or installing it via npm. Or anything else that might be related to the problem. I need that to properly reproduce the issue.

[ahpluim]

I wanted to confirm that this preview version resolved my login issue in Windows while dealing with multiple tenants. (In macOS, I didn't encounter this issue with the same account and was able to login with v3.5.)

I encountered an error message: "Your sign-in was successful but your admin requires the device requesting access to be managed by to access this resource." Don't repeat my mistake and waste time troubleshooting device management and profiles. Let's skip to the actual issue:

Initially, I attempted to resolve it using the CLI option. After finally getting 'az login' to run successfully, the CLI option remained disabled in the current version of the toolkit. I resolved that with the update to this preview version of the toolkit.

For those trying to get 'az login' working:

• After installation and verifying the path to the CLI, it is located either at "C:\Program Files\Microsoft SDKs\Azure\CLI2\wbin" or "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\bin".
• !! Make sure to restart your terminal (or PowerShell) !!
• Run 'az login' in your terminal.
• After successfully logging in, you'll find the CLI option becomes available in the preview version of this toolkit.

I hope this helps others facing similar issues!

[utillity]

Thanks for providing this update! I would love the following to be supported

• CosmosDB support
• CosmosDB emulator support
• CosmosDB Graph Explorer

[peterblazejewicz]

Great, it fixed 'az login' problem on Mac OS for me with multiple tenants (default one not being picked, etc). Thanks!

[moremanu]

Hello, I've installed the plugin and managed to authenticate fine but still seeing this warning message?

This is preventing me from running code locally with DefaultAzureCredential. I do have Azure CLI installed and am using MacOS.

Has anyone had the same issue and found a workaround?

Thanks

[moremanu]

Hello, thank you for your reply.

I can't see that option, how do you get that?

[rafaelldi]

These are plugin settings, they should be present out of the box. What version of the plugin do you have?

[moremanu]

I'm on 3.50.0.1773-2024.1 and all I can see is

[rafaelldi]

This thread is about the v4.0 preview version.
This feature doesn't work in the v3 versions due to some changes made in the upstream (you can find some details here #514 (comment) and here #204). You could try the v4.0 version, it should work there.

[moremanu]

Ah that explains, thank you 😅

Will look into those links. Much appreciated.

[svengeance]

What's the status on being able to run containerized solutions (whether via compose or a regular dockerfile) and have the identity injected? Visual Studio has solved this problem and it's becoming a bit of a pain point right now as we investigate workarounds to allow managed identity authentication in local development scenarios.

[rafaelldi]

Right now we are implementing existing features from version 3. After the first stable release of version 4 we will be able to add new features to the plugin.

[MeltdownInteractive]

Hello, when can we see support for Rider 2024.x, and Azure Authentication?
Being able to authenticate with multiple Azure accounts is quite important to my workflow.

Thanks!

[rafaelldi]

The current preview 5 has support for Rider 2024.1 and Azure Authentication. I'm not sure about multiple Azure accounts (and I can't check because I don't have multiple accounts), but in this field we are completely dependent on the base plugin. If they have it, we have it and vice versa.

[MattiaBonanni]

May I ask for a feedback?

We have a piece of code to authenticate against two resources, App Configuration and Azure Key Vault, which relies on a ChainedTokenCredential that uses either a ManagedIdentityCredential or DefaultAzureCredential. The first one is used when the application is deployed, and the latter locally.

ChainedTokenCredential credential = new ChainedTokenCredential([new ManagedIdentityCredential("identityName"), new DefaultAzureCredential()]);

When it tries to access a configuration which reference a value in the KV it throws this error:

By looking at it, it seems that it uses only the ManagedIdentityCredential without try even once with DefaultAzureCredential. Just to double check it, I tried to remove ManagedIdentityCredential all together and it worked as expected locally.

As far as I remember we haven't update Azure.Identity library recently, and some colleagues with Visual Studio haven't report any issue and it worked for me as well at least on preview1 (or 2, I don't quite remember). May it be related somehow to the toolkit?

Thanks

[rafaelldi]

To be honest, I don't know. For DefaultAzureCredential we mainly rely on the az cli login. You could try installing previous previews and see if you can find a version where the behavior has changed.
To do this:

1. Uninstall the current version;
2. On the release page, download the preview release archive;
3. Install the plugin from the disk.

If you find a version, I can check what's changed in that version.

[MattiaBonanni]

Thanks, I'll try to get back with some feedback as soon as I can

[deMD]

When trying the preview with Azure CLI login I get the following error:

2024-07-01 12:54:37,357 [ 423568] SEVERE - com.azure.core.credential.SimpleTokenCache - {"az.sdk.message":"Failed to acquire a new access token"}
2024-07-01 12:54:37,357 [ 423568] SEVERE - com.azure.core.implementation.AccessTokenCache - {"az.sdk.message":"Failed to acquire a new access token.","exception":"execute Azure Cli command 'az account get-access-token --resource https://management.core.windows.net/ -t [guid] --output json' failed due to error: Process exited with an error: 1 (Exit value: 1)."}
2024-07-01 12:54:37,357 [ 423568] SEVERE - com.azure.core.http.policy.RetryPolicy - {"az.sdk.message":"Retry attempts have been exhausted.","exception":"execute Azure Cli command 'az account get-access-token --resource https://management.core.windows.net/ -t [guid] --output json' failed due to error: Process exited with an error: 1 (Exit value: 1).","tryCount":3}
2024-07-01 12:54:37,357 [ 423568] WARN - com.microsoft.azure.toolkit.intellij.common.messager.IntellijAzureMessager - caught an error by messager
com.microsoft.azure.toolkit.lib.auth.AzureToolkitAuthenticationException: execute Azure Cli command 'az account get-access-token --resource https://management.core.windows.net/ -t [guid] --output json' failed due to error: Process exited with an error: 1 (Exit value: 1).
at com.microsoft.azure.toolkit.lib.auth.cli.AzureCliUtils.executeAzureCli(AzureCliUtils.java:84)
at com.microsoft.azure.toolkit.lib.auth.cli.AzureCliAccount$AzureCliTokenCredential.lambda$getToken$3(AzureCliAccount.java:113)
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:45)
at reactor.core.publisher.MonoDelaySubscription.accept(MonoDelaySubscription.java:53)
at reactor.core.publisher.MonoDelaySubscription.accept(MonoDelaySubscription.java:34)
at reactor.core.publisher.FluxDelaySubscription$DelaySubscriptionOtherSubscriber.onNext(FluxDelaySubscription.java:131)
at reactor.core.publisher.MonoDelay$MonoDelayRunnable.propagateDelay(MonoDelay.java:270)
at reactor.core.publisher.MonoDelay$MonoDelayRunnable.run(MonoDelay.java:285)
at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:68)
at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:28)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:840)
Suppressed: com.microsoft.azure.toolkit.lib.auth.AzureToolkitAuthenticationException: execute Azure Cli command 'az account get-access-token --resource https://management.core.windows.net/ -t [guid] --output json' failed due to error: Process exited with an error: 1 (Exit value: 1).
at com.microsoft.azure.toolkit.lib.auth.cli.AzureCliUtils.executeAzureCli(AzureCliUtils.java:84)
at com.microsoft.azure.toolkit.lib.auth.cli.AzureCliAccount$AzureCliTokenCredential.lambda$getToken$3(AzureCliAccount.java:113)
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:45)
at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:76)
at reactor.core.publisher.MonoUsing.subscribe(MonoUsing.java:102)
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53)
at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:76)
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53)
at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:76)
at reactor.core.publisher.MonoUsing.subscribe(MonoUsing.java:102)
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53)
at reactor.core.publisher.MonoFromFluxOperator.subscribe(MonoFromFluxOperator.java:83)
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53)
at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:76)
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53)
at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.subscribeNext(MonoIgnoreThen.java:264)
at reactor.core.publisher.MonoIgnoreThen.subscribe(MonoIgnoreThen.java:51)
at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:76)
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53)
at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:76)
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:53)
at reactor.core.publisher.Mono.subscribe(Mono.java:4512)
at reactor.core.publisher.FluxFlatMap.trySubscribeScalarMap(FluxFlatMap.java:205)
at reactor.core.publisher.MonoFlatMap.subscribeOrReturn(MonoFlatMap.java:53)
at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:63)
at reactor.core.publisher.MonoDeferContextual.subscribe(MonoDeferContextual.java:55)
at reactor.core.publisher.Flux.subscribe(Flux.java:8777)
at reactor.core.publisher.FluxExpand$ExpandBreathSubscriber.drainQueue(FluxExpand.java:179)
at reactor.core.publisher.FluxExpand.subscribeOrReturn(FluxExpand.java:71)
at reactor.core.publisher.InternalFluxOperator.subscribe(InternalFluxOperator.java:55)
at reactor.core.publisher.FluxDefer.subscribe(FluxDefer.java:54)
at reactor.core.publisher.Flux.subscribe(Flux.java:8777)
at reactor.core.publisher.Flux.blockLast(Flux.java:2755)
at com.azure.core.util.paging.ContinuablePagedByIteratorBase.requestPage(ContinuablePagedByIteratorBase.java:102)
at com.azure.core.util.paging.ContinuablePagedByItemIterable$ContinuablePagedByItemIterator.(ContinuablePagedByItemIterable.java:75)
at com.azure.core.util.paging.ContinuablePagedByItemIterable.iterator(ContinuablePagedByItemIterable.java:55)
at java.base/java.lang.Iterable.spliterator(Iterable.java:101)
at com.azure.core.util.paging.ContinuablePagedIterable.stream(ContinuablePagedIterable.java:85)
at com.microsoft.azure.toolkit.lib.appservice.webapp.WebAppModule.lambda$loadResourceIdsFromAzure$0(WebAppModule.java:72)
at java.base/java.util.Optional.map(Optional.java:260)
at com.microsoft.azure.toolkit.lib.appservice.webapp.WebAppModule.loadResourceIdsFromAzure(WebAppModule.java:72)
at com.microsoft.azure.toolkit.lib.appservice.AppServiceResourceModule.getResourcesFromAzure(AppServiceResourceModule.java:35)
at com.microsoft.azure.toolkit.lib.common.model.AbstractAzResourceModule.reloadResources(AbstractAzResourceModule.java:154)
at com.microsoft.azure.toolkit.lib.common.model.AbstractAzResourceModule.list(AbstractAzResourceModule.java:139)
at com.microsoft.azure.toolkit.lib.appservice.webapp.AzureWebApp.lambda$webApps$0(AzureWebApp.java:29)
at java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:273)
at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625)
at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921)
at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:682)
at com.microsoft.azure.toolkit.lib.appservice.webapp.AzureWebApp.webApps(AzureWebApp.java:29)
at com.microsoft.azure.toolkit.ide.common.component.Node$ChildrenBuilder.build(Node.java:409)
at com.microsoft.azure.toolkit.ide.common.component.Node.lambda$buildChildren$20(Node.java:260)
at java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:273)
at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625)
at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921)
at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:682)
at com.microsoft.azure.toolkit.ide.common.component.Node.buildChildren(Node.java:260)
at com.microsoft.azure.toolkit.ide.common.component.Node.refreshChildren(Node.java:294)
at com.microsoft.azure.toolkit.lib.common.utils.TailingDebouncer.lambda$debounce$0(TailingDebouncer.java:34)
at rx.internal.util.ActionSubscriber.onNext(ActionSubscriber.java:39)
at rx.observers.SafeSubscriber.onNext(SafeSubscriber.java:134)
at rx.internal.operators.OperatorSubscribeOn$SubscribeOnSubscriber.onNext(OperatorSubscribeOn.java:74)
at rx.internal.operators.OnSubscribeTimerOnce$1.call(OnSubscribeTimerOnce.java:49)
at rx.internal.schedulers.EventLoopsScheduler$EventLoopWorker$2.call(EventLoopsScheduler.java:189)
at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)

My guess is that this is caused by the fact the subscription I need to connect to requires MFA, which is quite a pain in Azure CLI

As per message in terminal:

The following tenants require Multi-Factor Authentication (MFA). Use 'az login --tenant TENANT_ID' to explicitly login to a tenant.

[shahidcodes]

The azure cli option is still greyed out for me. For the sake of testing, I logged in again from the terminal, restarted IDE and tried to signin from the sidebar pane.

More info:
JetBrains Rider 2024.1.4
Build #RD-241.18034.76, built on June 23, 2024
Runtime version: 17.0.11+1-b1207.24 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 14.5
.NET Core v8.0.1 ARM64 (Server GC)
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 8
Metal Rendering is ON
Registry:
ide.experimental.ui=true
ide.new.project.model.index.case.sensitivity=true
Non-Bundled Plugins:
com.intellij.ml.llm (241.18034.12)
com.github.copilot (1.5.17.6356)
com.intellij.resharper.azure (3.50.0.1784-2024.1)

[rafaelldi]

You're still using the v3 version of the plugin. Here in your message:

com.intellij.resharper.azure (3.50.0.1784-2024.1)

[shahidcodes]

my bad, it did login via cli. I will test and give my feedback of other things. Thanks