Three Things Microsoft Didn’t Replace When It Killed Prioritize My Inbox

You spent a chunk of 2025 teaching power users that the shiny new band at the top of their inbox, the one Copilot curated for them, was the thing to check first thing in the morning. Now Microsoft is taking it back. Prioritize My Inbox is being retired, with full removal from Outlook scheduled for the end of March 2027. There is no announced replacement. That is the whole story, and it’s the part that should annoy you.

So let’s do this as a bake-off: the feature that’s dying versus the thing you’ll actually land on when it’s gone. The incumbent, Focused Inbox, boring, free, still shipping, against the departing challenger. Judged on what matters to an admin who has to keep triage working after the lights go out.

Round one: longevity

Not close. Prioritize My Inbox has a death date. Focused Inbox doesn’t. One of these features will still be sorting mail in April 2027 and it isn’t the AI one. If you’re choosing where to point users and documentation today, the feature with a published retirement notice loses by default. Point goes to Focused Inbox.

Round two: what the user actually loses

Prioritize My Inbox did more than two-bucket sorting. It ranked messages by inferred importance and, the genuinely useful bit, told you why a message was flagged: a direct ask, a deadline, your name in the body rather than the CC line. That reasoning layer is what people got attached to. Focused Inbox gives you two piles and no explanation. So on raw capability, the challenger was better. The problem is you can’t keep a capability that’s been switched off.

Here’s the part that bites in four months: this is a Copilot-licensed feature. When it’s pulled, users who are paying for Microsoft 365 Copilot lose inbox triage specifically, while the free Focused Inbox keeps running for everyone who never paid. The premium tier ends up with the downgrade. Capability point to the challenger; value point back to the incumbent. Call it 2–1.

Round three: the reason, and the silence

Microsoft’s retirement notice says the feature is being removed. It does not, as of now, give a substantive why, and it does not name a successor. I’m not going to invent one for them. What I’ll say plainly: retiring a Copilot capability with no migration path and no replacement is a bad look for a product line sold on the premise that the AI keeps getting better. Don’t read it as a signal about other Copilot features, one retirement is one retirement. But do read it as a reminder that “new Copilot feature” and “durable feature” are not the same word. On trust, nobody wins.

Which clients, and who to warn

Here’s where you need to be careful quoting scope to anyone. Prioritize My Inbox only ever lived in the Copilot-enabled Outlook surfaces, new Outlook for Windows and Outlook on the web are where users actually saw it. The retirement notice covers those Copilot-enabled clients but does not itemise a full per-client list, it doesn’t spell out whether or how classic Win32 Outlook, Outlook for Mac, or the mobile apps are separately in scope, largely because the feature wasn’t surfaced identically across all of them to begin with. So: if someone asks you “does this hit Outlook on my Mac?”, the honest answer today is that Microsoft hasn’t published that granularity. Confirm the exact client scope against your tenant’s Message Center post before you send comms, that’s the authoritative list and it can shift. Don’t quote a client or a date to a VP without checking it there first.

There’s no tidy Graph property that says “this user had Prioritize My Inbox on.” It’s gated by Copilot licensing, so the honest way to scope your blast radius is to list everyone holding a Microsoft 365 Copilot license. Read-only, paginated, with the SKU resolved from your own tenant rather than a hard-coded GUID:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

Connect-MgGraph -Scopes 'User.Read.All','Organization.Read.All'
​
# Resolve the Copilot SKU from your tenant, confirm the part number first
$copilotSku = Get-MgSubscribedSku -All |
    Where-Object { $_.SkuPartNumber -like '*Copilot*' }
​
if (-not $copilotSku) {
    Write-Warning 'No Copilot SKU found. Check Get-MgSubscribedSku output and adjust the filter.'
    return
}
​
$targetSkuIds = $copilotSku.SkuId
​
try {
    Get-MgUser -All -Property 'id','displayName','userPrincipalName','assignedLicenses' `
        -ErrorAction Stop |
        Where-Object { $_.AssignedLicenses.SkuId | Where-Object { $_ -in $targetSkuIds } } |
        Select-Object DisplayName, UserPrincipalName |
        Export-Csv .\copilot-users.csv -NoTypeInformation
}
catch {
    Write-Error "Failed to enumerate users: $($_.Exception.Message)"
}
​
Write-Host "Review copilot-users.csv before sending any comms."

That CSV is your comms list, not your action list. Review it, then warn the humans on it manually, don’t automate a mail-merge straight off a live query.

Verdict

Focused Inbox wins, because it’s the one that’ll still be here. Set users’ expectations back to two buckets, document it now while you still have four months of runway to March 2027, and stop building workflows on the retiring feature today. The one case I’d still mourn the challenger: that “why this matters” reasoning line was genuinely good, and nothing native replaces it. If Microsoft ships a real successor, I’ll happily revisit. Until the Message Center says otherwise, plan for the downgrade.