Skip to content

Commit e82d09f

Browse files
committed
2 parents 740f6e3 + e1e0c14 commit e82d09f

File tree

53 files changed

+904
-74
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

53 files changed

+904
-74
lines changed
Lines changed: 161 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,161 @@
1+
---
2+
title: 'Tutorial: Configure Brivo Onair Identity Connector 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 Brivo Onair Identity Connector.
4+
services: active-directory
5+
documentationcenter: ''
6+
author: zchia
7+
writer: zchia
8+
manager: beatrizd
9+
10+
ms.assetid: 542ce04c-ef7d-4154-9b0e-7f68e1154f6b
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: 10/01/2019
18+
ms.author: Zhchia
19+
---
20+
21+
# Tutorial: Configure Brivo Onair Identity Connector for automatic user provisioning
22+
23+
The objective of this tutorial is to demonstrate the steps to be performed in Brivo Onair Identity Connector and Azure Active Directory (Azure AD) to configure Azure AD to automatically provision and de-provision users and/or groups to Brivo Onair Identity Connector.
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 Brivo Onair Identity Connector tenant](https://www.brivo.com/quote)
36+
* A user account in Brivo Onair Identity Connector with Senior Administrator permissions.
37+
38+
## Assigning users to Brivo Onair Identity Connector
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 Brivo Onair Identity Connector. Once decided, you can assign these users and/or groups to Brivo Onair Identity Connector 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 Brivo Onair Identity Connector
46+
47+
* It is recommended that a single Azure AD user is assigned to Brivo Onair Identity Connector to test the automatic user provisioning configuration. Additional users and/or groups may be assigned later.
48+
49+
* When assigning a user to Brivo Onair Identity Connector, 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 Brivo Onair Identity Connector for provisioning
52+
53+
1. Sign in to your [Brivo Onair Identity Connector Admin Console](https://acs.brivo.com/login/). Navigate to **Account > Account Settings**.
54+
55+
![Brivo Onair Identity Connector Admin Console](media/brivo-onair-identity-connector-provisioning-tutorial/admin.png)
56+
57+
2. Click on **Azure AD** tab. On the **Azure AD** details page re-enter the password of your senior administrator account. Click on **Submit**.
58+
59+
![Brivo Onair Identity Connector azure](media/brivo-onair-identity-connector-provisioning-tutorial/azuread.png)
60+
61+
3. Click on **Copy Token** button and save the **Secret Token**. This value will be entered in the Secret Token field in the Provisioning tab of your Brivo Onair Identity Connector application in the Azure portal.
62+
63+
![Brivo Onair Identity Connector token](media/brivo-onair-identity-connector-provisioning-tutorial/token.png)
64+
65+
## Add Brivo Onair Identity Connector from the gallery
66+
67+
Before configuring Brivo Onair Identity Connector for automatic user provisioning with Azure AD, you need to add Brivo Onair Identity Connector from the Azure AD application gallery to your list of managed SaaS applications.
68+
69+
**To add Brivo Onair Identity Connector from the Azure AD application gallery, perform the following steps:**
70+
71+
1. In the **[Azure portal](https://portal.azure.com)**, in the left navigation panel, select **Azure Active Directory**.
72+
73+
![The Azure Active Directory button](common/select-azuread.png)
74+
75+
2. Go to **Enterprise applications**, and then select **All applications**.
76+
77+
![The Enterprise applications blade](common/enterprise-applications.png)
78+
79+
3. To add a new application, select the **New application** button at the top of the pane.
80+
81+
![The New application button](common/add-new-app.png)
82+
83+
4. In the search box, enter **Brivo Onair Identity Connector**, select **Brivo Onair Identity Connector** in the results panel, and then click the **Add** button to add the application.
84+
85+
![Brivo Onair Identity Connector in the results list](common/search-new-app.png)
86+
87+
## Configuring automatic user provisioning to Brivo Onair Identity Connector
88+
89+
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in Brivo Onair Identity Connector based on user and/or group assignments in Azure AD.
90+
91+
### To configure automatic user provisioning for Brivo Onair Identity Connector in Azure AD:
92+
93+
1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
94+
95+
![Enterprise applications blade](common/enterprise-applications.png)
96+
97+
2. In the applications list, select **Brivo Onair Identity Connector**.
98+
99+
![The Brivo Onair Identity Connector link in the Applications list](common/all-applications.png)
100+
101+
3. Select the **Provisioning** tab.
102+
103+
![Provisioning tab](common/provisioning.png)
104+
105+
4. Set the **Provisioning Mode** to **Automatic**.
106+
107+
![Provisioning tab](common/provisioning-automatic.png)
108+
109+
5. Under the **Admin Credentials** section, input `https://scim.brivo.com/ActiveDirectory/v2/` in **Tenant URL**. Input the **SCIM Authentication Token** value retrieved earlier in **Secret Token**. Click **Test Connection** to ensure Azure AD can connect to Brivo Onair Identity Connector. If the connection fails, ensure your Brivo Onair Identity Connector account has Admin permissions and try again.
110+
111+
![Tenant URL + Token](common/provisioning-testconnection-tenanturltoken.png)
112+
113+
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**.
114+
115+
![Notification Email](common/provisioning-notification-email.png)
116+
117+
7. Click **Save**.
118+
119+
8. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Brivo Onair Identity Connector**.
120+
121+
![Brivo Onair Identity Connector User Mappings](media/brivo-onair-identity-connector-provisioning-tutorial/user-mappings.png )
122+
123+
9. Review the user attributes that are synchronized from Azure AD to Brivo Onair Identity Connector in the **Attribute Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Brivo Onair Identity Connector for update operations. Select the **Save** button to commit any changes.
124+
125+
![Brivo Onair Identity Connector User Attributes](media/brivo-onair-identity-connector-provisioning-tutorial/user-attributes.png)
126+
127+
10. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to Brivo Onair Identity Connector**.
128+
129+
![Brivo Onair Identity Connector Group Mappings](media/brivo-onair-identity-connector-provisioning-tutorial/group-mappings.png)
130+
131+
11. Review the group attributes that are synchronized from Azure AD to Brivo Onair Identity Connector in the **Attribute Mapping** section. The attributes selected as **Matching** properties are used to match the groups in Brivo Onair Identity Connector for update operations. Select the **Save** button to commit any changes.
132+
133+
![Brivo Onair Identity Connector Group Attributes](media/brivo-onair-identity-connector-provisioning-tutorial/group-attributes.png)
134+
135+
12. 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).
136+
137+
13. To enable the Azure AD provisioning service for Brivo Onair Identity Connector, change the **Provisioning Status** to **On** in the **Settings** section.
138+
139+
![Provisioning Status Toggled On](common/provisioning-toggle-on.png)
140+
141+
14. Define the users and/or groups that you would like to provision to Brivo Onair Identity Connector by choosing the desired values in **Scope** in the **Settings** section.
142+
143+
![Provisioning Scope](common/provisioning-scope.png)
144+
145+
15. When you are ready to provision, click **Save**.
146+
147+
![Saving Provisioning Configuration](common/provisioning-configuration-save.png)
148+
149+
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 Brivo Onair Identity Connector.
150+
151+
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).
152+
153+
## Additional resources
154+
155+
* [Managing user account provisioning for Enterprise Apps](../manage-apps/configure-automatic-user-provisioning-portal.md)
156+
* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
157+
158+
## Next steps
159+
160+
* [Learn how to review logs and get reports on provisioning activity](../manage-apps/check-status-user-account-provisioning.md)
161+

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

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The objective of this tutorial is to demonstrate the steps to be performed in G
2828
> [!NOTE]
2929
> The G Suite connector was recently updated on October 2019. Changes made to the G Suite connector include:
3030
- Added support for additional G Suite user and group attributes.
31-
- Updated G Suite target attribute names to match what is defined [here](/azure/active-directory/manage-apps/customize-application-attributes).
31+
- Updated G Suite target attribute names to match what is defined [here](https://developers.google.com/admin-sdk/directory).
3232
- Updated default attribute mappings.
3333

3434
## Prerequisites
@@ -125,6 +125,9 @@ This section guides you through the steps to configure the Azure AD provisioning
125125
> [!TIP]
126126
> You may also choose to enable SAML-based single sign-on for G Suite , following the instructions provided in the [G Suite Single sign-on tutorial](https://docs.microsoft.com/azure/active-directory/saas-apps/google-apps-tutorial). Single sign-on can be configured independently of automatic user provisioning, though these two features compliment each other.
127127
128+
> [!NOTE]
129+
> To learn more about G Suite's Directory API endpoint, refer to [Directory API](https://developers.google.com/admin-sdk/directory).
130+
128131
### To configure automatic user provisioning for G Suite in Azure AD:
129132

130133
1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
@@ -193,15 +196,6 @@ This operation starts the initial synchronization of all users and/or groups def
193196

194197
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).
195198

196-
> [!NOTE]
197-
> Another viable option for automating user provisioning to G Suite is to use [Google Cloud Directory Sync](https://support.google.com/a/answer/106368?hl=en). This option provisions your on-premises Active Directory identities to G Suite.
198-
199-
## Common issues
200-
* G Suite requires that all provisioned users are from verified domains. Ensure that any user that you would like to provision has a UPN from a verified domain in G Suite. If a user from an un verified domain is in scope for provisioning, you will see an error in the [provisioning logs](https://docs.microsoft.com/azure/active-directory/reports-monitoring/concept-provisioning-logs) such as "GoogleAppsInvalidDomain". You can prevent these errors and ensure that users from unverified domains are out of scope by using a [scoping filter](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts).
201-
* Target attribute: userPrincipalName
202-
* Operator: REGEX MATCH or NOT REGEX MATCH
203-
* Value: .*@domain.com
204-
205199
## Additional resources
206200

207201
* [Managing user account provisioning for Enterprise Apps](../manage-apps/configure-automatic-user-provisioning-portal.md)
44.9 KB
Loading
139 KB
Loading
Loading
11.5 KB
Loading
197 KB
Loading
30.8 KB
Loading
8.99 KB
Loading

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1545,6 +1545,8 @@
15451545
href: bonusly-provisioning-tutorial.md
15461546
- name: Box
15471547
href: box-userprovisioning-tutorial.md
1548+
- name: Brivo Onair Identity Connector
1549+
href: brivo-onair-identity-connector-provisioning-tutorial.md
15481550
- name: Cerner Central
15491551
href: cernercentral-provisioning-tutorial.md
15501552
- name: Cisco Webex

0 commit comments

Comments
 (0)