Under which situation is SecureConnect NOT supported?

SecureConnect is a feature that enables secure connectivity between workloads, ensuring that communication adheres to set policies. In the context of workload communication, understanding when SecureConnect is not supported is crucial for effective policy management.

In situations where workloads are actively communicating, SecureConnect operates by establishing secure connections based on the defined security policies. Therefore, this is a scenario where SecureConnect is fully supported as it facilitates ongoing communication securely.

Conversely, when workloads are idle, there is no active communication occurring, leading to a state where SecureConnect isn't required or utilized. This idleness means that while the workloads are not engaged in data transmission, SecureConnect's functionality becomes irrelevant, as there are no transactions that need securing.

When workloads are in conflict mode or using full enforcement, SecureConnect is supported because these scenarios involve active policy enforcement and conflict resolution, which requires secure connectivity to ensure that the correct policies are applied and adhered to for communications between workloads.

Understanding these contexts clarifies why SecureConnect is not supported when workloads are idle, highlighting the feature's reliance on active communication to fulfill its intended purpose.