AZURE VIRTUAL NETWORK GATEWAY TRANSIT    

In theory allowing Gateway Transit on Hub vnet should allow two spoke vnet that peered with hubvnet to talk to each other but that's not what is happening. I had to manually add routes to the spoke route table and pointing that to the vpn gateway IP address for the two spoke to talk to each other

 AZURE GLOBALPEERING, GATEWAY TRANSIT

only region matter in determining between VNet peering and VnetGlobalPeering

peering across region = VNetGlobalPeering 

peering within region -= VNet Peering

AZURE STORAGE COPY USING POWERSHELL

Azure Creating SAS Token using Stored Access Policy - PowerShell

CHANGING CONTAINER ACCESS POLICY TIME WILL CHANGE THE TIME SAS TOKE IS ACTIVE OR NOT

AZURE FIREWALL

Network rule take precedence over Application rules. so if HTTP/S is allowed in network rules then deny application rules will not take effect at all. need to allow all http/s in application rule and deny particular ones

NAT RULE is port translation inbound

AZURE ALLOW ICMP TO WINDOWS MACHINE

Ubuntu Gnome-Terminal Not working