Communication Services

2083
Total Pages
1869
Linux-Friendly Pages
214
Pages with Bias
10.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

367 issues found
Showing 126-150 of 367 flagged pages
Communication Services Plan user experience for virtual appointments ...oncepts/interop/virtual-visits/plan-user-experience.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references Teams Admin Center and PowerShell as primary methods for configuration discovery, with no mention of Linux/macOS equivalents or cross-platform alternatives. Windows tools (PowerShell) are mentioned before any other options, and there are no examples or guidance for Linux users, such as using Azure CLI, REST API, or cross-platform scripting. This creates friction for non-Windows users seeking to manage Teams configurations.
Recommendations
  • Include instructions for discovering Teams configuration using cross-platform tools such as Azure CLI or Microsoft Graph API.
  • Explicitly mention and provide examples for Linux/macOS users where possible.
  • Clarify which configuration steps require Windows-only tools and suggest alternatives when available.
  • Reorder examples so that cross-platform methods are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
Communication Services Pricing for Teams interop scenarios ...ion-services/concepts/pricing/teams-interop-pricing.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and terminology (e.g., Teams Desktop client, PowerShell cmdlets) are referenced before or exclusively, and Windows is mentioned as the platform in example scenarios. The instructions for enabling Teams Phone features rely on PowerShell cmdlets, which are Windows-centric, without offering Linux/macOS alternatives or parity. Examples and scenarios reference Windows clients and browsers, with no mention of Linux or macOS desktop clients or command-line tools.
Recommendations
  • Provide explicit examples and instructions for Linux and macOS users, such as using Teams web client on those platforms.
  • Include cross-platform alternatives to PowerShell cmdlets, such as Azure CLI or REST API instructions for license assignment and configuration.
  • Mention Linux/macOS desktop clients where applicable, or clarify platform support for Teams clients.
  • Ensure scenarios and tables reference non-Windows platforms equally, e.g., 'Teams desktop client (Windows, macOS, Linux)' instead of just 'Teams desktop client'.
GitHub Create Pull Request
Communication Services Azure Communication Services Call Automation how-to for adding Microsoft Teams User into an existing call ...w-tos/call-automation/teams-interop-call-automation.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates Windows bias primarily in the authorization step, where only PowerShell cmdlets (Set-CsTeamsAcsFederationConfiguration, Set-CsExternalAccessPolicy) are referenced for tenant and user policy configuration. No Linux/macOS alternatives or cross-platform CLI options are mentioned for these administrative tasks. The rest of the guide is cross-platform, with code samples for C#, Java, JavaScript, and Python, but the initial setup assumes access to Windows/PowerShell tools.
Recommendations
  • Provide equivalent instructions using Microsoft Teams admin portal UI, Microsoft Graph API, or Azure CLI for tenant and user policy configuration, making the process accessible from Linux/macOS.
  • Explicitly mention whether PowerShell cmdlets can be run from PowerShell Core on Linux/macOS, or clarify any platform limitations.
  • Add notes or links to cross-platform tools for administrative tasks, ensuring Linux/macOS users can complete all steps without Windows dependencies.
  • Reorder or supplement examples so that cross-platform methods are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
Communication Services Tutorial - Teams Shared Line Appearance ...ices/how-tos/cte-calling-sdk/shared-line-appearance.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits Windows bias by referencing Teams PowerShell as a primary method for assigning delegates and mentioning Windows tools before Linux alternatives. There are no explicit Linux/macOS command-line examples or guidance for non-Windows users, and the prerequisite steps focus on Microsoft Teams Client and Teams PowerShell, both of which are Windows-centric.
Recommendations
  • Provide equivalent instructions for assigning delegates using cross-platform tools, such as Azure CLI, REST API, or web interfaces.
  • Explicitly state whether Teams PowerShell can be run on Linux/macOS (e.g., via PowerShell Core) and provide installation guidance if possible.
  • Include examples or links for Linux/macOS users to perform key actions, ensuring parity in setup and management steps.
  • Clarify any platform limitations and suggest workarounds for non-Windows environments.
GitHub Create Pull Request
Communication Services Prerequisites ...des/create-azure-managed-domain-resource-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module, which is primarily associated with Windows environments. There are no examples or instructions for Linux/macOS users, such as using Azure CLI or Bash. The documentation assumes the user is on Windows and does not mention cross-platform alternatives, creating friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI commands for all operations (login, module installation, resource creation, management, deletion).
  • Explicitly mention cross-platform compatibility of Azure tools and provide guidance for Linux/macOS users.
  • Reorder examples to present both PowerShell and CLI/Bash alternatives side-by-side or in parallel sections.
  • Clarify prerequisites for non-Windows users, such as installing Azure CLI and using Bash or other shells.
