Fix Azure Toolkit for IntelliJ: Setup, Sign-In & Config Errors

Microsoft Fix Intermediate 14 min read Official Docs Grounded Updated April 20, 2026
What's in This Guide
  1. Why This Happens
  2. The Quick Fix
  3. Step-by-Step Solution
  4. Advanced Troubleshooting
  5. Prevention & Best Practices
  6. FAQ

Why This Is Happening

You installed the Azure Toolkit for IntelliJ, opened your IDE, and... nothing works the way it should. Maybe the plugin installed fine but Azure Explorer refuses to load. Maybe sign-in fails silently with no error message you can actually act on. Maybe you upgraded IntelliJ IDEA and now half the Azure menu items have vanished. I've seen this exact set of problems on dozens of developer machines, and I want to be upfront: Microsoft's own error messages in this plugin are often borderline useless. "Authentication failed" doesn't tell you whether it's your JDK, your network, your Azure subscription, or a proxy setting three layers deep.

Here's what's actually going on. The Azure Toolkit for IntelliJ is a plugin that wraps a significant amount of Azure SDK functionality , it supports services like Azure App Service, Azure Functions, Azure Spring Apps, Azure Kubernetes, Azure Container Apps, Azure Virtual Machines, Azure Database for MySQL, Azure Cosmos DB, SQL Server, Azure Storage, and Application Insights. That's a wide surface area, and each of those service integrations has its own authentication path and configuration requirements. When something breaks, the failure can originate in any one of those layers.

The most common root causes I see, in order of frequency:

  • JDK misconfiguration , IntelliJ is pointed at a JDK version that the toolkit doesn't support, or the JAVA_HOME environment variable is pointing somewhere it shouldn't.
  • Plugin version mismatch, You're running IntelliJ IDEA 2024.x but installed a plugin build compiled for 2023.x, or vice versa. This happens a lot after an IDE auto-update.
  • Azure sign-in method conflicts, The toolkit offers four distinct sign-in paths (Azure CLI, OAuth, Device Login, and Service Principal), and if a previous session used one method and your environment changed, the cached token causes silent failures.
  • GitHub Copilot version too old, The Azure MCP Server, which provides AI-powered Azure tooling inside Copilot, requires GitHub Copilot for IntelliJ version 1.5.50 or later. If your Copilot plugin is older than that, the MCP Server simply won't install alongside the Azure Toolkit.
  • Corporate proxy or firewall, Authentication flows that hit login.microsoftonline.com or the Azure management endpoints get silently blocked. You get a timeout with no explanation.

I know this is frustrating, especially when it's blocking your deployment pipeline and your team is waiting on you. The good news is that every one of these causes has a direct fix. Work through this guide in order and you'll have a working Azure Toolkit for IntelliJ setup by the end.

Browse all Microsoft fix guides →

The Quick Fix, Try This First

Before going deep on troubleshooting, try this single-pass reset. It resolves about 60% of broken Azure Toolkit for IntelliJ installations without any further work.

Step 1: Fully uninstall the existing plugin. In IntelliJ IDEA, go to File > Settings > Plugins. Find "Azure Toolkit for IntelliJ" in your Installed tab. Click the gear icon next to it and choose Uninstall. Do not just disable it, actually uninstall. Then close Settings and do a full IDE restart.

Step 2: Clear the plugin cache. After IntelliJ closes, navigate to your IDE's system directory. On Windows that's typically %APPDATA%\JetBrains\IntelliJIdea<version>\plugins. Delete any folder named azure-toolkit-for-intellij or similar. On macOS it lives at ~/Library/Application Support/JetBrains/IntelliJIdea<version>/plugins. This step matters, IntelliJ sometimes leaves behind partial plugin files that corrupt a fresh reinstall.

Step 3: Reinstall from the Marketplace with version matching. Reopen IntelliJ, go back to File > Settings > Plugins > Marketplace, search for "Azure Toolkit", and select Azure Toolkit for IntelliJ by Microsoft. Before hitting Install, verify that the listed compatibility range matches your current IntelliJ build number (you can check your build under Help > About).

Step 4: Sign out of all Azure sessions before signing back in. After the plugin reinstalls and IntelliJ restarts, go to Tools > Azure > Azure Sign Out before attempting any authentication. This clears cached tokens that might be carrying over broken sessions from the previous installation.

If that sequence gets you working, great, skip to the Prevention section. If you're still hitting errors, go through the step-by-step section below.

