NLB-7247: Update changelog with v3 plan and plan migration #1476
+61
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
arpith-f5
reviewed
Nov 24, 2025
|
|
||
| To review older entries, visit the [Changelog archive]({{< ref "/nginxaas-azure/changelog/archive" >}}) section. | ||
|
|
||
| ## December 13, 2025 |
|
Proposal looks good to me |
russokj
reviewed
Nov 25, 2025
content/nginxaas-azure/billing/change-plan/migrate-from-standardv2.md
Outdated
Show resolved
Hide resolved
russokj
reviewed
Nov 25, 2025
content/nginxaas-azure/billing/change-plan/migrate-from-standardv2.md
Outdated
Show resolved
Hide resolved
…s for standardv3 plan
…s for standardv3 plan
JTorreG
reviewed
Dec 8, 2025
content/nginxaas-azure/billing/change-plan/migrate-from-standardv2.md
Outdated
Show resolved
Hide resolved
JTorreG
reviewed
Dec 8, 2025
content/nginxaas-azure/billing/change-plan/migrate-from-standardv2.md
Outdated
Show resolved
Hide resolved
JTorreG
reviewed
Dec 8, 2025
content/nginxaas-azure/billing/change-plan/migrate-from-standardv2.md
Outdated
Show resolved
Hide resolved
JTorreG
reviewed
Dec 8, 2025
content/nginxaas-azure/billing/change-plan/migrate-from-standardv2.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com>
arpith-f5
reviewed
Dec 15, 2025
| The Standard V3 plan is an upgraded, purpose-built solution for modern enterprises looking to simplify application traffic management and scale workloads effortlessly. The Standard V3 pricing model is designed to optimize efficiency and transparency: customers benefit from an affordable fixed price per deployment ($0.25 USD/hour) that covers baseline overhead, while NCU usage ($0.008 USD/hour/unit) and data processing ($0.005 USD/GB) allow costs to scale precisely with demand. | ||
|
|
||
| {{< call-out "note" >}} | ||
| We currently only support in-place migration from Standard V2 plan to the Standard V3 plan and from Standard to Standard V3 plan. You cannot update your Basic plan deployments to Standard V3 plan using this guide. |
Contributor
There was a problem hiding this comment.
what about basic -> developer. instead of creating a separate page for developer. Make this page more generic and then list the possible transitions that are supported
JTorreG
approved these changes
Dec 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
standardv3planstandardv2tostandardv3Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