Configure Static Internal IP for Azure VMs

Configure and manage virtual networks in Azure

Run the New-AzureRMVMConfig PowerShell cmdlet.
Run the Set-AzureSubnet PowerShell cmdlet.
Modify the VM properties in the Azure Management Portal. Correct Answer
Modify the IP properties in Windows Network and Sharing Center.
Run the Set-AzureStaticVNetIP PowerShell cmdlet.

Answer Correct answer: C — Modify the VM properties in the Azure Management Portal to set the private IP allocation method to Static.

Community Insight

The AZ-104 exam tests Azure Resource Manager (ARM) concepts, making classic deployment cmdlets like Set-AzureStaticVNetIP invalid traps.

Assigning a static private IP address to an Azure VM requires modifying the network interface configuration in the Azure portal, as classic PowerShell cmdlets are deprecated. This guide clarifies the correct ARM deployment method for AZ-104.

Choosing the classic Set-AzureStaticVNetIP cmdlet (Option E) because it sounds correct for older exams, but it is deprecated and does not work for ARM VMs.

Community Discussion (116 comments)

GeoPoi 👍 1 Selected: E

Copilot Sol Think, thinks its the correct one

Srikantha 👍 1 Selected: E

Explanation: Set-AzureStaticVNetIP: In the classic Azure deployment model, this PowerShell cmdlet (typically piped with Get-AzureVM and saved with Update-AzureVM) is used to assign a static internal/private IP address to a virtual machine within an Azure virtual network. Because the application relies on hardcoded or direct IP-to-IP communication between SRV01 and SRV02, configuring static internal IP addresses ensures consistency post-migration.

GeoPoi 👍 1 Selected: E

C is incorrect: In the classic Azure Management Portal referenced in this question, you could not configure static private IPs through the GUI. Even in the modern Azure Resource Manager portal, static private IPs are configured under the Network Interface (NIC) $\rightarrow$ IP configurations blade, not within general "VM properties". So i go with E

Jonasgm07 👍 1 Selected: C

C is the correct answer.

zelm 👍 1 Selected: E

answer from claude: Your company has two on-premises servers named SRV01 and SRV02. Developers have created an application that runs on SRV01. The application calls a service on SRV02 by IP address. You plan to migrate the application on Azure virtual machines (VMs). You have configured two VMs on a single subnet in an Azure virtual network. You need to configure the two VMs with static internal IP addresses. What should you do? A. Run the New-AzureRMVMConfig PowerShell cmdlet. B. Run the Set-AzureSubnet PowerShell cmdlet. C. Modify the VM properties in the Azure Management Portal. Most Voted D. Modify the IP properties in Windows Network and Sharing Center. E. Run the Set-AzureStaticVNetIP PowerShell cmdlet.

GokuSS 👍 1 Selected: E

E. Run the Set-AzureStaticVNetIP PowerShell cmdlet. This cmdlet assigns a static internal IP address (DIP) from the virtual network's address range to an Azure VM, ensuring the IP doesn't change on reboot/reallocation — exactly what's needed since SRV02's replacement is being called by IP address. Configuring the static IP from within the guest OS (option D) doesn't work reliably in Azure because the Azure DHCP service manages IP assignment; you must configure it through the Azure platform itself.

Linso 👍 3 Selected: E

Explanation To configure static internal IP addresses for Azure VMs, you must reserve the IP within the Azure virtual network, not inside the guest OS. Azure controls IP allocation through the virtual network configuration, so setting the IP address inside Windows Network settings can cause connectivity issues. The correct approach is to assign the static private IP through Azure, which ensures the address remains fixed for the VM. Why Option E is Correct Set-AzureStaticVNetIP assigns a static private IP address to an Azure VM within its subnet. Example:Set-AzureStaticVNetIP -VM $vm -IPAddress 10.0.0.5

Froko 👍 1 Selected: C

