Use of ActiveMQ Artemis in cluster is unsupported on Azure if automatic scale down of nodes is expected. For example when used in Azure VMSS (Azure Virtual Machine Scale Sets). The reason is ActiveMQ Artemis is not able to scale down in automatic way.

Use of transactions in Azure VMSS (Azure Virtual Machine Scale Sets) is unsupported as it's not waiting for all transactions to finish during scale down. This might cause data integrity issues and it's expected that VM with unfinished transactions will be restarted so all transactions can be recovered after restart.

Following features should be added into "Using JBoss EAP in Microsoft Azure" guide:
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.4/html-single/using_jboss_eap_in_microsoft_azure/index#unsupported_features