Do Not Allow Signatures for E-mail Messages: Registry Setting Explained
Do not allow signatures for e-mail messages registry setting is what IT admins search for when they want to stop users from adding or changing email signatures in Outlook. The honest answer is that this setting does exactly that and nothing more. It does not touch legally binding e-signatures on documents or contracts. That confusion is common, and it's the main catch most guides skip.
Here's what happens behind the scenes: the registry key lives under HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\Options\Mail, and when enabled it locks the signature controls in the Outlook desktop client. Users can't create, edit, or swap signatures. But a contract that needs a real signature still gets signed the normal way, because that workflow runs through a different system entirely. For organizations that need controlled, compliant document signatures alongside email signature policies, a centralized e-signature solution like LoreSign handles the contract side.
| At a glance | Details |
|---|---|
| What it controls | Outlook email signatures only |
| Registry path | HKCU\Software\Policies\Microsoft\Office\16.0\Outlook\Options\Mail |
| Value name | DisableSignatures |
| Value data | 1 to block, 0 or absent to allow |
| Applies to | Outlook desktop on Windows |
| Does not affect | Document or contract e-signatures |
In This Guide
- What the 'Do Not Allow Signatures for E-mail Messages' Registry Setting Actually Does
- Email signatures vs document e-signatures: what each setting actually controls
- The Exact Registry Path and Value for Disabling Email Signatures
- Do Not Allow Signatures For E-mail Messages Registry: A Step-by-Step Guide
- How to Disable Email Signatures Using Group Policy
- How to Disable Email Signatures Using Microsoft Intune
- Platform-Specific Removal: Windows, Mac, Web, and Mobile
- What You Cannot Do After Disabling Email Signatures
- Email Signatures vs. Document E-Signatures: Why This Setting Doesn't Affect Contract Signing
- When to Use a Centralized E-Signature Solution Instead
What the 'Do Not Allow Signatures for E-mail Messages' Registry Setting Actually Does
The "Do not allow signatures for e-mail messages" policy blocks users from creating, editing, or applying email signatures in Outlook desktop clients. It does not touch document or contract e-signatures.
The setting is a Group Policy administrative template control. When enabled, Outlook hides the signature options under File > Options > Mail. Users can't add new signatures or modify existing ones through the Outlook interface.
What the setting controls
It controls one thing: manual email signature management in Outlook for Windows. That's it. Users lose the ability to create, edit, or assign signatures to outgoing mail.
What the setting does NOT control
It doesn't remove signatures already in place. It doesn't affect Outlook on the web, Outlook for Mac, or mobile apps. It doesn't stop users from typing a signature block directly into an email body. And it has zero effect on document signing workflows.
Email signatures vs. e-signatures: the critical distinction
An email signature is a text block appended to messages. An e-signature is a legally binding mark on a contract or document. The registry setting only governs the first. If your team signs PDFs or contracts, this policy won't touch that workflow.
The 'Do not allow signatures for e-mail messages' policy only blocks Outlook's email signature feature on Windows. It has no effect on document or contract e-signature workflows, which run through a separate signing platform and remain fully functional.
Email signatures vs document e-signatures: what each setting actually controls
| Factor | Email signature setting | Document e-signature workflow |
|---|---|---|
| What it governs | The sign-off block appended to outgoing Outlook messages | The legally binding signing of a PDF or contract |
| Where it lives | Windows registry policy under Outlook Options\Mail | A dedicated e-signature platform, separate from Outlook |
| Effect of disabling | Users cannot create, edit, or insert email signatures in Outlook | No effect — signing requests still send and complete normally |
| Who typically manages it | IT admins via Group Policy or registry deployment | Operations, legal, or sales teams via the signing platform |
| Audit and proof | None — it is cosmetic text only | Certificate of completion and audit trail record each signer |
The Exact Registry Path and Value for Disabling Email Signatures
The setting lives in HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\Options\Mail. That's the full path. If the key doesn't exist yet, you create it.
Registry path breakdown
Each segment matters. HKEY_CURRENT_USER means the policy applies per user, not machine-wide. Software\Policies is where Group Policy writes its settings. Microsoft\Office\16.0 targets Office 2016 and later, including Microsoft 365. Outlook\Options\Mail narrows it to email composition settings.
Value name and data
Create a DWORD value named DisableSignatures. Set it to 1 to block signature management. Set it to 0 or delete the value to restore normal behaviour.
| Component | Value |
|---|---|
| Key path | HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\Options\Mail |
| Value name | DisableSignatures |
| Value type | DWORD (32-bit) |
| Data to disable | 1 |
| Data to enable | 0 or delete the value |
How to verify the change applied
Open Registry Editor, navigate to the path, and confirm the DisableSignatures value shows 1. Then restart Outlook. Open File > Options > Mail. The Signatures button should be greyed out or missing entirely. If it's still clickable, the policy didn't reach the user profile. Check that the key was created under the correct hive and that no conflicting policy is overriding it.
If your team also sends contracts for signature, test the registry change on one machine first and confirm that signing-request emails still deliver — the policy strips the sender's email signature block, which some teams rely on for branding in those notifications.
Do Not Allow Signatures For E-mail Messages Registry: A Step-by-Step Guide
- Back up the registry or create a System Restore point before making any changes.
- Open Registry Editor (regedit.exe) with an account that has permission to edit HKEY_CURRENT_USER policies.
- Navigate to HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\Options\Mail. Create the missing keys if they do not exist.
- Create a new DWORD (32-bit) Value named DisableSignatures.
- Set its value data to 1 to block signatures, or 0 to allow them.
- Close Registry Editor and restart Outlook so the policy takes effect.
- For fleets, deploy the same key through Group Policy Preferences or your endpoint management tool rather than editing each machine by hand.
How to Disable Email Signatures Using Group Policy
Group Policy is the cleaner path when you're managing more than a handful of users. It writes the same DisableSignatures registry value, but centrally, so you don't touch each machine.
Locating the Outlook administrative template
Download the Office administrative template files (ADMX/ADML) from Microsoft and copy them to your Central Store or local PolicyDefinitions folder. The Outlook policy sits under User Configuration > Policies > Administrative Templates > Microsoft Outlook > Outlook Options > Mail Format.
Enabling the policy
Find Do not allow signatures for e-mail messages. Set it to Enabled. That's the whole step. Group Policy writes DisableSignatures=1 to the registry path covered above, under each user's hive at next refresh.
Applying and testing the GPO
Link the GPO to the OU holding your users. Run gpupdate /force on a test machine, restart Outlook, then open File > Options > Mail. The Signatures button should be greyed out. If it isn't, check gpresult /r to confirm the policy applied.
How to Disable Email Signatures Using Microsoft Intune
Intune works when your machines aren't domain-joined or you've moved past on-prem Group Policy. You get two routes: a Configuration Profile that sets the same registry value, or a PowerShell script that does it directly.
Using Configuration Profiles
Open the Intune admin center and go to Devices > Configuration > Create > New policy. Pick Windows 10 and later, then Settings catalog. Search for "signatures" and you'll find the Outlook policy under Microsoft Outlook 2016 > Outlook Options > Mail Format. Set Do not allow signatures for e-mail messages to Enabled. Assign the profile to a user or device group. It applies at next sync, no reboot needed.
Preparing a PowerShell script
The script route gives you more control over timing and scope. You're writing the registry value directly:
New-Item -Path "HKCU:\Software\Policies\Microsoft\Office\16.0\Outlook\Options\Mail" -Force
Set-ItemProperty -Path "HKCU:\Software\Policies\Microsoft\Office\16.0\Outlook\Options\Mail" -Name "DisableSignatures" -Value 1 -Type DWord
Save it as a .ps1 file. Test it on one machine first by running it manually, then restarting Outlook to confirm the Signatures button greys out.
Deploying the script to users
Go to Devices > Scripts and remediations > Add > Windows PowerShell script. Upload the .ps1, set it to run in the user context (not system, since this writes to HKCU), and assign to your user group. Scripts run every 8 hours by default, so it's slower than a Configuration Profile. Use the profile if you need it applied today.
Platform-Specific Removal: Windows, Mac, Web, and Mobile
The registry and GPO settings stop users from adding or changing signatures going forward. They don't touch signatures already sitting in Outlook profiles. You'll need to remove those manually, and the steps differ by platform.
Outlook on Windows
Open a new message, go to Signature > Signatures, select the signature you want gone, and click Delete. Repeat for each signature in the list. If the Signatures button is greyed out because your policy is already applied, you'll need to temporarily disable the policy, remove the signatures, then re-enable it.
Outlook on Mac
Go to Outlook > Preferences > Signatures. Select the signature on the left, then click the minus button below the list. Mac Outlook stores signatures separately from Windows, so a GPO applied to Windows machines won't touch anything here.
Outlook on the web
Click the gear icon, then View all Outlook settings > Mail > Compose and reply. Select the signature and clear the text box, or delete the signature entry entirely. Web signatures sync through your Microsoft 365 account, so removing one here removes it across browsers.
Outlook mobile apps
Open Settings > Signature in the Outlook app. Clear the text and save. There's no per-account signature management on mobile, just one global signature per app install.
What You Cannot Do After Disabling Email Signatures
The policy blocks users from adding, editing, or removing signatures in Outlook. The Signatures button greys out. Existing signatures stay put until an admin removes them manually.
User-level restrictions
Users can't create new signatures. They can't edit current ones. They can't delete them either. The setting is a full lock, not a partial one.
What still works
Document e-signatures are unaffected. Contracts still get signed. Email still sends normally, just without a signature block.
Common misconceptions
This setting doesn't remove existing signatures. It doesn't touch Outlook on Mac or mobile. And it has nothing to do with legally binding e-signatures on documents.
Email Signatures vs. Document E-Signatures: Why This Setting Doesn't Affect Contract Signing
Email signatures and e-signatures share a word. That's where the overlap ends.
What email signatures are for
An email signature is a text block: your name, title, phone number, maybe a logo. It sits at the bottom of every message you send. It's branding, not consent. Nobody checks it for legal validity. Nobody audits it.
What e-signatures are for
An e-signature is a legal act. When someone signs a contract, they're agreeing to terms. The signature carries a timestamp, an IP address, and an audit trail. Courts treat it as binding. That's why e-signature platforms exist as separate systems.
Why organizations need both managed separately
You can lock down Outlook signatures with a registry key and still run a full contract workflow in parallel. The two don't talk to each other. Disabling one does nothing to the other.
The honest answer: if you're worried this registry setting will stop your team from signing documents, it won't. It can't.
When to Use a Centralized E-Signature Solution Instead
The registry setting handles email signatures. It does nothing for contracts.
Why email signature controls aren't enough for contracts
Contracts need proof: who signed, when, from where. A registry key can't provide that. It only blocks Outlook text blocks.
What a centralized e-signature solution provides
A proper e-signature platform gives you an audit trail, a certificate of completion, and ordered multi-signer routing. You upload a PDF, place signing fields, and send one secure link. The system tracks every signer and delivers the completed document automatically.
How LoreSign fits into your workflow
LoreSign covers the document side while your do not allow signatures for e-mail messages registry policy handles email. You get automated reminders, a public verification page, and watermark-free PDFs on paid tiers. The two controls run in parallel and don't conflict.
Frequently Asked Questions
How do I turn off signatures?
In Outlook, go to File > Options > Mail > Signatures and delete or rename the default signature. To block signatures across an organization on Windows, set the DisableSignatures DWORD to 1 under the Outlook Options\Mail policy key.
How do I disable email signatures in Outlook?
You can disable them per user through Outlook's Signatures dialog, or centrally through the registry policy described above. The registry method is the only one that prevents users from re-enabling signatures themselves.
Are email signatures necessary?
They are a convention, not a legal requirement. Many organizations keep them for branding and contact details, while others disable them to standardize formatting or reduce clutter. Disabling them does not affect the validity of any contract you sign electronically.
How do I get rid of an email signature?
Open Outlook's Signatures dialog, select the signature, and delete it, or clear it from the 'New messages' and 'Replies/forwards' dropdowns. If a policy is enforced, the option will be greyed out and only an administrator can change it.
Does disabling email signatures stop me from signing documents?
No. Email signatures are just text appended to messages. Document and contract e-signatures are handled by a separate signing platform, so signing requests, reminders, and completed PDFs continue to work normally.
What is the difference between a roaming signature and a local signature in Outlook?
A local signature is stored on the individual machine, while a roaming signature is stored in the user's mailbox so it follows them across devices. Roaming signatures are controlled by a separate policy setting from DisableSignatures.
Can users bypass the DisableSignatures registry policy?
When the policy is applied correctly, the Signatures button in Outlook is disabled and users cannot create or edit signatures through the normal interface. They could still type a sign-off manually into the message body, so the policy is a formatting control, not a security boundary.
About LoreSign
LoreSign helps individuals and businesses create, send, sign, and track documents in one place. You can upload a PDF or create an agreement, add the required signing fields, send it to recipients, and automatically receive the completed document once everyone has signed.
