Alternate Access Mapping in SharePoint 2016

configure alternate access mappings sharepoint 2013 step by step

Here in this SharePoint 2016 tutorial we will discuss about what is an alternate access mapping in SharePoint 2016? How we can configure alternate access mapping?

What is Alternate Access Mapping (AAM)?

Alternate Access mappings in SharePoint allows you to create multiple URLs for the same web application. This will helps users from the internal company networks users to access intranet site by simply using http / https URL and forcing outside the network users accessing it from the internet to use the fully-qualified domain name.

Note: Alternate Access

Example:
Internal users: http://contoso.com
External users: http://intranet.contoso.com

There are 2 type of Alternate Access Mappings can be configured in SharePoint 2016 they are:
1. Internal URLs
2. Public URLs

Internal URL:
We could say Internal URL is simply an alias for the same site. Which means when users type this URL in browser SharePoint redirects them to Public URL of this Web Application.

Public URL:
This is an other URL configured / mapped to the SharePoint Web Application. This URL is completely looks different than the actual URL of the Web Application. However this URL will be pointed / linked to the same Web Application.

Flow:


 sharepoint 2013 alternate access mappings

sharepoint 2013 alternate access mappings

1. User requested SharePoint site and it must be resolved in DNS fist and then it will routed back to load balancer (or) SharePoint Web Front End Server (SP-WFE)
2. IN WFE, IIS will receive the request and look for an IIS binding or an IIS Site
3. Once IIS matches the one of the Sites then the request will go to SharePoint and render the SharePoint site to user
Note: The load balancer can any this like F5 / NetScaler / Kemp etc

Key Points:
Please follow the below 3 key points white working with Alternate Access Mappings

  • Alternate Access Mappings managed from Central admin will affect only in SharePoint alone.
  • Changing an Alternate Access Mapping does not make any changes in DNS or IIS
  • Whenever a new URL to be mapped to a Web Application nor edit the existed should be implemented in 3 different places:

1. DNS (Domain Name Server)
2. IIS
3. AAM

Create and Configure Alternate Access Mapping:

1. Log-on to Application server with FARM administrator account
2. Central Administration -> Configure alternate access mappings

alternate access mapping sharepoint 2016
alternate access mapping sharepoint 2016

3. It will take you to next page and you will be able to add / edit the Alternate Access Mappings

sharepoint 2013 central admin alternate access mapping
sharepoint 2013 central admin alternate access mapping

4. Click on “Add Internal URLs”


configure alternate access mappings sharepoint 2013 step by step
configure alternate access mappings sharepoint 2013 step by step

5. As soon as you create the Alternate Access Mapping you need to ensure that same has been added to DNS. It can be done by only IT.
6. After adding the DNS entry you need do the mapping in IIS also.

Steps to be followed:
– Open Internet Information Services
– Expand Sites and select the required web application
– Click on the bindings under Actions

configure alternate access mappings sharepoint 2016 step by step
configure alternate access mappings sharepoint 2016 step by step

–  Click on add on Add on the popup



configure alternate access mappings sharepoint 2013
configure alternate access mappings sharepoint 2013

– Enter the URL and click on OK.

configure alternate access mappings sharepoint 2016
configure alternate access mappings sharepoint 2016

7. Open the URL in IE

configure alternate access mappings sharepoint 2010
configure alternate access mappings sharepoint 2010

Hope this helps !!!!!

Similar SharePoint 2013 Tutorials


About Krishna Vandanapu

I am Krishna.Vandanapu a SharePoint architect working in IT from last 12 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

View all posts by Krishna Vandanapu →

Leave a Reply