Skip to main content

Overview

Ocean protects your Microsoft 365 environment with a cloud-native email security platform offered as a software-as-a-service solution. During the Proof of Concept (PoC), Ocean analyzes and reports on threats without taking active remediation actions, allowing your organization to evaluate our capabilities while retaining full operational control.
A Microsoft 365 Global Admin account is required to complete this integration. Once the integration is complete, the service does not need continuous access to the Global Admin account.
You won’t have to supply your admin credentials at any point.

Deployment Overview

Ocean’s email security platform integrates with Microsoft 365 via native APIs. This means that our system does not alter the email route, nor does it require any configuration changes to your existing email infrastructure. During the initial Proof of Concept (PoC) phase, Ocean will operate with read-only permissions:
  • No emails are quarantined or remediated
  • Detailed reports on potentially malicious emails are provided
  • You can review and manage threats without immediate intervention from our system
Active protection mode can be enabled after a successful PoC.

Integration Steps

Before starting the integration, Ocean’s sales team will provide you with a link to the integration wizard.
If you encounter any issues, contact your Ocean account executive for support.
1

Open the Link

Use the link provided by Ocean’s sales team to access the integration wizard.
2

Confirm Admin Permissions

Make sure you have Admin permissions, then click “Yes, I’m an admin” to start the integration.
Welcome to Ocean integration
3

Select Email Provider

Choose Microsoft M365 to proceed with the integration.
Select email provider
4

Review Permissions

Review the read-only API permissions Ocean requires. See the Permissions Reference section below for detailed information about each permission.Click “Grant Permissions” to proceed. You will be directed to the Microsoft 365 login page.
Review permissions
5

Authorize in Microsoft 365

  1. Log in to Microsoft 365 with a Global Admin account
  2. Review the requested permissions for Ocean’s application
  3. Click “Accept” to grant the permissions
Microsoft permissions consent
You will be redirected back to the Ocean Integration Wizard.
6

Integration Complete

Your integration is complete and the learning phase has started.

Permissions Reference

Ocean requires the following read-only Microsoft 365 permissions during the Proof of Concept (PoC). These permissions allow our AI to build context, understand communication patterns, and accurately identify potential threats.
All permissions are read-only. Ocean cannot modify, delete, or send emails during the PoC phase.

Mailbox Access

Scopes: Mail.ReadBasic, Mail.ReadBasic.All, Mail.ReadWhat it does: Gets the messages in the signed-in user’s mailbox (including the Deleted Items and Clutter folders). Retrieves the properties and relationships of message objects.Why it’s needed: Emails are read in real time as they arrive in the mailbox and scored along a variety of dimensions. Ocean looks at patterns of communication, urgent requests, emails requesting financial invoices, intellectual property, and sensitive customer data to identify threats.
Scope: Contacts.ReadWhat it does: Enables the app to read all contacts in all mailboxes without a signed-in user.Why it’s needed: Understanding established relationships and currently vetted contacts helps Ocean bootstrap its understanding of normal communication patterns and detect impersonation attempts.
Scope: MailboxSettings.ReadWhat it does: Enables the app to read the user’s mailbox settings without a signed-in user. Does not include permission to send mail.Why it’s needed: Fraudsters usually change settings and mail filters once they have access to an account. Ocean observes and monitors suspicious patterns of behavior to alert your security team about suspicious activity.

Directory & User Access

Scope: User.Read.AllWhat it does: Enables the app to read the full set of profile properties, reports, and managers of other users in your organization on behalf of the signed-in user.Why it’s needed: This data enables Ocean to make more accurate risk judgments while scoring emails. Learning about the organization and teams enables Ocean to model normal communication patterns. For example, emails from the Finance team may be used to train models about vendors.
Scopes: Group.Read.All, GroupMember.Read.AllWhat it does: Enables the app to list all the groups available in an organization.Why it’s needed: Group properties enable Ocean to infer relationships of people within your organization and normal working patterns between teams. For example, Ocean would infer that Finance team members are responsible for invoices and establish communication norms accordingly.

Security & Audit

Scope: AuditLog.Read.AllWhat it does: Enables the app to read and query your audit log activities without a signed-in user.Why it’s needed: Collects sign-in information about users to detect anomalies in sign-in activity that could indicate account compromise.
Scope: ActivityFeed.ReadWhat it does: Enables the application to read activity data for your organization.Why it’s needed: Provides an alternate source of sign-in data and includes SharePoint activity data for comprehensive threat analysis.
Scope: IdentityRiskEvent.Read.AllWhat it does: Enables the app to read the identity risk event information for your organization without a signed-in user.Why it’s needed: Allows Ocean to query risk events as detected by Microsoft and correlate them with email threats.
Scope: IdentityRiskyUser.Read.AllWhat it does: Enables the app to read the identity risky user information for your organization without a signed-in user.Why it’s needed: Allows Ocean to query risky user activity as detected by Microsoft for enhanced threat detection.
Scope: Policy.Read.AllWhat it does: Enables the app to read conditional access policies created by an organization.Why it’s needed: Enables Ocean to enrich context in its Knowledge Engines and support use cases across product surface areas.

API Permissions Summary

Below is the complete list of Microsoft Graph API permissions required for the integration:
User.Read.All
Mail.ReadBasic
Mail.ReadBasic.All
Mail.Read
Contacts.Read
AuditLog.Read.All
ActivityFeed.Read
IdentityRiskEvent.Read.All
IdentityRiskyUser.Read.All
Policy.Read.All
MailboxSettings.Read
Group.Read.All
GroupMember.Read.All

Frequently Asked Questions

No configurations are required. The only necessary step is to provide your organization’s Tenant ID and authorize the Ocean application as this guide outlines.
No, unlike email gateways, Ocean does not route, or intercept emails between the internet and Microsoft 365. Our system operates without adding any delay to email delivery.
No, the delivery of Microsoft 365 emails will remain unaffected even if Ocean services are temporarily unavailable.
The initial POC of Ocean operates in passive, read-only mode without interfering with existing email systems. While Ocean’s core platform is designed to auto-remediate threats, these capabilities remain disabled during the POC phase and require write permissions to enable.
No, the initial Proof of Concept (PoC) of Ocean operates without interfering with other email security systems. It operates in passive analysis mode to detect emails that pass through existing protection layers.
You can revoke access at any time through the Google Workspace Admin Console by removing the domain-wide delegation entry for Ocean’s Client ID.
No, Ocean automatically adapts to your email environment and behavior, beginning threat detection without additional setup.
No, our AI continuously learns and adapts to your organization’s needs, providing highly accurate protection for your employees’ inboxes. It operates autonomously, ensuring security while offering detailed and clear insights, without requiring ongoing maintenance or support from your IT team.

Need Help?

If you encounter any issues during the integration process, contact your Ocean account executive for support.