Skip to content

Commit 5d11f63

Browse files
Merge pull request #230594 from memildin/patch-66
Fixed wording re MDCA<->MDC integration
2 parents 987283b + 4138286 commit 5d11f63

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/defender-for-cloud/other-threat-protections.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ For a list of the Azure network layer alerts, see the [Reference table of alerts
3030

3131
Microsoft Defender for Cloud Apps (formerly known as Microsoft Cloud App Security) is a cloud access security broker (CASB) that supports various deployment modes including log collection, API connectors, and reverse proxy. It provides rich visibility, control over data travel, and sophisticated analytics to identify and combat cyberthreats across all your Microsoft and third-party cloud services.
3232

33-
Once Microsoft Defender for Cloud Apps has been enabled, you can then select the integration from within Defender for Cloud's settings. Your hardened recommendations from Defender for Cloud will appear in Defender for Cloud Apps with no other configuration needed.
33+
Once Microsoft Defender for Cloud Apps has been enabled, you can then select the integration from within Defender for Cloud's settings. Your security recommendations from Defender for Cloud will appear in Defender for Cloud Apps with no other configuration needed.
3434

3535
> [!NOTE]
3636
> Defender for Cloud stores security-related customer data in the same geo as its resource. If Microsoft hasn't yet deployed Defender for Cloud in the resource's geo, then it stores the data in the United States. When Microsoft Defender for Cloud Apps is enabled, this information is stored in accordance with the geo location rules of Microsoft Defender for Cloud Apps. For more information, see [Data storage for non-regional services](https://azuredatacentermap.azurewebsites.net/).

0 commit comments

Comments
 (0)