How to Manage and Disable Outlook Roaming Signatures in Windows 11 Using PowerShell

In Microsoft 365 and Microsoft Outlook for Windows, user email signatures historically resided exclusively on the local client PC inside the file system path %APPDATA%\Microsoft\Signatures. To provide a seamless experience across multiple desktop devices and Outlook on the web, Microsoft introduced Outlook Roaming Signatures. Under this architecture, Outlook automatically synchronises signature definitions directly to the user’s cloud mailbox within Exchange Online. While beneficial for individual end users, Roaming Signatures creates critical operational disruptions in corporate environments: it overrides local signature injection scripts, bypasses centralized third-party email signature tools (such as Exclaimer, CodeTwo, or WiseStamp), and produces duplicate disclaimers. By leveraging PowerShell and Group Policy registry configurations, IT administrators can audit, manage, and disable Outlook roaming signatures across Windows 11 enterprise fleets.

Understanding How Roaming Signatures Operate

When an updated Click-to-Run installation of Microsoft 365 Apps connects to an Exchange Online mailbox, the client queries mailbox settings to determine whether cloud signature roaming is active:

  • Cloud Synchronization: Outlook creates and updates signature records in the UserConfiguration\RoamingDictionary MAPI table of the user’s Exchange Online mailbox.
  • Local Signature Bypass: Rather than reading HTML, RTF, or plain text templates from the traditional local Signatures folder on disk, Outlook prioritizes cloud-synchronized signatures.
  • Third-Party Conflicts: Centralized signature tools that push standard corporate disclaimers to local disk profiles are effectively rendered invisible, causing staff to send unbranded emails or mix inconsistent legal disclosures.

Auditing Roaming Signatures Configuration in the Registry

On Windows 11, the behavior of Outlook Roaming Signatures is governed by client-side policy keys under the Microsoft Office registry tree. Open an elevated PowerShell session to check the active policy status.

To inspect whether signature roaming overrides are currently applied:

$OutlookPolicyPath = "HKCU:\Software\Microsoft\Office\16.0\Outlook\Setup"

if (Test-Path $OutlookPolicyPath) {
    Get-ItemProperty -Path $OutlookPolicyPath |
        Select-Object DisableRoamingSignaturesTemporaryToggle -ErrorAction SilentlyContinue
} else {
    Write-Host "Outlook Setup registry path not found." -ForegroundColor Yellow
}

If the DisableRoamingSignaturesTemporaryToggle DWORD value is missing or set to 0, Outlook Roaming Signatures is active by default.

Disabling Roaming Signatures for the Current User via PowerShell

To disable cloud roaming signatures on an individual workstation so that Outlook reverts to using classic local signature files stored in %APPDATA%\Microsoft\Signatures:

$UserPolicyPath = "HKCU:\Software\Microsoft\Office\16.0\Outlook\Setup"

# Ensure registry key exists
if (!(Test-Path $UserPolicyPath)) {
    New-Item -Path $UserPolicyPath -Force | Out-Null
}

# Set the temporary toggle to 1 (Disabled)
Set-ItemProperty -Path $UserPolicyPath `
    -Name "DisableRoamingSignaturesTemporaryToggle" `
    -Value 1 `
    -Type DWord

Write-Host "Outlook Roaming Signatures disabled successfully for current user." -ForegroundColor Green

After applying the key, restart Microsoft Outlook. Outlook will immediately resume reading and writing signatures from the local disk repository.

Enforcing Fleet-Wide Roaming Signature Lockdown via Machine Policy

In enterprise managed environments, administrators should enforce signature settings across all users of a machine rather than relying on per-user profiles. This ensures roaming signatures remain disabled regardless of who logs into the Windows 11 PC.

To apply a fleet-wide policy under HKEY_LOCAL_MACHINE:

$MachinePolicyPath = "HKLM:\SOFTWARE\Policies\Microsoft\Office\16.0\Outlook\Setup"

# Create policy container if not present
if (!(Test-Path $MachinePolicyPath)) {
    New-Item -Path $MachinePolicyPath -Force | Out-Null
}

# Enforce signature roaming lockdown across all users
Set-ItemProperty -Path $MachinePolicyPath `
    -Name "DisableRoamingSignaturesTemporaryToggle" `
    -Value 1 `
    -Type DWord

Write-Host "Machine-wide Roaming Signatures policy enforced successfully." -ForegroundColor Green

Managing Roaming Signatures via Exchange Online PowerShell

In addition to client-side registry toggles, administrators managing Microsoft 365 tenants can inspect and govern cloud signature features using the Exchange Online PowerShell module.

To connect to Exchange Online:

Connect-ExchangeOnline -UserPrincipalName [email protected]

To inspect mailbox signature settings for a specific user:

Get-MailboxMessageConfiguration -Identity "[email protected]" |
    Select-Object Identity, AutoAddSignature, AutoAddSignatureOnReply, SignatureHtml

To update an employee’s server-side signature directly from administrative PowerShell:

$SignatureContent = @"
<p><strong>John Doe</strong><br>
Senior Infrastructure Engineer | Example Corp<br>
Email: [email protected]</p>
"@

Set-MailboxMessageConfiguration -Identity "[email protected]" `
    -AutoAddSignature $true `
    -AutoAddSignatureOnReply $true `
    -SignatureHtml $SignatureContent

Re-enabling Roaming Signatures

If your organization decides to transition to native cloud signature roaming in the future, remove the toggle key to restore default synchronisation:

# Remove the policy override from user registry
Remove-ItemProperty -Path "HKCU:\Software\Microsoft\Office\16.0\Outlook\Setup" `
    -Name "DisableRoamingSignaturesTemporaryToggle" -ErrorAction SilentlyContinue

# Remove the policy override from machine policy
Remove-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Office\16.0\Outlook\Setup" `
    -Name "DisableRoamingSignaturesTemporaryToggle" -ErrorAction SilentlyContinue

Write-Host "Outlook Roaming Signatures restored to default behavior." -ForegroundColor Cyan

Managing Outlook roaming signatures via PowerShell guarantees that enterprise branding policies, automated disclaimer scripts, and third-party compliance tools maintain full control over outgoing email communications on Windows 11.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.