Book: Using JBoss EAP on Microsoft Azure
Revision: n_2641013_using-jboss-eap-on-microsoft-azure_version_7.0_edition_1.0_release_0-revision_9151433

Issue description
There is an Important section in Chapter 3 which talks about configuring JBoss EAP high availability. It says:
you must create your virtual machines inside the same Azure storage account, in the same blob container, and in the same virtual network.

This is not correct. Only the cluster nodes have to share the same storage/container configuration for AZURE_PING discovery protocol.
The information about "the same virtual network" is valid for AZURE_PING. (It's not required when users configures TCPPING protocol with static list of addresses - the public ones on Azure. But in such case the communication between cluster nodes goes through public network which means additional costs and security risks for users.)

Suggestions for improvement
I would use sth like:
If you are configuring JBoss EAP high availability with AZURE_PING discovery protocol, you must create your virtual machines in the same virtual network.

This should be also fixed in section 6.3. TROUBLESHOOTING JBOSS EAP HIGH AVAILABILITY