Outlook is retiring Prioritize My Inbox, not its entire Copilot feature set
The phased removal begins October 26. People who relied on the ranking layer need a replacement habit even if administrators have no switch to configure.
Outlook is losing Copilot Prioritize, the feature that tried to surface the messages most relevant to a person’s work. Microsoft’s retirement begins on October 26, 2026, with completion expected by the end of March 2027. That is a phased removal, so two colleagues may see the feature disappear at different times.
The Microsoft 365 notice, preserved as MC1519861, says the change covers all Outlook clients and requires no opt-in. It describes a simplification of the Copilot experience and a refocusing of investment. It does not provide adoption figures, accuracy measurements or a detailed explanation of why this particular feature is being removed.
The feature being retired is a specific sorting layer
In its July 2025 explanation of Prioritize My Inbox, Microsoft described a system that used work context, past behavior and user instructions to identify important messages. A person could specify the kinds of correspondence that mattered and receive an explanation of why a message was prioritized.
That is a narrower function than “Copilot in Outlook.” The retirement notice should not be read as a shutdown of Outlook, a deletion of mailboxes or the removal of every AI feature associated with email. It concerns the Prioritize experience. Existing users need to identify whether that is the tool on which their routine depends.
There is an important operational difference between losing a convenience and losing a habit. Someone who has trained themselves to check the prioritized view first may continue assuming it represents the most urgent work. When that view changes, a replacement routine needs to be deliberate: where time-sensitive requests arrive, who escalates them, and which messages must be checked directly.
A transition for people, even without an admin switch
Microsoft says administrators do not need to make a configuration change. It nevertheless recommends notifying affected users, preparing support teams and removing references from internal training. Those tasks are the transition. A help page that tells staff to click a button that has vanished creates confusion even when the service itself is working as designed.
For an Italian organization using the feature, the same distinction applies. This is an all-client product change, not a US-only announcement. The exact disappearance date may vary during the rollout; October 26 is its beginning, not a universal cutoff for every account.
The broader lesson is about dependence on a particular workflow rather than a verdict on AI as a category. An intelligent sorting layer can be useful and still remain a service feature whose lifecycle is controlled by the vendor. Our comparison of workplace AI accounts makes a related point: the features a person can use depend on the account and service context, not just the name of the assistant.
A sensible replacement starts with the decisions the feature helped make. If its real value was keeping one project’s requests visible, preserve that requirement explicitly in the team’s process. The feature can disappear over five months; an important message should not disappear with it.
