Introduction
Deploying centralized email signatures across your organization doesn't have to be complex. Whether you use Microsoft 365 (Exchange Online) or on-premises Exchange Server, this guide walks you through the entire process—from connecting your tenant to rolling out signatures to your first users.
Step 1: Connect Your Microsoft 365 Tenant
For NextClaimer (E-Kache) Cloud, start by granting admin consent. Navigate to the NextClaimer (E-Kache) setup wizard and authenticate with your Microsoft 365 admin account. OAuth 2.0 and Microsoft Graph API handle the secure connection. You'll need Global Administrator or Exchange Administrator permissions to complete this step.
Step 2: Configure Your First Signature Template
Create a template in the HTML editor. Use dynamic fields for name, title, department, phone, and email—these will pull from Active Directory or Azure AD automatically. Preview how the signature will look for different users before deploying.
Step 3: Set Up Rules
Define when each signature applies. Common rules: use Signature A for external mail, Signature B for internal; or different templates by department. The rule engine supports conditions based on sender, recipient, message direction, subject, and more.
Step 4: Map Directory Attributes
Connect to Active Directory (LDAP/LDAPS) or Azure AD (Microsoft Graph). Map DisplayName, Title, Department, Office, TelephoneNumber, Mobile, and Manager to your template fields. Test with a few users to ensure data populates correctly.
Step 5: Pilot and Roll Out
Start with a pilot group—one department or 10–20 users. Verify signatures apply correctly, then expand. Most organizations are fully deployed within 2–4 hours of starting the setup.
Next Steps
Once your signatures are live, consider adding disclaimers for external mail, campaign banners for marketing, or out-of-office message automation. NextClaimer (E-Kache) supports all of these from the same central console.