Connect Amazon SES and Microsoft Office 365 to unlock the power of automation
- No credit card required
- Free forever for core features
- 14-day trial for premium features and apps
How Zapier works
Zapier makes it easy to integrate Amazon SES with Microsoft Office 365 - no code necessary. See how you can get setup in minutes.
Choose a trigger
A trigger is the event that starts your Zap—like a "New Verified Identity" from Amazon SES.
Add your action
An action happens after the trigger—such as "Create Event" in Microsoft Office 365.
You’re connected!
Zapier seamlessly connects Amazon SES and Microsoft Office 365, automating your workflow.
Supported triggers and actions
Zapier helps you create workflows that connect your apps to automate repetitive tasks. A trigger is an event that starts a workflow, and an action is an event a Zap performs.
- New Verified Identity
Triggers when a new identity is verified in SES.
Try ItTriggerPolling - Calendar
- Time BeforeRequired
- Time Before (Unit)Required
Try ItTriggerPolling- Calendar
Try ItTriggerPolling- Shared Inbox
Try ItTriggerPolling
- Sender Address
- Subject
- Body
- To_addresses
- Cc_addresses
- Bcc_addresses
- Format
- Reply_addresses
- Return_path
ActionWrite- Parent FolderRequired
- Child Folder
Try ItTriggerPolling- Contact Folder
Try ItTriggerPolling- Parent Folder
- Child Folder
- Search termsRequired
- Note
Try ItTriggerPolling
Zapier is the automation platform of choice for 87% of Forbes Cloud 100 companies in 2023




93%
Customers who say using Zapier has made them better at their job
25m
Customers have created over 25 million Zaps on the platform
6 mins
The average user takes less than 6 minutes to set up a Zap
Learn how to automate Microsoft Office 365 on the Zapier blog
Frequently Asked Questions about Amazon SES + Microsoft Office 365 integrations
New to automation with Zapier? You're not alone. Here are some answers to common questions about how Zapier works with Amazon SES and Microsoft Office 365
How do I configure Amazon SES to send emails using Microsoft Office 365?
To configure Amazon SES to send emails using Microsoft Office 365, you'll need to set up Amazon SES as an SMTP relay. Begin by verifying your domain with Amazon SES, and then create SMTP credentials. In Office 365, use these credentials to set up a new outbound connector that redirects outbound mail through the Amazon SES servers.
What triggers can we use in Office 365 when integrating with Amazon SES?
When integrating with Amazon SES, you can trigger actions based on events such as receiving new emails in Office 365, changes in calendar events, or updates in contact lists. These triggers enable automated workflows that involve sending notifications or triggering email campaigns through Amazon SES.
Can I receive bounce back notifications in my Office 365 inbox when an email fails via Amazon SES?
Yes, you can receive bounce back notifications for emails sent via Amazon SES. By configuring your AWS SNS topics and associating them with your verified domains or email addresses, you can set up notification rules that forward bounce and complaint emails directly to your Office 365 inbox.
How does authentication work between Office 365 and Amazon SES?
Authentication between Office 365 and Amazon SES primarily involves SMTP authentication. Follow the steps in AWS to create SMTP credentials for the application. In your Office 365 settings, these credentials authenticate outbound mail traffic through a connector setup specifically for the integration.
What actions are possible after triggering on an event in Office 365?
After triggering an event within Office 365—like a new email received or a calendar update—you have multiple options for actions using Amazon SES. You could automatically send transactional emails or distribute newsletters leveraging these changes instantly without manual intervention.
What are the typical challenges faced during this integration process?
Typical challenges include setting up correct DNS configurations for domain verification, ensuring SMTP settings are properly configured within both platforms, and managing compliance requirements concerning data handling and transmission when routing emails outside native services like Microsoft Exchange Online.
Is it necessary to verify each sender email address individually with both platforms during integration?
It is not strictly necessary if you verify entire domains instead of individual addresses. Verifying a domain with both platforms simplifies management and allows sending from any email address within that domain without additional configuration steps.