Deployment issues for new customers

Currently, all new-customer deployments are non-functional. Existing customers deploying into a new region are also affected. See Known Issues for updates.

Billing Overview

NGINX as a Service for Azure Billing

NGINXaaS for Azure is a consumption-based service, billed hourly in NGINX Capacity Units (NCUs).

These costs will appear on the Azure Portal Cost Analysis page and the Azure Consumption APIs. There may be a 24h delay before usage is visible.

NGINX Capacity Unit (NCU)

An NGINX Capacity Unit (NCU) quantifies the capacity of an NGINX instance based on the underlying compute resources. You specify the desired capacity by the number of NCUs without having to consider the regional hardware differences.

An NGINX Capacity Unit consists of the following parameters:

  • CPU: an NCU provides 20 Azure Compute Units(ACUs)
  • Bandwidth: an NCU provides 60 Mbps of network throughput
  • Concurrent connections: an NCU provides 75 concurrent connections
These limits are subject to change during public preview.

To calculate how many NCUs to provision, take the maximum of each metric.

Sizing Example 1: “I need to support 1,200 concurrent connections but only 4 Mbps of traffic. I need 52 ACUs.” You would need Max(52/20, 4/60, 1200/75) = Max(2.6, 0.07, 16) = At least 16 NCUs.

Sizing Example ?: “I don’t know any of these yet!” Take a rough guess and then, once the NGINX deployment processes some traffic, you can observe the current usage in Azure Monitor and then adjust the provisioned capacity to match the requirements without interruption.

Each NCU provisioned (not consumed) is billed at the rate specified on the Azure Marketplace Offer. The minimum billing interval is 1 hour.

Billing Example: “I provisioned a 20 NCU NGINXaaS for Azure deployment in East US 2. The deployment ran for 1.5 hours, and then I deleted it.”. The hourly rate in East US 2 is $0.05/NCU/hour. The cost, then, is 20 NCU * 0.05$/NCU/hour * 2 hours = $2. Remember, hours are always rounded up.


To provide visibility into how many NCUs are being consumed, NGINXaaS for Azure offers several key metrics, including the following:

  • Bytes recieved: plus.http.request.bytes_rcvd
  • Bytes Sent: plus.http.request.bytes_sent
  • Connections Accepted: nginx.conn.accepted
  • Connections Dropped: nginx.conn.dropped

For more information on the metrics available, see the Metrics Catalog.


The standard Azure networking and bandwidth charges apply to NGINX deployments.

The management traffic for NGINX instances is billed as a Virtual Network Peering - Intra-Region Egress charge. This charge includes the data for shipping metrics and logs. The cost for shipping metrics data is approximately $0.03/month. If you enable NGINX logging the cost increases by roughly $0.005 per GB of logs NGINX generates. To estimate this, multiply the number of requests by the average log line size of the access_log format you have configured.


When creating deployments with ARM templates, the correct SKU is publicpreview_Monthly_gmz7xq9ge3py.