Skip to content

Added NGINXaaS for Azure doc on how to change from basic to standard plan #1359

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 23, 2025
Merged

Added NGINXaaS for Azure doc on how to change from basic to standard plan #1359

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions content/nginxaas-azure/billing/change-plan/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
title: Change pricing plan
weight: 300
url: /nginxaas/azure/billing/change-plan/
---
40 changes: 40 additions & 0 deletions content/nginxaas-azure/billing/change-plan/basic-to-standard.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
---
title: Change from basic plan to standard plan
weight: 200
toc: false
url: /nginxaas/azure/change-plan/basic-to-standard/
type:
- how-to
---

The basic plan is designed for early-stage trials and testing and is not intended for production use. If you are ready to create a standard plan deployment and wish to preserve the configuration of an existing basic plan deployment, you can [create a new deployment]({{< ref "/nginxaas-azure/getting-started/create-deployment.md">}}), selecting the latest standard pricing plan, and manually reapply your NGINX configuration and certificates. You can also follow the instructions below to recreate your deployment using an Azure Resource Manager (ARM) template.

## Prerequisites

- [Azure CLI Installation](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli)
- You must be logged in to your Azure account through the CLI. See [Azure CLI Authentication](https://learn.microsoft.com/en-us/cli/azure/authenticate-azure-cli)

## Recreate deployment using ARM template

To export an ARM template for an existing deployment:

1. Go to your existing NGINXaaS deployment.
1. Select **Export template** under **Automation** in the left menu.
1. Wait for the template to generate.
1. Select **Download**.
1. Decompress the template archive.
1. Open the `template.json` file and verify that the data in the template is correct.
1. In the `resources` section, change `sku.name` to `standardv2_Monthly`. This recreates the deployment as a standard plan deployment.
1. Delete the original basic plan deployment.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it necessary to do this step first? Won't the new deployment have a new IP address? I would think they'd want to change the DNS mapping first (which we can't be specific about) and then when they know it's rerouting traffic, they can delete the original basic plan deployment.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If they care that much about preserving existing traffic, then they can refer to the recreate deployment guide (which I reference in this page). My intention was to give users a quick and easy way to recreate the deployment. The order of the step is intentional. If they wish to preserve the backing resources, such as the deployment's frontend IP address, there would be conflicts if they did not delete the original deployment first. FYI this PR is now merged, so I'll need to open a new PR with any emendations we wish to make.

1. On the command line, run:

```shell
az deployment group create \
--subscription=<deployment subscription ID> \
--resource-group=<resource group name> \
--template-file=</path/to/template.json>
```

## Further reading

For further details on recreating a deployment, see our [guide]({{< ref "/nginxaas-azure/quickstart/recreate.md">}}).
4 changes: 2 additions & 2 deletions .../getting-started/migrate-from-standard.md → ...ling/change-plan/migrate-from-standard.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
---
title: Migrate from Standard to Standard V2
weight: 1000
weight: 100
toc: true
url: /nginxaas/azure/getting-started/migrate-from-standard/
url: /nginxaas/azure/billing/change-plan/migrate-from-standard/
type:
- how-to
---
Expand Down
8 changes: 2 additions & 6 deletions content/nginxaas-azure/changelog/changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,10 +68,8 @@ NGINXaaS now allows both precompiled and custom policies for F5 NGINX App Protec
protected-files: protected-1.conf,protected-2.conf
```


- To enhance security, the service principal used for Azure login prior to running the NGINXaaS for Azure Deployment Action now only requires the Contributor role at the scope of the NGINXaaS for Azure deployment. It no longer needs the Contributor role at the resource group level containing the deployment.


## May 22, 2025

- {{% icon-feature %}} **NGINXaaS for Azure now supports IPv6**
Expand All @@ -80,7 +78,6 @@ NGINXaaS now allows both precompiled and custom policies for F5 NGINX App Protec

If you plan to use an IPv6 IP address whether standalone or in dual-stack mode, ensure that the subnet used by NGINXaaS has both IPv4 and IPv6 address spaces included. For more information on creating a vnets and subnets with IPv6 address spaces, refer to [Add IPv6 to virtual Network](https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/add-dual-stack-ipv6-vm-portal?tabs=azureportal#add-ipv6-to-virtual-network)


- {{% icon-feature %}} **NGINXaaS is now running NGINX Plus Release 33 (R33) in the Stable Upgrade Channel**

NGINXaaS for Azure deployments using the **Stable** [Upgrade Channel]({{< ref "/nginxaas-azure/quickstart/upgrade-channels.md" >}}) have now been automatically upgraded to [NGINX Plus Release 33 (R33)]({{< ref "/nginx/releases.md#nginxplusrelease-33-r33" >}}). This upgrade also includes updates to the following NGINX Plus modules:
Expand Down Expand Up @@ -112,7 +109,6 @@ F5 WAF for NGINX is now generally available and is no longer a preview feature a

## March 31, 2025


- {{% icon-feature %}} **NGINXaaS for Azure is now generally available in more regions**

NGINXaaS for Azure is now available in the following additional regions:
Expand All @@ -132,7 +128,7 @@ See the [Supported Regions]({{< ref "/nginxaas-azure/overview/overview.md#suppor

- {{% icon-info %}} **Retirement of Standard Plan**

The `Standard` plan for NGINXaaS for Azure has been retired, and you can no longer use it to create new deployments. If you have a deployment running on the `Standard` plan, consider [migrating]({{< ref "/nginxaas-azure/getting-started/migrate-from-standard.md">}}) it to the [`Standard V2 plan`]({{< ref "/nginxaas-azure/billing/overview.md#standard-v2-plan" >}}) to access new features such as F5 WAF for NGINX and additional listen ports. Plan migration does not incur downtime.
The `Standard` plan for NGINXaaS for Azure has been retired and can no longer be used to create new deployments. If you have an existing deployment on the `Standard` plan, consider [migrating]({{< ref "/nginxaas-azure/billing/change-plan/migrate-from-standard.md">}}) to the [`Standard V2 plan`]({{< ref "/nginxaas-azure/billing/overview.md#standard-v2-plan" >}}) to access new features such as F5 WAF for NGINX and additional listen ports. Migrating your plan does not cause downtime.

## February 10, 2025

Expand All @@ -144,4 +140,4 @@ See the [Supported Regions]({{< ref "/nginxaas-azure/overview/overview.md#suppor

- {{< icon-feature >}} **In-place SKU Migration from Standard to Standard V2**

You can now migrate NGINXaaS for Azure from the Standard plan to the Standard V2 plan without redeploying. We recommend upgrading to the Standard V2 plan to access features like F5 WAF for NGINX and more listen ports. The Standard plan will be retired soon. For migration details, see [migrate from standard]({{< ref "/nginxaas-azure/getting-started/migrate-from-standard.md">}}).
You can now migrate NGINXaaS for Azure from the `Standard` plan to the `Standard V2` plan without redeploying. We recommend upgrading to the `Standard V2` plan to access features such as F5 WAF for NGINX and additional listen ports. The `Standard` plan will be retired soon. For migration steps, see [Migrate from Standard]({{< ref "/nginxaas-azure/billing/change-plan/migrate-from-standard.md">}}).