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..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,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.