GitHub Create Pull Request
Communication Services Add a bot to your chat app ...uickstarts/chat/quickstart-botframework-integration.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows development environments. It exclusively references Visual Studio (Windows-only), .NET Core, and C# for all code samples and deployment instructions. Package installation uses 'dotnet' and 'powershell' commands, with no mention of Linux/macOS equivalents or alternative editors. There are no Linux/macOS-specific setup or deployment instructions, nor any examples using cross-platform tools or languages. All screenshots and UI instructions are from the Azure Portal, which is cross-platform, but all local development assumes Windows tooling.
Recommendations
  • Add instructions for setting up and deploying bots using cross-platform editors (e.g., VS Code) and command-line tools on Linux/macOS.
  • Include examples for bot creation and deployment using Node.js/JavaScript or Python SDKs, which are more common on Linux/macOS.
  • Provide package installation commands for Linux/macOS (e.g., using bash, not just powershell).
  • Clarify that .NET Core and dotnet CLI are cross-platform, and provide explicit instructions for Linux/macOS users (e.g., installation links, troubleshooting tips).
  • Add a section or callouts for Linux/macOS users highlighting any differences or additional steps required.
  • Show deployment via Azure CLI or GitHub Actions, which are platform-agnostic, rather than relying solely on Visual Studio publishing.
GitHub Create Pull Request
Communication Services Add custom verified email domains ...vices/quickstarts/email/add-custom-verified-domains.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it provides platform pivots for Azure Portal, Azure CLI, .NET, and PowerShell, the presence of PowerShell as a dedicated pivot and the inclusion of links to guides for adding DNS records using 'Windows-based DNS' (with no mention of Linux-based DNS management tools like BIND or common Linux CLI utilities) indicate a preference for Windows tools and workflows. The DNS record instructions for 'Other (General)' also point to Windows-based DNS documentation, omitting Linux/macOS equivalents. There are no explicit Linux/macOS command-line examples or references to Linux-native DNS management.
Recommendations
  • Add Linux/macOS-specific instructions or pivots, especially for DNS record management using common tools (e.g., BIND, `dig`, `nsupdate`, or editing `/etc/bind/named.conf.local`).
  • Include links or examples for managing DNS records on Linux-based DNS servers, not just Windows DNS Manager.
  • Where PowerShell is shown, provide equivalent Bash or shell script examples for Linux/macOS users.
  • Ensure that 'Other (General)' DNS instructions include both Windows and Linux approaches, or link to cross-platform guides.
GitHub Create Pull Request
Communication Services Prerequisites ...es/create-custom-managed-domain-resource-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module for all resource management tasks. There are no examples or instructions for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform tools. The documentation assumes familiarity with Windows/PowerShell environments and does not mention alternatives or parity for non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI commands for all resource management tasks, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly state that PowerShell Core is available on Linux/macOS, and provide installation instructions for those platforms.
  • Include Bash script examples or references to REST API usage for advanced users.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell examples.
  • Add a section clarifying platform compatibility and recommending tools for Linux/macOS users.
GitHub Create Pull Request
Communication Services Prerequisites ...rts/email/includes/create-email-resource-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell commands and references Windows-centric tools for managing Azure Email Communication Service resources. There are no examples or guidance for Linux/macOS users, such as Azure CLI or Bash equivalents. The prerequisites and all operational steps assume a Windows/PowerShell environment, creating friction for users on other platforms.
Recommendations
  • Add Azure CLI examples alongside PowerShell commands for all resource management tasks.
  • Include installation instructions for Azure CLI and relevant modules for Linux/macOS.
  • Explicitly state cross-platform options and note any limitations or differences.
  • Reorder or parallelize examples so that Windows and Linux/macOS users are equally supported.
GitHub Create Pull Request
Communication Services Subscribe to events ...ion-services/quickstarts/events/subscribe-to-events.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for Azure portal, Azure CLI, and PowerShell, with explicit mention of PowerShell—a Windows-centric tool—without referencing Linux/macOS equivalents (such as Bash or shell scripting). The structure lists PowerShell as a primary method, and there are no explicit Linux/macOS-specific instructions or examples, which may create friction for non-Windows users.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users alongside PowerShell.
  • Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (CMD/PowerShell) and Linux/macOS (Bash/zsh).
  • If PowerShell is mentioned, note that PowerShell Core is available on Linux/macOS, or provide guidance for those platforms.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are presented before Windows-specific tools (PowerShell).
