- VNET address range is 10.2.0.0/23 with Default subnet of 10.2.0.0/27
- Brand new ASE instance, configured to use the VNET from step 1 and on that same Default subnet
- MySQL VM joined to VNET from step one at 10.2.0.8, good to go!
- Add new Azure Web App to Service Plan of the ASE from step 2
- Deploy web site code to Azure Web App that's configured to point to 10.2.0.8 for MySQL VM
- Hit web site from step 5 and, when attempting to talk to MySQL VM, it gets denied on network access trying to connect to 10.2.0.8
Now, if I set up a point-to-site and explicitly connect the web app to that point-to-site I can get through, but obviously now all my traffic is going through a gateway and this is not the desired set up. Also, if I use the .cloudapp.net public address (and expose the MySQL port public) I can get through, but obviously that's even worse because I'm going out to the internet. Obviously the whole point of putting the VM and the ASE on the same VNet/subnet is so that they can talk directly to one another.
So, what am I missing? Am I completely off base in my understanding that putting an ASE on a VNet should cause its related apps to run in that same VNet automatically?