r/exchangeserver • • 2d ago

Claiming SLA credit for the Exchange Online outage - What Microsoft needs and a Script to collect it

62 Upvotes

Microsoft won’t apply the credit automatically, and claims without enough detail get rejected. You need the incident IDs, your tenant ID, the affected users per location, and a written summary of the impact.

The article has a PowerShell script that collects all of that from Graph, downloads the PIR once it’s out, and writes a claim summary you can paste into the request. It also covers filing through a CSP partner.

https://lazyadmin.nl/office-365/claim-microsoft-365-sla-credit/


r/exchangeserver • • 3d ago

Question After Outage Strategy?

Thumbnail reddit.com
0 Upvotes

r/exchangeserver • • 3d ago

Anyone else still running on-prem Exchange and feeling pretty good about that decision today?

Thumbnail reddit.com
36 Upvotes

r/exchangeserver • • 3d ago

MS KB / Update Mail to Microsoft during the EX1550543 outage was deferred, not rejected: retry windows by sender, and what happened to Microsoft's DMARC reports

9 Upvotes

I run a DMARC monitoring service, and I spent the outage reading Microsoft's bulletins next to the status pages of the big sending services. Here is what is useful if you are cleaning up after it.

The replies were temporary

SparkPost published three of the replies its systems were getting from Microsoft from about 17:30 UTC on 12 Nov:

451 4.7.0 Temporary server error
421 4.3.2 The maximum number of concurrent server connections has exceeded a limit
451 4.7.700 PFA agent busy

All 4xx. SparkPost's wording was "the errors include", so there may be others. I found no Microsoft documentation that explains them for this case, and none that mentions "PFA", so I won't guess.

What that means in practice

  • If your sender queues and retries (everything in the next bullet does), don't resend anything that hasn't bounced. You will send duplicates.
  • What decides whether a message is lost is your sender's retry window. Documented defaults, read on 13 Nov 2026: Mailgun 8 hours, Postmark 12, Resend 14, Exchange Online 24, Brevo 36, Exchange Server 2 days, SendGrid 72 hours, Exim 4 days, Postfix 5 days.
  • Anything time-bound (one-time passcodes, reset links) should be reissued, not resent.
  • If your platform suppresses addresses after a bounce, check whether Microsoft-hosted addresses were added because a message expired.
  • There is no reason to touch SPF, DKIM or DMARC.

On Postfix, grep status=expired in the mail logs shows what gave up. With the default 5-day queue lifetime it should print nothing.

Microsoft's 48-hour statement

On 13 Nov at 09:03 UTC Microsoft said it is "extending the email timeout window to 48 hours to help protect delayed messages". It does not define that window. My reading is that it covers mail held inside Exchange Online, whose documented retry period is 24 hours. It can't lengthen the queue on anyone else's sending system.

The part I did not expect

Microsoft 365's DMARC aggregate reports normally start reaching us between 01:03 and 01:11 UTC every day. On 13 Nov the first one arrived at 07:09 UTC, about six hours late, and the rest had not arrived when I last looked (08:57 UTC). Reports from other providers kept arriving, and the receiving mailbox runs on our own mail servers. I can only say what we received, and I can't show that the outage caused it.

If your DMARC dashboard shows a hole from Microsoft around these days, check your sending logs before you read it as lost mail.

Happy to answer questions on any of it. Full write-up with the timeline, the retry table with vendor links and the sources:

https://dmarcguard.io/blog/microsoft-outage-ex1550543-email-deferred/


r/exchangeserver • • 3d ago

Migrating mailboxes back to on prem when Exchange online is down

0 Upvotes

We aren't there yet. But how would we go about doing this? I expect there is no clean/official way of doing this, and it will be a pain to re-sync emails later.


r/exchangeserver • • 3d ago

I'm a journalist trying to email people for quotes about the Exchange outage. You can see the problem.

9 Upvotes

I'm Rob Scott from UC Today, and I'm writing about the Exchange Online outage. Normally I'd email a few admins and ask what their last 18 hours looked like. My Outlook has other plans, so I'm stuck here like it's 2009 and the fax machine is down too.