Pro Tip
Check your IntelliJ IDEA build number (not just the version name) before installing the plugin. Go to Help > About and look for the build number like 243.21565.193. When you're on the Marketplace page for the Azure Toolkit, the plugin listing shows exactly which build ranges it supports. A version name mismatch ("IntelliJ 2024.3") isn't enough, the build number is what the plugin compatibility check actually uses, and a mismatch here is invisible until the plugin silently malfunctions at runtime.
1
Install the Plugin Correctly, Marketplace or Manual Disk Install

The Azure Toolkit for IntelliJ works with both IntelliJ IDEA Ultimate and Community editions. That's worth knowing upfront, you don't need a paid license to use most of the core Azure functionality. What you do need is a supported JDK installed and recognized by IntelliJ before the plugin installs.

Installing from the Marketplace (recommended path):

  1. Launch IntelliJ IDEA.
  2. Open File > Settings (on macOS: IntelliJ IDEA > Settings).
  3. Select Plugins from the left sidebar.
  4. Make sure you're on the Marketplace tab, not Installed.
  5. In the search box, type Azure Toolkit.
  6. When "Azure Toolkit for IntelliJ by Microsoft" appears, click it, then click Install.
  7. When prompted, restart your IDE.

Installing manually from disk (use this when your machine has no internet access or your organization hosts an internal plugin repository):

  1. Download the correct release file from the JetBrains Marketplace page for Azure Toolkit for IntelliJ. Make sure you select the version marked compatible with your IDE build.
  2. In IntelliJ, open File > Settings > Plugins.
  3. Click the gear icon (settings icon) at the top of the Plugins panel.
  4. Select Install Plugin from Disk...
  5. Navigate to the downloaded .zip archive file and select it.
  6. Click OK, then restart when prompted.

After a successful install, you should see an Azure menu item appear in IntelliJ's top menu bar, and a new Azure Explorer tool window should be available in your sidebar. If neither appears, do not move on, the plugin did not load correctly. Check IntelliJ's Help > Show Log in Explorer/Finder for a idea.log file and look for lines containing azure-toolkit or PluginException.

2
Verify Your JDK Configuration Before Anything Else

This step trips up more developers than any other. The Azure Toolkit for IntelliJ requires a properly configured JDK, not just any Java runtime on your system path. IntelliJ needs to know explicitly which JDK to use, and that JDK needs to be one of the versions supported for Azure development.

Microsoft's documentation on JDKs available for Azure development covers this in detail at the Java support on Azure and Azure Stack page. The short version: use a Microsoft Build of OpenJDK or an Azul Zulu distribution when targeting Azure, as these are the distributions with long-term Azure support guarantees.

To check and fix your JDK configuration:

  1. Go to File > Project Structure (shortcut: Ctrl+Alt+Shift+S on Windows/Linux, Cmd+; on macOS).
  2. Select SDKs under Platform Settings in the left panel.
  3. Look at what's listed. If you see a red exclamation mark next to your JDK, IntelliJ can't find the SDK files at the path listed.
  4. Click the + button to add a new SDK. Select JDK and navigate to your JDK installation directory.
  5. Also check File > Settings > Build, Execution, Deployment > Build Tools > Maven (or Gradle), make sure the JVM there matches your project SDK.

You also want to verify the JAVA_HOME environment variable at the system level. Open a terminal (outside of IntelliJ) and run:

echo %JAVA_HOME%    # Windows CMD
echo $JAVA_HOME     # macOS/Linux bash

That path should point to a full JDK installation directory, not a JRE, and not a symlink that resolves to a different version than IntelliJ is using. Mismatches between what your shell sees and what IntelliJ uses are a common cause of Azure Functions local run failures and deployment authentication errors.

If the configuration looks correct and you still see JDK-related errors in the Azure Toolkit output panel, try setting the JDK explicitly inside IntelliJ's Help > Find Action, search for "Switch Boot Java Runtime for the IDE", and point it at your target JDK. This overrides the runtime IntelliJ itself uses, separate from your project SDK.

3
Fix Azure Sign-In Failures, Work Through All Four Methods

Once the plugin is installed and your JDK is sorted, the next wall developers hit is authentication. The Azure Toolkit for IntelliJ provides four sign-in methods, and the right one depends on your environment. Here's how to work through each one when it's failing.

Method 1, Azure CLI Sign-In: This is the method I recommend first for individual developers. It reuses the session from the Azure CLI, so if you're already signed in there, the plugin picks it up automatically. To use it, make sure Azure CLI is installed and you're authenticated:

az login
az account show   # Verify the right subscription is active

Then in IntelliJ: Tools > Azure > Azure Sign In > Azure CLI. If this fails with a "CLI not found" error, your az binary isn't on IntelliJ's PATH. Fix that by adding the CLI's directory to your system PATH and restarting IntelliJ entirely.

