Choosing the Right Number for Microsoft Account Verification

One-time code or a number you keep: which fits your Microsoft account?

Decide this first, because Microsoft accounts tend to come back for another code later.

• OTP Gateway suits a single verification: confirming a test Outlook.com sign-up, checking how your own app's "Sign in with Microsoft" onboarding behaves, or reproducing a QA case. The number serves one code inside a 20-minute window and is then gone.
• Dedicated Virtual Number suits an account the team must keep using: a shared operations mailbox, a staging tenant admin, or anything where Microsoft may later send a code to the security-info phone. These lines are available in the United States and Canada, from $1.95/month, renew from the wallet, and forward inbound SMS to your webhook.

If you add a gateway number as security info, you lose access to it once the activation ends. For anything long-lived, use a Dedicated Number or a phone your business controls. The comparison in temporary vs dedicated numbers goes deeper, and the virtual numbers page covers renewal.

When does Microsoft ask for a phone number?

A Microsoft account covers Outlook.com and Hotmail mail, OneDrive, Teams, Xbox and Microsoft 365 sign-ins. Phone verification shows up in a few familiar places: during account creation when Microsoft wants extra confirmation, when adding a phone as security info, when a sign-in looks unfamiliar and Microsoft wants to confirm it is you, for two-step verification, and in account recovery. The SMS usually contains a short numeric security code. The exact prompts change over time and differ by region, so build tests around the code itself rather than a specific screen.

Requesting a Microsoft verification code through the API

Authenticate to https://otproute.com/api/v1 with a Bearer key prefixed or_live_. The service id is microsoft.

1. Fetch the price with GET /api/v1/prices?country=<id>&service=microsoft.
2. Create the activation with POST /api/v1/activations and {"service": "microsoft", "country": "us"}, changing the country id to match your test.
3. Enter the returned number at Microsoft's prompt.
4. Receive the code through the activation.sms_received webhook, or poll GET /api/v1/activations/{id}.
5. Call POST /api/v1/activations/{id}/cancel if the test is abandoned.

For webhooks, check X-OTPRoute-Signature (t=<unix>,v1=<hex>) by recomputing HMAC-SHA256 over "<t>.<raw body>" with the endpoint secret, reject old timestamps, and make the handler idempotent on the activation id. Handle activation.expired and activation.cancelled too. Limits: 10 keys, 5 webhook endpoints, 300 requests per minute.

Which countries can receive Microsoft and Outlook codes?

The microsoft service is currently listed in 198 countries. Choose the country that matches the account's market or the scenario you are reproducing, since Microsoft may adapt prompts and language to the number's region. Options include the United States, Canada, the United Kingdom, Germany, India, Brazil, Mexico, Argentina, Greece, Poland, Japan, Nigeria, South Africa, the Philippines, Australia and Papua New Guinea. Availability changes through the day, so read GET /api/v1/countries before a batch.

Ordering a number for Outlook in the dashboard

1. Create an account at signup with an email and a 6-digit code, or Google sign-in.
2. Top up the wallet by card or with USDT/USDC; each top-up comes with a PDF invoice.
3. Open the OTP Gateway, pick Microsoft & Outlook and a country, and confirm the displayed price.
4. Type the number into the Microsoft screen and watch the activation for the code.

There is no monthly fee or plan; the wallet is pay as you go. A development account can be moved to sandbox on request for simulated end-to-end tests.

Why might the Microsoft code not arrive?

Microsoft can decline virtual numbers, limit how many codes it sends in a short span, or route the prompt to another method such as an authenticator app. Delivery time also depends on the route. Let the 20-minute window run; if nothing arrives, or you cancel, the full amount returns to the wallet automatically. Then try later, try another country route, and avoid re-ordering in a tight loop. The article on reducing failed OTP deliveries lists more checks.

Using Microsoft verification responsibly

Follow Microsoft's terms: one account per real person or business, and no attempts to sidestep its security checks. OTP Route is meant for testing your own products and operating your own legitimate accounts, and its Acceptable Use Policy applies. Microsoft, Outlook and related names are trademarks of their owner, and OTP Route has no affiliation with Microsoft.

Frequently asked questions

What is the service id for Microsoft in the OTP Route API?

It is microsoft, used in the service field when creating an activation and in the prices query.

Can I use a virtual number for Microsoft security info?

Only a number you keep. A Dedicated Number in the US or Canada works for that; a one-time gateway number expires after its 20-minute window.

How much does it cost to receive a Microsoft OTP?

From $0.20 per code, depending on country; the live price is returned by GET /api/v1/prices.

Does Microsoft accept every virtual number?

No. Microsoft may reject some numbers, and in that case the activation is refunded when no code arrives.

Can I test Outlook SMS verification for testing in CI?

Yes. Create activations by API, receive codes by webhook, and add back-off so failed attempts do not loop.

Which country should I pick for an Outlook phone number?

Pick the market the account or test case belongs to, since prompts and language may follow the number's region.

Service names are trademarks of their respective owners. OTP Route is not affiliated with them. Use numbers lawfully, follow each service's terms and our Acceptable Use Policy.