Skip to main content

Exchange Server Email Signature Rules and Scoping

Control which signature applies to which mail with server-side signature rules, groups and sync scoping on Exchange. Platform and Enterprise capability.

WiseStamp for IT › Exchange › Step 7 of 12 — Signature Rules & Scoping


Plan requirement: Server-side signature rules — Platform or Enterprise. Security Group sync — Enterprise (or trial).


Server-side signature rules

Rules assign signatures automatically based on conditions, with no user action.

  • Path: Integrations > Server-side > Signature rules > Add rule.

  • Sender conditions: all employees / specific groups / specific employees.

  • Email type: all / new / reply.

  • Recipient conditions: all / at least one internal / all internal / at least one external / all external.

  • Priority: when multiple rules match, the higher-priority (higher number) rule applies.

Create: select a Signature, configure Senders / Email type / Recipients / Priority, Save. Activate: turn on the rule’s Active toggle and confirm.

Use cases: a compliance disclaimer on all external mail; a department-specific signature for a group; a lighter signature on replies.


Groups

Organize employees for signature assignment: Employees > Manage groups > Add Group, then assign a signature per group. Groups can also be referenced as a sender condition in server-side rules.


Sync scoping (which employees are managed)

From Settings > Sync & Automations:

  • Synced employees: entire directory / specific (departments, OUs, cost centers) / from Security Group (Enterprise).

  • Selective import: Synced employees > Sync specific > Manage, choose scopes, Save & Sync.

Security Group synchronization (Enterprise)

For Entra ID environments, you can drive the managed set from a Microsoft Security Group (Enterprise only; Microsoft domains; no nested groups — explicit members only). Setup is an assisted Microsoft Graph process: grant WiseStamp GroupMember.Read.All, then send the Security Group’s Object ID to WiseStamp, who enables it. (This mirrors the Microsoft 365 Security Group flow; see the Microsoft 365 portal’s group-sync article for the full Graph steps.)

Topology note: Security Group sync depends on Entra ID. Pure on-prem (no Entra ID) does not apply — employee sync is not supported for on-prem, and no plan supports it (Identity & Employee Sync).


Validation

  • For each rule, send test mail that matches its conditions and confirm the right signature applies.

  • Verify priority ordering when multiple rules could match.

  • Confirm group-based assignment maps the intended signature to the intended group.

  • After scoping changes, confirm only intended employees appear in Employees.

Related articles


Did this answer your question?