Skip to content

Commit 8811a6c

Browse files
committed
Learn Editor: Update apivendorecosystem.md
1 parent f71450c commit 8811a6c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

defender-office-365/apivendorecosystem.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,7 @@ The following dashboards display this information:
141141

142142
**I have multiple ICES/CAPES solutions. How does that work?**
143143

144-
You can use this integration with multiple ICES/CAPES vendors as long as they're part of the API Vendor Ecosystem partnership. The integration will work the same, where each third-party is able to provide verdicts on the messages in your mailboxes. You can see the third-party catch and be able to identify which third-party the catch is attributed to, within the security portal experiences. If multiple third parties send verdicts on the same message, both third-party verdicts and explainability will be logged. The highest verdict between the third-party verdicts determines what action is taken on the message.
144+
You can use this integration with multiple ICES/CAPES vendors as long as they're part of the API Vendor Ecosystem partnership. The integration works the same, where each third-party is able to provide verdicts on the messages in your mailboxes. You can see the third-party catch and be able to identify which third-party the catch is attributed to, within the security portal experiences. If multiple third parties send verdicts on the same message, both third-party verdicts and explainability are logged. The highest verdict between the third-party verdicts determines what action is taken on the message.
145145

146146
**Which verdict takes precedence?**
147147

0 commit comments

Comments
 (0)