mendix · oenerayca · Jun 26, 2025 · Jun 27, 2025 · Jun 30, 2025 · Jun 30, 2025
diff --git a/content/en/docs/apidocs-mxsdk/apidocs/deployment/pipelines-api.md b/content/en/docs/apidocs-mxsdk/apidocs/deployment/pipelines-api.md
@@ -3,7 +3,6 @@ title: "Pipelines API"
 url: /apidocs-mxsdk/apidocs/pipelines-api/
 type: swagger
 description: "The Pipelines API sends requests to pipelines."
-restapi: true
 weight: 85
 ---
 

diff --git a/content/en/docs/catalog/_index.md b/content/en/docs/catalog/_index.md
@@ -14,6 +14,10 @@ aliases:
     - /data-hub/data-hub-catalog/
 ---
 
+{{% alert color="info" %}}
+The Mendix Portal is the online platform of Mendix. It includes [Apps](/developerportal/), [Control Center](/control-center/), [Community](/community-tools/), [Marketplace](/appstore/), Catalog, and [Mendix Support](/support/).
+{{% /alert %}}
+
 ## Introduction
 
 The [Catalog](https://catalog.mendix.com) is a development tool provided in Mendix Cloud. 

diff --git a/content/en/docs/community-tools/_index.md b/content/en/docs/community-tools/_index.md
@@ -12,6 +12,10 @@ aliases:
     - /developerportal/community-tools/
 ---
 
+{{% alert color="info" %}}
+The Mendix Portal is the online platform of Mendix. It includes [Apps](/developerportal/), [Control Center](/control-center/), Community, [Marketplace](/appstore/), [Catalog](/catalog/), and [Mendix Support](/support/).
+{{% /alert %}}
+
 ## Introduction
 
 Visit the [Mendix Community](https://community.mendix.com) for all the information you need as a member of the Mendix community. Each section of the site represents a community tool that is continuously updated with new content and exciting developments. Furthermore, the content on the site is not only created for the Mendix community, it is created by the Mendix community!

diff --git a/content/en/docs/control-center/_index.md b/content/en/docs/control-center/_index.md
@@ -12,6 +12,10 @@ aliases:
     - /developerportal/control-center
 ---
 
+{{% alert color="info" %}}
+The Mendix Portal is the online platform of Mendix. It includes [Apps](/developerportal/), Control Center, [Community](/community-tools/), [Marketplace](/appstore/), [Catalog](/catalog/), and [Mendix Support](/support/).
+{{% /alert %}}
+
 ## Introduction
 
 When you sign up on the Mendix Platform, you are able to create new apps, invite other users to your app teams, deploy your apps, and invite app end-users to give feedback, among many other activities. Insights into these company activities are provided in Control Center in one central overview. These insights will help you to be in control and remain aware of everything happening within the Mendix landscape of your company.

diff --git a/content/en/docs/control-center/content-curation/portfolios.md b/content/en/docs/control-center/content-curation/portfolios.md
@@ -130,7 +130,7 @@ On the **Privacy Requests** tab, you can decide whether a Mendix Admin needs to
 
 {{< figure src="/attachments/control-center/content-curation/portfolios/admin-curation-toggle.png" alt="Mendix Admins must approve changes to portfolio privacy settings" class="no-border" >}}
 
-The toggle is turned off by default. If the toggle is turned on, as a Mendix Admin, you automatically get a [notification](/portal/global-navigation/#notifications) whenever someone creates a restricted or open portfolio or changes the privacy settings of an existing portfolio. 
+The toggle is turned off by default. If the toggle is turned on, as a Mendix Admin, you automatically get a [notification](/developerportal/global-navigation/#notifications) whenever someone creates a restricted or open portfolio or changes the privacy settings of an existing portfolio. 
 
 On the **Privacy Requests** tab, you can view all the pending requests. You can approve or reject a request here. Every request contains the following items:
 

diff --git a/content/en/docs/deployment/mendix-cloud-deploy/mendix-cloud-request-headers.md b/content/en/docs/deployment/mendix-cloud-deploy/mendix-cloud-request-headers.md
@@ -18,18 +18,6 @@ Most of the request headers are added by the HTTP client (the web browser, for e
 
 Using custom Java code in the application, the full content of an incoming request can be inspected.
 
-Request header names are case-insensitive, as defined by [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). This means that headers such as `X-Header-Key`, `x-header-key`, and `X-HEADER-KEY` must be processed in the same way. 
-
-When processing request headers, Mendix recommends converting all request headers names to lowercase to account for case-insensitivity. For example:
-
-```bash
-toLowerCase($HeaderKey) = 'x-header-key'
-```
-
-This ensures consistent handling regardless of the casing used in incoming requests and supports compliance with HTTP standards.
-
-{{< figure src="/attachments/deployment/mendix-cloud-deploy/mendix-cloud-request-headers/tolowercase-header-name.png" alt="Lowercase Request Header Names" width=50%  >}}
-
 ### Usually Available Request Headers Set by the HTTP Client
 
 The following headers are usually set by the HTTP client. Mendix Cloud does not touch the value of these headers. This also means that they might not be available if the HTTP client does not set them.

diff --git a/content/en/docs/deployment/mendix-cloud-deploy/node-permissions.md b/content/en/docs/deployment/mendix-cloud-deploy/node-permissions.md
@@ -16,7 +16,7 @@ Team members who have a role with **Cloud Access** can view the permissions. For
 
 ## Viewing Your Nodes{#nodes}
 
-To find a list of all Mendix Cloud licensed nodes that you have access to, open the [Global Navigation menu](/portal/global-navigation/) and click **Deployment**.
+To find a list of all Mendix Cloud licensed nodes that you have access to, open the [Global Navigation menu](/developerportal/global-navigation/) and click **Deployment**.
 
 You will see a list of all your licensed nodes:
 

diff --git a/content/en/docs/deployment/mx-azure/backups.md b/content/en/docs/deployment/mx-azure/backups.md
diff --git a/content/en/docs/deployment/mx-azure/mx-azure-installation.md b/content/en/docs/deployment/mx-azure/mx-azure-installation.md
@@ -17,9 +17,8 @@ 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 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 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 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" >}}
 
@@ -56,21 +55,15 @@ 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. 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.
+    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.
 
     {{< figure src="/attachments/deployment/mx-azure/preflight-check.png" class="no-border" >}}
 
-    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:
+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:
 
     {{< figure src="/attachments/deployment/mx-azure/preflight-check-successful.png" class="no-border" >}}
 
-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.
+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.
 
     You can update the following advanced options:
 
@@ -80,19 +73,16 @@ 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 shown 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 shwon below:
 
     {{< figure src="/attachments/deployment/mx-azure/resourceGroup.png" class="no-border" >}}
 
@@ -124,13 +114,12 @@ 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
 
@@ -238,15 +227,7 @@ 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 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/).
+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/).
 
 ## Adding a New Cluster Manager
 
@@ -255,4 +236,3 @@ 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.
-
diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md
@@ -53,7 +53,7 @@ Should you consider using a connected environment, the following URLs should be
 
     {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/image4.png" class="no-border" >}}
 
-4. Open the [Global Navigation menu](/portal/global-navigation/) and select **Deployment**.
+4. Open the [Global Navigation menu](/developerportal/global-navigation/) and select **Deployment**.
 5. Select **Mendix for Private Cloud** from the top menu bar in the Mendix Portal.
 
     {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/cluster-manager.png" class="no-border" >}}

diff --git a/...deployment/private-cloud/private-cloud-cluster/private-cloud-global-operator.md b/...deployment/private-cloud/private-cloud-cluster/private-cloud-global-operator.md
@@ -175,10 +175,6 @@ 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.
diff --git a/...ployment/private-cloud/private-cloud-cluster/private-cloud-standard-operator.md b/...ployment/private-cloud/private-cloud-cluster/private-cloud-standard-operator.md
@@ -21,7 +21,7 @@ Before you can use the Mendix Operator in your namespace you need to install it
 
 If you are not already on the installation tab for your namespace, go to it by following these instructions:
 
-1. Go to the Cluster Manager page by opening the [Global Navigation Menu](/portal/global-navigation/), and then clicking **Deployment** > **Private Cloud**.
+1. Go to the Cluster Manager page by opening the [Global Navigation Menu](/developerportal/global-navigation/), and then clicking **Deployment** > **Private Cloud**.
 
     {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/cluster-manager.png" class="no-border" >}}
 

diff --git a/content/en/docs/deployment/private-cloud/private-cloud-data-transfer.md b/content/en/docs/deployment/private-cloud/private-cloud-data-transfer.md
@@ -7,7 +7,7 @@ weight: 60
 ---
 ## Introduction
 
-{{% alert color="warning" %}}This tool is provided as-is, and no additional features or enhancements will be implemented in the future. {{% /alert %}}
+{{% 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 %}}
 
 The Private Cloud data migration tool allows you to: