Host named site collections and Web Application Extensions

The question came up about whether the mix of an SharePoint 2013 extended web application that may have different authentication providers, could also support Host Named Site Collections (HNSC).

Well, they can.  The documentation isn’t that clear, never seen it explicitly called out.

But, just from a foundation of setting up a web application, extending it, then establishing a HNSC that is addressable from 2 different SP Zones (Extended zone), these are the simple steps:


New-SPWebApplication -Name ‘Wingtip Public HNSC’ -port 8000 -ApplicationPool WingtipHnscAppPool -ApplicationPoolAccount (Get-SPManagedAccount ‘wingtip\svc_spcontent’) -AuthenticationProvider (New-SPAuthenticationProvider –UseWindowsIntegratedAuthentication)

#1.1 – create a root site collection….
New-SPSite ‘http://WINGTIPSERVER:8000′ -Name ‘Portal’ -Description ‘Portal on root’ -OwnerAlias ‘wingtip\administrator’ -language 1033 -Template ‘STS#0’

Get-SPWebApplication ‘http://WINGTIPSERVER:8000′ | New-SPWebApplicationExtension -Name "Internet Site" -Zone "Internet" -Port 80 -URL ""

New-SPSite ‘′ -HostHeaderWebApplication ‘http://WINGTIPSERVER:8000’ -Name ‘HNSC1’ -Description ‘HNSC 1’ -OwnerAlias ‘wingtip\administrator’ -language 1033 -Template ‘STS#0’

Set-SPSiteUrl (Get-SPSite ‘′) –Url ‘’ –Zone Internet

Comments (1)

  1. SharePointMichael says:

    This is a huge help, thank you. However, I am still having an issue with authentication on the HSNC site collection. My internet zone is configured for FBA. It works find on the root site collection. Usernames to not resolve on the HSNC. Any Suggestions