Communication Services

1044
Total Pages
900
Linux-Friendly Pages
144
Pages with Bias
13.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

656 issues found
Showing 251-275 of 656 flagged pages
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-sender-username-resource-powershell.md ...includes/create-sender-username-resource-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 users (e.g., Bash, Azure CLI), and the use of PowerShell is presented as the default and only option. This creates a Windows-centric bias and may hinder accessibility for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all resource management tasks (login, module installation, resource creation, update, listing, deletion).
  • Explicitly mention cross-platform options and clarify that Azure CLI and PowerShell are both supported on Windows, Linux, and macOS.
  • Provide guidance on installing and using Azure CLI on Linux and macOS.
  • Reorder sections or provide parallel examples so that Linux/macOS users do not feel secondary to Windows users.
  • Include notes or links to documentation for Bash scripting and Azure CLI usage.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/send-email-powershell.md ...es/quickstarts/email/includes/send-email-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily biased towards Windows and PowerShell. All examples use Azure PowerShell, with explicit instructions to use Windows PowerShell for prerequisite checks and module installation. There are no Linux or cross-platform CLI examples, nor any mention of Bash, Azure CLI, or other non-Windows tools. The documentation assumes a Windows environment throughout and does not provide guidance for Linux or macOS users.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include Bash or shell script examples for Linux users, especially for tasks like reading files and sending emails.
  • Clarify which steps are platform-specific and provide alternatives for Linux/macOS users (e.g., using pwsh instead of Windows PowerShell, or using compatible modules).
  • Update prerequisite checks to mention how to verify module installation on Linux/macOS (e.g., using pwsh or Azure CLI).
  • Ensure all tooling references (such as PowerShell) are accompanied by cross-platform alternatives or explicit notes about platform compatibility.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/send-email-net.md ...-services/quickstarts/email/includes/send-email-net.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on C#/.NET examples and workflows, which are traditionally associated with Windows environments. Command-line instructions reference Windows shells (cmd, PowerShell) before Bash, and all code samples and package management commands use .NET CLI tools. There are no Linux-specific instructions, troubleshooting notes, or alternative code samples for other platforms or languages. The documentation does not mention Linux-specific tools, nor does it provide parity for Linux users beyond generic references to 'your operating system'.
Recommendations
  • Explicitly mention Linux and macOS compatibility in prerequisites and instructions.
  • Provide Linux/macOS-specific terminal commands and troubleshooting notes (e.g., environment variable setup, file paths).
  • Include Bash/zsh examples before or alongside Windows shell examples.
  • Add a section or sidebar for running the sample on Linux, including installation of .NET Core on popular distributions.
  • Reference cross-platform editors (e.g., VS Code) and provide guidance for both Windows and Linux users.
  • Clarify that the .NET SDK and Azure Communication Services Email client library are cross-platform.
  • Consider providing sample code in additional languages (e.g., Python, Java) if supported by the service.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-email-resource-powershell.md ...rts/email/includes/create-email-resource-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 for all tasks, without mentioning or providing examples for Linux/macOS users or alternative tools such as Azure CLI. This presents a clear Windows bias, as PowerShell is primarily associated with Windows environments, and no cross-platform or Linux-specific guidance is offered.
