I am just exploring Azure and I made a Virtual Machine using the portal and I deleted that after two hours or something.
In my cost management I can see that I am still paying for that resource group that contained components of the Virtual Machine, it is been a week since I deleted it.
I am still paying for that resource group even though I can't see it in my resource groups, neither on the portal nor on Powershell.
Is this a common issue?
As per this doc, I suggest you check if all disks attached to the vm are not deleted.
For managed disk, please follow this to find and delete them.
For Unmanaged disks(the vhd files stored in azure blob storage), please follow this to find and delete them.
Delete any orphaned Network Interface Cards (NIC) and Public IPs that were associated with the VM. They are billed even when the VM is deleted.
Update:
run powershell in azure portal:
Related
I am testing out Azure VMs as a disaster recovery option for my organization. I'm on an Azure AD trial. My use case is this: Ideally, I'd like to have an image standing by with all the software that my users need, pre-installed, and hooked up to our Azure AD domain. Then, if we should need our DR environment, I'd like to spin up 1..n VMs from the image, send my users the RDP connection files, have them log in with their Office 365 credentials (we also subscribe to Azure AD Premium P1), and get back to work using OneDrive.
I created a VM and populated it with the settings and software I need for my users. It has a local admin, and I confirmed I could log in using my Azure AD credentials. Then I ran sysprep /generalize and created an image of the virtual workstation. So far so good. As I could no longer access the original VM, I deleted it. The original VM was of the DS3_v2 size.
Now I'm going to create a new VM from my image to test. In the Azure portal, I go to Virtual Machines -> Add. I select my image and Resource Group. However, when I go to select a Size, I get the following error message:
"4 vCPUs are needed for this configuration, but only 0 vCPUs (of 4) remain for the Standard DSv2 Family vCPUs." I cannot select any of the available options. The "Troubleshoot" link directs me to a page instructing me to request a quota increase, but that shouldn't be necessary; I de-allocated [edit: deleted] the old VM and its 4 vCPUs so I could create a new one. Why is Azure telling me I only have 0 vCPUs left in my trial subscription?
This morning when I tried again, the console allowed me to select a size. It appears that there is a very substantial delay between when you delete the VM and when Azure marks the vCPUs as available to use once again.
I have a old vm on microsoft azure, that I need to delete. There are a bunch of resources over that vm (vnet, public ip, disk, ...)
As I don't want to have unused resources, is it possibile to list all resources linked to another?
thank so much!
N.
there is nothing built-in in Azure to achieve this, kinda. One way of doing this (if you are not using shared virtual networks, backups, etc) is to put all the resources that logically relate to the vm in the same resource group and just delete the resource group.
an alternative would be to create a script to delete all the related resources along with the vm
I have a premium Azure Managed Disk (SSD) in the same region as a Windows VM, but when I go to attach it via the Azure portal (settings -> Disks -> + Add data disk) the drop down under name says "No managed disk available" (see below). What do I need to do?
To use Premium storage, you'll need a Premium Storage enabled VM size like the DS-series or GS-series virtual machine. You cannot use premium storage disks with VM series that are not Premium Storage-compatible. For details, see Premium Storage: High-Performance Storage for Azure Virtual Machine Workloads.
I ran into this problem after I had detached a disk from one VM and tried to attach it to another VM. Apparently those changes take some time to propagate through the system, and the solution for me was to log out of the Azure portal and then log back in again.
It's a 3 step process, once you create & attach, you need to mount it as well.
Follow the instructions presented here.
lsblk -o NAME,HCTL,SIZE,MOUNTPOINT | grep -i "sd"
This command will show you if you have the disk or not.
Before:
After:
I faced the same problem and it turned to be because I had chosen the incorrect resource group. Under Basics tab, you need to check the resource group where the Disk belongs to and make the appropriate selection. This solved the problem for me.
I faced the same problem, and I checked so many times if the vm would support premium LRS and mine did, but still not seeing the disk I just created.
I solved it by just refreshing the whole portal after creating snapshot disk, and then every disk that I can possibly attached shows up.
I faced the same problem, and I checked so many times if the vm would support premium LRS and mine did, but still not seeing the disk I just created. Also tried to refresh the whole portal but still issue didn't fixed. After that i checked my disk was not created in availability zone. And my VM was in availability zone 1. once i created the disk in availability 1. it appeared in my new VM data disk.
I want to migrate resources (VMs, networks, gateways ...) from a tenant /client with a subscription to another tenant /client with another subscription, with the exact same parameters, how can I do that ? (the move function works only for subscriptions in the same tenant / client, if I download vhd of the VMs I must recreate manually the VMs configuration
The best and most reliable way is through Azure Billing Support. It is free support service and can handle that type of support questions.
Couple of very important things though (hard requirements that cannot be changed):
target subscription must be empty.
Service Administrator e-mail should be same for both subscriptions
There should not be co-administrators in both subscriptions for the time of migrating resources
Some services (i.e. Application Insights) cannot be moved (which services cannot be moved is determined by the support engineers)
For information, I didn't managed to migrate the VMs the way I wanted. I've finally recreate the network infrastructure on the destination tenant, poweredoff the VMs, use azcopy AzCopy.exe /source:https://<sourceaccountstorage>.blob.core.windows.net/vhds/ /Dest:https://<destaccountstorage>.blob.core.windows.net/vhds/ /sourcekey:<sourceaccountstoragekey> /destkey:<destaccountstoragekey> /pattern:<name of VHD to copy>.vhd to move the VHDs from the source storage account to the destination storage account (13 min for 130 Gb in westeurope location), and recreate the VMs with powershell with the VHDs New-AzureRmNetworkInterface, New-AzureRmVMConfig, Add-AzureRmVMNetworkInterface, Set-AzureRmVMOSDisk and New-AzureRmVM.
I don't know how I had two virtual machines in Windows Azure, one application server that was stopped and one running database server, and all of a sudden, the machines no longer exist.
I have these questions:
is there a way to restore the machines?
if not is there a way to delete the storage?
Go to Virtual Machines.
Click on Disks.
Click on any remaining disks.
Click on Delete Disk - there is an option to "retain", so make sure you choose delete.
Once all the disks are deleted, then delete the storage container.
You can delete the storage with the help of steps specified in the below post
Follow this post steps
You may have hit a billing limit for a subscription with a limit. This typically happens with MSDN and Trial accounts. Once the limit is hit, Microsoft deletes any VMs running in the subscription. For IaaS VMs the actual disks still exist in storage and the VMs can be rehydrated from there once the account has some money in it or the monthly limit is reset by a new month starting. For PaaS instances, the package and configuration file is presumably still deployed to Windows Azure so, again, the service can be rehydrated when the account is flush with money.