Microsoft 36514 min read

Outlook Roaming Signatures: What They Are and How to Fix Them

Microsoft introduced roaming signatures to sync your email signature across devices via the cloud. Sounds great in theory. In practice, it causes more problems than it solves — signatures disappearing, duplicating, not updating, or reverting to old versions. This guide explains exactly how the feature works, what goes wrong, and how to fix it.

By the NeatStamp Team · Published March 2026 · 14 min read

Jump to the section you need

What are Outlook roaming signatures?

Roaming signatures is a Microsoft 365 feature that moves your email signature storage from your local machine to Exchange Online — Microsoft’s cloud email infrastructure. The feature rolled out between 2022 and 2023 for Microsoft 365 Business and Enterprise subscribers.

Before roaming signatures existed, Outlook stored your signature as three files on your local machine:

%APPDATA%\Microsoft\Signatures\MySignature.htm %APPDATA%\Microsoft\Signatures\MySignature.rtf %APPDATA%\Microsoft\Signatures\MySignature.txt

Those files lived on one machine. If you logged into Outlook on a second laptop, you had to recreate the signature there too. Roaming signatures were supposed to solve that by storing the signature in Exchange Online instead, so any device with your Microsoft 365 account could pull it down automatically.

The problem is that “any device” means something very specific to Microsoft. It means New Outlook and Outlook Web Access. It does not mean classic Outlook — the traditional Windows desktop application that most business users still run every day.

That gap between what the feature promises and what it actually supports is where 90% of the confusion and frustration comes from. If your organization has a mix of classic Outlook users and New Outlook users — which most do right now — roaming signatures will cause inconsistent behavior for everyone.

How roaming signatures work

When roaming signatures are enabled for your Microsoft 365 tenant, Outlook changes where it reads and writes signature data.

Instead of saving to the local %APPDATA%\Microsoft\Signatures folder, New Outlook and OWA write signatures directly into Exchange Online using the Microsoft Graph API. The signature data is stored in your mailbox settings in the cloud, under your account properties in Exchange.

When you open New Outlook on a different device, it authenticates with your Microsoft 365 account, fetches your mailbox settings including the stored signature data, and presents it in your compose window. From a user’s perspective, the signature just appears — no manual setup.

Administrators can control roaming signatures at the tenant level or per-user level using Exchange Online PowerShell. The main setting is a boolean property called RoamingSignaturesEnabledon the organization config. When it’s set to $true, the cloud storage is active. When it’s $false, Outlook falls back to local file storage.

Important distinction

Roaming signatures are a tenant-wide setting, not a per-device setting. You can’t turn them on for some users and off for others without using per-mailbox overrides. This matters a lot if your organization has a mix of tech-savvy and non-technical users.

The sync itself happens asynchronously. Microsoft doesn’t guarantee a specific sync window — in practice, updates can take anywhere from minutes to several hours to propagate. For a feature designed to keep signatures consistent, that delay is a significant limitation.

The problems with roaming signatures

Here are the 6 most common problems that roaming signatures cause — and why each one happens.

1

Only works in New Outlook and OWA — not classic Outlook

Classic Outlook (the traditional Windows .exe application) reads signatures from the local file system, period. It does not talk to Exchange Online to fetch roaming signature data. So if your organization enables roaming signatures and some users are still on classic Outlook, those users will see either their old local signature or no signature at all — depending on what’s in their local Signatures folder.

This isn’t a minor edge case. As of early 2026, a large proportion of business users are still on classic Outlook. Microsoft is pushing the New Outlook transition, but many organizations haven’t made the switch — and some are actively resisting it due to missing features in the new version.

2

Signatures sync slowly — and sometimes not at all

When you update your signature in New Outlook on one device, the change doesn’t immediately appear on your other devices. Microsoft routes the change through Exchange Online, and the sync can take hours.

In some cases, the sync never completes at all — especially when there are conflicts between the local and cloud versions (see problem 3). Users end up with different signatures on different devices, which defeats the entire purpose of the feature.

3

Conflicts between local and cloud versions

