SharePoint Tutorial Contents
In any SharePoint web application, we could see 2 types of users Internal or External. If we want to collaborate on the SharePoint site with both Internal and External users the best approach from Microsoft is Extend the Web Application.
Once we extend the web application we can configure a different set of permissions to that users. However, both web applications communicate the same Content Database.
Note: When you extend the Web Application SharePoint creates only a new IIS site in Application Pool and connects with the same content database.
In an organization, we have 2 verticals Finance and BPO. If we need to share the same SharePoint web application between verticals without breaking the permissions! The best way is Extending Web Application.
In this article, we are going to learn how to extend a web application in both
- SharePoint Central Administration
- PowerShell Commands
Follow the below steps to extend a web application in SharePoint 2013 through Central Administration.
Log-on to Application Server with a FARM administrator account. Select the required web application under Manage Web Applications. From SharePoint Central Administration -> Application Management -> Manage Web Applications.
Click on Extend option as part ribbon control to extend the web application
Provide all the details of a new extending web application in the model dialogue window.
Note: In this model dialogue window do can’t see the below option which you see while creating a new web application as they carry forward from the original Web Application.
- Database server name
- Failover DB server name
- Application services
Once you provide all the details click on OK at the end of model dialogue window to create the extended web application.
Follow the below steps to extend the SharePoint 2013 web application using PowerShell commands.
Log-On to the Application server with a FARM administrator account
Open SharePoint 2013 Management Shell with a FARM administrator account
Run the below command to extend the desired web application
$ap = New-SPAuthenticationProvider -ASPNETRoleProviderName roleprovidername -ASPNETMembershipProvider membershipprovidername Get-SPWebApplication -Identity <Existing Web Application> | New-SPWebApplicationExtension -Name <Web Application Name> -HostHeader <HostHeader> -Zone <Zone> -URL <URL> -Port <Port> -AuthenticationProvider $ap Parameters: <Name> is the name of the new IIS web site in the web application. – Mandatory <HostHeader> is the hostname assigned to this zone of the web application. – Optional <Zone> is the zone with which this new extension is to be associated. – Mandatory <URL> is the public URL for this web application zone. – Mandatory <Port> is the port on which this zone of the web application can be accessed. – Mandatory
$ap = New-SPAuthenticationProvider -ASPNETRoleProviderName roleprovidername -ASPNETMembershipProvider membershipprovidername Get-SPWebApplication -Identity http://contoso.sales.com | New-SPWebApplicationExtension -Name IntranetSite -Zone Intranet -URL http://intranet.conoso.sales.com -Port 9876 -AuthenticationProvider $ap
You may like following SharePoint web application tutorials:
- Delete Hidden Web Application in SharePoint 2013 using PowerShell
- Manage Web Application Settings in SharePoint 2013
- Create SharePoint site programmatically
- SharePoint content database tutorial
Tags: extending web application sharepoint 2013, extending web application sharepoint 2016, extending web application sharepoint 2010, sharepoint 2013 extend web application, sharepoint 2016 extend web application, PowerShell extend web application sharepoint 2013, sharepoint 2013 extend web application ssl, sharepoint 2013 extend web application extranet
Enjoy administration in SharePoint 2013 !!!
I am Krishna.Vandanapu a SharePoint architect working in IT from last 13+ years, I worked in SharePoint 2007, 2010, 2013, 2016 and Office 365. I have extensive hands on experience in customizing SharePoint sites from end to end. Expertise in SharePoint migration tools like Sharegate, Doc Ave and Metalogix. Migrated SharePoint sites from SharePoint 2007 to 2010 and 2010 to 2013 several times seamlessly. Implementing CSOM with Microsoft best practices. Spent quality time in configuring SharePoint application services like User Profile, Search, Managed Meta data services etc. Now exploring SharePoint Framework and SharePoint 2019