GitHub Create Pull Request
Communication Services include file ...es/quickstarts/email/includes/send-email-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell. All examples and instructions use Azure PowerShell, with explicit references to running commands in 'windows PowerShell'. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform scripting. The installation instructions and module checks are Windows/PowerShell-specific, and no alternatives are mentioned.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Clarify that Azure PowerShell can be installed and used on Linux/macOS (if true), and provide installation steps for those platforms.
  • Include Bash or shell script examples for sending emails via Azure Communication Services, if supported.
  • Rephrase 'In a windows PowerShell' to 'In PowerShell', and specify that PowerShell Core is available cross-platform.
  • Provide links to Linux/macOS installation guides for Azure PowerShell and/or Azure CLI.
GitHub Create Pull Request
Communication Services Prerequisites ...vents/includes/create-event-subscription-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell commands and patterns, with no mention of cross-platform alternatives such as Azure CLI, Bash, or scripting examples for Linux/macOS. All examples and instructions assume PowerShell usage, which is traditionally associated with Windows environments, and there is no guidance for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all tasks (create, list, update, delete event subscriptions).
  • Explicitly mention that PowerShell is available cross-platform, but also provide Bash/CLI alternatives.
  • Include installation instructions for Azure CLI and note compatibility with Linux/macOS.
  • Reorder examples or provide tabs for PowerShell and CLI to avoid Windows-first presentation.
  • Clarify any platform-specific requirements or differences.
GitHub Create Pull Request
Communication Services Prerequisites ...includes/create-sender-username-resource-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module, which is primarily associated with Windows environments. There are no examples or guidance for Linux/macOS users, such as using Azure CLI or Bash. The instructions and examples are Windows-centric, and alternative cross-platform tools are not mentioned.
Recommendations
  • Add equivalent Azure CLI commands for all operations (login, resource creation, update, listing, deletion).
  • Explicitly mention that Azure CLI is available and supported on Linux/macOS.
  • Provide Bash or shell script examples alongside PowerShell.
  • Clarify any platform-specific requirements or limitations for the Az.Communication module.
  • Reorder examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
GitHub Create Pull Request
Communication Services include file ...-services/quickstarts/email/includes/send-email-net.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by referencing Windows-specific consoles (cmd, PowerShell) before Bash, and by exclusively providing .NET/C# examples and commands. While .NET Core is cross-platform, there are no explicit Linux/macOS instructions, troubleshooting notes, or examples. The documentation assumes familiarity with Windows tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Explicitly mention that all .NET CLI commands work on Linux/macOS and provide example terminal commands for those platforms.
  • List Bash or Linux/macOS terminal first or equally alongside Windows consoles when referencing command-line usage.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, environment variable setting).
  • Provide links to platform-specific .NET installation guides for Linux/macOS.
  • Clarify that the sample code and instructions are applicable across operating systems.
GitHub Create Pull Request
Communication Services include file ...ail-advanced/includes/inline-attachments-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples and instructions using Azure PowerShell commands and Windows-specific terminology. There are no equivalent instructions or examples for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform scripting. The prerequisite check and installation steps assume a Windows environment and PowerShell usage, creating friction for non-Windows users.
Recommendations
  • Add equivalent instructions and examples for Linux/macOS users, such as using Azure CLI or Bash scripts.
  • Clarify whether the Azure PowerShell module can be used on Linux/macOS (PowerShell Core), and provide installation steps for those platforms.
  • Include cross-platform code samples, or at least mention alternatives for non-Windows users.
  • Avoid assuming Windows as the default environment in prerequisite checks and example sections.
GitHub Create Pull Request
Communication Services Set up and create access tokens for Teams users ...nication-services/quickstarts/manage-teams-identity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the administrator troubleshooting section, where PowerShell commands and the Microsoft Graph PowerShell module are used exclusively to resolve service principal issues. There are no equivalent instructions or examples for Linux/macOS users, nor are alternative tools (such as Azure CLI or REST API) mentioned. This creates friction for non-Windows administrators who may not have access to PowerShell or prefer platform-agnostic solutions.
Recommendations
  • Provide equivalent instructions using Azure CLI, which is cross-platform and widely available on Linux/macOS.
  • Include REST API examples for service principal creation and consent, allowing users to perform these actions regardless of OS.
  • Explicitly mention that PowerShell instructions are Windows-centric and offer links or guidance for Linux/macOS alternatives.
  • Add troubleshooting steps for common issues using platform-agnostic tools.
