Add deployment slots
Deployment slots are configured in the Azure portal. You can swap your app content and configuration elements between deployment slots, including the production slot.
How to use deployment slots in Azure App Service
Things to know about creating deployment slots
Let's review some details about how deployment slots are configured.
New deployment slots can be empty or cloned.
Deployment slot settings fall into three categories:
- Slot-specific app settings and connection strings (if applicable)
- Continuous deployment settings (when enabled)
- Azure App Service authentication settings (when enabled)
When you clone a configuration from another deployment slot, the cloned configuration is editable. Some configuration elements follow the content across the swap. Other slot-specific configuration elements stay in the source slot after the swap.
Swapped settings versus slot-specific settings
The following table lists the settings that are swapped between deployment slots, and settings that remain in the source slot (slot-specific). As you review these settings, consider which features are required for your App Service apps.
| Swapped settings | Slot-specific settings |
|---|---|
| General settings, such as framework version, 32/64-bit, web sockets App settings * Connection strings * Handler mappings Public certificates WebJobs content Hybrid connections ** Service endpoints ** Azure Content Delivery Network ** Path mapping |
Custom domain names Nonpublic certificates and TLS/SSL settings Scale settings Always On IP restrictions WebJobs schedulers Diagnostic settings Cross-origin resource sharing (CORS) Virtual network integration Managed identities Settings that end with the suffix _EXTENSION_VERSION |
* Setting can be configured to be slot-specific.
** Feature isn't currently available.