In Azure: Du setzt statische interne IPs nicht im Windows OS. Du setzt sie auf der Netzwerkkarte (NIC) in Azure. Warum? Weil Azure das Netzwerk kontrolliert (SDN). Wenn du im Windows-Netzwerkcenter eine statische IP einstellst, geht die VM offline oder bekommt Probleme. C: Du gehst zu: VM → Networking → NIC → IP Configuration → Static E. Set-AzureStaticVNetIP. Das war früher im Classic Deployment Model (ASM). Heute nicht mehr gültig im ARM-Modell. Merken: On-Prem: IP im OS setzen. Azure: IP auf NIC-Ebene in Azure setzen.

IY_mqc 👍 1 Selected: C

In Azure (ARM model), static private IP addresses are configured at the Azure level, not inside the guest OS. Key points: • Azure assigns private IPs via the network interface (NIC). • You can change the private IP assignment from Dynamic to Static in: • Azure Management Portal • NIC → IP configurations → Private IP address assignment • This ensures the IP remains consistent even after VM restarts.

Chrissy102 👍 1 Selected: E

E is the correct answer

thalasi 👍 2 Selected: C

In the portal, you set: VM → Networking → Network Interface → IP configurations → Private IP address → Static

5ad3dcf 👍 2 Selected: E

Correct answer is E: Run the Set-AzureStaticVNetIP PowerShell cmdlet.

starkids004 👍 2

No — Set-AzureStaticVNetIP is a legacy (classic) Azure Service Manager cmdlet and should not be used for modern Resource Manager (ARM) VMs.

2f7bc07 👍 1 Selected: E

This is the correct cmdlet to assign a static internal IP address to a VM in a virtual network (classic deployment model).

BIRCHR 👍 1 Selected: E

In Azure, VMs must use DHCP and you can’t set a static private IP inside the guest OS. For classic (ASM) VMs, you reserve a static internal IP at the platform level with Set-AzureStaticVNetIP. (Changing Windows NIC settings or subnet settings won’t work, and New-AzureRMVMConfig doesn’t set private IPs.)

vitorsantosvs 👍 2 Selected: E

correct

Alcpt 👍 2 Selected: E

The answer is E. You cannot set vm ip addy via Azure portal > VM > properties blade It would have to be Azure portal > VM > network settings blade

khamrumunnu 👍 1 Selected: E

E. Set-AzureStaticVNetIP is correct answer Why other options are incorrect: A. New-AzureRMVMConfig Used to configure VM parameters, not networking/IP settings. B. Set-AzureSubnet Not a valid cmdlet for configuring VM IPs. C. Modify the VM properties in the Azure Portal While partially true, you don’t assign static IPs directly in VM properties, but in the network interface settings, so this isn’t the most accurate answer in the context of the options. D. Modify the IP properties in Windows Network and Sharing Center Azure assigns dynamic IPs unless you reserve them at the NIC level — setting IPs manually inside the OS causes conflicts and is unsupported. This cmdlet is used to assign a static private IP to an Azure VM's network interface (for the old Azure Service Manager model).

ITCORESExam 👍 1 Selected: E

E is Correct Answer

rah_rule100 👍 1 Selected: E

E is the correct answer

saadraaz 👍 2 Selected: C

Set-AzureStaticVNetIP is from the Azure Service Management (ASM or "Classic") model, and it has been deprecated in favor of the Azure Resource Manager (ARM) model — which is what most deployments use today.

Ekramy_Elnaggar 👍 2 Selected: C

Set-AzureStaticVNetIP (Classic VMs only – Deprecated)

GohanF2 👍 2 Selected: C

I will vote for C as well. We the command for Option E is already deprecated. I dont think so that they will be evaluating on old content. https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-networks-static-private-ip?tabs=azureportal

HartMS 👍 4 Selected: C

In VM settings, we need to go to Networking to make the required changes. C is the correct answer. Set-AzureStaticVnetIP is not a valid option, as that cmdlet was part of the classic model, which is now deprecated. The correct cmdlet is Set-AzNetworkInterface.

Nathan12345 👍 3 Selected: C

