Skip to content

Commit ba29980

Browse files
authored
Merge pull request #103486 from v-sonan/user/v-sonan/teamviewer
TeamViewer provisioning tutorial
2 parents b051a17 + 0b702cb commit ba29980

File tree

7 files changed

+151
-0
lines changed

7 files changed

+151
-0
lines changed
17.5 KB
Loading
15.6 KB
Loading
3.44 KB
Loading
8.38 KB
Loading
19.6 KB
Loading
Lines changed: 149 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,149 @@
1+
---
2+
title: 'Tutorial: Configure TeamViewer for automatic user provisioning with Azure Active Directory | Microsoft Docs'
3+
description: Learn how to automatically provision and de-provision user accounts from Azure AD to TeamViewer.
4+
services: active-directory
5+
documentationcenter: ''
6+
author: Zhchia
7+
writer: Zhchia
8+
manager: beatrizd
9+
10+
ms.assetid: 73dd5494-f572-42bb-9071-d599361b9bd7
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: 01/27/2020
18+
ms.author: Zhchia
19+
---
20+
21+
# Tutorial: Configure TeamViewer for automatic user provisioning
22+
23+
This tutorial describes the steps you need to perform in both TeamViewer and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [TeamViewer](https://www.teamviewer.com/buy-now/) using the Azure AD 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).
24+
25+
26+
## Capabilities supported
27+
> [!div class="checklist"]
28+
> * Create users in TeamViewer
29+
> * Remove users in TeamViewer when they do not require access anymore
30+
> * Keep user attributes synchronized between Azure AD and TeamViewer
31+
> * [Single sign-on](https://docs.microsoft.com/azure/active-directory/saas-apps/teamviewer-tutorial) to TeamViewer (recommended)
32+
33+
## Prerequisites
34+
35+
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
36+
37+
* [An Azure AD tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant)
38+
* 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 TeamViewer account with admin permissions.
40+
41+
## Step 1. Plan your provisioning deployment
42+
1. Learn about [how the provisioning service works](https://docs.microsoft.com/azure/active-directory/manage-apps/user-provisioning).
43+
2. Determine who will be in [scope for provisioning](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts).
44+
3. Determine what data to [map between Azure AD and TeamViewer](https://docs.microsoft.com/azure/active-directory/manage-apps/customize-application-attributes).
45+
46+
## Step 2. Configure TeamViewer to support provisioning with Azure AD
47+
48+
1. Login to the Admin Console of TeamViewer app. Navigate to **Edit Profile**.
49+
50+
![TeamViewer Admin Console](./media/teamviewer-provisioning-tutorial/admin.png)
51+
52+
2. Navigate to **Apps**. Click on **Create Script Token**.
53+
54+
![TeamViewer Create Token](./media/teamviewer-provisioning-tutorial/createtoken.png)
55+
56+
3. Provide a name for the script token. Click on the **Save** button.
57+
58+
![TeamViewer Token Name](./media/teamviewer-provisioning-tutorial/tokenname.png)
59+
60+
4. Copy the **Token** and click **OK**. This value will be entered in the **Secret Token** field of your TeamViewer application in the Azure portal.
61+
62+
![TeamViewer Token](./media/teamviewer-provisioning-tutorial/token.png)
63+
64+
## Step 3. Add TeamViewer from the Azure AD application gallery
65+
66+
Add TeamViewer from the Azure AD application gallery to start managing provisioning to TeamViewer. If you have previously setup TeamViewer 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).
67+
68+
## Step 4. Define who will be in scope for provisioning
69+
70+
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).
71+
72+
* When assigning users and groups to TeamViewer, 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.
73+
74+
* 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).
75+
76+
77+
## Step 5. Configure automatic user provisioning to TeamViewer
78+
79+
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in TestApp based on user and/or group assignments in Azure AD.
80+
81+
### To configure automatic user provisioning for TeamViewer in Azure AD:
82+
83+
1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
84+
85+
![Enterprise applications blade](common/enterprise-applications.png)
86+
87+
2. In the applications list, select **TeamViewer**.
88+
89+
![The TeamViewer link in the Applications list](common/all-applications.png)
90+
91+
3. Select the **Provisioning** tab.
92+
93+
![Provisioning tab](common/provisioning.png)
94+
95+
4. Set the **Provisioning Mode** to **Automatic**.
96+
97+
![Provisioning tab](common/provisioning-automatic.png)
98+
99+
5. Under the **Admin Credentials** section, input your TeamViewer admin credentials and username. Click **Test Connection** to ensure Azure AD can connect to TeamViewer. If the connection fails, ensure your TeamViewer account has Admin permissions and try again.
100+
101+
![provisioning](./media/teamViewer-provisioning-tutorial/provisioning.png)
102+
103+
6. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
104+
105+
![Notification Email](common/provisioning-notification-email.png)
106+
107+
7. Select **Save**.
108+
109+
8. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to TeamViewer**.
110+
111+
9. Review the user attributes that are synchronized from Azure AD to TeamViewer in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in TeamViewer for update operations. If you choose to change the [matching target attribute](https://docs.microsoft.com/azure/active-directory/manage-apps/customize-application-attributes), you will need to ensure that the TeamViewer API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
112+
113+
|Attribute|Type|
114+
|---|---|
115+
|userName|String|
116+
|displayName|String|
117+
|active|Boolean|
118+
119+
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).
120+
121+
11. To enable the Azure AD provisioning service for TeamViewer, change the **Provisioning Status** to **On** in the **Settings** section.
122+
123+
![Provisioning Status Toggled On](common/provisioning-toggle-on.png)
124+
125+
12. Define the users and/or groups that you would like to provision to TeamViewer by choosing the desired values in **Scope** in the **Settings** section.
126+
127+
![Provisioning Scope](common/provisioning-scope.png)
128+
129+
13. When you are ready to provision, click **Save**.
130+
131+
![Saving Provisioning Configuration](common/provisioning-configuration-save.png)
132+
133+
This operation starts the initial synchronization cycle of all users and groups defined in **Scope** in the **Settings** section. The initial cycle takes longer to perform than subsequent cycles, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running.
134+
135+
## Step 6. Monitor your deployment
136+
Once you've configured provisioning, use the following resources to monitor your deployment:
137+
138+
* Use the [provisioning logs](https://docs.microsoft.com/azure/active-directory/reports-monitoring/concept-provisioning-logs) to determine which users have been provisioned successfully or unsuccessfully
139+
* Check the [progress bar](https://docs.microsoft.com/azure/active-directory/manage-apps/application-provisioning-when-will-provisioning-finish-specific-user) to see the status of the provisioning cycle and how close it is to completion
140+
* If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](https://docs.microsoft.com/azure/active-directory/manage-apps/application-provisioning-quarantine-status).
141+
142+
## Additional resources
143+
144+
* [Managing user account provisioning for Enterprise Apps](../manage-apps/configure-automatic-user-provisioning-portal.md)
145+
* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
146+
147+
## Next steps
148+
149+
* [Learn how to review logs and get reports on provisioning activity](../manage-apps/check-status-user-account-provisioning.md)

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1775,6 +1775,8 @@
17751775
href: signagelive-provisioning-tutorial.md
17761776
- name: Tableau Online
17771777
href: tableau-online-provisioning-tutorial.md
1778+
- name: TeamViewer
1779+
href: teamviewer-provisioning-tutorial.md
17781780
- name: ThousandEyes
17791781
href: thousandeyes-provisioning-tutorial.md
17801782
- name: Templafy

0 commit comments

Comments
 (0)