docs: Nginxaas/add comparison link

[JTorreG]

Background

The current Feature comparison page includes a side-by-side table comparing NGINX Open Source (NOSS), NGINX Plus (N+), and NGINX as a Service for Azure (N4A).

Although the table was meant to highlight N4A features, it became the place customers went to compare NOSS and N+, whether they were looking for N4A information or not.

Marketing is publishing a dedicated NOSS vs. N+ comparison doc, which will serve as the source of truth for that comparison. To align with this, the N4A page should focus only on N4A features.

---

Acceptance Criteria

1. Remove the NGINX Open Source (NOSS) and NGINX Plus (N+) columns from the feature comparison table.
2. Convert the NGINX as a Service for Azure (N4A) features into a bulleted list, preserving all current feature details.
3. Add a cross-reference link to the Marketing-owned NOSS vs. N+ comparison doc. Use a placeholder link until Marketing provides the final URL.
4. Confirm formatting and style follow the NGINX Style Guide for lists, headings, and product naming conventions.
5. Verify the page builds and publishes cleanly: no broken links, missing features, or layout issues.

---

Checklist

Before sharing this pull request, I completed the following checklist:

• I read the Contributing guidelines
• My branch adheres to the Git conventions
• My content changes adhere to the F5 NGINX Documentation style guide
• If my changes involve potentially sensitive information¹, I have assessed the possible impact
• I have waited to ensure my changes pass tests, and addressed any discovered issues

Footnotes

1. Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

[github-actions]

✅ Deploy Preview will be available once build job completes!

Name	Link
😎 Deploy Preview	https://frontdoor-test-docs.nginx.com/previews/docs/1057/

---

[mjang]

Based on spot checks, this is a faithful representation of the F5 NGINXaaS for Azure column in the current version of this page.

Since this is no longer a feature comparison (we're linking to the new feature comparison), the title change is appropriate.

[russokj]

I think in the offline slack thread, we'd like to see the table. It's a much clearer and concise way to see what NGINXaaS is supporting from the current NGINX+ release.

[mjang]

I think in the offline slack thread, we'd like to see the table. It's a much clearer and concise way to see what NGINXaaS is supporting from the current NGINX+ release.

My concerns:

• We would need to ensure consistency with the coming page that compares only NGINX OSS and NGINX Plus
  • That process will take time
  • I've set up an "internal" issue to discuss further updates
• Even if the two sources of truth are totally consistent, I predict that readers are going to be confused

IMO, it's important to have a "single source of truth" for these comparisons.

[russokj]

NGINXaaS does not need to be compared with NOSS. We run only N+. Our customers know which version of N+ we are running and all they care about is what features of N+ we support. Having this as a table in our docs is the most convenient and the most accurate for our N4A customers.

[mjang]

NGINXaaS does not need to be compared with NOSS. We run only N+. Our customers know which version of N+ we are running and all they care about is what features of N+ we support. Having this as a table in our docs is the most convenient and the most accurate for our N4A customers.

@russokj we welcome your suggested changes (or an alternative PR)

[travisamartin]

I added background and acceptance criteria to this pull request so the context is clear.

Going forward, let’s handle doc requests through GitHub issues with acceptance criteria. That way, requirements don’t shift, and we can prioritize and manage requests more effectively.