release notes and documentation for networking added

content/en/docs/deployment/mx-azure/_index.md

@@ -7,8 +7,6 @@ no_list: false
 description_list: true
 ---
 
-{{% alert color="info" %}} This feature is currently available to participating customers. For more information, contact your Customer Success Manager. {{% /alert %}}
-
 ## Introduction
 
 Mendix on Azure provides a simplified, integrated way to deploy Mendix applications to a Microsoft Azure environment. With this solution, users are empowered to deploy their Mendix applications in Azure environments without the need for intricate infrastructure setup in cloud services. They can also seamlessly manage infrastructure services through an intuitive user interface. No matter their IT skills, users can realize their project value quickly and securely with Azure.

content/en/docs/deployment/mx-azure/backups.md

@@ -8,7 +8,7 @@ description: "Describes the backups functionality for apps running on Mendix on
 
 ## Introduction
 
-For apps running in Mendix on Azure, the [Backups](/developerportal/operate/backups/) functionality enables you to create and restore database or file document backups. Other backup functionalities, such as uploading and downloading backup snapshots, or scheduling nightly backups, are not yet supported for Mendix on Azure. 
+For apps running in Mendix on Azure, the [Backups](/developerportal/operate/backups/) functionality enables you to create/restore database or file document backups. Other backup functionalities are also supported for Mendix on Azure environments. This includes functionalities such as uploading and downloading backup snapshots and scheduling nightly, weekly, or monthly backups.
 
 Backup snapshots contain both the database and file documents referred to in the database.
 
@@ -92,6 +92,53 @@ Do not update the environment while the restore process is in progress.
 
 Your environment details page displays a message while the backup is being restored. After the restore process is completed, the environment activity log shows the status as **FINISHED**. If a backup restore fails, the backup activity log of your environment shows the status as **FAILED**.
 
