You port phone numbers from a legacy earner to Microsoft Teams Phone to use with Microsoft Teams Calling Plans. You attempt to assign a number to a resource account that will be used by an auto…

Question

Options

• ASubmit a request to convert the number from a user number to a service number.
• BRun the Set-CsOnlineApplicationlnstance cmdlet.
• CRun the Set-CsTeamsUnassignedNumber Treatment cmdlet.
• DOrder a new number from Microsoft.

• A
  71% (20)
• B
  7% (2)
• C
  18% (5)
• D
  4% (1)

Explanation

When phone numbers are ported into Microsoft Teams, they arrive as user numbers by default. Auto attendants and call queues are assigned through resource accounts, which require service numbers - a different number type. Because the ported number is still classified as a user number, it won't appear in the available pool for resource accounts. Submitting a conversion request through the Microsoft Teams admin center (or via Microsoft support) changes the number's classification to a service number, making it assignable to the resource account.

Why the distractors are wrong:

• B - Set-CsOnlineApplicationInstance configures properties of an existing resource account (like its display name or application type); it doesn't change how a phone number is classified.
• C - Set-CsTeamsUnassignedNumberTreatment controls what happens when someone calls an unassigned number (e.g., route to a voicemail or auto attendant); it has no role in number type conversion.
• D - Ordering a new number is unnecessary and wasteful - you already own the ported number; you just need to change its type.

Memory tip: Think "Services need Service numbers." Any time a number is going to a resource account (auto attendant, call queue), it must be a service number. Ported numbers land as user numbers - you must explicitly request a conversion before they're usable for services.

No community discussion yet for this question.