Merge pull request mendix#9760 from Nidhi251289/Portunus_7_15_0

Portunus 7.15.0 and MxOnAzure v1.4

Author: katarzyna-koltun-mx

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

@@ -0,0 +1,99 @@
+---
+title: "Backups for Mendix on Azure"
+url: /developerportal/deploy/mendix-on-azure/backups/
+weight: 13
+description: "Describes the backups functionality for apps running on Mendix on Azure."
+#To update these screenshots, you can log in with credentials detailed in How to Update Screenshots Using Team Apps.
+---
+
+## 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. 
+
+Backup snapshots contain both the database and file documents referred to in the database.
+
+## Enabling Backups
+
+If you would like to enable creating and restoring backups, select **Try new Backup and Restore** on the **Backups** page. 
+
+{{< figure src="/attachments/deployment/mx-azure/backups/backup-controls.png" alt="" >}}
+
+You must have permission to **Manage Apps Backups** for the namespace.
+
+## Creating a Backup {#creating-backup}
+
+1. In the [Apps](https://sprintr.home.mendix.com) page, select your app.
+2. In the navigation pane, click **Backups**.
+3. Select the environment for which you want to create a backup from the dropdown on the right. 
+
+{{% alert color="info" %}}
+You may not create backups while the environment status is any of the following:
+
+* Environment creation is in progress
+* Environment creation failed
+* A deployment package is being deployed in the environment
+* The environment is in transition state (runtime is processing)
+{{% /alert %}}
+
+4. Click **Create Backup**. 
+5. To check the status of the backup, see the **Status** column. 
+
+{{% alert color="info" %}}
+If you want to restart your environment after creating a backup archive, wait until the backup completes. Tables are locked while the database is in the process of creating a backup, so you may receive a timeout error if you try to start your environment while the backup is being created.
+{{% /alert %}}
+
+### Backup Details {#backups-details}
+
+You can view details of a backup by clicking **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) and then **Details**. The following details are displayed:
+
+| Backup Details | Description |
+| --- | --- |
+| **Status** | The status of the backup (**Processing**,**Failed**, or **Finished**) |
+| **Snapshot ID** | A unique identifier for the backup snapshot |
+| **Created on** | The creation date and time of the backup |
+| **Deployment Package** | The version of the deployment package used during backup creation |
+| **Comment** | A comment added to the backup |
+
+{{< figure src="/attachments/deployment/mx-azure/backups/backup-details.png" alt="Backup Details" max-width=60% class="no-border" >}}
+
+## Deleting a Backup {#backups-delete}
+
+To delete a backup snapshot, perform the following steps:
+
+1. Click **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) by a backup that you want to delete.
+2. Click **Delete**.
+
+The backup file is retained until you delete it from the portal. 
+
+## Restoring a Backup {#restore-backup}
+
+You can restore a backup that has been created in your Mendix on Azure environment. Backups from other cloud providers are not supported.
+
+{{% alert color="info" %}}
+You can only restore a backup if you have **Manage Apps Backups and Stop Apps** permissions in the respective namespace.
+{{% /alert %}}
+
+To restore a backup, perform the following steps:
+
+1. If your app is running, stop it by clicking **Stop Application**.
+2. Click **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) by a backup that you want to restore.
+
+    If you select a backup snapshot that was originally deployed with a different Mendix version, you will see a warning. You can still restore the data, but you must deploy the same model afterwards.
+   
+4. Click **Restore**.
+
+    {{< figure src="/attachments/deployment/mx-azure/backups/backups-restore.png" alt="Backup Restore" max-width=60% class="no-border" >}}
+
+5. Choose the destination environment to which you want to restore the backup snapshot. This allows you to, for example, restore a production environment backup to an acceptance environment.
+
+{{% alert color="info" %}}
+Do not update the environment while the restore process is in progress.
+{{% /alert %}}
+
+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**.
+
+## 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.
+* There is currently no API support for the backup and restore process.
+* The portal interface appears to allow restoring backups across different namespaces, but in reality this operation is unsupported. Backup and restore operations must be performed within the same namespace only.

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

