Field report 11 · Identity and security
One mail route instead of many: reuse beats a new integration
Why new applications send their notifications through one shared, hardened mail route instead of their own providers.
- Status
- Built Built and proven in our own use.
- Published
- Publisher
- SIMO GmbH, Aschaffenburg, Germany
Starting questionNew applications need to send email notifications. Do you connect a separate provider for each of them?
What we decided and built
All applications send through one hardened mail route in the central gateway. It uses Microsoft Graph, and the other services call it through an internal endpoint.
Monitoring alerts also run through this route via a small bridge, because the monitoring tools cannot do modern SMTP authentication.
What it means for business architecture
Every additional external interface brings its own credentials, templates, limits and review duties. A shared capability noticeably reduces that load.
Learnings
- A second provider doubles the effort for key rotation and review.
- Where tools cannot do modern authentication, a narrow bridge helps. Falling back to passwords does not.
- Brand and privacy notice stay consistent when there is only one family of templates.
- Microsoft Graph
- reuse
- gateway