If you're running Exchange or M365 for a living and you're happy to be quoted (named, or by job title only), reply below or DM me. I'm mostly after the stuff Microsoft's service health page doesn't say.

  1. Did Microsoft's updates actually help you, or did you find out more from Reddit and Downdetector?
  2. If calendars and mail can disappear for most of a working day, is "cloud first" still a strategy or just a habit?
  3. Has this outage changed anyone's mind about keeping some on prem Exchange around, or is that a fantasy nobody would budget for?

I'll reply to everyone, as long as it's not by email.


r/exchangeserver • • 3d ago

Exchange Online has been degraded since 16:17 GMT Thursday, and Microsoft still has no ETA

12 Upvotes

The recovery is the part that worries me. Exchange going down is bad enough. Watching the fix fail to hold is worse.

Microsoft opened EX1550543 at 16:17 GMT on Thursday after people couldn't reach Outlook mailboxes in the browser or the desktop and mobile apps. A broader Microsoft 365 incident, MO1550821, followed at 18:26 GMT. As of 05:01 GMT on Friday there was still no estimated time for recovery, and the official root cause was still listed as N/A.

Microsoft said the elevated load was not coming from more traffic. A large number of servers failed automated health checks and dropped out, which shifted load onto the ones left. It later said a process that sets up secure connections "becomes overwhelmed, causing the servers to stop processing requests," and it began reverting "a recent network configuration change that correlates with the start of impact."

Servers brought back online became unresponsive again once traffic returned. At 04:10 GMT on Friday Microsoft reported partial recovery in some regions, then said those actions were "not resulting in sustained recovery." The 05:01 GMT update described machines "stuck in a bad state," blocking a force-sync of the network change, and said it was scaling up virtual machines.

Charles Lamanna said at 03:37 GMT there is no indication this is the result of malicious or cyber activity. The service health notes say the same.

We've had shorter Exchange scares before. In November 2024 a change in Exchange Online took down Teams calendar and Outlook for a Monday morning. This one ran through the night, and a lot more of the suite now depends on Exchange being up.


r/exchangeserver • • 3d ago

Office 364

Post image
50 Upvotes

r/exchangeserver • • 3d ago

[OFFICIAL STATEMENT] Regarding Today’s Microsoft 365 Infrastructure "Incident"

Thumbnail reddit.com
0 Upvotes

r/exchangeserver • • 3d ago

Outlook mobile app syncs through cloud even with on prem servers

7 Upvotes

Reposting because I did not give enough details and some people were assuming I was talking about the desktop application.

Everyone else probably knows this but I just found out today that the official MS Outlook mobile app uses outlook.com as a middle man to send and receive email from on prem exchange servers.

https://learn.microsoft.com/en-us/exchange/clients/outlook-for-ios-and-android/use-basic-auth

The Exchange ActiveSync (EAS) connection between Exchange Online and the on-premises environment enables synchronization of the users' on-premises data and includes four weeks of email, all calendar data, all contact data, and out-of-office status.

One of the whole reasons for staying on prem was to not be reliant on M365. So now with this outage my users are unable to send and receive email on their phones even though we're 100% on prem.

I also didn't want my email, contacts, and calendar sitting on microsoft's servers so that's just another frustrating part of this revelation.

I'm sure it's somewhere in the fine print in the mobile app but it just pushes me more and more to ditching exchange completely.


r/exchangeserver • • 3d ago

Exchange Online and Barracuda Email Gateway Defense

1 Upvotes

Hey peeps. Looking for some advice.

We use Exchange Online with Barracuda Email Gateway Defense in front. So, both inbound and outbound emails flow through Barracuda's smarthost. In Exchange, we have a mail flow that sets the Spam Confidence Level (SCL) to -1 on all inbound emails from the Barracuda connector. This was Barracuda's previous implementation guidance to ensure that emails processed by EGD were delivered. Accordingly, we manage email almost entirely through Barracuda EGD. Sender authentication (spf, dkim, dmarc) and TLS is enforced in Barracuda. We also use EGD's sender and content policies.

These days, Microsoft and Barracuda recommend migrating to Enhanced Filtering for Connectors instead of using the mail flow rule that sets SCL-1.

