One of my engineers noticed something recently that I thought reasonable to request as a feature.
When managing NSG rules in the Azure Portal, Azure tries to be helpful and give you warnings when a rule may not produce the desired effect. In my sample case, we have a rule with the orange warning exclamation icon
NMM does not surface this warning or notification in the UI. I think it would be valuable to bring that to the NMM UI (assuming Microsoft surfaces it via API) that a less than optimal condition exists. In this particular case the engineer did the rule in the portal and edited the source port field (unintentionally), we didn't catch it until it failed to produce the desired result.
This probably wouldn't have happened if they had done it in NMM (I keep preaching it as the easy button), but upon reviewing the rules myself (in NMM) we didn't notice this until we looked closer in the portal and found the oops. I know I've seen similar warnings for other rules in the past which are a bit more dire, like the one shown below, and probably the most valuable to surface to avoid mistakes.
Not a cataclysmic earth shattering improvement, but sometimes it is the little things.
Comments (2 comments)