Document Details

Teams Phone Extensibility Quickstart
Home / Scan #41 / Teams Phone Extensibility Quickstart
Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
GitHub View on GitHub 📚 View on Microsoft Learn

Bias Analysis

Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a significant Windows bias. All command-line examples for provisioning bots and Teams resources use PowerShell cmdlets (e.g., New-CsOnlineApplicationInstance, Set-CsOnlineApplicationInstance, Connect-MicrosoftTeams), and there are no equivalent Bash, Linux shell, or cross-platform CLI examples. The instructions assume the use of Windows-based tools (PowerShell, Teams PowerShell module, Azure PowerShell modules) and reference the Teams Admin Center, which is primarily accessed via a browser but is often associated with Windows environments. There is no mention of Linux or macOS alternatives, nor any guidance for users on non-Windows platforms.
Recommendations
  • Provide equivalent Bash or Azure CLI commands for all PowerShell cmdlets where possible, especially for resource provisioning and bot registration.
  • Explicitly state platform requirements for each tool or command, and note any cross-platform compatibility (e.g., Azure CLI is cross-platform, but Teams PowerShell module may require Windows/PowerShell Core).
  • Include guidance or links for installing and using PowerShell Core on Linux/macOS if PowerShell is required.
  • Where Teams Admin Center or Microsoft 365 Admin Center is referenced, clarify that these are web-based and accessible from any OS.
  • Add a section or callouts for Linux/macOS users, outlining any differences or additional steps needed.
  • If certain operations are only possible on Windows, clearly state this limitation and, if possible, provide workarounds or alternatives.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2025-07-12 23:44 #41 cancelled Biased Biased
2025-07-12 00:58 #8 cancelled Clean Clean
2025-07-10 05:06 #7 processing Clean Clean

Flagged Code Snippets

Sync-CsOnlineApplicationInstance -ObjectId cc123456-5678-5678-1234-ccc123456789 -ApplicationId aa123456-1234-1234-1234-aaa123456789  

    Install-Module Az.BotService -AllowClobber 
    
Connect-AzAccount 

Install-Module Az.Resources 

Register-AzResourceProvider -ProviderNamespace Microsoft.BotService 

New-AzBotService -ResourceGroupName <your RG name here> -Name "<name of Teams Phone bot>" -ApplicationId <your Application/ClientID from Entra> -Location <bot location> -Sku S1 -Description "<description of bot>" 

New-AzBotService -ResourceGroupName teamsphonetest-rg -Name "teamsPhoneBot" -ApplicationId aa123456-1234-1234-1234-aaa123456789 -Location "global" -Sku S1 -Description "My Teams Phone Test Bot" 

Connect-MicrosoftTeams 

Update-Module MicrosoftTeams 

 New-CsOnlineApplicationInstance -UserPrincipalName myteamsphoneresourceaccount@contoso.com -ApplicationId aa123456-1234-1234-1234-aaa123456789 -DisplayName "My Teams Phone Resource Account" 

Set-CsOnlineApplicationInstance -Identity myteamsphoneresourceaccount@contoso.com -ApplicationId aa123456-1234-1234-1234-aaa123456789 -AcsResourceId bb567890-1234-1234-1234-bbb123456789 

    Set-CsPhoneNumberAssignment -Identity <your-TeamsResourceAccount> -PhoneNumber <acquired-number> -PhoneNumberType <DirectRouting|CallingPlan|OperatorConnect> 
    
    Get-CsPhoneNumberAssignment -TelephoneNumber <acquired-number>