Merge pull request #243764 from batamig/patch-357

prmerger-automator[bot] · web-flow · commit e3fef10c69d9 · 2023-07-31T10:41:35.000Z
d4iot capture filter limitations
diff --git a/articles/defender-for-iot/organizations/cli-ot-sensor.md b/articles/defender-for-iot/organizations/cli-ot-sensor.md
@@ -617,8 +617,9 @@ The basic use case for capture filters uses the same filter for all Defender for
 - `traffic-monitor`: Captures communication statistics
 
 > [!NOTE]
-> Capture filters don't apply to [Defender for IoT malware alerts](../alert-engine-messages.md#malware-engine-alerts), which are triggered on all detected network traffic.
+> - Capture filters don't apply to [Defender for IoT malware alerts](../alert-engine-messages.md#malware-engine-alerts), which are triggered on all detected network traffic.
 >
+> - The capture filter command has a character length limit that's based on the complexity of the capture filter definition and the available network interface card capabilities. If your requested filter commmand fails, try grouping subnets into larger scopes and using a shorter capture filter command.
 
 ### Create a basic filter for all components
 

Original file line number	Diff line number	Diff line change
`@@ -617,8 +617,9 @@ The basic use case for capture filters uses the same filter for all Defender for`
`617`	`617`	- `traffic-monitor`: Captures communication statistics
`618`	`618`
`619`	`619`	`> [!NOTE]`
`620`		`-> Capture filters don't apply to [Defender for IoT malware alerts](../alert-engine-messages.md#malware-engine-alerts), which are triggered on all detected network traffic.`
	`620`	`+> - Capture filters don't apply to [Defender for IoT malware alerts](../alert-engine-messages.md#malware-engine-alerts), which are triggered on all detected network traffic.`
`621`	`621`	`>`
	`622`	`+> - The capture filter command has a character length limit that's based on the complexity of the capture filter definition and the available network interface card capabilities. If your requested filter commmand fails, try grouping subnets into larger scopes and using a shorter capture filter command.`
`622`	`623`
`623`	`624`	`### Create a basic filter for all components`
`624`	`625`