If you edited your signature locally on classic Outlook, then your organization enables roaming signatures, you now have two conflicting versions: the local file and whatever is (or isn’t) in Exchange Online. New Outlook will show the cloud version. Classic Outlook will show the local version. Neither will be automatically reconciled.

The same conflict can occur if you edit the signature on two different devices before the sync completes. Whichever version was written last to Exchange Online usually “wins,” but that’s not always predictable.

4

IT admins can’t manage roaming signatures via Group Policy

Group Policy was the standard way IT teams managed Outlook signatures centrally. They could push a signature template to every user’s machine via GPO, and it would appear automatically in classic Outlook. That workflow doesn’t work for roaming signatures.

Roaming signatures are controlled through Exchange Online PowerShell or the Microsoft 365 Admin Center — not Group Policy. IT teams have to learn a completely different management system, and many signature deployment tools built on GPO don’t support the roaming model at all.

5

Signature disappears when switching between classic and New Outlook

This is the most disorienting experience for users. Someone sets up their signature in classic Outlook, everything looks fine. They open New Outlook one day (maybe for a specific feature, or because IT pushed an update) and their signature is gone.

It hasn’t actually been deleted — it’s still in the local Signatures folder. But New Outlook looks in Exchange Online, where there’s nothing. The user then sets up the signature in New Outlook, switches back to classic, and the signature they see there is the old local one — not the updated cloud version. Both clients think they’re right, and neither is talking to the other.

6

Only 1 signature in some configurations

Classic Outlook supports multiple named signatures — you can create 10 different signatures and manually select which to use when composing. Some roaming signature configurations limit this to 1 active signature per mailbox, or only expose 1 signature in the New Outlook compose UI.

For users who legitimately need different signatures for different contexts — formal vs. casual, different languages, project-specific signatures — this is a real functional regression from how classic Outlook worked.

How to check if roaming signatures are enabled

You need Exchange admin access to run these commands. Connect to Exchange Online PowerShell first, then run:

Check the tenant-wide setting

Get-OrganizationConfig | Select RoamingSignaturesEnabled

This returns either True or False. If the property doesn’t exist on your tenant (older Exchange Online configurations), the feature hasn’t been provisioned and is effectively disabled.

Check a specific user’s setting

Get-MailboxMessageConfiguration -Identity [email protected] | Select SignatureHtml, SignatureText

This shows you what signature content is stored in Exchange Online for that user. If both fields are empty, the user hasn’t set up a roaming signature yet — or they’re using classic Outlook and never touched New Outlook’s signature settings.

Check without admin access (user self-check)

If you’re a regular user without PowerShell access, the easiest way to check is to open Outlook Web Access at outlook.office.com, go to Settings → Mail → Compose and reply, and look at the signature section. If there’s a signature there that you never set up on OWA, your admin has pushed one via Exchange — or roaming signatures picked it up from your New Outlook session.

If the signature in OWA is different from what you see in classic Outlook, that’s a sign that roaming signatures are causing a split — two separate versions living in two separate places. See also: full Outlook signature troubleshooting guide for diagnosing other causes.

How to disable roaming signatures

Disabling roaming signatures at the organization level is a single PowerShell command. You need Exchange Administrator or Global Administrator privileges.

Disable for the entire tenant

# Connect to Exchange Online first
Connect-ExchangeOnline -UserPrincipalName [email protected]

# Disable roaming signatures
Set-OrganizationConfig -RoamingSignaturesEnabled $false

# Verify the change
Get-OrganizationConfig | Select RoamingSignaturesEnabled

After running this, Outlook will fall back to reading signatures from the local %APPDATA%\Microsoft\Signatures folder — the same behavior as before roaming signatures existed. Users who had set up signatures in New Outlook or OWA will need to set them up again in classic Outlook.

Before you disable

Tell your users in advance. When you flip this setting, anyone who was relying on New Outlook or OWA to show their signature will lose it. Give them time to export their signature HTML from OWA (Settings → Mail → Compose and reply → copy the signature text) before you make the change.

Disable for a specific user only

If you want to test the change on one user before rolling it out, or if you need per-user control, you can override at the mailbox level. However, note that per-user overrides for roaming signatures require setting a mailbox-level property, and Microsoft’s documentation on this is thin. The most reliable approach is the tenant-wide setting.

