This blog post will give you a good idea of what App Service is capable and what are the different deployment options available. App Service capabilities enable developers to focus on their code and quickly reach a stable and highly scalable production state. Key capabilities of why App Service, Multiple languages and frameworks, Global scale with high availability, DevOps optimization, Security and compliance, Connections to SaaS platforms and lot more..

Your App Service plans are Free and Shared SKUs to Basic, Standard, and Premium SKUs

The 64-bit and Always On options can be enabled in Basic plans and higher.

AutoSwap can only be enabled on Standard plans and higher.

You can improve the performance of your state-less applications by turning off the Affinity Cookie, state-full applications should keep the Affinity Cookie turned on for increased compatibility.

Securely access resources available in or through your Azure VNET, Backup and Restore feature requires your App Service plan to be Standard or higher

Clone app is a feature that is only available to apps hosted on Premium App Service Plans.

Log Stream Service is great to see the application logs on the console

There are 4 different ways of sync based web apps deployments

1. Kudu Deployment Engine,
2. Integrated with App Service.
3. One drive and
4. Dropbox as deployment source

Continuous Deployment workflow, bitbucket, github and VSTS these models are great for the frequent and multiple contributions. At any point in time these can be disabled by using the Disconnect button.

Web Jobs are deployed using FTP / GIT

In Standard or Premium, Staging environment are available where in you can deploy and provided the ability to test with an Auto swap option if tests are passed.

You cannot change App Service Plan if you more than one slot. Also, non-production slots cannot be scaled.

You can have multiple non-production slots, however

1. Settings are not swapped between the slots are Publishing endpoints, Custom Domain Names, SSL Bindings, Scale Settings and Web Jobs Scheduler
2. Settings swapped are General Settings, Application Settings, Connection Strings, Handlers, Web Jobs Content and Monitoring/Diagnostic settings

You can move web apps between App Service plan only if the plans exist in the same resource group and geographical location.

App service clone will copy the content and certificates of your app into a newly created application. Some settings can also be included in the clone operation which are App Settings, Connection Strings, Deployment Source and Custom domain if any.

App Service Clone can happen only if from a Premium to Premium Plans. It Can be in different resource group

When cloning Web Apps few settings are not cloned

1. Auto Scale, Backup Schedule,
2. VNET,
3. Kudu Extensions,
4. TiP rules and Database Contents.

Backups are available in Standard as Daily and Premium as 50 times Daily.

App Configuration, File Content and any Azure SQL/MySQL Connected with the Application.

A new Traffic manager profiles can be created and configure along with the cloning process.

SSL bindings can be used in Basic plans and higher.

Certificates must be associated with your application before you can use them to create a binding. You can upload Only. Pfx certificate you purchased externally, or import an App Service Certificate.

Custom Domains configuration requires Shared, Basic, Standard and Premium Modes

1. Buy the domain if you don’t have one already
2. Get app’s IP Address (A Record)
3. Create the DNS record that map your domain to your app (So that Domain registrar knows to resolve)
4. Enable Custom Domain name for your app in azure portal
5. Verify the DNS Propagations

CNAME should not be used for the Root Domain instead use A Record.

SubDomain the preferred way CNAME, (to your app’s Azure domain name, <appname>.azurewebsites.net.) so moving the app between pricing tier will not involve the changing of IP address.