Skip to content

Commit c36f9df

Browse files
Pencil edit
1 parent 13e95d6 commit c36f9df

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

CloudAppSecurityDocs/protect-zoom.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ To see security posture recommendations for Zoom in Microsoft Secure Score, crea
2020
For example, recommendations for Zoom include:
2121

2222
- *Enable multi-factor authentication (MFA)*
23-
- *Enable session timeout for web users
23+
- Enable session timeout for web users
2424
- *Enforce end to end encryption in all Zoom meetings*
2525

2626
If a connector already exists and you don't see Zoom recommendations yet, refresh the connection by disconnecting the API connector, and then reconnecting it with the `“account:read:admin`, `chat_channel:read:admin` and `user:read:admin”` permissions.
@@ -40,7 +40,8 @@ Before connecting Zoom to Defender for Cloud Apps, make sure that you have the f
4040
The admin account is used only for initial consent while connecting Zoom to Defender for Cloud Apps. Defender for Cloud Apps uses an OAuth app for daily transactions.
4141

4242
>[!NOTE]
43-
> The authentication mechanism utilized in the Zoom connector doesn't support two separate connectors utilizing the same user credentials.
43+
> The authentication mechanism utilized in the Zoom connector doesn't support two separate connectors utilizing the same user credentials.<br>
44+
>
4445
> When a new instance with an existing authentication token is used, this revokes the old connector token and will cause a "Bad credentials" error.
4546
4647
## How to connect Zoom to Defender for Cloud Apps

0 commit comments

Comments
 (0)