From df18992b7260a0583a5b5ad44808b59adb2b08cf Mon Sep 17 00:00:00 2001 From: ClydeW Date: Fri, 12 Jun 2026 13:43:22 +0200 Subject: [PATCH] Remove PIM blocker from Mendix on Azure prerequisites MXFORAZURE-577: Remove outdated restriction stating that temporary elevated PIM access does not suffice for Owner role on target subscription. Testing has confirmed PIM-elevated accounts work correctly. --- content/en/docs/deployment/mx-azure/mx-azure-deploy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/deployment/mx-azure/mx-azure-deploy.md b/content/en/docs/deployment/mx-azure/mx-azure-deploy.md index 6613da3eb22..1a7a86dfb76 100644 --- a/content/en/docs/deployment/mx-azure/mx-azure-deploy.md +++ b/content/en/docs/deployment/mx-azure/mx-azure-deploy.md @@ -16,7 +16,7 @@ To deploy Mendix on Azure, make sure you have the following available: * A Mendix platform account * An Azure account with the following permissions: * Permission to grant admin consent on the Mendix on Azure portal app registration (e.g. Global Administrator in Entra ID) - * Owner role assigned on the target subscription (temporary elevated Privileged Identity Management - PIM - access does not suffice) + * Owner role assigned on the target subscription * In case you want to integrate the Mendix on Azure environment into your existing corporate network, be sure to consider the [network configuration options](/developerportal/deploy/mendix-on-azure/configuration/#networking-settings) that cannot be changed after initial environment deployment ## Deploying the Mendix on Azure offering from Azure Marketplace