Skip to content
Communications ⇄ CRM

Amazon SES to Microsoft Dynamics 365 Sales integration — real-time, two-way sync

Keep Amazon SES and Microsoft Dynamics 365 Sales in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Amazon SES and Microsoft Dynamics 365 Sales

Keep Microsoft Dynamics 365 Sales and Amazon SES working from the same contacts, and log every call, message, and meeting back on the record, in real time and in both directions.

Microsoft Dynamics 365 Sales holds the people the business talks to: the contacts, their phone numbers and email addresses, and which rep owns the relationship. Amazon SES is where the talking happens, whether that is calls, texts, email, or meetings. The two depend on the same people, and when the contact list in one drifts from the other, outreach goes to stale numbers and the record of what was said never makes it back to the account.

Stacksync syncs Activities, Custom Tables, Accounts, Contacts in Microsoft Dynamics 365 Sales with Email Templates, Suppression List, Verified Identities, Configuration Sets in Amazon SES field by field, in real time, and in both directions. Current contact details flow out to Amazon SES so it can reach the right person, and the calls, messages, and meetings Amazon SES produces flow back onto the matching record in Microsoft Dynamics 365 Sales. You decide which system owns which fields, and conflicts resolve by rules you set.

Common use cases

  • 01 Write product usage and warehouse-computed scores onto Dataverse tables so sellers see them in the model-driven app.
  • 02 Run a two-way dual-run between Dynamics and another CRM during a migration.
  • 03 Keep Email Templates in sync from a CMS or Git-backed source into SES via CreateEmailTemplate and UpdateEmailTemplate across environments.
  • 04 Two-way sync Contacts and their topic subscription state between the SES contact list and a Postgres database or CRM so opt-outs propagate in both directions.

Common sync patterns

One contact list, opt-outs included

A number, address, or unsubscribe recorded in either system updates the other, so no one calls a disconnected line or messages someone who opted out.

New contacts reachable right away

A contact created or updated in Microsoft Dynamics 365 Sales appears in Amazon SES within seconds, so outreach starts without exporting a list or re-keying numbers.

Where Amazon SES reaches out: contacts kept current

Names, phone numbers, email addresses, and the owning rep from Microsoft Dynamics 365 Sales stay current in Amazon SES, so every call, text, or email goes to the right person at the right address.

What you can sync between Amazon SES and Microsoft Dynamics 365 Sales

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Amazon SES objects Microsoft Dynamics 365 Sales objects How this pairing syncs
Contacts Subscribers in the contact list with per-topic opt-in state; CRUD via CreateContact/ListContacts/UpdateContact/DeleteContact, each carrying a LastUpdatedTimestamp for polling. Contacts Person records linked to accounts; synced with marketing and support systems. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Messages (SendEmail / SendBulkEmail) Outbound email is produced via SendEmail and SendBulkEmail, accepting raw MIME or a template plus destination list. Send-only; there is no message store to read back. Invoices Billing records; usually mastered in the ERP and mirrored back for seller visibility. Messages (SendEmail / SendBulkEmail) is specific to Amazon SES and Invoices to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side.
Contact Lists One list per AWS account, subdivided into Topics that group subscriptions; read and write via CreateContactList and GetContactList. Activities Emails, calls, appointments, and tasks; read out for activity analytics. Contact Lists is specific to Amazon SES and Activities to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side.
Email Templates Reusable subject/HTML/text templates with replacement variables; synced via CreateEmailTemplate, GetEmailTemplate, ListEmailTemplates, and UpdateEmailTemplate. Custom Tables Tenant-defined Dataverse tables; exposed through the same Web API as standard tables. Email Templates is specific to Amazon SES and Custom Tables to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side.
Suppression List Addresses auto-added on bounce or complaint; read with ListSuppressedDestinations and written with Put/DeleteSuppressedDestination to control re-sends. Accounts Company records in Dataverse; the usual anchor for two-way sync with databases and ERPs. Suppression List is specific to Amazon SES and Accounts to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side.
Verified Identities Email-address and domain identities cleared to send; managed via CreateEmailIdentity, ListEmailIdentities, GetEmailIdentity (DKIM and verification status). Leads Prospect records; written in from enrichment or web forms, read out on qualification. Verified Identities is specific to Amazon SES and Leads to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side.

How changes propagate between Amazon SES and Microsoft Dynamics 365 Sales

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Amazon SES Microsoft Dynamics 365 Sales Sub-second propagation

DetectionAmazon SES notifies Stacksync of record changes through webhook events. Message events (delivery, bounce, complaint, open, click) are pushed in near real time through configuration-set event destinations.

DeliveryEach detected change is written to Microsoft Dynamics 365 Sales through its API, with automatic retries and rate-limit backoff.

Microsoft Dynamics 365 Sales Amazon SES Sub-second propagation

DetectionMicrosoft Dynamics 365 Sales notifies Stacksync of record changes through webhook events. Dataverse change tracking with delta tokens, plus registered webhooks on table events.

DeliveryEach detected change is written to Amazon SES through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Amazon SES: Every SES API action except SendEmail, SendRawEmail, and SendTemplatedEmail is throttled to 1 request/second per Region; the send rate and 24-hour sending quota are account-specific, adjustable, and per Region.
  • Microsoft Dynamics 365 Sales: Requests are governed by Dataverse service protection limits evaluated per user and time window.
What ships with Amazon SES ⇄ Microsoft Dynamics 365 Sales

Connect Amazon SES and Microsoft Dynamics 365 Sales for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon SES–Microsoft Dynamics 365 Sales connection.

Real-time

Two-way sync

Changes in Amazon SES or Microsoft Dynamics 365 Sales instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Amazon SES or Microsoft Dynamics 365 Sales data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Amazon SES or Microsoft Dynamics 365 Sales record.

Observability

Monitoring

Track your Amazon SES ⇄ Microsoft Dynamics 365 Sales sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Amazon SES and Microsoft Dynamics 365 Sales.

How the Amazon SES and Microsoft Dynamics 365 Sales connectors work

Amazon SES

Integration surface
AWS SES API v2 (REST/JSON over HTTPS) plus an SMTP sending interface
Authentication
AWS IAM credentials (access key + secret) signed with Signature Version 4, or an assumed IAM role via STS; the SMTP interface uses SMTP credentials derived from an IAM user
Change detection
Message events (delivery, bounce, complaint, open, click) are pushed in near real time through configuration-set event destinations (SNS/EventBridge/Firehose); contacts, templates, and suppression entries are polled via List/Get operations
Capabilities
read · write · webhooks
Rate limits
Every SES API action except SendEmail, SendRawEmail, and SendTemplatedEmail is throttled to 1 request/second per Region; the send rate and 24-hour sending quota are account-specific, adjustable, and per Region

Microsoft Dynamics 365 Sales

Integration surface
Dataverse Web API (OData v4 REST)
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
Dataverse change tracking with delta tokens, plus registered webhooks on table events
Capabilities
read · write · webhooks
Rate limits
Requests are governed by Dataverse service protection limits evaluated per user and time window.
How it works

How to connect Amazon SES to Microsoft Dynamics 365 Sales — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Amazon SES and Microsoft Dynamics 365 Sales with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Amazon SES connected
    Microsoft Dynamics 365 Sales connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Amazon SES and Microsoft Dynamics 365 Sales objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Amazon SES ⇄ Microsoft Dynamics 365 Sales
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Amazon SES Microsoft Dynamics 365 Sales
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Amazon SES and Microsoft Dynamics 365 Sales integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 335 integrations available for Amazon SES and Microsoft Dynamics 365 Sales.

Popular · 8 of 335
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.