The new deployment slot has no content, even if you clone the settings from a different slot. For example, you can publish to this slot with Git. You can deploy to the slot from a different repository branch or a different repository. Get publish profile from Azure App Service can provide required information to deploy to the slot. The profile can be imported by Visual Studio to deploy contents to the slot.
The slot's URL has the format http://sitename-slotname.azurewebsites.net. To keep the URL length within necessary DNS limits, the site name will be truncated at 40 characters, and the combined site name and slot name must be fewer than 59 characters.
https://learn.microsoft.com/en-us/azure/app-service/deploy-staging-slots?tabs=portal
Targeting staging slot web endpoints
The app must be running in the Standard, Premium, or Isolated tier in order for you to enable multiple deployment slots.
Run the following command in a terminal: Azure CLI
For more information, see az webapp deployment slot create.
The new deployment slot has no content, even if you clone the settings from a different slot. For example, you can publish to this slot with Git. You can deploy to the slot from a different repository branch or a different repository. Get publish profile from Azure App Service can provide required information to deploy to the slot. The profile can be imported by Visual Studio to deploy contents to the slot.
The slot's URL has the format http://sitename-slotname.azurewebsites.net. To keep the URL length within necessary DNS limits, the site name will be truncated at 40 characters, and the combined site name and slot name must be fewer than 59 characters.