A deployment slot lets an application team prepare a separate configuration before moving an approved release into production. Read which settings move with the application and which stay attached to a slot. A database connection meant only for staging should not become the production connection during a swap.
These tasks model a web app, a staging slot and ordinary or slot-specific settings. Under the default modeled behavior, protocol settings remain attached to their slots. The simulator exchanges configuration only; it doesn't publish app content, send warm-up requests or test real traffic. Keep production security and recovery checks in the release plan instead of treating a successful local swap as a complete rollout.
Swap the approved configuration while retaining each slot’s data setting.