Really puzzled why I am not seeing all locations - only 4 - US West, US East, Japan West and Japan East in my trial subscription. Is there any filtering I inadvertently setup?
Any pointers would be really helpful
Shas
I am giving many workshops for Azure and I see this behavior a lot for Azure Passes (also kind of trial accounts) but have not seen this for Azure Trials.
I noticed that I have more location options in the new Azure portal (https://portal.azure.com) and less in the old management portal (https://manage.windowsazure.com).
Also to consider, not all services are available at all locations. But the standard services like VMs or storage should be available everywhere. You can check via the service overview whether your desired service is available.
Related
I want to create an Azure function app in West Germany region, however that fails with:
This region has quota of 0 instances for your subscription. Try
selecting different region or SKU. (Code:
SubscriptionIsOverQuotaForSku)
I could create the Azure Function App in another region, but I want to understand why I am unable to create an Azure Function App in the West Germany region.
I already checked the quotas of my subscription, but there I can't find anything about Azure Functions:
I also checked Products available by region which confirms that Azure Functions are available in the West Germany region:
So, why can't I create an Azure Function App in the West Germany region?
One of the reasons and resolutions could be followed as #skin suggested:
It may be that all resources allocated to AF’s in that region are exhausted. Try again tomorrow.
Even the Microsoft documentation shows quota available for the products by region, they have certain limits for the Subscription level in terms of Azure Compute Units allocation because the Hardware Configuration of the Function App is not specified.
You can visit this MS Doc1 & Doc2 for the ACUs Quota allocation per instance and Hosting Plan based.
And also, Same issue registered in Microsoft Q&A Forum #878011 where #MayankBargali-MSFT explained the cause of the error you mentioned regarding why quota is limited on the location and subscription level.
Also, you can mail to AzCommunity#microsoft.com by stating your business justification and details for quota increase request along with the Azure Subscription Id, Azure Resource Name and the Issue Time of occurrence in UTC.
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.
Azure Germany Central shows that WebApps and CosmosDB are available in the Azure Germany Central region, but they're not showing in the Webplans or the individual items.
MCD (Microsoft Cloud Deutschland) is a completely separated cloud thats why you won't be able to see it at portal.azure.com, you may want to start here:
https://portal.microsoftazure.de
Microsoft Cloud Deutschland does not exist any more, because Microsoft now has new Data Centers in Germany. (See https://learn.microsoft.com/en-us/previous-versions/azure/germany/germany-migration-main)
According to Microsoft, the Availability Zone "Germany West Central" (GermanyWestCentral) supports CosmosDb. Though I do not see it offered in the portal yet (May 2022).
See
https://azure.microsoft.com/en-gb/global-infrastructure/geographies/#geographies
and
https://azure.microsoft.com/en-gb/global-infrastructure/services/?regions=germany-west-central,non-regional&products=cosmos-db
At some point about a month ago we are not able to create Cloud Service (web/worker roles) in Azure in North Central US region in one of our subscriptions. Nothing is mentioned at official page here http://azure.microsoft.com/en-us/regions/#services. We can do it in our old MSDN subscription, but cannot do it in new Pay-As-Go one.
Old portal doesn't list North Central in the list of available regions. New portal allows to select it but then some general error happens when we try to create the service. Cannot find any official information about it.
Does anyone know what is going on?
We contacted Microsoft. Apparently, they try to unload North Central US datacenter as it is one of their oldest ones. We really wanted this particular, and they let us use it, just gave us access back.
I am having trouble creating an Azure Search instance from the preview portal:
Search creation failed in resource group x.
I have tried different combinations of:
resource groups (even created a new one)
regions (East US, West Europe, North Europe)
pricing tiers (both free and standard)
What am I doing wrong?
Just to close on this issue, we have determined that there was an issue with the Azure portal in a recent update that is causing new subscriptions to fail to create new Azure Search services. This would explain why it worked for me but failed for you (as I suspect you have a new subscription).
The Azure portal is working to roll back this change. I am still waiting to get the time but I am hopeful this should happen in the next day or two.
I really apologize for this issue.
Liam
Its advisable to check the limits while planning to create azure search. here are some details:
https://azure.microsoft.com/en-us/documentation/articles/search-limits-quotas-capacity/