How to Use Microsoft Number Checker for Bulk List Checks

In the Microsoft ecosystem, a phone number is not a contact detail. It is an identity anchor: the MFA code receiver, the recovery path, the guardian of a shared account. The check is not about whether numbers are "correct." It is about whether they can still do their job. Microsoft Number Checker is the ZelNum page designated for this job: Microsoft Number Checker.

Quick answer

Prepare a CSV with one number per row and a record ID, run the check, and read each row as an identity-health signal. A number that passes format checks can still fail the job: a landline cannot receive MFA codes, and an ex-employee's number may be valid but no longer under company control. Route by what the number is supposed to do.

Pick the right entry point

The check runs three ways, and picking the wrong one wastes either time or coverage:

• Single lookup — the help desk path. A user is locked out now; check the one number and answer in seconds.
• Bulk upload — the review path. Directory export, quarterly ledger, work the flags.
• API jobs — the automation path. Scheduled drift monitoring and offboarding-triggered re-checks.

Most IT teams live in bulk upload but need the single lookup more often than they expect. Keep both bookmarked.

Step 1: Prepare the file

One phone number per row, a record ID, and, if the list mixes roles, a role column: login, recovery, MFA, shared account. The role tells you what "valid" has to mean for that row.

Step 2: Run the check

The export returns a status per row: valid and SMS-capable, valid but not SMS-capable, invalid, or unknown.

The middle row is where the check earns its keep. A landline passes every format check and cannot receive an MFA code, which makes it a lockout waiting to happen.

Step 3: Read by role

• Login and MFA numbers need SMS capability. A valid-but-not-SMS-capable row here is an access risk.
• Recovery numbers need to be current. A stale recovery path is how accounts get locked out.
• Shared-account guardians need to belong to someone still at the company. An ex-employee's number may be valid and now owned by a stranger.

Say an IT team has 12,100 numbers in an access review. The pilot comes back 68% valid and SMS-capable, 17% valid but not SMS-capable, 11% invalid, 4% unknown. (Figures below are sample outputs for context, not benchmark targets.) The 17% are the rows that change the review from a hygiene pass into an access decision.

Step 4: Sort the 17% by scenario

The same status needs different handling depending on why the number is in the list:

• Enterprise lead validation. A lead whose number cannot receive SMS is a dead contact. Suppress it from outreach and note the reason; no urgency, no escalation.
• Email deliverability protection. Numbers attached to notification and alert flows fail silently when they cannot receive SMS. Flag them before the alert chain depends on a dead receiver.
• Vendor and partner review. A partner contact number that went landline or dead means two-factor codes will stop arriving the next time their system challenges. Treat it as an operations risk, not a data-quality footnote.
• Internal identity rows. The access-decision tier: replace or re-provision, highest priority, before the lockout.

Step 5: Route and re-check

• Replace or re-provision numbers that cannot do their job.
• Re-check quarterly, and immediately after any offboarding wave, because employee departures are when guardianship quietly changes.

Mistakes to avoid

• Treating every valid number as MFA-capable. The format check and the SMS-capability check are different jobs.
• Checking once and calling it done. A number that checked out in January is not a promise for July, especially after offboardings.
• Treating "valid" as "under our control." The check says the number works. Ownership is a separate question.
• Working the flags as one pile. A dead lead number and a dead MFA number share a status and nothing else.

FAQ

What does SMS-capable mean?

It means the number can receive text messages, which is what MFA and recovery flows depend on. A landline or a VoIP number that cannot receive SMS fails the job even when the format is perfect.

Why is a Microsoft number an identity asset?

Because it carries the MFA codes and recovery paths for accounts. A stale or wrong number is not a data error, it is an access problem.

How often should I re-check?

Plan on a quarterly cycle, and immediately after offboarding waves. Guardianship changes when people leave.

What should I do with valid-but-not-SMS-capable rows?

Flag them and replace them in the account settings. They are a lockout waiting to happen, especially for login and MFA roles.

Does the check prove ownership?

No. It reports what the check's signal shows. Who controls the number is a question for the account-side data.

Related ZelNum pages

• Microsoft Number Checker Use Cases showing how each team reads the results.
• Microsoft Number Checker API Workflow for scheduled runs.
• Bulk Microsoft Number Checker: the batch-file guide with the format gotchas covered.