Skip to content

Commit 75256dc

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

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

defender-office-365/apivendorecosystem.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -51,12 +51,12 @@ Integration features are available to customers with Microsoft Defender for Offi
5151

5252
1. **Select a Partner**
5353

54-
1. Choose from approved API vendors listed above.
55-
54+
1. Choose from approved API vendors.
55+
5656
1. **Enable Integration**
5757

58-
1. Upon onboarding to the strategic integration partner, their solution is seamlessly and automatically incorporated into your security architecture.
59-
58+
1. Once you onboard to the strategic integration partner, their solution is seamlessly and automatically incorporated into your security architecture.
59+
6060
1. **Monitor and Manage**
6161

6262
1. Use the unified dashboards and quarantine to monitor threat activity and take action.
@@ -82,7 +82,7 @@ Additionally, administrators are encouraged to use the [Configuration Analyzer]
8282

8383
To maintain consistent message handling and threat response across the ecosystem, it is critical to align policy configurations between MDO and the integrated third-party solution. This alignment ensures that messages flagged by either system exhibit predictable behavior and are surfaced appropriately in unified dashboards and quarantine views.
8484

85-
Once policy alignment is established, the remainder of the integration lifecycle - including monitoring, reporting, and response - can be managed directly within the Microsoft 365 Securityportal.
85+
Once policy alignment is established, the remainder of the integration lifecycle - including monitoring, reporting, and response - can be managed directly within the Microsoft 365 Security portal.
8686

8787
## Portal Experiences
8888

@@ -165,7 +165,7 @@ The "highest" verdict takes precedence. The precedence should be as follows (hig
165165

166166
**What if I utilize a different third-party application?**
167167

168-
Currently, this integration only works for authorized partners which are Darktrace and KnowBe4. If you utilize a different ICES/CAPES vendor, you won't be able to take advantage of this integration.
168+
Currently, this integration only works for authorized partners which are Darktrace and KnowBe4. If you utilize a different ICES/CAPES vendor, you cannot take advantage of this integration.
169169

170170
**Will I be charged for the third-party verdict data and actioning by MDO policies?**
171171

0 commit comments

Comments
 (0)