For most organizations, the cleanest solution is to disable roaming signatures tenant-wide and use a consistent distribution method instead — which we cover in the best practices section below.

When to keep roaming signatures enabled vs. disabled

There are situations where roaming signatures actually work well. And there are situations where they’re a guaranteed headache. Here’s a straightforward breakdown:

Keep roaming signatures ON if:

  • +Your entire organization has migrated to New Outlook
  • +All users primarily access email via OWA/browser
  • +Nobody in the org uses classic Outlook desktop
  • +You don't need Group Policy-based signature management
  • +Users work on many different devices and manual setup would be a burden

Disable roaming signatures if:

  • −Any users are still on classic Outlook desktop
  • −You manage signatures centrally via Group Policy
  • −Your org uses a third-party signature management tool
  • −You've seen reports of signatures disappearing or conflicting
  • −Users need multiple named signatures to switch between
  • −You need predictable, immediate signature updates

For most organizations in 2026, the honest answer is: disable roaming signatures until the Classic-to-New Outlook migration is fully complete. The feature adds complexity without clear benefits for mixed-client environments, and the sync delays alone make it unsuitable for anyone who needs reliable signature behavior.

Best practices for teams using Microsoft 365

Whether you keep roaming signatures enabled or disabled, here’s what actually works well for teams managing signatures across Microsoft 365.

1

Pick one Outlook client per user and stick with it

The majority of signature problems come from users who bounce between classic Outlook and New Outlook. If you're in transition, pick one for each user and make sure their signature is set up correctly in that client. Mixing clients on the same mailbox is where conflicts multiply.

2

Use HTML-based signatures, not plain text

Plain text signatures work everywhere but can't include logos, social icons, or formatted contact details. HTML signatures look professional and work reliably in both classic Outlook and New Outlook as long as you use table-based layout with inline styles — not flexbox or CSS classes. For a full Outlook-compatible signature, see our guide to Outlook 365 signatures.

3

Host signature images externally

Never embed images as base64 in your signature HTML. Classic Outlook converts base64 images to file attachments, which is confusing for recipients and makes emails look unprofessional. Host images on your company website or a CDN and reference them by absolute https:// URL.

4

Document the signature setup process for new hires

"My signature is gone" is one of the top IT helpdesk tickets in any organization that uses Outlook. Write a one-page setup guide and put it in your employee onboarding docs. Include the Outlook client version, the steps to add the signature, and where to get the signature HTML from.

5

Test on mobile too

The Outlook mobile app on iOS and Android has its own signature settings, separate from both classic Outlook and New Outlook desktop. If your team sends emails from their phones, make sure they've set up a consistent mobile signature. The Outlook mobile signature guide covers this separately.

6

If you manage signatures centrally, use PowerShell or a dedicated tool

Group Policy works for classic Outlook signatures but not roaming signatures. For organization-wide signature management across Microsoft 365, you need either Exchange Online PowerShell scripts, a server-side signature injection tool (like those covered in the company-wide management guide), or a per-user distribution method that doesn't depend on GPO.

For company-wide signature rollouts across Microsoft 365, the company-wide email signature management guide covers your options in detail — from free PowerShell scripts to enterprise signature management platforms, with real cost comparisons. If you also need Teams signatures to match, see the Microsoft Teams signature guide.

The NeatStamp approach: no roaming required

NeatStamp doesn’t use roaming signatures at all. Your signature is designed and saved in NeatStamp — our free online editor generates clean, Outlook-compatible HTML that you copy once and paste into any email client.

That approach bypasses the entire roaming signatures problem:

  • No sync delays — you paste the HTML once and it works immediately
  • Works in classic Outlook, New Outlook, OWA, Gmail, Apple Mail, and Outlook mobile
  • No Exchange Online dependency — the signature is just HTML in your email client
  • No conflicts between local and cloud versions — there's only one version, and it's in NeatStamp
  • Easy to update — change it in NeatStamp, copy the new HTML, paste to replace the old signature

