Outlook Mobile App vs Desktop: Which Features You Lose on Phone

If you built your Outlook workflow on a desktop — a wall of rules, a categorised inbox, a signature with a logo and a phone number, delegated access to a shared team mailbox — it will not survive the switch to a phone unchanged. The Outlook mobile app is a good triage client, not a slim copy of the desktop, and the features it drops are the ones most likely to break the day you decide to work from a train.

This piece is a per-capability walk through what changes when you move between the two surfaces, aimed at people who already know Outlook and are trying to decide which jobs are safe to do from a phone. It covers the honest limits — where mobile really cannot do the thing at all — and the softer ones, where it can, but in a way you would not want as your primary workflow.

The primary keyword here is deliberate: this compares the Outlook mobile app on iOS and Android against Outlook on Windows and Outlook for Mac. Where a distinction matters between new Outlook and classic Outlook on the desktop side, we call it out; where it does not, treat "desktop" as either.

The verdict up front#

Outlook mobile is the right client for reading, triaging, replying briefly, and confirming meetings. It is not the right place to build or maintain the structural parts of your inbox — the rules, the signatures, the folder taxonomy, the shared mailbox permissions, the add-in integrations. Those live on the desktop, and they follow you to the phone once configured, not the other way around.

That is the trade Microsoft designed into the app, and it is why so many workflows that look fine at a desk quietly break on a commute. The rule you meant to write while waiting for a train has no surface on the phone. The signature that made a client reply feel considered is a plain-text stub on the phone. The unified search across four accounts that shipped with the desktop is a single-account search on the phone. Each of these is fixable — mostly by admitting that the phone is a triage layer, not the primary editing surface — but you cannot fix them by looking harder in Settings.

The one dimension where mobile wins outright is the one that matters most for actually getting through mail in a spare five minutes: getting to the message. Push notifications, share-to-Outlook from any other app, biometric unlock, one-hand swipes, and native scheduling are all better on mobile than on any Outlook desktop build. If you triage in short bursts between other things, the mobile client is what you should design for. Just do not expect it to be where you build the structure.

At a glance: Outlook mobile app vs desktop, feature by feature#

The table below is sourced from Microsoft's own help articles and from the settings surfaces exposed in the current iOS and Android builds as of August 2026. "Partial" means the capability is present but reduced from desktop in a way that matters for a real workflow, and the specific gap is described further down.

Where the desktop wins outright#

The features below are the ones a desktop user is most likely to notice missing on their phone. They are not oversights — each one exists on the desktop because the desktop has the screen real estate, the keyboard, and (on Windows) the process model to host it. Reproducing them on a phone would either be unusable or require Microsoft to invent a new mobile-native pattern, which is a bigger project than porting a dialog box.

Inbox rules and Quick Steps: read-only on the phone#

You cannot create, edit, delete or reorder inbox rules from the Outlook mobile app. There is no rules surface in Settings, no long-press "create rule from this message" gesture, no rule import. The mobile app is a rules consumer, not a rules editor. Rules you authored on the desktop or on Outlook on the web that live server-side — the kind Exchange runs before mail reaches the client — do keep working, because they run before the message ever touches the phone. That is why a rule filing newsletters into a folder appears to "work on mobile" even though you could not have written it there.

Client-only rules — the ones that run on your Windows PC and can do things like play a sound or run a script — do not run on mobile at all, because there is no client to run them on. If you built a workflow that relies on a client-only rule to trigger a local action, it stops the moment the mail arrives on your phone before your PC sees it.

Quick Steps are a related casualty. Quick Steps let you chain a series of actions — move, mark, reply with a template, forward, set a category — behind a single click on the desktop. There is no Quick Steps surface on mobile, and nothing is planned. The closest mobile analogue is a well-chosen pair of swipe actions plus a schedule, which covers roughly a third of what a Quick Steps power user does on the desktop and no more.

Signatures: plain text, and one at a time#

Outlook mobile signatures are plain text. There is no rich formatting, no image, no logo, no table, no coloured text, no clickable disclaimer block. You get either one global signature applied to every account or a separate plain-text signature per account, depending on which build of the mobile app you are on. That is it.

This surprises people who set up a considered HTML signature on the desktop with a name, title, phone number, calendar link and small logo, expecting it to sync to the phone. It does not, because the mobile signature and the desktop signature are configured in different places and stored differently. The desktop stores rich signatures per-profile; the mobile app stores plain-text signatures in the app itself. There is no sync between them, and there is no signature roaming across surfaces the way there is between two Windows PCs on the same tenant.

