Not able to access other website blocked by azure

Common causes are:

1. VM-level outbound filtering A firewall on the Windows VM can block outbound web traffic on ports 80 or 443. Since DNS resolution can still work while web access fails, this matches cases where nslookup succeeds but browser access and Test-NetConnection fail.
2. Azure network filtering An NSG or other network path control can deny outbound internet traffic from the VM. In Azure, this can be tested from the VM networking experience. If the test shows Traffic status: Denied, the summary identifies the blocking rule.
3. Website-side or ISP-side blocking If other Azure VMs can reach the site but this VM cannot, the issue can be specific to the source IP path, such as the website host or ISP blocking Azure-originated traffic from that region.

Useful checks:

1. On the VM, verify Windows Firewall allows outbound traffic on 80 and 443.
2. In Azure, run the Network security group test for outbound connectivity:
   • Service type: Custom
   • Port: 50000
   • Protocol: Any
   • Destination type: Any IP address
   • Select Run test
   • If the result is Denied, review the blocking NSG rule.
3. If Azure outbound access is allowed and the VM firewall is not blocking, test from another Azure VM or another Azure region. That helps confirm whether the destination site is blocking Azure traffic based on source IP or geography.
4. If the site is blocked only from this Azure path, contact the site administrator or ISP.

References:

• Network security group test
• Unable to browse a website from my VM in azure - Microsoft Q&A