Deploy using the Azure portal


This guide explains how to deploy NGINX as a Service (NGINXaaS) for Azure using Microsoft Azure portal. The deployment process involves creating a new deployment, configuring the deployment, and testing the deployment.

Find the NGINX as a Service for Azure offer in the Azure portal

You can start the NGINXaaS deployment process by visiting the Create NGINXaaS page or finding the NGINXaaS service in the Azure portal:

  1. Sign in to the Azure portal with your Azure account.
  2. Use the search field to find “NGINXaaS” in the Azure Portal. In the Services results, select NGINXaaS.
  3. Select + Create on the NGINXaaS page to start the deployment process.

Create a deployment

Basics tab

  1. On the Create NGINXaaS Deployment Basics page, provide the following information:

    Resource Basics Tab

    Field Description
    Subscription Select the appropriate Azure subscription that you have access to.
    Resource group Specify whether you want to create a new resource group or use an existing one.
    For more information, see Azure Resource Group overview.
    Name Provide a unique name for your deployment.
    Region Select the region you want to deploy to.
    Pricing Plan Select the Standard plan. For more information, see Pricing Plans
    Scaling Select Manual to set the capacity of your deployment in NCUs or select Autoscale to automatically adjust the capacity of your deployment. Learn more about NCUs in Scaling Guidance.
    Email Provide an email address that can be notified about service alerts, maintenance data and activity reports.
    Upgrade Channel Select the desired upgrade channel for your deployment. For more information, see Upgrade Channels.

  2. Select Next: Networking.

Networking tab

  1. On the Create NGINXaaS Deployment Networking page, provide the following information:

    Resource Networking Tab

    Field Description
    Virtual Network A virtual network is required for communication between the resources you create.
    You can create a new virtual network or use an existing one (for an existing one see note below).
    Additionally, you can peer a new virtual network with existing ones (in any region) to create network access from NGINXaaS for Azure to your upstream servers. To peer the virtual network with another see Create, change, or delete a virtual network peering.
    Subnet If you select an existing virtual network, you can select the existing subnet to be used. Before creating a deployment, the existing subnet needs to be delegated to NGINX.NGINXPLUS/nginxDeployments. To delegate a subnet to an Azure service, see Delegate a subnet to an Azure service.

    Otherwise, if you have chosen to create a new virtual network, a new subnet will be selected by default.

    The minimum size subnet is /27; however, we recommend a subnet size of /24.

    The subnet can contain other resources and is not dedicated to the NGINXaaS for Azure resource.
    Allow NGINX access to Virtual Network Confirm that you allow:
    - Registration of the NGINX provider to your Azure subscription.
    - Delegation of the subnet to the NGINX provider.
    IP address Set the IP address (public or private) that the service listens to for requests:

    If you select a public IP address:
    - Create a new public IP or use an existing one (for an existing one see the note below).
    - Set the resource name for your public IP address.
    Newly created public IPs are zone-redundant in supported regions.

    If you select a private IP address:
    - Provide a static IP address from the same subnet range set previously.
    Inbound port rules Select None to disallow inbound access on any port, or choose to allow traffic from one of these common http(s) ports.

    Note: This option is only available when specifying a new virtual network as part of the create workflow. If you select an existing virtual network which is associated with a subnet and Network Security Group (NSG), you will need to edit the Inbound security rules to add access for the specific ports you want to allow (for example, ports 80 and 443).
    Apply default NGINX configuration Confirm that you want your NGINXaaS deployment to be bootstrapped with a default NGINX configuration and a browsable splash page.

  2. Select Next: Tags.

Tags tab

  1. Add custom tags for the new NGINXaaS Deployment. Each tag consists of a name and value.

    Resource Tags Tab
  2. After adding the tags, select Next: Review+Create

Review + create tab

  1. On the Review + create tab, your configuration is validated. You can review the selections made in the previous screens.

    Resource Review+Create Tab
  2. After validation has succeeded and you’ve reviewed the terms, select Create for Azure to start the deployment.

    Resource Deployment
  3. After the deployment finishes, select the NGINX deployment to view information about the deployed resource.

    Resource Deployment Completed

Test your deployment

  1. To test your deployment, you can go to the IP address noted on the overview page. The default NGINX welcome screen should load.

    You will not see the default NGINX welcome screen if you unchecked “Apply default NGINX configuration” in the Networking Tab screen above. You can proceed with providing your own NGINX configuration as outlined in the NGINX configuration section.
    Test Deployment

What’s next

Assign Managed Identities