Discover

Get Started

Developers

Industries

Integrate Microsoft Purview

Overview

You can integrate Microsoft Purview to scan files during Transfer and detect or block potential threats.

Once configured, transferred files are scanned. If a threat is detected, the configured On detection action is applied to block the Transfer or generate an alert.

The overall process consists of the following steps:

① Verify API Credentials → ② Configure the Integration in the Product

Prerequisites

Before you begin, verify the following requirements.

ItemDescription
Azure AD ApplicationPermission to register an application in Azure AD (Microsoft Entra ID) and obtain a Tenant ID, Client ID, and Client Secret is required.
API CredentialsA Tenant ID, Client ID, and Client Secret are required.
NetworkThe environment where the product is installed must allow outbound HTTPS communication (port 443) to Microsoft Entra ID and Microsoft Purview endpoints.

Verify API Credentials

To integrate with Microsoft Purview, register an application in Azure AD (Microsoft Entra ID) and obtain the required Tenant ID, Client ID, and Client Secret.

Step 1. Register an Application and Verify the IDs

In Azure AD (Microsoft Entra ID), register a new application and locate the Tenant ID and Client ID (Application ID).

Grant the application the permissions required for Microsoft Purview integration.

17_1

Step 2. Generate a Client Secret

In the registered application's Certificates & Secrets section, generate a new Client Secret and copy its value. The secret value is displayed only once when it is created.

Treat the Client Secret as a password. Anyone with access to it can authenticate to the scanning API, so do not expose it in public repositories or external documentation. If the Client Secret is compromised, revoke it and generate a new one.

17_2

Verification

✔ The Tenant ID and Client ID have been verified.

✔ The Client Secret has been generated.

Configure Microsoft Purview Integration

Enter the verified credentials and configure the detection policy.

When you open the Security configuration page, the following screen is displayed.

17_3

Step 1. Enter the Tenant ID

Enter the Tenant ID verified in the "Verify API Credentials" section into the Tenant ID field.

Step 2. Enter the Client ID

Enter the Client ID verified in the "Verify API Credentials" section into the Client ID field.

Step 3. Enter the Client Secret

Enter the Client Secret generated in the "Verify API Credentials" section into the Client Secret field.

Step 4. Select On Detection

Select how the system should respond when a threat is detected in On detection.

OptionDescription
Block transferBlock the Transfer when a threat is detected.
Alert onlyAllow the Transfer to continue and generate an alert only.
Admin confirmRequire administrator confirmation before proceeding.

Step 5. Save the Configuration

After completing the configuration, click Add to save the integration.

Verification

✔ The Tenant ID, Client ID, and Client Secret have been entered.

✔ The On detection option has been selected.

Verify the Integration

Verify that the integration is operating correctly.

Step 1. Perform a Test Transfer

Transfer a file to verify that scanning is performed. You can safely verify the scanning behavior using a standard antivirus test file such as EICAR.

17_4

Step 2. Verify the Result

Verify that the configured On detection action is applied correctly (for example, Block transfer blocks the Transfer, while Alert only generates a warning).

17_5

Verification

✔ File scanning has been performed.

✔ The configured detection action is applied correctly.

Configuration Complete

After the configuration is saved, the integration becomes active.

From this point forward, transferred files are scanned automatically. If a threat is detected, the configured action is applied.

Troubleshooting

If scanning does not operate correctly, verify the following.

IssueVerification
Integration does not workVerify that the Tenant ID, Client ID, and Client Secret are correct.
Authentication error occursVerify that the Client Secret has not expired or been revoked, and that the required application permissions have been granted.
Threats are detected but Transfers are not blockedVerify that On detection is set to Block transfer.
Integration fails in a restricted networkVerify that outbound HTTPS communication (port 443) to Microsoft Entra ID and Microsoft Purview endpoints is allowed through the firewall or proxy.