Take help from copilot or chatgpt

Bikth 👍 1 Selected: E

To configure Azure virtual machines (VMs) with static internal IP addresses, the best approach is to use the Set-AzureStaticVNetIP PowerShell cmdlet. This allows you to assign a static private IP address to the VM within the Azure virtual network (VNet).

0dc4dd8 👍 2 Selected: C

To configure static internal IP addresses for Azure VMs, you need to set the IP address configuration directly in the Azure portal or using Azure PowerShell/CLI.

superrvirgo 👍 3 Selected: C

There is no Set-AzureStaticVNetIP anymore. But if there was, I would say that the correct answer should be C & E

mpaen10928 👍 2 Selected: C

C is the closest answer, but the change is done within Settings, not Properties. https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-networks-static-private-ip?tabs=azureportal In the following steps, you change the private IP address static for the VM created previously: In the portal, search for and select Virtual machines. In Virtual machines, select myVM from the list. On the myVM page, under Settings, select Networking.

lockmas101 👍 3 Selected: E

Answer is E. You cannot edit the properties in the VM Overview --> Properties. The command might be old but this is probably an old question

TodRose 👍 2 Selected: E

E. Run the Set-AzureStaticVNetIP PowerShell cmdlet. --- Explanation: To configure a static internal IP address for Azure VMs in the same virtual network, you need to use the Set-AzureStaticVNetIP PowerShell cmdlet. This cmdlet allows you to assign a specific private IP address to a virtual machine's network interface within a subnet.

58b2872 👍 2 Selected: E

Option C modifies general VM properties but cannot manage the static IP configuration for the NIC. Option E is designed specifically for static IP assignment, which is exactly addresses the NIC level.

58b2872 👍 1 Selected: E

The Set-AzureStaticVNetIP cmdlet is specifically used to assign a static internal IP address to an Azure VM in a virtual network. Modifying VM properties in the Azure Management Portal (Option C) does not allow you to directly set a static internal IP address. Static IP addresses for Azure VMs must be configured at the network interface level, and this is best done via PowerShell.

bhaskarraobaipothu 👍 1 Selected: E

C. partially correct but not the best answer for the given context. E.E. Run the Set-AzureStaticVNetIP PowerShell cmdlet. It allows you to assign a static IP address to a VM within an Azure Virtual Network

_fvt 👍 1 Selected: E

Set-AzureStaticVNetIP

Anonymouse1312 👍 7 Selected: C

old question, nnow its C or Set-AzNetworkInterface

7bc6163 👍 5 Selected: C

To configure static internal IP addresses for Azure VMs in the Resource Manager model, modify the NIC properties in the Azure Portal. This ensures the IP address is managed correctly by Azure and avoids conflicts.

MackD 👍 3

Correct answer is currently not applicable anymore. It should be Set-AzNetworkInterface See: https://learn.microsoft.com/en-us/powershell/module/az.network/set-aznetworkinterface?view=azps-12.4.0

RVivek 👍 4 Selected: C

Set-AzureStaticVNetIP The cmdlets referenced in this documentation are for managing legacy Azure resources that use Azure Service Manager (ASM) APIs. This legacy PowerShell module isn't recommended when creating new resources since ASM is scheduled for retirement. For more information, see Azure Service Manager retirement. https://learn.microsoft.com/th-th/powershell/module/servicemanagement/azure/set-azurestaticvnetip?view=azuresmps-4.0.0

DT95 👍 7 Selected: C

E is wrong in 2024. The Set-AzureStaticVNetIP cmdlet is part of the classic (ASM) PowerShell module (Azure), which is deprecated. Answer is C: $nic = Get-AzNetworkInterface -Name <NIC_Name> -ResourceGroupName <Resource_Group> $nic.IpConfigurations[0].PrivateIpAllocationMethod = 'Static' $nic.IpConfigurations[0].PrivateIpAddress = '<Desired_IP_Address>' Set-AzNetworkInterface -NetworkInterface $nic

Rovdy 👍 1

El cmdlet Set-AzureStaticVNetIP se usaba en el antiguo modelo Azure Service Manager (ASM), que ya no se recomienda usar, ya que Azure ahora utiliza Azure Resource Manager (ARM). Por lo tanto, modificar la IP desde el portal es la mejor opción en el contexto actual. https://learn.microsoft.com/en-us/powershell/module/servicemanagement/azure/set-azurestaticvnetip?view=azuresmps-4.0.0

kagomezfk 👍 1

Correct Answer E

EmnCours 👍 4 Selected: E

Specify a static internal IP for a previously created VM If you want to set a static IP address for a VM that you previously created, you can do so by using the following cmdlets. If you already set an IP address for the VM and you want to change it to a different IP address, you'll need to remove the existing static IP address before running these cmdlets. See the instructions below to remove a static IP. For this procedure, you'll use the Update-AzureVM cmdlet. The Update-AzureVM cmdlet restarts the VM as part of the update process. The DIP that you specify will be assigned after the VM restarts. In this example, we set the IP address for VM2, which is located in cloud service StaticDemo. Get-AzureVM -ServiceName StaticDemo -Name VM2 | Set-AzureStaticVNetIP -IPAddress 192.168.4.7 | Update-AzureVM

blackmetalx 👍 39

Set-AzureStaticVNetIP is for Classic VMs and will be retired on September 1, 2023. For new VM it can be don in the portal or using Powershell: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/reset-network-interface #Add/Change static IP. This process will change MAC address $vnet = Get-AzVirtualNetwork -Name $VNET -ResourceGroupName $ResourceGroup $subnet = Get-AzVirtualNetworkSubnetConfig -Name $subnet -VirtualNetwork $vnet $nic = Get-AzNetworkInterface -Name $NetInter -ResourceGroupName $ResourceGroup #Remove the PublicIpAddress parameter if the VM does not have a public IP. $nic | Set-AzNetworkInterfaceIpConfig -Name ipconfig1 -PrivateIpAddress $PrivateIP -Subnet $subnet -PublicIpAddress $publicIP -Primary $nic | Set-AzNetworkInterface

tsummey 👍 4 Selected: C

If this question is still on the test, the answer today would be C. You can log in to the portal, select the VM, then Networking followed by Network Settings. There is a box named 'Network Interface / IP Configuration' with a link. If you click on the link, you can change the associated IP to static. The PowerShell command 'Set-AzureStaticVNetIP' is still available in PowerShell: PS C:> Find-Command -Name Set-AzureStaticVNetIP Name Version ModuleName Repository ---- ------- ---------- ---------- Set-AzureStaticVNetIP 5.3.1 Azure PSGallery However, when I tried to use the cmdlet after verifying it's available, the result was: 'Set-AzureStaticVNetIP : The term 'Set-AzureStaticVNetIP' is not recognized as the name of a cmdlet, function, script file, or operable program.' That's just what I see today.

Debugs_Bunny 👍 1

you need to have azure powershell module installed.

lj114 👍 1 Selected: C

Correct answer C.

Bobip 👍 1

Argue: ?! In the ARM model, setting a static IP address is typically done through the Azure Portal or by using ARM-specific PowerShell cmdlets like New-AzNetworkInterface or by specifying the static IP during VM creation via the New-AzVM cmdlet. The Set-AzureStaticVNetIP is not applicable in ARM, which is now the default and recommended deployment model in Azure.

Nico1973 👍 1

Based on the scenario provided, the correct option to configure the two Azure VMs with static internal IP addresses is: E. Run the Set-AzureStaticVNetIP PowerShell cmdlet. Explanation: The Set-AzureStaticVNetIP PowerShell cmdlet is used to set a static internal IP address for an Azure VM within a virtual network. This cmdlet allows you to specify the desired IP address that you want to assign to the VM within the Azure virtual network. By running this cmdlet, you can ensure that the VMs have static internal IP addresses as required for the application migration.

23169fd 👍 4 Selected: C

