Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, February 28, 2019 7:03 PM
Hi,
When we do not use a VM on Azure, we generally stop the VM. Please let me know its impact in terms of technical and in terms of billing.
Regards
TekQ
InTechSys
All replies (6)
Friday, March 1, 2019 7:08 AM ✅Answered | 2 votes
Hello
Make sure when it is stopped it should be deallocated state, But keep in mind that if your have any attached storage, you will still be incurring charges for that - Premimu disk will incur charges for the entirety of the volume size used or unused while standard storage will incur charges for used space.
Hope thatr helps,
Isaac Oben MCITP:EA, MCSE,MCC <a href="https://www.mcpvirtualbusinesscard.com/VBCServer/4a046848-4b33-4a28-b254-e5b01e29693e/interactivecard"> View my MCP Certifications</a>
Friday, March 1, 2019 8:39 PM ✅Answered | 1 vote
Hello,
Yes the public and private IP addresses might change if you deallocate the VM and then bring it back online.
To prevent this, you will need to go to the NIC settings for that VM on ARM interface and set the IP as static for private (Please do not do this on the OS but on the Azure portal NIC config).
You can go to the Services, public IP and set that as static as well. Also keep in mind tht the public IP if you set it to static/reserved you will be charged for that even when the VM is deallocated but the charge is pretty minimal
Hope that helps,
Isaac Oben MCITP:EA, MCSE,MCC <a href="https://www.mcpvirtualbusinesscard.com/VBCServer/4a046848-4b33-4a28-b254-e5b01e29693e/interactivecard"> View my MCP Certifications</a>
Saturday, March 2, 2019 1:25 AM ✅Answered
InTechSys, glad to know that it was helpful.
Please 'Mark as answer' if any of the replies helped, so that others in the community who are looking for similar question, can benefit from it.
Thanks Isaac!
Karishma Tiwari - MSFT
Thursday, February 28, 2019 7:11 PM | 2 votes
Hi,
In 'Stopped' state it will continue charging on the VM resources like disk
Regards From: Exchange Online | World of Cloud Computing
Thursday, February 28, 2019 11:29 PM | 2 votes
Stopped (Deallocated) is the status you will see in the Azure portal, that indicates the VM is stopped and you are not being billed the hourly compute time for the VM while it is in that state.
The VM’s OS and data disks remain intact in Azure storage and can be used to restart the VM later. However, the temporary (scratch) disk associated with the VM is released and any data on that disk could be lost. You continue to accrue charges for the Azure storage needed for the VM’s OS disk and any attached data disks.
Stopped state but not deallocated:
When performing a Guest OS shutdown or restart ( ie., a shutdown or restart operation initiated from the Guest OS running inside the VM ), the VM configuration will not be deallocated from fabric resources. Note that it may require a few minutes for the Azure Portal to reflect that the VM is in a "Stopped" state in this scenario, because we are performing an OS shutdown inside the VM rather than through an Azure management endpoint.
VMs shown in a "Stopped" status will continue to accumulate compute charges, because fabric resources are still being reserved for these VMs. However, this also means that DIPs and VIPs are preserved for VMs in this state, so you don't have to worry about VMs and cloud services getting different IP addresses when they are started in the future.
Few resources to refer to:
https://blogs.technet.microsoft.com/keithmayer/2013/06/19/best-of-teched-2013-windows-azure-new-choices-and-flexibility-for-stopped-vms/
Friday, March 1, 2019 7:44 PM
I would like to say thank you for all. I would like to share my scenario. I connected VM using RDP exe. After doing some work on VM. I turned off VM OS or you can say I shut down the windows machine.
Then, I logged in azure portal. Clicked the VM in virtual machine. Then I clicked Stop. Now I see Stopped (deallocated).
I read about Stopping versus Stopping (deallocated). If I am right, stopping (deallocated) charges very less than stopping but in case of stopping (deallocated) Public IP will be changed in next start. Am I right? What about Private IP in case of stopping (deallocated)?
InTechSys