Select Azure Web App from the list of available targets and click Next.

Fill out the necessary fields, being sure to provide a unique role that clearly identifies your Azure Web App target.

If you are using a Standard or Premium Azure Service Plan, you can also select a specific slot as your target.
The Azure Web App Slot field will allow you to select one of the slots available on the Web App. If there are no slots, this will be empty.

You can also leave the slot selection blank and specify the slot, by name, on the step too. The slot selected on the deployment target will take precedence over a slot defined on the step.

After clicking Save, your deployment target will be added and go through a health check to ensure Octopus can connect to it.

If all goes well, you should see your newly created target in your Deployment Targets list, with a status of Healthy.

Creating Web App Targets by Scripts

Azure Web App targets can also be created via a PowerShell Cmdlet within a Deployment Process, this can be especially handy if you are also creating the Azure Web App via a script.

Troubleshooting

If your Azure Web App target does not successfully complete a health check, you may need to check that your Octopus Server can communicate with Azure. It may be worth checking that your Azure Account is able to complete a Save and Test to ensure Octopus can communicate with Azure. If your Octopus Server is behind a proxy or firewall, you will need to consult with your Systems Administrator to ensure it can communicate with Azure.