Skip to content
2 changes: 2 additions & 0 deletions content/en/docs/deployment/mx-azure/configuration/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -116,6 +116,8 @@ Additional cluster managers have the same configuration privileges as the origin
Before adding a cluster manager, ensure the invited user signs in to the Mendix on Azure portal prior to accepting the invitation. Otherwise, the invitation might show as accepted, but the user will not have access to any Mendix on Azure resources.
{{% /alert %}}

For detailed information about cluster visibility and permission requirements for viewing and editing clusters, see [Cluster Visibility and Permissions](/developerportal/deploy/mendix-on-azure/cluster-visibility/).

## Configuration Assistance Available by Submitting a Support Ticket through the Mendix on Azure Portal

Certain configuration changes require Mendix intervention and can only be performed by submitting a support ticket through the Mendix on Azure portal:
Expand Down
63 changes: 63 additions & 0 deletions content/en/docs/deployment/mx-azure/mx-azure-cluster-visibility.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
title: "Cluster Visibility and Permissions"
url: /developerportal/deploy/mendix-on-azure/cluster-visibility/
description: "Describes how cluster visibility and editing permissions work in Mendix for Private Cloud on Azure based on user roles and Azure RBAC permissions."
weight: 8
---

## Introduction

The **Cluster Overview** page in Mendix on Azure displays clusters based on your assigned role and Azure permissions. This document explains how cluster visibility and editing permissions work.

## Overview

Below is a short summary of the key aspects of cluster visibility. For more information, refer to the following sections.

* Visibility - All cluster namespace members can view initialized clusters to facilitate support and monitoring.
* Security - Only Cluster Managers with appropriate Azure RBAC roles (Owner or Contributor) can modify cluster settings.
* Separation of Concerns:
* Initialized clusters are visible to all namespace members regardless of Azure RBAC.
* Editing capabilities require both Cluster Manager role or Azure Owner or Contributor permissions.

## Cluster Visibility

### All Users

All users who are members of a Mendix cluster namespace can see initialized clusters in the cluster overview page, regardless of their Azure RBAC permissions. This allows all users to view cluster details and submit support tickets.

Clusters that are ready to initialize (that is, not yet initialized) follow the standard Azure RBAC visibility rules.

### Cluster Manager Role

Users with the Cluster Manager role have the same visibility as other users for initialized clusters, as well as the following:

* Access to view and potentially edit cluster configuration (depending on Azure RBAC permissions)
* Ability to see clusters awaiting initialization (based on Azure RBAC permissions)

## Editing Cluster Settings

### Permission Requirements

To edit cluster settings, a user must have the following roles:

* In Mendix - Cluster Manager
* In Azure RBAC - Azure Owner or Azure Contributor

### Permission Scenarios

| User Type | Azure RBAC | Can View Initialized Clusters | Can Edit Clusters |
| --- | --- | --- | --- |
| Any cluster namespace member | Any | Yes | No |
| Cluster Manager | Reader | Yes | No |
| Cluster Manager | Owner/Contributor | Yes | Yes |

### Error Handling

If a Cluster Manager attempts to edit cluster settings without the required Azure Owner or Contributor role, an error message like the following is displayed, explaining that additional Azure permissions are required:

*The user must be cluster manager to edit the Azure environment.You are not cluster manager of this Azure environment.*

## Read More

* [Configuring Mendix on Azure](/developerportal/deploy/mendix-on-azure/configuration/) – Configuration options available through the Mendix on Azure Portal
* [Support for Mendix on Azure](/developerportal/deploy/mendix-on-azure/support/) – Support model and shared responsibility
4 changes: 4 additions & 0 deletions content/en/docs/deployment/mx-azure/mx-azure-deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -79,6 +79,10 @@ To deploy the solution, perform the following steps:

7. Identify the entry belonging to the Managed Application you deployed in previous steps. In the **Actions** column, click the dropdown menu icon, and then select **Initialize**.

{{% alert color="info" %}}
For information about how cluster visibility and editing permissions work based on user roles and Azure RBAC, see [Cluster Visibility and Permissions](/developerportal/deploy/mendix-on-azure/cluster-visibility/).
{{% /alert %}}

The preflight check launches to verify the conditions are in place to successfully initialize a Mendix on Azure cluster.

{{< figure src="/attachments/deployment/mx-azure/preflight-check.png" class="no-border" >}}
Expand Down
10 changes: 10 additions & 0 deletions content/en/docs/releasenotes/deployment/mendix-azure.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,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: May 7, 2026

* We have fixed an issue where an unavailable VM could be selected.
* We have added a cost calculator link to the Cluster Deployment and Edit flows.
* PostgreSQL replicas can no longer be scaled when Read Replica is enabled.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Nidhi251289 @mxashokkhedkar what is the reason for this change? Is it for performance reasons?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was causing an error during deployment; the customer reported this, so we put this condition now, but both can be performed together for the first time when the read replica is disabled/ cluster initlisation/edit flow.

* We have extended the quota check to warn users when the available quota for the selected VM type, including family and regional, is less than 8.
* Initialized clusters are now visible to cluster members regardless of Azure RBAC.
* Only Cluster Managers with the Azure Owner or Contributor roles can now edit cluster settings.
* We have added a warning to inform users about the implications of enabling network-isolated cluster and internal load balancers.

## Release date: February 26, 2026

* We have improved the handling of PostgreSQL HA unavailability issues in certain Azure regions to prevent failed Spacelift Stack runs when infrastructure redundancy is enabled.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,12 @@ For information on the current status of deployment to Mendix on Kubernetes and

## 2026

### May 7, 2026

#### Portal Improvements

* We have fixed an issue where an error pop-up would appear when opening Grafana for Logs and Metrics. (Ticket 277132)

### May 1, 2026

#### Mendix Ops CLI
Expand Down
Binary file modified static/attachments/deployment/mx-azure/initializeCluster.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified static/attachments/deployment/mx-azure/preflight-check.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.