Fix Azure Toolkit for Eclipse: Setup, Sign-In & Deploy Errors
Why This Is Happening
You sat down to get some Java development done, fired up Eclipse, installed the Azure Toolkit for Eclipse, and then... nothing works the way it should. Maybe the Azure Explorer view is just gone. Maybe clicking Tools → Azure → Sign In opens a browser that seems to complete sign-in, but Eclipse never acknowledges it. Or the classic one: you go to create a new project, look for Dynamic Web Project under the New menu, and it simply isn't there. I've seen all of these on dozens of developer machines , and they all have fixable causes.
The Azure Toolkit for Eclipse is a genuinely powerful plugin. It lets you create, test, and deploy cloud applications to Azure App Service directly from your Eclipse IDE, manage Redis caches and storage accounts, and even submit Spark jobs to HDInsight clusters. The problem is that it sits on top of a fairly finicky dependency stack: your Eclipse IDE version, your Java Development Kit build, your OS-level proxy settings, and Microsoft's authentication endpoints all have to cooperate simultaneously. When one of them is slightly off, the whole experience falls apart , and Eclipse's error messages are famously unhelpful about which layer is actually broken.
Here are the most common root causes I see:
- Wrong Eclipse build selected in Marketplace, the toolkit lists compatible builds explicitly, and installing against an incompatible Eclipse version causes silent failures at sign-in and deployment
- Unsupported JDK version, the plugin requires an Azure-supported JDK; Oracle JDK builds that are not on Microsoft's approved list cause authentication and runtime errors
- Missing Web/Java EE components, Eclipse ships in flavors; the standard "Eclipse IDE for Java Developers" does not include the Web, XML, Java EE and OSGi Enterprise Development tools, which means Dynamic Web Project never shows up
- Device Login browser redirect failures, corporate network policies, VPNs, and browser cookie settings frequently break the OAuth Device Login flow mid-authentication
- Azure Explorer view accidentally closed, it's not obvious how to get it back, so many developers assume the plugin uninstalled itself
- Subscription filtering set to zero, you sign in successfully, but no subscriptions are checked in the Select Subscriptions dialog, so the Explorer shows nothing
I know this is frustrating, especially when you just want to push a quick update to Azure App Service and instead find yourself troubleshooting an IDE plugin for two hours. The good news is that every one of these issues follows a predictable pattern, and this guide walks through each one in order. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you go deep into advanced troubleshooting, this single sequence resolves the majority of Azure Toolkit for Eclipse issues I encounter. It takes about five minutes and covers the most common failure modes.
Step 1, Verify your Eclipse version is compatible. Open Eclipse, go to Help → About Eclipse IDE, and note your version (e.g., 2023-06, 2024-03). Now open the Eclipse Marketplace page for the Azure Toolkit and confirm your version is listed as compatible. Trying to run the toolkit on an unsupported Eclipse build is the single most common reason things silently break.
Step 2, Reinstall via Eclipse Marketplace, not the drag-and-drop method. In your Eclipse IDE, go to Help → Eclipse Marketplace. Search for "Azure Toolkit for Eclipse" and click Install. Follow the wizard through. Let it resolve dependencies automatically, do not skip any items it wants to install alongside the main plugin. Accept the license agreements and restart when prompted.
Step 3, Use Device Login, not the default sign-in method. After restart, go to Tools → Azure → Sign In. In the Azure Sign In window, explicitly select Device Login and then click Sign in. Click Copy & Open in the next dialog, this copies your one-time device code and opens your default browser simultaneously. Paste the code in the browser when prompted and complete authentication. Switch back to Eclipse and check the Select Subscriptions dialog. Make sure at least one subscription is checked before clicking Select.
If that sequence gets you signed in and the Azure Explorer view shows your resources, you're done. If not, keep reading, the step-by-step section covers every remaining scenario in detail.
https://microsoft.com/devicelogin and paste it there. This saves you from thinking the whole sign-in flow is broken when it's just a browser permission issue.
There are two legitimate ways to install the Azure Toolkit for Eclipse, and one of them causes problems significantly more often than the other. Let me be direct: use the Eclipse Marketplace method. The "Install New Software" approach via a direct update site URL works, but it requires you to manually manage the update site address, and if you're pointing at the wrong URL or a stale one, you'll get partial installs that look complete but fail at runtime.
Here's the Marketplace method, step by step:
- In Eclipse, click Help in the top menu bar
- Click Eclipse Marketplace
- In the search box, type Azure Toolkit for Eclipse and press Enter
- When the result appears, click Install
- Work through the installation wizard, do not uncheck any of the bundled components it wants to install
- In the Review Licenses dialog, accept the license terms and click Finish
- When installation completes, click Restart Now when prompted
If the Marketplace isn't accessible from your network (corporate proxy environments sometimes block it), the alternative is Help → Install New Software. In the Available Software dialog, click Manage, confirm the latest Eclipse version is selected, then click Apply and Close. Use the Work with: dropdown to select the latest Eclipse version site, scroll to find Web, XML, Java EE and OSGi Enterprise Development, and install it. This ensures you have the foundational web tools the Azure Toolkit depends on.
After a successful install, you should see Azure appear under the Tools menu in Eclipse's top navigation bar. If it's not there, Eclipse likely needs a full restart, not just a quick restart, but a full close-and-reopen from the OS.
The Azure Toolkit for Eclipse sign-in flow supports multiple authentication methods, but Device Login is the one that actually works reliably across corporate networks, VPNs, and machines where browser-to-desktop OAuth redirects are blocked. Here's exactly how to use it.
After installing the toolkit and restarting Eclipse:
- Click Tools in the top menu
- Hover over Azure
- Click Sign In
- In the Azure Sign In window, select Device Login from the available options
- Click Sign in
- The Azure Device Login dialog will appear with a code, click Copy & Open
- Your default browser opens to the Microsoft device login page, paste the code (it's already in your clipboard) and click Next
- Select your Azure account from the list and complete any multi-factor authentication prompts your organization requires
- Once your browser shows a "Signed in" confirmation, close the browser tab and switch back to Eclipse
- In the Select Subscriptions dialog that appears in Eclipse, check every subscription you want to work with, then click Select
The step most people miss is that last one. If you click Select without checking any subscriptions, the Azure Explorer shows up empty and it looks like authentication failed, but you're actually signed in, you just told Eclipse not to display any resources. If that happened to you, go to Tools → Azure → Select Subscriptions to reopen that dialog and check the right ones.
After sign-in completes, you should see your Azure subscriptions expand in the Azure Explorer view. If the Explorer view isn't visible at all, move on to Step 4 of this guide.
This is the fix for the missing "Dynamic Web Project" problem. When you go to File → New → Project and expand the Web folder in the New Project dialog, and nothing is there, it means your Eclipse installation doesn't have the Java EE web tooling installed. This is extremely common because standard Eclipse downloads don't include it by default.
Here's how to add it:
- Click Help in the top menu
- Click Install New Software
- In the Available Software dialog, click Manage
- Confirm that your current Eclipse version (e.g., 2023-06 or 2024-03) is shown and selected
- Click Apply and Close
- Back in the Available Software dialog, click the Work with: dropdown and select the update site that matches your Eclipse version
- Wait for the software list to load, then scroll down until you see Web, XML, Java EE and OSGi Enterprise Development
- Check the box next to it and click Next
- In the Install Details window, review what will be installed and click Next again
- Accept the license terms and click Finish
- Watch the progress indicator in the lower-right corner of your Eclipse workspace, installation runs in the background
- Click Restart Now when Eclipse prompts you
After Eclipse restarts, go to File → New, expand the menu, click ...Project, and look under the Web category. You should now see Dynamic Web Project listed. This is the project type you need for Azure App Service deployments.
With the plugin installed, signed in, and web tools in place, creating the actual project is straightforward. This step walks through building a working Dynamic Web Project from scratch.
- Click File, hover over New, then click ...Project
- In the New Project dialog, expand Web and select Dynamic Web Project
- Click Next
- Enter a project name, for testing purposes, something like MyWebApp works fine
- Accept the default settings for Target Runtime and Dynamic Web Module version unless you have a specific Azure App Service runtime target
- Click Finish
Now add your JSP content:
- In the Package Explorer pane on the left, expand your project
- Right-click WebContent, hover over New, and click Other...
- Expand Web and select JSP File, then click Next
- Name the file index.jsp, confirm the parent folder is set to
MyWebApp/WebContent, and click Next - In the Select JSP Template dialog, choose New JSP File (html 5) and click Finish
When the file opens in the editor, add your content inside the existing <body> element. A minimal working example looks like this:
<body>
<b><% out.println("Hello World!"); %></b>
</body>Save the file with Ctrl+S. The project is now ready to deploy. You should see no red error markers in the Package Explorer, if you do, it usually means the JDK configuration needs attention (see the Advanced section below).
This is where the Azure Toolkit for Eclipse really earns its keep, deploying directly from the IDE to Azure App Service without touching the Azure portal. Here's the exact deployment path:
- In the Package Explorer pane, right-click your project (e.g., MyWebApp)
- Hover over Azure in the context menu
- Click Publish as Azure Web App
- The Deploy Web App dialog box appears. You have two paths here:
- If you already have a web app running on Azure App Service, select it from the list
- If you need a new one, click Create
- If creating new: In the Create App Service dialog, configure your runtime environment (choose a Java version that matches your project's JDK), select or create an App Service plan, assign it to a resource group, and add any necessary app settings. Click Create
- Once the App Service is ready (new or existing), select it and click Deploy
Watch the Azure Activity Log tab at the bottom of Eclipse. A successful deployment shows a Published status entry that is clickable, it's a hyperlink directly to your deployed web app's URL. Click it to verify everything is live in your browser.
If the deployment fails with a timeout or connection error, it's almost always either a proxy issue (see Advanced section) or an App Service plan that is stopped rather than running. You can check App Service status right inside Eclipse via the Azure Explorer, right-click your web app and look at the available options in the context menu. You can also delete the resource from there when you're done testing, which is the cleanest way to clean up.
Advanced Troubleshooting
Azure Explorer View Is Gone
This catches a lot of developers off guard. The Azure Explorer view can be accidentally closed just like any other Eclipse view panel, and it's not obvious how to get it back. No reinstall needed, here's what to do:
- Click Window in the top menu
- Hover over Show View
- Click Other...
- In the Show View dialog, expand the Azure folder
- Select Azure Explorer
- Click Open
It will reappear in your IDE exactly where it was before. You can then drag it to dock wherever you prefer.
Sign-In Fails Behind a Corporate Proxy
If your Eclipse environment sits behind a corporate proxy, the Device Login browser redirect may complete in the browser but the token never makes it back to Eclipse. The fix is to configure Eclipse's network settings explicitly: go to Window → Preferences → General → Network Connections. Set the Active Provider to Manual, then add your proxy host and port for both HTTP and HTTPS. If your proxy requires authentication, add credentials here as well. After saving, attempt the Device Login flow again.
Subscription Shows in Azure Portal but Not in Eclipse
This is almost always a subscription selection issue. After signing in through Tools → Azure → Sign In, Eclipse prompts you with a Select Subscriptions dialog. If you dismissed it without checking any boxes, or if your access to a subscription changed after you last signed in, the Explorer will appear empty. Go to Tools → Azure → Select Subscriptions to reopen the dialog. Check every subscription you need, then click Select. Your resources should appear in the Azure Explorer within a few seconds of refresh.
JDK Compatibility Errors at Build Time
The Azure Toolkit requires an Azure-supported JDK, not just any JDK installed on your machine. If your project has red error markers related to the JRE System Library, right-click your project in Package Explorer, go to Build Path → Configure Build Path, click the Libraries tab, select the JRE System Library entry, and click Edit. Point it to an Azure-supported JDK (available from Microsoft's Java download page). Save and rebuild.
Domain-Joined / Managed Device Environments
On domain-joined machines managed by Intune or Group Policy, the Device Login flow may be blocked at the OS level. Your IT department may have a Conditional Access policy that prevents device code authentication from non-compliant devices. In that case, the real fix lives with your Azure AD / Entra ID admin, the policy governing which authentication methods are permitted for developer tooling needs to be reviewed. In the meantime, you can try the Interactive Login option in the Azure Sign In dialog instead of Device Login, which uses a standard browser redirect that may be permitted under a different Conditional Access rule.
Reading Eclipse Error Logs
When something silently fails in the toolkit, Eclipse logs the full stack trace in its error log. Go to Window → Show View → Error Log. Sort by Timestamp descending and look for entries from com.microsoft.azure or com.microsoft.tooling. The actual error message in these entries is almost always more useful than whatever was shown (or not shown) in the UI. Copy the full stack trace when raising an issue on the GitHub repository.
Prevention & Best Practices
Once you have the Azure Toolkit for Eclipse working the way it should, a few habits will keep it that way. The plugin gets updated regularly, new features, bug fixes, compatibility adjustments for newer Eclipse releases, and staying on top of those updates prevents the slow drift where things "just stop working" and you can't quite pinpoint when it started.
Keep your Eclipse version current. The toolkit's compatibility matrix is tied to Eclipse release trains (named like 2023-06, 2024-03, etc.). When Eclipse ships a new quarterly release, the toolkit team validates against it and usually ships an update within a few weeks. Running an Eclipse version that's more than two releases behind means you're depending on compatibility that may not be maintained long-term.
Stick with an Azure-supported JDK. Using an arbitrary JDK you downloaded from Oracle or OpenJDK's website isn't wrong per se, but using one from Microsoft's list of Azure-supported builds means your runtime environment on your dev machine matches what Azure App Service will use. This eliminates an entire class of "works on my machine" deployment bugs where the WAR deploys fine but behavior differs between local testing and production.
Clean up Azure resources after testing. The Azure Toolkit for Eclipse makes deployment so easy that it's tempting to spin up App Service plans and web apps constantly during testing. Azure App Service plans cost money even when idle. Make it a habit to right-click finished test web apps in Azure Explorer and select Delete immediately after you're done. This also keeps your resource list clean and prevents you from accidentally deploying to a test environment you'd forgotten about.
Don't share Eclipse workspaces across JDK versions. Switching the JDK that a workspace uses, especially between major versions like Java 11 and Java 21, can corrupt project build paths in ways that are time-consuming to untangle. If you need to work with different Java versions, use separate Eclipse workspaces.
- Check for toolkit updates monthly: Help → Check for Updates in Eclipse takes 30 seconds and prevents compatibility drift
- Bookmark the Eclipse Marketplace page for the Azure Toolkit for Eclipse, the compatible builds list updates without announcement and is the fastest way to confirm version support
- Configure Eclipse's network proxy settings before you need them, doing it proactively means sign-in just works when you change networks
- Pin the Azure Explorer view to your Eclipse layout and save the perspective, this way a misclick never hides it again
Frequently Asked Questions
The Azure Toolkit for Eclipse isn't showing up under the Tools menu after installation, what went wrong?
This almost always means Eclipse did not fully restart after installation, or the installation was interrupted before completion. Do a full close-and-reopen of Eclipse, not just the "Restart" button inside the IDE, but actually closing it from the taskbar and relaunching it. If it still doesn't appear, go to Help → Installation Details and look for the Azure Toolkit in the Installed Software tab. If it's not listed there, the installation failed silently, repeat the Marketplace install process from the beginning, watching the progress indicator at the bottom-right of the Eclipse workspace to confirm it actually completes.
I completed the Device Login in my browser and it said "Signed in successfully" but Eclipse still shows me as signed out. Help?
This is the corporate proxy scenario in almost every case I've seen. The Device Login token exchange happens between Eclipse and Microsoft's authentication servers, and if your proxy blocks that callback, Eclipse never receives confirmation even though your browser authenticated fine. Go to Window → Preferences → General → Network Connections, set Active Provider to Manual, and enter your proxy details. Then try the sign-in flow again. If you don't know your proxy settings, check with your IT department, or try the Interactive Login option in the Azure Sign In dialog, which uses a different network path that sometimes bypasses the issue.
Where is Dynamic Web Project? I can't find it under File → New in Eclipse.
This means your Eclipse installation is missing the Web, XML, Java EE and OSGi Enterprise Development component package. It's a separate install from the core Eclipse IDE and from the Azure Toolkit. Go to Help → Install New Software, use the Work with dropdown to select your current Eclipse version's update site, scroll to the Web and Java EE section, check it, and install. Restart Eclipse after. After that restart, Dynamic Web Project will appear under File → New → ...Project → Web.
My Azure Explorer view shows my subscriptions but no resources inside them, is my account broken?
Your account is almost certainly fine. This is usually one of two things: either the Azure Explorer view needs a manual refresh (right-click anywhere in the Explorer and look for a Refresh option), or you're signed in but the subscription you care about wasn't checked in the Select Subscriptions dialog. Go to Tools → Azure → Select Subscriptions, verify the right subscriptions are checked, and click Select. The Explorer should populate within a few seconds. If you genuinely have no resources in a subscription, they'll also appear empty in the Azure portal, so that's an easy cross-check.
Deployment to Azure App Service fails with a "timeout" error from within Eclipse, what should I check?
First, check that your App Service is in the Running state and not Stopped, you can verify this in the Azure Explorer by expanding your subscription and navigating to the web app. Second, check the Azure Activity Log tab in Eclipse for a more specific error code, timeout is the generic message but the underlying cause varies. Third, if you're on a corporate network, large WAR file deployments sometimes exceed proxy timeout thresholds; try splitting your build or deploying during off-peak hours. Finally, verify that your App Service plan has enough compute tier to accept the deployment, free and shared tiers have deployment limitations that higher tiers don't.
Can I use the Azure Toolkit for Eclipse with IntelliJ IDEA instead?
Yes, there is a separate Azure Toolkit for IntelliJ that is distinct from the Eclipse version but offers equivalent functionality for deploying Java web apps and managing Azure resources from within IntelliJ IDEA. Microsoft maintains both toolkits in parallel. The sign-in flow, App Service deployment steps, and Azure Explorer behavior are very similar between the two, so switching is relatively painless if IntelliJ is your preferred IDE. The official Microsoft documentation covers both and links between the two tutorials.