Skip to content

Commit 8edcee8

Browse files
authored
move vnet integration to non-swapped setting
Removed 'Virtual network integration' from the list of settings that aren't swapped during slot swaps.
1 parent b0ce10c commit 8edcee8

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

includes/app-service-deployment-slots-settings.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,6 @@ When you clone a configuration from another deployment slot, the cloned configur
2323
- Service endpoints
2424
- Azure Content Delivery Network
2525
- Path mappings
26-
- Virtual network integration
2726

2827
**When you swap slots, these settings aren't swapped**
2928

@@ -40,6 +39,7 @@ When you clone a configuration from another deployment slot, the cloned configur
4039
- Managed identities
4140
- Settings ending with the suffix `_EXTENSION_VERSION`
4241
- Settings that [Service Connector](../articles/service-connector/overview.md) created
42+
- Virtual network integration
4343

4444
> [!NOTE]
4545
> Settings marked with * can be made swappable by adding the app setting `WEBSITE_OVERRIDE_PRESERVE_DEFAULT_STICKY_SLOT_SETTINGS` to every slot of the app and setting its value to `0` or `false`. This reverts to legacy swap behavior from before these settings were made slot-specific. When you use this override, these marked settings become either all swappable or all not swappable. You can't make just some settings swappable and not the others.

0 commit comments

Comments
 (0)