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
title: 'Tutorial: Configure Zoom 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 Zoom.
3
+
description: Learn how to automatically provision and de-provision user accounts from Azure AD to Zoom.
4
4
services: active-directory
5
5
documentationcenter: ''
6
6
author: zchia
@@ -14,70 +14,75 @@ ms.tgt_pltfrm: na
14
14
ms.devlang: na
15
15
ms.topic: article
16
16
ms.date: 06/3/2019
17
-
ms.author: "jeedes"
17
+
ms.author: Zhchia
18
18
---
19
19
20
20
# Tutorial: Configure Zoom for automatic user provisioning
21
21
22
-
The objective of this tutorial is to demonstrate the steps to be performed in Zoom and Azure Active Directory (Azure AD) to configure Azure AD to automatically provision and de-provision users and/or groups to Zoom.
22
+
This tutorial describes the steps you need to perform in both Zoom and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [Zoom](https://zoom.us/pricing/) 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).
23
23
24
-
> [!NOTE]
25
-
> 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](../app-provisioning/user-provisioning.md).
26
-
>
27
-
> 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/).
24
+
25
+
## Capabilities supported
26
+
> [!div class="checklist"]
27
+
> * Create users in Zoom
28
+
> * Remove users in Zoom when they do not require access anymore
29
+
> * Keep user attributes synchronized between Azure AD and Zoom
30
+
> *[Single sign-on](https://docs.microsoft.com/azure/active-directory/saas-apps/zoom-tutorial) to Zoom (recommended)
28
31
29
32
## Prerequisites
30
33
31
34
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
32
35
33
-
* An Azure AD tenant
34
-
*[A Zoom tenant](https://zoom.us/pricing)
35
-
* A user account in Zoom with Admin permissions
36
-
37
-
## Add Zoom from the gallery
36
+
*[An Azure AD tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant).
37
+
* 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).
38
+
*[A Zoom tenant](https://zoom.us/pricing).
39
+
* A user account in Zoom with Admin permissions.
38
40
39
-
Before configuring Zoom for automatic user provisioning with Azure AD, you need to add Zoom from the Azure AD application gallery to your list of managed SaaS applications.
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 Zoom](https://docs.microsoft.com/azure/active-directory/manage-apps/customize-application-attributes).
40
45
41
-
**To add Zoom from the Azure AD application gallery, perform the following steps:**
46
+
## Step 2. Configure Zoom to support provisioning with Azure AD
42
47
43
-
1.In the **[Azure portal](https://portal.azure.com)**, in the left navigation panel, select **Azure Active Directory**.
48
+
1.Sign in to your [Zoom Admin Console](https://zoom.us/signin). Navigate to **Advanced > Zoom for Developers** in the left navigation pane.
44
49
45
-
64
+
5. Copy and save the **JWT Token**. This value will be entered in the **Secret Token** field in the Provisioning tab of your Zoom application in the Azure portal. If you need a new non-expiring token, you will need to reconfigure the expiration time which will auto generate a new token.
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.
68
+
## Step 3. Add Zoom from the Azure AD application gallery
62
69
63
-
Before configuring and enabling automatic user provisioning, you should decide which users and/or groups in Azure AD need access to Zoom. Once decided, you can assign these users and/or groups to Zoom by following the instructions here:
70
+
Add Zoom from the Azure AD application gallery to start managing provisioning to Zoom. If you have previously setup Zoom 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).
64
71
65
-
*[Assign a user or group to an enterprise app](../manage-apps/assign-user-or-group-access-portal.md)
72
+
## Step 4. Define who will be in scope for provisioning
66
73
67
-
### Important tips for assigning users to Zoom
74
+
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).
68
75
69
-
*It is recommended that a single Azure AD user is assigned to Zoom to test the automatic user provisioning configuration. Additional users and/or groups may be assigned later.
76
+
*When assigning users and groups to Zoom, 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.
70
77
71
-
*When assigning a user to Zoom, you must select any valid application-specific role (if available) in the assignment dialog. Users with the **Default Access** role are excluded from provisioning.
78
+
*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).
72
79
73
-
## Configure automatic user provisioning to Zoom
74
80
75
-
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users or groups in Zoom based on user and/or group assignments in Azure AD.
81
+
## Step 5. Configure automatic user provisioning to Zoom
76
82
77
-
> [!TIP]
78
-
> You may also choose to enable SAML-based single sign-on for Zoom, following the instructions provided in the [Zoom single sign-on tutorial](zoom-tutorial.md). Single sign-on can be configured independently of automatic user provisioning, though these two features compliment each other.
83
+
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.
79
84
80
-
### Configure automatic user provisioning for Zoom in Azure AD
85
+
### To configure automatic user provisioning for Zoom in Azure AD:
81
86
82
87
1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
83
88
@@ -95,73 +100,60 @@ This section guides you through the steps to configure the Azure AD provisioning
5. Under the **Admin Credentials** section, enter `https://api.zoom.us/scim` in **Tenant URL**. To retrieve the **Secret Token** of your Zoom account, follow the walkthrough as described in Step 6.
99
-
100
-
6. Sign in to your [Zoom Admin Console](https://zoom.us/signin). Navigate to **Advanced > Zoom for Developers** in the left navigation pane.
Retrieve the JWT Token value shown below and input this into the **Secret Token** field in Azure AD. If you need a new non-expiring token, you will need to reconfigure the expiration time which will auto generate a new token.
103
+
5. Under the **Admin Credentials** section, enter `https://api.zoom.us/scim` in **Tenant URL**. Input the **JWT Token** value retrieved earlier in **Secret Token**. Click **Test Connection** to ensure Azure AD can connect to Zoom. If the connection fails, ensure your Zoom account has Admin permissions and try again.
7. Upon populating the fields shown in Step 5, click **Test Connection** to ensure Azure AD can connect to Zoom. If the connection fails, ensure your Zoom account has Admin permissions and try again.
8. 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**.
107
+
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.
10. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Zoom**.
113
+
8. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Zoom**.
131
114
132
-
115
+
9. Review the user attributes that are synchronized from Azure AD to Zoom in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Zoom 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 Zoom API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
133
116
134
-
11. Review the user attributes that are synchronized from Azure AD to Zoom in the **Attribute Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Zoom for update operations. Select the **Save** button to commit any changes.
135
-
136
-
12. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
126
+
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).
127
+
128
+
11. To enable the Azure AD provisioning service for Zoom, change the **Provisioning Status** to **On** in the **Settings** section.
139
129
140
-
13. To enable the Azure AD provisioning service for Zoom, change the **Provisioning Status** to **On** in the **Settings** section.
141
-
142
130
143
131
144
-
14. Define the users and/or groups that you would like to provision to Zoom by choosing the desired values in **Scope** in the **Settings** section.
132
+
12. Define the users and/or groups that you would like to provision to Zoom by choosing the desired values in **Scope** in the **Settings** section.
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 Zoom.
140
+
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.
153
141
154
-
For more information on how to read the Azure AD provisioning logs, see [Reporting on automatic user account provisioning](../app-provisioning/check-status-user-account-provisioning.md).
142
+
## Step 6. Monitor your deployment
143
+
Once you've configured provisioning, use the following resources to monitor your deployment:
155
144
156
-
## Connector limitations
145
+
1. 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
146
+
2. 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
147
+
3. 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).
157
148
158
-
* Zoom does not support provisioning for groups.
149
+
## Connector limitations
150
+
* Zoom only allows a maximum of 9,999 basic users today.
159
151
160
152
## Additional resources
161
153
162
-
*[Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)
154
+
*[Managing user account provisioning for Enterprise Apps](../manage-apps/configure-automatic-user-provisioning-portal.md)
163
155
*[What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
164
156
165
157
## Next steps
166
158
167
-
*[Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)
159
+
*[Learn how to review logs and get reports on provisioning activity](../manage-apps/check-status-user-account-provisioning.md)
Copy file name to clipboardExpand all lines: articles/app-service/configure-language-java.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,24 @@ Do not deploy your .war using FTP. The FTP tool is designed to upload startup sc
33
33
34
34
Performance reports, traffic visualizations, and health checkups are available for each app through the Azure portal. For more information, see [Azure App Service diagnostics overview](overview-diagnostics.md).
35
35
36
+
### Use Flight Recorder
37
+
38
+
All Java runtimes on App Service using the Azul JVMs come with the Zulu Flight Recorder. You can use this to record JVM, system, and Java level events to monitor the behavior and troubleshoot problems in your Java applications.
39
+
40
+
To take a timed recording you will need the PID (Process ID) of the Java application. To find the PID, open a browser to your web app's SCM site at https://<your-site-name>.scm.azurewebsites.net/ProcessExplorer/. This page shows the running processes in your web app. Find the process named "java" in the table and copy the corresponding PID (Process ID).
41
+
42
+
Next, open the **Debug Console** in the top toolbar of the SCM site and run the following command. Replace `<pid>` with the process ID you copied earlier. This command will start a 30 second profiler recording of your Java application and generate a file named `timed_recording_example.jfr` in the `D:\home` directory.
For more information, please see the [Jcmd Command Reference](https://docs.oracle.com/javacomponents/jmc-5-5/jfr-runtime-guide/comline.htm#JFRRT190).
49
+
50
+
#### Analyze `.jfr` files
51
+
52
+
Use [FTPS](deploy-ftp.md) to download your JFR file to your local machine. To analyze the JFR file, download and install [Zulu Mission Control](https://www.azul.com/products/zulu-mission-control/). For instructions on Zulu Mission Control, see the [Azul documentation](https://docs.azul.com/zmc/) and the [installation instructions](https://docs.microsoft.com/java/azure/jdk/java-jdk-flight-recorder-and-mission-control).
0 commit comments