The practical workaround is either to accept the phone signature as a triage-shaped signature that says less than the desktop one, or to type your considered signature into the mobile signature field as literal text (name, title, plain-text phone, plain-text URL) and let recipients see the text version when you reply from the phone. Neither approach gives you a logo, and neither is a bug — Microsoft has not shipped a rich-signature editor for the mobile app in ten years and does not appear to be about to.

Search scope: the current account, not all of them#

Outlook desktop lets you search across all your connected accounts at once — a query for an invoice returns hits from Microsoft 365, your Gmail account, and any IMAP account you added, all in a single result list scoped to "All Mailboxes." Outlook mobile does not work this way. The search bar operates within the account you are currently viewing, and switching to a different account for the same query is a manual step: change accounts, retype the query, search again.

This is one of the most visible reductions on the phone, and it is the one that shows up in help forums most often. People assume they have a search index problem when the account they are searching does not contain the message they are looking for; the message is in a different account, and mobile has quietly hidden that from them. The fix is not a settings toggle — it is knowing that mobile search is per-account by design.

Within an account, mobile search itself is reasonable: it hits the server-side search index the same way the desktop does, so results are not limited to what is cached on the device. Filters for sender, folder, date, and attachment are available, and search-across-folders inside a single account works. It is the cross-account boundary that is missing.

Shared mailboxes, delegates and permissions#

Shared mailboxes are one of the areas where Outlook mobile has quietly caught up with the desktop in recent years. You can now add a Microsoft 365 shared mailbox on iOS and Android via Settings, view it in its own account switcher slot, and send mail from it if your permissions allow. That is a real capability that comparison content written even two years ago said the mobile app could not do.

What has not changed is the management surface. To grant someone else access to a shared mailbox, add a delegate to your own mailbox, remove a delegate, or change the permissions a delegate has, you still have to go to the desktop or use Exchange admin controls. There is no delegation surface in Outlook mobile Settings, and there is no shared-mailbox permission editor. If you run a team where an executive assistant is added and removed from mailboxes regularly, that administrative work is desktop-only.

Send-as and send-on-behalf permissions themselves are respected on mobile — once an admin has granted them, the corresponding "From" picker appears in the mobile composer and you can send in the correct identity. But the granting itself is not a mobile action. This is a fair split for security reasons (permission editing on a phone that is easy to lose is a real threat model), and it is the split most enterprises design around: the phone is where the delegate works; the desktop is where the delegation is set up.

Add-ins, categories, PST and profiles#

Add-ins are the sharpest gap and the one most likely to catch out a workflow built around a third-party integration. Outlook desktop hosts the full add-in surface — the classic COM and VSTO add-ins that ship as installers (Salesforce Lightning, DocuSign for Outlook, dictation clients, in-house VSTO deployments) and the modern web add-ins that run inside the same host. Outlook mobile hosts a small subset of the web add-in surface only, and many vendor add-ins that advertise mobile support cover a fraction of the desktop workflow. Test the specific action your team relies on rather than trusting a vendor's "available on mobile" claim.

Categories are a softer split. Mobile can apply and remove categories, filter by category, and show them in the list — the reader experience is intact. What mobile cannot do is create a new category, rename one, change a colour, or manage the category master list. That is a desktop-only surface. In practice this is fine, because categories are a taxonomy you set up once and then use; but a team member joining and needing to add their own category cannot do it from a phone.

PST files do not exist on mobile at all. There is no way to open a PST, no way to import one, no way to reference one as an archive. If your annual routine involves attaching a PST for a matter or a compliance hold, the phone is not going to be part of that routine. Multiple mail profiles — the classic Outlook on Windows feature for switching between two entire configured environments — are also not on mobile; the mobile app treats every account as a peer under one profile, which is the right decision for a phone but is worth stating plainly.

Where mobile wins outright#

Mobile has to concede a lot on the structural side, but conceding it back would be dishonest — there are workflows the mobile app does better than any Outlook desktop build, and they are the workflows that actually get email done in short bursts between other things.

First, notifications and lock-screen behaviour. Outlook mobile ships a genuinely usable push notification pipeline — sender, subject, snippet, and quick actions (archive, delete, mark read, schedule) directly from the lock screen without opening the app. Desktop notifications on Windows or Mac depend on the OS notification centre and do not offer the same one-tap actions from a locked device. If your triage is measured in five-second decisions, the mobile app removes more steps than the desktop.

