The Send button in Outlook greys out because Outlook has no valid way to deliver the message: it cannot resolve an address, has no connection to a mail server, is missing an account, or is enforcing a policy. Classic Outlook's offline state, unresolvable recipients, and expired Microsoft 365 licenses are the most common triggers. New Outlook and Outlook on the web grey out Send for a different reason: the draft has not saved to the server yet.
Most people assume a greyed-out Send button means Outlook is broken. Usually it means Outlook is protecting you from sending something it cannot deliver or store. The button is a state indicator, not a fault light. Once you know which state Outlook is in, the fix is usually a few clicks.
How Outlook decides to disable Send
Outlook does not run one check before enabling Send. It runs a stack of preconditions, and any single failure can grey the button. The message must have at least one resolvable recipient, a sending account with valid credentials, a route to the outgoing server, and, in the new Outlook and web versions, a confirmed server-side save of the draft. Classic Outlook evaluates these independently and disables Send when the weakest link fails.
The most instructive case is the modern save pipeline. New Outlook and Outlook on the web autosave drafts to the mailbox before sending. If that save fails, Outlook treats the draft as unpersisted and blocks Send, because sending an unsaved message risks losing it. This is why the button can look dead even when you are online and every address looks correct. The blocker is storage, not delivery.
Classic Outlook behaves differently. It checks addresses against the local address books and the server, checks whether the account is in an offline state, and checks whether the outgoing server is reachable. An unresolved recipient in the To, Cc, or Bcc line is enough to disable Send until the name resolves or you remove it. Ambiguous names that match multiple contacts can also hold the button in a disabled state.
A fifth gate is policy. Microsoft 365 compliance settings, mail flow rules, and sensitivity-label requirements can block sending until the message meets a condition. Examples include mandatory encryption for external recipients or a required label. When policy is the cause, Outlook typically shows a banner or a bar above the message rather than only greying the button.
The professional caveat: the button's appearance is a UI signal, not a diagnostic. Two machines with identical symptoms can have completely different root causes. Read the status bar, the info bar above the message, and any notification before changing settings.
The offline state and connection gates
Classic Outlook holds an explicit offline state that disables all sending. The status bar at the bottom of the window shows "Working Offline" when this is active. The toggle lives under the Send/Receive tab as Work Offline. Outlook can also enter this state automatically when it loses its connection to the Exchange server, then stay there after the connection returns until you toggle it back.
Connection gating works at several layers. Outlook may have a network connection but no route to the mail server, or the server may be reachable while authentication fails. Expired credentials, a changed password on another device, and conditional access policies all produce a disabled Send with little visible explanation beyond a credentials prompt you may have dismissed.
Cached mode adds a wrinkle. Outlook works from a local cache and syncs in the background. If the cache is corrupted or the mailbox is over its quota, synchronization stalls, and sending can be held. Mailbox quotas are a common silent cause in managed environments: once the mailbox exceeds its limit, the server refuses new items and Outlook reflects that refusal by blocking Send.
Quantify the practical range: typical corporate mailboxes carry quotas between 50 GB and 100 GB, and consumer Outlook.com mailboxes commonly sit around 15 GB of storage shared with OneDrive photos. A mailbox at 99 percent of quota can still receive but fail to send, because sent items and drafts also consume space. That asymmetry surprises people: receiving works, sending does not.
Counterintuitive detail: deleting items from Deleted Items is often not enough, because the mailbox counts items in Recoverable Items until the retention period expires. A mailbox that looks empty can still be full for up to 14 to 30 days depending on retention policy.
Address resolution and the autocomplete cache
The recipient field is a resolution engine. When you type a name, Outlook matches it against contacts, the global address list, and the autocomplete cache. A name that matches nothing stays underlined or unresolved, and Send remains disabled. A name that matches multiple entries can also block sending until you pick one.
The autocomplete cache is the usual culprit in day-to-day use. It stores recently used addresses in a local file, and stale entries for departed colleagues or changed domains persist there. Outlook can show a resolved-looking chip for an address that no longer exists on the server. The send attempt then fails, or the button stays greyed until you delete the stale entry and re-resolve the name.
Distribution lists complicate resolution further. An expired or permission-restricted list may resolve locally but be rejected server-side. In that case the button may enable, the send may fail, and the failure appears as a non-delivery report rather than a greyed button. The two symptoms point to the same underlying resolution problem but arrive at different stages.
Plain-language version: Outlook has to know exactly who you mean and confirm the address is valid before it lets you commit. If it is unsure, it keeps the button off.
Edge cases: shared mailboxes, licenses, and add-ins
Shared mailboxes are a frequent edge case. A shared mailbox without its own license can be opened and read, but sending from it requires Send As or Send on Behalf permissions. Without those permissions, the From field shows the shared address but Send is disabled or the message fails immediately. The fix is an administrator action, not a client setting.
License state matters in Microsoft 365. An expired subscription, an unassigned license, or a license transition in progress can leave Outlook in a reduced mode where sending is blocked. The client may still open and display cached mail for a period, which makes the failure look random. Check the account status in the Microsoft 365 admin center before troubleshooting the client.
Add-ins can intercept the send pipeline. Some CRM and compliance add-ins attach a send handler that blocks sending until the add-in finishes tagging or logging the message. When the add-in errors, Send stays greyed. Starting Outlook in safe mode, which disables add-ins, is the fastest test: if Send works in safe mode, an add-in is the cause.
There is also a version-specific bug class. New Outlook and web Outlook occasionally show a disabled Send after a failed autosave even when connectivity is fine. A refresh of the page or reopening the draft usually clears it, because the retry succeeds and the save state flips.
Red-flag warnings to treat as stop signs:
A banner demanding credentials you did not expect to enter; verify the sender before typing a password. A notice that your organization requires a sensitivity label or encryption before sending. A prompt about mailbox quota or storage that repeats after you delete large items. An error naming a policy or compliance rule by ID. Any message that sends you to a non-Microsoft domain to "re-authenticate" your account.
Common misconceptions
Misconception one: the greyed button means Outlook is offline. Offline is only one of several gates, and in modern Outlook it is often not the cause. Misconception two: restarting Outlook fixes it. Restarting clears transient save failures but does nothing for permissions, quotas, or stale addresses.
Misconception three: the problem is the recipient's server. A bad recipient address on the other end produces a bounce after sending, not a disabled Send before sending. If the button is greyed, the failure is local or account-level. Misconception four: reinstalling Office is a reasonable next step. Reinstallation is slow, disruptive, and almost never relevant to a send gate that lives in account state or message state.
The useful mental model: a greyed Send button is a pre-flight failure. It happens before the plane leaves, not during the flight. Bounces and non-delivery reports are in-flight failures. Confusing the two wastes the most time.
A step-by-step diagnostic path
Work from the message outward, then from the client to the account. Each step isolates one gate.
Check the status bar and any info bar above the message; read the exact wording and act on it first. Remove and re-add the recipient, or delete the stale autocomplete entry, then re-resolve the name. Toggle Work Offline off under Send/Receive if the status bar shows it. Confirm the sending account: correct From address, valid license, and for shared mailboxes, confirmed Send As permission. Test in safe mode or with add-ins disabled; if Send works, disable add-ins one at a time. Check mailbox storage and quota in account settings; empty Deleted Items and the Recoverable Items folder if permitted.
Reconcile the thresholds explicitly. Offline state is binary: either Work Offline is on or it is not. Quota is a percentage of a plan-specific limit, so the meaningful check is your mailbox's reported usage against its stated limit in account settings, not a universal number. Permission failures are binary as well: the permission is present or absent. Save-state failures are transient and usually clear on a retry or a draft reopen. Treat binary causes first because they are fastest to confirm.
| Symptom | Most likely cause | First action |
|---|---|---|
| "Working Offline" in status bar | Offline toggle or lost server connection | Turn Work Offline off |
| Recipient chip unresolved or ambiguous | Address resolution failure | Re-resolve or pick the correct contact |
| Send dead only in new Outlook or web | Draft autosave failed | Reopen the draft or refresh the page |
| From shows a shared address, Send dead | Missing Send As or Send on Behalf permission | Ask an administrator to grant it |
| Info bar names a label, rule, or policy | Compliance or mail flow gate | Apply the required label or contact IT |
| Quota warning repeats after deletions | Mailbox storage limit | Clear Recoverable Items or request a larger quota |
| Send works in safe mode only | Add-in intercepting send | Disable add-ins one at a time |
Timeline: how a stuck send typically resolves
| Elapsed time | What happens |
|---|---|
| 0 seconds | Send is greyed; status bar or info bar shows the gate |
| Seconds to a minute | Transient autosave failure retries; reopening the draft often restores Send |
| Minutes | Credentials re-prompt completes or fails; sign-in state updates |
| Hours | Server-side sync catches up after connectivity returns; cached mode updates |
| Hours to a day | Administrator grants or corrects shared mailbox permissions |
| One retention cycle | Deleted items clear from Recoverable Items, freeing quota |
| Days | License or subscription issue is corrected in the admin center |
The timeline is a guide, not a guarantee. Transient save and sync issues typically clear within minutes. Permission, license, and quota issues need someone with administrative access, so they resolve on a working-day timescale rather than a technology timescale.
What you cannot fix from the client
Some causes sit entirely outside the desktop app. Mail flow rules, transport rules, data loss prevention policies, and tenant-level compliance settings are configured in the Microsoft 365 admin center or by security teams. When one of these blocks sending, the client can only display the condition, not resolve it. The same is true of license assignment and shared mailbox permissions. Recognizing the boundary early saves hours: if the info bar names a policy or your account shows no license, the path forward is a support request, not a settings change.
There is also a data-integrity limit. A corrupted local profile or Outlook data file can produce send failures that survive every message-level fix. Creating a new Outlook profile is the standard remedy, but it is a last step because it costs time and does not address account or policy causes. Treat profile rebuilds as the final tool, not the first.
Finally, the article cannot tell you why your specific button is greyed. The gates above cover the overwhelming majority of causes, and the diagnostic order is designed to find the active one quickly. If the status bar, info bar, and account settings are all clean and Send is still dead, the remaining suspects are server-side and organizational, which means your IT administrator has the visibility you lack.
This article is general educational information about software behavior, not a diagnosis of your specific account or a guarantee of any outcome. For issues involving organizational policy, licensing, or permissions, consult your IT administrator or Microsoft support.