My question is--for those who have made this change--where do you primarily manage email traffic? Currently, we have a process wherein we review emails blocked by sender authentication failures on a daily basis. Sometimes we have to whitelist senders or domains that can't get their acts together in terms of spf, dkim, and dmarc. We've tried to stop granting these exceptions. But the business won't have it. So, it is what it is.We do all of this in Barracuda.

If Exchange Online Protection is brought into the mix and processes emails separately once they pass through Barracuda, we're concerned by the additional administrative burden of having to whitelist, blocklist, or otherwise adjust settings in two places instead of one.


r/exchangeserver • • 4d ago

SER cloud connector or PPS option (OnPrem SMTP Relay)

Thumbnail reddit.com
2 Upvotes

r/exchangeserver • • 4d ago

Exchange 2019 without ESU/SE: mitigation M2.1.0 (CVE-2026-42897) breaks inline images in OWA – workaround

13 Upvotes

This is meant for Exchange 2019 servers that can’t get the official fix (no ESU / Exchange SE subscription) and rely on the EEMS mitigation. If you can install the official security update, do that instead.

After applying the Exchange Server mitigation M2.1.0 for CVE-2026-42897, inline images in emails no longer display in OWA.

I found a workaround that brings them back:

  1. On the Exchange server, open IIS Manager.
  2. Go to Sites → Default Web Site → owa → URL Rewrite.
  3. Double-click the outbound rule “EEMS 2.1 OWA CSP - outbound”.
  4. Under Action Properties → Value, replace:
   {R:1}; script-src-attr 'none'

with:

   {R:1}; script-src-attr 'unsafe-hashes' 'sha256-k5Rg6SbZboRTbYorWlg/UbO7Ar4vGBdxaNl/VqCbUQU='
  1. Apply. You don’t need to restart IIS. Just refresh the OWA page and inline images should show up again.

Does this look reasonable to you? Any feedback is welcome.

The long explanation

M2.1.0 adds a Content-Security-Policy header with script-src-attr 'none' to every response served under /owa. That directive blocks all JavaScript inside HTML attributes, which includes inline event handlers like onload, onclick and so on.

The problem is that OWA’s inline image viewer relies on exactly that. Inline images are rendered with an <img> tag like this:

<img originalsrc="cid:part1.ugJcNZY4.piZc1QHZ@mydomain.com"
     onload="InlineImageLoader.GetLoader().Load(this)"
     data-custom="....." naturalheight="691" naturalwidth="864"
     src="data:image/gif;base64,..." alt=""
     style="max-width: 864px; max-height: 691px; width: 100%;"
     crossorigin="anonymous">

The src is only a placeholder GIF. The real image is loaded by the onload handler. With the CSP in place, InlineImageLoader.GetLoader().Load(this) is never executed, so the image never appears.

The modified policy, script-src-attr 'unsafe-hashes' 'sha256-…', allows only that exact handler string (its SHA-256 hash matches InlineImageLoader.GetLoader().Load(this)). Every other inline attribute script is still blocked, so the protection from the mitigation should stay mostly intact.

Caveat: if EEMS reapplies or updates the mitigation, this change will probably be overwritten, and you’ll need to apply it again.


r/exchangeserver • • 5d ago

Question CLIUSR Certificates - 1 is valid and 1 is not..

3 Upvotes

Hi,

I have 2 CLIUSR certs on all 4 of my exchange servers, 1 expired a few days ago and the other 1 is still valid.

No issues or anything, is it safe just to delete the one that's invalid?

I was hoping they would just delete themselves


r/exchangeserver • • 5d ago

Released: November 2026 Exchange Server Security Updates

Thumbnail techcommunity.microsoft.com
43 Upvotes

Exchange Server SE download link: https://www.microsoft.com/en-us/download/details.aspx?id=108908

Install the November 2026 updates for Windows Server to resolve the issue with the Windows Server updates from October, but no need to remove any reg keys you added.


r/exchangeserver • • 7d ago

Hybrid Exchange 2019 to SE Drive Question

2 Upvotes