Recommendations
  • Add equivalent Azure CLI examples for all resource management tasks, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell is available on Linux/macOS, but also provide installation instructions for Azure CLI.
  • Reorganize the documentation to present both PowerShell and CLI options side-by-side, or at least clarify which commands are platform-specific.
  • Include notes or links for Linux/macOS users on how to perform these tasks using their preferred shell environments.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-smtp/includes/send-email-smtp-smtpclient.md ...send-email-smtp/includes/send-email-smtp-smtpclient.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments. It references Windows-specific consoles (cmd, PowerShell) before mentioning Bash, and does not provide any Linux-specific instructions or examples. All code samples and instructions are generic but implicitly assume a Windows/.NET development environment, with no mention of Linux package installation, environment setup, or alternative tools.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms where .NET Core can run.
  • Provide Linux-specific instructions for installing .NET Core (e.g., using apt, yum, or snap).
  • Show example commands in Bash or other Linux shells alongside Windows examples.
  • Clarify that the steps work cross-platform and highlight any platform-specific considerations (e.g., environment variables, file paths).
  • Include troubleshooting tips for common Linux issues (e.g., firewall, SSL certificates).
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/events/subscribe-to-events.md ...ion-services/quickstarts/events/subscribe-to-events.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by listing PowerShell as a primary method for subscribing to events, which is traditionally a Windows-centric tool. There is no mention of Linux-specific tools or shell examples (e.g., Bash), and the order of presentation puts PowerShell on equal footing with Azure CLI, despite CLI being more cross-platform. There are no explicit Linux shell examples or references to Linux-native workflows.
Recommendations
  • Add explicit Bash or Linux shell examples alongside Azure CLI instructions.
  • Clarify that Azure CLI works natively on Linux and macOS, and provide platform-specific notes where relevant.
  • If PowerShell is mentioned, also mention that PowerShell Core is available cross-platform, or provide alternative Linux-native commands.
  • Consider reordering examples to present cross-platform or Linux-friendly tools (Azure CLI, Bash) before Windows-centric ones (PowerShell).
  • Include a section or note about Linux compatibility and best practices for Linux users.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/inline-attachments-powershell.md ...ail-advanced/includes/inline-attachments-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 towards Windows and PowerShell. All examples use Azure PowerShell, and instructions explicitly reference Windows PowerShell. There are no Linux or cross-platform CLI examples, nor any mention of Bash, Azure CLI, or other non-Windows tools. The prerequisite steps and module installation are described only for PowerShell, which is primarily a Windows tool, and the documentation does not address how to perform these tasks on Linux or macOS.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include instructions for installing and using Azure PowerShell on Linux and macOS, or clarify cross-platform support.
  • Provide Bash or shell script examples for file handling and email sending tasks.
  • Rephrase prerequisite checks to be inclusive of non-Windows environments (e.g., 'In a terminal, run...').
  • Mention and link to documentation for Azure CLI and other cross-platform tools alongside PowerShell.
  • Ensure that all steps and code samples have Linux/macOS equivalents or notes about platform compatibility.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-smtp/send-email-smtp.md ...s/quickstarts/email/send-email-smtp/send-email-smtp.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides examples for sending email via SMTP using SmtpClient (typically .NET, often used on Windows) and Windows PowerShell, but does not include any Linux-specific examples or mention Linux tools (such as sendmail, mailx, or Python scripts). The inclusion of Windows PowerShell as a dedicated example and the absence of Linux command-line or scripting alternatives indicates a Windows-centric bias.
Recommendations
  • Add Linux-specific examples using common tools such as sendmail, mailx, or mutt.
  • Include cross-platform scripting examples, such as Python's smtplib, that work on both Windows and Linux.
  • Explicitly mention Linux alternatives alongside Windows tools in each section.
  • Ensure that the order of examples does not prioritize Windows tools over Linux equivalents.
  • Consider adding a section on configuring SMTP on Linux systems.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/events/includes/register-provider-powershell.md ...starts/events/includes/register-provider-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation exclusively provides PowerShell commands for registering the Event Grid resource provider, which are primarily used on Windows. There are no examples for Linux or macOS users (e.g., Azure CLI or Bash), and Windows tooling is implicitly prioritized.
Recommendations
  • Add equivalent Azure CLI commands for registering and checking the Event Grid resource provider status, which work cross-platform (Linux, macOS, Windows).
  • Explicitly mention that PowerShell is one option and provide guidance for users on other operating systems.
  • Consider reordering or presenting both PowerShell and CLI examples side-by-side to avoid implicit prioritization of Windows tools.
  • Include a note about platform compatibility for each command.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/microsoft-entra-id-authentication-integration.md ...ntity/microsoft-entra-id-authentication-integration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by primarily referencing Windows-centric tools (Azure portal, Microsoft Entra admin center, Graph Explorer) and providing examples using Azure CLI and REST API, but omitting explicit Linux or cross-platform command-line examples. There are no PowerShell-specific instructions, but the overall workflow assumes familiarity with Windows-based graphical interfaces and does not mention Linux equivalents or alternative approaches for non-Windows users.
