PoliteMail Implementation Method Comparison
SimpleIdeal for M365, Outlook desktop, and SaaS users in organizations from 500 to 20,000 employees. |
TechnicalIdeal for large enterprises sending high volume (>20K) email broadcasts with M365 or Exchange on-premises. | |
Fast; only 1 M365 Admin resource required. Requires an M365 group be set-up for PoliteMail app users, and a dialog checkbox to consent to set of M365 app permissions. M365 Admin grants org-level permissions upon initial PoliteMail app set-up. Any new user of the PoliteMail for Outlook app (setup.exe) or PoliteMail for M365 app (manifest) can login without additional permissions or authorization steps. |
Slower; multiple IT and Security resources required. Technical service-side changes to M365 tenant, SSO, customer network DNS and SMTP mail flow configurations. Your IT Security team will get approvals for PoliteMail M365 integration configuration:
|
| Simple | Technical | |
|---|---|---|
| Difficulty | Low | Medium-High. Difficulty level depends upon additional customer requirements (e.g. SMTP external email, subdomains, data integration). |
| Speed | Fast | Slow |
| Security | Minimal app permissions | Approvals required |
| Resources | M365 Admin | M365 Admin, IT Security, Network, Desktop |
| Time Required | <1 hour (not including meetings, reviews, and approvals) | 4+ hrs. Generally, service side implementations take 2 weeks to 2 months depending upon technical resources availability and your own organization's change management approvals process. |
