Skip to content

Commit 0090caa

Browse files
authored
Merge branch 'main' into gcc
2 parents 28238e4 + 7915f50 commit 0090caa

File tree

3 files changed

+8
-8
lines changed

3 files changed

+8
-8
lines changed

CloudAppSecurityDocs/cas-compliance-trust.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,9 @@ Microsoft Defender for Cloud Apps collects information from your configured clou
2121
- System settings and policies
2222
- User and group configurations
2323

24+
> [!NOTE]
25+
> The data collected from the various applications is dependent on the customer-provided data from the various applications and may include personal information.
26+
2427
## Data storage location
2528

2629
Defender for Cloud Apps operates in the Microsoft Azure data centers in the following geographical regions:

CloudAppSecurityDocs/mde-govern.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,8 @@ To block an app, do the following steps:
120120
> - Any organizational scoping that was set manually on indicators that were created by Defender for Cloud Apps before the release of this feature will be overridden by Defender for Cloud Apps. The required scoping should be set from the Defender for Cloud Apps experience using the scoped profiles experience.
121121
> - To remove a selected scoping profile from an unsanctioned app, remove the unsanctioned tag and then tag the app again with the required scoped profile.
122122
> - It can take up to two hours for app domains to propagate and be updated in the endpoint devices once they're marked with the relevant tag or/and scoping.
123-
> - When an app is tagged as *Monitored*, the option to apply a scoped profile shows only if the built-in *Win10 Endpoint Users* data source has consistently recieved data during the past 30 days.
123+
> - When an app is tagged as *Monitored*, the option to apply a scoped profile shows only if the built-in *Win10 Endpoint Users* data source has consistently received data during the past 30 days.
124+
> - Device groups in Microsoft Defender for Business(MDB) are managed differently. Due to this- No device groups will appear in MDA device groups for customers with MDB license.
124125
125126
## Educate users when accessing risky apps
126127

CloudAppSecurityDocs/protect-github.md

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Protect your GitHub Enterprise environment | Microsoft Defender for Cloud Apps
33
description: Learn how about connecting your GitHub Enterprise app to Defender for Cloud Apps using the API connector.
4-
ms.date: 12/05/2023
4+
ms.date: 04/27/2025
55
ms.topic: how-to
66
---
77
# How Defender for Cloud Apps helps protect your GitHub Enterprise environment
@@ -85,10 +85,6 @@ These steps can be completed independently of the [Configure GitHub Enterprise C
8585

8686
1. **Create an OAuth App for Defender for Cloud Apps to connect your GitHub organization.** Repeat this step for each additional connected organization.
8787

88-
> [!NOTE]
89-
> If you have [preview features](/microsoft-365/security/defender/preview) and [app governance turned on](app-governance-get-started.md), use the **App governance** page instead of the **OAuth apps** page to perform this procedure.
90-
>
91-
9288
1. Browse to **Settings** > **Developer settings**, select **OAuth Apps**, and then select **Register an application**. Alternatively, if you have existing OAuth apps, select **New OAuth App**.
9389

9490
![Screenshot showing creating an oauth app.](media/connect-github-create-oauth-app.png)
@@ -129,8 +125,8 @@ These steps can be completed independently of the [Configure GitHub Enterprise C
129125

130126
1. Select the **GitHub Profile picture** -> **your enterprises**.
131127
1. Select **your enterprise account** and choose the account you want to connect to Microsoft Defender for Cloud Apps.
132-
1. Confirm that the URL is the enterprise slug. For instance, in this example `https://github.com/enterprises/testEnterprise` *testEnterprise* is the enterprise slug. Enter only the enterprise slug, not the entire URL.
133-
128+
1. Confirm that the URL contains the enterprise slug. For instance, `https://github.com/enterprises/testEnterprise`
129+
2. Enter only the enterprise slug, not the entire URL. In this example, *testEnterprise* is the enterprise slug.
134130
1. Select **Next**.
135131

136132
1. Select **Connect GitHub**.

0 commit comments

Comments
 (0)