Recommendations
  • Add explicit instructions and examples for Linux users, such as using Azure CLI on Linux, and clarify that Azure CLI commands are cross-platform.
  • Include screenshots or steps for using the Azure portal and Microsoft Entra admin center from Linux or macOS browsers, or note their platform independence.
  • Provide REST API examples using curl or other cross-platform tools, not just Graph Explorer.
  • Mention that all SDKs and tools referenced (Azure CLI, SDKs) are available on Linux and macOS, and provide links to installation guides for those platforms.
  • If PowerShell is referenced elsewhere, ensure Bash or shell equivalents are provided.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/events/includes/create-event-subscription-powershell.md ...vents/includes/create-event-subscription-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 (Az) commands for all examples and instructions, which are typically associated with Windows environments. There are no examples or references to equivalent Azure CLI commands, Bash scripts, or Linux-native tooling. The prerequisites and all operational steps assume the use of PowerShell, which may not be the default or preferred environment for Linux or macOS users.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all operations (create, list, update, delete event subscriptions).
  • Include installation instructions for the Azure CLI, especially for Linux/macOS users, alongside the PowerShell module.
  • Where possible, provide Bash script examples or note cross-platform compatibility of commands.
  • Explicitly mention that PowerShell Core is cross-platform if PowerShell is to be used, and clarify any OS-specific differences.
  • Reorganize sections to present both PowerShell and CLI examples side by side, or allow users to select their preferred environment.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/active-directory/service-principal-net.md ...ity/includes/active-directory/service-principal-net.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by listing Windows terminals (Command Prompt, PowerShell) before Bash when instructing users to open a terminal. All command-line examples use generic 'dotnet' CLI commands, which are cross-platform, but there are no explicit Linux-specific instructions, troubleshooting, or environment setup notes. The documentation does not mention Linux-specific considerations, such as permissions, package managers, or shell differences, nor does it provide example output for Linux terminals. There is also a lack of parity in terms of guidance for Linux users, such as using VS Code on Linux or running the application in a Linux container.
Recommendations
  • List Bash (or Linux terminal) first when mentioning terminal options, or explicitly state that instructions apply equally to Linux, macOS, and Windows.
  • Add Linux-specific notes, such as how to install .NET SDK on popular Linux distributions, and troubleshooting tips for common Linux issues (e.g., permissions, environment variables).
  • Provide example output from a Linux terminal, and clarify that the dotnet CLI commands work identically on Linux.
  • Include instructions for running the application in a Linux container (e.g., Docker), or mention how to use VS Code on Linux.
  • Explicitly state cross-platform compatibility in the prerequisites or overview section.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/includes/create-resource-powershell.md ...ces/quickstarts/includes/create-resource-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses PowerShell commands and examples, which are primarily associated with Windows environments. There are no examples or instructions for using Azure CLI, Bash, or other Linux-native tools. The installation and management steps are all presented with PowerShell syntax, and references to resource group management also link to PowerShell-specific documentation. This creates a strong Windows bias and may hinder users working on Linux or macOS platforms.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all resource creation and management tasks.
  • Include installation instructions for the Azure CLI and relevant modules on Linux and macOS.
  • Reference cross-platform documentation for resource group and tag management, not just PowerShell guides.
  • Clearly indicate which commands are cross-platform and which are Windows-specific.
  • Consider restructuring the documentation so that CLI and PowerShell examples are presented side-by-side or with clear headings for each platform.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/rooms/includes/rooms-quickstart-net.md ...ces/quickstarts/rooms/includes/rooms-quickstart-net.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. Console examples mention 'cmd' and 'PowerShell' before 'Bash', and all command-line instructions use the dotnet CLI without explicit Linux shell syntax (e.g., no mention of Linux-specific nuances or package managers). There are no Linux-specific instructions, troubleshooting, or examples, and no mention of Linux tools or patterns. The sample code and setup steps are generic, but the environment references and order of mention favor Windows.
