Back to Azure Resource templates index <–
Azure Web App deployment in an existing Azure App Service Plan.
Template Locations
Infrastructure As Code Advisor (Beta)
WAF-compliance
The WAF-compliance advisor validates templates based on the Well Architected Framework practices. Every day a GitHub Action updates the templates compliance data and lists the recomendations.
Sustainbility Advisor
The sustainability advisor is based on the Sogeti Cloud Reference Architecture with sustainble practices. These sustainble practices cover application code, cloud infrastructures and data. The global Sogeti community is continously evolving the sustainble practices and every day new and tuned are added. For cloud infrastructures the sustainble practices are automatically validated and reported below.
note: when 100% it can be that there is no sustainble practices yet for this Cloud infrastructure.
Online documentation
Template reference
Service description
Requirements
- Resource group must been created with a valid name and location.
- App Service Plan must be created.
Input values
- webAppName : Web Application Name.
- sku : Give sku.
- location : GIve location name.
- dockerImageName : Give existing docker image name.
- dockerRegistryUrl : Give existing docker registry URL.
- dockerRegistryUsername : Give existing docker registry username.
- dockerRegistryPassword : Give existing docker registry Password.
- servicePlanName : Give existing App Service Plan name.
Output values
Additional information
An Azure Web app resource is never alone. It will always need an App Service Plan and also require docker registry.
Compliance Advisor details
Resource Health Result
| Message | ResourceType | Severity |
|---|---|---|
| It is recommended to use below property for your resource Microsoft.Web/sites{ "minTlsVersion": "1.2" }TLS should be updated to the latest version for you web app | Microsoft.Web/sites | 3 |
| It is recommended to use below property for your resource Microsoft.Web/sites{ "ftpsState": "Disabled" }If DevOps is used for Deployment then Ftps should be disabled, else Ftps can be used for Deployment. So ftpsState can be 'AllAllowed', 'FtpsOnly' or 'Disabled | Microsoft.Web/sites | 3 |
| Managed Identity should be turned On for your resource | Microsoft.Web/sites | 3 |
| It is recommended to use below property for your resource Microsoft.Web/sites { "httpsOnly": true }Application or Functions should be only be accessible over HTTPS | Microsoft.Web/sites | 2 |
| Location for the resource should not be hardcoded, it should be parameterized and should refer from Resource Group's location i.e. [resourceGroup().location] | Microsoft.Web/sites | 2 |
| It is recommended to enable slots for your App service for non production environment, which will eliminate the need of having multiple hardware allocation for different environment | Microsoft.Web/sites | 2 |
| Consider using a CDN to distribute your application's static assets closer to the source of a request. This distrubution of assets reduces the distance all request for static assets has to travel over the network' | Microsoft.Web/sites | 2 |
| Your current API Version i.e.2016-08-01 for the resource Microsoft.Web/sites is outdatedconsider updating to new recent version available i.e. 2022-09-01 or 2022-03-01 | Microsoft.Web/sites | 2 |
| It is recommended to use below property for your resource Microsoft.Web/sites{ "use32BitWorkerProcess": "false" }Consider upgrading your application to 64 Bit worker process to future proof your application | Microsoft.Web/sites | 1 |
| It is recommended to use tags for your resource, which is currently missing | Microsoft.Web/sites | 1 |
| To help other contributors understand the purpose of the resource, specify comments for each resource in the template | Microsoft.Web/sites | 1 |
| It is recommended to parameterized your tag and make it as object type | Microsoft.Web/sites | 1 |
TemplateParameterHealthResult
| Message | Severity |
|---|---|
| It is recommended to make your parameter as camel case, wherever possible for i.e. webappcustomnameRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. webappcustomnameRead More | 1 |
| It is recommended to add description for your parameters i.e. for dockerImageNameRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. dockerImageNameRead More | 1 |
| It is recommended to add description for your parameters i.e. for dockerRegistryUrlRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. dockerRegistryUrlRead More | 1 |
| It is recommended to add description for your parameters i.e. for dockerRegistryUsernameRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. dockerRegistryUsernameRead More | 1 |
| It is recommended to add description for your parameters i.e. for dockerRegistryPasswordRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. servicePlanNameRead More | 1 |
TemplateVariableHealthResult
| Message | Severity |
|---|---|
| It is recommended to make your variable as camel case, wherever possible for e.g. environmentRead More | 1 |
TemplateOthersHealthResult
| Message | Severity |
|---|---|
| Current schema version is not valid, Please change the version year to 2019-04-01 or greater | 2 |
Sustainable Advisor details
| Message | ResourceType | Severity |
|---|---|---|
| It is recommended to enable slots for your App service for non production environment, which will eliminate the need of having multiple hardware allocation for different environment | Microsoft.Web/sites | 2 |
| Consider using a CDN to distribute your application's static assets closer to the source of a request. This distrubution of assets reduces the distance all request for static assets has to travel over the network' | Microsoft.Web/sites | 2 |