Note that this is not to map the storage blobs but only File Shares.

You will also need port 445 open for outbound to allow SMB protocol traffic. You can quickly use the following PowerShell script to do a quick port scan test.

$resourceGroupName = "resourcename"
$storageAccountName = "storageaccount"

Connect-AzAccount
$storageAccount = Get-AzStorageAccount -ResourceGroupName $resourceGroupName -Name $storageAccountName

Test-NetConnection -ComputerName ([System.Uri]::new($storageAccount.Context.FileEndPoint).Host) -Port 445

Now, let’s open File Explorer, go to This PC, click Computer tab and Map network drive.

Select the drive letter and enter the UNC Path of your Azure Storage File Share, formatted as below:

\\storageaccount.file.core.windows.net\filesharename

Make sure to check the option “Connect using different credentials” and click Finish.

When prompted for a credential, put in AZURE\storageaccount as the username and your Azure Storage account access key as the password.

Hit OK, and done.

You can do so via Command Line or even PowerShell but somehow I find this is actually easier.

For anyone interested in diving deep in Azure’s world.

Microsoft Training and Certification

Azure Essentials – the best place to get started with Azure and learn new skills

Pluralsight – free self-paced courses

Hands-on Labs – an array of self-paced labs, instructor-led classes, and challenging exercises to practice the skills

Certifications – boost your career with a Microsoft certification

It’s a whole wild world to explore.

There are three different kinds of IP address that can be assigned to virtual machines (VMs) in Microsoft Azure:

• Dynamic IP address (DIP)
• Virtual IP address (VIP)
• Instance-level public IP address (PIP)

//via Petri

1. VHDX handles power outages better
2. Integrity check needs to be disabled if VHDX running on top of ReFS system
3. Only VHD to upload to Azure virtual server.

So, really, there are not many points to use VHDX to replace the classic VHD.

//via Technet