Tutorial: Azure Active Directory integration with SharePoint on-premises
In this tutorial, you learn how to integrate SharePoint on-premises with Azure Active Directory (Azure AD). Integrating SharePoint on-premises with Azure AD provides you with the following benefits:
- You can control in Azure AD who has access to SharePoint on-premises.
- You can enable your users to be automatically signed-in to SharePoint on-premises (Single Sign-On) with their Azure AD accounts.
- You can manage your accounts in one central location - the Azure portal.
If you want to know more details about SaaS app integration with Azure AD, see What is application access and single sign-on with Azure Active Directory. If you don't have an Azure subscription, create a free account before you begin.
To configure Azure AD integration with SharePoint on-premises, you need the following items:
- An Azure AD subscription. If you don't have an Azure AD environment, you can get a free account
- SharePoint on-premises single sign-on enabled subscription
In this tutorial, you configure and test Azure AD single sign-on in a test environment.
- SharePoint on-premises supports SP initiated SSO
Adding SharePoint on-premises from the gallery
To configure the integration of SharePoint on-premises into Azure AD, you need to add SharePoint on-premises from the gallery to your list of managed SaaS apps.
To add SharePoint on-premises from the gallery, perform the following steps:
In the Azure portal, on the left navigation panel, click Azure Active Directory icon.
If the element should not be available, it can also be opened through the fixed All services link at the top of the left navigation panel. In the following overview, the Azure Active Directory link is located in the Identity section or it can be searched for by using the filter text box.
Navigate to Enterprise Applications and then select the All Applications option.
To add new application, click New application button on the top of dialog.
In the search box, type SharePoint on-premises, select SharePoint on-premises from result panel then click Add button to add the application.
Configure and test Azure AD single sign-on
In this section, you configure and test Azure AD single sign-on with SharePoint on-premises based on a test user called Britta Simon. For single sign-on to work, a link relationship between an Azure AD user and the related user in SharePoint on-premises needs to be established.
To configure and test Azure AD single sign-on with SharePoint on-premises, you need to complete the following building blocks:
- Configure Azure AD Single Sign-On - to enable your users to use this feature.
- Configure SharePoint on-premises Single Sign-On - to configure the Single Sign-On settings on application side.
- Create an Azure AD test user - to test Azure AD single sign-on with Britta Simon.
- Create an Azure AD Security Group in the Azure portal - to enable a new security group in Azure AD for single sign-on.
- Grant access to SharePoint on-premises Security Group - grant access for particular group to Azure AD.
- Assign the Azure AD Security Group in the Azure portal - to assign the particular group to Azure AD for authentication.
- Test single sign-on - to verify whether the configuration works.
Configure Azure AD single sign-on
In this section, you enable Azure AD single sign-on in the Azure portal.
To configure Azure AD single sign-on with SharePoint on-premises, perform the following steps:
In the Azure portal, on the SharePoint on-premises application integration page, select Single sign-on.
On the Select a Single sign-on method dialog, select SAML/WS-Fed mode to enable single sign-on.
On the Set up Single Sign-On with SAML page, click Edit icon to open Basic SAML Configuration dialog.
On the Basic SAML Configuration section, perform the following steps:
a. In the Sign-on URL text box, type a URL using the following pattern:
b. In the Identifier box, type a URL using the following pattern:
c. In the Reply URL text box, type a URL using the following pattern:
These values are not real. Update these values with the actual Sign-On URL, Identifier and Reply URL. Contact SharePoint on-premises Client support team to get these values. You can also refer to the patterns shown in the Basic SAML Configuration section in the Azure portal.
On the Set up Single Sign-On with SAML page, in the SAML Signing Certificate section, click Download to download the Certificate (Base64) from the given options as per your requirement and save it on your computer.
Please note down the file path to which you have downloaded the certificate file, as you need to use it later in the PowerShell script for configuration.
On the Set up SharePoint on-premises section, copy the appropriate URL(s) as per your requirement. For Single Sign-On Service URL, use a value of the following pattern:
my_directory_id is the tenant id of Azure Ad subscription.
a. Login URL
b. Azure AD Identifier
c. Logout URL
Sharepoint On-Premises application uses SAML 1.1 token, so Azure AD expects WS Fed request from SharePoint server and after authentication, it issues the SAML 1.1. token.
Configure SharePoint on-premises Single Sign-On
In a different web browser window, sign in to your SharePoint on-premises company site as an administrator.
Configure a new trusted identity provider in SharePoint Server 2016
Sign into the SharePoint Server 2016 server and open the SharePoint 2016 Management Shell. Fill in the values of $realm (Identifier value from the SharePoint on-premises Domain and URLs section in the Azure portal), $wsfedurl (Single Sign-On Service URL), and $filepath (file path to which you have downloaded the certificate file) from Azure portal and run the following commands to configure a new trusted identity provider.
If you're new to using PowerShell or want to learn more about how PowerShell works, see SharePoint PowerShell.
$realm = "<Identifier value from the SharePoint on-premises Domain and URLs section in the Azure portal>" $wsfedurl="<SAML single sign-on service URL value which you have copied from the Azure portal>" $filepath="<Full path to SAML signing certificate file which you have downloaded from the Azure portal>" $cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2($filepath) New-SPTrustedRootAuthority -Name "AzureAD" -Certificate $cert $map = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name" -IncomingClaimTypeDisplayName "name" -LocalClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn" $map2 = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname" -IncomingClaimTypeDisplayName "GivenName" -SameAsIncoming $map3 = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname" -IncomingClaimTypeDisplayName "SurName" -SameAsIncoming $map4 = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress" -IncomingClaimTypeDisplayName "Email" -SameAsIncoming $map5 = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.microsoft.com/ws/2008/06/identity/claims/role" -IncomingClaimTypeDisplayName "Role" -SameAsIncoming $ap = New-SPTrustedIdentityTokenIssuer -Name "AzureAD" -Description "SharePoint secured by Azure AD" -realm $realm -ImportTrustCertificate $cert -ClaimsMappings $map,$map2,$map3,$map4,$map5 -SignInUrl $wsfedurl -IdentifierClaim "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name"
Next, follow these steps to enable the trusted identity provider for your application:
a. In Central Administration, navigate to Manage Web Application and select the web application that you wish to secure with Azure AD.
b. In the ribbon, click Authentication Providers and choose the zone that you wish to use.
c. Select Trusted Identity provider and select the identify provider you just registered named AzureAD.
d. On the sign-in page URL setting, select Custom sign in page and provide the value “/_trust/”.
e. Click OK.
Some of the external users will not able to use this single sign-on integration as their UPN will have mangled value something like
MYEMAIL_outlook.com#ext#@TENANT.onmicrosoft.com. Soon we will allow customers app config on how to handle the UPN depending on the user type. After that all your guest users should be able to use SSO seamlessly as the organization employees.
Create an Azure AD test user
The objective of this section is to create a test user in the Azure portal called Britta Simon.
In the Azure portal, in the left pane, select Azure Active Directory, select Users, and then select All users.
Select New user at the top of the screen.
In the User properties, perform the following steps.
a. In the Name field enter BrittaSimon.
b. In the User name field type
For example, BrittaSimon@contoso.com
c. Select Show password check box, and then write down the value that's displayed in the Password box.
d. Click Create.
Create an Azure AD Security Group in the Azure portal
Click on Azure Active Directory > All Groups.
Click New group:
Fill in Group type, Group name, Group description, Membership type. Click on the arrow to select members, then search for or click on the member you will like to add to the group. Click on Select to add the selected members, then click on Create.
In order to assign Azure Active Directory Security Groups to SharePoint on-premises, it will be necessary to install and configure AzureCP in the on-premises SharePoint farm OR develop and configure an alternative custom claims provider for SharePoint. See the more information section at the end of the document for creating your own custom claims provider, if you don’t use AzureCP.
Grant access to SharePoint on-premises Security Group
Configure Security Groups and Permissions on the App Registration
In the Azure portal, select Azure Active Directory, then select App registrations.
In the search box, type and select SharePoint on-premises.
Click on Manifest.
SecurityGroup. Then, click on Save
Click on Settings, then click on Required permissions.
Click on Add and then Select an API.
Add both Windows Azure Active Directory and Microsoft Graph API, but it’s only possible to select one at a time.
Select Windows Azure Active Directory, check Read directory data and click on Select. Go back and add Microsoft Graph and select Read directory data for it, as well. Click on Select and click on Done.
Now, under Required Settings, click on Grant permissions and then Click Yes to Grant permissions.
Check under notifications to determine if the permissions were successfully granted. If they are not, then the AzureCP will not work properly and it won’t be possible to configure SharePoint on-premises with Azure Active Directory Security Groups.
Configure the AzureCP on the SharePoint on-premises farm or an alternative custom claims provider solution. In this example, we are using AzureCP.
Please note that AzureCP is not a Microsoft product or supported by Microsoft Technical Support. Download, install and configure AzureCP on the on-premises SharePoint farm per https://yvand.github.io/AzureCP/
Grant access to the Azure Active Directory Security Group in the on-premises SharePoint :- The groups must be granted access to the application in SharePoint on-premises. Use the following steps to set the permissions to access the web application.
In Central Administration, click on Application Management, Manage web applications, then select the web application to activate the ribbon and click on User Policy.
Under Policy for Web Application, click on Add Users, then select the zone, click on Next. Click on the Address Book.
Then, search for and add the Azure Active Directory Security Group and click on OK.
Select the Permissions, then click on Finish.
See under Policy for Web Application, the Azure Active Directory Group is added. The group claim shows the Azure Active Directory Security Group Object ID for the User Name.
Browse to the SharePoint site collection and add the Group there, as well. Click on Site Settings, then click Site permissions and Grant Permissions. Search for the Group Role claim, assign the permission level and click Share.
Configuring one trusted identity provider for multiple web applications
The configuration works for a single web application, but needs additional configuration if you intend to use the same trusted identity provider for multiple web applications. For example, assume we had extended a web application to use the URL
https://portal.contoso.local and now want to authenticate the users to
https://sales.contoso.local as well. To do this, we need to update the identity provider to honor the WReply parameter and update the application registration in Azure AD to add a reply URL.
In the Azure portal, open the Azure AD directory. Click App registrations, then click View all applications. Click the application that you created previously (SharePoint SAML Integration).
In the settings blade, click Reply URLs.
Add the URL for the additional web application with
/_trust/default.aspxappended to the URL (such as
https://sales.contoso.local/_trust/default.aspx) and click Save.
On the SharePoint server, open the SharePoint 2016 Management Shell and execute the following commands, using the name of the trusted identity token issuer that you used previously.
$t = Get-SPTrustedIdentityTokenIssuer "AzureAD" $t.UseWReplyParameter=$true $t.Update()
In Central Administration, go to the web application and enable the existing trusted identity provider. Remember to also configure the sign-in page URL as a custom sign in page
In Central Administration, click the web application and choose User Policy. Add a user with the appropriate permissions as demonstrated previously in this article.
Fixing People Picker
Users can now sign into SharePoint 2016 using identities from Azure AD, but there are still opportunities for improvement to the user experience. For instance, searching for a user presents multiple search results in the people picker. There is a search result for each of the 3 claim types that were created in the claim mapping. To choose a user using the people picker, you must type their user name exactly and choose the name claim result.
There is no validation on the values you search for, which can lead to misspellings or users accidentally choosing the wrong claim type to assign such as the SurName claim. This can prevent users from successfully accessing resources.
To assist with this scenario, there is an open-source solution called AzureCP that provides a custom claims provider for SharePoint 2016. It will use the Microsoft Graph API to resolve what users enter and perform validation. Learn more at AzureCP.
Assign the Azure AD Security Group in the Azure portal
In the Azure portal, select Enterprise Applications, select All applications, then select SharePoint on-premises.
In the applications list, type and select SharePoint on-premises.
In the menu on the left, select Users and groups.
Click the Add user.
Search for the Security Group you want to use, then click on the group to add it to the Select members section. Click Select, then click Assign.
Check the notifications in the menu bar to be notified that the Group was successfully assigned to the Enterprise application in the Azure portal.
Create SharePoint on-premises test user
In this section, you create a user called Britta Simon in SharePoint on-premises. Work with SharePoint on-premises support team to add the users in the SharePoint on-premises platform. Users must be created and activated before you use single sign-on.
Test single sign-on
In this section, you test your Azure AD single sign-on configuration using the Access Panel.
When you click the SharePoint on-premises tile in the Access Panel, you should be automatically signed in to the SharePoint on-premises for which you set up SSO. For more information about the Access Panel, see Introduction to the Access Panel.