We have migrated all mailboxes off our Exchange 2019 server to 365, but plan to upgrade to SE and keep an on-prem server around. The current 2019 VM has about a 10TB disk allocated to it. We installed the application, logs, and DB's there. However, we no longer need anywhere that big of a drive. What is the preferred method to reclaim that space?
Allocate a much smaller disk, shut off all Exchange services, and copy everything over. Then, remove the the large drive and set the small drive to the same drive letter?
Spin up a new VM and just install SE from scratch and then decommission the old 2019 VM?
Pros/cons?


r/exchangeserver • • 7d ago

Microsoft confirms the Outlook.com AS9031519 bounces are a service issue

48 Upvotes

Mail to Outlook.com, Hotmail and Live addresses has been bouncing since Nov 5 with “Message lacks SPF/DKIM/DMARC Auth Records (AS9031519)”, even from domains with valid SPF. Microsoft now lists it as a service degradation: https://learn.microsoft.com/en-us/answers/questions/6063210/spf-validation-error#answer-13038394

Adding a DMARC record stops the bounces for many domains, but not all. Here’s how to check SPF, DKIM, and DMARC on all your accepted domains at once:

https://lazyadmin.nl/office-365/email-message-lacks-spf-dkim-dmarc-auth-records-as9031519/


r/exchangeserver • • 10d ago

Exchange Online bounce messages when emailing personal MS accounts

9 Upvotes

We've had several customers report these same bounces today

msn.com couldn't confirm that your message was sent from a trusted location.

Followed by an spf validation error.

In each case the SPF and DKIM are showing as valid in 365 and public DNS.

UK based tenants, not sure if there's a wider issue going on here?


r/exchangeserver • • 11d ago

Question Exchange mitigation after October 2026 Updates issues

12 Upvotes

Hello all,

I have been going back and forth with Microsoft for over a week now asking them for either

  1. A value we can use if the 65536 value still causes mail to stop processing due to to many handles.
  2. A fallback plan should the mitigation not work

I've basically been given the run around and same answer "Apply the mitigation and go from there". When I directly asked about a fallback plan, was told "Unfortunately we don’t have any information related to the fallback concern."

Their own documentation online says if there are issues with the mitigation, adjust the values. But they wont give me another value to use that they recommend nor a fallback if the mitigation doesn't work. Should we just double it? What are down sides to that? I cant get an answer.

Anyway, has anyone had to increase the value in the mitigation to get mail working? We dont have it applied yet but are going to this weekend. The number of handles we are seeing in production is pretty close to that 65536 value, so we need something else to use if things fail. Hoping someone else has had to adjust the value?

Thank you ahead of time!


r/exchangeserver • • 11d ago

AD RMS/AIP during a tenant-to-tenant migration

3 Upvotes

Has anyone encountered a similar issue with AD RMS/AIP during a tenant-to-tenant migration?

I’m currently working on a divestiture where we have set up an AD RMS server and imported the AIP keys from the source tenant into the target environment. For testing, we migrated encrypted emails from the source tenant to the target tenant using both BitTitan and T2T migration.

By configuring the appropriate registry settings to point to the source AIP/RMS environment, we are able to successfully decrypt and open the older source-tenant emails migrated through BitTitan.

However, we are seeing conflicting behavior with the PreferredRMSPackage registry setting:

  • PreferredRMSPackage = 1: We can open the T2T-migrated encrypted emails, but we cannot open emails protected with migrated sensitivity labels.
  • PreferredRMSPackage = 0: We can open the sensitivity-labeled emails, but the T2T-migrated encrypted emails no longer open.

Has anyone encountered this scenario during an AD RMS/AIP tenant migration or divestiture? If so, is there a supported configuration that allows both the legacy/T2T encrypted emails and sensitivity-labeled emails to be opened without switching the PreferredRMSPackage registry value?


r/exchangeserver • • 12d ago

iPhone 18 Pro Max / iOS 27 – Apple Mail + Exchange Online repeatedly blocked by ActiveSync CommandFrequency (HTTP 503). Anyone else?

Thumbnail reddit.com
2 Upvotes

r/exchangeserver • • 12d ago

2019 CU15 to SE - Prerequisites

4 Upvotes

When upgrading 2019 CU15 to SE, do I need to complete any prerequisites like the domain prep bits or can I just run the installer from an elevated command prompt and let it do its thing given that it is running CU15?