Recommendations
  • List Bash (Linux/macOS) before or alongside cmd/PowerShell when referencing console windows.
  • Add explicit Linux/macOS instructions for installing .NET Core and running dotnet commands, including any required dependencies.
  • Include troubleshooting notes for common Linux issues (e.g., permissions, environment variables).
  • Reference Linux package managers (apt, yum, Homebrew) for .NET installation where appropriate.
  • Ensure all code and CLI examples are tested and confirmed to work on Linux/macOS as well as Windows.
  • Consider adding a section or callout for Linux/macOS users to highlight any differences or additional steps.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/sms/includes/send-sms-java.md ...ion-services/quickstarts/sms/includes/send-sms-java.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides command-line instructions specifically for Windows environments, including Command Prompt and PowerShell examples, but omits explicit Linux or macOS shell examples (e.g., bash/zsh). This prioritizes Windows tooling and patterns, potentially making it less accessible for Linux users.
Recommendations
  • Add explicit Linux/macOS shell (bash/zsh) command examples alongside Windows Command Prompt and PowerShell instructions.
  • When listing command examples, present Linux/macOS commands first or equally with Windows commands to avoid implicit prioritization.
  • Clarify that Maven commands can be run in any terminal (e.g., bash, zsh, Windows Command Prompt, PowerShell) and provide syntax for each where differences exist.
  • Include notes or sections for Linux/macOS users regarding environment setup, file paths, and common issues.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-answer-teams-calls.md ...ts/tpe/teams-phone-extensibility-answer-teams-calls.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by exclusively providing PowerShell commands for Teams resource account management and DevTunnel setup, referencing Windows-centric tools and modules, and omitting equivalent Linux/bash instructions. There are no examples or guidance for performing these steps on Linux or macOS, which may hinder cross-platform adoption.
Recommendations
  • Provide equivalent bash/CLI examples for all PowerShell commands, especially for Teams resource account creation and association.
  • Clarify whether DevTunnel is available and supported on Linux/macOS, and if so, provide installation and usage instructions for those platforms.
  • Reference cross-platform tools (e.g., Azure CLI, Microsoft Graph API) where possible, and link to their documentation.
  • If certain steps require Windows-only tools (like some Teams PowerShell modules), explicitly state this limitation and suggest alternatives or workarounds for Linux/macOS users.
  • Ensure that all code snippets and setup instructions are presented in a platform-neutral way or include both Windows and Linux/macOS variants.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-access-teams-phone.md ...ts/tpe/teams-phone-extensibility-access-teams-phone.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias by providing user enablement instructions exclusively via the Microsoft 365 admin center GUI, which is primarily accessed on Windows. It references the MicrosoftTeams PowerShell module for obtaining resource account IDs, without mentioning Linux alternatives or cross-platform CLI tools. No Linux-specific instructions or parity examples (such as Azure CLI, Bash, or cross-platform scripting) are provided for administrative tasks.
Recommendations
  • Add equivalent instructions for enabling Teams users using cross-platform tools such as Azure CLI or Microsoft Graph API, with example commands for Linux/macOS.
  • Provide examples for obtaining resource account ObjectId using REST API or Graph API, which can be executed from any OS, not just via PowerShell.
  • Explicitly mention that administrative tasks can be performed from Linux/macOS using supported CLI tools or APIs, and provide sample commands.
  • Where GUI steps are described, offer alternative CLI or API-based steps for environments without access to Windows or the Microsoft 365 admin center.
  • Review all examples and ensure parity between Windows and Linux, including authentication, consent, and resource management flows.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-user/teams-user-ios.md ...ce-video-calling/includes/teams-user/teams-user-ios.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates bias towards Windows by referencing Windows-centric tools and patterns, such as requiring Teams users to be Enterprise Voice enabled via PowerShell and linking to Windows-focused Teams deployment guides. There are no Linux equivalents or alternative instructions provided for enabling Teams features or deploying Teams, and PowerShell is mentioned as the primary method for configuration.
