Outlook "Promotions" Tag in Microsoft 365: What It Means for Your Newsletters and Notifications
Short answer: Since late July 2026 Microsoft 365 tags bulk promotional mail as "Promotions" in every tenant, whatever its complaint level; the rollout should finish by the end of October. Admins can also move it to a Promotions folder. Keep transactional mail separate, authenticated and easy to unsubscribe from.
| Who | Microsoft |
|---|---|
| Status | confirmed |
| Dates |
|
Who is affected
Anyone who sends newsletters, marketing or other bulk mail to Microsoft 365 business mailboxes, plus automated mail (invoices, alerts) that Microsoft classifies as bulk. Tenants can't switch the tag off; admins can only exempt chosen senders and decide whether tagged mail moves to a folder.
What you will see
- Recipients see a Promotions tag on your message in Outlook on the web and the new Outlook for Windows.
- Your message lands in a Promotions folder instead of the Inbox where the recipient's admin turned on "Bulk moves enabled".
- Automated mail such as invoices from accounting software gets tagged too (reported in Microsoft Q&A: "Emails labeled promotions that are not promotions").
- The message headers of a received copy carry a BCL (bulk complaint level) value above 0.
Check your setup today
- Send a test to a Microsoft 365 mailbox in another organization (mail from a tenant's own domains is never tagged) and look for the Promotions tag in Outlook on the web.
- Open that message's headers and find the BCL value: 0 means not bulk, 1–3 bulk with few complaints, 4–7 mixed complaints, 8–9 many complaints.
- Check whether invoices, password resets and alerts leave from the same domain and service as your newsletters.
- Run our checker on each sending domain: SPF, DKIM and DMARC should all pass. That doesn't remove the tag, but Outlook.com rejects high-volume senders without them (550 5.7.515).
How to fix it
- Split your streams: send marketing from a subdomain (for example
news.yourdomain.com) and keep transactional mail apart. Microsoft recommends a subdomain for bulk email services so their reputation doesn't affect your main domain. - Keep complaints low, because the BCL rises with them. Make unsubscribing easy with a visible link and a List-Unsubscribe header; Microsoft tells admins to have users look for an unsubscribe option. Microsoft doesn't document either as a way to avoid the tag.
- Authenticate every sending domain: one SPF record (SPF generator), DKIM with your own domain, and DMARC (DMARC generator).
- Ask business recipients to move your messages out of Promotions. Microsoft says the system learns from these moves for future messages.
- For mail that must never be tagged (for example invoices to a client), the recipient's admin can add a mail flow rule that sets
X-MS-Exchange-Organization-BulkStampingto0for your sender, or add you to their allow list.
Check your domain now
After the fix, send a test email to see SPF, DKIM and DMARC pass on a real message, then keep an eye on it: free DMARC monitoring shows every service that sends mail as your domain and which ones fail, in plain English.
Get it fixed on Fiverr
Prefer to do it yourself? Get the step-by-step Fix Kit ($15) – 28-page guide, checklist, 20+ providers.
Related pages
Sources
- Microsoft Learn: Bulk email detection (Promotions tag and folder), updated 22 Oct 2026
- Microsoft 365 Message Center MC1279093: Enhancing how we handle promotional mail (mirror)
- Microsoft Learn: What's the difference between junk email and bulk email?
- Microsoft Learn: Set up SPF for Microsoft 365 (use a subdomain for bulk email services)
- Microsoft Support: Fix NDR error 550 5.7.515 in Outlook.com
- Microsoft Q&A: Emails labeled promotions that are not promotions (23 Oct 2026)
Other upcoming changes
- Microsoft 365 SMTP AUTH: Basic Authentication Off by Default at the End of December 2026
- DMARCbis (RFC 9989): pct Is Gone, t=, np= and psd= Are New — Update Your DMARC Record
- Gmail Stops Fetching POP Mail and Ends Gmailify in January 2027: Switch to Forwarding or IMAP
- Shorter TLS Certificates for Mail Servers: Let's Encrypt 64 Days (Feb 2027), 100-Day Maximum (Mar 2027)
- April 15, 2027 Root CA Distrust: Will Your Mail Server's Certificate Still Be Trusted?
- Microsoft 365 MX Records Move to *.mx.microsoft: What Changes for New and Existing Domains
- MailerSend Retires DKIM TXT Records on 1 February 2027: Move to the New CNAME Records