From 32fe3418f9961fde5b1a3d49bf1a9b3e4e689d01 Mon Sep 17 00:00:00 2001 From: Ashwini Shinde Date: Tue, 29 Sep 2026 15:30:09 +0530 Subject: [PATCH 1/2] Add Known limitation of browser while accessing go to ticket --- content/en/docs/deployment/mx-azure/mx-azure-support.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/en/docs/deployment/mx-azure/mx-azure-support.md b/content/en/docs/deployment/mx-azure/mx-azure-support.md index 3f34e647453..b1054291ab2 100644 --- a/content/en/docs/deployment/mx-azure/mx-azure-support.md +++ b/content/en/docs/deployment/mx-azure/mx-azure-support.md @@ -240,3 +240,4 @@ Customers can completely off-board from the service by deleting the Managed Appl * Downtime or issues with Mendix on Kubernetes may affect Mendix on Azure availability (for example, cluster creation may not be possible). * [Remote microflow debugging](/refguide/debug-microflows-remotely/) is not currently available for Mendix on Azure, because the remote debugger does not support single-instance apps. This issue will be resolved in a future release. * Azure Confidential Compute VM sizes (for example, the DCasv5, DCxeds_v6, and ECxeds families) are not supported for the AKS node pool. Deployment fails when one of these sizes is selected, and the environment cannot be recovered. It must be deleted and redeployed with a standard VM size, for example `Standard_B4als_v2`. +* In some browsers, clicking `Go to Ticket` on the Support Center page of the Mendix on Azure Portal might not redirect you to your Zendesk ticket. If this happens, use Google Chrome instead. \ No newline at end of file From 4359d8d0042f544bbb2e78cd308d187ebba69a60 Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Wed, 30 Sep 2026 09:36:01 +0200 Subject: [PATCH 2/2] Update mx-azure-support.md --- content/en/docs/deployment/mx-azure/mx-azure-support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/deployment/mx-azure/mx-azure-support.md b/content/en/docs/deployment/mx-azure/mx-azure-support.md index b1054291ab2..982089e34fe 100644 --- a/content/en/docs/deployment/mx-azure/mx-azure-support.md +++ b/content/en/docs/deployment/mx-azure/mx-azure-support.md @@ -240,4 +240,4 @@ Customers can completely off-board from the service by deleting the Managed Appl * Downtime or issues with Mendix on Kubernetes may affect Mendix on Azure availability (for example, cluster creation may not be possible). * [Remote microflow debugging](/refguide/debug-microflows-remotely/) is not currently available for Mendix on Azure, because the remote debugger does not support single-instance apps. This issue will be resolved in a future release. * Azure Confidential Compute VM sizes (for example, the DCasv5, DCxeds_v6, and ECxeds families) are not supported for the AKS node pool. Deployment fails when one of these sizes is selected, and the environment cannot be recovered. It must be deleted and redeployed with a standard VM size, for example `Standard_B4als_v2`. -* In some browsers, clicking `Go to Ticket` on the Support Center page of the Mendix on Azure Portal might not redirect you to your Zendesk ticket. If this happens, use Google Chrome instead. \ No newline at end of file +* In some browsers, clicking **Go to Ticket** on the Support Center page of the Mendix on Azure Portal might not redirect you to your Zendesk ticket. If this happens, use Google Chrome instead.