I am trying to delete everything related to a mobile app back-end I previously created, and I was able to delete everything but the app service plan.
It shows that the App service plan has no connected apps and no pricing tier, but I still can't delete it:
And when I try to click on the plan to see its details, the portal goes into an infinite loading state and nothing else happens:
Can anyone help me solve this problem?
I had a similar issue. The app service plan couldn't be deleted, but I wasn't able to access is properly from the Azure Portal. I managed to remove the plan like this:
Make sure all related apps (web jobs, ...) were removed.
Open PowerShell and log in to your Azure account: Login-AzureRmAccount.
Remove the app service plan: Remove-AzureRmAppServicePlan -Name <name> -ResourceGroupName <resourcegroup>.
If you delete the ResourceGroup it is located in, it will dissapear.
Nowadays it's possible to move most resources between ResourceGroups.
So you can create a new ResourceGroup, for example "ToBeDeleted", and then move the AppServicePlan to "ToBeDeleted" and then remove the ResourceGroup.
Once I had a WebApp in an App Service Plan (only one). There was some problem with the Aplication, and it was consuming all the CPU of the plan. I then moved the WebApp to another plan. It started to consume all the CPU (~100%) in the new (destination) App Service Plan.
After moving the app, in Azure portal, the original App Service Plan appeared as having "0 apps, 0 slots" (empty), yet the CPU was still around 100%. Weird!
Azure wouldn't let me remove that empty origin App Service Plan, telling me to first remove all the App it contained (which should be none).
I guessed Azure had registered the movement of the WebApp to the destination App Service Plan, yet some process was somehow stuck in the original App Service Plan, and until the process wouldn't end, I wouldn't be able to remove the App Service Plan (hence I would pay for it).
My trick here was to Scale Down that original App Service Plan. It was Premium, and I scaled it down to Free. When you scale up/down, Azure migrate deploys your app on a new set of machines. That is the stuck process would then forcely disappear. No new process was spawned on the new machine, as Azure had no account of any app being deployed on that App Service Plan anyway :)
Once scaled down to Free, I was instantly able to remove the empty plan.
So, in case you have any such problem, scale Up or Down the plan. It will assign new VMs, with no remaining processes nor new app process (as no apps are registred to the empty plan!)
Make sure no Resource Group is attached to the Service Plan.
I had the same issue and below fix worked for me.
Go to Resource Group tab in Azure portal.
Delete the attached Resource Group and then App Service Plan will delete automatically.
To confirm, go to All Resource tab and you should not see that App Service Plan anymore. Refresh if required or wait if delete is still in-progress.
Hope that helps.
I have just delete a service plan right now without issues.
Looks like any transient situation in azure Web Apps, try again/verify in a few minutes.
If the problem persist you can create a support ticket here:
Support Ticket
After deleting the Recourcegroup, it's no longer possible to rech the Service Plan over the portal!
If you don't have some Important things running on them, you can cancel the subscription.
Home --> Subscription --> Cancel subscription.
That stops everything and all billing costs.
Then you can add a new one.
To make the new subscription visible, you have to go setting --> Directories + subscriptions --> Default subscription filter --> select new subscription --> logout --> login.
On new Azure portal:
Click on your App service plan
Delete it
I had the same problem, also tried the script which executed without errors. In the end I pressed F12 to bring up the browser dev-tools, checked "disable cache" in the network tab and refreshed the web page with the service plans. And it's gone :)
Related
For GDPR compliance we want to change the region of our static web app to Europe or even better Germany.
There is no option to do so. On other SO questions I found the solution to create a new static web app and redeploy. But now when I create it with region=westeurope the newly created resource still has the location Global.
How to change the region of our web app to the EU or even better Germany?
Edit: The region is still Global but in the overview of the resource group it shows the right location. We redeployed the app and just manually copied the (luckily few) settings, still 4 hours of work..
Jahnavi's answer should work if you have the Premium plan. Unfortunately we migrated before we saw the answer.
Thanks to #Joel Odey. By referring to this blog I found an approach using "Clone APP".
You can try this replica for your question with the following steps:
Create another destination app service plan.
Make sure you clone the app service into the same resource group and region as the destination plan.
Search for the web app you want to clone.
Inside the web app, click on clone app feature available on the left side of the blade.
Select the new region while cloning the app and click on clone
Delete the previous service plan.
Before cloning, the region is Central Us:
After cloning, I moved it to East US region:
Note: To perform cloning operation, you need to have premium app sevice plan otherwise it will not be possible.
For more info you can refer this Ms Doc
We are planning to scale our Azure App Service to PremiumV3 to decrease our costs, however there is a limitation of Azure and so the documentation guides to create a new app service and then redeploy the application. But we really need to perform a complete migration for the following:
We have more than 170 domains pointed to this Application Service
We need to keep our public IP, otherwise we will lose the pointers from our customers.
We have tried:
Create new V3 plan, in the same region and in the same Resource Group but the console informs that this is not possible.
Cloning the app from the console, but nothing happens.
Does anyone have any suggestions on this situation?
Thanks
I am trying to delete app service plan from azure portal and understand the fact that it cant be deleted if an app sits in the service plan. Found an interesting thing here, even though there is no app or slots available in service plan it is not allowing me to delete app service plan. Following screen, any help or insights is appreciated-
I just had the same issue, this is how I deal with it.
The fact you see the number of apps/slots with the values 0/0, means you app has been well deleted. But your browser still keep in memory the old values, reason why it display a message saying one app is still in the Service Plan.
If you simply hit F5, the value will be updated and you'll be able to remove the App Service Plans.
We have BizSpark subscription with shared app service plan, where we are hosting our product. I need to host another version of the project for testing purpose, which fits into a free tier. I have checked the azure portals, but there is no provision to add a new service plan. does the BizSpark subscription support only one app service plan or am I missing anything?
Because an App Service services is an underlying component to other services, there isn't a simple way to directly create an App Service.
Since the only use case to create an App Service is to put something in it, the logic (I imagine) behind the Portals is that you create the resources you require and and it will create dependent resources within that process.
(Using the New Portal)
In order to create a new App Service plan, presuming you are deploying a new Web App. Click on New, Web + Mobile and then Web App.
When you click on Web App you will get this screen, if you fill in the details, and click App Service plan / Location at the bottom, you will be given the opportunity to select either an existing App Service or to create a new one.
The easiest solution would be to create a new Web app and when asked for App Service create a new one .. or use Azure Resource Manager template to achieve this: https://azure.microsoft.com/en-gb/documentation/templates/.
If it's another version of the App for testing purposes, why not use Deployment Slots? Slots have their custom URL separate from the Production app, separated configuration, domain bindings, it's like an App inside an App. You'll be able (if you want) to even swap the content of the Production environment with the Testing one for example.
And you don't incur in any extra cost because it runs on the resources of the current App Service :)
I have an Azure Cloud Service out in production. I recently received the following message from Microsoft about upcoming service for their Cloud Services platform:
All Cloud Services running web and/or worker roles referenced below will experience downtime during this maintenance. Cloud Services with two or more role instances in different upgrade domains will have external connectivity at least 99.95 percent of the time. Please note that the SLA guaranteeing service availability only applies to services that are deployed with more than one instance per role. Azure updates one upgrade domain at a time. For more information about distribution of roles across upgrade domains and the update process, please visit the Update an Azure Service webpage.
The way I take the email, each instance is essentially a VM on a different host, and they'll be rebooting hosts throughout the maintentance period, so if I don't want to be out of service during this time, I need to ensure I have more than one instance. Is this accurate? If so, how do I "add" an instance?
That is correct.
You can increase your instance count by updating the configuration for the role. In Visual Studio, you can do this in the Properties window for the role and increase the Instance count setting. Then, redeploy the service.
A faster way is to download the configuration file (.cscfg) for the role from the Azure portal, update the instance count setting, and then upload the changed configuration file. The setting is in the Instances element shown here.
You can download the configuration file for the role from the Azure portal (portal.azure.com) by going to the Cloud Service blade and clicking on Settings in the toolbar. In the Settings blade click Configuration. In the Configuration blade are where you will find Download and Upload buttons in the toolbar.
The way I take the email, each instance is essentially a VM on a
different host, and they'll be rebooting hosts throughout the
maintentance period, so if I don't want to be out of service during
this time, I need to ensure I have more than one instance. Is this
accurate?
Your understanding is correct.
If so, how do I "add" an instance?
There are many ways to do it.
One would be to edit your role's configuration file (*.cscfg) and changing the Instances element's count property from 1 to 2 and then uploading this file through Azure Portal (Cloud Service --> Configure Tab --> Upload button)
Other one would be to change the instance count through "Scale" tab for Cloud Service in question. On this tab, you will see "Instance Count" setting. Just update it from 1 to 2.
Other options include PowerShell, writing code but I think the ones I mentioned above should be the easiest way to accomplish the task.