You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/sharepoint-on-premises-tutorial.md
+32-32Lines changed: 32 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,15 +55,16 @@ To add SharePoint on-premises from the gallery, perform the following steps:
55
55
56
56
4. In the search box, type **SharePoint on-premises**, select **SharePoint on-premises** from result panel.
57
57
58
-
[!div class="mx-imgBorder"]
59
-

58
+
> [!div class="mx-imgBorder"]
59
+
> 
60
60
61
61
1. Specify a name for your SharePoint OnPrem and click the **Add** button to add the application.
62
62
63
63
1. In the new Enterprise Application click on Properties and check the value for **User assignment required**
64
64
65
-
[!div class="mx-imgBorder"]
66
-

65
+
> [!div class="mx-imgBorder"]
66
+
> 
67
+
67
68
in our scenario this value is set to **No**.
68
69
69
70
## Configure and test Azure AD
@@ -96,8 +97,8 @@ To configure Azure AD single sign-on with SharePoint on-premises, perform the fo
96
97
97
98
4. On the **Basic SAML Configuration** section, perform the following steps:
98
99
99
-
[!div class="mx-imgBorder"]
100
-

100
+
> [!div class="mx-imgBorder"]
101
+
> 
101
102
102
103
1. In the **Identifier** box, type a URL using the following pattern:
103
104
`urn:<sharepointFarmName>:<federationName>`
@@ -114,8 +115,8 @@ To configure Azure AD single sign-on with SharePoint on-premises, perform the fo
114
115
115
116
5. 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.

186
+
> [!div class="mx-imgBorder"]
187
+
> 
187
188
188
189
c. Select **Show password** check box, and then write down the value that's displayed in the Password box.
189
190
@@ -199,25 +200,24 @@ The objective of this section is to create a test user in the Azure portal.
199
200
200
201
3. 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**.
201
202
202
-
[!div class="mx-imgBorder"]
203
-

203
+
> [!div class="mx-imgBorder"]
204
+
> 
204
205
205
206
### Grant permissions to Azure Active Directory account in SharePoint on-premises
206
207
207
208
To Grant access to the Azure Active Directory User in the on-premise SharePoint you need to share the site collection or add the Azure Active Directory User to one of the site collection's group.Users can now sign into SharePoint 201x 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 claims types that are 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. This can prevent users from successfully accessing resources.
213
214
214
215
**To fix the people picker** with this scenario, there is an open-source solution called [AzureCP](https://yvand.github.io/AzureCP/) that provides a custom claims provider for SharePoint 2013, 2016 and 2019. It will use the Microsoft Graph API to resolve what users enter and perform validation. Learn more at [AzureCP](https://yvand.github.io/AzureCP/).
215
216
216
217
> [!NOTE]
217
-
> without AzureCP you can add Groups by adding the Azure AD group's ID but this is not user's friendly and reliable.
218
-
There is how it looks:
219
-
[!div class="mx-imgBorder"]
220
-

218
+
> without AzureCP you can add Groups by adding the Azure AD group's ID but this is not user's friendly and reliable. There is how it looks:
219
+
> [!div class="mx-imgBorder"]
220
+
> 
221
221
222
222
### Grant permissions to Azure AD group in SharePoint on-premises
223
223
@@ -240,8 +240,8 @@ To grant access to the Azure Active Directory Security Group in the on-premise S
240
240
241
241
1. Browse to the SharePoint Site Collection, under Site Settings for the Site Collection, click on "People and groups". Select the SharePoint group then click on New, "Add Users to this Group" and start to type the name of your group the People Picker will display the Azure Active Directory Security Group.
242
242
243
-
[!div class="mx-imgBorder"]
244
-

243
+
> [!div class="mx-imgBorder"]
244
+
>
245
245
246
246
### Grant access to a Guest account to SharePoint on-premises in the Azure portal
247
247
@@ -255,13 +255,13 @@ it's now possible to grant access to your SharePoint Site to a Guest Account in
255
255
256
256
1. Change the **Source Attribute** Property to the value **user.localuserprincipalname** and **save**.
4. On the SharePoint server, open the **SharePoint 201x Management Shell** and execute the following commands, using the name of the trusted identity token issuer that you used previously.
0 commit comments