Microsoft.Web sites/hostNameBindings

The sites/hostNameBindings resource type can be deployed to: Resource groups.

To learn about resource group deployments, see Bicep or ARM template.

Template format

To create a Microsoft.Web/sites/hostNameBindings resource, add the following Bicep or JSON to your template.

resource symbolicname 'Microsoft.Web/sites/hostNameBindings@2021-02-01' = {
  name: 'string'
  kind: 'string'
  properties: {
    azureResourceName: 'string'
    azureResourceType: 'string'
    customHostNameDnsRecordType: 'string'
    domainId: 'string'
    hostNameType: 'string'
    siteName: 'string'
    sslState: 'string'
    thumbprint: 'string'

Property values


Name Description Value
type The resource type

For Bicep, set this value in the resource declaration.
apiVersion The resource api version

For Bicep, set this value in the resource declaration.
name The resource name

See how to set names and types for child resources in Bicep or JSON ARM templates.
string (required)
kind Kind of resource. string
properties HostNameBinding resource specific properties HostNameBindingProperties


Name Description Value
azureResourceName Azure resource name. string
azureResourceType Azure resource type. 'TrafficManager'
customHostNameDnsRecordType Custom DNS record type. 'A'
domainId Fully qualified ARM domain resource URI. string
hostNameType Hostname type. 'Managed'
siteName App Service app name. string
sslState SSL type. 'Disabled'
thumbprint SSL certificate thumbprint string

Quickstart templates

The following quickstart templates deploy this resource type.

Template Description
Web App with Private Endpoint

Deploy to Azure
This template allows you to create a Web App and expose it through Private Endpoint
Web App with a custom domain and optional SSL binding

Deploy to Azure
Create a web app and with a custom domain and optionally add SSL certificate for https encryption.
Web App with VNet Injection and Private Endpoint.

Deploy to Azure
This template allows you to create a secure end to end solution with two web apps, front end and back end, front end will consume securely the back through VNet injection and Private Endpoint