the correct way to set a static internal IP address for Azure VMs is either by modifying the VM properties in the Azure Management Portal (Option C) or using the appropriate ARM-based PowerShell cmdlets (Set-AzNetworkInterfaceIpConfig), but not Set-AzureStaticVNetIP, which is deprecated for ARM deployments.

3c5adce 👍 3

C. Modify the VM properties in the Azure Management Portal. This is the best option because it allows you to configure static internal IP addresses for the VMs directly through the Azure Management Portal, providing a user-friendly interface and ensuring the changes are correctly applied within the Azure environment. This method is effective and integrates seamlessly with other Azure services and configurations.

3c5adce 👍 1

C. Modify the VM properties in the Azure Management Portal. This approach allows you to securely set and manage static IP configurations within the Azure infrastructure, ensuring that the settings are maintained across reboots and do not conflict with Azure’s network management.

tashakori 👍 2

C is right answer

nospampls 👍 3 Selected: E

delacruzjoshua30 👍 2

I think C can be a correct answer too. I have tried this multiple times already on our AzVMs.

photon99 👍 2

Tbh, This Commandlet Set-AzureStaticVNetIP does not adheres to Az Powershell module name. It should start with Set-AzStaticVNetIP. Idk why they include such kinds of questions.

JWS80 👍 4

E: Is correct however the command is no longer accurate. Set-AzNetworkInterface is the new command. C: You cannot change from dynamic to static in properties. In the portal go to your Virtual Machine, select networking, Select the Network Interface, Ip configurations, then the ipconfig at the bottom, where you can change it from dynamic to static

dhivyamohanbabu 👍 1

Correct answer E

GoldBear 👍 5

The answer is now C and E. You can use the Portal or Powershell to make this change.

Chette 👍 2 Selected: E

Correct answer E.

mestorrent86 👍 1

Correct E

Madbo 👍 1

E. Run the Set-AzureStaticVNetIP PowerShell cmdlet. To configure static internal IP addresses for Azure VMs, you can use the Set-AzureStaticVNetIP PowerShell cmdlet. This cmdlet sets the static IP address for a VM in a virtual network. You need to specify the name of the VM, the IP address to set, and the subnet in which the VM is located.

M_dehaan 👍 2

You will have to edit these properties in the NIC

flaviobrf 👍 4 Selected: C

The Set-AzureStaticVNetIP just works for classic, for new Vms its can be done straight in the Portal console: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/reset-network-interface

Driede 👍 3

That is not the VM properties tho. So the only valid answer is still E.

Doman01 👍 4

C is correct https://imgur.com/a/d118T7K You can also read how to do it here It is also shown here https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-networks-static-private-ip-arm-pportal E is not correct due to this: https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-networks-static-private-ip-arm-ps

mythjava 👍 1

correct answer is E. can also do the same in VM->Networking->Settings->Network interface name

kklohit 👍 3 Selected: E

Your company has two on-premises servers named SRV01 and SRV02. Developers have created an application that runs on SRV01. The application calls a service on SRV02 by IP address. You plan to migrate the application on Azure virtual machines (VMs). You have configured two VMs on a single subnet in an Azure virtual network. You need to configure the two VMs with static internal IP addresses. What should you do? A. Run the New-AzureRMVMConfig PowerShell cmdlet. B. Run the Set-AzureSubnet PowerShell cmdlet. C. Modify the VM properties in the Azure Management Portal. D. Modify the IP properties in Windows Network and Sharing Center. E. Run the Set-AzureStaticVNetIP PowerShell cmdlet

Mazinger 👍 1

