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/aws-multi-accounts-tutorial.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ If you want to know more details about SaaS app integration with Azure AD, see [
38
38
39
39
**Please note that we do not recommend to use this approach for following reasons:**
40
40
41
-
* You have to use the Graph Explorer approach to patch all the roles to the app. We don’t recommend using the manifest file approach.
41
+
* You have to use the Microsoft Graph Explorer approach to patch all the roles to the app. We don’t recommend using the manifest file approach.
42
42
43
43
* We have seen customers reporting that after adding ~1200 app roles for a single AWS app, any operation on the app started throwing the errors related to size. There is a hard limit of size on the application object.
44
44
@@ -243,7 +243,7 @@ In this section, you enable Azure AD single sign-on in the Azure portal and conf
243
243
244
244
16. Perform the above step for all the roles in all the accounts and store all of them in format **Role ARN,Trusted entities** in a notepad.
245
245
246
-
17. Open [Azure AD Graph Explorer](https://developer.microsoft.com/graph/graph-explorer) in another window.
246
+
17. Open [Microsoft Graph Explorer](https://developer.microsoft.com/graph/graph-explorer) in another window.
247
247
248
248
a. Sign in to the Graph Explorer site using the Global Admin/Co-admin credentials for your tenant.
249
249
@@ -322,7 +322,7 @@ In this section, you enable Azure AD single sign-on in the Azure portal and conf
322
322
> [!Note]
323
323
> You can only add new roles after the **msiam_access** for the patch operation. Also, you can add as many roles as you want per your Organization need. Azure AD will send the **value** of these roles as the claim value in SAML response.
324
324
325
-
j. Go back to your Graph Explorer and change the method from **GET** to **PATCH**. Patch the Service Principal object to have desired roles by updating appRoles property similar to the one shown above in the example. Click **Run Query** to execute the patch operation. A success message confirms the creation of the role for your Amazon Web Services application.
325
+
j. Go back to Graph Explorer and change the method from **GET** to **PATCH**. Patch the Service Principal object to have desired roles by updating appRoles property similar to the one shown above in the example. Click **Run Query** to execute the patch operation. A success message confirms the creation of the role for your Amazon Web Services application.
326
326
327
327

328
328
@@ -360,7 +360,7 @@ For more information about the Access Panel, see [Introduction to the Access
360
360
361
361
## Additional resources
362
362
363
-
* [How to configure provisioning using MS Graph APIs](https://docs.microsoft.com/azure/active-directory/manage-apps/application-provisioning-configure-api)
363
+
* [How to configure provisioning using Microsoft Graph APIs](https://docs.microsoft.com/azure/active-directory/manage-apps/application-provisioning-configure-api)
364
364
* [List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory](tutorial-list.md)
365
365
* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/sharepoint-on-premises-tutorial.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -329,7 +329,7 @@ Users can now sign into SharePoint 2016 using identities from Azure AD, but ther
329
329
330
330
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.
331
331
332
-
To assist with this scenario, there is an open-source solution called [AzureCP](https://yvand.github.io/AzureCP/) that provides a custom claims provider for SharePoint 2016. It will use the Azure AD Graph to resolve what users enter and perform validation. Learn more at [AzureCP](https://yvand.github.io/AzureCP/).
332
+
To assist with this scenario, there is an open-source solution called [AzureCP](https://yvand.github.io/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](https://yvand.github.io/AzureCP/).
333
333
334
334
### Assign the Azure AD Security Group in the Azure portal
0 commit comments