Microsoft 365 Connector Prerequisites: Register an App in Microsoft Entra ID

Modified on Tue, 5 May at 4:47 PM


This article explains the Microsoft Entra ID setup that must be completed before enabling the Microsoft 365 connector in Omniscope. You will register an application, create a client secret, and grant the required Microsoft Graph permissions so that the connector can be configured with the correct Tenant ID, Client ID, and Client Secret and be authorized to read mail, and if required, send mail.


1) Register an app
  1. Go to Microsoft Entra admin center (Entra ID)
  2. Applications App registrationsNew registration
  3. Name: e.g. Omniscope Email Connector (App-Only)
  4. Supported account types: typically Accounts in this organizational directory only
  5. Click Register



2) Create a client secret
  1. In the app: Certificates & secrets
  2. Client secretsNew client secret
  3. Choose an expiry that aligns with your ops policy (longer = fewer outages)
  4. Click Add
  5. Copy the Value immediately


:warning: Important: you must copy the Value.
You cannot retrieve it later.
Do not confuse it with the “Secret ID”.

That Value is clientSecret.


3) Add Microsoft Graph permissions (application permissions)
  1. App → API permissionsAdd a permission
  2. Choose Microsoft Graph
  3. Choose Application permissions
  4. Add the required Microsoft Graph application permissions:
    Mail.Read - required for reading emails using the Microsoft 365 connector.
    Mail.Send - required if you want Omniscope to send emails using Microsoft 365



Then:
  1. Click Grant admin consent (required)
Without admin consent, Graph calls will fail with 403.



4) (Recommended) Restrict mailbox access

Microsoft Graph application permissions such as `Mail.Read` and `Mail.Send` can be broad by default. To enforce least privilege, restrict which mailboxes the application can access in Exchange Online.


Microsoft currently recommends using **Application RBAC for Exchange** for this: https://learn.microsoft.com/exchange/permissions-exo/application-rbac


Application Access Policies are the older mechanism and may still be available in some tenants: https://learn.microsoft.com/exchange/permissions-exo/application-access-policies


The exact configuration depends on your organisation's Microsoft 365 environment and security policies. This configuration is performed in Microsoft 365 / Exchange Online, not in Omniscope.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article