Ravi Kanth Koppala 3,231Reputation points • Microsoft Employee
@Mohammad Bin Qasim Niaz ,
I can reproduce the error and able to fix the issue. I created a windows 2019 data center SKU with default values (and public IP). Then, when I tried to log into the machine, the IIS feature was not enabled by default, and I installed the feature. When I access the default website, I can browse the default IIS website. 
I am not able to access the website from the outside. To make it work, I did open port 80 for HTTP access to the website via the internet. To do this, follow the below steps:
- Click on your VM in the Azure portal.
- Click on Network Interfaces > The IP address tab > Network Security groups > Click on the NSG that is available there.
- On the tab that appears click on Inbound Security rules > Add > Click on the Service dropdown and select http > Click on OK.
After these changes, I can browse the website from the outside. 
I understand you did the same steps. Can you please confirm if a public IP is configured for the VM?
----------
(If the reply was helpful, please don't forget to upvote and accept as an answer, thank you)
Ravi Kanth
Boleslav 0Reputation points
2023-08-12T10:53:27.2566667+00:00 I am soooo not surprised. Microsoft is sh%ty again even in default setup of its software! The default website just DOESN'T work BY DEFAULT! Such primitive logic and yet no luck!
Instead, you just setup linux machine with basic Apache/Ngnix, and voila.
Maybe those are just signs to us: "guys, f%ck IIS, this is the 19th century, none uses it anymore, please go to linux with ngnix"!
Boleslav 0Reputation points
2023-08-12T11:10:27.7233333+00:00 The worst thing is that in case of "I just reinstalled my Virtual Machine", you just don't have any confidence it won't happen again, because you don't have clear understanding what caused the issue! "Well, there are some files corrupted!" Really? Maybe I should tell that to my customers: "Oh, you know, Microsoft is somewhere corrupted... you know?!"
Any default ngnix/apache setups just don't have that for the DEFAULT EMPTY websites!
Prrudram-MSFT 24,366Reputation points
2023-08-14T05:53:10.47+00:00 Hi Boleslav
It is important to identify where the issue is in case the default website is inaccessible outside of the VM.
Like, previously suggested, the common blocker in this case is NSG rules, you need to allow inbound traffic on port 80 from the internet.
If that is already done and still there is an issue accessing the website from outside of the VM, it needs to be debugged from 2 aspects, one the IIS and two networking.
I recommend raising a support case with azure technical support for a deeper investigation.
I also recommend following the code of conduct for Microsoft Q&A being a user on this forum. Any kind of abuse in the Q&A community forum will result in your profile being banned from the community.
Boleslav 0Reputation points
2023-08-14T12:26:47.5633333+00:00 It has nothing to do neither with networking nor FireWall. It happens even locally on localhost! By default! When with other VM setup it works well, again, BY DEFAULT. That's why it's so frustrating!
Prrudram-MSFT 24,366Reputation points
2023-10-13T17:53:25.35+00:00 This issue needs deeper investigation, Azure technical support team will be able to check and help on this. I would recommend you open an azure support case. If you don't have the ability to open a technical support ticket, please let me know and I can help you further with this.
Sign in to comment
