tweaks for finding public ips

Author: mlhoop

articles/aks/use-multiple-node-pools.md

@@ -724,7 +724,7 @@ It may take a few minutes to update your AKS cluster depending on the node pool
 > You must install the CLI preview extension 0.4.43 or greater to use the public IP per node feature.
 
 > [!Important]
-> The Azure Instance Metadata Service doesn't currently support public IP addresses for the standard tier VM SKU. Due to this limitation, you can't use kubectl commands to display the public IPs assigned to the nodes. However, the IPs are assigned and function as intended.
+> The Azure Instance Metadata Service doesn't currently support public IP addresses for the standard tier VM SKU. Due to this limitation, you can't use kubectl commands to display the public IPs assigned to the nodes. However, the IPs are assigned and function as intended. You can use the PowerShell command Get-AzPublicIpAddress to view the public IPs.
 
 AKS nodes do not require their own public IP addresses for communication. However, scenarios may require nodes in a node pool to receive their own dedicated public IP addresses. An common scenario is for gaming workloads, where a console needs to make a direct connection to a cloud virtual machine to minimize hops. This scenario can be achieved on AKS by registering for a preview feature, Node Public IP (preview).
 
@@ -765,6 +765,15 @@ For existing AKS clusters, you can also add a new node pool, and attach a public
 az aks nodepool add -g MyResourceGroup2 --cluster-name MyManagedCluster -n nodepool2 --enable-node-public-ip
 ```
 
+You can view the public IPs for your nodes with [PowerShell or Bash commands][vmss-commands]. You can also view the public IPs in the Azure Portal by viewing the instances in the Virtual Machine Scale Set.
+
+> [!Important]
+> The [node resource group][node-resource-group] contains the nodes and their public IPs. Use the node resource group with the following PowerShell command:
+
+```powershell
+Get-AzPublicIpAddress -ResourceGroupName MC_MyResourceGroup2_MyManagedCluster_eastus -VirtualMachineScaleSetName YourVirtualMachineScaleSetName
+``` 
+
 ## Clean up resources
 
 In this article, you created an AKS cluster that includes GPU-based nodes. To reduce unnecessary cost, you may want to delete the *gpunodepool*, or the whole AKS cluster.
@@ -828,3 +837,5 @@ To create and use Windows Server container node pools, see [Create a Windows Ser
 [vm-sizes]: ../virtual-machines/linux/sizes.md
 [use-system-pool]: use-system-pools.md
 [ip-limitations]: ../virtual-network/virtual-network-ip-addresses-overview-arm#standard
+[node-resource-group]: faq#why-are-two-resource-groups-created-with-aks.md
+[vmss-commands]: ../virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-ipv4-per-virtual-machine