Outlook signature not saving for Google Workspace accounts is a common issue in classic Outlook, where the selected signature keeps reverting back to (none) after restarting Outlook.
This typically happens in environments using Google Workspace Sync for Microsoft Outlook (GWSMO). Microsoft’s roaming signatures feature can interfere with how signatures are assigned and saved, causing Outlook to forget the default selection.
Quick fix: Disable roaming signatures via registry, restart Outlook, and reassign the default signature. In most cases, this resolves the issue immediately.
For businesses that rely on consistent email branding and professional communication, resolving this ensures signatures are automatically applied for new emails and replies. If your team needs help troubleshooting Outlook or Google integrations, Osmicro provides IT support and Google Workspace support.
Quick Summary
- Issue: Outlook signature defaults for a Google Workspace account do not stay saved
- Symptom: New messages and Replies/forwards revert to (none) after Outlook is closed and reopened
- Cause: A known interaction between GWSMO and Microsoft roaming signatures
- Fix: Disable roaming signatures with a registry change, restart Outlook, and reassign the signature defaults
Direct Answer
If Outlook signatures are not saving for a Google Workspace account, disable roaming signatures using the registry, restart Outlook, and reassign the signature defaults. This resolves most cases immediately.
Common Signs of This Issue
You may be dealing with this issue if you notice any of the following:
- A signature is created correctly in Outlook
- The correct Google Workspace account is selected in the signature window
- The signature can be chosen manually
- After restarting Outlook, New messages and Replies/forwards return to (none)
- Users need to manually insert their signature each time
This commonly appears in classic Outlook where the mailbox is connected using Google Workspace Sync for Microsoft Outlook.
Why Outlook Signature Keeps Resetting to None
Microsoft introduced roaming Outlook settings, which can store certain Outlook preferences in the cloud. In some Google Workspace Sync environments, this interferes with signature assignment and causes the selected default signature to fail to persist.
In practical terms, the signature itself still exists and remains editable, but Outlook does not retain which signature should be used by default for new emails and replies.
Osmicro Resolution Process
Our standard process is:
- Confirm the user is using classic Outlook
- Confirm the affected account is the Google Workspace mailbox
- Confirm the signature itself exists
- Check whether the signature defaults keep reverting to (none)
- Apply the registry fix
- Restart Outlook
- Reassign the signature defaults and test persistence
Step 1: Confirm the Problem
Open Outlook and go to:
File > Options > Mail > Signatures
From there:
- Confirm the correct E-mail account is selected
- Check whether New messages and Replies/forwards are set to a signature or to (none)
If the user sets the dropdowns correctly, clicks OK, and after reopening Outlook they return to (none), this is the issue covered by this guide.
Step 2: Apply the Registry Fix
Disable the roaming signatures behaviour by running the following command in Command Prompt:
reg add HKCU\Software\Microsoft\Office\16.0\Outlook\Setup /v DisableRoamingSignaturesTemporaryToggle /t REG_DWORD /d 1 /fWhat this does
This creates the following registry value under the current user profile:
- Path:
HKCU\Software\Microsoft\Office\16.0\Outlook\Setup - Value:
DisableRoamingSignaturesTemporaryToggle - Type:
REG_DWORD - Data:
1
This disables the roaming signatures behaviour that causes the default signature settings not to save.
Step 3: Restart Outlook
After applying the registry value:
- Fully close Outlook
- Reopen Outlook
- Return to the signature settings window
Step 4: Reassign the Default Signature
Go back to:
File > Options > Mail > Signatures
Then:
- Select the correct Google Workspace account
- Set New messages to the required signature
- Set Replies/forwards to the required signature
- Click OK
Now close Outlook again and reopen it to test whether the selections remain saved.
Step 5: Test the Result
Create a brand-new email from the affected account and confirm:
- The signature inserts automatically for new messages
- The signature remains assigned after restarting Outlook
- Replies and forwards use the correct signature if configured
If the signature remains selected after restarting Outlook, the fix has worked.
Important Notes
This fix is most relevant for Google Workspace Sync for Microsoft Outlook
This issue is most commonly seen where Outlook is using GWSMO for the Google Workspace mailbox.
This is a per-user registry setting
Because the registry path is under HKEY_CURRENT_USER, the change applies only to the currently logged-in Windows user. If multiple users sign into the same PC, the setting may need to be applied for each profile.
The signature content may still exist even if the defaults are not saving
In many cases, the signature itself is still present and editable, but Outlook fails to retain which signature should be used by default.
If the Fix Does Not Work
If the issue continues after applying the registry change, additional troubleshooting may be needed:
- Confirm Outlook is classic Outlook
- Confirm the mailbox is using Google Workspace Sync for Microsoft Outlook
- Repair or recreate the Outlook or GWSMO profile
- Check for Outlook or GWSMO corruption
Final Thoughts
This is a small issue that can create unnecessary frustration for staff, especially where signatures are required for branding and consistency.
If a Google Workspace account in classic Outlook keeps losing its default signature selections, disabling roaming signatures is a simple and effective fix.
At Osmicro, we regularly troubleshoot Outlook, Microsoft 365, and Google Workspace integration issues like this as part of keeping business communication stable, consistent, and professional.