← cd ~/roles
// roles/entra
Teams Devices AdministratorMicrosoft Entra built-in role
Can perform management related tasks on Teams certified devices.
| Role ID | 3d762c5a-1b6c-493f-843e-55a3b42923d4 |
|---|---|
| Privileged | No |
| Permissions | 2 |
What it can do
| Permission | What it allows |
|---|---|
microsoft.office365.webPortal/allEntities/standard/read | Read basic properties on all resources in the Microsoft 365 admin center |
microsoft.teams/devices/standard/read | Manage all aspects of Teams-certified devices including configuration policies |
Assign it
The role ID is the same in every tenant, so these work as they are. Make it eligible through PIM:
Connect-MgGraph -Scopes "RoleEligibilitySchedule.ReadWrite.Directory"
$user = Get-MgUser -UserId "jane.doe@contoso.com"
New-MgRoleManagementDirectoryRoleEligibilityScheduleRequest -BodyParameter @{
Action = "AdminAssign"
Justification = "Needs Teams Devices Administrator for <reason>"
RoleDefinitionId = "3d762c5a-1b6c-493f-843e-55a3b42923d4"
DirectoryScopeId = "/"
PrincipalId = $user.Id
ScheduleInfo = @{
StartDateTime = (Get-Date).ToUniversalTime().ToString("o")
Expiration = @{ Type = "afterDuration"; Duration = "P180D" }
}
}Who already has it?
Connect-MgGraph -Scopes "RoleManagement.Read.Directory"
Get-MgRoleManagementDirectoryRoleAssignment -Filter "roleDefinitionId eq '3d762c5a-1b6c-493f-843e-55a3b42923d4'" -ExpandProperty Principal |
ForEach-Object { $_.Principal.AdditionalProperties.displayName }Related roles
- Agent ID Developer · 2 permissions
- Attack Payload Author · 2 permissions
- Attribute Definition Administrator · 2 permissions
- Attribute Definition Reader · 2 permissions
- Attribute Log Administrator · 2 permissions
- Cloud App Security Administrator · 2 permissions
- Customer Delegated Admin Relationship Administrator · 2 permissions
- Customer Lockbox Access Approver · 2 permissions