How to choose the right VPN listing for Azure

three types of cloud deployments on a blue background openvpn
Share

Choose Hourly for short-term projects like testing, demos, or temporary contractor access. Run a single server at a known, stable size and pay only for the hours it runs, billed through your Azure account. Choose PAYG SaaS for ongoing deployments, with a monthly or annual contract on your Azure invoice and predictable spend you can budget for. Choose BYOL if you run servers outside Azure too, or want one connection pool across every cloud and data center.

You can pay for OpenVPN Access Server on Microsoft Azure three ways: OpenVPN Access Server – Hourly, a listing with a fixed connection count billed by the hour; a PAYG SaaS contract billed monthly or annually through Azure; and BYOL (bring your own license), where you deploy from Azure Marketplace and buy your subscription from OpenVPN. All three run the same Access Server. What changes is who bills you for the software, how you scale connections, and whether your connections can follow you outside Azure.

We're writing this because customers told us they needed some clarity on which to choose. That's fair, and here's the straight answer for Azure.

OpenVPN Access Server banner

 

The three Azure listings at a glance

 

Hourly

PAYG SaaS (monthly/annual)

BYOL

Who bills the Access Server software

Microsoft Azure

Microsoft Azure

OpenVPN

Who bills Azure infrastructure

Microsoft Azure

Microsoft Azure

Microsoft Azure

How the software is billed

Hourly Marketplace fee while the VM runs

Monthly or yearly SaaS contract, optional auto-renew

Monthly or yearly Access Server subscription

Connection sizing

Fixed tiers, 5 to 750 connections

Preset connection plans, or a custom contract through sales

Any count. Two connections are free with no time limit.

Changing number of connections

Deploy a new instance.

Change the contracted connection limit at renewal; no VM redeployment required.

Increases apply immediately. Decreases take effect at the end of the term.

Share connections across servers

No, each instance has its own tier

Yes, one pool across multiple Access Servers running in Azure

Yes, one pool across any number of servers, in any cloud or on-premises

Account setup

None beyond Azure

A new Access Server Hub account, linked from the Azure portal

An OpenVPN account and an activation key

OpenVPN Access Server – Hourly: pre-licensed and fixed

Hourly works best for short-term projects like testing, demos, or temporary contractor access. The listing comes pre-licensed for a fixed number of simultaneous connections, in 23 tiers from 5 to 750. Azure bills both the Access Server software and the infrastructure through your Azure account. This is helpful if you need access quickly, and without having to onboard a new vendor.

Like other Azure Marketplace VM offers, the software is priced as an hourly Marketplace fee, with partial hours charged per minute and billed monthly.

The trade-off is flexibility. The connection count belongs to the instance, so if you outgrow your tier, or a short-term project becomes a permanent deployment, we recommend migrating to PAYG or a subscription instead of changing tiers in place.

Good fit: one server at a size you're confident about, where hourly metering on the Azure bill is all the procurement you want.

PAYG SaaS: an Azure contract, billed monthly or annually

Azure PAYG is a SaaS contract you buy in the Microsoft Marketplace. When you subscribe, you choose a plan based on the number of connections you need, a monthly or yearly term, and whether it auto-renews. Then you select Configure your account in the Azure portal to link the subscription to a new Access Server Hub account, and deploy the VM with the Azure launcher.

Two things make PAYG work well for larger teams:

  • Pooled or separated connections. You can share one contracted pool across several Access Servers, or give each department or project its own PAYG subscription so spend is easy to track.
  • Azure procurement. The software charge appears on your Azure bill, so there's no new vendor to onboard.

Good fit: teams that buy through Azure, want a predictable monthly or annual commitment, and run their Access Servers in Azure.

BYOL: deploy from Azure, license from OpenVPN

With BYOL, you deploy the Access Server VM from Azure Marketplace and activate it with an Access Server subscription. OpenVPN bills you for the subscription, and Azure bills you separately for the VM and other resources it uses.

The subscription is a central pool of connections. You can activate it on as many servers as you like, so a server in Azure, another in AWS, and one in your own data center all draw from the same pool. Increases apply right away, and decreases take effect at the end of your current term. You can also get an activation key for two free connections with no time limit, which is handy for a lab or a proof of concept. See pricing for current plans.

Good fit: hybrid and multi-cloud environments, teams that already hold an Access Server subscription, and anyone who wants connection counts to move freely between servers.

How to choose

Four questions usually settle it:

  1. Does the purchase need to go through Azure? If procurement wants one invoice, choose PAYG SaaS, or Hourly for a single fixed server.
  2. Do you run Access Server outside Azure? If so, BYOL lets one subscription cover every location.
  3. Will your connection count change? If you expect growth or seasonal swings, skip Hourly. PAYG and BYOL both resize without redeploying.
  4. Is this a short test? The hourly option gives you flexibility to only pay for the amount of time you need. BYOL's two free connections cost nothing beyond Azure infrastructure.

Mixing Hourly, PAYG, and BYOL

This is the question that started this post, so here are the rules:

  • One server, one model. Each Access Server instance is licensed by exactly one model. You can't convert the licensing model on an existing instance.
  • Switching means a new VM. To move an existing running instance from Hourly to PAYG or BYOL, you deploy a new VM, restore your configuration from a backup, move your public IP or hostname, and retire the old VM. After that one-time move, you change connection counts through PAYG or your subscription without migrating again. The migration tutorial covers each step, including the Azure networking settings that a backup doesn't carry over.
  • Pools don't merge. A PAYG contract is billed by Azure, and a BYOL subscription is billed by OpenVPN, so they're separate pools. Size each one for the servers it covers.
  • Different servers can use different models. For example, production can run on a PAYG contract billed through Azure while a lab server runs on BYOL's two free connections.

What stays the same

Whichever listing you choose, you get the same self-hosted Access Server running in your own VNet, with the same features and configuration. Azure always bills the infrastructure (VM, storage, networking) directly, so plan for that cost in every option. If you're replacing Azure VPN Gateway point-to-site before the SSTP cutoff, our SSTP migration guide covers the move itself.

FAQ

Can I switch from the Hourly listing to PAYG or BYOL without redeploying?

No. The licensing model is tied to the instance. You deploy a new VM on the new model and restore your configuration from a backup, as described in the migration tutorial.

Can one subscription cover servers in Azure and other clouds?

Yes, with BYOL. An Access Server subscription can be activated on multiple servers, wherever they run, and they all share one connection pool. An Azure PAYG pool can be shared across multiple Access Servers you deploy through Azure.

Is there a free way to start?

Yes. A BYOL server includes two free connections with no time limit, so you pay only for Azure infrastructure. PAYG also offers a plan with two free connections.

Do I pay Azure infrastructure costs on every listing?

Yes. Azure bills the VM and related resources directly under all three models. Only the Access Server software charge moves between Azure and OpenVPN.

What if I don't want to run a VPN server at all?

Consider CloudConnexa, our cloud-delivered VPN/ZTNA service. You connect your Azure VNet with IPsec or a Connector from Azure Marketplace, and there's no gateway to size or patch. See Comparing CloudConnexa and Azure VPN Gateway.

Find the right fit for your team

Still not sure which listing matches the way you buy and run infrastructure? Look at the options side by side, or talk to us about a custom contract.

 

Get started on Azure

Access Server hourly is available now on Azure Marketplace. Deploy it in your own VNet, connect your first user in minutes, and pay only for the hours it runs.

Deploy Access Server on Azure

Further reading

Sources

Related posts from OpenVPN

Subscribe for Blog Updates