Skip to content

Commit 402ad10

Browse files
Merge pull request #291063 from kochavis/patch-13
Update connect-defender-for-cloud.md
2 parents 2f06060 + b373ae0 commit 402ad10

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/sentinel/connect-defender-for-cloud.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,8 @@ ms.author: yelevin
1818
[Microsoft Defender for Cloud Defender plans](/azure/defender-for-cloud/defender-for-cloud-introduction#protect-cloud-workloads) are enabled per subscription. While Microsoft Sentinel's legacy connector for Defender for Cloud Apps is also configured per subscription, the **Tenant-based Microsoft Defender for Cloud** connector, in preview, allows you to collect Defender for Cloud alerts over your entire tenant without having to enable each subscription separately. The tenant-based connector also works with [Defender for Cloud's integration with Microsoft Defender XDR](ingest-defender-for-cloud-incidents.md) to ensure that all of your Defender for Cloud alerts are fully included in any incidents you receive through [Microsoft Defender XDR incident integration](microsoft-365-defender-sentinel-integration.md).
1919

2020
[!INCLUDE [reference-to-feature-availability](includes/reference-to-feature-availability.md)]
21+
> [!NOTE]
22+
> The connector does not support syncing alerts from subscriptions owned by other tenants, even when Lighthouse is enabled for those tenants.
2123
2224
## Alert synchronization
2325

0 commit comments

Comments
 (0)