To configure static internal IP addresses for Azure VMs, you should use the Set-AzureStaticVNetIP PowerShell cmdlet. This cmdlet allows you to specify the IP address that you want to assign to each VM. Here's an example command that assigns IP addresses to two VMs: Set-AzureStaticVNetIP -VMName "VM1","VM2" -IPAddress "10.0.1.4","10.0.1.5" | Update-AzureVM This command assigns the IP address 10.0.1.4 to VM1 and 10.0.1.5 to VM2. The Update-AzureVM cmdlet updates the VMs with the new IP addresses. Option A (New-AzureRMVMConfig) and Option B (Set-AzureSubnet) are not the correct cmdlets to use in this scenario. Option C (Modify the VM properties in the Azure Management Portal) is not the best approach since it is time-consuming and can be error-prone. Option D (Modify the IP properties in Windows Network and Sharing Center) is not applicable since the VMs are in Azure and not on-premises.

Shirsangshu 👍 1

coorect answewr given

myarali 👍 2 Selected: E

Set-Azure Static VNetIP: Sets the static virtual network IP address information for a virtual machine object. https://learn.microsoft.com/es-es/powershell/module/servicemanagement/azure.service/set-azurestaticvnetip?view=azuresmps-4.0.0

stacyneal 👍 2

Correct Answer E:

Pinkshark 👍 1

Agree with E

MVCChicago 👍 1

Correct Answer E:

NaoVaz 👍 4 Selected: E

