Merge pull request #232713 from mohitp930/mp3292023-freshness-pass-2036655

Freshness Pass User Story: 2036655(https://mseng.visualstudio.com/Tec…

Author: denrea

articles/virtual-network/media/virtual-networks-viewing-and-modifying-hostnames/virtual-machine-properties.png

@@ -1,54 +1,82 @@
 ---
-title: Viewing and Modifying Hostnames
-description: How to view and change hostnames for Azure virtual machines, web and worker roles for name resolution
+title: View and Modify hostnames
+description: Learn how to view and modify hostnames for your Azure virtual machines by using the Azure portal or a remote connection.
 services: virtual-network
 author: asudbring
 manager: dcscontentpm
 ms.assetid: c668cd8e-4e43-4d05-acc3-db64fa78d828
 ms.service: virtual-network
 ms.topic: how-to
 ms.workload: infrastructure-services
-ms.date: 05/14/2021
+ms.date: 03/29/2023
 ms.author: allensu
 ---
 
-# Viewing and modifying hostnames
-To allow your role instances to be referenced by host name, you must set the value for the host name in the service configuration file for each role. You do that by adding the desired host name to the **vmName** attribute of the **Role** element. The value of the **vmName** attribute is used as a base for the host name of each role instance. For example, if **vmName** is *webrole* and there are three instances of that role, the host names of the instances will be *webrole0*, *webrole1*, and *webrole2*. You do not need to specify a host name for virtual machines in the configuration file, because the host name for a virtual machine is populated based on the virtual machine name. For more information about configuring a Microsoft Azure service, see [Azure Service Configuration Schema (.cscfg File)](/previous-versions/azure/reference/ee758710(v=azure.100))
+# View and modify hostnames
 
-## Viewing hostnames
-You can view the host names of virtual machines and role instances in a cloud service by using any of the tools below.
+The hostname identifies your virtual machine (VM) in the user interface and Azure operations. You first assign the hostname of a VM in the **Virtual machine name** field during the creation process in the Azure portal. After you create a VM, you can view and modify the hostname either through a remote connection or in the Azure portal.
 
-### Service configuration file
-You can download the service configuration file for a deployed service from the **Configure** blade of the service in the Azure portal. You can then look for the **vmName** attribute for the **Role name** element to see the host name. Keep in mind that this host name is used as a base for the host name of each role instance. For example, if **vmName** is *webrole* and there are three instances of that role, the host names of the instances will be *webrole0*, *webrole1*, and *webrole2*.
+## View hostnames
+You can view the hostname of your VM in a cloud service by using any of the following tools.
+
+### Azure portal
+
+In the Azure portal, go to your VM, and select **Properties** from the left navigation. On the **Properties** page, you can view the hostname under **Computer Name**.
+
+:::image type="content" source="./media/virtual-networks-viewing-and-modifying-hostnames/virtual-machine-properties.png" alt-text="Screenshot that shows the Properties page of a virtual machine and highlights the Computer Name.":::
 
 ### Remote Desktop
-After you enable Remote Desktop (Windows), Windows PowerShell remoting (Windows), or SSH (Linux and Windows) connections to your virtual machines or role instances, you can view the host name from an active Remote Desktop connection in various ways:
+You can connect to your VM using a remote desktop tool like Remote Desktop (Windows), Windows PowerShell remoting (Windows), SSH (Linux and Windows) or Bastion (Azure portal). You can then view the hostname in a few ways:
 
-* Type hostname at the command prompt or SSH terminal.
-* Type ipconfig /all at the command prompt (Windows only).
+* Type *hostname* in PowerShell, the command prompt, or SSH terminal.
+* Type *ipconfig /all* in the command prompt (Windows only).
 * View the computer name in the system settings (Windows only).
 
-### Azure Service Management REST API
+### Azure API
 From a REST client, follow these instructions:
 
-1. Ensure that you have a client certificate to connect to the Azure portal. To obtain a client certificate, follow the steps presented in [How to: Download and Import Publish Settings and Subscription Information](/previous-versions/dynamicsnav-2013/dn385850(v=nav.70)). 
-2. Set a header entry named x-ms-version with a value of 2013-11-01.
-3. Send a request in the following format: `https://management.core.windows.net/<subscription-id>/services/hostedservices/<service-name>?embed-detail=true`
-4. Look for the **HostName** element for each **RoleInstance** element.
+1. Ensure that you have an authenticated connection to the Azure portal. Follow the steps presented in [Create an Azure Active Directory application and service principal that can access resources](/azure/active-directory/develop/howto-create-service-principal-portal). 
+2. Send a request in the following format:
+
+    ```http
+    GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/virtualMachines/{vmName}?api-version=2022-11-01`. 
+    ```
+
+    For more information on GET requests for virtual machines, see [Virtual Machines - Get](/rest/api/compute/virtual-machines/get).
+3. Look for the **osProfile** and then the **computerName** element to find the host name.
 
 > [!WARNING]
-> You can also view the internal domain suffix for your cloud service from the REST call response by checking the **InternalDnsSuffix** element, or by running ipconfig /all from a command prompt in a Remote Desktop session (Windows), or by running cat /etc/resolv.conf from an SSH terminal (Linux).
+> You can also view the internal domain suffix for your cloud service by running `ipconfig /all` from a command prompt in a remote desktop session (Windows), or by running `cat /etc/resolv.conf` from an SSH terminal (Linux).
 > 
 > 
 
-## Modifying a hostname
-You can modify the host name for any virtual machine or role instance by uploading a modified service configuration file, or by renaming the computer from a Remote Desktop session.
+## Modify a hostname
+You can modify the hostname for any VM by renaming the computer from a remote desktop session or by using **Run command** in the Azure portal.
 
-## Next steps
-[Name Resolution (DNS)](virtual-networks-name-resolution-for-vms-and-role-instances.md)
+From a remote session:
+* For Windows, you can change the hostname from PowerShell by using the [Rename-Computer](/powershell/module/microsoft.powershell.management/rename-computer) command. 
+* For Linux, you can change the hostname by using `hostnamectl`.
+
+You can also use run these commands to find the hostname for your VM from the Azure portal by using **Run command**. In the Azure portal, go to your VM, and select **Run command** from the left navigation. From the **Run command** page in the Azure portal:
+* For Windows, select **RunPowerShellScript** and use `Rename-Computer` in the **Run Command Script** pane.
+* For Linux, select **RunShellScript** and use `hostnamectl` in the **Run Command Script** pane.
 
-[Azure Service Configuration Schema (.cscfg)](/previous-versions/azure/reference/ee758710(v=azure.100))
+The following image shows the **Run command** page in the Azure portal for a Windows VM.
 
-[Azure Virtual Network Configuration Schema](/previous-versions/azure/reference/jj157100(v=azure.100))
+:::image type="content" source="./media/virtual-networks-viewing-and-modifying-hostnames/virtual-machine-run-command.png" alt-text="Screenshot that shows the Run command page for a Windows virtual machine and highlights the RunPowerShellScript feature.":::
 
-[Specify DNS settings using network configuration files](/previous-versions/azure/virtual-network/virtual-networks-specifying-a-dns-settings-in-a-virtual-network-configuration-file)
+After you run either `Rename-Computer` or `hostnamectl` on your VM, you need to restart your VM for the hostname to change.
+
+## Azure classic deployment model
+
+The Azure classic deployment model uses a configuration file that you can download and upload to change the host name. To allow your host name to reference your role instances, you must set the value for the host name in the service configuration file for each role. You do that by adding the desired host name to the **vmName** attribute of the **Role** element. The value of the **vmName** attribute is used as a base for the host name of each role instance. 
+
+For example, if **vmName** is *webrole* and there are three instances of that role, the host names of the instances are *webrole0*, *webrole1*, and *webrole2*. You don't need to specify a host name for virtual machines in the configuration file, because the host name for a VM is populated based on the virtual machine name. For more information about configuring a Microsoft Azure service, see [Azure Service Configuration Schema (.cscfg File)](/previous-versions/azure/reference/ee758710(v=azure.100))
+
+### Service configuration file
+In  the Azure classic deployment model, you can download the service configuration file for a deployed service from the **Configure** pane of the service in the Azure portal. You can then look for the **vmName** attribute for the **Role name** element to see the host name. Keep in mind that this host name is used as a base for the host name of each role instance. For example, if **vmName** is *webrole* and there are three instances of that role, the host names of the instances are *webrole0*, *webrole1*, and *webrole2*. For more information, see [Azure Virtual Network Configuration Schema](/previous-versions/azure/reference/jj157100(v=azure.100))
+
+
+## Next steps
+* [Name Resolution (DNS)](virtual-networks-name-resolution-for-vms-and-role-instances.md)
+* [Specify DNS settings using network configuration files](/previous-versions/azure/virtual-network/virtual-networks-specifying-a-dns-settings-in-a-virtual-network-configuration-file)