Source note · Teams voice administration with PowerShell
For application-based authentication, Microsoft says not to configure a 'Skype and Teams Tenant Admin API' permission (doing so may cause failures); session RBAC comes from the Entra directory role assigned to the application.
Checked 2026-09-25
- Vendor
- Microsoft
- Product
- MicrosoftTeams PowerShell module
- Subsystem
- authentication
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Application-based authentication in Teams PowerShell Module — Microsoft · tier 2 current vendor documentation · How does it work?; Setup Application-based authentication, step 2 Note and step 5
Cite this note
APA
WarmTransfer. (2026, September 25). Teams voice administration with PowerShell: source note teams-powershell-voice-admin-app-auth-rbac. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-powershell-voice-admin-app-auth-rbac
BibTeX
@misc{warmtransfer-claim-teams-powershell-voice-admin-app-auth-rbac,
title = {Teams voice administration with PowerShell: source note teams-powershell-voice-admin-app-auth-rbac},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-powershell-voice-admin-app-auth-rbac},
note = {Source note teams-powershell-voice-admin-app-auth-rbac, checked 2026-09-25}
}