@@ -17,8 +17,9 @@ Before starting the installation and implementation process, make sure that you
 
 * Obtain and configure a Microsoft Azure account. For more information, refer to the the Microsoft Azure documentation.
 * Purchase the Mendix on Azure offering in the [Azure Marketplace](https://azuremarketplace.microsoft.com/).
-* You must sign in to the Mendix on Azure portal with the same Azure account that was used to purchasing the offering. If you sign in with another account, the cluster is not visible for initialization.
+* You must buy cloud tokens (min. 14 cloud tokens per environment) to consume Mendix on Azure platform services. Cloud tokens are not utilized during an active trial.
 * You must log in to [Private Cloud page](https://privatecloud.mendixcloud.com/) before starting the installation process in the Mendix on Azure portal.
+* You must sign in to the Mendix on Azure portal with the same Azure account that was used to purchase the offering. If you sign in with another account, the cluster is not visible for initialization.
 
 {{< figure src="/attachments/deployment/mx-azure/coadmin-permission.png" class="no-border" >}}
 
@@ -55,15 +56,21 @@ To create a cluster for your Mendix on Azure app, perform the following steps:
 
 7. In the **Actions** column, click the icon, and then select **Initialize**. 
 
-    The preflight check launches to verify that the required resources can be registered in the cluster. Mendix apps are hosted with virtual images, so the preflight check determines whether the cluster contains the required type of virtual image. To view a list of the required resource providers, hover your cursor over the **Information** icon. If required, you can register any missing providers in the **Resource providers** section of the Microsoft Azure portal.
+    The preflight check launches to verify that the required resources can be registered in the cluster. The check also validates if there are valid (trial) service entitlements for Mendix on Azure assigned to your company, or sufficient cloud tokens to initialise the cluster. Finally, the preflight checks validates if the Azure account used for the initialization has the Owner role.
+
+   Mendix apps are hosted with virtual machines, so the preflight check determines whether the cluster contains the required type of virtual machine. To view a list of the required resource providers, hover your cursor over the **Information** icon. If required, you can register any missing providers in the **Resource providers** section of the Microsoft Azure portal.
 
     {{< figure src="/attachments/deployment/mx-azure/preflight-check.png" class="no-border" >}}
 
-8. In the **Preflight Check** screen, click **Next** to be redirected to the **Provision** screen. When all preflight checks are passed, the status is displayed as **Done** in the **Preflight Check** section, as in the following figure:
+    If the number of cloud tokens is not sufficient, the following error message is shown:
+
+    {{< figure src="/attachments/deployment/mx-azure/clusterInitializeFailedQuota.png" class="no-border" >}}
+
+9. In the **Preflight Check** screen, click **Next** to be redirected to the **Provision** screen. When all preflight checks are passed, the status is displayed as **Done** in the **Preflight Check** section, as in the following figure:
 
     {{< figure src="/attachments/deployment/mx-azure/preflight-check-successful.png" class="no-border" >}}
 
-9. 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.
+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:
 
@@ -73,16 +80,19 @@ To create a cluster for your Mendix on Azure app, perform the following steps:
     * 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
 
     {{% 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 %}}
+
     {{< figure src="/attachments/deployment/mx-azure/provision-additional-option.png" class="no-border" >}}
 
 11. In the **Review & Initialize** screen, review the information and click **Initialize**.
 
     {{< figure src="/attachments/deployment/mx-azure/initializeCluster.png" class="no-border" >}}
 
-    The initialization process takes approximately 15 minutes. It creates a resource group in the managed app that you created in step 3 above as shwon below:
+    The initialization process takes approximately 15 minutes. It creates a resource group in the managed app that you created in step 3 above as shown below:
 
     {{< figure src="/attachments/deployment/mx-azure/resourceGroup.png" class="no-border" >}}
 
@@ -114,12 +124,13 @@ If required, you can change the following options for your cluster. The **Edit**
 * AKS node size
 * VM type
 * Load balancer type
+* Managed Grafana
 * Postgres compute SKU
 * Postgres Performance tier for storage IOPS
 * Postgres Compute tier
 * Postgres Compute size
 
-    {{< figure src="/attachments/deployment/mx-azure/editClusterPage.png" class="no-border" >}}
+{{< figure src="/attachments/deployment/mx-azure/editClusterPage.png" class="no-border" >}}
 
 ## Enabling Connections Between Different Azure Resource Groups
 
@@ -227,7 +238,15 @@ To enable private endpoints for your Mendix on Azure app, perform the following
 
 ## Deploying an App to an Azure Cluster
 
-After creating your cluster in Microsoft Azure, you can deploy now deploy your applications to the cluster. The deployment process is the same as with Mendix for Private Cloud. For more information, see [Deploying a Mendix App to a Private Cloud Cluster](/developerportal/deploy/private-cloud-deploy/).
+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 for Private Cloud. 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 Private Cloud 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
+
+For more information about backing up and restoring Mendix on Azure environments, see [Backups in Mendix on Azure](/developerportal/deploy/mendix-on-azure/backups/).
 
 ## Adding a New Cluster Manager
 
@@ -236,3 +255,4 @@ Once the cluster is successfully created and initialized in the Mendix on the Az
 After being added, the new cluster manager has the ability to view and manage the cluster within the Mendix on the Azure portal. They can also access and update the support ticket associated with the cluster in the Mendix on Azure portal. However, the newly added cluster manager does not have access to the Zendesk ticket linked to the cluster's support ticket.  
 
 If a cluster manager is deleted, they can no longer view the associated cluster or its support ticket in the Mendix on Azure portal.
+

content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-global-operator.md

@@ -175,6 +175,10 @@ Licenses imported in the PCLM Server appear in the PCLM Statistics section of th
 
 Claimed licenses are visible in the PCLM Statistics section of the Managed namespace.
 
+### Offline License and Subscription Secret
+
+For Global operator, the Runtime and Operator licenses must be applied to all the managed namespaces separately. 
+
 ## Upgrading Managed Namespaces
 
 When you [upgrade](/developerportal/deploy/private-cloud-upgrade-guide/#upgrade-cluster) the Global Operator main namespace, the managed namespaces within the global operator namespace are also automatically upgraded.

content/en/docs/deployment/private-cloud/private-cloud-data-transfer.md

@@ -7,7 +7,7 @@ weight: 60
 ---
 ## Introduction
 
-{{% alert color="warning" %}}This feature is currently in preview mode - to collect feedback about the UX and features which should be added to the final version.{{% /alert %}}
+{{% alert color="warning" %}}This tool is provided as-is, and no additional features or enhancements will be implemented in the future. {{% /alert %}}
 
 The Private Cloud data migration tool allows you to:
 

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: July 3, 2025
+
+* Mendix on Azure users can now create and restore environment backups through Private Cloud Portal. 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 cluster initialization and environment creation in Mendix on Azure, except when a trial is active. The preflight check now validates if you have sufficient valid cloud tokens.
+* The Mendix on Azure portal is now available in Japanese and Korean, enhancing user experience for native speakers. Language preferences can be adjusted in the **Work environment** tab under **Preferences**.
+* We have fixed a portal issue where error messages were incorrectly displayed despite successful resource provisioning.
+* We have made improvements to the handling of cluster deployment retries.
+* We have added the option to enable managed Grafana with private access to the **Initialize** and **Edit** steps for the cluster.
+* The preflight check can now validate that the Azure account used to initialize the cluster has an Owner role assigned on the target subscription.
+
 ### Release date: May 29, 2025
 
 * We have strengthened the preflight check process to deliver a better user experience.

content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md

@@ -12,6 +12,17 @@ For information on the current status of deployment to Mendix for Private Cloud
 
 ## 2025
 
+### July 3, 2025
+
+#### Portal Improvements
+
+* We have fixed an issue where the Cluster Manager was unable to delete namespaces which were disconnected or pending installation.
+* PCLM releases are now displayed in descending order.
+
+#### Deploy API
+* We have fixed the issue where users other than the Technical Contact were unable to update the environment by using the Update environment API. (Ticket #250927)
+* We have improved the logging for the Deploy API when a JA exception occurs while reading the certificate content.
+
 ### June 25, 2025
 
 #### Mendix Operator v2.22.0 {#2.22.0}