0% found this document useful (0 votes)
14 views67 pages

Planning Microsoft Teams Android Devices

This document outlines the planning and deployment process for Microsoft Teams on Android devices, focusing on device selection, account creation, and deployment logistics. Key considerations include procurement, consistency, scalability, and operational readiness, along with training and security measures. It also details the steps for configuring resource accounts and assigning phone numbers for various device types within an organization.

Uploaded by

Donald Rye
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
14 views67 pages

Planning Microsoft Teams Android Devices

This document outlines the planning and deployment process for Microsoft Teams on Android devices, focusing on device selection, account creation, and deployment logistics. Key considerations include procurement, consistency, scalability, and operational readiness, along with training and security measures. It also details the steps for configuring resource accounts and assigning phone numbers for various device types within an organization.

Uploaded by

Donald Rye
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Planning and Deploying Microsoft

Teams on Android Devices


Module 2
Deploying devices throughout your
Objectives organization

Selecting the right devices for your


users and spaces

Understand how to create resource


accounts and assign phone numbers
Feature availability icons

Available Partial Not available

Teams phones

Teams displays

Teams Rooms

Teams panels
Considerations and goals

Procurement – Account for and Options – Ensure all devices Shipping – Ensure all items are
manage all individual are standardized, accessible, delivered to sites prior to
components including and meet the needs of your deployment, asset tagged, and
regionalizing for power, network users and spaces. inventoried where applicable.
requirements (POE/POE+).

Consistency – Centralize the Scalability – All aspects are


process so that every system intentional, controlled,
across customers and rooms use trackable and supportable
consistent components.
The big picture

Envision Onboard Drive value

Inventory
spaces
& plan Device Site Service Configuration Maintenance
capabilities selection Procurement readiness readiness & deployment Adoption & operations

Facilities Devices team IT project team


Room/space inventory Plan Network readiness (POE)
Hang/drill/power Configure Provision/configure
Signage Install Scale
Support Monitor/maintain
Envision personal device
deployment

Standardize device definitions


Desk phone or Teams display
Handset/Speakerphone
Meeting join capabilities

Options
Camera
Sidecar
Envision Teams Rooms
deployment

Standardize meeting
room definitions
Size
Layout
Number of people
Desired modalities

Options
Teams panels
Teams Rooms console
Touch enabled display
Device selection: Phones and Displays

Call center Information Executive Shared Retail


Worker space

Basic phone, Teams Display Teams Display Basic phone, Basic phone,
large screen small screen medium screen
Productivity Feature rich video
phone phone Conference
phone
Sidecar for
delegates
Device selection – Teams Rooms

Executive Shared
space

End User Account Resource Account

Executive office Console or Remote control

Single touch-enabled display Single or dual display

Teams panel
Use distributor logistics
best practices

Avoid multiple sources, centralize where possible


Ship to central location, if needed

Plan for product delays


Deployment schedules are a life saver!

Request MAC addresses if provisioning devices


remotely
Developing a
standardized deployment
Installation
Account provisioning hand-off
Create and configure accounts in advance
Use remote provisioning where possible for ease
of deployment

Create and communicate standards


Step-by-step instructions
Cable dressing
Mounting locations and methods
Device setup instructions and configuration
profiles
Basic troubleshooting
Microsoft Teams is great for ongoing cross-team
coordination!
Operations

Have clear escalation paths


during this critical time
Account types

User Common area Meeting room

Used by end users who will Used for devices that are not Used for devices that are
answer calls, be a delegate, owned by any single person, shared among many people,
or be in a call queue such as a phone in a kitchen such as Teams Rooms and
or lobby Teams panels.
Training and enablement

User training

IT training

Awareness
Operational readiness

Device repair

Out of service

Helpdesk readiness
Network bandwidth planning

Determine and organize network


requirements for connecting Microsoft
Teams users across your organization.

Network Planner calculates your network


