-
Notifications
You must be signed in to change notification settings - Fork 193
RADAR-7960: Add Microsoft Teams cloud data source onboarding doc #2106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,185 @@ | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| --- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| page_title: Add a data source - Microsoft Teams | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| description: >- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Add Microsoft Teams as a data source for Vault Radar to monitor Teams channels for sensitive data and secrets. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| # START AUTO GENERATED METADATA, DO NOT EDIT | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| created_at: 2026-03-26T00:00:00Z | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| last_modified: 2026-03-26T00:00:00Z | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| # END AUTO GENERATED METADATA | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| --- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| # Add a Microsoft Teams data source | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
jonathanfrappier marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Connect Microsoft Teams as a data source to HCP Vault Radar to monitor Teams | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| channels for sensitive data and secrets. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ## Prerequisites | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| - HCP IAM user with the HCP owner or admin role. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| <Tabs> | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| <Tab heading="HCP Vault Radar cloud scan"> | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Before you begin, make sure you have the following access: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| - Permission to sign in to the Microsoft 365 tenant that contains the Teams | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| data you want to scan. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| - Enable admin consent workflow in the Microsoft 365 tenant if tenant-wide consent is restricted. This | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| allows users to request admin approval to connect their Microsoft Teams data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| to HCP Vault Radar. Refer to the [Microsoft documentation for enabling admin | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| consent workflow](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-admin-consent-workflow). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| - Permission to sign in to the Microsoft 365 tenant that contains the Teams | |
| data you want to scan. | |
| - Enable admin consent workflow in the Microsoft 365 tenant if tenant-wide consent is restricted. This | |
| allows users to request admin approval to connect their Microsoft Teams data | |
| to HCP Vault Radar. Refer to the [Microsoft documentation for enabling admin | |
| consent workflow](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-admin-consent-workflow). | |
| - Access to the Microsoft 365 tenant that contains the Teams data you want to scan. | |
| - Enable [admin consent workflow](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-admin-consent-workflow) in the Microsoft 365 tenant if tenant-wide consent is restricted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well you don't need to be an admin to onboard MS Teams on Vault Radar.
But admin consent workflow need to be enabled on the tenant side by the user - this might require the user to contact his admin and get it setup.
Link contain steps involved to make it happen.
Outdated
Copilot
AI
Mar 31, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Heading structure is inconsistent with other Vault Radar “Add a ” pages that use tabs (for example, add-data-sources/slack.mdx:30 has the “## Add …” section outside the <Tabs> block). Placing “## Add a Microsoft Teams data source” inside only the cloud-scan tab can create an odd TOC and uneven sectioning between tabs; consider moving the shared “Add …” section heading above <Tabs> and keeping tab content under consistent subheadings.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree w copilot here - move this up above tabs
jonathanfrappier marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
jonathanfrappier marked this conversation as resolved.
Show resolved
Hide resolved
Outdated
Copilot
AI
Mar 31, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The OIDC scope is spelled openid (all lowercase). Using openId may cause confusion when readers configure permissions/scopes in Entra / Microsoft Graph.
| - `openId` to sign users in. | |
| - `openid` to sign users in. |
Outdated
Copilot
AI
Mar 31, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Grammar: “view users basic profile” is missing an apostrophe/article. Consider changing this to “view the user's basic profile” (or equivalent) to keep the permission descriptions clear.
| - `profile` to view users basic profile. | |
| - `profile` to view the user's basic profile. |
Outdated
Copilot
AI
Mar 31, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section states that Vault Radar requires “Microsoft Graph application permissions”, but the list later includes openid, profile, and offline_access, which are delegated OIDC scopes rather than Graph application permissions. Update the wording to match the permission type actually required (delegated vs application), or split the lists so readers grant the right permission types in Entra.
| ### Configure Microsoft Graph permissions | |
| Grant the application the Microsoft Graph application permissions required to | |
| read the Teams content that Vault Radar scans. | |
| For a guide to adding API permissions to an app, see [Quickstart: Configure app access to web APIs](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-configure-app-access-web-apis). | |
| - `Team.ReadBasic.All` to list teams. | |
| - `Channel.ReadBasic.All` to list channels. | |
| - `ChannelMessage.Read.All` to read channel messages. | |
| - `Organization.Read.All` to read organization information, such as the tenant name. | |
| - `openId` to sign users in. | |
| - `profile` to view users basic profile. | |
| - `offline_access` to allow the application to maintain access to the Microsoft Graph API when the user is not signed in. | |
| ### Configure Microsoft Graph and delegated permissions | |
| Grant the application the following permissions in Microsoft Entra ID so Vault Radar can | |
| read the Teams content it scans and sign users in. | |
| For a guide to adding API permissions to an app, see [Quickstart: Configure app access to web APIs](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-configure-app-access-web-apis). | |
| - **Microsoft Graph application permissions:** | |
| - `Team.ReadBasic.All` to list teams. | |
| - `Channel.ReadBasic.All` to list channels. | |
| - `ChannelMessage.Read.All` to read channel messages. | |
| - `Organization.Read.All` to read organization information, such as the tenant name. | |
| - **Delegated permissions (scopes):** | |
| - `openid` to sign users in. | |
| - `profile` to view users' basic profile. | |
| - `offline_access` to allow the application to maintain access to the Microsoft Graph API when the user is not signed in. |
Uh oh!
There was an error while loading. Please reload this page.