SugarCRM

SugarCRM sends email through your Microsoft 365 mailboxes with its Microsoft connector, using an app you register in your own Microsoft tenant, and Footer365 signs mail that passes through your Microsoft 365. Choose how your CRM or app sends its mail explains the two ways to send, and this guide follows the first.

At a glance

• Can be signed: email Sugar sends through the Microsoft connector: the system's outbound email, set in Admin > System Email Settings, and each user's own outgoing email account. SugarCRM says the connector lets Sugar "connect to the Microsoft API Services via OAuth2 to send outbound emails."
• Cannot be signed: anything Sugar sends without the connector. The page read does not say how campaign email is sent, so check one message.
• How it connects: an app that you register in your tenant, with delegated Microsoft Graph permissions. From Sugar 14.0.3 that is Mail.Send. Before 14.0.3 it is SMTP.Send, and SMTP sign-in must be on.
• Status: from SugarCRM's documentation as read on 23 October 2026, not tested by Footer365.

Before you start

• Footer365 mail flow is set up. With the Outlook add-in only, no mail Sugar sends is signed. Using the Outlook add-in only
• Every person who sends from Sugar has a Footer365 signature rule that covers them.
• SugarCRM says you must be an administrator user in Sugar and have an active Microsoft Azure account. For Sugar before 14.0.3 it also says: "You must have SMTP AUTH enabled on your email server." Turn on SMTP sign-in for one mailbox

Step 1: Approve the app in Microsoft 365

Unlike most CRMs, SugarCRM has no app of its own for your tenant. You register one, so you are the app's owner. SugarCRM's steps, in the Azure portal:

1. Search for "app registrations" and open it, then select + New registration, or Register an application if that button is not shown.
2. Enter a name and choose a supported account type. SugarCRM says the single-tenant option needs Sugar 14.0 or later.
3. Under API permissions, select + Add a permission and add Microsoft Graph delegated permissions. For Sugar 14.0.3 and higher, SugarCRM says: "Select "Mail.Send" under the Mail permissions option." For lower versions it says to add offline_access, IMAP.AccessAsUser.All and SMTP.Send.
4. Under Authentication, select + Add a platform, choose Web, and enter the redirect address {Your Sugar URL}/oauth-handler/MicrosoftOauth2Redirect.
5. Under Certificates & secrets, select + New client secret, and copy the value at once, because it cannot be read again.
6. On Overview, note the Application (client) ID, and for a single-tenant app the Directory (tenant) ID.

SugarCRM's page does not mention administrator consent. If Microsoft asks for it, see Approve an app's access in Microsoft 365.

Step 2: Choose the mailbox

• Each person's own mailbox. SugarCRM says: "Please do not assign any group users to the application." Assign individual users instead, and allow several hours for a change to take effect. The mail is signed with the signature your rules give that person.
• A shared mailbox: SugarCRM's page does not cover it. Do not assume it works.

Step 3: Connect it in Sugar

1. System email: in Sugar, go to Admin > System Email Settings and configure the outbound email with the Microsoft connector, using the details you noted in step 1.
2. Each user's own account: a user selects the Emails module tab, then Email Settings, and creates an outgoing email account with the Microsoft connector.

SugarCRM's own steps: Integrating with Microsoft for admins.

Step 4: Check one message

1. Send an email from Sugar to an address outside your organisation that you can read.
2. Open the headers of the copy you receive.
3. Return-Path should be the sender's own address, and X-Footer365-Relay-Id should be there.
4. Look in the sender's Sent Items. SugarCRM's page does not say whether the message is saved there.

What other results mean: Mail from our CRM is not signed.

Where the signature goes

SugarCRM's page read does not describe a signature setting. If you see two signatures, remove Sugar's. To place Footer365's signature in a template, use a marker, and check one message, because SugarCRM's page does not say what Sugar does with text in double braces. Place the signature with a marker

What is not signed

• Campaign email. The page read does not say how Sugar sends it. Check one message before relying on it.
• Sugar Market. This guide does not cover it.

What stops working

Sugar before 14.0.3 uses the SMTP.Send permission and needs SMTP AUTH on the mailbox. SMTP sign-in with a password is the subject of Microsoft's announced change at the end of December 2026, and the connector signs in with OAuth, but the SugarCRM page does not say which Sugar versions stop working. Move to Sugar 14.0.3 or later and the Mail.Send permission if you can. SugarCRM's page does not mention Exchange Web Services. Turn on SMTP sign-in for one mailbox

Limits

SugarCRM's page states no sending limit. Microsoft's limits for a mailbox apply: 10,000 recipients a day and 30 messages a minute. Microsoft: Exchange Online limits

Last resort: a connector to Exchange Online

The Sugar page read describes no connector from Sugar into Exchange Online. If you run Sugar on a server your organisation runs, with a fixed address that only your organisation uses, a connector is possible under Microsoft's conditions, and Sugar would then need SMTP settings that point at your Microsoft 365. SugarCRM's page does not describe that. Sugar hosted by SugarCRM is a service hosted by someone else, and Microsoft says SMTP relay cannot be used for one. Last resort: a connector to Exchange Online

If it does not work

1. A user cannot connect. Check the user is assigned to your app individually, not through a group, and allow several hours.
2. Microsoft asks for administrator approval. Approve an app's access in Microsoft 365
3. The message has no X-Footer365-Relay-Id. It did not pass through Microsoft 365.
4. It passed through Footer365 but is unsigned. The signature was not added
5. Still not clear. Mail from our CRM is not signed

Sources

Read on 23 October 2026:

• SugarCRM: Integrating with Microsoft for admins, no date shown.