A narrow allowed path
A fictional operations service accepts HTTPS from a specified office range. An inbound TCP rule for port 443 with that source is different from allowing every source or every protocol. Lower numeric NSG priorities are evaluated first. Read potentially matching rules before adding another one.
NSGs are stateful. You don’t need a mirror rule solely for return traffic on an allowed connection. That doesn’t establish that the destination application is listening or that routing and other controls permit the request.
Configuration practice
Open the NSG rules exercise and identify the requested security group. Configure the source range, protocol, port and priority in the local console. Inspect the saved rule instead of relying on its display name.
Change one field and explain the consequence. A plausible rule name can hide an overbroad source or a priority that doesn’t meet the request. The local model checks configuration; it doesn’t send packets or reproduce Azure’s complete effective-rule evaluation.
Network investigation
Continue in the Azure course with subnets, network interfaces and incident cases. Use networking practice for addresses, routes and packet evidence. In a real environment, test the actual path and the receiving service before concluding that an NSG change restored connectivity.