Set-AzureStaticVNetIP - "Sets the static VNet IP address information for a virtual machine object." (https://docs.microsoft.com/en-us/powershell/module/servicemanagement/azure.service/set-azurestaticvnetip?view=azuresmps-4.0.0)

AZC054 👍 1

i.e :Set-AzureStaticVNetIP -IPAddress 10.0.0.7 ` https://docs.microsoft.com/en-us/previous-versions/azure/virtual-network/virtual-networks-reserved-private-ip

NTT_Sttg09 👍 2

Recently it uses Set-AzNetworkInterfaceIpConfig @config -Primary for that. https://docs.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-networks-static-private-ip-arm-ps

dv_evan 👍 1

correct

vhphuocvo 👍 1

The correct answer is E

justjeroen 👍 7

The answer here is E but it is already legacy. Now you should do with Set-AzNetworkInterfaceIpConfig

Sandeept1992 👍 1

Correct answer is E

Dhanya2022 👍 1

Set-AzNetworkInterface

Azure_daemon 👍 3

the correct answer is E, if you want to choose the portal, you have to find the interface of the VM and change the dynamic private IP to static, not the VM properties, so C is wrong

godchild 👍 1

because "properties" not only means "properties blade" but can also means the general characteristic of the VM.

josevirtual 👍 5 Selected: E

Set-AzureStaticVNetIP is correct, although an updated answer might be Set-AzNetworkInterface

Azure_daemon 👍 1

The correct answer is E

AzureLearner76 👍 4 Selected: E

Answer should be E but its really shocking since this is from the service management days (classic) not the resource manager , pointless question

HananS 👍 1

E is the answer crystal clear

pawel_ski 👍 2 Selected: E

Correct answer E. Although you can also change this option in the Portal. But not VM properties only NIC properties which is a separated object in Azure.

MYJ 👍 1

Selected Answer: E

JayJay22215 👍 2 Selected: E

Dunno, why so many ppl vote for C, because you cant edit stuff under "properties". You can under "settings", but it specifically states "properties"

beelee6973 👍 1

Correct answer E.

fml1996 👍 2

The Set-AzureStaticVNetIP cmdlet sets the static virtual network (VNet) IP address information for a virtual machine object.

arxxas 👍 3 Selected: E

Run the Set-AzureStaticVNetIP PowerShell cmdlet.

Tom34 👍 2

Correct answer E. But this method Set-AzNetworkInterface is obsolete. It should be like this. $vm = Get-AzVM -ResourceGroupName $vmInfo.ResourceGroupName -Name $vmInfo.Name $nic = Get-AzNetworkInterface -ResourceGroupName $vm.ResourceGroupName $nic.IpConfigurations[0].PrivateIpAddress = "10.0.1.20" $nic.IpConfigurations[0].PrivateIpAllocationMethod = "Static" $nic.Tag = @{Name = "Name"; Value = "Value"} Set-AzNetworkInterface -NetworkInterface $nic

timmytimtimo 👍 1

Correct answer is E

Irishtk 👍 2

Correct Answer is E.

googlearch 👍 1

Set-NetIPAddress in the newer version

adrien_m59 👍 1 Selected: C

Allfreen 👍 2

This is wrong, VM1->Networking->NIC to change under VM properties where as in answer section this is not described

Axial30z 👍 6

Adrien, in this case, I believe the correct answer is E I also thought C initially but when you read the option, it says 'Modify the VM properties'. You can't configure the static ip from the properties blade of the VM. Also following your link ref https://docs.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-networks-static-private-ip-arm-pportal To use the portal means going through the following steps which is not the VM properties VM>Settings.Networking Select NIC>Settings.IP Configuration Select NIC and change assignment

JayJay22215 👍 1

Wrong, because you cant edit within the properties menu. Its specifically called "properties"!

Snownoodles 👍 5

Set-AzureStaticVNetIP is for 'legacy resource" Correct method:Portal->VM->Networking->Network interface->IP configuration

londonboy 👍 1

E sounds correct to me.

arkadius 👍 3 Selected: C

C You should modify VM network interface IP in Azure portal

LeomHD 👍 1

I agree, in Azure Portal is possible to set static IP, the both option are valid?

rhanielcb23 👍 5

Set-AzureStaticVNetIP PowerShell cmdlet Correct answer E.

Quantigo 👍 24

Correct Answer E: Run the Set-AzureStaticVNetIP PowerShell cmdlet.

Saravana12g 👍 3

Test-AzureStaticVNetIP –VNetName xxx –IPAddress xxx and then Set-AzureStaticVNetIP

Adebowale 👍 1

What if the ip properties in the Network and Sharing center of the VM is changed

jellybiscuit 👍 3

It would work to start with. The problem is that the network interface in Azure would still be set to DHCP. If anything ever causes that IP to change, the server will be completely inaccessible (because you don't have console access).

Kopy 👍 1

why not Modify the VM properties in the Azure Management Portal?

jellybiscuit 👍 12

You could use the portal, but static IP settings are on the network interface, not the virtual machine.

CloudyTech 👍 2

E is correct

rawrkadia 👍 4

Are the pre AZ/ARM cmdlets and management paradigm even on the exam?

ppp131176 👍 4

E is correct:

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

Option C is correct because in the Azure Resource Manager (ARM) model, you assign a static internal IP address by modifying the network interface properties via the Azure portal. While the option broadly says "VM properties," the setting is accessed through the VM's networking blade, which leads to the underlying NIC configuration where the private IP allocation method is set to Static.

Why the Other Options Are Wrong

Option A (New-AzureRMVMConfig) is used to create a local VM configuration object, not to update an existing VM's IP configuration. Option B (Set-AzureSubnet) is not a valid cmdlet for configuring a static IP on a VM. Option D is incorrect because changing IP settings inside the Windows guest OS via Network and Sharing Center will break Azure networking. Option E (Set-AzureStaticVNetIP) is a deprecated Azure Service Management (Classic) cmdlet and does not apply to ARM VMs.

Community Comment Notes

Multiple commenters point out that Option E is a legacy cmdlet for Classic VMs, as DT95 noted, "E is wrong in 2024. The Set-AzureStaticVNetIP cmdlet is part of the classic (ASM) PowerShell module". While jellybiscuit correctly observes that "static IP settings are on the network interface, not the virtual machine," Option C remains the closest valid ARM-based method among the choices, assuming "VM properties" implies the networking properties accessed through the VM blade.

Official Reference

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-networks-static-private-ip-arm-pportal

Exam Strategy

For AZ-104, always eliminate any options using Azure Service Management (ASM) cmdlets like Set-Azure* without the Az prefix, as the exam strictly tests Azure Resource Manager (ARM) deployments.

Related Analysis

Practice All AZ-104 Questions

Access 100 questions with complete answers and detailed explanations.

View Full AZ-104 Practice Test →

← Back to AZ-104 Study Guide