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 476-500 of 656 flagged pages
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/entra-id/support-entra-id-users-net.md ...entity/includes/entra-id/support-entra-id-users-net.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references Windows-specific console environments (cmd, PowerShell) before mentioning Bash, and does not provide any Linux-specific guidance or examples (e.g., for environment variable setup, editor usage, or troubleshooting). All instructions and examples are platform-neutral at the command level, but the overall framing and lack of Linux-specific details suggest a Windows-first bias.
Recommendations
  • Explicitly mention Linux and macOS environments alongside Windows in setup instructions.
  • Provide examples of setting environment variables in Bash (e.g., export ENTRA_CLIENT_ID=...) and guidance for common Linux text editors (nano, vim).
  • Add troubleshooting notes for Linux users (e.g., permissions, .NET SDK installation differences).
  • Ensure that all referenced commands and tools are confirmed to work on Linux/macOS, and note any platform-specific caveats.
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. In the 'Create a new C# application' section, Windows-specific consoles ('cmd, PowerShell') are mentioned before Bash, and no explicit Linux terminal examples or instructions are provided. All command-line examples use generic 'dotnet' commands, which are cross-platform, but there are no Linux-specific notes, troubleshooting, or environment setup details. No Linux package manager alternatives (e.g., apt, yum) or shell-specific instructions are given. The documentation assumes familiarity with Windows conventions and does not address Linux-specific differences or needs.
Recommendations
  • List Bash (Linux/macOS) before Windows consoles in instructions, or mention them equally.
  • Add explicit Linux/macOS setup instructions, including prerequisites such as installing .NET Core via package managers (apt, yum, brew).
  • Include troubleshooting notes for common Linux issues (e.g., permissions, environment variables).
  • Provide example commands for Linux shells (e.g., Bash, zsh) where relevant.
  • Clarify that all 'dotnet' commands work cross-platform and highlight any OS-specific caveats.
  • Add links to official .NET installation guides for Linux/macOS.
  • Mention differences in file paths, permissions, or execution if applicable.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/router/includes/router-quickstart-net.md ...s/quickstarts/router/includes/router-quickstart-net.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions Windows console environments (cmd, PowerShell) before Bash, and all code samples and instructions use .NET and NuGet, which are cross-platform but have a historical association with Windows. There are no Linux-specific instructions, troubleshooting, or examples, and no mention of Linux package managers or shell environments beyond a brief mention of Bash. The documentation does not provide parity for Linux users in terms of environment setup or command-line usage.
Recommendations
  • Explicitly state that all commands work on Linux, macOS, and Windows, and provide any necessary platform-specific notes.
  • Include Linux-specific instructions for installing .NET (e.g., using apt, yum, or snap), and clarify how to run the sample in Bash or other Linux shells.
  • Mention cross-platform compatibility of NuGet and .NET, and provide troubleshooting tips for common Linux issues (e.g., permissions, environment variables).
  • List Bash or Linux terminal first when mentioning console environments, or present all environments equally.
  • Add a section on verifying .NET installation on Linux and macOS, and link to official installation guides for those platforms.
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references enabling Teams users for Enterprise Voice via PowerShell and links to a Teams deployment guide that is Windows-centric. There are no Linux-specific instructions or alternatives for managing Teams users or deploying Teams, and no mention of cross-platform tools for these administrative tasks.
Recommendations
  • Provide Linux/macOS alternatives for Teams administration tasks, such as using Microsoft 365 admin center web UI or cross-platform CLI tools if available.
  • Clarify whether PowerShell steps can be performed on PowerShell Core (pwsh) on Linux/macOS, and provide instructions if so.
  • Include links or notes about Teams deployment and user management from non-Windows environments.
  • Explicitly state platform requirements for administrative steps, and suggest remote management options for Linux users.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-ai-javascript.md ...ices/samples/includes/call-automation-ai-javascript.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation shows evidence of Windows bias by referencing Windows-specific tabs in prerequisite links and instructing users to open a PowerShell window to run the application, without mentioning Linux or macOS alternatives. There are no Linux/macOS-specific setup or run instructions, and no mention of equivalent terminal commands or environments.
Recommendations
  • Provide explicit instructions for running the application on Linux and macOS, including using Bash or Terminal instead of PowerShell.
  • Avoid referencing Windows tabs exclusively in prerequisite links; include or default to cross-platform instructions.
  • Add notes or sections highlighting any platform-specific differences in setup or execution.
  • Ensure all command-line examples are compatible with Bash and PowerShell, or provide alternatives where necessary.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-ai-python.md ...services/samples/includes/call-automation-ai-python.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates mild Windows bias, primarily in the prerequisites section where links and instructions default to Windows tabs (e.g., 'Create an Azure Communication Services resource' uses '?tabs=windows'). There are no explicit Linux-specific instructions or examples, and platform-neutral commands are used elsewhere. However, the documentation does not provide Linux-specific setup guidance or examples, and Windows is implicitly prioritized in some links.