GitHub Create Pull Request
Communication Services include file ...ion-services/quickstarts/sms/includes/send-sms-java.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides command-line examples for both Windows Command Prompt and PowerShell, but does not include explicit examples for Linux/macOS shells (e.g., Bash). Windows-specific shells are mentioned first and exclusively, which may cause confusion or friction for Linux/macOS users. There are no Linux-specific instructions or clarifications, despite Maven and Java being cross-platform.
Recommendations
  • Add explicit Bash (Linux/macOS) command examples alongside Command Prompt and PowerShell.
  • Clarify that all Maven commands work in Bash and other Unix-like shells, and provide syntax where it differs.
  • List Linux/macOS instructions before or alongside Windows instructions to avoid Windows-first bias.
  • Mention common Linux/macOS text editors (e.g., nano, vim) when instructing users to edit files.
GitHub Create Pull Request
Communication Services Send an email using SMTP ...s/quickstarts/email/send-email-smtp/send-email-smtp.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides a dedicated section for sending email via Windows PowerShell, a Windows-specific tool, without offering equivalent Linux/macOS command-line examples (e.g., using sendmail, mailx, or curl). The inclusion of PowerShell as a pivot option highlights Windows tooling, and there is no mention of Linux-native methods or cross-platform alternatives. This creates friction for Linux/macOS users who cannot use PowerShell natively.
Recommendations
  • Add a section or pivot for Linux/macOS users, demonstrating how to send email via SMTP using common tools (e.g., sendmail, mailx, swaks, curl, or Python scripts).
  • Explicitly mention cross-platform alternatives to PowerShell for command-line email sending.
  • Ensure that examples for both Windows and Linux/macOS are presented with equal prominence.
GitHub Create Pull Request
Communication Services Prerequisites ...ces/quickstarts/includes/create-resource-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell commands and references Windows-centric tools and patterns, such as 'PS C:\>' prompts and PowerShell module installation. There are no examples or instructions for Linux/macOS users, such as using Azure CLI or Bash, nor is there mention of how to perform these tasks outside of PowerShell.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all resource management tasks.
  • Include installation instructions for Azure CLI and relevant modules on Linux/macOS.
  • Show command examples using Bash or zsh shell prompts (e.g., $) alongside PowerShell.
  • Clarify cross-platform compatibility of Az PowerShell module and how to run it on Linux/macOS if possible.
  • Explicitly state which steps are platform-agnostic and which are Windows-specific.
GitHub Create Pull Request
Communication Services Migrating from Twilio Conversations Chat to Azure Communication Services Chat C# ...orials/includes/twilio-to-acs-chat-android-tutorial.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily in the prerequisites and setup sections. Visual Studio is listed as the only required IDE, and the package installation example uses PowerShell syntax ('dotnet add package'), which is most commonly associated with Windows environments. There are no explicit instructions or examples for Linux/macOS users, such as using VS Code, JetBrains Rider, or terminal-based workflows. The Azure CLI command is cross-platform, but the overall setup assumes a Windows development environment.
Recommendations
  • Add instructions for installing and using the Azure Communication Services Chat SDK on Linux/macOS, including using terminal/bash and alternative IDEs like VS Code.
  • Provide package installation examples using bash/zsh syntax (e.g., 'dotnet add package' in a generic shell, not PowerShell).
  • Clarify that the Azure CLI command works on all platforms and provide links or notes for installing Azure CLI on Linux/macOS.
  • Mention cross-platform .NET development and testing options, such as using Docker or GitHub Codespaces.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., certificate trust, environment variables).
GitHub Create Pull Request
Communication Services Additional Prerequisites ...ity/includes/active-directory/service-principal-cli.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by linking exclusively to Windows VM setup guides for managed identities, referencing Windows-specific tools (PowerShell, Azure portal for Windows VMs), and omitting Linux VM equivalents. The examples and instructions do not mention Linux or macOS environments, nor do they provide parity for users on those platforms.
Recommendations
  • Include links to managed identity setup guides for Linux VMs alongside Windows VM guides.
  • Provide Azure CLI and PowerShell examples that explicitly mention compatibility with Linux/macOS terminals.
  • Add notes or sections describing environment variable setup for Linux/macOS shells (e.g., bash, zsh) and development environments.
  • Ensure all referenced articles have Linux/macOS equivalents or alternatives, and link to them.
  • Avoid using 'Windows VM' in link text unless there is a corresponding 'Linux VM' option presented.
