Do you already have that feeling about why your Azure App Service ignores the updated settings you just made? You know that:
- You update an application setting in Azure App Service.
- You’re sure you saved it.
- You refresh your app.
But still, nothing changes!! You double‑check your code, redeploy, test again — still the old values. So what is actually happening?
What’s Happening?
Azure saves your updated settings instantly, that is a fact, however….
Your running app loaded its configuration at startup — and it hasn’t looked back since. Changing a setting in the portal updates the infrastructure layer, but your process doesn’t know that. It’s still running with the values it read when it first booted.
This catches you out if your app:
- Reads environment variables at startup
- Caches configuration on boot
- Builds its dependency injection container at initialization
The portal saves the setting and shows a green checkmark. It just doesn’t tell you that none of it matters until you restart.
📝 One-Minute Brief
Azure App Service doesn’t reload configuration automatically. When you update an application setting in the portal, the running process keeps using the values it loaded at startup. Your app won’t reflect any changes until you restart it. A quick restart — local or across all instances — ensures consistent configuration and prevents confusing, inconsistent behavior.
The Fix: Restart the App Service
To apply your new settings, you must restart the app:
- On the Azure Portal, click Restart in the App Service overview page.
- Or run the following CLI command:
az webapp restart --name <app-name> --resource-group <rg-name>
If you’re running multiple instances, make sure they all restart — a partial restart leaves you with mixed config across your fleet, which looks like an intermittent bug and is miserable to debug.
Why This Matters
- Stops you from blaming your code for an infrastructure problem.
- Saves you from chasing phantom bugs across redeploys.
- Keeps configuration consistent across all instances.
- Eliminates “phantom bugs” caused by stale configuration.
Sometimes the problem isn’t your code.
Sometimes it just needs a restart.
To lazy to read? We’ve got you covered! Check out our video version of this content!
Hope you find this helpful! If you enjoyed the content or found it useful and wish to support our efforts to create more, you can contribute towards purchasing a Sauron’s Action Figure for Sandro’s son, yep, not for me!