requirements for deploying Teams and
cloud voice across your organization's
physical locations.

https://aka.ms/TeamsRoomsLearning
Network connectivity testing

OneDrive, Outlook, and Teams


report network metrics to the
tenant

The metrics are aggregated to a


geographic region, allowing
administrators to see network
performance

You can manually run a test at


connectivity.office.com
Security

Security isn’t just software, it’s


physical too.

Assess where you deploy your


devices and understand the risks.

Deploy physical locks, disable PC


network ports, and – if needed -
limit some features to harden your
devices.
Resource account

This account can sign into Teams Rooms, Teams


panels, conference phones, or common area phones.

Must be Microsoft Teams enabled

Consider enabling for telephony, as appropriate

For Teams Rooms, this is the account that you invite to


meetings.

Establish a naming convention


Resource account

Teams Rooms requires its own unique account for


each space

One account should be shared between all devices in a


space – Teams Rooms, console, and Teams panel.

It is recommended to create the account in advance of


hardware installation

You can create account via:


Microsoft 365 admin center
PowerShell
Resource account security

Uses modern authentication Sign-in token secured on device


Conditional Access (CA) policies Optional calendar processing for Teams
Rooms and Panels
Recommend using different CA policies for Device
accounts than other User accounts Optional settings using the Set-
• Location based CA policy for device accounts CalendarProcessing Cmdlet

• Microsoft Teams, Exchange, & SharePoint Online CA policies ProcessExternalMeetingMessages, DeleteSubject,


should match DeleteNonCalendarItems, DeleteAttachments,
• Do not enforce multi-factor authentication or Sign in Frequency AddAdditionalResponse, AddOrganizerToSubject
for device accounts

• Do not enforce "Require compliant device" condition for devices


with Hotdesking capability

Do not enforce password expiry for device accounts


Microsoft 365 admin center
Add Common Area Phone account

Navigate to Users -> Active Users

Click on Add a user


Microsoft 365 admin center
Add Common Area Phone account

Fill in appropriate values

Do not select Require this user to change their


password when they first sign in
Microsoft 365 admin center
Add Common Area Phone account

Assign Common Area Phone license

Assign calling plan license.

If you are using Microsoft Phone System Direct


Routing or Operator Connect, you do not need to
assign a Calling Plan license.
Microsoft 365 admin center
Add Common Area Phone account

Review settings

Click Finish adding to create account.


Create account via PowerShell

Connect-MsolService

$UPN='[email protected]'
$DisplayName='Lobby 1 Common Area Phone'
$FirstName='Lobby 1'
$LastName='Common Area Phone'
$Password='HappyPwd!!!'
$PhoneNumber='+13175551212'
$UsageLocation='US'
#Get-MsolAccountSku to list SKU's for next line
$License='contoso:MCOCAP'

New-MsolUser -UserPrincipalName $UPN -DisplayName $DisplayName -FirstName $FirstName -LastName


$LastName -UsageLocation $UsageLocation -LicenseAssignment $License -Password $Password
‐PasswordNeverExpires $True
Resource account creation flow

Configure
Resource Set password Assign Teams Configure
Identify room Calendar Auto
exists to not expire License device
Accept

Create
Exchange
Resource
Microsoft 365 admin center
Add resource account

Sign in to: https://admin.Microsoft.com

Navigate to Resources → Rooms & equipment


Microsoft 365 admin center
Add resource account

See and edit current room inventory

Click +Add resource to create a new room


Microsoft 365 admin center
Add resource account

Fill in appropriate values


Microsoft 365 admin center
Add resource account

Acknowledgement that the room has


been created
Microsoft 365 admin center
Review booking options

Available scheduling options


Microsoft 365 admin center
Set password

Navigate to Users -> Active Users

Click on key icon to set password


Microsoft 365 admin center
Set password

Enter password

Do not tick the box to require a


password change.
Microsoft 365 admin center
Assign license

