I'm trying to turn off the AlwaysOn feature for my App Service, but after saving the change it reverts back to "On".
It's a Windows Service Plan currently on a B1 pricing tier. I'd like to scale down to either D1 or F1 pricing tier but those require the AlwaysOn feature to be turned off. When I try to scale down to either of those pricing tiers I get a notification:
"Cannot update the site '[my-site-name]' because it use AlwaysOn feature which is not allowed in the target compute mode"
So I then go to the apps Configuration > General Settings, turn off the AlwaysOn feature and save. When I refresh to check if the change saved the AlwaysOn feature is back to On.
Summary of steps I'm taking to turn off AlwaysOn feature:
From the App Service > Configuration > General Settings
Toggle "Always On" from "On" to "Off"
"Save" and "Continue"
I refresh and the AlwaysOn feature reverts to "On"
Any help is appreciated.
What App Service Plan are you using?
By default, web apps are unloaded if they are idle for some period of time. This lets the system conserve resources. By enabling Always On you keep the app loaded all the time.
Just trying to understand and confirm, why are you attempting to disable?
Are you an admin, co-admin or contributor on the subscription?
Do you notice the activity success when you disable Always On?
Kindly try these steps just to isolate the issue:
Try this operation on a different browser and validate.
If feasible restart the WebApp and then test.
Scale-down App Service plan and then re-check.
Related
Even if always on flas is setted, azure closes our web apps after inactivity 20 minutes. Then it opens them when first request comes. Is it possible to avoid from this behaviour. We want our services always running and responds immediately.
App service plan is Standard: 1 Large. Subscription's offer is "Azure in Open"
Thanks in advance
Go to the App Service Web App within the Azure Portal, navigate to the "Application Settings" section, and set the "Always On" option to "On". This will ensure the application is always running.
FYI, the "Application Settings" pane in the Azure Portal is changing to "Configuration", and is currently in Preview at the time of writing this.
My web job goes on sleep after a while
and as per Microsoft docs
"A web app can time out after 20 minutes of inactivity. Only requests to the scm (deployment) site or to the web app's pages in the portal reset the timer. Requests to the actual site don't reset the timer. If your app runs continuous or scheduled WebJobs, enable Always On to ensure that the WebJobs run reliably"
but I am not able to find this setting. Thats how web job looks like in portal
Can some one please help me , how can I turn on this setting
Go to the Web App that is hosting your WebJobs and select the Application Settings menu option. The Always On setting is there.
Note that Always On is only available for Basic or greater service tiers. Free and Shared do not have this setting.
Is it possible to put app to sleep during night time anymore?
I have the app service setting NOT on "Always On", but this setting is not respected.
The bills used to be twice as much as they are now, because in past they app set itself to sleep. How do I know this? The service hours are now around 730 (that's a full month). Is Azure no more "Pay-As -You-Go?"
Thanks.
#Joonas, There was never an option to put the app to sleep in Azure Web Apps. The only way to ensure that you are not getting billed is to Scale down the corresponding App Service Plan of the web app to FREE tier.
You can configure scale settings based on a specific schedule so that the app service plan can be scaled up.
Always On is a setting used to keep your app up and running at all times. Assume that you have 10 web apps hosted on a server, out of which 8 are your dev or least used sites, while the other 2 are busy sites accessed throughout the day. In such a scenario you don't want the dev sites to be running at all times as they will hold system resources. The Always On feature is handy in such scenarios. You can set Always On to true for the 2 busy sites and false for the other 8 sites.
Check the number of App Service Plans in your subscription and
also their pricing tier. This will help you understand the costs. In
Azure App Service, you get billed for the App Service Plan and not
the Web App.
This image should help you understand App Service Plan
You can get the answer from this official FAQ:
Am I charged for apps while they are in stopped state?
Yes. Rates listed apply to apps in stopped state. Please delete apps that are not in use or update tier to Free to avoid charges.
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'm testing different Azure web app pricing tiers. In the portal I clicked "Scale up (App Service plan)" and chose the B1 Basic pricing tier to test how the performance compared with F1 Free and D1 Shared. When I try to scale down from Basic to Free or Shared, it says "Successfully updated App Service plan", but it doesn't work. I've tried this over a week or so and it just doesn't work. I was able to switch between Free and Shared with no problems before this. Surely this is some sort of error? We must be able to downgrade?
You must turn off the "Always On" feature of the Web App from the Azure portal "Application Settings" before changing (downgrading) the App Service Plan.
So the new portal has a few bugs. I tried to do this operation with the old portal and got a helpful error message:
Cannot update the site 'test' because it uses x64 worker process which is not allowed in the target compute mode.
If you choose a setting not available in a downgrade, for example 64-bit or "Always On" (confirmed), and then try to downgrade, it will say it succeeded when actually it failed.
And they won't let us use the old portal soon. Great.
"Always On" can be found here now:
I had the same issue; it was not possible to change the tier even after I changed the app service configuration to 32-bit. The problem was the other app services in the app service plan. After changing all the app services of the service plan into 32-bit, it was possible to change it to Free tier.