Documentation

Microsoft 365 Connector - Connect your mailbox

Integrations
Updated Apr 30, 2026

Overview

The Microsoft 365 Connector lets your organisation send all ChangeBreeze email notifications, approval requests, change updates and stakeholder alerts from your own Office 365 mailbox instead of the default [email protected] address.

Once enabled, recipients see emails from your domain (e.g. [email protected]), which improves deliverability and brand trust.

What you'll need

  • An Azure AD (Entra ID) account with permission to register applications
  • An Office 365 mailbox to send from (e.g. a shared mailbox or service account)
  • Organisation Admin access in ChangeBreeze

Step 1 - Register an App in Azure AD

  1. Sign in to the Azure Portal → App registrations
  2. Click + New registration
  3. Enter a name, e.g. ChangeBreeze Mail Connector
  4. Under Supported account types Normally (Single tenant) but this may differ for your organisation
  5. Set the redirect URI to Web, the URL can be obtained from the Integrations page for M365 on changebreeze
  6. Click Register

After registration, copy these two values from the Overview page, you'll need them shortly:

  • Application (client) ID
  • Directory (tenant) ID

Step 2 - Add API Permissions

  1. In your new app registration, go to API permissions
  2. Click + Add a permission
  3. Select Microsoft Graph
  4. Choose Delegated permissions
  5. Search for and add:
    • Mail.Send
    • User.Read
  6. Click Add permissions
  7. Optional: Click Grant admin consent for [your tenant] if your Azure AD policy requires it

Step 3 - Create a Client Secret

  1. Go to Certificates & secrets
  2. Under Client secrets, click + New client secret
  3. Enter a description (e.g. ChangeBreeze) and choose an expiry period
  4. Click Add
  5. Important: Copy the Value immediately, it won't be shown again. (Do not copy the Secret ID.)

Step 4 - Enter Credentials in ChangeBreeze

  1. In ChangeBreeze, go to Settings → Integrations → Microsoft 365
  2. Enter the following values from your Azure App Registration:
    • Tenant ID (Directory ID)
    • Client ID (Application ID)
    • Client Secret (the Value you copied in Step 3)
  3. Click Save Settings

All credentials are encrypted at rest using AES encryption and are never exposed in plain text.

Step 5 - Authorise the Connection

  1. After saving, click the Authorise Connection button
  2. You'll be redirected to Microsoft's consent screen
  3. Sign in with the mailbox account you want to send from (e.g. [email protected])
  4. Review the permissions and click Accept
  5. You'll be redirected back to ChangeBreeze with a success message

Update the Sender Email Address and Display Name.

Step 6 - Enable the Integration

  1. Tick the Enable Microsoft 365 email sending checkbox
  2. Click Save Settings

All email notifications for your organisation and its sub-companies will now be sent via the connected mailbox.

Testing the Connection

Click the Test Connection button on the settings page to verify the OAuth token is valid. You should see a confirmation message showing the connected email address.

You can also trigger a test notification (e.g. submit a change for approval) to confirm emails arrive from your custom domain.

Disconnecting

Click Disconnect on the settings page to remove the OAuth connection. Notifications will automatically revert to the default ChangeBreeze relay address.

Can I use a shared mailbox?

Yes. During the authorisation step, sign in with a user who has Send As permissions on the shared mailbox, then set the shared mailbox address as the Sender Email Address in ChangeBreeze.

Does this affect all companies under my organisation?

Yes. The Microsoft 365 Connector is an organisation-level integration. Once enabled, all companies within your organisation will send notifications from the connected mailbox.

Related Articles

Integrations

Microsoft Teams Integration - Organisation-Wide Webhooks

Organisation-wide Teams webhooks provide centralized, automated monitoring of all change management activities across your entire organisation. Unlike company-specific webhooks that require manual selection, org-wide webhooks operate silently in the background, ensuring management and compliance teams never miss critical change notifications.

Integrations

Auvik Integration Overview

What this integration does The Auvik integration lets your organisation: Connect ChangeBreeze to your Auvik account using API credentials Map each ChangeBreeze company to an Auvik tenant/site Sync devices from mapped Auvik tenants into ChangeBreeze Device Inventory Optionally sync managed devices only Open each company’s Auvik Maintenance Window directly from Change pages

Integrations

ConnectWise Integration Guide

The ConnectWise integration for ChangeBreeze allows you to seamlessly connect your change management workflow with your ConnectWise PSA environment. This integration provides automatic ticket linking, real-time status updates, and device synchronization.

Integrations

How to set up Auvik with ChangeBreeze

This guide will provide a step by step guide in how to integrate Auvik with ChangeBreeze.

Integrations

Hudu Integration Guide

The Hudu integration allows you to seamlessly link your Hudu documentation platform with ChangeBreeze, enabling you to reference passwords, websites, knowledge base articles, and processes directly within your change controls and standard change templates. This integration provides quick access to critical documentation and credentials during change implementation.