Method 2, OAuth Sign-In: Opens a browser window for standard Microsoft account authentication. If your browser opens but you get a callback error, it often means IntelliJ's internal HTTP listener (which waits for the OAuth redirect on localhost) is being blocked by a firewall rule. Temporarily disable any local firewall software and retry.

Method 3, Device Login: The most reliable option in corporate environments. It gives you a code and a URL, you go to https://microsoft.com/devicelogin on any browser, enter the code, and authenticate. This bypasses any localhost redirect issues entirely.

Method 4, Service Principal: For CI/CD pipelines and non-interactive automation. You'll need your tenant ID, client ID, and client secret (or certificate). Enter these under Tools > Azure > Azure Sign In > Service Principal.

After any successful sign-in, you should see your Azure subscriptions populate in the Azure Explorer panel. If the panel stays empty after authentication, right-click inside it and choose Refresh. If subscriptions still don't appear, your account may not have the Reader role on the subscription, check your Azure RBAC assignments in the Azure portal.

4
Configure the Azure MCP Server and GitHub Copilot Integration

The Azure MCP Server is one of the toolkit's newer capabilities, and its installation requirements are specific enough that a lot of developers miss them. The MCP Server adds context-aware AI tools inside GitHub Copilot for IntelliJ, it gives Copilot actual awareness of your Azure resources across services like App Service, Functions, Cosmos DB, and more.

Here's what you need to know: the Azure MCP Server is automatically installed with the Azure Toolkit only when GitHub Copilot for IntelliJ version 1.5.50 or later is already installed on your machine. If Copilot isn't installed, or if it's an older version, the MCP Server does not install automatically. You won't get an error, it just silently won't be there.

To check your Copilot version: File > Settings > Plugins > Installed, find GitHub Copilot, and check the version number shown. If it's below 1.5.50, click the update button.

One thing worth being clear about: GitHub Copilot for Azure (the Microsoft-specific Copilot variant) is not available for IntelliJ. What you want is GitHub Copilot for IntelliJ (the JetBrains plugin from GitHub), version 1.5.50 or later. That's the one that gets Azure-aware capabilities added to it by the MCP Server.

To verify the Azure MCP Server installed correctly after you have both plugins:

  1. Open File > Settings > Tools > Azure Toolkit, look for an MCP Server section.
  2. In a Copilot Chat window inside IntelliJ, try asking something Azure-specific like "What App Services do I have in my subscription?", if the MCP Server is active, Copilot will query your actual Azure resources rather than giving a generic answer.

If the MCP Server installed but Copilot can't see Azure resources, make sure you've completed Azure sign-in (Step 3 above) first. The MCP Server needs a valid Azure session to pull resource context.

5
Deploy to Azure and Validate Your First Service Connection

Once authentication is working, the real test is actually deploying something. The Azure Toolkit for IntelliJ provides workflow support for Azure Web App, Azure Functions, Azure Spring Apps, and Azure Container Apps, each with its own deployment path inside IntelliJ.

The fastest validation is deploying a Hello World app to Azure App Service. The official getting started guide walks through creating a basic web application and deploying it within minutes using the toolkit's built-in wizard. To access it: Tools > Azure > Getting Started Guide. This wizard creates a basic Spring Boot or Jakarta EE project, configures App Service settings, and runs the deployment, all from inside IntelliJ.

For Azure Functions specifically, the workflow is: scaffold a new Functions project via File > New > Project > Azure Functions, run and debug it locally using the local Functions runtime, then right-click the function in the Azure Explorer and choose Deploy to Azure. Common errors at this stage:

  • "Azure Functions Core Tools not found", Install the Functions Core Tools separately (npm install -g azure-functions-core-tools@4) and make sure func is on your system PATH.
  • "Deployment failed: 403 Forbidden", Your Azure account doesn't have Contributor access on the target resource group. Fix the RBAC assignment in the Azure portal.
  • Deploy completes but app doesn't start, Check the application logs via Azure Explorer > App Services > [your app] > View Streaming Log. The toolkit streams logs directly into IntelliJ's output panel, which is genuinely useful for chasing down startup errors.

For Kubernetes and Container Apps deployments, the Azure Explorer panel under the respective service node gives you create/manage options. For Apache Spark jobs targeting Azure Synapse or HDInsight, the toolkit provides project templates and job submission dialogs, HDInsight ESP clusters (domain-joined) require MFA authentication, which routes through the Device Login method from Step 3.

