Skip to content

Commit a2a9764

Browse files
committed
MediusFlow user provisioning tutorial update
1 parent 83e1a19 commit a2a9764

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/active-directory/saas-apps/mediusflow-provisioning-tutorial.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ This tutorial describes the steps you need to perform in both MediusFlow and Azu
3636
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
3737

3838
* [An Azure AD tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant)
39-
* A user account in Azure AD with [permission](https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-assign-admin-roles) to configure provisioning (e.g. Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator).
39+
* A user account in Azure AD with [permission](https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-assign-admin-roles) to configure provisioning (for example, Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator).
4040
* An active MediusFlow subscription with a Quality assurance or Production tenant.
4141
* A user account in MediusFlow with admin access rights to be able to carry out the configuration within MediusFlow.
4242
* The companies added in the MediusFlow tenant where the users should be provisioned to.
@@ -49,14 +49,14 @@ The scenario outlined in this tutorial assumes that you already have the followi
4949
## Step 2. Configure MediusFlow to support provisioning with Azure AD
5050

5151
### Activate the Office 365 app within MediusFlow
52-
Start by enabling the access of the Azure AD login and the Azure AD configuration feature within MediusFlow by performing the following:
52+
Start by enabling the access of the Azure AD login and the Azure AD configuration feature within MediusFlow by performing the following steps:
5353

5454
#### User login
55-
To enable the login flow to Office 365/Azure AD refer [this](https://success.mediusflow.com/documentation/administration_guide/user_login_and_transfer/office365userintegration/#user-login-setup).
55+
To, enable the login flow to Office 365/Azure AD refer [this] (https://success.mediusflow.com/documentation/administration_guide/user_login_and_transfer/office365userintegration/#user-login-setup) article.
5656

5757
#### User transfer configuration
58-
To enable the configuration portal of the users for provisioning from Azure AD refer [this](
59-
https://success.mediusflow.com/documentation/administration_guide/user_login_and_transfer/office365userintegration/#user-sync-setup).
58+
To, enable the configuration portal of the users for provisioning from Azure AD refer [this](
59+
https://success.mediusflow.com/documentation/administration_guide/user_login_and_transfer/office365userintegration/#user-sync-setup) article.
6060

6161
#### Configure user provisioning
6262

@@ -94,7 +94,7 @@ https://success.mediusflow.com/documentation/administration_guide/user_login_and
9494

9595
![Config users](./media/mediusflow-provisioning-tutorial/8_configure_user_configuration_1.png)
9696

97-
9. Provide the default settings for the users. In this view it is possible to set the default attribute. If the standard settings are ok it is enough to provide just a valid company name. Since these configuration settings are fetched from Mediusflow, they need to be configured first. See the **Prerequisites** section of this article for more information.
97+
9. Provide the default settings for the users. In this view, it is possible to set the default attribute. If the standard settings are ok, it is enough to provide just a valid company name. Since these configuration settings are fetched from Mediusflow, they need to be configured first. For more information see the **Prerequisites** section of this article.
9898

9999
![Config users](./media/mediusflow-provisioning-tutorial/9_configure_user_config_detail_1.png)
100100

@@ -108,15 +108,15 @@ https://success.mediusflow.com/documentation/administration_guide/user_login_and
108108

109109
## Step 3. Add MediusFlow from the Azure AD application gallery
110110

111-
Add MediusFlow from the Azure AD application gallery to start managing provisioning to MediusFlow. If you have previously setup MediusFlow for SSO you can use the same application. However it is recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](https://docs.microsoft.com/azure/active-directory/manage-apps/add-gallery-app).
111+
Add MediusFlow from the Azure AD application gallery to start managing provisioning to MediusFlow. If you have previously setup MediusFlow for SSO, you can use the same application. However it is recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](https://docs.microsoft.com/azure/active-directory/manage-apps/add-gallery-app).
112112

113113
## Step 4. Define who will be in scope for provisioning
114114

115115
The Azure AD provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user / group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following [steps](../manage-apps/assign-user-or-group-access-portal.md) to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described [here](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts).
116116

117117
* When assigning users and groups to MediusFlow, you must select a role other than **Default Access**. Users with the Default Access role are excluded from provisioning and will be marked as not effectively entitled in the provisioning logs. If the only role available on the application is the default access role, you can [update the application manifest](https://docs.microsoft.com/azure/active-directory/develop/howto-add-app-roles-in-azure-ad-apps) to add additional roles.
118118

119-
* Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an [attribute based scoping filter](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts).
119+
* Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control it by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an [attribute based scoping filter](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts).
120120

121121

122122
## Step 5. Configure automatic user provisioning to MediusFlow

0 commit comments

Comments
 (0)