In this blog, I’ll discuss our customer requirement for changing the URL of an existing web application, changing the URL of its extended application, and steps to do those successfully.
Background
In one of our SharePoint 2013 environments, we have created a web application, deployed our solution, and also extended the web application to different zones. But later, the customer says to change the URL. I Googled a bit but found different steps to perform this. Following are the steps which I followed in our environment so as to change the URLs successfully.
Steps to change the URL of existing web applications and extended web application
- Change the Alternate Access Mappings for your application.
- Open the “Central Administration”.
- Open the link “System Settings >> Configure alternate access mappings” and you will be redirected to “AlternateUrlCollections.aspx” page (_admin/AlternateUrlCollections.aspx).
- On this page, you will see all your web application internal URLs, respective zones, and the public URL as shown below.
Figure 1 - SharePoint OnPremises - Alternate Access Mapping page
- Click on “Edit Public URLs” link from the top right. You will be redirected to the “EditOutboundUrls.aspx” page. Select your web application from the drop-down “Alternate Access Mapping Collection”.
Figure 2 - Central Admin - Alternate Access Mappings - Editing "Edit Public Zone URLs"
Update your new URLs in your respective zones and click on the “Save” button. This is the first step we need to perform; the next step is to update the IIS bindings.
- Change bindings in IIS on all your front-end servers for both the web applications.
- Open the IIS Manager.
- From “Sites”, select the web application for which we need to change the binding.
- Right click on the web application and then select “Edit Bindings…”. The “Site Bindings” drop-down will open.
Figure 3-"Site Bindings" dialog
- Click on “Edit…” button and change the Hostname with your new URL for web application.
- Repeat the same steps for your extended web applications.
- Just try accessing both the web applications.
Reference