Mapping of Azure services to the vNet
Company security restrictions do not allow to open port 80, 443, 1433, ... (or other) from a vNet / VPN to the Internet.
Mapping Azure services with a public IP to a vNet should become a general feature (not only for SQL as requested in the following request).
See also https://feedback.azure.com/forums/217321-sql-database/suggestions/5537689-allow-sql-database-to-join-virtual-network-vpn
vNet internal dynamic or static IP / name + port -- mapping -> Public dynamic IP / name + port
Stella Hu commented
I have come across the same issue. :(