Hi @Michael Torbett ,
Greetings!
Adding a few points.
- You don't have to create outbound NSG rule for this scenario. Only NSG inbound rule should suffice your requirement.
- There could be a few possible causes here:
a. To verify NSG is not an issue, create an inbound rule as suggested by Ganesh in above comment and keep the source IP as Any (0.0.0.0/0) and destination port as Any (*) Protocol as TCP. Sometimes doing this is not possible if there is a policy that restricts you from allowing the traffic in that case, connect to VPN first. Check what is your public IP and then whitelist it in NSG rule.
Also ensure that this rule has priority 100 and should be above of any deny rule.
b. You can utilize Azure network watcher to check if there is any traffic blocked in Azure.
https://learn.microsoft.com/en-us/azure/network-watcher/connection-troubleshoot-overview
https://learn.microsoft.com/en-us/azure/network-watcher/ip-flow-verify-overview
c. Check the firewall status at the OS level where site is hosted. Try whitelisting the IP address or disabling OS firewall for testing.
d. Possibly your VPN brings any kind of proxy which doesn't have the website allowed. Or VPN is not able to resolve the DNS name of the website. Please post the error screenshot in that case.
I hope this helps.