An external email warning in Outlook tells people, before they click or reply, that a message came from outside your company. It is one of the most affordable defenses against phishing. Microsoft 365 admins can set it up in just 15 minutes.
This guide walks you through a step by step process of how you add, edit, and remove Outlook external email warning. Moreover, each section ends with a check so you know the step worked before you move on.
What is the external email warning in Outlook, and why does it show up?
When a message arrives from a sender outside your organization, Microsoft 365 can mark it in one of two ways:
- The External tag. Outlook shows a small “External” label on the message, along with a way to see the sender’s real email address. Admins turn it on with one PowerShell cmdlet.
- A custom warning. A mail flow rule inserts a banner at the top of the message body, or adds a prefix such as [EXTERNAL] to the subject line. You write the text and decide who gets it.
Both exist for the same reason. Attackers often impersonate executives, vendors, or colleagues, and a visible “this came from outside” signal gives employees a moment to stop and check.
Two things to keep in mind:
- A warning is not a spam filter. It does not block anything. It only labels mail, so keep your anti-phishing and anti-spam policies on as well.
- Users cannot remove it themselves. If you are an end user who wants the banner gone, only your IT admin can change it. Send them this article.
Native External tag vs mail flow rule: which should you use?
Choose the method before you build anything. Picking the wrong one is the most common reason admins redo this work.
| Feature | Native External tag | Mail flow rule banner |
|---|---|---|
| What users see | A small “External” label in Outlook | A text banner inside the email body (and/or a subject prefix) |
| Custom wording | No | Yes, including HTML styling |
| Works in non-Outlook mail apps | No, Outlook only | Yes, because the banner is part of the message |
| Changes the message itself | No | Yes |
| Affects conversation threading | No | Subject prefix does; body banner does not |
| Exceptions for trusted senders | Allow list (addresses and domains) | Rule exceptions (very flexible) |
| Setup effort | One cmdlet | A rule with conditions, exceptions, and testing |
| Time before users see it | 24 to 48 hours | Usually minutes after the rule is enabled |
Simple decision rule:
- Want the least effort and no changes to message content? Use the native tag.
- Need custom wording, your own colors, a legal notice, or coverage for people using non-Outlook apps? Use a mail flow rule banner.
Note: Do not turn on both. Users then see an External label and a banner on the same message. That is allowed, but do it on purpose, not by accident.
Before you start: permissions and prerequisites
Run through this checklist first. It prevents most of the errors people hit later.
- Check your role. You need Organization Management, or a role group that includes the Transport Rules role. In the Exchange Admin Center, go to Roles > Admin roles to confirm you are in the right group.
- Tell your team before you switch anything on. Mail flow rules and the native tag affect the whole organization. A short heads-up avoids a flood of “is this a phishing attack?” tickets.
Check: Connect-ExchangeOnline finishes without an error, and Get-AcceptedDomain lists every domain your company sends mail from.
Method 1: Turn on the native External tag
This is the fastest option. Open the PowerShell and follow the steps below:
Step 1. Enable the tag.
Set-ExternalInOutlook -Enabled $true
Step 2. Confirm the setting.
Get-ExternalInOutlook
The output should show Enabled as True.
Step 3. Wait.
After you enable it, it can take 24 to 48 hours before users see the External label. Do not troubleshoot before that window passes.
Step 4. Exclude trusted senders (optional).
Use the allow list for partners, vendors, or other domains your staff deal with every day, so the tag keeps its meaning.
Step 5. Test.
Send a message from a personal account (for example Gmail) to a test mailbox in your tenant. Open it in Outlook on Windows, Outlook on the web, and Outlook mobile. You should see the External label.
To turn it off, run the following command:
Set-ExternalInOutlook -Enabled $false
The label can take up to 48 hours to disappear everywhere, just as it did to appear.
Method 2: Add a custom external email warning with a mail flow rule
Use this method when you want your own wording or banner. We will apply the warning using the Exchange Admin Center.
- Sign in to the Exchange Admin Center at admin.exchange.microsoft.com.
- Go to Mail flow > Rules, select Add a rule, then choose Create a new rule.
- Give the rule a clear name, such as External sender warning.
- Under Apply this rule if, choose The sender, then is external/internal, then select Outside the organization and save.
- Select the + icon to add a second condition. Choose The recipient, then is external/internal, then select Inside the organization and save. This stops the banner being added to mail you send out.
- Under Do the following, choose Apply a disclaimer to the message, then prepend a disclaimer.
- Select Enter text and paste your banner. HTML works here (a ready-made template is in the next section). Save it.
- Select the fallback action link and choose Wrap. This matters for signed or encrypted messages, which cannot be edited without breaking them. Wrap places the original inside a new message that carries your warning, so the warning is never silently skipped.
- Select Next. For Rule mode, choose Test without Policy Tips if you want to test first, or Enforce to go live. Leave Stop processing more rules unchecked unless you have a reason to use it.
- Select Next, review the summary, then select Finish.
- Back on the Rules page, select your new rule. Rules created in the admin center are usually Disabled by default, so click the Enabled toggle to turn it on.
Check: The rule’s status turns from Disabled to Enabled. It can take a few minutes, and sometimes up to about 30, for the rule to start working.
Common mistake: Choosing the test mode and then wondering why no banner appears. Test mode logs matches but does not add the banner. Switch to Enforce when you are ready.
How to test the warning
Do not skip this. Test before you announce anything to the company.
- Send a message from a personal account (such as Gmail) to a test mailbox in your tenant. Expect a banner (or tag).
- Send a message from one internal mailbox to another. Expect no banner.
- Reply from the test mailbox to the external message. Check the reply the external person receives. It should have no warning because it is not going to your users.
- Open the message in Outlook on Windows, Outlook on the web, and Outlook mobile.
- If anything looks wrong, go straight to the troubleshooting section below.
Customize the warning without annoying users: exceptions, priority, and testing
A warning that fires on every message from every trusted partner gets ignored. Fix that with exceptions.
Skip trusted domains
To skip adding the Outlook external email warning tag or banner on your trusted domains, use the following command.
Set-TransportRule -Identity "External sender warning" -ExceptIfSenderDomainIs "partner.com","trustedvendor.com"
Note: this replaces the existing list of excepted domains with exactly what you provide. If you already have exceptions, include all of them in the same command.
Set the rule priority
Rules run in order, and the lowest number runs first. If another rule stops processing before yours runs, your banner never appears.
Set-TransportRule -Identity "External sender warning" -Priority 0
A warning about duplicate banners on replies: When an external person replies on an old thread, the quoted text can include your earlier banner, and your rule adds a new one on top. It is tempting to add an exception that skips messages containing your banner text. Avoid this, because an attacker can copy your banner wording into a phishing email and your rule would then skip it. Either live with the occasional duplicate or use the native External tag, which does not alter the message.
How to edit the external email warning
When modifying an existing email warning, the changes will only apply to new messages. Messages already delivered keep their old banner.
In the Exchange Admin Center
- Go to Mail flow > Rules and select the rule.
- Choose Edit rule conditions to change who gets the warning, or Edit rule settings to change mode, priority, or the schedule.
- To change the wording, edit the disclaimer text in the rule’s actions, then save.
Check: send a fresh test message from an external account and confirm the new wording appears. Allow a few minutes for the change to take effect.
How to disable or remove the external email warning
Disable the warning if you might want it back. Deleting removes the rule and its settings permanently.
Disable in the Exchange Admin Center
- Go to Mail flow > Rules and select the rule.
- Switch the Enabled toggle to off.
- Wait for the status to read Disabled.
Disable in PowerShell
Disable-TransportRule -Identity "warning-name" -Confirm:$false
Delete in the Exchange Admin Center
- Go to Mail flow > Rules and select the rule.
- Select Delete, then confirm.
Delete in PowerShell
Remove-TransportRule -Identity "warning-name" -Confirm:$false
Turn off the native tag
Set-ExternalInOutlook -Enabled $false
Check: send a test message from an external account. After a few minutes (up to 48 hours for the native tag), no warning should appear. If one still does, you may have two warning methods running.
Run Get-TransportRule | Format-Table Name,State,Priority and Get-ExternalInOutlook to see what is still active.
Troubleshooting: external email warning not showing, or showing twice
| What you see | Likely cause | What to do |
|---|---|---|
| No banner after creating the rule | Rule is still disabled, or still in test mode | Enable the rule and set the mode to Enforce |
| Banner missing, rule is enabled | Another rule with a lower priority number stops processing first | Move your rule to priority 0, or review the rules that run before it |
| Banner missing a few minutes after enabling | Change is still spreading | Wait up to about 30 minutes and test again |
| Native External tag not visible | Not enough time passed, unsupported Outlook version, or sender is on the allow list | Wait 24 to 48 hours, confirm with Get-ExternalInOutlook, and update Outlook |
| Internal mail is flagged as external | A domain is missing from accepted domains, or a third-party service sends as your domain | Check Get-AcceptedDomain, and make sure those services send through a connector |
| Banner and External label both appear | Both methods are on | Decide on one method and turn the other off |
| Two banners on one message | Reply on an old thread, or two overlapping rules | Check Get-TransportRule for duplicates, and read the note on duplicates above |
| Banner shows as raw HTML code | Text was entered as plain text, or the HTML is malformed | Re-enter it as HTML and keep tags simple and closed |
New-TransportRule says the rule already exists |
A rule with that name is already in the tenant | Pick a different name, or edit the existing one with Set-TransportRule |
| “You don’t have permission” error | Missing role | Ask a Global Admin to add you to Organization Management |
| Cmdlet not recognized | Module not installed or you are not connected | Re-run Install-Module ExchangeOnlineManagement and Connect-ExchangeOnline |
| Banner missing on an encrypted or signed message | Fallback action is not set to Wrap | Edit the rule and set the fallback action to Wrap |
Best practices for external sender warnings
- Pick one primary method. One clear signal beats two overlapping ones.
- Pilot first. Start with the IT team or one department, then expand.
- Announce it. Tell staff what the warning means and what to do when they see it.
- Keep exceptions small. Review the trusted-domain list every few months. Every domain you exempt is a domain an attacker may try to imitate.
- Pair it with real protection. Turn on anti-phishing policies in Microsoft Defender for Office 365, and consider the first contact safety tip, which warns users when they get mail from someone they rarely hear from. Settings sit in the Defender portal under the anti-phishing policy, and menu labels change, so check the current wording.
- Review the rule on a schedule. Check that it is still enabled and still ordered correctly after other admins add rules.
Conclusion
Managing the external email warning in Outlook comes down to one choice and a handful of safe steps:
- Check your role, your connection, and your accepted domains.
- Choose the native External tag for simplicity, or a mail flow rule banner for control.
- Create it, keep it short, add exceptions for trusted senders, and test with an external account.
- To edit, change the rule or allow list. To remove, disable first and delete only when you are sure.
Frequently asked questions
Can users remove the external email warning themselves?
No. The warning is added by Microsoft 365 at the organization level. Only an admin with the right role can change or remove it.
Why is a legitimate email flagged as external?
The sender’s domain is not one of your accepted domains. This happens with partners, vendors, and sometimes with your own tools, such as a marketing platform that sends mail as your domain. Add trusted domains to the allow list or rule exceptions, and use a connector for services that send as you.
Does the external email warning work in Outlook on the web and mobile?
The native External tag is built for Outlook, including Outlook on the web, Mac, iOS, and Android, as long as the app is a supported version. A banner added by a mail flow rule is part of the message, so it shows in any email app.
Can I exclude certain domains or senders?
Yes. Use the allow list for the native tag, or the -ExceptIfSenderDomainIs setting on a mail flow rule.
Which is better, the native tag or a mail flow rule?
Use the native tag for a simple, no-maintenance label that does not change messages. Use a mail flow rule when you need custom wording, styling, or coverage for non-Outlook apps.
Does the external email warning stop phishing?
It helps people notice risky mail, but it does not block anything. Keep anti-phishing and anti-spam protection turned on.
How do I add “External” to the subject line?
Create a mail flow rule with the Prepend the subject of the message with action (-PrependSubject in PowerShell). Read the downsides in Method 2 first, since subject changes can cause duplicate tags and break conversation threading.