Azure High IOPS is not initiliazing disk - stripped for own template - solution included

[azure-quickstart-templates/301-vm-32-data-disks-high-iops/](https://github.com/Azure/azure-quickstart-templates/tree/master/301-vm-32-data-disks-high-iops)

### Issue Details
Azure High IOPS is not initiliazing disk

### Repro steps (*if necessary, delete otherwise*)
1. Stripped the config for own use
2. Tested deployments
3. Adjusted script to work with msft virtual disks
4. Checked config - deployed with succes
5. Below is the script: StoragePool.ps1

Configuration StoragePool
{
param ($MachineName)

Node $MachineName
{
Script ConfigureStoragePool {
SetScript = {
$disk = get-disk | where partitionstyle -eq ‘raw’
foreach ($d in $disk){
$diskNumber = $d.Number
$dl = get-Disk $d.Number | Initialize-Disk -PartitionStyle GPT
Start-Sleep 2
}
$PhysicalDisks = Get-StorageSubSystem -FriendlyName "Windows Storage*" | Get-PhysicalDisk -CanPool $True
New-StoragePool -FriendlyName "StoragePoolDataDisks" -StorageSubsystemFriendlyName "Windows Storage*" -PhysicalDisks $PhysicalDisks |New-VirtualDisk -FriendlyName "DATA Virtual Disk" -UseMaximumSize -ResiliencySettingName "Simple" -ProvisioningType Fixed -Interleave 65536 | Initialize-Disk -Confirm:$False -PassThru | New-Partition -DriveLetter H –UseMaximumSize | Format-Volume -FileSystem NTFS -NewFileSystemLabel "DATA" -Confirm:$false
}
TestScript = {
Test-Path H:\
}
GetScript = { <# This must return a hash table #> } }
}
}

Start with the 301-vm-32-data-disks-high-iops template and the provided StoragePool.ps1 script. Compare the template's disk-initialization flow with the successful script, then verify a deployment initializes the data disks and exposes the H: volume; the issue does not specify which upstream files should change.

Written by the indexing model from the issue text.