Introduction

iManage Work for Outlook integrates at the tenant level and must be registered as a Microsoft Entra ID (formerly Azure AD) app so admins can grant the necessary Microsoft Graph and Exchange Online application permissions, centrally scope mailbox access through RBAC and a mail-enabled security group, and supply the Entra artifacts (tenant ID, client ID, client secret, validation mailbox) used by iManage Control Center. This ensures least-privilege access, centralized governance, and compliance.

Prerequisites

The following are required to be in place to configure iManage Work for Outlook in Azure:

For the PowerShell Setup Script method:

PowerShell—Verify version and update

If you don’t know which version of Microsoft PowerShell you have installed:

  1. Open PowerShell.

  2. At the prompt, type $PSVersionTable and press Enter.

  3. In the output, look for the PSVersion value, which is the version installed on your system.

  4. If your value isn't 7.0 or later, and you need to upgrade your PowerShell version, refer to the following for the complete information: https://learn.microsoft.com/en-us/powershell/scripting/install/install-powershell?view=powershell-7.6.

Two setup approaches

There are two options for configuring the iManage Work for Outlook app in Azure:

  • Approach 1 (the manual path): Manually, using the Azure administrator, Microsoft 365 admin center, Microsoft PowerShell, and then the Exchange admin center.

  • Approach 2 (the setup script): Using a PowerShell setup script from iManage, which walks you through most of the steps to fully set up the iManage Work for Outlook app.

Which approach should you use?

Approach 1: Choose the manual path when one or all of the following conditions apply:

  • Your organization restricts third‑party scripts

  • Your tenant/RBAC model is non‑standard

  • PowerShell access or skills are limited

  • Duties are split across teams (Azure, Exchange, security) who each perform their own portal steps

Refer to Manual setup process for iManage Work for Outlook for steps to set up using the manual approach.

Approach 2: Choose the setup script path when one or more of the following conditions apply:

  • You want to save time, standardize configuration, and reduce manual errors—especially for repeatable, multi‑tenant deployments

  • You have the required permissions to run approved scripts and your environment matches the script’s assumptions: RBAC model, groups, and app registration patterns

Refer to the PowerShell Script setup process for iManage Work for Outlook for steps to set up using the iManage setup script.

Additional resources

Configuring iManage Work for Outlook in Microsoft Azure requires an understanding of Azure, Microsoft 365, PowerShell, and Exchange admin center. For more detailed information about these Microsoft products, consult the following sources: