WiseStamp for IT › Exchange › Step 9 of 12 — Go-Live Checklist
What WiseStamp requires, and what we recommend beyond it: the product requirement to mark an integration live is a single test email from any active employee with an assigned signature. The pilot-and-rollout process below goes further on purpose; treat it as recommended IT acceptance practice rather than a product requirement.
Pre-go-live: configuration sign-off
☐ Topology confirmed (off-prem / hybrid / on-prem). Pure on-prem is not supported — do not proceed past this checklist for pure on-prem.
☐ Entra ID connected; expected employees imported (Identity & Employee Sync). (Employee sync is not supported for on-prem; no plan supports it.)
☐ Synced fields verified against Entra ID.
☐ Deployment configured:
☐ Outlook Add-In deployed centrally (Outlook Add-In Setup), and/or
☐ Server-side connectors + transport rules created and enabled (Server-Side Routing).
☐ (Hybrid mode) Both configured; duplicate-prevention confirmed.
☐ (Platform/Enterprise) SSO tested if in scope (SSO (SAML)).
☐ Signatures assigned (Primary Signature; groups; server-side rules as needed).
☐ (Server-side) SPF verified; DKIM added and signing enabled; RTF = Never.
Stage 1 — Pilot group
Pick 5–10 users across supported environments: Outlook desktop (Win), Outlook for Mac, Outlook web, Outlook mobile, and — for server-side — at least one non-Outlook sender (mobile mail app or CRM).
Per pilot user:
☐ Set Active in WiseStamp.
☐ (Add-In) Restarted Outlook desktop / refreshed Outlook web.
☐ New / Reply / Forward show expected signature behavior.
☐ Correct rendering to internal and external recipients.
☐ Images/logos load and sized correctly.
☐ No duplicate signature (else check manual copy/paste signatures — Troubleshooting Reference).
☐ (Server-side) Signature appears from a non-Outlook device.
☐ (Server-side) Authentication shows SPF and dkim=pass.
☐ Legible in dark mode.
Validation matrix (record results)
User | Client/Device | New | Reply | Forward | Internal | External | Duplicates? | Notes |
Outlook desktop (Win) | ||||||||
Outlook for Mac | ||||||||
Outlook web | ||||||||
Outlook mobile | ||||||||
Non-Outlook (server-side) |
Stage 2 — Rules & scoping check (if used)
☐ Each server-side rule applies to the intended senders/email types/recipients.
☐ Rule priority produces the intended result when multiple match.
☐ Group-based assignment maps the right signature to the right group.
Stage 3 — Full rollout
☐ Enough seats for all employees to activate (Ongoing Admin Guide).
☐ New employee default status set to Active if you want auto-activation (Ongoing Admin Guide).
☐ Activate remaining employees (bulk Set status > Active).
☐ (Add-In) Communicate the restart/refresh requirement (Employee Rollout Handoff).
☐ Send the employee handoff communication (Employee Rollout Handoff).
Stage 4 — Post-go-live monitoring (1–2 weeks)
☐ Triage "no signature" / "duplicate" tickets with Troubleshooting Reference.
☐ (Server-side) Confirm mail flow healthy; no routing-induced delays/rejections.
☐ New hires in Entra ID appear on the next daily sync; leavers removed.
☐ Several admins retain Exchange admin center access.
Rollback / safety
Server-side: disable the Identify messages to send to WS SMTP rule to bypass routing, then contact support (Server-Side Routing, Troubleshooting Reference).
Add-In: disconnect/remove from the Microsoft 365 admin center (Outlook Add-In Setup).