You are migrating users from Microsoft Skype for Business to Microsoft Teams. You plan to create an auto attendant that can be used by all the users during the migration. You need to create the…

Question

Options

• Athe Resource accounts node in the Microsoft Teams admin center
• Bthe Users node in the Microsoft 365 admin center
• Cthe New-CsHybridApplicationEndpoint cmdlet
• Dthe New-CsOnlineApplicationEndpoint cmdlet
• Ethe New-CsOnlineApplicationlnstance cmdlet

• A
  8% (2)
• D
  4% (1)
• E
  88% (22)

Explanation

New-CsOnlineApplicationInstance (option E) is the correct PowerShell cmdlet for creating resource accounts for auto attendants and call queues in Microsoft Teams - it provisions the application instance in Azure AD that serves as the identity for the resource account. Option A is a distractor because while the Teams admin center's Resource accounts node is where you assign a license and configure the auto attendant, you cannot create the underlying resource account from there; Option B (Microsoft 365 admin center Users node) is for managing regular user accounts, not resource accounts. Options C and D are legacy/on-premises Skype for Business cmdlets - New-CsHybridApplicationEndpoint is for hybrid on-premises scenarios, and New-CsOnlineApplicationEndpoint is outdated and no longer used for Teams resource accounts.

Memory tip: Think "Instance = Identity" - New-CsOnlineApplicationInstance creates the Azure AD instance (identity) that the auto attendant lives on. The word "Online" confirms it's cloud/Teams, and "Instance" reminds you it's the creation step before any configuration happens.

No community discussion yet for this question.