book: https://access.qa.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/single/using-jboss-eap-on-microsoft-azure/

Azure instances usually have two IP addresses: private and public. Private IP address is the address that EAP can bind to and which is visible from inside the cloud, public IP address is not configured on any interface on the instance itself, it is the IP address of the instance from outside the cloud. This means that for some subsystems, more configuration is required to work properly (subsystems affected: Remoting, Messaging, Web Services). The approach is the same as with EC2.

For EC2, the configuration is documented here (Messaging, Web Services):
https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/deploying-red-hat-jboss-enterprise-application-platform-on-amazon-ec2/#configuring_messaging_and_webservice_subsystem

and here's a jira for Remoting (usually used together with remote EJB invocations): https://issues.jboss.org/browse/JBEAP-6295

The Azure documentation should contain this information, or at least a link to it, as well. Even though it isn't Azure-specific (or even cloud-specific), this configuration will be required if a customer deploys on Azure.

jmartisk@redhat.com might have something more to say about Remoting, rsvoboda@redhat.com about Web Services and mnovak1@redhat.com about Messaging.