Second, biometric lock. Outlook mobile has an app-level Face ID / Touch ID / fingerprint requirement that runs even when the phone itself is unlocked, so a colleague glancing at your phone at a coffee shop cannot see your inbox. Desktop builds rely on the OS lock screen for equivalent protection, which is a coarser control. On a device that leaves the house, the app-level lock is the right default.

Third, the share sheet. Every other app on the phone can send content to Outlook — a photo, a PDF, a Safari page, a Files document — as a new message with the attachment already attached. That is a native platform capability desktop cannot match, and it is why the mobile app is often the fastest way to send a document from a phone even if you keep Outlook open on the desktop.

Fourth, one-hand triage. Configurable left and right swipes let you clear the inbox with a thumb, with schedule and archive being the two most common pairings. Combined with the pull-down search and the persistent Focused / Other switch, mobile is genuinely better at getting through a large morning of mail while walking somewhere than the desktop is at a keyboard. The desktop wins the write-a-considered-reply workflow; mobile wins the get-through-fifty-messages workflow.

Pricing: same licence covers both#

There is no separate SKU for Outlook mobile and there is no Outlook mobile paywall. Both the mobile app and the desktop builds are included with the same Microsoft 365 subscriptions and, for classic Outlook on Windows, the same perpetual Office licences that already entitle you to Outlook. Downloading the app is free from the Apple App Store or Google Play, and there is no in-app upgrade required to unlock the features covered in this comparison.

What Microsoft does gate behind Microsoft 365 licensing is the mailbox itself — Exchange Online, the shared mailbox, and the delegated permissions all sit on the server side, and their availability is licensing-shaped rather than app-shaped. If you can use Outlook on the desktop today, you can install Outlook mobile with the same credentials and get the same mailbox, minus the desktop-only capabilities described above.

Microsoft 365 pricing changes periodically and any number a comparison article printed today would age badly. Check the live Microsoft 365 plan pages for what your specific licence costs, and if you are considering Copilot for Microsoft 365, price that separately — it is a distinct per-user add-on and its features live on the desktop and web before landing on mobile.

Who each is genuinely for#

The right answer is almost always both, with a clear split of labour. That is not a hedge — it is the shape Microsoft designed the two surfaces to fit together. Concretely:

• Use Outlook desktop as your primary client if your day involves writing rules regularly, sending mail from a shared team mailbox that you manage, maintaining a rich HTML signature, filing across many folders manually, running third-party desktop add-ins, or working with PST files. Any of those alone tilts the balance toward desktop; two or three make mobile a supporting client only.
• Use Outlook mobile as your primary triage layer if your work is mostly reading, replying briefly, confirming meetings, and clearing volume — and you are willing to accept that structural work (rules, signatures, delegation, add-ins) happens on the desktop. This is the pattern for most executives, most field workers, most people who spend the working day in meetings and want the inbox handled between them.
• Run both, deliberately, with the split above in mind. The mistake to avoid is expecting the mobile app to grow into the desktop over time. Ten years of Outlook mobile updates suggest it will not — Microsoft is building the mobile app as a phone-shaped client, not a smaller desktop, and that is the right decision. Plan for the split rather than fighting it.

A third option, honestly#

This comparison is between two Microsoft builds of the same client. If part of the reason you are reading it is that Outlook itself — either surface — is not really the workflow you want, that is a different question worth naming separately. Third-party mobile clients like Spark and Apple Mail each handle Microsoft 365 accounts to varying degrees, with their own trade-offs around delegation, categories and shared mailboxes.

We build AI Emaily, an AI-native email client that connects to Microsoft 365, Gmail and IMAP with an approve-before-send agent and a full undo and audit trail. On mobile our iOS app is native; on Android we ship a PWA rather than a native app today. It does not replace the deep Exchange features Outlook desktop wins on above — no COM add-ins, no PST support, no shared-mailbox permission editor — and we are not going to pretend otherwise. Where it fits is the triage layer that Outlook mobile already occupies: reading, drafting in your voice from a Personal Context brain and per-client profiles (not from your past mail), and closing loops without you touching them. If that is the shape of the problem, start with a 7-day free trial on Pro or Autopilot — card at signup, nothing is charged if you cancel before day seven. Check AI Emaily pricing for what each tier covers. We build AI Emaily.