Learn about the latest updates, new features, and resolved bugs in NGINX as a Service for Azure
March 16, 2023
- Deployment configuration now succeeds after adding a managed identity.
After adding a managed identity to a deployment, the deployment transitions from an Accepted state to a Succeeded state only after the operation to add the managed identity succeeds. The user can then proceed to configure the deployment.
February 21, 2023
auth_jwt_requireare now supported.
Refer to the
auth_jwt_require documentation for more information on using these directives.
- PKCS12 certificates may now be added to your NGINXaaS deployment.
Previously, NGINXaaS only accepted PEM formatted certificates. Now, both PEM and PKCS12 certificates are supported.
- State files may now be used with the
For information on storing the state of a key-value database with a state file, see
January 11, 2023
- NGINXaaS is generally available
We are pleased to announce the general availability of NGINX as a Service (NGINXaaS), a first-party-like experience as a service co-developed by Microsoft and NGINX and tightly integrated into the Azure ecosystem.
NGINXaaS, powered by NGINX Plus, is a fully managed service that removes the burden of deploying your own NGINX Plus cluster, installing libraries, upgrading, and managing it.
NGINXaaS simplifies the process of moving your existing NGINX configuration to the Azure cloud. Once your configurations are moved to Azure, securely manage SSL/TLS certificates and keys stored in Azure Key Vault and reference them within your NGINX configurations. You can watch your application’s traffic in real time with Azure monitoring and alerts, and scale your deployment to fit your needs, maximizing cost efficiency. You can create, update, and delete your NGINXaaS deployment via the Azure Resource Manager, the Azure SDK, CLI, and Terraform in addition to the Azure portal.
Our new “Standard” plan is ready for production workloads. If you have a deployment on the “Public Preview” plan, it will continue to work; however, we recommend you recreate it under the “Standard” plan. See Migrating from Public Preview for details.
To learn more, refer to the following NGINXaaS documentation:
- NGINXaaS for Azure overview
- NGINXaaS, NGINX Plus, and NGINX Open Source feature comparison
- NGINXaaS billing details
January 10, 2023
Special parameters in
geodirectives are now supported.
matchdirective is now supported.
December 14, 2022
- New customer deployments are now functional.
We have rolled out a fix that addresses the issue, and new customers or existing customers in a new region can create deployments.
December 7, 2022
- System Assigned Managed Identitiy can now be used with a deployment.
Users can now leverage System Assigned Managed Identities with their deployment. The lifecycle of the identity is tied to the lifecycle of the corresponding deployment. See Managed Identity Types for more information.
November 29, 2022
- Absolute paths may now be used with the
NGINXaaS for Azure has new restrictions on file paths for Auxiliary files (Certificate files, njs files, etc). See the NGINX Filesystem Restrictions table for more information. Existing configurations will not be affected unless they need to be updated.
November 22, 2022
Logging support is now available
Please visit the Logging Support documentation for more information on exporting NGINX logs with NGINXaaS for Azure.
NGINXaaS for Azure ARM API schema supports previously unused fields
November 14, 2022
- NGINX deployment can be configured to send metrics-based alerts.
November 7, 2022
- New deployments utilize Availability Zones to ensure data planes are highly available.
- Files containing sensitive data can be uploaded as a “Protected File”, see: NGINX Configuration
October 24, 2022
NGINXaaS for Azure is now generally available in more regions
NGINXaaS for Azure is now available in the following additional regions:
- West US 2
- East US
- Central US
- North Central US
See the Supported Regions documentation for the full list of supported regions.
October 11, 2022
Resolved known NJS filepath issues
Affecting new deployments only, two NJS files in different subdirectories may share the same filename. For example:
js_path "njs"; js_import d1 as d1/test.js; js_import d2 as d2/test.js;
October 5, 2022
Updated the error returned when a certificate cannot be applied to the NGINX Configuration
This change improves the readability of some errors that may be returned when a certificate cannot be applied.
September 22, 2022
NGINX configurations have default logging directives
error_logto NGINX configurations in preparation for upcoming logging features. Requires a config push to be applied.
Improved likelihood of deployment success
Improved performance and reliability of backend services
Fixed bug where NGINX version appeared empty
July 21, 2022
Basic caching is now supported
For more information on caching with NGINXaaS for Azure, please visit the Basic Caching documentation.
Rate Limiting is now supported
For information on rate limiting with NGINXaaS for Azure, please visit the Rate Limiting documentation.
May 24, 2022
Welcome to the NGINXaaS Public Preview
NGINXaaS for Azure is now available for public preview. Give it a try! If you find any issues please let us know by raising a support ticket.
Visit the Known issues section to learn about the issues present in this release.