acrolinx and cleaned up powershell code

Author: asudbring

articles/virtual-network/ip-services/virtual-networks-static-private-ip-classic-ps.md

@@ -7,7 +7,7 @@ ms.service: virtual-network
 ms.subservice: ip-services
 ms.topic: how-to
 ms.workload: infrastructure-services
-ms.date: 02/02/2016
+ms.date: 03/22/2023
 ms.author: allensu
 ms.custom: H1Hack27Feb2017
 ---
@@ -24,13 +24,19 @@ This article covers the classic deployment model. You can also [manage a static
 
 [!INCLUDE [virtual-networks-static-ip-scenario-include](../../../includes/virtual-networks-static-ip-scenario-include.md)]
 
-The sample PowerShell commands below expect a simple environment already created. If you want to run the commands as they are displayed in this document, first build the test environment described in [Create a VNet](/previous-versions/azure/virtual-network/virtual-networks-create-vnet-classic-netcfg-ps).
+The following sample PowerShell commands expect a simple environment already created. If you want to run the commands as they're displayed in this document, first build the test environment described in [Create a VNet](/previous-versions/azure/virtual-network/virtual-networks-create-vnet-classic-netcfg-ps).
 
 ## How to verify if a specific IP address is available
+
 To verify if the IP address *192.168.1.101* is available in a VNet named *TestVNet*, run the following PowerShell command and verify the value for *IsAvailable*:
 
 ```azurepowershell
-Test-AzureStaticVNetIP –VNetName TestVNet –IPAddress 192.168.1.101 
+$tstip = @{
+    VNetName = "TestVNet"
+    IPAddress = "192.168.1.101"
+}
+Test-AzureStaticVNetIP @tstip
+
 ```
 
 Expected output:
@@ -44,16 +50,42 @@ OperationStatus      : Succeeded
 ```
 
 ## How to specify a static private IP address when creating a VM
-The PowerShell script below creates a new cloud service named *TestService*, then retrieves an image from Azure, creates a VM named *DNS01* in the new cloud service using the retrieved image, sets the VM to be in a subnet named *FrontEnd*, and sets *192.168.1.7* as a static private IP address for the VM:
+
+The following PowerShell script creates a new cloud service named *TestService*. The script then retrieves an image from Azure and creates a VM named *DNS01* in the new cloud service. Finally, the script using the sets the VM to be in a subnet named *FrontEnd*, and sets *192.168.1.7* as a static private IP address for the VM:
+
 
 ```azurepowershell
-New-AzureService -ServiceName TestService -Location "Central US"
+$azsrv = @{
+    ServiceName = "TestService"
+    Location = "Central US"
+}
+New-AzureService @azsrv
+
 $image = Get-AzureVMImage | where {$_.ImageName -like "*RightImage-Windows-2012R2-x64*"}
-New-AzureVMConfig -Name DNS01 -InstanceSize Small -ImageName $image.ImageName |
-    Add-AzureProvisioningConfig -Windows -AdminUsername adminuser -Password MyP@ssw0rd!! |
-    Set-AzureSubnet –SubnetNames FrontEnd |
-    Set-AzureStaticVNetIP -IPAddress 192.168.1.7 |
-    New-AzureVM -ServiceName TestService –VNetName TestVNet
+
+$azcfg = @{
+    Name = "DNS01"
+    InstanceSize = "Small"
+    ImageName = $image.ImageName
+}
+
+$azprv = @{
+    AdminUsername = "adminuser"
+}
+
+$azsub = @{
+    SubnetNames = "FrontEnd"
+}
+
+$azip = @{
+    IPAddress = "192.168.1.7"
+}
+
+$azvm = @{
+    ServiceName = "TestService"
+    VNetsName = "TestVNet"
+}
+New-AzureVMConfig @azcfg | Add-AzureProvisioningConfig @azprv -Windows | Set-AzureSubnet @azsub | Set-AzureStaticVNetIP @azip | New-AzureVM @azvm
 ```
 
 Expected output:
@@ -67,10 +99,15 @@ New-AzureVM          3b99a86d-84f8-04e5-888e-b6fc3c73c4b9 Succeeded
 ```
 
 ## How to retrieve static private IP address information for a VM
-To view the static private IP address information for the VM created with the script above, run the following PowerShell command and observe the values for *IpAddress*:
+
+To view the static private IP address information for the VM created with the previous script, run the following PowerShell command and observe the values for *IpAddress*:
 
 ```azurepowershell
-Get-AzureVM -Name DNS01 -ServiceName TestService
+$vm = @{
+    Name = "DNS01"
+    ServiceName = "TestService"
+}
+Get-AzureVM @vm
 ```
 
 Expected output:
@@ -105,12 +142,15 @@ OperationStatus             : OK
 ```
 
 ## How to remove a static private IP address from a VM
-To remove the static private IP address added to the VM in the script above, run the following PowerShell command:
+
+To remove the static private IP address added to the VM in the previous script, run the following PowerShell command:
 
 ```azurepowershell
-Get-AzureVM -ServiceName TestService -Name DNS01 |
-    Remove-AzureStaticVNetIP |
-    Update-AzureVM
+$vm = @{
+    Name = "DNS01"
+    ServiceName = "TestService"
+}
+Get-AzureVM -ServiceName @vm | Remove-AzureStaticVNetIP | Update-AzureVM
 ```
 
 Expected output:
@@ -122,12 +162,18 @@ Update-AzureVM       052fa6f6-1483-0ede-a7bf-14f91f805483 Succeeded
 ```
 
 ## How to add a static private IP address to an existing VM
-To add a static private IP address to the VM created using the script above, run the following command:
+
+To add a static private IP address to the VM created using the previous script, run the following command:
 
 ```azurepowershell
-Get-AzureVM -ServiceName TestService -Name DNS01 |
-    Set-AzureStaticVNetIP -IPAddress 192.168.1.7 |
-    Update-AzureVM
+$vm = {
+    Name = "DNS01"
+    ServiceName = "TestService"}
+
+$ip = {
+    IPAddress = "192.168.1.7"
+}
+Get-AzureVM @vm | Set-AzureStaticVNetIP @ip | Update-AzureVM
 ```
 
 Expected output:
@@ -140,9 +186,12 @@ Update-AzureVM       77d8cae2-87e6-0ead-9738-7c7dae9810cb Succeeded
 
 ## Set IP addresses within the operating system
 
-It’s recommended that you do not statically assign the private IP assigned to the Azure virtual machine within the operating system of a VM, unless necessary. If you do manually set the private IP address within the operating system, ensure that it is the same address as the private IP address assigned to the Azure VM, or you can lose connectivity to the virtual machine. You should never manually assign the public IP address assigned to an Azure virtual machine within the virtual machine's operating system.
+It’s recommended that you don't statically assign the private IP assigned to the Azure virtual machine within the operating system of a VM, unless necessary. If you do manually set the private IP address within the operating system, ensure that it's the same address as the private IP address assigned to the Azure VM. Failure to match the IP address could result in loss of connectivity to the virtual machine.
 
 ## Next steps
+
 * Learn about [reserved public IP](/previous-versions/azure/virtual-network/virtual-networks-reserved-public-ip) addresses.
+
 * Learn about [instance-level public IP (ILPIP)](/previous-versions/azure/virtual-network/virtual-networks-instance-level-public-ip) addresses.
+
 * Consult the [Reserved IP REST APIs](/previous-versions/azure/reference/dn722420(v=azure.100)).