Skip to main content
Meet us at G7, X2 Conference in Antalya & GLA in Shenzhen

Setup

nemox: Setup & System Requirements

Setting up nemox consists of two steps: the add-in, which your team uses to work with nemox directly in the mailbox, and mailbox access, through which nemox processes incoming emails in the background. This page walks through both steps and lists the system requirements.

Part 1

Install the add-in

The nemox add-in is an Outlook web add-in: it is not installed as a program on the PC but assigned to the user (their mailbox account), either centrally by the administrator or by the user themselves. The prerequisite is a mailbox on Exchange Online or self-hosted Exchange 2016 or newer (details: system requirements). Once installed, it is automatically available in all of the user’s Outlook clients (Windows, Mac, Outlook on the web, new Outlook); Outlook Mobile (iOS/Android) is currently not supported.

Manifest (XML), for Option A and B

https://app.nemox.ai/api/outlook/manifest.xml

Manifest (JSON, app package)

https://app.nemox.ai/api/outlook/manifest.json

Option A: Centralized rollout by the Microsoft 365 administrator

Recommended
  1. 01
    Sign in to the Microsoft 365 Admin Center (admin.microsoft.com). Requires Exchange administrator or global administrator rights.
  2. 02
    Settings → Integrated Apps → "Upload custom apps".
  3. 03
    Choose the app type "Office Add-in".
  4. 04
    Select "Provide link to manifest file" and enter https://app.nemox.ai/api/outlook/manifest.xml. Alternatively, download the XML manifest and upload it as a file.
  5. 05
    Specify the users or groups the add-in should be deployed to (entire organization or specific users/groups, for example the sales team) and complete the deployment.
  6. 06
    Deployment can take up to 24 hours; after that, "Nemo" appears for the assigned users in the ribbon or under "Apps" as soon as an email is opened or composed.

Centralized rollout also works when self-installation has been disabled by policy.

Option B: Self-installation by the user

  1. 01
    Download the XML manifest file (download button above).
  2. 02
    Open https://aka.ms/olksideload in the browser; the "Add-Ins for Outlook" dialog opens. (In classic Outlook for Windows alternatively: File → Info → Manage Add-ins, which opens the same dialog in the browser.)
  3. 03
    "My Add-ins" → section "Custom Add-ins" → "Add a custom add-in" → "Add from file" → select the downloaded XML file and confirm.
    The "Add-Ins for Outlook" dialog with "My add-ins" selected, showing the "Custom Addins" section and the "Add a custom add-in" link
  4. 04
    In Outlook on the web and the new Outlook, the add-in is available immediately; in classic desktop Outlook it can take up to 24 hours (cache).

The installation applies to the signed-in user and syncs automatically to all of their Outlook clients. The administrator may have disabled self-installation by policy; in that case, use Option A.

First sign-in

Open an email → click "Nemo" in the ribbon → the task pane opens at the side and guides you through signing in with your nemox credentials.

Part 2

Set up mailbox access

To process incoming emails, nemox needs access to the relevant mailboxes. This access works in the background and is independent of the add-in.

Microsoft 365 / Exchange Online

Standard

These steps are performed by your Microsoft 365 administrator.

  1. 01
    Open the Microsoft Entra admin center at https://entra.microsoft.com and sign in as administrator.
  2. 02
    Select "App registrations" in the left sidebar, then click "New registration".
    Entra admin center with "App registrations" selected in the sidebar and the "New registration" button
  3. 03
    Enter a name (e.g. nemox-nemo), leave everything else at the defaults (single tenant), and click "Register".
    The "Register an application" form with the name nemox-nemo and default settings
  4. 04
    "API permissions" → "Add a permission" → "Microsoft Graph" → "Application permissions": add Mail.ReadWrite and Mail.Send, then click "Grant admin consent".
    Configured API permissions with Microsoft Graph application permissions and granted admin consent
  5. 05
    Optional: access can be restricted to the specific mailboxes nemox will process instead of tenant-wide (see "Restrict access to specific mailboxes" below).
  6. 06
    "Certificates & secrets" → "New client secret": choose a description and expiry and click "Add". Copy the secret value right away, it is shown only once.
    Certificates & secrets with the "New client secret" button and a created client secret
  7. 07
    Send us: Tenant ID, Client ID, client secret, and the email addresses of the mailboxes to connect (UPN). Your nemox contact will provide a secure transfer channel for this; please do not send it unencrypted by email.

Mail.ReadWrite for reading incoming emails and creating email drafts (e.g. reply and invoice drafts that open directly in Outlook). Mail.Send exclusively for sending freight-rate requests to carriers. Once we have received the credentials, we set up the connection and create the nemox user accounts for your team; you will receive the sign-in credentials for the add-in from us.

Tenant-wide access is the standard route. If your organization requires it, access can be restricted to a defined set of mailboxes via RBAC for Applications in Exchange Online. This route requires more setup effort (Exchange Online PowerShell) and replaces the older Application Access Policies.

IMAP/EWS (on request)

Connection for mailboxes outside Microsoft 365 / Google Workspace (IMAP) or on self-hosted Exchange (EWS): contact us. The Outlook add-in is not available for IMAP-connected mailboxes.

Which mailboxes?

Shared mailboxes

The usual route: nemox processes the emails of the shared mailbox (e.g. import@, quotes@).

Personal mailboxes of individual employees

Also possible, with explicit consent of the affected employees.

Reference

System requirements

Outlook add-in

RequirementDetails
Account
  • Mailbox on Exchange Online (Microsoft 365) or self-hosted Exchange (2016 or newer; only Exchange Server Subscription Edition remains in Microsoft support).
  • POP3/IMAP accounts in Outlook do not support add-ins.
Supported clients
  • Outlook on the web
  • New Outlook for Windows
  • Outlook for Windows from Microsoft 365 (for shared mailboxes at least version 2304)
  • Outlook 2024 (LTSC)
  • Outlook for Mac (Microsoft 365)
Limited
  • Outlook 2021 (LTSC): the add-in runs, but without shared-mailbox features
Not supported
  • Office 2016 and Office 2019 (Microsoft support ended on October 14, 2025; no longer listed by Microsoft as add-in clients)
  • Outlook Mobile (iOS/Android)
Network
  • Outbound HTTPS (port 443) to app.nemox.ai and to the standard Microsoft 365 endpoints (including appsforoffice.microsoft.com)

Mailbox access

RequirementDetails
Microsoft 365 / Exchange Online
  • Exchange Online mailbox required. Self-hosted Exchange (on-premises) is not supported by default; the integration uses the Microsoft Graph API, which only reaches Exchange Online mailboxes. EWS connectivity available on request.
  • Entra ID app registration with the application permissions Mail.ReadWrite and Mail.Send, one-time admin consent.
Mailboxes
  • Shared mailboxes and personal mailboxes are both supported.
Network
  • Notifications flow via Microsoft Graph webhooks from Microsoft to nemox; no firewall changes required on the customer side.

Questions about the setup?

We'll walk you through the rollout, from mailbox access to first sign-in.

Get in touch