Navigate to Users -> Active Users

Click on Display name to see properties

Click on Licenses and apps


Microsoft 365 admin center
Assign license

Select license

Click Save changes


Create account via PowerShell

Connect-MsolService
Connect-ExchangeOnline

$UPN='[email protected]'
$DisplayName='St. Petersburg Focus Room 3'
$MailBoxName='MTR-STP-FocusRoom3'
$MailBoxAlias='MTR-STP-FocusRoom3'
$Password=ConvertTo-SecureString 'HappyPwd!!!' -asplaintext -force
$AdditionalResponse='St. Petersburg Focus Room 3'
$UsageLocation='US'
$License='contoso:MEETING_ROOM'

New-Mailbox -MicrosoftOnlineServicesID $UPN -Name $DisplayName -Alias $MailBoxAlias -Room


‐EnableRoomMailboxAccount $true -RoomMailboxPassword $Password

Set-CalendarProcessing -Identity $MailBoxAlias -AutomateProcessing AutoAccept -AddOrganizerToSubject $false


‐DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false -AddAdditionalResponse $true
‐AdditionalResponse $AdditionalResponse -ProcessExternalMeetingMessages $true

Set-MsolUser -UserPrincipalName $UPN -PasswordNeverExpires $true -UsageLocation $UsageLocation


Set-MsolUserLicense -UserPrincipalName $UPN -AddLicenses $ADLicense
Sign-in modes

User mode Common area phone Meeting room

Signs in with E3/E5 license Phones in common areas which Devices in meeting rooms which
do not require user login do not require end user login

Registers with Intune Does not register with Intune Registers with Intune
Provides full feature set No calendar support Optimized calendar UI
Hotdesking supported Hotdesking supported No hotdesking
Sign-in modes
Phone UI Comparison

User mode Common area phone Meeting room


User sign-in with E3/E5 license Phones in common areas which do not Devices in meeting rooms which do
require user login not require end user login
Sign-in modes

override

New-CsTeamsIPPhonePolicy
Grant-CsTeamsIPPhonePolicy

New-CsTeamsIPPhonePolicy –Identity 'User Sign in' –Description 'User Sign In Phone Policy' -SignInMode
MeetingSignIn

Grant-CsTeamsIPPhonePolicy –Identity [email protected] –PolicyName 'User Sign In Phone Policy'


Web sign-in
Web sign-in
Web sign-in
Web sign-in
Web sign-in
Remote provisioning

Remotely provision and sign into a Teams device


using the Teams admin center.

Add an individual device via MAC address or upload


a csv file to add devices in bulk.
Remote provisioning

Select devices to provision and click Generate verification code


Remote provisioning
Remote provisioning
Remote provisioning
Remote provisioning

Teams admin center


Remote provisioning
Remote provisioning
Multi-cloud sign-in
support

Devices now support specialized clouds.

Users can click the gear and switch to


the option applicable to their tenant.

Accessed from the in settings.


Assigning phone number – calling plans

Configurable using Teams admin center.

For USA and Canada, you must create an emergency location first.
Assigning Calling Plan phone number - PowerShell

$UPN='[email protected]'

$PhoneNumber='+14255553223'

#Get Location ID via Get-CsOnlineLisLocation


$LocationID='c04255ef-0aac-4cc8-b5fe-510c4578f792'

Set-CsOnlineVoiceUser -Identity $UPN -TelephoneNumber $PhoneNumber


-LocationID $LocationID
Assigning Direct Routing phone number - PowerShell

$UPN='[email protected]'

$PhoneNumber='tel:+14255553223'

Set-CsUser $UPN -OnPremLineUri $PhoneNumber -EnterpriseVoiceEnabled $true


‐HostedVoiceEnabled $true
Have a plan for deploying devices
Summary
Standardize on devices

Create any required accounts

Assign phone numbers as


necessary
Thank you.

You might also like