> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/whats-new/april-2026-feature-wave/april-2026-feature-wave/enabling-outbound-emails-via-microsoft-graph-api.md).
# Enabling Outbound Emails via Microsoft Graph API
We're making a significant update to Enate’s email system: With the release of the April 2026 Feature Wave, outbound Email Connectors now support the use of Microsoft Graph API.
This feature is designed for organizations that want to align their communication workflows directly with Microsoft’s preferred, high-security API protocols for improved security, compliance, and governance standards.
### Benefits of Microsoft Graph API
Microsoft Graph API brings some additional features at the server level:
* **Sent Items are preserved automatically.** Emails sent from Enate via Graph API are saved to the Sent Items folder of the sending mailbox on your Exchange/Microsoft 365 server, giving you a server-side record of all outbound Enate correspondence. For specific information on how Microsoft Graph API handles the storing of sent items see [here](https://learn.microsoft.com/en-us/graph/outlook-things-to-know-about-send-mail).
* **Modern authentication replaces legacy credentials.** Graph API uses OAuth 2.0 via an Azure AD app registration, rather than the username/password or app-password approach.
* **Outbound mail flows through the full M365 stack.** Because emails sent via Graph API, pass through Exchange Online transport rules, DLP policies, and message tracking logs just like any other mail from your organisation. That means your existing compliance controls, retention policies, and audit trails apply automatically, with no additional configuration needed.
### How do you configure a Graph API Outbound Connector?
Configuring an Outbound Graph API Connector is very similar to configuring Inbound Graph API Connectors which are already present in the Enate system. For a full set of detailed instructions on configuring permissions and credentials for a Office 365 Integration see [**here**](https://docs.enate.net/enate-help/builder/builder-2021.1/email-mailbox-configuration/microsoft-office-365-email-integration-with-enate-via-graph-api-model).
Once you have finished configuring an Office 365 Integration, you can move ahead and create a Outbound Graph API Connector. First go to the Email Connector page in Builder and select to add a Graph API Connector (i.e. the same as you do if you were adding an *Inbound* Graph API Connector).
This will bring up the Graph API Connector pop-up for you to configure the connector. Give the connector a name then select ‘Outgoing’ in the Use For dropdown.
You should also set the Primary Email Address, i.e. the email address this connector will be sending mail out From.
After you have finished configuring the Outbound options for the connector, remember to ‘Test Connection’, Enable the connector, and then Save it to set the connector live.
Once you have saved your Outbound Connector and set it live, a default Route will automatically be created, and this new email address will be available to set as a From address in outgoing emails.
### Can an Outbound Graph API Connector be edited after creation?
**Yes.** Should you need to make any edits or delete the Connector, the connector will be visible on the Connector page of Builder. However, it should be noted that you can not change the ‘Use For’ direction once the connector has been created.
### Can Additional Routes/Aliases be added to an Outbound Graph API Connector?
**Yes.** You can create additional Routes for an Outbound Graph API Connector via the Routes page in Builder, essentially creating Alias from addresses that can then be used by the system. You can find information for creating additional outbound Alias/Routes on the Outbound Routes page.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.enate.net/whats-new/april-2026-feature-wave/april-2026-feature-wave/enabling-outbound-emails-via-microsoft-graph-api.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.