Your company configures an environment that contains Skype for Business 2019 on-premises and Teams. Direct Routing is enabled for the company. The manager plans to move common area phones used…

Question

Options

• AService Support admin
• BGlobal administrator
• CCSServerAdminstrator
• DTeams Device Administrator
• ETeams Communications Support Engineer

• A
  16% (7)
• B
  70% (31)
• D
  5% (2)
• E
  9% (4)

Explanation

Moving common area phones from Skype for Business on-premises to Teams requires administrative control on both sides of the migration boundary. Global Administrator (B) holds full Microsoft 365 authority and can manage Teams licensing, policies, and device assignments needed on the cloud side. CSServerAdministrator (C) is the Skype for Business Server on-premises RBAC role that grants full control over SfB Server resources - without it, you cannot manage or release the on-premises phone objects to begin the migration.

The distractors fail for distinct reasons: Service Support Admin (A) only opens and manages service requests and has no device or telephony management rights. Teams Device Administrator (D) manages devices already enrolled in Teams but has no authority over on-premises Skype for Business objects, so it can't initiate the move. Teams Communications Support Engineer (E) is a read-only troubleshooting role for call quality data - it cannot modify or migrate anything.

Memory tip: Picture a bridge between two buildings. You need a key for the door on the on-premises side (CSServerAdministrator) and a master key for the cloud side (Global Administrator). Roles that only work inside one building - or are just maintenance staff - can't unlock both doors.

No community discussion yet for this question.