Can't able to purchase GPU based VMs in Azure [duplicate] - azure

I am new to Azure and started a new free trial account. As one of the first things to try, I decided to create a VM. As I followed steps in Azure portal, I was stuck when it came to 'Select Size', because all of them are greyed out; and per my understanding, the field is required.
I was using the default region (USEast), and I selected no AZ and 'Ubuntu 18.04 LTS' as the image the VM is based upon.
I googled this issue on the internet. And I have done the following to rectify the issue but no luck:
switched to use different PC with different IP (as some suggested)
"clear All filter' in Select Size window and specified VM size
selected different VM images
ensured there is a credit attached to my subscription (as some suggested)
ensured there is no resources created to avoid hit the quotas (as some suggested)
This is something very basic, and it should've worked out-of-the-box. I am disappointed with the experience. But I want to give it the benefit of doubt and will continue to try out Azure if this issue is resolved. Maybe something very simple that I might've missed on my side.
Thank you so much for the help in advance.

Due to COVID-19 most of the enterprise user working from home and the usage of Azure and Microsoft service has increased a lot. Microsoft says that there has been a colossal 775 percent increase in usage of its cloud services.
All that Azure usage appears to have led to users in many regions "observing deployments for some compute resource types in these regions drop below our typical 99.99 per cent success rates". Which goes a long way towards explaining the inability to create resources as The Register revealed last week.
Concurrently, we monitor support requests and, if needed, encourage customers to consider alternative regions or alternative resource types, depending on their timeline and requirements.
Try to change your deployment region.

Most of the VM's we are unable to create. This is due to heavy toll on the resources.
You can read more here : https://azure.microsoft.com/en-us/blog/our-commitment-to-customers-and-microsoft-cloud-services-continuity/
For time being seems like we have to opt for some other size.

Related

When Creating VM in Azure 'Select Size' is Greyed Out

I am new to Azure and started a new free trial account. As one of the first things to try, I decided to create a VM. As I followed steps in Azure portal, I was stuck when it came to 'Select Size', because all of them are greyed out; and per my understanding, the field is required.
I was using the default region (USEast), and I selected no AZ and 'Ubuntu 18.04 LTS' as the image the VM is based upon.
I googled this issue on the internet. And I have done the following to rectify the issue but no luck:
switched to use different PC with different IP (as some suggested)
"clear All filter' in Select Size window and specified VM size
selected different VM images
ensured there is a credit attached to my subscription (as some suggested)
ensured there is no resources created to avoid hit the quotas (as some suggested)
This is something very basic, and it should've worked out-of-the-box. I am disappointed with the experience. But I want to give it the benefit of doubt and will continue to try out Azure if this issue is resolved. Maybe something very simple that I might've missed on my side.
Thank you so much for the help in advance.
Due to COVID-19 most of the enterprise user working from home and the usage of Azure and Microsoft service has increased a lot. Microsoft says that there has been a colossal 775 percent increase in usage of its cloud services.
All that Azure usage appears to have led to users in many regions "observing deployments for some compute resource types in these regions drop below our typical 99.99 per cent success rates". Which goes a long way towards explaining the inability to create resources as The Register revealed last week.
Concurrently, we monitor support requests and, if needed, encourage customers to consider alternative regions or alternative resource types, depending on their timeline and requirements.
Try to change your deployment region.
Most of the VM's we are unable to create. This is due to heavy toll on the resources.
You can read more here : https://azure.microsoft.com/en-us/blog/our-commitment-to-customers-and-microsoft-cloud-services-continuity/
For time being seems like we have to opt for some other size.

Cannot create Compute Instance Microsoft Azure ML

I am new at working with Microsoft Azure and I am trying to open a Notebook from the Azure Machine learning studio.
Every time I try to create a new compute it says Creation failed so I cannot work. My region is francecentral and I have tried different Virtual Machine size
Your reason might be explained here:
As demand continues to grow, if we are faced with any capacity
constraints in any region during this time, we have established clear
criteria for the priority of new cloud capacity. Top priority will be
going to first responders, health and emergency management services,
critical government infrastructure organizational use, and ensuring
remote workers stay up and running with the core functionality of
Teams.
If you qualify for this category, you should reach out to Azure Support or your Microsoft representative. If not, you need to keep retrying (might work better at night) or try a different region.

Contradictory information between Azure Portal and az command getting available SKUs for VMs

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.

How is Geo Redundant Storage charged on Microsoft Azure?

