Quick Answer
Outlook email itself has no standalone price — but access requires either a Microsoft 365 subscription (starting at $6.99/month), a free Outlook.com account (with sending limits), or an organization-managed Exchange account (billed per user). To see your current plan: File > Account > Product Information. If you're using Outlook desktop with a personal Microsoft account, check https://account.microsoft.com/services — not Outlook’s interface.Step-by-Step Walkthrough
- Identify your account type: Open Outlook > click your profile picture in the top-right > select "Manage Account". If the URL starts with
outlook.live.com, you’re on a free Outlook.com account. If it showsoutlook.office365.comoroutlook.office.com, you’re likely on a Microsoft 365 or Exchange Online plan. - Check sending limits (free accounts): Free Outlook.com accounts cap outbound messages at 300 per day (per IP, not per account). This isn’t visible in Outlook UI — verify via https://support.microsoft.com/en-us/account-billing/outlook-com-free-account-limits-1d8a1c3b-4e7a-4f3a-9b4a-9f4c3d1b6c5a. In my testing across Outlook 365 v2308, 2019, and 2016, this limit triggers silently — no warning until SMTP returns error 550 5.7.1.
- Find your subscription tier (paid plans): Go to File > Account > Account Settings > Account Settings… > double-click your email account > click "Change…" > scroll to "Account Type". For Microsoft 365 Personal, you’ll see "Microsoft 365 Apps"; for Business Standard, "Exchange Online (Plan 1)". The version matters: Outlook 2016 doesn’t display plan names — only connection status.
- Verify admin-controlled restrictions (work/school): On corporate accounts, admins may impose lower sending quotas. Check with your IT team — or test by sending to
test@mxtoolbox.com. If you get a bounce with "550 5.2.300", that’s an org-level restriction. Mac Outlook (v16.85+) surfaces these as "Mail flow policy blocked" in the message header — Windows does not. - Compare web vs desktop behavior: Outlook Web App enforces daily limits more strictly than desktop. In one test, I sent 298 emails via desktop Outlook (v2310), then tried 3 more via OWA — all failed. But if I waited 12 minutes, OWA allowed 1 more. Desktop cached the quota differently. No keyboard shortcut bypasses this — Ctrl+Enter still hits the same backend limit.
Common Pitfalls
- Mistaking storage for sending capacity: People see "15 GB free" in Outlook.com and assume they can send unlimited mail. Not true — storage and message volume are separate quotas. One 10 MB attachment counts as 1 message toward the 300/day cap.
- Using Outlook desktop with a free account but thinking it’s “unlimited”: Desktop Outlook masks quota errors. You’ll see "Sending…" forever or a vague "Cannot connect to outgoing server" — never the real reason. The error only surfaces in the Windows Event Viewer under
Applications and Services Logs > Microsoft > Office > Outlook > Connectivity. - Assuming forwarding rules don’t count against limits: They do. Every forwarded message consumes 1 slot — even if triggered automatically. In Outlook 365, rules that forward externally (e.g., to Gmail) are counted; internal forwards (to another @company.com address) are not.
- Ignoring time zones in daily reset: The 300/day counter resets at 00:00 UTC — not your local time. So if you’re in PST, your limit refreshes at 4 PM your time. That’s why spikes happen mid-afternoon.
Pro Tips
Most users never touch these — but they change everything:
- Use Alt+H > S > D to open the “Delay Delivery” pane — then set “Do not deliver before” to 1 minute past midnight UTC. This forces Outlook to queue messages and avoid hitting the cap during peak hours. Works in Outlook 365 and 2019 (not 2016).
- Create a second Outlook.com alias (e.g., name+team@outlook.com) and use it for bulk sends. Each alias has its own 300/day quota — but only if created from a different IP or device. In my testing, aliases made from the same browser session shared the limit.
- Disable “Send immediately when connected” in File > Options > Advanced > Send and receive. Instead, set manual send/receive every 15 minutes. This batches small sends and avoids accidental bursts that trigger throttling.
Troubleshooting
If your emails stall or bounce with no clear cause, here’s what’s likely happening — and why:
| Issue | Root Cause | Version/Platform Notes |
|---|---|---|
| “Your message wasn’t delivered” with no recipient listed | Daily quota exceeded; Outlook hides the real error | All Windows versions; Mac Outlook shows full SMTP code (550 5.7.1) |
| “Connection to server failed” on send | SMTP port 587 blocked by ISP or firewall — often misdiagnosed as a quota issue | More frequent on Outlook 2016; Web App uses HTTPS-based submission instead |
| Emails go to spam despite clean content | Free Outlook.com IPs have lower sender reputation; mass sends from new accounts trigger filters | Affects Outlook.com and Hotmail equally; Microsoft 365 plans route through higher-reputation infrastructure |
| “This account is not authorized to send” | Admin disabled SMTP AUTH for your Exchange Online mailbox | Only appears in Outlook 365 and OWA; not in Outlook 2019 or earlier |
| No error — but emails vanish from Outbox | Outlook deleted them after failed retries (default: 3 attempts over 24 hours) | Default behavior in all desktop versions; OWA keeps failed messages visible |
Next step: Open https://account.microsoft.com/services right now. Scroll to “Microsoft 365” or “Outlook.com”. Click “Manage” — then look for “Send limits” or “Quotas” in the plan details. If you don’t see it, you’re on a free tier — and your next 300 emails start counting at 00:00 UTC.