Recommendations
  • Include instructions for enabling Teams Phone and Enterprise Voice using cross-platform tools or provide equivalent steps for Linux/macOS environments.
  • Reference Teams deployment guides that cover non-Windows platforms, or clarify platform requirements.
  • If PowerShell is required, mention alternatives such as Azure CLI or web portal steps where possible.
  • Clearly state any platform limitations and provide guidance for users on Linux or macOS.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/phone-numbers-net.md ...es/quickstarts/telephony/includes/phone-numbers-net.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows-specific consoles (cmd, PowerShell) before Bash, and by not providing any Linux-specific examples or guidance. All terminal commands are generic and use the dotnet CLI, which is cross-platform, but there is no mention of Linux-specific considerations, nor are Linux tools or patterns discussed. The documentation assumes familiarity with Windows environments and omits details that might help Linux users (e.g., environment variable setup, file path differences).
Recommendations
  • Explicitly mention Linux and macOS as supported platforms wherever Windows is referenced.
  • Provide Linux/macOS-specific instructions or notes, such as how to set environment variables, install .NET Core, and run dotnet commands in Bash/zsh.
  • List Bash or Linux terminal examples first or alongside Windows terminals (e.g., 'In a console window (such as Bash, cmd, or PowerShell)...').
  • Include troubleshooting tips for common Linux issues (e.g., permissions, dependency installation).
  • Add links to Linux-specific .NET installation guides.
  • Clarify any platform-specific differences in file paths, environment variable syntax, or prerequisites.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-quickstart.md ...uickstarts/tpe/teams-phone-extensibility-quickstart.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias, primarily through exclusive use of Windows-specific tools (PowerShell cmdlets, Teams Admin Center, Microsoft 365 Admin Center) and examples. All administrative and provisioning steps for Teams Phone extensibility rely on PowerShell commands or GUI tools only available on Windows, with no mention of Linux alternatives or cross-platform equivalents. The order of presentation also places Windows-centric methods first and does not acknowledge Linux or macOS environments, nor does it provide CLI or REST API alternatives for key provisioning steps.
Recommendations
  • Provide equivalent examples using cross-platform tools such as Azure CLI, Microsoft Graph API, or REST endpoints for provisioning and managing Teams Resource Accounts and phone numbers.
  • Explicitly mention platform requirements and limitations for PowerShell cmdlets and GUI tools, and offer guidance for Linux/macOS users.
  • Add instructions for installing and using PowerShell Core (which is cross-platform) on Linux/macOS, including any required modules for Teams administration.
  • Where possible, prioritize or at least equally present cross-platform methods (e.g., Azure CLI, REST API) before or alongside Windows-specific tools.
  • Include troubleshooting notes or links for common issues encountered by Linux/macOS users when attempting Teams Phone extensibility tasks.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-teams-interop-group-calls.md ...video-calling/get-started-teams-interop-group-calls.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias in several ways. The prerequisites and instructions reference Windows-centric tools and patterns, such as Teams Phone licensing and enabling Enterprise Voice via PowerShell, and the Teams deployment link points to Windows installation. There are no Linux-specific instructions, nor are Linux equivalents for PowerShell commands or Teams deployment mentioned. The page does not provide parity for Linux users in terms of setup or troubleshooting.
Recommendations
  • Include Linux-specific instructions for Teams deployment and configuration, such as links to Linux installation guides or notes on Teams web client usage.
  • Provide alternative commands or instructions for enabling Enterprise Voice and Teams Phone licensing that do not rely solely on PowerShell, or mention cross-platform options (e.g., Azure CLI, Graph API).
  • Explicitly state whether the sample code and prerequisites are platform-agnostic, and highlight any platform-specific requirements or limitations.
  • Add troubleshooting notes or tips for Linux users, especially regarding device permissions and Teams interoperability.
  • Ensure that references to tools (e.g., PowerShell) are accompanied by Linux/macOS alternatives or clarify when only Windows is supported.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-user/teams-user-android.md ...ideo-calling/includes/teams-user/teams-user-android.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates bias toward Windows by referencing Teams deployment and user enablement steps that rely on Windows-centric tools and patterns (e.g., PowerShell for enabling Enterprise Voice). There are no Linux equivalents or alternatives mentioned for these administrative tasks, nor is there guidance for Teams deployment or user management from non-Windows platforms. The quickstart itself is Android-focused, but the prerequisites and setup steps assume a Windows environment.