SO I have been using the azure 3 month trial, to test out whether I want to use Microsoft Azure to host a project I am working on, however I have been very confused as I have run out of "Geo Redundant Storage" in the first month and I don't really understand why.
I have read this: https://www.windowsazure.com/en-us/pricing/details/ and the only thing I can make of it, is that it takes an average of how much storage you are using across a month, eg as long as I am using less then 35gb (for a 35gb limit) on average of storage space I am in the clear.
So under my Azure Subscriptsions 'STORAGE (GB/MONTH) - GEO REDUNDANT' it says '101.027% of 35 GB/month' (so I have reached my cap).
But I don't understand why this would be happening, all I have is a simple server with a nodejs web application and a redis database (pretty much an empty at the moment), all running on an ubuntu VM, and as I can't login and check storage now because it is disabled, but I am pretty sure it is nowhere even near 35gb total storage and never has been?
I am hoping someone can explain how the azure storage is charged or if I have missed something silly?
Edit: It just hit me that it could be redis, doing crazy things with IO? not sure if this is possible, but if it is, would I be better to use locally redundant storage and pay for locally redundant storage transactions?
Edit 2: On my graph it says I had been using 1.96gb / day. So that means its not the total harddrive space per month, is it harddrive space / day? (using 2gbs of data probably sounds about right with the OS included, if this is the case, that means they give you less then 2gb space on the trial, seems minute??)
This caused due to the limitation on the geo redundant storage I have faced the same issue to fix this just disable geo redundant storage from the Windows Azure preview portal.
Open the Windows Azure preview portal.
Select Storage left.
The select your storage.
Click Configure on the top.
Turn off geo-replication.
I hope this will help.
This is probably caused by the image of your Ubuntum VM. If you read the pricing details (the link in your question) you'll see this:
Compute hours do not include any Windows Azure Storage costs
associated with the image running in Windows Azure Virtual Machines. These costs are billed separately.
How large was the VM you created?

Doubts about Windows Azure Platform Introductory Special

I'm considering to join the Windows Azure Platform Introductory Special, but I'm a little bit afraid of losing money with it. I don't wanna develop any fancy large scale application, I want to join just to learn Azure and do my experiments, what should I be afraid of?
In the transference, it says: "Data Transfers (per region)", what does that mean?
Can I put limits to stop the app if it goes over this plan in order to avoid get charged?
Can it be "pre pay" instead "bill pay"?
Would it be enough for a blog?
Any experiencie so far?
Kind regards.
As ligget pointed out, Azure isn't cost affect as a host for an application that can be easily deployed to a traditional shared hosting provider. Azure's target market are those that want dedicated resources without the need to micro-manage the infrasture and the capability to easily scale up/down based on demand.
That said, here's the answers to the questions you posted:
Data Transfers are based on bandwidth in and out of the hosting data center. bandwidth for communication occuring within components (SQL Azure, Windows Azure, Azure Storage, etc...) in the same datacenter are not billable.
Your usage is not currently capped when the free quotas are used up. However, you will recieved warning emails when those items approach their usage threadsholds.
There is the option to pay your subscription using a PO, but the minimum threshold for most of these operations is $500/month. So as a hobbyist, its unlikely you're wanting that route.
The introductory special does not provide enough resources for hosting a 24x7 personal blog. That level includes only 25hrs of compute resources. Each hour a single instance of your application is deployed will count against this, even if the application received no traffic. Think of it like renting office space. You still pay rent on the office even if there are no customers there.
All this said, there's still much to be learned with the introductory special. The azure development tools allows you to work with Windows Azure and Azure storage locally and get a feel for how they work. The introductory special then lets you deploy those solutions so you can see what works and what doesn't (not everything that works locally works hosted).
I would recommend you host your blog somewhere else - it's a waste of resources running it on Azure and you'll find much cheaper options. A recently introduced extra small instance would be a better choice in this case, but AFAIK it is charged separately as of now, e.g. even when you have an MSDN subscription those extra small instance hours do not count towards free Azure hours that come with the subscription.
There is no pre-pay option I know of and it's not possible to stop the app automatically. It'll be running until the deployment is deleted (beware! even if suspended/stopped the deployment will continue to accrue charges). I believe you will be sent a notification shortly before reaching your free hours threshold.
Be aware that when launching more than 1 instance you are charged for every hour of every instance combined. This can happen for example when you have more than one role in your Azure project (1 web role + 1 worker role - a separate instance will be started for each role).
Data trasfer means your entire data trasfer: blobs/Table storage/queues (transfers between your hosted service and storage account inside the same data center are free) + whatever data is transfered in/out of your hosted application, e.g. when somebody visits your pages. When you create storage accounts and hosted services in Azure you will specify a region that will be hosting your account/app - hosting in Asia is slightly more expensive than in Europe/U.S.
Your best bet would be to contact Microsoft with these questions.

Resources