I get "getting Scale out issues detected Storage is not configured properly, Function scaling will be limited. Click to learn more." error in azure portal while in azure function apps.
It is on consumption model.
I followed the Microsoft guide-https://learn.microsoft.com/en-us/azure/azure-functions/functions-recover-storage-account#storage-account-was-deleted
and other answer here and added the missing values WEBSITE_CONTENTAZUREFILECONNECTIONSTRING and
WEBSITE_CONTENTSHARE(I only have AzureWebJobsStorage set right now).
When I then run my logic apps, all azure functions return 404 not found. I had to delete WEBSITE_CONTENTAZUREFILECONNECTIONSTRING and WEBSITE_CONTENTSHARE to make them work again.
My concern is how to fix this because we are also facing performance issues and I am not sure if this scaling issue is contributing to it?
AFAIK Below might be reasons for getting the error,
Region for storage account and function app are different.
Region for storage account and logic app are different.
App service plan is different for logic app and function app.
Check whether AzureWebJobsStorage and WEBSITE_CONTENTAZUREFILECONNECTIONSTRING values are same or not in standard logic app configuration.
Check the AzureWebJobsStorage in function app is matching with the value of AzureWebJobsStorage in standard logic app configuration.
Check below links that may helps you,
Reference link 1
Reference link 2
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 have been trying to create a Web App Bot using the Microsoft Azure Portal. However, I have been unsuccessful in doing so, as I am constantly getting the error "Location '{any server location}' is currently not supported" when I try to add any new App Service-Plan. My active App Service Plan (B1, Linux, West Europe) is not even an option that I can select when choosing a plan.
I am somewhat confused and frustrated with this behavior as during my free trial period the creation of an Web App Bot did work and I am also able to create a Functions Bot.
I am sure, that there is some kind of problem with the App Service Plan, but I am not able to figure it out myself. Maybe one of you did stumble upon this issue already and is able to help me?
I had the same issue, but I resolved it by changing "consumption plan" to "app service plan."
screenshot
We have an Azure subscription through a Cloud Service Provider (CSP), which causes some limitations on what we can get and see in Azure. Nevertheless, we can see CPU and Memory usage per App Service Plan.
How can we see the same for specific App Services under the plan?
If I see abnormal CPU/memory utilization for the plan, how can I tell which App Service is causing it?
You can check this under any Site -> scroll down to the "Metrics (App Service Plan)" option. There you will be able to see the metrics across all sites which are in the plan and filter the data the way you want:
Update 2018-12-04
Check other answers for more updated information, since the experience evolve and change over time. And stop down voting just because you came 2 years later.
I will not include the current solution/screenshots here, because it will be unfair to the other contributors. And I cannot delete this answer as it is accepted one (because it was correct by the time asked and answered).
Go to any site (app) that's part of the App Service Plan
Click on 'Diagnose and Solve Problems'
In the screen that opens, click 'Metrics (App Service Plan)'.
For an App Service it's currently under:
Go to any site (app) that's part of the App Service Plan
Click on "Diagnose and Solve Problems"
Click on Performance Counters (on the right side of the screen)
Check e.g. the "Average Memory Working Set" checkbox
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 :)