Setting up EPLAN on Azure: what it actually takes.

Teams arrive at this task from different places. Some have run EPLAN on one laptop for years and have outgrown it. Some are retiring the office server it lives on. And some have just purchased EPLAN, and company standards say new workloads run in Azure.

The destination is the same either way: EPLAN on a virtual desktop, the design data in managed storage with backups, and every seat available from anywhere.

EPLAN supports running in your own Azure subscription and publishes Azure Marketplace templates to help: a preconfigured virtual desktop deployment, a SQL server image, and a License Manager image, designed for smaller environments of up to ten users. What the templates do not include is everything underneath and around them. In EPLAN's own words, once the deployments are rolled out, the operation, maintenance, and responsibility for the environment are in your hands.

EPLAN gives you the Marketplace templates. Turning them into a production environment, with networking, security, storage, and costs all configured properly, is the work this piece covers.

What a complete EPLAN Azure setup involves

The application is the visible part. A production setup also includes the networking, the storage, the SQL server that holds parts and project management databases, the license server, the virtual desktop itself, the migration of your master data and projects, printer setup, a security baseline, and testing against real work before anyone relies on it. It ends with a runbook and a credential handover, so the environment is documented and owned by you, not by whoever built it.

None of these steps is exotic. The point is that they all have to happen, in order, configured to work together, and the Marketplace templates assume someone is doing that work.

The license prerequisite to confirm before anything else

The single most common surprise: EPLAN does not permit standalone (single) licenses on Azure Virtual Desktop. Running EPLAN in Azure requires a network license served through EPLAN License Manager, which is why a license server appears in every serious design.

A single-seat network license behaves the way most small teams want anyway: one person at a time, with the seat moving between whoever needs it. But it is a different license type from a standalone license tied to a laptop, and converting is a conversation with EPLAN, not with your infrastructure partner. If 3D is in scope, the same conversation should confirm Pro Panel coverage, because 3D changes the hardware the desktop needs: EPLAN's own guidance calls for a GPU-capable virtual machine for ProPanel and Harness proD work, and that graphics-capable desktop is typically the largest single line in the monthly cost.

What actually drives the monthly cost

An EPLAN environment in Azure has two kinds of cost. A fixed portion runs whether anyone logs in or not: disks, backups, the file share, security and monitoring, networking. And a variable portion that you control directly, where two levers matter most.

Hours the desktop runs. Compute is billed by the hour, which makes running time the biggest lever in the entire bill. For sporadic use, an automatic shutdown outside working hours changes the economics substantially: the desktop is not billing overnight, on weekends, or during the months when design work is quiet. This is where cloud genuinely beats a permanently-on machine for intermittent workloads.

How much storage you reserve. The file share is billed on space reserved, not space used. EPLAN's defaults are generous; if your actual projects and master data are a fraction of the default allocation, right-sizing the share is immediate, permanent savings.

A setup done properly has both levers configured from day one, not discovered on the third invoice.

Who supports what, and the gap in the middle

EPLAN is clear about the support boundary: they support the application, and the operation and maintenance of the virtual environment is the customer's responsibility, with support requests going to whoever operates the Azure environment. When an issue needs both parties, EPLAN expects the customer to coordinate between them.

For a team without Azure operations in-house, that boundary is worth taking seriously before go-live rather than during the first incident. The environment needs an owner: someone accountable for the infrastructure side, who can work an application issue with EPLAN when the cause is ambiguous. That relationship is exactly the kind of thing worth having held for you.

How we make this smooth

We build EPLAN environments on Azure with the setup priced fixed before we start: the full list above, from networking to credential handover, so the risk of it taking longer than expected sits with us rather than you. Azure itself bills nothing until the build begins.

And because the first month is when the assumptions get tested, we treat it that way: the first full Azure bill gets reviewed against the estimate, the shutdown schedule gets tuned to how your team actually works, and anything in the build that needs adjusting gets adjusted. The goal is an environment you own outright, documented, secured, and costing what it should, with the license question settled before a single resource is deployed.

If EPLAN on Azure is on your list, start with two questions: what license type do you hold today, and how many hours a month will the desktop actually run? Those two answers shape everything else. We can help you work through both.