Skip to content

Commit 97cf2fb

Browse files
authored
Merge pull request #89130 from v-sonan/user/v-sonan/blink
blink provisioning tutorial
2 parents 46e9224 + 1ba7883 commit 97cf2fb

File tree

4 files changed

+150
-0
lines changed

4 files changed

+150
-0
lines changed
Lines changed: 148 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,148 @@
1+
---
2+
title: 'Tutorial: Configure Blink for automatic user provisioning with Azure Active Directory | Microsoft Docs'
3+
description: Learn how to configure Azure Active Directory to automatically provision and de-provision user accounts to Blink.
4+
services: active-directory
5+
documentationcenter: ''
6+
author: zchia
7+
writer: zchia
8+
manager: beatrizd
9+
10+
ms.assetid: 9ebcbf4a-0cf9-41c3-96af-d8ab6ab11639
11+
ms.service: active-directory
12+
ms.subservice: saas-app-tutorial
13+
ms.workload: identity
14+
ms.tgt_pltfrm: na
15+
ms.devlang: na
16+
ms.topic: article
17+
ms.date: 09/19/2019
18+
ms.author: Zhchia
19+
---
20+
21+
# Tutorial: Configure Blink for automatic user provisioning
22+
23+
The objective of this tutorial is to demonstrate the steps to be performed in Blink and Azure Active Directory (Azure AD) to configure Azure AD to automatically provision and de-provision users and/or groups to Blink.
24+
25+
> [!NOTE]
26+
> This tutorial describes a connector built on top of the Azure AD User Provisioning Service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../manage-apps/user-provisioning.md).
27+
>
28+
> This connector is currently in Public Preview. For more information on the general Microsoft Azure terms of use for Preview features, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
29+
30+
## Prerequisites
31+
32+
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
33+
34+
* An Azure AD tenant
35+
* [A Blink tenant](https://joinblink.com/pricing)
36+
* A user account in Blink with Admin permissions.
37+
38+
## Assigning users to Blink
39+
40+
Azure Active Directory uses a concept called *assignments* to determine which users should receive access to selected apps. In the context of automatic user provisioning, only the users and/or groups that have been assigned to an application in Azure AD are synchronized.
41+
42+
Before configuring and enabling automatic user provisioning, you should decide which users and/or groups in Azure AD need access to Blink. Once decided, you can assign these users and/or groups to Blink by following the instructions here:
43+
* [Assign a user or group to an enterprise app](../manage-apps/assign-user-or-group-access-portal.md)
44+
45+
## Important tips for assigning users to Blink
46+
47+
* It is recommended that a single Azure AD user is assigned to Blink to test the automatic user provisioning configuration. Additional users and/or groups may be assigned later.
48+
49+
* When assigning a user to Blink, you must select any valid application-specific role (if available) in the assignment dialog. Users with the **Default Access** role are excluded from provisioning.
50+
51+
## Setup Blink for provisioning
52+
53+
1. Log a [Support Case](https://help.joinblink.com/hc/requests/new) or email **Blink support** at [email protected] to request a SCIM token. .
54+
55+
2. Copy the **SCIM Authentication Token**. This value will be entered in the Secret Token field in the Provisioning tab of your Blink application in the Azure portal.
56+
57+
## Add Blink from the gallery
58+
59+
Before configuring Blink for automatic user provisioning with Azure AD, you need to add Blink from the Azure AD application gallery to your list of managed SaaS applications.
60+
61+
**To add Blink from the Azure AD application gallery, perform the following steps:**
62+
63+
1. In the **[Azure portal](https://portal.azure.com)**, in the left navigation panel, select **Azure Active Directory**.
64+
65+
![The Azure Active Directory button](common/select-azuread.png)
66+
67+
2. Go to **Enterprise applications**, and then select **All applications**.
68+
69+
![The Enterprise applications blade](common/enterprise-applications.png)
70+
71+
3. To add a new application, select the **New application** button at the top of the pane.
72+
73+
![The New application button](common/add-new-app.png)
74+
75+
4. In the search box, enter **Blink**, select **Blink** in the results panel, and then click the **Add** button to add the application.
76+
77+
![Blink in the results list](common/search-new-app.png)
78+
79+
## Configuring automatic user provisioning to Blink
80+
81+
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in Blink based on user and/or group assignments in Azure AD.
82+
83+
> [!TIP]
84+
> You may also choose to enable SAML-based single sign-on for Blink , following the instructions provided in the [Blink Single sign-on tutorial](https://docs.microsoft.com/azure/active-directory/saas-apps/blink-tutorial). Single sign-on can be configured independently of automatic user provisioning, though these two features compliment each other
85+
86+
### To configure automatic user provisioning for Blink in Azure AD:
87+
88+
1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
89+
90+
![Enterprise applications blade](common/enterprise-applications.png)
91+
92+
2. In the applications list, select **Blink**.
93+
94+
![The Blink link in the Applications list](common/all-applications.png)
95+
96+
3. Select the **Provisioning** tab.
97+
98+
![Provisioning tab](common/provisioning.png)
99+
100+
4. Set the **Provisioning Mode** to **Automatic**.
101+
102+
![Provisioning tab](common/provisioning-automatic.png)
103+
104+
5. Under the **Admin Credentials** section, input `https://api.joinblink.com/scim` in **Tenant URL**. Input the **SCIM Authentication Token** value retrieved earlier in **Secret Token**. Click **Test Connection** to ensure Azure AD can connect to Blink. If the connection fails, ensure your Blink account has Admin permissions and try again.
105+
106+
![Tenant URL + Token](common/provisioning-testconnection-tenanturltoken.png)
107+
108+
6. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and check the checkbox - **Send an email notification when a failure occurs**.
109+
110+
![Notification Email](common/provisioning-notification-email.png)
111+
112+
7. Click **Save**.
113+
114+
8. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Blink**.
115+
116+
![Blink User Mappings](media/blink-provisioning-tutorial/User_mappings.png)
117+
118+
9. Review the user attributes that are synchronized from Azure AD to Blink in the **Attribute Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Blink for update operations. Select the **Save** button to commit any changes.
119+
120+
![Blink User Attributes](media/blink-provisioning-tutorial/User_attributes.png)
121+
122+
10. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../manage-apps/define-conditional-rules-for-provisioning-user-accounts.md).
123+
124+
11. To enable the Azure AD provisioning service for Blink, change the **Provisioning Status** to **On** in the **Settings** section.
125+
126+
![Provisioning Status Toggled On](common/provisioning-toggle-on.png)
127+
128+
12. Define the users that you would like to provision to Blink by choosing the desired values in **Scope** in the **Settings** section.
129+
130+
![Provisioning Scope](common/provisioning-scope.png)
131+
132+
15. When you are ready to provision, click **Save**.
133+
134+
![Saving Provisioning Configuration](common/provisioning-configuration-save.png)
135+
136+
This operation starts the initial synchronization of all users and/or groups defined in **Scope** in the **Settings** section. The initial sync takes longer to perform than subsequent syncs, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running. You can use the **Synchronization Details** section to monitor progress and follow links to provisioning activity report, which describes all actions performed by the Azure AD provisioning service on Blink.
137+
138+
For more information on how to read the Azure AD provisioning logs, see [Reporting on automatic user account provisioning](../manage-apps/check-status-user-account-provisioning.md).
139+
140+
## Additional resources
141+
142+
* [Managing user account provisioning for Enterprise Apps](../manage-apps/configure-automatic-user-provisioning-portal.md)
143+
* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
144+
145+
## Next steps
146+
147+
* [Learn how to review logs and get reports on provisioning activity](../manage-apps/check-status-user-account-provisioning.md)
148+
48.4 KB
Loading
7.85 KB
Loading

articles/active-directory/saas-apps/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1476,6 +1476,8 @@
14761476
href: atlassian-cloud-provisioning-tutorial.md
14771477
- name: BitaBIZ
14781478
href: bitabiz-provisioning-tutorial.md
1479+
- name: Blink
1480+
href: blink-provisioning-tutorial.md
14791481
- name: BlueJeans
14801482
href: bluejeans-provisioning-tutorial.md
14811483
- name: Bonusly

0 commit comments

Comments
 (0)