Issue: The "Pricing Tier" dropdown is empty due to which the create Translator resource workflow fails as the form validation is unsuccessful.
Background: I am trying Azure for the first time so I have free credit and free testing for 30 days on this account.
What I have tried:
I went to create resource and selected "Translator"
I clicked create and then filled in the details but the Pricing Tier dropdown is empty, so I could not select anything:
Next, I clicked on "Review and Create" but it does not create as validation failed:
Now, I am stuck and don't know how to go forward. Appreciate any help that I can get.
This is a bug on our end and we are working to fix it. Meanwhile, as a workaround, can you try changing between subscriptions/regions and the pricing tier should load.
Related
I have created a new work item type "Risk" and would like to add to the backlog shortcut as shown in the image below. My version of Azure DevOps is hosted by Microsoft. Pls advise :)
I found it! Under Organisation Setting > 'Your custom process' > Backlog Levels > Under Iteration backlog, you can add more work items over there
I am new to azure and i am exploring it now, as first step i created a free azure account and in that i created a Resource group and an App service to that resource group.
When i try to access the Url https://azurehome.azurewebsites.net/ its giving an error 'The service is unavailable.'
any help on this ?
Please follow this document to troubleshoot:
https://learn.microsoft.com/en-us/azure/app-service/troubleshoot-http-502-http-503
By the way, this problem may be caused by the region you choose, trying to change the region may be effective. I'm using Central US and it works fine.
If it still doesn't resolve, please provide more information.
If you need support, you can click this link:
https://azure.microsoft.com/en-us/support/options/
This is part of an exercise of MS Learning, https://learn.microsoft.com/en-us/learn/modules/create-release-pipeline/5-deploy-to-appservice. On manual creation of Azure App Service, I am getting the error.
Please help with the Cause and Resolution
Steps to recreate:
azure.com >> Azure App Service >> +Add > add the project details like subscription, resource group etc... >> Review+Create, Below error:
The template deployment 'Microsoft.Web-WebApp-Portal-3994ede8-a307' is not valid according to the validation procedure. The tracking id is 'ca7e085f-a756-4344-bfe1-07444ff0fe0e'. See inner errors for details.
I'd like to know what is causing this error - and how I can avoid it?
So looking at the output in the network tab of the browser i saw this:
The requested app service plan cannot be created in the current resource group because it is hosting Linux apps. Please choose a different resource group or create a new one.
So deleted the app service plan/web app and now it works.
MS, please show us the error ...
I was able to fix this error by simply recreating webapp, and selecting another location. From Central Usa to South Central USA. It worked for me
Changing the location, helped me in fixing this error.
I was facing the same issue so I changed the location from "East US" to "East US 2" and it also worked for me.
I'm new to Azure platform. I'm trying free trial and creating a CI/CD setup for docker by following from the below link.
https://www.azuredevopslabs.com/labs/vstsextend/docker/
I have no issue until setting up build definition. I'm getting below issues when doing changes in the release definition.
when i click on "Authorize" button in azure subscription, I'm getting below issue.
Please let me know what mistake i am doing.
well, the text says it all. you are trying to create a connection with a name that already exists. you need to call it something different or rename the existing one
I have created a new service connection and mapped in the release definition.
Click on Manage link
Click on New service connection button
at top right corner
Select Azure resource manager
Once you select the respective option and click Next. Enter valid name and select respective subscription and resource group details.
When I try to create a new Azure Redis Cache and choose a location I just get a "There are no locations available." message.1 Setting everything else first still results in the same error. Refreshing the page doesn't resolve the issue. The problem occurs in both IE and Chrome.
Thanks for reporting this. It seems to be a bug in the portal. I can reproduce it if I click "Location" immediately after the "New Redis Cache" blade opens. However, if I wait a few seconds before clicking "Location", it doesn't repro.
As a workaround, if you close and reopen the "Location" blade it should populate correctly.
We will also work on fixing this in the portal.
Finally, for any issues with Azure Redis Cache you can contact us via email at azurecache#microsoft.com.
After working with the Azure team via email we were able to narrow down the problem and find a workaround.
There are 3 problems at work here that result in my symptoms:
The various New blades in the portal will default you to a disabled subscription. I believe they currently default to the first subscription (oldest) which may not be an active subscription. This results in the default behavior upon choosing a blade to be that of no-subscription.
The New Redis Cache blade will only show locations if you have selected a valid (not disabled) subscription. This behavior differs from the other New blades (such as Create VM) which will show you locations even if you have a disabled subscription selected.
Changing the resource group will automatically change the subscription and lock it, but changing the subscription in this way will not trigger an update to the blade. This means that the locations don't get updated for the new subscription because the subscription-changed-event (made up name) was not fired. In my case, I was always changing the subscription by way of changing the resource group, so I was never able to set the location.
The workaround:
Simply change to an active subscription before choosing a resource group. This will cause the locations list to be updated, and you can then choose a resource group after.