Every mail the application sends leaves from a real mailbox in the buyer’s own tenant through the corporate mail API, with no SMTP relay and no third-party mail vendor in the path, with the full template suite the business actually sends and a test-recipient mode that redirects all outgoing mail so a test run can never reach a real customer.
What ports as-is
- The integration recipe: app-only credential and mail client
- One configuration section with an enabled gate
- Bind-only configuration so a blank template still boots
- Application permission and admin consent
- HTML bodies with user-input encoding
- Contact-form wiring including CORS for a static-site caller
- The test-recipient redirect
- The secrets posture
The template suite is itself reusable in shape: confirmations, cancellations, appointment and service notices, combination templates, tokenised self-service links, with send-tracking fields and a lock that freezes a record once a notification has gone out.
What we build for you
- App registration and admin consent
- The sending mailbox
- Template copy and branding in their language and register
- Recipient and CC rules
- The redirect address for their test environment
Template bodies are the bulk of it.