Recommendations
  • Provide explicit Linux/macOS instructions or tabs alongside Windows in all setup links and resource creation guides.
  • Ensure that referenced quickstarts and guides default to a platform-neutral or user-selected tab, not Windows by default.
  • Add notes or examples for common Linux/macOS terminal usage, especially for environment setup and running the sample.
  • Review all links and ensure parity in instructions for both Windows and Linux platforms.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/contact-center.md ...les/communication-services/tutorials/contact-center.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its use of Windows-centric tabs and pivots in linked quickstarts and examples. References to 'windows', 'uwp', and 'visual-studio' appear in URLs and tab selectors, while there is a lack of explicit Linux or cross-platform examples or instructions. No Linux-specific tools, commands, or guidance are provided, and Windows terminology is used by default in several places.
Recommendations
  • Add explicit Linux and macOS tabs/pivots to all quickstart and example links, ensuring parity in instructions and code samples.
  • Reference cross-platform development environments (e.g., VS Code, JetBrains IDEs) alongside Visual Studio.
  • Include Linux-specific setup instructions and troubleshooting steps where relevant.
  • Avoid using 'windows' or 'uwp' as the default tab or example; instead, present platform options equally or default to web-based examples.
  • Mention and link to Linux-compatible SDKs, tools, and deployment patterns where available.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/web-calling-hero.md ...nication-services/samples/includes/web-calling-hero.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by listing Windows-specific terminals (PowerShell, Windows Terminal, Command Prompt) first and exclusively in the instructions for cloning the repository, without mentioning Linux or macOS equivalents (e.g., Bash, Terminal, zsh). There are no explicit Linux/macOS examples or tool mentions, and the troubleshooting and setup steps do not address cross-platform considerations.
Recommendations
  • Explicitly mention Linux/macOS terminals (e.g., Bash, Terminal, zsh) alongside Windows terminals in setup instructions.
  • Provide examples or notes for Linux/macOS users where commands or file paths may differ.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, HTTPS requirements, port usage).
  • Ensure parity in tool recommendations (e.g., suggest VS Code for all platforms, mention alternatives if relevant).
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/hmac-header-csharp.md ...tion-services/tutorials/includes/hmac-header-csharp.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows tools (cmd, PowerShell) before Bash when describing how to run commands, and by exclusively referencing Visual Studio for development setup without mentioning Linux alternatives. There are no Linux-specific instructions or examples for installing prerequisites, running the code, or using alternative editors/environments. The documentation assumes a Windows-centric workflow and omits guidance for Linux users.
Recommendations
  • Explicitly mention and provide instructions for Linux environments, such as using VS Code, JetBrains Rider, or command-line editors.
  • List Bash and Linux terminal usage before or alongside Windows tools (cmd, PowerShell) when describing command execution.
  • Include Linux-specific prerequisites, such as installing .NET SDK on Ubuntu or other distributions.
  • Provide troubleshooting tips for common Linux issues (e.g., file permissions, environment variables).
  • Ensure parity in examples and instructions for both Windows and Linux users throughout the documentation.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/enable-closed-captions.md ...on-services/concepts/interop/enable-closed-captions.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. It lists 'Windows' as a supported client-side SDK platform before Linux, and references Teams policies using PowerShell modules (with links to /powershell/module/skype/set-csteamsmeetingpolicy and /powershell/module/skype/set-csteamscallingpolicy) without mentioning Linux equivalents or alternatives. There are no explicit Linux examples, nor is Linux referenced as a supported platform for the SDK.
Recommendations
  • Explicitly mention Linux as a supported platform for the Azure Communication Services client-side SDK if applicable.
  • Provide examples or guidance for Linux users, such as CLI or shell commands, alongside PowerShell references.
  • When referencing Teams policies, include information on how Linux administrators can manage these policies (e.g., via Microsoft Graph API or web portal) if PowerShell is not available.
  • Ensure parity in documentation by listing platforms in a neutral order (e.g., 'Web, Windows, Linux, iOS, and Android') and including Linux in architecture diagrams and feature tables where appropriate.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/entra-id/support-entra-id-users-net.md ...entity/includes/entra-id/support-entra-id-users-net.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by listing Windows console environments (cmd, PowerShell) before Bash when describing where to run commands. There are no explicit Linux-specific instructions, examples, or troubleshooting notes, and the documentation does not mention platform-specific differences in environment variable setup or .NET SDK installation. All examples are generic and do not address Linux users' needs directly.
