{"id":15652,"date":"2020-08-07T04:46:36","date_gmt":"2020-08-07T04:46:36","guid":{"rendered":"https:\/\/www.testpreptraining.com\/tutorial\/?page_id=15652"},"modified":"2022-04-04T10:16:47","modified_gmt":"2022-04-04T10:16:47","slug":"setting-up-staging-environments-in-azure-app-service","status":"publish","type":"page","link":"https:\/\/www.testpreptraining.ai\/tutorial\/setting-up-staging-environments-in-azure-app-service\/","title":{"rendered":"Setting up staging environments in Azure App Service"},"content":{"rendered":"\n

AZ-303 is retired.\u00a0AZ-305<\/a>\u00a0replacement is available.<\/strong><\/h2>\n\n\n\n

This tutorial will help you in Setting up staging environments in Azure App Service. When you deploy your web app, web app on Linux, mobile back end, or API app to Azure App Service, you can use a separate deployment slot instead of the default production slot when you’re running in the Standard<\/strong>, Premium<\/strong>, or Isolated<\/strong> App Service plan tier.<\/p>\n\n\n\n

Add a slot<\/strong><\/h3>\n\n\n\n

The app must be running in the Standard<\/strong>, Premium<\/strong>, or Isolated<\/strong> tier in order for you to enable multiple deployment slots.<\/p>\n\n\n\n

  1. Visit Azure portal, search for and choose App Services<\/strong> and choose your app.<\/li><\/ol>\n\n\n\n
    \"Search
    Image source – Microsoft<\/figcaption><\/figure><\/div>\n\n\n\n

    In the left pane, choose Deployment slots<\/strong> > Add Slot<\/strong>.<\/p>\n\n\n\n

    \"Add
    Image source – Microsoft<\/figcaption><\/figure><\/div>\n\n\n\n

    In the Add a slot<\/strong> dialog box, give the slot a name, and select whether to clone an app configuration from another deployment slot. Select Add<\/strong> to continue.You can clone a configuration from any existing slot. Settings that can be cloned include app settings, connection strings, language framework versions, web sockets, HTTP version, and platform bitness.<\/p>\n\n\n\n

    \"Configuration
    Image source – Microsoft<\/figcaption><\/figure><\/div>\n\n\n\n

    After the slot is added, select Close<\/strong> to close the dialog box. The new slot is now shown on the Deployment slots<\/strong> page. By default, Traffic %<\/strong> is set to 0 for the new slot, with all customer traffic routed to the production slot.<\/p>\n\n\n\n

    Select the new deployment slot to open that slot’s resource page.<\/p>\n\n\n\n

    \"Deployment
    Image source – Microsoft<\/figcaption><\/figure><\/div>\n\n\n\n

    The staging slot has a management page just like any other App Service app. You can change the slot’s configuration. To remind you that you’re viewing the deployment slot, the app name is shown as <app-name>\/<slot-name><\/strong>, and the app type is App Service (Slot)<\/strong>. You can also see the slot as a separate app in your resource group, with the same designations.<\/p>\n\n\n\n

    Select the app URL on the slot’s resource page. The deployment slot has its own host name and is also a live app. To limit public access to the deployment slot, see Azure App Service IP restrictions.<\/p>\n\n\n\n

    What happens during a swap<\/strong><\/h3>\n\n\n\n

    Swap operation steps<\/strong><\/h4>\n\n\n\n

    When you swap two slots (usually from a staging slot into the production slot), App Service does the following to ensure that the target slot doesn’t experience downtime:<\/p>\n\n\n\n

    1. Apply the following settings from the target slot (for example, the production slot) to all instances of the source slot: