Helpdesk: "Dana's out of office works for people inside the company, but a customer says they got nothing. The Support shared mailbox reply never fires at all, and classic Outlook says the server is currently unavailable when I open Automatic Replies for it. Marco set his in new Outlook and his manager got the reply once, then never again. Can you just turn it off and on for everyone?"
Don't toggle it yet. "Automatic replies not working" is usually one broken layer in a documented chain, not a broken mailbox: the reply isn't actually on (or scheduled, or allowed to reach external senders) for that mailbox → the message never reached the mailbox, so nothing triggered the reply (forwarding without a copy, a redirect rule, Junk, a distribution group) → the sender already got a reply once, and Exchange sends one per sender → a remote domain stops the reply for external senders, or for one domain → a mail flow rule blocks the reply, or the message trace shows where it went → the client can't read or save the settings (EWS, rules quota, proxy, a classic Outlook shared mailbox bug) → the wrong or a duplicate reply goes out because of a leftover rule or template. Get-MailboxAutoReplyConfiguration, Get-Mailbox, Get-RemoteDomain, Get-TransportRule, and message trace are the sources for that chain. Turning the reply off and on clears the reply history, but it can't fix forwarding, a remote domain, or a mail flow rule.
If the shared mailbox itself is missing from Outlook, start with Shared Mailbox Not Showing in Outlook. If the trace points at a transport rule that isn't doing what you expect, use Exchange Online Mail Flow Rule Not Working. This post covers "automatic replies (out of office) are on, or should be, and senders don't get them, get the wrong one, or the setting won't open, and you need a read-first path before you reset rules, change remote domains, or edit mail flow rules."
TL;DR
-
Read the mailbox's own settings first.
Get-MailboxAutoReplyConfigurationshows the state (Enabled, Scheduled, Disabled), the schedule, and ExternalAudience (None, Known, All). Known means only external senders in the mailbox's Contacts list get a reply. - Automatic replies are server-side Inbox rules. Microsoft: they fire whether or not the client is running. If the message never lands in the mailbox (SMTP forwarding without "deliver to both," a redirect rule, Junk), no reply is generated.
- One reply per sender. Exchange keeps an OOF history and sends one reply to each sender until the reply is turned off and on, or the rule changes. Testing twice from the same address proves nothing.
-
External replies depend on remote domains.
AutoReplyEnabledandAllowedOOFTypeon the Default remote domain (or a domain-specific one, which overrides Default) can stop every external reply. -
Message trace tells you whether the reply was generated. Microsoft: for OOF replies the original sender becomes the recipient in the trace. A Drop event saying
RESOLVER.OOF.IntToExtis normal. - "Your automatic reply settings cannot be displayed because the server is currently unavailable" points at EWS on the mailbox, the rules quota, a WinHTTP proxy, or, for a shared mailbox in classic Outlook, a known build issue.
Where in the chain did it break?
| Step | What should be true | Typical symptom when it breaks |
|---|---|---|
| 1. Symptom captured | Mailbox, sender, internal or external, first test from that sender, client, exact error | "Out of office isn't working" with no detail |
| 2. Mailbox setting | State Enabled or Scheduled, inside the window, ExternalAudience allows the sender | Nobody gets a reply; external senders don't; only contacts do |
| 3. Delivery to the mailbox | Message lands in the mailbox, not forwarded away, redirected, or in Junk | Mailtip shows the reply, but no reply arrives |
| 4. Reply history | Sender hasn't already had a reply since the last change | First message gets a reply, later ones don't |
| 5. Remote domains | AutoReplyEnabled true, AllowedOOFType sends external replies to that domain | Internal senders get replies, external senders never do |
| 6. Mail flow and trace | No rule blocks a reply with a blank return path; trace shows it sent | Nobody in the tenant gets external replies; trace shows a reject |
| 7. Client and settings access | EWS enabled, rules quota not exceeded, proxy correct, supported build | "Server is currently unavailable"; reply can't be saved |
| 8. Wrong or duplicate reply | No duplicate Inbox rule, client-side rule, or corrupt template | Old text goes out; two replies; reply after it was turned off |
| 9. Change | Only after Steps 1–8 agree, one layer at a time | Every reply toggled, every rule reset, still not working |
Step 1: Capture the exact symptom (read-only)
Write these facts on the ticket before anyone toggles the reply or edits a rule:
| Fact | Why it matters |
|---|---|
| The mailbox and its type | User, shared, or Microsoft 365 group mailbox. Each is set from a different place (Step 2) |
| Who sent the test, internal or external | Internal and external replies are separate messages with separate rules and remote domain checks (Steps 2 and 5) |
| Was it that sender's first message since the reply was set? | One reply per sender (Step 4) |
| Was the sender in the mailbox's Contacts? | ExternalAudience Known only replies to contacts (Step 2) |
| Sent directly or through a group | Distribution group members' replies don't reach the sender by default (Step 3) |
| Which client set it, and the exact error | New Outlook, classic Outlook, Outlook on the web, admin center, or PowerShell. The error text maps to Step 7 |
| Forwarding, journaling, or a third-party mail filter in front of Microsoft 365 | Steps 3 and 6 |
Then match the symptom:
| What you see | Likely layer |
|---|---|
| Nobody gets a reply, internal or external | Step 2 (not on, outside the schedule), Step 3 (forwarding, redirect), Step 7 (rules quota, templates) |
| Internal senders get it, external senders don't | ExternalAudience None or Known (Step 2), remote domains (Step 5), a mail flow rule (Step 6) |
| Every external reply in the tenant is missing | Default remote domain (Step 5) or a mail flow rule (Step 6) |
| First message got a reply, the next didn't | Expected: one reply per sender (Step 4) |
| Sender sees the reply mailtip but no reply arrives | Forwarding without a copy, or a redirect rule (Step 3) |
| Shared mailbox reply set in classic Outlook fails to open | Step 7, known issue |
| Old text, two different replies, or replies after it was turned off | Step 8 |
Step 2: Is the reply actually on, for this sender? (read-only)
Microsoft describes automatic replies as Inbox rules that the client sets in the mailbox. They're server-side, so they run whether or not Outlook is open. The rules can be set from Outlook, Outlook on the web, the Microsoft 365 admin center, the Exchange admin center, or PowerShell, and they all configure the same mailbox feature. That's the setting to read:
# Read-only. Exchange Online PowerShell (Connect-ExchangeOnline)
Get-MailboxAutoReplyConfiguration -Identity 'dana@contoso.com' |
Format-List Identity, AutoReplyState, StartTime, EndTime, ExternalAudience, InternalMessage, ExternalMessage
# Read-only: every mailbox that currently has automatic replies on or scheduled
Get-Mailbox -ResultSize Unlimited | Get-MailboxAutoReplyConfiguration |
Where-Object { $_.AutoReplyState -ne 'Disabled' } |
Select-Object Identity, AutoReplyState, StartTime, EndTime, ExternalAudience
| Field | What Microsoft documents |
|---|---|
| AutoReplyState | Enabled sends replies. Scheduled sends them only between StartTime and EndTime. Disabled is the default |
| StartTime / EndTime | Used only when the state is Scheduled. Outside that window, no reply goes out |
| ExternalAudience | None: no replies to external senders. Known: only external senders in the mailbox's Contacts list. All: every external sender |
| InternalMessage | Required for Enabled and Scheduled |
| ExternalMessage | Required when ExternalAudience is Known or All. It's used only when the state is Enabled or Scheduled and ExternalAudience isn't None |
In the clients, Known is the Send replies only to contacts option (new Outlook and Outlook on the web) or My contacts only (classic Outlook). Microsoft's support article recommends it for external replies, because Send replies outside your organization answers every message, including newsletters, advertisements, and potentially junk email. If a customer isn't in the user's Contacts, a Known setting is working as designed.
Where each mailbox type is set:
| Mailbox | Where Microsoft documents setting it |
|---|---|
| User | The user's own client (new Outlook: View → View settings → Accounts → Automatic Replies; classic Outlook: File → Automatic Replies; Outlook on the web: Settings → Account → Automatic replies), the Microsoft 365 admin center (Users → Active users → the user → Mail (mail settings) → Automatic replies), the Exchange admin center (Recipients → Mailboxes → the mailbox → Others → Manage automatic replies), or Set-MailboxAutoReplyConfiguration
|
| Shared | Microsoft 365 admin center: Teams & groups → Shared mailboxes → the mailbox → Edit under Automatic replies (text only, no images), Outlook on the web with the shared mailbox opened in its own window, or PowerShell |
| Microsoft 365 group |
Set-MailboxAutoReplyConfiguration -Identity <group mailbox>. If the group mailbox is over quota, the cmdlet fails with QuotaExceededException; Microsoft's fix is to reduce the group mailbox, wait an hour, and rerun it |
Accounts that can't use it. Microsoft: automatic replies aren't supported for Gmail, Yahoo, or other POP or IMAP accounts. In classic Outlook, no Automatic Replies button under File usually means that kind of account, and the fallback is an Outlook rule that only works while Outlook is running.
If a scheduled reply starts or stops at an hour nobody expected, compare StartTime and EndTime with the mailbox's time zone (Get-MailboxRegionalConfiguration). Microsoft's cmdlet reference says the values you enter use the short date format of the computer running the command.
Step 3: Did the message reach the mailbox? (read-only)
Microsoft's article for "senders see the Automatic reply mailtip but get no reply" names two causes, both by design: the message never lands in the mailbox, so the reply never triggers.
| Check | What Microsoft documents |
|---|---|
| SMTP forwarding without a copy | If ForwardingAddress or ForwardingSmtpAddress is set and DeliverToMailboxAndForward is false, messages go only to the forwarding target and no reply is generated |
| A transport rule redirects the mailbox's mail | Same result. Microsoft's guidance is to remove forwarding rules made for that mailbox, and to use Inbox rules instead when forwarding is required |
| Junk | Microsoft: if the message is marked as spam and delivered to Junk, no automatic reply is generated |
| JournalingReportNdrTo | If the mailbox is the organization's JournalingReportNdrTo address, replies aren't sent for it. Microsoft recommends a dedicated mailbox, or an external address, for that setting |
| Sent to a distribution group | SendOofMessageToOriginatorEnabled decides whether members' out-of-office replies reach the sender. The default is $false |
# Read-only: forwarding, mailbox type, and rules quota
Get-Mailbox -Identity 'dana@contoso.com' |
Format-List RecipientTypeDetails, ForwardingAddress, ForwardingSmtpAddress, DeliverToMailboxAndForward, RulesQuota
# Read-only: Inbox rules that forward or redirect
Get-InboxRule -Mailbox 'dana@contoso.com' |
Select-Object Name, Enabled, ForwardTo, ForwardAsAttachmentTo, RedirectTo
# Read-only: is this mailbox the journaling NDR address? Do group members' replies reach senders?
Get-TransportConfig | Format-List JournalingReportNdrTo
Get-DistributionGroup -Identity 'sales@contoso.com' | Format-List SendOofMessageToOriginatorEnabled
A sender who wrote to sales@ and expected Dana's reply is a group question, not a Dana question.
Step 4: Did this sender already get a reply? (read-only)
Microsoft: an OOF response is sent one time per recipient. The mailbox keeps an OOF history of everyone who has had a reply. It's cleared when the state changes (enabled or disabled) or when the OOF rule is modified. Microsoft's support article says the same thing from the user side: the reply is sent once to each person who emails you while you're away.
That explains the most common false alarm. "My manager got it once, then never again" is the design. So is "I tested from my Gmail twice and got nothing the second time."
| Situation | What Microsoft documents |
|---|---|
| Test sender already replied to | No second reply until the history clears. Test from a new address, or change the reply first |
| History limit | 10,000 entries. Past that, new senders aren't added, so they get a reply to every message. Senders already in the list still get only one |
| You need a reply to every message | Microsoft's alternative is a server-side Inbox rule with have server reply using a specific message instead of the OOF feature |
Step 5: Do remote domains allow the external reply? (read-only)
Internal senders get the reply and external senders don't? Read the remote domains. Every organization has a remote domain named Default for *, and a remote domain for a specific domain overrides Default for that domain.
# Read-only: which remote domains exist, and what each allows
Get-RemoteDomain | Format-Table -AutoSize Name, DomainName, AutoReplyEnabled, AllowedOOFType, IsInternal
| Setting | What Microsoft documents |
|---|---|
| AutoReplyEnabled | $false means no automatic replies are delivered to recipients in that domain. Microsoft's OOF article says it takes precedence over the mailbox's settings and the OOF type. Default: $true for the built-in Default remote domain in Exchange Online and for new remote domains; $false for Default in on-premises Exchange |
| AllowedOOFType | External (only replies designated external; the cmdlet reference calls this the default), ExternalLegacy, InternalLegacy, or None (no replies to that domain) |
| A domain-specific entry | Overrides Default. If there's a fabrikam.com remote domain, its settings decide for @fabrikam.com senders, whatever Default says |
| Hybrid | Microsoft: with AllowedOOFType External, only external replies go to on-premises mailboxes. To send internal replies to Exchange on-premises, set AllowedOOFType to InternalLegacy on the remote domain that covers the on-premises mailboxes |
| IsInternal | Linked to AllowedOOFType: setting InternalLegacy changes IsInternal to $true, and setting IsInternal to $false changes AllowedOOFType to ExternalLegacy |
Two cautions. First, Microsoft's Outlook troubleshooting article says AllowedOOFType defaults to None, while the Set-RemoteDomain reference and the remote domains page say external replies are sent by default. Read your own values instead of trusting either default. Second, an organization may have turned these off on purpose, because an automatic reply confirms to any outside sender that the address is real and the person is away. Ask before you change Default.
Some forum answers point to an organization-wide auto-reply switch in Set-OrganizationConfig. The Set-OrganizationConfig reference we read lists no such parameter, so stick to the mailbox, remote domain, and mail flow layers.
Step 6: Does a mail flow rule block it, and what does the trace say? (read-only)
Microsoft's OOF article: if replies seem to be missing for all users in the tenant, a transport rule is usually to blame.
The scenario Microsoft highlights: MX points at a third-party filter, and a rule rejects mail received from outside the organization unless it comes from the filter's IP addresses. Automatic replies have a blank (<>) return path, so a rule that matches the sender in the envelope only can unexpectedly match the reply and block it. Microsoft's fix is to set the rule's Match sender address in message property to Header or envelope. The mail flow rule reference adds that, for auto-replies, the sender a rule sees depends on that property.
# Read-only: rules that could match replies, in priority order
Get-TransportRule | Sort-Object Priority |
Select-Object Priority, Name, State, Mode, SenderAddressLocation
# Read-only: the original sender is the RECIPIENT of the reply (Microsoft's tip)
$trace = Get-MessageTraceV2 -RecipientAddress 'sam@fabrikam.com' -StartDate (Get-Date).AddDays(-2) -EndDate (Get-Date)
$trace | Select-Object Received, SenderAddress, RecipientAddress, Subject, Status
# Read-only: event-by-event detail for those messages
$trace | Get-MessageTraceDetailV2 | Select-Object Date, Event, Detail
| What the trace shows | What Microsoft documents |
|---|---|
| No reply message at all | It was never generated. Go back to Steps 2–5 |
| Reply rejected or blocked by a rule | Microsoft: the trace clearly shows when a transport rule blocks the reply |
Drop: 250 2.1.5 RESOLVER.OOF.IntToExt; handled internal OOF addressed to external recipient |
Normal. Exchange Online generates both the internal and external reply, then drops the one that doesn't apply. The reverse is ExtToInt
|
550 5.7.750 Service unavailable. Client blocked from sending from unregistered domains. |
Microsoft: contact Microsoft Support to learn why the unregistered domain block was enforced |
| Delivered, but the sender never saw it | Microsoft sends OOF replies through the high risk delivery pool, because they're lower priority. What the receiving system does with it is outside your tenant, so ask the sender to check junk |
Message trace limits from the cmdlet reference: 90 days of data, 10 days per query, the last 48 hours if you give no dates, and timestamps in UTC.
Step 7: Can the client read and save the setting? (read-only first)
The error "Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later." has several documented causes:
| Cause | What Microsoft documents |
|---|---|
| EWS disabled on the mailbox | Microsoft: automatic replies rely on EWS. Re-enabling it can take several hours. EwsEnabled on the mailbox is meaningful only if it isn't set to $false at the organization level |
| Rules quota exceeded | The rules quota counts the size of enabled rules, not the number. Exchange Online's default and maximum is 256 KB (262,144 bytes). When it's full, the OOF rules can't be created, and quota changes can take up to two hours to apply |
| Wrong WinHTTP proxy | Microsoft's Outlook article ties this error, missing MailTips, and missing free/busy to an incorrect WinHTTP proxy. Its fix is netsh winhttp reset proxy (from SysWOW64 for 32-bit Office on 64-bit Windows). The article lists Outlook 2007–2013, so treat it as one candidate for current builds |
| Shared mailbox in classic Outlook | Known issue: with a shared mailbox added as an additional or primary account, classic Outlook shows this error starting with builds 18510.10000+ (first seen in Current Channel Version 2505). Fixed in Version 2508 Build 19127.20000. Workaround: set it in Outlook on the web with the shared mailbox opened in its own window (Settings → Account → Automatic replies) |
# Read-only: EWS for this mailbox and for the organization
Get-CASMailbox -Identity 'dana@contoso.com' | Format-List EwsEnabled
Get-OrganizationConfig | Format-List EwsEnabled
# Read-only, on the PC (elevated prompt): the WinHTTP proxy Outlook may be using
netsh winhttp show proxy
New Outlook. Microsoft's path is View → View settings → Accounts → Automatic Replies. If those steps don't match the screen, Microsoft notes you may still be on classic Outlook. The setting itself lives in the mailbox, so Get-MailboxAutoReplyConfiguration shows whether new Outlook actually saved it. Reading it there tells you whether you're looking at a client problem or a mailbox problem.
Step 8: Wrong reply, two replies, or a reply after it was turned off? (read-only)
| Symptom | What Microsoft documents |
|---|---|
| Old or duplicate reply | Look for a duplicate Inbox rule. If there isn't one, the OOF history may have hit its 10,000-entry limit (Step 4) |
| Two different replies | Likely an OOF rule in the Outlook client: File → Automatic Replies → Rules |
| A reply after automatic replies were turned off | Can happen when someone created a rule by hand with the out-of-office template |
| Reply can't be saved, or never sent even though it's on | Malformed or corrupted OOF rule templates, or the rules quota (Step 7). Microsoft's fix removes the OOF rules and the templates (message classes IPM.Note.Rules.OofTemplate.Microsoft and IPM.Note.Rules.ExternalOofTemplate.Microsoft) with MFCMapi, then disables and re-enables the reply |
Microsoft warns that MFCMapi can damage Exchange mailboxes. Keep it as the last step, on one mailbox, after Steps 2–7 are clean.
Step 9: Change one layer, then retest (only after the read)
Pick the one change Steps 1–8 point at:
-
Mailbox setting: turn the reply on or fix the schedule and audience in the user's client, the admin center, or
Set-MailboxAutoReplyConfiguration. Changing the state or the reply rule also clears the reply history. -
Delivery: if forwarding has to stay, set
DeliverToMailboxAndForwardto$trueso mail reaches the mailbox. Or replace the forward with an Inbox rule, as Microsoft suggests. -
Group: set
SendOofMessageToOriginatorEnabledon the distribution group only if the business wants every member's reply going to senders. - Remote domain: for one partner, create a domain-specific remote domain rather than loosening Default for the whole internet. Change Default only with the owner's sign-off.
- Mail flow rule: set Match sender address in message to Header or envelope on the rule that matches the blank return path, or add an exception, then retest.
- Client: re-enable EWS (allow hours), raise or clean up the rules quota (allow two hours), fix the WinHTTP proxy, or update classic Outlook past the known-issue build.
- Rules and templates: remove the duplicate or client-side rule; MFCMapi template cleanup only as the last step.
# Change (one mailbox, reversible): Microsoft's Examples 1 and 2 combined (Scheduled, internal and external text)
Set-MailboxAutoReplyConfiguration -Identity 'dana@contoso.com' -AutoReplyState Scheduled `
-StartTime '10/19/2026 08:00' -EndTime '10/23/2026 17:00' `
-InternalMessage 'I am out of the office until Friday. For urgent issues, contact the service desk.' `
-ExternalMessage 'I am out of the office until Friday. For urgent issues, contact support@contoso.com.' `
-ExternalAudience All -WhatIf
# Change (one mailbox): keep the forward, but deliver a copy so the reply can fire
Set-Mailbox -Identity 'dana@contoso.com' -DeliverToMailboxAndForward $true -WhatIf
Run with -WhatIf first, then without it. Retest from an address that hasn't had a reply since the change, and confirm the reply in the message trace (Step 6).
When a change is justified
| Finding | Prefer | Avoid |
|---|---|---|
| ExternalAudience Known, customer not in Contacts | Explain it, or switch to All with the user's agreement | Changing remote domains for one user |
| Forwarding without a copy | DeliverToMailboxAndForward $true, or an Inbox rule | Removing forwarding the business needs |
| Same test sender, no second reply | Test from a new address | Toggling every mailbox's reply |
| Default remote domain blocks external replies | Confirm intent; a domain-specific remote domain for the partner who needs it | Re-enabling replies to the whole internet without sign-off |
| Rule with envelope-only sender match blocks replies | Header or envelope, or an exception | Disabling the rule that protects your MX path |
| "Server is currently unavailable" on a shared mailbox in classic Outlook | Outlook on the web or the admin center now; update the build | Rebuilding the user's Outlook profile |
| EWS disabled by policy | Set the reply from the admin center or PowerShell | Re-enabling EWS for everyone |
| Rules quota full | Clean up enabled rules, or raise the quota | Deleting all of the user's rules |
| Duplicate or leftover reply | Remove the extra rule | MFCMapi on every mailbox |
FAQ
Why is my out of office not working for external emails?
In order: the mailbox's ExternalAudience is None, or Known and the sender isn't in Contacts; the sender already got a reply; the Default or a domain-specific remote domain has AutoReplyEnabled $false or AllowedOOFType None; or a mail flow rule blocks replies with a blank return path. Message trace, with the external sender as the recipient, shows whether the reply was generated and what happened to it.
Why are automatic replies not working on a shared mailbox?
Set the reply on the shared mailbox itself, from the Microsoft 365 admin center (Teams & groups → Shared mailboxes → Automatic replies), Outlook on the web with the shared mailbox opened in its own window, or Set-MailboxAutoReplyConfiguration. If classic Outlook shows "server is currently unavailable" for it, that's a known issue fixed in Version 2508 Build 19127.20000. Then run the same delivery, remote domain, and trace checks as any mailbox.
Why are automatic replies not working in new Outlook?
Check that the setting saved: Get-MailboxAutoReplyConfiguration reads what the mailbox actually has. If it's on there, the client isn't the problem, so continue with Steps 3–6. Automatic replies aren't supported for POP or IMAP accounts in any Outlook.
Why did someone get my automatic reply only once?
By design. Exchange sends one reply per sender and keeps a history until the reply is turned off and on or the rule changes. Microsoft's option for a reply to every message is a server-side rule that replies with a specific message.
What does "Your automatic reply settings cannot be displayed because the server is currently unavailable" mean?
Microsoft lists EWS disabled on the mailbox, the rules quota, and an incorrect WinHTTP proxy, plus a known classic Outlook issue for shared mailboxes. Read EwsEnabled, RulesQuota, and netsh winhttp show proxy before you rebuild anything, and set the reply from Outlook on the web or the admin center meanwhile.
Related posts
- Shared Mailbox Not Showing in Outlook (when the shared mailbox you need to set the reply on isn't in Outlook at all)
- Exchange Online Mail Flow Rule Not Working (rule priority, mode, and message trace, for the rule that blocks replies)
- A Monthly Exchange Online Hygiene Check: External Forwarding and Mailbox Permissions (finding the forwarding that stops replies before users notice)
Free checklist
Automatic-reply tickets cluster around travel and leave. That's the same week a traveling user hits a Conditional Access location or device block, can't sign in to turn their reply on, and the helpdesk ends up setting it from the admin center. Before you enforce, the free Conditional Access pre-enforcement checklist keeps break-glass accounts, pilot groups, and report-only review on one page:
If you want the rest of the Intune runway written down for the team (enrollment hygiene, compliance phasing, break/fix cards and read-only PowerShell snapshots), the Intune & M365 Admin Starter Pack pairs with this triage: https://cashflow4375.gumroad.com/l/joonf?utm_source=devto&utm_medium=article&utm_campaign=aps_first_sale&utm_content=automatic-replies-not-working
Admin Pack Studio; not affiliated with Microsoft. Steps 1–8 favor read-only checks: Get-MailboxAutoReplyConfiguration, Get-Mailbox, Get-InboxRule, Get-TransportConfig, Get-DistributionGroup, Get-RemoteDomain, Get-TransportRule, Get-MessageTraceV2, Get-MessageTraceDetailV2, Get-CASMailbox, Get-OrganizationConfig, and netsh winhttp show proxy. Turning replies on or off, changing forwarding, group, remote domain, or mail flow rule settings, re-enabling EWS, changing the rules quota or WinHTTP proxy, and removing rules or templates are deliberate changes. Change one layer at a time, retest from a sender that hasn't had a reply yet, and check current Microsoft Learn for console labels and supported versions.