Recommendations
  • Explicitly mention Linux and macOS environments alongside Windows when referring to console windows, e.g., 'in a console window (such as cmd, PowerShell, Bash, or Terminal)'.
  • Provide platform-specific instructions for setting environment variables (e.g., using 'export' in Bash for Linux/macOS, 'set' in cmd, and '$env:' in PowerShell for Windows).
  • Include troubleshooting notes for common Linux/macOS issues, such as permissions or SDK installation paths.
  • Ensure parity in examples by showing how to run commands and edit files on Linux/macOS (e.g., using nano or vim to edit Program.cs).
  • Add a section or note confirming that the instructions apply equally to Linux/macOS and Windows, and highlight any platform-specific caveats.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-ai-javascript.md ...ices/samples/includes/call-automation-ai-javascript.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exhibits Windows bias by referencing Windows-specific tabs in prerequisite links and instructing users to open a PowerShell window to run the application, without providing equivalent instructions for Linux or macOS users. No Linux/macOS terminal commands or platform-agnostic instructions are given for running the sample.
Recommendations
  • Provide setup and run instructions for Linux and macOS users, including terminal/bash equivalents alongside PowerShell.
  • Avoid referencing Windows-specific tabs or pivots in prerequisite links; ensure parity by linking to platform-neutral or multi-platform instructions.
  • Use generic terms like 'terminal' or 'command prompt' instead of 'PowerShell window' when possible.
  • Explicitly mention cross-platform compatibility and provide any necessary adjustments for non-Windows environments.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-provisioning.md .../interop/tpe/teams-phone-extensibility-provisioning.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Teams administration tasks and cmdlets without specifying cross-platform alternatives or providing Linux/macOS-specific instructions. The use of 'cmdlet' and references to Teams Admin tools implicitly favor Windows/PowerShell environments, and no examples or guidance are given for performing these provisioning or authorization steps on Linux systems.
Recommendations
  • Explicitly state whether provisioning and authorization steps (such as using Teams Admin cmdlets) can be performed on Linux/macOS, and provide equivalent instructions or examples for those platforms.
  • Include cross-platform command-line examples (e.g., using Microsoft Graph API via curl or other REST clients) alongside or instead of PowerShell/cmdlet examples.
  • Reference and link to any available CLI tools or web interfaces that are platform-agnostic.
  • Clarify any platform limitations or requirements for administrators performing these tasks.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/virtual-visits/govern-meeting-experience.md ...ts/interop/virtual-visits/govern-meeting-experience.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Microsoft 365 and Teams administration tools, which are primarily Windows-centric. There are no examples or mentions of Linux-specific tools, command-line interfaces, or cross-platform administration methods. All described management approaches assume use of Microsoft-provided GUIs or services, with no consideration for Linux environments or alternative tooling.
