Your signatures.
Your Microsoft 365.
Your control.
Centrally design, personalise, target and deploy Outlook signatures from a customer-hosted platform built around Microsoft Entra ID, Microsoft Graph and Azure.
Your email is not rerouted through a SoftLinkx signature service.
Next Signature Manager uses Outlook client-side signature insertion. The signature is resolved from customer-controlled configuration, inserted in the compose experience, then the message follows your normal Microsoft 365 mail flow.
Signature delivery path
New mail, reply, reply all or forward
Profile, photo and relevant group membership
Rules resolve the correct managed template
No SoftLinkx signature relay added to the path
One platform from design to delivery.
Give IT and communications teams central control over signature design, employee data, targeting, campaigns, assets and publishing without asking every employee to maintain their own Outlook signature.
Automatic Outlook insertion
Apply the centrally managed signature in supported Outlook compose experiences.
Rich signature designer
Visual and HTML modes share the same canonical signature, with live preview and fallback text.
Live Microsoft 365 profiles
Populate templates from Entra-backed user information and Microsoft 365 profile photos.
Advanced assignment rules
Priorities, ALL/ANY logic, profile fields and Entra group membership select the correct template.
Campaign scheduling
Add temporary or recurring campaign messaging without redesigning standard signatures.
Optional Auto Translate
Create a separate translated template while preserving placeholders and HTML structure.
Central asset library
Host and reuse logos, social icons, campaign images and GIF assets.
Diagnostics before publish
Catch broken references and hosted asset problems before configuration goes live.
Controlled administration
Use Entra authentication plus Azure RBAC/ABAC for narrowly scoped signature publishing.
Design. Target. Validate. Publish.
Normal template, rule, campaign, default and asset changes can be published without repeatedly redeploying the Outlook manifest.
Create full, compact, executive, sales or campaign templates.
Assign by user, profile data, location or Entra group.
Set temporary or recurring campaign windows.
Run diagnostics against references and hosted assets.
Authorised admins publish directly to customer Azure.
Everything included in Next Signature Manager.
Expand each category for the complete capability list.
Automatic managed signature insertion in supported Outlook compose experiences
Separate template selection for New Mail
Separate template selection for Reply and Reply All
Separate template selection for Forward
HTML signature delivery using Outlook's supported signature API
Plain-text fallback support
Silent Nested App Authentication flow for normal users
Task pane for status, profile context and troubleshooting
Organisation defaults when no higher-priority rule matches
Native Outlook signature handling options to reduce duplicates
Visual signature editing mode
Direct HTML editing mode
Shared canonical HTML between visual and HTML modes
Formatting toolbar
Hyperlink insertion
Hosted image insertion
Dynamic placeholder insertion
Live resolved preview
Plain-text fallback content
Duplicate templates for variants
Full, compact, executive, sales, contractor and campaign templates
Conditional HTML blocks for optional data
Display name
Given name
Surname
Email / UPN
Job title
Department
Company name
Office location
Mobile phone
Business phone
Formatted address
Employee ID where available
Microsoft 365 profile photo
Conditional hide/show for missing optional fields
HTML escaping of user-supplied profile characters
Enable / disable rules without deleting
Explicit rule priority
Match ALL logic
Match ANY logic
Stop-processing behaviour
Specific user targeting by email / UPN
Department targeting
Job title targeting
Company targeting
Office / location targeting
Employee attribute targeting
Microsoft 365 group targeting
Security group targeting
Mail-enabled security group targeting
Static distribution-group targeting
Nested / transitive group membership evaluation
Immutable Entra Object ID matching
Equals, not-equals, contains, starts/ends with, in, regex and exists operators
Campaign-specific signature content and banners
Campaign start date/time
Campaign end date/time
Recurring campaign schedules
Campaign audience targeting
Campaign priority with standard assignment logic
Central signature asset library
PNG upload
JPEG upload
WebP upload
GIF upload
Copy hosted asset URLs
Delete obsolete assets
Reuse assets across templates and campaigns
Responsive SaaS-style administration dashboard
Persistent light / dark mode
Status cards and operational summaries
Confirmation dialogs
Warning banners
Toast feedback
Template create / duplicate / edit / delete
Visual rule administration
Default New / Reply / Forward templates
Advanced JSON access for expert admins
Pre-publish configuration validation
Hosted asset URL checks
Template, rule and campaign reference validation
Direct publish to customer Azure using admin identity
No manifest redeployment for normal config changes
Optional full-directory Entra group search
Customer Azure Storage hosting
Customer Entra application registration
Microsoft Entra / Nested App Authentication
Microsoft Graph delegated User.Read for normal users
Optional Group.Read.All for admin group search
Azure Storage delegated user_impersonation for admin publishing
Dedicated signature administrator Entra group
Custom Azure Blob data role
Azure ABAC path conditions
Signature admins can be restricted from application JavaScript
No embedded client secret
No embedded storage account key
No embedded SAS token
No Translator key exposed in static admin app
No SoftLinkx mail relay required for signature stamping
Microsoft 365 Integrated Apps deployment
Single-tenant customer-specific production build
Optional Auto Translate workflow
Translation creates a new template rather than overwriting source
Dynamic placeholders preserved during translation
HTML structure preserved during translation
Optional Azure Function translation proxy
Managed identity for Azure Translator access
Customer-specific production build tooling
End-to-end Azure/Entra deployment script
Existing-deployment updater
Preservation of live signature config during supported upgrades
Preservation of signature assets during supported upgrades
Stable Outlook add-in identity across updates
Pilot-first deployment and acceptance workflow
Dynamic distribution groups are not advertised as supported group targets because they are not represented as normal Microsoft Graph group memberships. Auto Translate is optional and requires its Azure translation service to be deployed.
Built for organisations that want control, not another recurring SaaS dependency.
Exclaimer, CodeTwo and Opensense are mature signature platforms. Next Signature Manager takes a deliberately different route: customer-hosted, Outlook-centric, perpetual and designed to avoid a vendor-operated signature delivery service.
| Capability / model | Next Signature Manager | Exclaimer | CodeTwo | Opensense |
|---|---|---|---|---|
| Customer-hosted application & configuration | YesCustomer Azure | Vendor SaaS | Vendor SaaS | Vendor SaaS |
| Vendor-operated service required for signature delivery | NoCustomer-hosted add-in path | Yes | Yes | Yes |
| Third-party mail routing required in client-side Outlook mode | No | No | No | No |
| Perpetual single-tenant licence | Included | Subscription | Subscription | Subscription |
| Recurring per-user signature licence | None | User/mailbox based | User based | User based |
| Unlimited authorised users in licensed tenant | Yes | Licensed users | Licensed users | Licensed users |
| Microsoft Entra profile personalisation | Yes | Yes | Yes | Yes |
| Outlook client-side signature experience | Core model | Available | Available | Available |
| Campaign / banner management | Yes | Yes | Yes | Yes |
Where Next Signature Manager is the stronger fit: organisations standardised on Microsoft 365 that prefer customer-controlled Azure hosting, do not want a vendor-operated signature service in the delivery architecture, and favour one-off perpetual licensing over recurring per-mailbox subscriptions.
Comparison reflects publicly documented vendor capabilities reviewed in August 2026. Vendor products and licensing can change; validate current requirements during procurement.
Runs on services your IT team already governs.
Production deployment is built around a customer Entra application, Microsoft Graph, customer Azure hosting and Microsoft 365 Integrated Apps.
- Microsoft Entra ID for authentication and administrator identity.
- Microsoft Graph for live user profile, photo and supported group context.
- Customer Azure Storage for hosted application, configuration and signature assets.
- Azure RBAC + ABAC to constrain signature administrators to approved content paths.
- Microsoft 365 Integrated Apps for central Outlook deployment.
Built for the people who actually manage signatures.
A responsive portal keeps templates, rules, campaigns, assets, diagnostics and publishing in one place.
M 0400 000 000 | E [email protected]
SoftLinkxThis vector product mock-up makes the page usable immediately. Replace it later with a real dashboard/designer screenshot for a fully authentic product showcase.
Product gallery
Administration Dashboard
01-dashboard.png
Administration Dashboard
Overview, status cards and navigation
Signature Designer
02-signature-designer.png
Signature Designer
Visual editor, HTML and live preview
Assignment Rules
03-assignment-rules.png
Assignment Rules
Priorities, conditions and Entra targeting
Campaign Scheduling
04-campaigns.png
Campaign Scheduling
Dates, recurrence and audience targeting
Asset Library
05-assets.png
Asset Library
Hosted logos, icons and campaign artwork
Diagnostics
06-diagnostics.png
Diagnostics
Pre-publish validation and health checks
Assignment - Reporting
07-outlook-new-message.png
Assignment - Reporting
Managed signature automatically inserted
New - Rule Setup
08-outlook-reply.png
New - Rule Setup
Compact reply signature experience
Outlook Add-in Pane
09-outlook-pane.png
Outlook Add-in Pane
Status, user context and diagnostics
We deploy it into your environment.
The deployment service establishes the Azure, Entra and Microsoft 365 components, configures the administration boundary, pilots the add-in and hands over a working customer-hosted environment.
Prepare customer Azure and Microsoft Entra components.
Set permissions, publishing controls, defaults and initial templates.
Deploy through Microsoft 365 Integrated Apps to an agreed pilot group.
Complete acceptance testing, production rollout and admin handover.
Buy it once. Deploy it in your tenant.
No per-mailbox subscription and no recurring annual software licence fee for the licensed tenant.
One-time software licence for a single Microsoft 365 tenant.
Deployment, initial configuration, functional testing and administrator handover.
Perpetual licence is for one licensed Microsoft 365 tenant. Additional tenants, major customisation, third-party Microsoft/Azure charges and optional support after the included support period are separate unless agreed in writing.
Frequently asked.
The questions IT, security and procurement teams usually ask first.
The standard architecture does not route messages through a SoftLinkx signature server. The signature is inserted in supported Outlook compose experiences and the message then follows the customer's normal Microsoft 365 mail flow.
The production application, signature configuration and hosted signature assets are deployed into customer-controlled Azure services. Identity comes from the customer's Microsoft Entra tenant.
No. The perpetual enterprise licence covers unlimited authorised users inside the single licensed Microsoft 365 tenant. There is no recurring per-user software licence fee.
Yes. Normal changes to templates, rules, campaigns, defaults and signature assets are published through the administration portal. Manifest redeployment is only needed when the add-in itself changes in a way that requires it.
The recommended deployment uses a dedicated Entra security group, a custom Azure Blob data role and Azure ABAC conditions so signature admins can be limited to configuration and signature asset paths instead of hosted application code.
Next Signature Manager is currently an Outlook-centric client-side solution. It should only be advertised for Outlook clients and environments that support the required Microsoft add-in/event APIs and have been accepted during deployment. It does not currently claim universal coverage for every non-Outlook mail client.
The software licence remains perpetual for the licensed tenant. The customer can continue using the legitimately deployed licensed version. Ongoing support after the included period is optional and quoted separately.
Control every Outlook signature from your own Microsoft environment.
One tenant. Unlimited authorised users. One perpetual licence.