Recommendations
  • Provide Linux/macOS alternatives for Teams deployment and user enablement, such as using Microsoft 365 admin center web UI or cross-platform CLI tools where available.
  • Explicitly mention whether steps (e.g., enabling Enterprise Voice) can be performed via browser-based admin portals, and link to those instructions.
  • If PowerShell is required, clarify if PowerShell Core (cross-platform) is supported and provide installation instructions for Linux/macOS.
  • Add notes or sections for non-Windows users to ensure parity and accessibility.
  • Review all prerequisite steps to ensure they are platform-neutral or offer alternatives.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/references/how-to-collect-diagnostic-audio-recordings.md ...ferences/how-to-collect-diagnostic-audio-recordings.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively providing build instructions and prerequisites for Windows (Visual Studio 2022, Windows depot_tools guide), referencing only the Windows build of unpack_aecdump.exe, and omitting any Linux or macOS equivalents or instructions. There are no Linux-specific examples, tools, or troubleshooting steps, and Windows is presented as the default platform for these tasks.
Recommendations
  • Add Linux and macOS build instructions for unpack_aecdump, including required dependencies (e.g., gcc/clang, Python, depot_tools) and platform-specific commands.
  • Reference Linux and macOS documentation for depot_tools installation and Chromium build environment setup.
  • Show example commands for running unpack_aecdump on Linux/macOS (e.g., ./unpack_aecdump audio_debug.5.aecdump).
  • Clarify that unpack_aecdump is cross-platform and provide parity in troubleshooting steps and screenshots for non-Windows environments.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/email-resource-management-powershell.md ...mples/includes/email-resource-management-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 towards Windows and PowerShell. All examples, instructions, and scripts use Azure PowerShell cmdlets and syntax, with no mention of Bash, Azure CLI, or cross-platform alternatives. The prerequisite check and installation instructions reference PowerShell and Windows-specific patterns, and there are no Linux/macOS-specific instructions or examples. This makes the documentation less accessible to users on Linux or macOS, who may prefer Bash or Azure CLI.
Recommendations
  • Provide equivalent Azure CLI (az) examples for each PowerShell script block, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include a 'Prerequisites' section for Linux/macOS users, such as instructions for installing Azure CLI and authenticating with az login.
  • Add a note clarifying that all operations can be performed using Azure CLI, and link to relevant Azure CLI documentation.
  • Where possible, use generic shell commands (e.g., Bash) for scripting examples, or provide both PowerShell and Bash/CLI alternatives.
  • Explicitly mention that Azure PowerShell is available cross-platform, but clarify installation steps for Linux/macOS.
  • Ensure that tool references (e.g., Connect-AzAccount) are accompanied by their Azure CLI equivalents (e.g., az login).
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/references/how-to-collect-browser-verbose-log.md ...lling/references/how-to-collect-browser-verbose-log.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively provides instructions and command-line examples for collecting verbose logs from browsers on Windows, referencing Windows file paths, executables, and tools. There are no examples or guidance for Linux or macOS users, nor are cross-platform considerations mentioned.
Recommendations
  • Add equivalent instructions and command-line examples for Linux and macOS, including typical executable paths (e.g., /usr/bin/google-chrome) and file locations.
  • Mention platform-specific differences in browser command-line arguments and log file locations.
  • Provide guidance on how to open a terminal and run the commands on Linux/macOS.
  • Clarify any differences in log flushing and file management across platforms.
  • Consider reordering or grouping instructions by platform to ensure parity and clarity.
GitHub Create Pull Request
← Previous Page 11 of 27 Next →