For individual users, this means you design your signature in NeatStamp, follow the Outlook signature setup guide, and you’re done. No IT ticket, no PowerShell, no waiting for sync. It takes about 5 minutes.

For teams, you can build a signature template in NeatStamp, send the setup instructions to everyone, and each person pastes it into their own Outlook. It’s simpler than any centralized management solution — no infrastructure to maintain, no Exchange admin needed.

What about the Outlook 365 signature specifically?

NeatStamp generates table-based HTML with inline styles that renders correctly in every version of Outlook — 2016, 2019, 2021, and 365. The same HTML file works in classic Outlook and New Outlook. You don’t need to maintain separate signatures for separate clients.

If your signature is showing the wrong content or has disappeared, the fastest fix is to rebuild it in NeatStamp and paste the fresh HTML into Outlook. Check the email signature not showing in Outlook guide if you’re having trouble getting the pasted signature to appear. For signatures that disappear repeatedly, see why Outlook signatures disappear and how to stop it.

Frequently asked questions

What are Outlook roaming signatures?

Roaming signatures is a Microsoft 365 feature that stores your Outlook email signature in the cloud (Exchange Online) instead of on your local machine. The idea is that your signature follows you to any device where you log in — New Outlook on a work laptop, Outlook Web Access, etc. It was introduced in 2022-2023 for Microsoft 365 Business subscribers.

Do roaming signatures work in classic Outlook?

No. Roaming signatures only work in New Outlook (the web-based version rolling out since 2024) and Outlook Web Access (OWA). Classic Outlook — the traditional .exe desktop app — reads signatures from the local %APPDATA%\Microsoft\Signatures folder, not from Exchange Online. This mismatch is the root cause of most roaming signature problems.

How do I check if roaming signatures are enabled in my organization?

Run this PowerShell command as an Exchange admin: Get-OrganizationConfig | Select RoamingSignaturesEnabled. If it returns True, roaming signatures are active for your tenant. If False or the property doesn't exist, they're off. You can also check per-user with Get-MailboxMessageConfiguration -Identity [email protected].

How do I disable roaming signatures for my organization?

Run: Set-OrganizationConfig -RoamingSignaturesEnabled $false in Exchange Online PowerShell. This disables roaming signatures for the entire tenant. Users will then manage signatures locally in classic Outlook again. Note: you need Exchange Administrator or Global Administrator privileges to run this command.

Why does my signature disappear when I switch between classic and new Outlook?

Because they use separate signature storage systems. Classic Outlook reads from %APPDATA%\Microsoft\Signatures on your local machine. New Outlook reads from Exchange Online. When you switch clients, you're looking at a different signature store. You need to set up the signature separately in each client, or disable roaming signatures entirely and manage everything locally.

How long does it take for roaming signatures to sync?

Microsoft doesn't publish a guaranteed sync time. In practice, updates can take anywhere from a few minutes to several hours to propagate across devices. This makes roaming signatures unreliable for anything time-sensitive — like updating your signature before an important email goes out. IT admins and users consistently report sync delays as the biggest pain point with this feature.

Can IT admins control roaming signatures with Group Policy?

Not directly. Traditional Group Policy works against the local registry and file system — which is how classic Outlook signatures work. Roaming signatures are stored in Exchange Online, so they're managed through Exchange PowerShell or Microsoft 365 Admin Center, not Group Policy. This breaks many existing IT workflows that relied on GPO-based signature management.

Is there a way to manage signatures centrally without dealing with roaming signatures?

Yes. The simplest approach is to disable roaming signatures and distribute a pre-built signature HTML to all users, which they paste into classic Outlook manually. For teams, NeatStamp lets each person build their own signature with consistent branding — no server-side infrastructure needed. You create it once in NeatStamp, copy the HTML, paste into Outlook, done. It works the same way on every device.

More resources

Outlook-compatible signature formatsEmail signature templatesNeatStamp Pro for teamsFree signature editor

Skip the roaming signatures headache

Build your signature in NeatStamp and paste the HTML into any version of Outlook. No Exchange admin needed, no sync delays, no conflicts. Free, no account required. Takes about 5 minutes.

Create My Signature — Free