Buying Outlook accounts for API access: what to check

If your app needs to read an Outlook inbox, the first question is not “How many accounts?” It is “How does this app connect?” A tool that asks for an email and password is asking for something different from a tool that needs a Microsoft sign-in or a token. Sort that out before choosing a package.

This checklist covers the delivery formats in our Outlook catalogue. It is not a claim that every app accepts every delivered credential. The same distinction matters when choosing Hotmail packages.

Start with the app, not the package size

Open the connection settings or ask the app vendor which interface it uses. Look for one of three answers: browser sign-in, Microsoft Graph, or IMAP/SMTP. “Supports Outlook” is not specific enough. Also check whether the app supports personal Outlook.com accounts, rather than only work or school accounts.

Write down the required fields exactly. If the tool needs an interactive Microsoft login, a file import is not automatically a substitute. If it expects a token, ask which token type it accepts and how it handles renewal. You should not have to guess these details after paying.

What Standard and Full actually contain

Our Full format is described for Graph API access. That does not mean it plugs into an arbitrary IMAP importer. A client ID is not a password, a recovery address is not an API permission, and the word “oauth” does not describe a token’s complete capabilities.

IMAP is not the outdated version of OAuth

They do different jobs. IMAP handles mailbox synchronization; OAuth handles access authorization. IMAP can use OAuth. The outdated connection method in this comparison is password-only Basic Authentication for Outlook.com, not IMAP itself. Microsoft’s Outlook.com settings require Modern Auth/OAuth2.

For a new integration, compare what your app actually supports instead of choosing a label that sounds newer. Graph and IMAP expose different interfaces. The Outlook connection guide covers server settings and troubleshooting after delivery.

Ask these questions before ordering for API use

• Does my app need Graph or IMAP/SMTP, and does it support personal Microsoft accounts?
• What does the OAuth field contain: an access token, a refresh token, or another value?
• Which service and permissions is the token intended for?
• Does the app require its own registration or an interactive consent step?
• How are token expiry, renewal and revoked access handled?
• Can we confirm a compatible redacted field layout before I place a larger order?

For context, Microsoft documents listing messages through Graph separately from OAuth authentication for IMAP and SMTP. Successful access to one interface is not evidence that the other is ready.

One small check before a bigger order

Ask support to confirm the format for your named app. Then test a small order in that exact workflow: sign in as supported, read a message in an inbox you control, and check how the connection survives a restart. If sending is part of the requirement, test it separately. Record the outcome without copying secrets into tickets.

A useful support message is: “I use [app and version], need [Graph or IMAP], and the importer asks for [field names]. Does your Full format match?” That is much easier to answer than “Does API work?” Never include a working token or password in a public example.

Choose the format deliberately at checkout

Each Outlook or Hotmail item has its own delivery-format selector in the basket. Select Full when that is the format you have confirmed with support. For Standard, the order text says [Format: email:password]; for Full, it lists the extended fields. The pack count is separate: 3x 100 Outlook.com Emails means three 100-account packs.

Review our terms and the provider’s conditions before ordering. A store purchase does not grant additional Microsoft permissions or change the rules for using the service. When the requirements are clear, compare the current Outlook packages.