Recommendations
  • Include examples of how Teams meeting policies and options can be managed using cross-platform tools, such as Azure CLI or Microsoft Graph API, which are available on Linux.
  • Explicitly mention whether administrative tasks can be performed from Linux systems and provide instructions or references for doing so.
  • Add notes or sections highlighting any platform limitations, and suggest workarounds or alternatives for Linux administrators.
  • Ensure parity by providing both GUI and command-line examples, and clarify which tools are available on Windows, Linux, and macOS.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/sms/messaging-connect.md ...mmunication-services/concepts/sms/messaging-connect.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page for Messaging Connect does not provide any platform-specific code examples, CLI instructions, or tooling references for Linux environments. All SDK examples are generic (C# and JavaScript), but the provisioning and management flow is described exclusively in terms of the Azure portal (a web interface), with no mention of cross-platform CLI tools (such as Azure CLI or Bash scripting) that are commonly used on Linux. There are no references to Linux-specific patterns, nor are Linux command-line examples or instructions present. The absence of Linux parity is most evident in the lack of Azure CLI or REST API walkthroughs, which are standard for cross-platform documentation. The page implicitly assumes a Windows-first experience by centering the Azure portal and omitting Linux-native workflows.
Recommendations
  • Add Azure CLI examples for provisioning Messaging Connect numbers, sending SMS, and managing resources. This enables Linux and cross-platform users to follow the same workflows without relying on the Azure portal.
  • Include REST API request/response examples for key operations (number provisioning, sending SMS, error handling) to support automation and scripting on any OS.
  • Explicitly mention that all features are available via cross-platform tools and provide links to relevant CLI and API documentation.
  • Add a section comparing portal-based and CLI/API-based workflows, highlighting parity and differences.
  • Ensure troubleshooting and diagnostics instructions include Azure CLI and Bash examples, not just portal navigation.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/sdk-options.md ...rticles/communication-services/concepts/sdk-options.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias, primarily in the SDK platform support section. Windows platforms and tools (UWP, WinUI3, .NET on Windows, Windows Server) are listed first and in greater detail compared to Linux and macOS. There is no mention of Linux-specific tools, package managers, or command-line examples, and Windows-specific deployment notes (e.g., unpackaged app support) are included. However, SDK language support tables do include cross-platform languages and package managers, and Linux is mentioned as supported for .NET Standard 2.0, but with less detail.
Recommendations
  • Add explicit Linux and macOS platform support details in the SDK platform support section, including supported distributions and versions.
  • Include Linux-specific deployment notes and troubleshooting links, similar to the Windows unpackaged app note.
  • Provide parity in example tools and patterns (e.g., mention apt, yum, or other Linux package managers if relevant, or provide CLI examples for Linux/macOS).
  • Ensure that platform lists do not always start with Windows; consider alphabetical or usage-based ordering.
  • Add links to Linux/macOS-specific documentation or quickstarts where available.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/prepend-net.md ...arts/email/send-email-advanced/includes/prepend-net.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows-specific console environments ('cmd', 'PowerShell') before mentioning 'Bash', and by omitting Linux/macOS-specific instructions or examples for common operations such as environment variable setup, application execution, and authentication. All examples and tooling references are generic or Windows-centric, with no explicit Linux parity.
Recommendations
  • Provide explicit Linux/macOS instructions for setting environment variables (e.g., using 'export' in Bash).
  • Include Linux/macOS-specific terminal commands and examples alongside Windows ones, such as using 'Terminal' or 'xterm' instead of only 'cmd' and 'PowerShell'.
  • Add notes or sections clarifying cross-platform compatibility and any OS-specific considerations for .NET SDK usage.
  • Ensure that all code and command examples are demonstrated in both Windows and Linux contexts, where applicable.
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-oauth.md ...kstarts/email/send-email-smtp/send-email-smtp-oauth.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by mentioning Windows-specific console environments (cmd, PowerShell) before Bash when instructing users to create a new C# application. There are no explicit Linux-specific instructions, examples, or troubleshooting notes, and the workflow assumes parity across platforms without addressing potential Linux-specific differences or issues.
Recommendations
  • List Bash (Linux/macOS) before or alongside cmd/PowerShell when referencing console environments.
  • Explicitly mention that the instructions apply to Linux and macOS, and note any platform-specific prerequisites or differences (e.g., package installation, permissions).
  • Provide Linux/macOS-specific troubleshooting tips for .NET and MailKit usage.
  • Include a brief section or note confirming cross-platform compatibility and linking to official .NET documentation for Linux/macOS setup.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/send-email-with-inline-attachments.md ...d-email-advanced/send-email-with-inline-attachments.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for multiple programming languages and command-line interfaces, including Azure CLI and PowerShell. However, PowerShell is featured as a distinct pivot, which is primarily a Windows-centric tool, and there is no mention of Linux shell equivalents (such as Bash scripts) or Linux-specific instructions. The order of pivots places PowerShell immediately after Azure CLI, which may suggest a Windows-first approach. There are no explicit Linux examples or references to Linux tools.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially for command-line operations.
  • Clarify in the documentation that Azure CLI is cross-platform and provide usage notes for both Windows and Linux environments.
  • If PowerShell is included, consider also including examples for other popular Linux shells (e.g., Bash, Zsh) to ensure parity.
  • Review the order of pivots to avoid suggesting Windows tools before Linux equivalents unless justified by usage statistics.
  • Include troubleshooting steps or notes relevant to Linux environments, such as file permissions or package installation.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/active-directory/service-principal-cli.md ...ity/includes/active-directory/service-principal-cli.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by listing only Windows-specific setup articles for managed identities (all links reference Windows VMs), and omits Linux VM equivalents. There are no Linux-specific instructions or examples for setting up managed identities or configuring environment variables, despite the Azure CLI being cross-platform.
Recommendations
  • Include links and instructions for enabling managed identities on Linux VMs using Azure portal, CLI, PowerShell, ARM templates, and SDKs.
  • Provide explicit Linux shell examples for setting environment variables (e.g., export commands for bash/zsh).
  • Clarify that the Azure CLI commands work on both Windows and Linux, and mention any platform-specific considerations.
  • Add parity in guidance for restarting the console or development environment on Linux (e.g., 'restart your terminal session').
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/includes/manage-teams-identity-net.md ...ices/quickstarts/includes/manage-teams-identity-net.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions Windows-specific consoles (cmd, PowerShell) before Bash, and does not provide any Linux-specific instructions or examples. All commands and environment variable usage are presented generically, but there is no explicit guidance for Linux users regarding shell differences, environment variable setup, or editor choices.
Recommendations
  • List Bash (Linux/macOS) before or alongside Windows consoles (cmd, PowerShell) when describing terminal usage.
  • Provide explicit instructions or examples for setting environment variables in Linux (e.g., export AAD_CLIENT_ID=...) and running dotnet commands in Bash.
  • Mention common Linux text editors (e.g., nano, vim) alongside generic 'text editor' instructions.
  • Add troubleshooting notes for platform-specific issues (e.g., file permissions, path separators) that may affect Linux users.
  • Ensure all steps and code samples are verified to work on Linux and macOS, and note any platform-specific differences.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/router/includes/router-quickstart-net.md ...s/quickstarts/router/includes/router-quickstart-net.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by listing Windows-specific console environments (cmd, PowerShell) before Bash when describing where to run commands. All examples use .NET and C#, which are cross-platform, but there are no explicit Linux-specific instructions, troubleshooting, or parity checks. No Linux-specific tools or patterns are mentioned, and there is no guidance for Linux users regarding environment setup or potential differences.
Recommendations
  • List Bash (Linux/macOS) before or alongside cmd/PowerShell when describing console environments.
  • Add explicit notes confirming that all commands and steps work on Linux and macOS, or provide troubleshooting tips for those platforms.
  • Include links or references to .NET installation instructions for Linux and macOS, not just a generic download link.
  • Mention any platform-specific considerations (e.g., file permissions, environment variables) that may affect Linux users.
  • Provide example terminal output from Linux or macOS environments to demonstrate parity.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-ai-python.md ...services/samples/includes/call-automation-ai-python.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page shows mild Windows bias, primarily in the prerequisites section where links default to Windows tabs (e.g., 'Create an Azure Communication Services resource' uses '?tabs=windows'). There are no explicit PowerShell-heavy examples or Windows-only tools, but Linux-specific instructions or parity are missing. The instructions mention running Python from PowerShell, command prompt, or Unix terminal, but do not provide Linux-specific setup or troubleshooting guidance.
Recommendations
  • Ensure all prerequisite links offer both Windows and Linux setup instructions, or default to a neutral tab.
  • Add explicit Linux/macOS setup steps where relevant, such as virtual environment creation and dev tunnel usage.
  • Provide troubleshooting notes for common Linux/macOS issues (e.g., permissions, firewall, Python environment differences).
  • Avoid mentioning Windows tools or environments first; present cross-platform options equally.
  • Include screenshots or command examples from both Windows and Linux terminals.
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-javascript.md ...o-calling/includes/teams-user/teams-user-javascript.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits Windows bias in the prerequisites section, where enabling Teams Phone features for users is referenced via a PowerShell-only link, and the Teams deployment link points to a Windows-centric installation guide. No Linux equivalents or cross-platform instructions are provided for these steps. The rest of the tutorial (JavaScript/web app) is platform-neutral.
Recommendations
  • Include Linux/macOS instructions or links for Teams deployment and management, if available.
  • Reference cross-platform tools (such as Microsoft Graph API or Teams Admin Center web UI) for enabling Teams Phone features, rather than only PowerShell.
  • Explicitly state platform requirements or limitations if certain steps are Windows-only, and suggest alternatives for non-Windows users.
  • Add a note clarifying that the web app code is platform-independent, but some Teams administration steps may require Windows or PowerShell.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/web-calling-hero.md ...nication-services/samples/includes/web-calling-hero.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by listing Windows-specific terminals (PowerShell, Windows Terminal, Command Prompt) first and exclusively in the instructions for cloning the repository, without mentioning Linux or macOS equivalents (such as Bash, Terminal, or iTerm). The use of PowerShell as the primary example for opening a terminal further reinforces this bias. No Linux-specific tools, patterns, or troubleshooting steps are provided.
Recommendations
  • Explicitly mention Linux/macOS terminal options (e.g., Bash, Terminal, iTerm) alongside Windows terminals when instructing users to open a terminal.
  • Provide cross-platform instructions and clarify that the commands (git, npm, az CLI) work on Linux/macOS as well as Windows.
  • Add troubleshooting steps relevant to Linux/macOS environments, such as permissions, HTTPS requirements, or package manager installation notes.
  • Consider including screenshots or examples from Linux/macOS environments to improve parity and inclusivity.
GitHub Create Pull Request
← Previous Page 20 of 27 Next →