Microsoft Exchange 365 (Service Accounts)

Microsoft Exchange 365 (Service Accounts)

Overview

The DryvIQ Microsoft Exchange 365 enables you to make a connection using a service account with the necessary privileges to manage Office 365 configurations. The first step is to create the connection by providing the information required for DryvIQ to connect to the Exchange server. This connection is a primarily read-only connection that can scan a Microsoft Exchange account for data discovery. This connection cannot be used as part of a migration because it only provides delete functionality and not write access. DryvIQ will scan the email subject, body, and attachments, extracting metadata from the messages to use for reporting.

Creating a Connection

  1. Expand the Manage section in the left navigation menu.

  2. Click Connections.

  3. Click Add connection.

  4. Select Microsoft Exchange 365 as the platform on the Add connection modal.

  5. Enter the connection information. Reference the table below for details about each field.  

  6. Click Test connection.

  7. You will see a green "Connected” message at the bottom of the modal when DryvIQ establishes a connection. (If the connection fails, verify the information you entered.)

  8. Click Done to finish creating the connection. 

 

Add Connection Modal for Microsoft Exchange 365 (Service Accounts)

Microsoft Exchange 365 Service Accounts.png

Field

Description

Required

Field

Description

Required

Display as

Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists. If you do not add a display name, the connection will automatically be named “Microsoft Exchange 365.”

Optional

Client ID

Enter the client ID that needs to be used to access the Exchange server. You can find the client ID in the Azure Active Directory admin center. Refer to Registering DryvIQ as a Custom Application for Microsoft Exchange 365.

Required

Client Secret

Enter the client secret required to access the Exchange server. You can find the client ID in the Azure Active Directory admin center. Refer to Registering DryvIQ as a Custom Application for Microsoft Exchange 365.

Required

Tenant ID

Enter your Microsoft 365 tenant ID. You can find the tenant ID in the Azure Active Directory admin center. Refer to Registering DryvIQ as a Custom Application for Microsoft Exchange 365.

Required

Token endpoint

This setting is rare for most Microsoft connections and can be left blank. If needed, your administrator will provide this value.

Optional

Graph API endpoint

This setting is rare for most Microsoft connections and can be left blank. If needed, your administrator will provide this value.

Optional

Behavior When Deleting Items

Select the type of deletion DryvIQ should perform when deleting items: Permanent or Soft.  

Soft delete is the default behavior. A soft delete marks items as deleted. You can still access them to restore or permanently delete the items. 

Permanent delete is the recommended behavior. A permanent delete removes the items. This deletion is not reversible.

Optional

Features and Limitations 

  • The connection has primarily read-only access.

  • The connection can be used for content scans.

  • The connection does not have write privilege.

  • Only delete actions can be taken against content at this time.

  • This connection cannot be used for migrations.

  • The connector does not support native change detection.

Understanding “Shared to” Reporting

DryvIQ uses the following metadata fields to identify sharing for email messages:

  • BCC Recipients

  • CC Recipients

  • Reply to

  • Recipients.

Understanding Author Reporting

DryvIQ considers the sender (From) to be the author of the email message.

Metadata Options

When creating a Govern policy, you can use the custom metadata entity type to scan the following metadata fields for an email message.

Metadata Name

Type

Description

Metadata Name

Type

Description

1

bccRecipients

String

The Bcc: recipients for the message

These recipients are considered “shared to.”

2

categories

String

The categories associated with the message

3

ccRecipients

String

The Cc: recipients for the message

These recipients are considered “shared to.”

4

conversationId

String

The ID of the conversation the email belongs to

5

from

String

The owner of the mailbox from which the message is sent

In most cases, this value is the same as the sender property, except for sharing or delegation scenarios. DryvIQ considers the sender (From) to be the author of the email message.

6

hasAttachments

Boolean

Indicates whether the message has attachments

The possible values are true or false.

7

importance

String

The importance of the message

The possible values are: low, normal, and high.

8

inferenceClassification

String

The classification of the message for the user, based on inferred relevance or importance or based on an explicit override

The possible values are: focused or other.

9

internetMessageId

String

The message ID in the format specified by RFC2822

10

isDraft

Boolean

Indicates whether the message is a draft

A message is a draft if it hasn't been sent yet.

11

isRead

Boolean

Indicates whether the message has been read

12

replyTo

String

The email addresses to use when replying

These recipients are considered “shared to.”

13

sender

String

The account that is actually used to generate the message

In most cases, this value is the same as the from property. However, this value can be different when sending a message from a shared mailbox, for a shared calendar, or as a delegate. The value must correspond to the actual mailbox used. DryvIQ considers the sender (From) to be the author of the email message.

14

receivedDateTime

DateTimeOffset

The date and time the message was received

The date and time information uses ISO 8601 format and is always in UTC time. For example, midnight UTC on January 2, 2014, is 2014-01-02T00:00:00Z.

15

sentDateTime

DateTimeOffset

The date and time the message was sent. The date and time information uses ISO 8601 format and is always in UTC time. For example, midnight UTC on January 2, 2014, is 2014-01-02T00:00:00Z.

DryvIQ Platform Version: 5.9.19
Release Date: June 4, 2026