In this video, I walk through Azure Perfinsights, a performance reporting and troubleshooting tool for Windows and Linux Virtual Machines.
This video that goes over how to enable and use Microsoft’s newly announced Global VNet Peering. This feature expands on existing VNet peering, allowing for connectivity between VNets in two different regions. More information can be found here
Commands used in this video are:
I had the pleasure of spending a significant amount of time elbows deep in a Remote Desktop Services deployment this week. As part of the effort, I published the RDS RDWeb IIS page with the Azure AD Application Proxy so MFA can be leveraged for remote desktop services.
Microsoft announced a new Azure Connectivity Check as part of the Network Watcher service. Below is the announcement from Microsoft:
A couple things to note before you use it:
First, you have to enable your subscription for Network Watcher. Do this by going into Network Watcher and selecting your subscription in the Overview blade. Go to the three dots on the right and enable your subscription.
If you deployed a VM using the new Resource Manager mode in Azure and need to find the IP and if it is static you may have ran across the “Get-AzureVM” command as an option to retrieve IP information. This command is for “Clasic” mode and won’t work in Resource Manager mode.
To get IP information including the internal IP and if it is set dynamic or static, use this command:
Get-AzureRmNetworkInterface -name <NIC_Name> -ResourceGroupName <NIC_ResourceGroup>
Notice that this does not specify the VM Name, it specifies the NIC attached to the VM. The output will give you the IP address and indicate if it is static or dynamic.