I've just checked my current Azure usage, and I'm seeing an item called...
Premium Storage - Page Blob/P10 (Units) - US West
This item is quite expensive, but I don't know what it is, or how it's been allocated, or how to remove it.
I've checked my storage accounts, vm's, and databases, and confirmed that they're all in Australia.
This is the first time I've noticed this "US West" storage item.
The only new thing I've added to Azure recently is an "S0 Standard (10 DTUs)" database account. However this says it's located in Australia, and it currently has nothing in it. I've checked the resource cost, and it's currently showing $0.
How do I go about figuring out what this mystery storage resource is?
I think I've traced it. It's the disk for one of my VM's. I don't know why the location for the storage is "US West", when the location for the VM is Australia. The VM was created as an experiment and isn't currently being used. I was testing out the new ARM deployment type. My fault for not fully understanding the pricing before creating the resource. I assumed storage cost would be negligible, and that the VM wouldn't cost much if it was deallocated most of the time. Anyway I'll delete the VM, and do more reading about pricing before trying it again.
Related
I created a new Azure Machine Learning Workspace and Compute Instance to work through some Python ML tutorials. I was stuck on this issue for a few days. While I was waiting for assistance, I stopped the compute instance.
Looking through the Cost Analysis for this Resource Group, it looks like I'm being charged even though the Compute Instance has been stopped for a few days.
Is there a pay-as-you-go version of AML Compute Instance so I don't get charged when the instance is turned off?
EDIT:
Hm. It looks like the bulk of the cost is coming from a Load Balancer and Storage not the Compute Instance (assuming this is the "VM" shown). The Compute Instance was stopped in the AML Studio.
Its unclear to me which Azure Resource the Load Balancer represents.
Also the only Storage account in this Resource Group has 3 empty Containers...
Maybe these costs were associated with setting up the AML Workspace?
The answer is yes. As seen in the docs here, there is a Load Balancer resource that is provisioned as part of the AML Workspace. This resource is not visible in the Resource Group (which was throwing me off). It appears to accumulate cost even with the Compute Resource turned off.
Since yesterday, I'm trying to create new VM and I'm not able because the majority of the sizes are not available for my region, West Europe. Using Azure Portal I get all D series greyed:
I tried Azure Reservations with same result:
I suppose there are issues in this and another regions.
But then I tried to get availability using CLI tool az, following this reference. The, executing referenced command I get this list of available sizes:
It seems contradictory information, because I see some D series VM.
May it be that they are available in general, not taking into account current occupation?
Is there any az command to get actual available sizes in my region?
Da/Das series VMs use AMD CPU. However, based on my test, they are not available in location West Europe.
The normal D series VM should be available in West Europe. There are several reasons which may prevent you from choosing it:
You have reached your CPU resource limitation in that region. To solve this, you may request an increase in CPU quota limits per Azure VM series
Some Azure subscriptions (trial, MSDN developer, student trial and so on) can only create limited resources in limited locations. To solve this, you may update your subscription to a pay-as-you-go one.
Other reasons. You may directly contact the Azure Support team by submitting a support request on the Azure portal.
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:
I recently created and renamed an additional pay-as-you-go subscription in order to segregate billing by site. Now, however, when I try to create a VM the majority of the sizes no longer seem to be available. I have tried changing regions, no change. What might be the cause for this?
I had the same issue, I had an MSDN subscription which allowed me access to all VM sizes, but when I created a new subscription there was a very limited set of VM sizes available to me. This was due to Capacity Management restrictions.
I raised a Subscription support ticket with Microsoft (subscription support is free, no need to purchase a support plan) and they are in the process of lifting the restrictions.
Include in the support ticket what VM sizes, number of cores, Azure region, subscription GUID and amount of storage in TB you will want to use - these are the first things they asked me.
I have a cloud service and a storage account deployed using the classic resource manager in the East US region; there is also a classic backup vault in the West Europe region.
Due to high latency, I want to move all of these resources to the UK South region, which is the closest one to me and others using these services. I have created a new resource group in the UK South region, however, when I try to move my existing classic resources to the new resource group, it says:
Classic resources must be moved separately and aren't displayed below.
Reading the article it linked to, it says that to move classic resources when experiencing this limitation, I need to contact support to have this operation done manually.
I do not have a support plan and am hoping not to buy one for this single task. Is there any other way around this limitation?
I think that you can walk around it by:
1. Create a new blank cloud service in your new resource group in UK South region.
2. Modify the deployment process to deploy the code to the newly created cloud service.
I hope this helps.
As you mentioned that it is limited by Azure. The following is snippet from the official document.
When moving resources from one resource group to another resource group within the same subscription, the following restrictions apply:
Virtual networks (classic) cannot be moved.
Virtual machines (classic) must be moved with the cloud service.
Cloud service can only be moved when the move includes all its virtual machines.
Only one cloud service can be moved at a time.
Only one storage account (classic) can be moved at a time.
Storage account (classic) cannot be moved in the same operation with a virtual machine or a cloud service.
As Toan nguyen mentioned that we need to redeploy it if you don't want to call Azure Support.