---
title: "Azure App Service deployment slots: which settings should stay sticky?"  
description: "Azure App Service deployment slots: which settings should stay sticky?"  
author: "Vaibhav Kumar"  
published: 2026-10-12  
updated: 2026-10-12  
canonical: https://www.mindstick.com/forum/162265/azure-app-service-deployment-slots-which-settings-should-stay-sticky  
category: "Azure App Service"  
tags: ["Azure App Service", "Deployment Slots", "Application Configuration"]  
reading_time: 1 minute  

---

# Azure App Service deployment slots: which settings should stay sticky?

We use staging slots in Azure App Service to test releases before swapping them into production. A few settings, such as the database connection string, should clearly remain tied to the production slot, but I’m less sure about feature flags and external service endpoints.

How do you decide which **slot settings** should be marked as deployment-slot settings? I’d especially like to hear how teams handle configuration that differs between staging and production without accidentally carrying test values across during a swap.


---

Original Source: https://www.mindstick.com/forum/162265/azure-app-service-deployment-slots-which-settings-should-stay-sticky

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.