GitHub Create Pull Request
Communication Services Answer Teams Phone calls from Call Automation ...ts/tpe/teams-phone-extensibility-answer-teams-calls.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation shows notable Windows bias: key setup steps (creating Teams resource accounts, associating resources, and hosting DevTunnels) are presented exclusively with PowerShell commands and references to Windows-centric tools. There are no Linux/macOS alternatives or CLI examples, and Windows/PowerShell instructions are given first and exclusively, which may hinder Linux/macOS users from completing the setup without additional research.
Recommendations
  • Provide equivalent Azure CLI or Bash commands for all PowerShell steps, especially for creating and associating Teams resource accounts.
  • Document how to install and use DevTunnels on Linux/macOS, including any platform-specific prerequisites or limitations.
  • Explicitly state platform compatibility for all tools and commands, and link to cross-platform installation guides.
  • Include Linux/macOS examples alongside Windows/PowerShell instructions to ensure parity.
  • If certain steps are Windows-only, clarify this and suggest workarounds or alternatives for other platforms.
GitHub Create Pull Request
Communication Services Quickstart - Teams interop calls on Azure Communication Services ...video-calling/get-started-teams-interop-group-calls.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation displays moderate Windows bias. The prerequisites and setup steps reference Windows-centric tools and patterns, such as PowerShell for enabling Teams Phone features and links to Windows-focused deployment guides. There are no explicit Linux/macOS alternatives or examples for these steps, and the documentation does not clarify cross-platform compatibility for critical tasks like enabling Enterprise Voice. However, the main code samples and app hosting instructions are platform-neutral (JavaScript, npx/webpack), and there are no PowerShell scripts or Windows-only commands in the main workflow.
Recommendations
  • Add explicit instructions or links for enabling Teams Phone and Enterprise Voice using cross-platform tools (e.g., Azure CLI, Microsoft Graph API) where possible.
  • Clarify whether steps that reference PowerShell can be completed via browser or other OS-agnostic interfaces.
  • Include Linux/macOS-specific notes or examples for any steps that may differ from Windows (e.g., Teams deployment, user ID retrieval).
  • Ensure all referenced documentation (such as Teams deployment) includes Linux/macOS guidance or alternatives.
GitHub Create Pull Request
Communication Services Quickstart - How to call to Teams user from an Android app ...ideo-calling/includes/teams-user/teams-user-android.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references enabling Teams Phone features via PowerShell, which is a Windows-centric tool, and links to a Windows-focused Teams deployment guide. There are no Linux/macOS alternatives or examples for these administrative steps. All other code and instructions are platform-neutral (Android/Java).
Recommendations
  • Provide Linux/macOS-compatible instructions for enabling Teams Phone features, such as using Microsoft 365 admin center web UI or cross-platform CLI tools if available.
  • Clarify whether PowerShell steps can be performed using PowerShell Core on Linux/macOS, or provide equivalent commands for those platforms.
  • Add explicit notes or links for Linux/macOS users on how to complete Teams user enablement without Windows dependencies.
GitHub Create Pull Request
Communication Services Teams Phone Extensibility ...uickstarts/tpe/teams-phone-extensibility-quickstart.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, especially in sections related to provisioning Teams Resource Accounts and bot services. All command-line examples use PowerShell cmdlets and Azure CLI modules that are primarily Windows-centric. There are no Linux/macOS shell equivalents or guidance for non-Windows environments, and Windows tools (Teams PowerShell, MicrosoftTeamsPowerShell, Az.BotService) are mentioned exclusively and before any alternatives. This creates friction for Linux/macOS users attempting to follow the quick start and provisioning steps.
Recommendations
  • Provide equivalent Linux/macOS shell commands (e.g., bash, Azure CLI) for all PowerShell examples.
  • Clarify which steps can be performed via cross-platform Azure CLI and which require PowerShell, and offer alternatives or workarounds for Linux/macOS users.
  • Explicitly state OS requirements for PowerShell modules and suggest Docker containers or cloud-based shells for non-Windows users.
  • Add links or references to official Microsoft documentation on using Teams and Azure modules in Linux/macOS environments.
  • Where GUI steps are described (e.g., Azure Portal, Teams Admin Center), clarify that these are OS-agnostic.
GitHub Create Pull Request
← Previous Page 6 of 15 Next →