If the Azure Explorer tool window shows your resources but operations like "Start" or "Deploy" silently fail, open Help > Show Log in Explorer and check idea.log for HTTP 401 or HTTP 403 responses from Azure management APIs. These almost always mean your token expired or your RBAC permissions changed.

Advanced Troubleshooting

Proxy and network-level authentication failures are the hardest category to debug because the error surface is so opaque. If you're in a corporate environment where outbound traffic routes through an authenticated proxy, the OAuth and Device Login flows may time out before completing. Here's how to configure IntelliJ's proxy settings to match your network:

  1. Go to File > Settings > Appearance & Behavior > System Settings > HTTP Proxy.
  2. Select Manual proxy configuration and fill in your proxy host, port, and credentials.
  3. Click Check connection and point it at https://management.azure.com, that's the Azure Resource Manager endpoint the toolkit hits for most operations.

If that test times out, your proxy is blocking the connection and you need to work with your network team to whitelist the Azure management endpoints.

IntelliJ idea.log analysis, When you have a failure with no visible error, this file is your best friend. Find it at Help > Show Log in Explorer. Search for these specific patterns:

  • com.microsoft.azure.toolkit, All Azure Toolkit log entries are prefixed here.
  • AzureLoginHelper, Authentication flow events.
  • PluginException, Plugin load failures, often accompanied by a stack trace pointing at the exact incompatibility.

Multiple Azure subscriptions and tenant switching, If your account has access to multiple Azure tenants or subscriptions, the toolkit may authenticate against the wrong one. After sign-in, go to Tools > Azure > Select Subscriptions. A dialog lists all accessible subscriptions. Make sure the right ones are checked. If you need to switch tenants entirely, sign out completely (Tools > Azure > Azure Sign Out) and re-authenticate using the CLI method with az login --tenant <tenant-id> to target the specific tenant.

Plugin conflicts, Some third-party plugins that hook into IntelliJ's HTTP client or authentication chain can interfere with the Azure Toolkit's token handling. If you've tried everything and the toolkit still misbehaves, try running IntelliJ in safe mode: Help > Find Action > "Restart in Safe Mode". Safe mode disables all non-bundled plugins. If things work in safe mode, re-enable your plugins one by one to find the conflict.

Enterprise domain-joined machines with Conditional Access, If your Azure AD tenant enforces Conditional Access policies (device compliance, managed device requirements, MFA at specific intervals), the OAuth and CLI flows may fail even with valid credentials. Device Login is typically the most Conditional Access-friendly option because it delegates the full auth flow to the browser. If even that fails, contact your Azure AD administrator to confirm your device is marked compliant in Intune.

When to Call Microsoft Support
If you've worked through every step here and the toolkit is still failing, particularly if you're seeing 5xx errors from Azure management APIs in the idea.log, or if your service principal authentication worked yesterday and stopped today without any configuration change, that's a signal to escalate. Authentication token issuance failures and Azure-side permission propagation delays are not things you can fix on the client side. Open a support ticket at Microsoft Support. Before you do, export your idea.log (redact any tokens you see), note your plugin version (Settings > Plugins > Installed > Azure Toolkit), your IntelliJ build number, and your JDK version, support will ask for all of these immediately.

Prevention & Best Practices

Most Azure Toolkit for IntelliJ problems are preventable. They cluster around a handful of recurring patterns, and once you set things up correctly the first time, you rarely need to revisit them.

Pin your IntelliJ and plugin versions in team environments. Auto-updating IntelliJ to a new major version without simultaneously updating the Azure Toolkit plugin is the single biggest cause of the "Azure menu disappeared" complaint. If you're working on a team, decide on a tested IntelliJ version and a specific Azure Toolkit version together, document that combination, and update them together on a schedule. The JetBrains Toolbox app makes this easy, you can pin a specific IDE version and get notified of updates without auto-applying them.

Use the Azure CLI as your primary sign-in method for development. The CLI session is the most predictable and easiest to refresh. When your token expires, running az login in a terminal immediately updates the session the toolkit is reading. Compare that to OAuth sessions, where a silent expiry means you don't know you're unauthenticated until a deployment fails mid-flight.

Set up a dedicated Azure service principal for CI/CD. Do not use your personal Azure account credentials in any automated pipeline. Create a service principal with the minimum required RBAC permissions for what your pipeline needs to do, and configure the toolkit's Service Principal sign-in method for non-interactive runs. Rotate the service principal secret on a schedule and store it in Azure Key Vault or your CI system's secret manager, not in a config file in your repo.

