eStreamer works on a different VNET from eStreamer client on Azure?

[takeshi yabuki]

I understand using VNET Peering could be solution for this.
When deploying FMCv, there is a parameter "public inbound ports" that connections are restricted except from same VNET and Azure LB by default.
Even if this is enabled, only HTTPS, SSH and SFTunnel can be selected, and I'm not sure if eStreamer SSL tcp8302 can connect.
Please give me some advises.

public inbound ports: By default, access to the virtual machine is restricted to sources in the same virtual network, and traffic from Azure load balancing solutions. Select None to confirm, or choose to allow traffic from the public internet to one of these common ports.(Management interface only)

Thank you.

[Marvin Rhoads]

Normally eStreamer clients would not be requesting data via a public IP address. Your direct connect or VPN into Azure would be the patch via which the requests occur. Otherwise the Azure NSG natively is quite limited as to what you can setup to allow incoming traffic (as you noted).