+## Uploading a Backup {#upload-backup}
+
+To upload a backup, click **Upload Backup**, and then select the backup archive which you want to upload. For information on downloading backup archives, see [Downloading a Backup](#download-backup).
+
+You can upload archives containing a Full Snapshot.
+
+Uploading a backup creates a new backup item in your backup list. You can then restore the new backup item by following the regular restore process,  as described in [Restoring a Backup](#restore-backup). This ensures less downtime for your application.
+
+## Downloading a Backup {#download-backup}
+
+To download a backup, click **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) > **Download** on the backup which you want to download.
+
+You can download archives containing a Full Snapshot.
+
+{{% alert color="info" %}}
+Because the download archive is generated on request, it is not possible to estimate the file size before requesting a download.
+{{% /alert %}}
+
+To download a backup of an app, follow these steps:
+
+1. Go to [Apps](https://sprintr.home.mendix.com) and open your app.
+2. In the [navigation pane](/developerportal/#navigation-pane), click **Backups**.
+3. On the backup you want to download, click **More Options** ({{% icon name="three-dots-menu-horizontal" %}}).
+4. Select **Download** from the drop-down list.
+5. Click **Start** to submit a backup download request. 
+6. After the download request is processed and the backup is completed, click on the **Download** button to retrieve the backup file.
+7. You can click on the **Show URL** button to view/copy the download link.
+
+## Nightly/Weekly/Monthly Backups
+
+Backups are created and retained as follows:
+
+| Frequency | Timing | Type | Retention Period |
+| --- | --- | --- | --- |
+| Nightly | Each night | Automatic | 14 days (counting from yesterday) |
+| Weekly | Each Sunday | Automatic | Three months(counting from yesterday) |
+| Monthly | First Sunday of each month | Automatic | One year(1st Sunday of each month) |
+| On demand | On demand | Manual (user initiated) | 14 days (counting from yesterday) |
+
+Each backup is automatically deleted when its retention period is over, but you can always manually delete it before then. By default, backups are retained for exactly the specified period; for example, a weekly backup created at on October 22nd expires at January 22nd. If you want to keep a backup for longer than scheduled, you can download the backup to your computer.
+
+{{% alert color="info" %}}Automatic backups are only created when the app is deployed.{{% /alert %}}
+
+### Notes on Retention
+
+The monthly backup occurs on the first Sunday of the month. If the first nightly backup takes place after the first Sunday in the month, then there is no monthly backup retained for that month. In this case, you can download a copy of a nightly or weekly backup if you need to retain a backup for longer than three months.
+
 ## Known Limitations
 
 * If a backup restore fails, all data that was restored until the point of failure is present in the database. This leaves the database only partially restored.

content/en/docs/deployment/mx-azure/mx-azure-getting-started.md

@@ -5,8 +5,6 @@ description: "Documents the pre-implementation tasks for Mendix on Azure."
 weight: 10
 ---
 
-{{% alert color="info" %}} This feature is currently available to participating customers. For more information, contact your Customer Success Manager. {{% /alert %}}
-
 ## Introduction
 
 Before you can deploy your Mendix app on Azure, you must plan and complete a number of pre-implementation tasks.

content/en/docs/deployment/mx-azure/mx-azure-installation.md

@@ -5,8 +5,6 @@ description: "Documents the initial configuration tasks for Mendix on Azure."
 weight: 20
 ---
 
-{{% alert color="info" %}} This feature is currently available to participating customers. For more information, contact your Customer Success Manager. {{% /alert %}}
-
 ## Introduction
 
 To get started with your Mendix on Azure deployment, you must first register your Microsoft Azure cloud cluster in the Mendix Portal. This will provide you with the resources required to deploy the Mendix Operator and host your Mendix app in an Azure deployment.
@@ -65,19 +63,26 @@ To create a cluster for your Mendix on Azure app, perform the following steps:
 
     {{< figure src="/attachments/deployment/mx-azure/preflight-check-successful.png" class="no-border" >}}
 
+    The platform account check is used to validate that only one platform account is associated with the customer ID.
+
 10. In the **Provision** screen, add the custom tags if required and review the information in the **Advanced Options** section. If required, adjust any settings as needed. Note that selecting higher service tiers will also incur higher costs.
 
     You can update the following advanced options:
 
     * AKS Service Tier
-    * AKS Node Size
-    * VM Type
+    * AKS Node VM Size
+    * AKS Maximum Node Count
     * Load Balancer Type
-    * Postgres Flexible Server - Under this, you can update Compute Tier, Compute Size and Storage Performance Tier.
-    * AKS Node IP Address 
-    * Managed Grafana
-    * Enable Read Replica
-
+    * AKS Node CIDR IP Range
+    * AKS Network Isolated Cluster
+    * Managed Grafana    
+    * Postgres Flexible Server:
+
+        * Enable Read Replica
+        * Compute Tier
+        * Compute Size
+        * Storage Performance Tier
+
     {{% alert color="info" %}}If you plan to use [virtual network peering](#network-peering), you must set the **Load Balancer Type** to **Private (Internal)**.{{% /alert %}}
 
     {{% alert color="info" %}}If **Managed Grafana** is set to **False**, private access to a Grafana dashboard is required. Make sure that the required network is set up to accomodate private access.{{% /alert %}}
@@ -238,9 +243,6 @@ To enable private endpoints for your Mendix on Azure app, perform the following
 
 After creating your cluster in Microsoft Azure, you can now deploy your applications to the cluster. The deployment process is the same as with Mendix on Kubernetes. However, in order to use the Mendix on Azure Platform service, you need to have a minimum of 14 cloud tokens to create an environment. For more information, see [Deploying a Mendix App to a Mendix on Kubernetes Cluster](/developerportal/deploy/private-cloud-deploy/). 
 
-If the number of cloud tokens is insufficient, the following error message is shown:
-
-{{< figure src="/attachments/deployment/mx-azure/envCreationFailedQuota.png" class="no-border" >}}
 
 ## Backing up and Restoring Eenvironments
 

content/en/docs/releasenotes/deployment/mendix-azure.md

@@ -12,6 +12,16 @@ These release notes cover changes to deployment to [Mendix on Azure](/developerp
 
 For information on the current status of Mendix deployment, see [Mendix Status](https://status.mendix.com/).
 
+### Release date: October 23, 2025 - [General Availability (GA) Release](/releasenotes/release-status/#general-availability)
+
+* In order to minimize the risk of security breaches and networking issues, we have added a new **Enable AKS Network Isolation** feature when creating new clusters. Please note that this feature can be enabled in the Initialize cluster and Edit cluster flow. However, once enabled in Initialize flow, it cannot be disabled in the Edit Cluster flow.
+* We have improved the log level handling in the Grafana dashboard. The logs are now available in JSON format.
+* We have fixed the issue where the cluster tags were not added to the read replicas database.
+* We have added a new preflight check in Cluster Initialization flow to validate that only one platform account should be used to initialize the cluster.
+* Mendix on Azure users can now upload and download environment backups through Mendix on Kubernetes Portal. For more information, see [Backups in Mendix on Azure](/developerportal/deploy/mendix-on-azure/backups/).
+* We have added a new feature which performs automatic nightly, weekly, or monthly backups of the environment. For more information, see [Backups in Mendix on Azure](/developerportal/deploy/mendix-on-azure/backups/).
+* [Cloud tokens](/control-center/cloud-tokens//) are now required for environment creation in Mendix on Azure after the trial period (120 days).
+
 ### Release date: October 16, 2025
 
 * After being added to a [Mendix on Azure](/developerportal/deploy/mendix-on-azure/) cluster in the Mendix on Kubernetes Portal, a [cluster manager](/developerportal/deploy/mendix-on-azure/installation/#adding-a-new-cluster-manager) can now view and edit the cluster from the Mendix on Azure Portal.