Keep GitHub Copilot for IntelliJ at version 1.5.50 or later if you want the Azure MCP Server features. This isn't a nice-to-have, if Copilot drops below that version, the MCP Server loses its connection to Azure context and Copilot's Azure-aware responses degrade back to generic answers. Set Copilot updates to automatic in Settings > Plugins > Installed > GitHub Copilot > Enable auto-update.

Quick Wins

Frequently Asked Questions

The Azure menu isn't showing in IntelliJ after installing the toolkit, what do I do?

This almost always means the plugin didn't load successfully, even if the Marketplace shows it as "installed." Go to Help > Show Log in Explorer and open idea.log. Search for "azure-toolkit" and look for any PluginException or ClassNotFoundException entries. The most common causes are a JDK version mismatch (the plugin failed to initialize), or an IntelliJ build incompatibility. Try a full uninstall-and-reinstall as described in the Quick Fix section, making sure your IntelliJ build number falls within the plugin's stated compatibility range before reinstalling.

Azure Toolkit for IntelliJ sign-in keeps failing with "Authentication failed", how do I actually fix this?

That error message is almost criminally unhelpful, I know. The first thing to try is switching sign-in methods, if OAuth is failing, go to Tools > Azure > Azure Sign In and try Device Login instead. Device Login gives you a code and a URL to visit in any browser, bypassing any localhost redirect issues. If all four methods fail, check your corporate proxy settings at File > Settings > Appearance & Behavior > System Settings > HTTP Proxy and make sure IntelliJ can reach https://login.microsoftonline.com. Also check whether your Azure AD tenant has Conditional Access policies that might be blocking non-compliant device authentication.

Does the Azure Toolkit for IntelliJ work with the Community Edition, or do I need Ultimate?

It works with both IntelliJ IDEA Ultimate and Community editions. The plugin itself doesn't require an Ultimate license. That said, some workflows, like working with Spring Boot run configurations or certain database integrations, benefit from Ultimate's additional features. For pure Azure Functions, Azure App Service, Kubernetes, and Cosmos DB development, Community edition is fully capable. The requirements listed in the official documentation are just a supported JDK and, optionally, GitHub Copilot for IntelliJ if you want the Azure MCP Server features.

How do I get the Azure MCP Server working inside GitHub Copilot for IntelliJ?

The Azure MCP Server installs automatically alongside the Azure Toolkit only if GitHub Copilot for IntelliJ is already at version 1.5.50 or later. Check your Copilot version at Settings > Plugins > Installed > GitHub Copilot. If it's below 1.5.50, update it first. Then reinstall the Azure Toolkit for IntelliJ, the MCP Server should install with it this time. After that, complete an Azure sign-in (Tools > Azure > Azure Sign In) so the MCP Server has a session to query your actual Azure resources. Note that GitHub Copilot for Azure is not available for IntelliJ, you need the standard GitHub Copilot for IntelliJ plugin.

Azure Explorer shows my subscriptions but no resources, why is it empty?

This is almost always an RBAC (role-based access control) issue. The Azure Toolkit queries the Azure Resource Manager API to list resources, and if your account only has permissions at the resource level (not the subscription or resource group level), Explorer can't enumerate them. Sign into the Azure portal and check what role assignments your account has at the subscription and resource group level, you need at least the Reader role on a subscription or resource group for Explorer to list its contents. Also try right-clicking inside the Azure Explorer panel and choosing Refresh, and make sure you've selected the correct subscriptions under Tools > Azure > Select Subscriptions.

I upgraded IntelliJ IDEA and now the Azure Toolkit says it's incompatible, what's the fastest fix?

Go to File > Settings > Plugins > Installed, find the Azure Toolkit, and click the Update button if one is available. If no update is shown, click the gear icon and select Manage Plugin Certificates & Repositories to force a refresh of the plugin index. Sometimes IntelliJ caches plugin compatibility data and doesn't pick up new releases immediately. If the latest available version of the plugin still lists your new IntelliJ version as incompatible, check the Azure Toolkit's GitHub repository for any open issues about that specific IntelliJ build, it may be a known gap with a workaround or a fix that's in the next plugin release.

Related Microsoft Fix Guides

Microsoft Fix
How to Fix Windows Update Errors (Error 0x80070003 & More)
Microsoft Fix
Fix Microsoft 365 Sign-In Problems, Complete Guide
Microsoft Fix
Azure Active Directory Troubleshooting Guide
Browse All
5,000+ Microsoft Fix Guides →
H
Sai Kiran Pandrala
Our team includes certified Microsoft engineers, Azure architects, and system administrators with 10+ years of enterprise IT experience. Every guide is written from hands-on troubleshooting, not guesswork. We test every fix before publishing.