Pipedrive

Pipedrive's Email sync connects a person's Microsoft 365 mailbox, and Footer365 signs mail that passes through your Microsoft 365. Pipedrive's pages do not say how the mail it sends is delivered, so this guide tells you what to check. 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 sent from Pipedrive with Email sync turned on, if it goes through the connected Microsoft 365 mailbox. Pipedrive says you can "View, send and reply to email conversations directly from your Sales Inbox" and that group emails need "Email sync enabled with a valid email account". It does not say through which servers the mail is sent, so check one message.
• Cannot be signed: Campaigns email, which Pipedrive sends with DNS records on your domain that point to Pipedrive.
• How it connects: the provider list names "Office 365 / Outlook" and "Microsoft Exchange (EWS)". Pipedrive does not say whether Office 365 uses Microsoft Graph, OAuth or another protocol.
• Status: from Pipedrive'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 Pipedrive sends is signed. Using the Outlook add-in only
• Every person who sends from Pipedrive has a Footer365 signature rule that covers them.
• A Microsoft 365 global administrator or application administrator may have to approve Pipedrive, as in step 1.

Step 1: Approve the app in Microsoft 365

Pipedrive says that when your Microsoft organisation requires administrator consent before third-party apps can access user mailboxes, it is "a Microsoft permission setting and not a Pipedrive error." Someone with the Microsoft 365 global administrator or application administrator role must approve it:

1. In Pipedrive, go to Personal preferences > Email sync, select + Email account, and enter the email address.
2. Sign in to Microsoft with an administrator account.
3. On the permissions screen, check Consent on behalf of your organization, then select Accept.
4. Pipedrive says that at the next step you can cancel adding the administrator's account. Allow several minutes for the change to apply across the organisation.

Pipedrive's page does not list the permissions. Read them on Microsoft's screen first. Approve an app's access in Microsoft 365 shows the other ways to approve. Pipedrive's own page: Resolving Microsoft admin approval issue.

Step 2: Choose the mailbox

• Each person's own mailbox is what Email sync connects. The mail is signed with the signature your rules give that person.
• A shared address: Pipedrive's team account "allows multiple users to access and manage emails from a shared address", on Premium and higher plans. Its pages do not say whether a Microsoft 365 shared mailbox can be connected.
• Aliases: Pipedrive says sending from an alias is available only for Gmail accounts, not Outlook or Exchange.

Step 3: Connect it in Pipedrive

Following Pipedrive's steps:

1. Open the account menu in the top right and go to Personal preferences > Email sync.
2. Enter the email address and select Get started.
3. Choose your email provider, Office 365 / Outlook, and sign in to Microsoft.
4. Grant Pipedrive access, and choose a personal or team account.

Choose Office 365 / Outlook, never Microsoft Exchange (EWS). Pipedrive's own steps: How can I set up the email sync.

Step 4: Check one message

1. Send an email from Pipedrive to an address outside your organisation that you can read. Pipedrive says emails sent through it "are queued and processed in short intervals", and group emails have "a 30-second delay", so allow a minute.
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. Pipedrive's pages do not say whether the message is saved there.

If X-Footer365-Relay-Id is missing, the message did not pass through your Microsoft 365, and Footer365 cannot sign Pipedrive's mail. What other results mean: Mail from our CRM is not signed.

Where the signature goes

Pipedrive's pages read say team accounts have shared signatures, and do not describe a personal signature setting. If you see two signatures, remove Pipedrive's. To place Footer365's signature in a template, use a marker, and check one message, because Pipedrive's pages do not say what it does with text in double braces. Place the signature with a marker

What is not signed

• Campaigns. Pipedrive's domain authentication tells email providers "that Pipedrive is a trusted sender from your domains", with CNAME and TXT records that "point those records to Pipedrive", and the SPF record is described as "One key and return path". That is mail sent from Pipedrive's servers, so Footer365 never sees it. Pipedrive: Campaigns email domain authentication
• Anything Pipedrive does not send through your mailbox. Check one message of each kind you send.

What stops working

Pipedrive lists "Microsoft Exchange (EWS)" as a provider. Microsoft starts switching Exchange Web Services off in October 2026 and finishes in April 2027, so a mailbox connected that way will stop working. Reconnect it as Office 365 / Outlook. Exchange Web Services is being switched off

Limits

Pipedrive's page says sending limits are shared across the company account, with "Up to 40 email actions per minute within a company account". It says a group email can have up to 100 contacts, and states no daily limit. Microsoft's limits for a mailbox are 10,000 recipients a day and 30 messages a minute. Microsoft: Exchange Online limits

Last resort: a connector to Exchange Online

Pipedrive's pages describe no connector from Pipedrive into Exchange Online, and Pipedrive runs on its own servers. Microsoft says SMTP relay cannot be used for a service hosted by someone else, and asks such a service for a certificate of your own. So there is no connector route for Pipedrive mail. Last resort: a connector to Exchange Online

If it does not work

1. A person sees that administrator consent is required. Follow step 1.
2. The connection stops after October 2026. It may use EWS. Reconnect as Office 365 / Outlook.
3. The message has no X-Footer365-Relay-Id. It did not pass through Microsoft 365. It may be a Campaigns email.
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:

• Pipedrive: Email sync, last updated 23 September 2026.
• Pipedrive: How can I set up the email sync, last updated 3 September 2026.
• Pipedrive: Which provider is best for email sync, last updated 3 September 2026.
• Pipedrive: Resolving Microsoft admin approval issue, last updated 3 September 2026.
• Pipedrive: Group emailing, last updated 3 September 2026.
• Pipedrive: Campaigns email domain authentication, last updated 3 September 2026.