Skip to content

Commit f28bfbd

Browse files
authored
Update connect-defender-for-cloud.md
Fixing a typo
1 parent 57c46d7 commit f28bfbd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ 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-
> [!NNOTE]
21+
> [!NOTE]
2222
> The connector does not support syncing alerts from subscriptions owned by other tenants even when Lighthouse is enabled for those tenants.
2323
2424
## Alert synchronization

0 commit comments

Comments
 (0)