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 301-325 of 367 flagged pages
Communication Services Prerequisites ...es/quickstarts/telephony/includes/phone-numbers-net.md
Low 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 mentions Windows-specific consoles (cmd, PowerShell) before Bash, and does not provide any Linux/macOS-specific instructions or troubleshooting. All examples use the dotnet CLI, which is cross-platform, but there is a subtle Windows-first ordering and no explicit Linux/macOS guidance.
Recommendations
  • List Bash (Linux/macOS) before or alongside cmd/PowerShell when mentioning console windows.
  • Include explicit notes or troubleshooting tips for Linux/macOS users (e.g., permissions, environment variable setup).
  • Provide example commands for setting environment variables on both Windows (set/PowerShell) and Linux/macOS (export).
  • Clarify that all dotnet CLI commands work on Linux/macOS and Windows.
  • Add a section or note confirming support and parity for Linux/macOS users.
GitHub Create Pull Request
Communication Services include file ...kstarts/telephony/includes/voice-routing-sdk-csharp.md
Low 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 Windows-specific tools (Command Prompt, PowerShell) first when describing how to create a C# application, with Bash only mentioned as an afterthought. There are no explicit Linux/macOS-specific instructions or examples, and the overall flow assumes familiarity with Windows environments.
Recommendations
  • List Bash (Linux/macOS) first or equally alongside Windows tools when describing console usage.
  • Explicitly mention that all dotnet CLI commands work on Linux/macOS terminals.
  • Provide a brief note or example for installing .NET Core on Linux/macOS, or link to platform-specific installation guides.
  • Clarify any file path or environment variable differences for non-Windows platforms if relevant.
GitHub Create Pull Request
Communication Services Access a user's Teams Phone separate from their Teams client ...ts/tpe/teams-phone-extensibility-access-teams-phone.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation demonstrates mild Windows bias by referencing Windows-specific tools (Microsoft 365 admin center, PowerShell cmdlet) and UI patterns before or instead of platform-agnostic or Linux/macOS alternatives. The only explicit tool for retrieving the Resource Account ObjectId is a PowerShell cmdlet, and the user enablement workflow is described via the Microsoft 365 admin center, which is most accessible on Windows. No Linux/macOS-specific instructions or CLI alternatives are provided for these steps.
Recommendations
  • Provide equivalent instructions for enabling Teams users via CLI tools (e.g., Azure CLI, Microsoft Graph API) that work cross-platform.
  • Offer Linux/macOS-friendly alternatives to the PowerShell cmdlet for retrieving Resource Account ObjectId, such as Graph API queries.
  • Explicitly note that all REST API examples are platform-agnostic and can be executed from any OS using tools like curl, Postman, or native SDKs.
  • Reorder examples to present platform-neutral or cross-platform methods first, followed by Windows-specific options.
GitHub Create Pull Request
Communication Services Quickstart - Make a call to Teams user from a web app ...o-calling/includes/teams-user/teams-user-javascript.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias in the prerequisites section, where enabling Teams Phone features for users is described using a PowerShell-based process and links to Windows-centric documentation. No Linux/macOS alternatives or parity guidance are provided for these administrative steps. The rest of the tutorial (JavaScript code, web app setup, and running with webpack) is platform-agnostic.
Recommendations
  • Add explicit guidance for enabling Teams Phone features using Microsoft 365 admin center (web UI), which is cross-platform.
  • If PowerShell is required, clarify that PowerShell Core is available on Linux/macOS and provide instructions for installation and usage on those platforms.
  • Include links or notes about how Linux/macOS users can perform Teams user management tasks, or state any limitations.
  • Review linked documentation to ensure Linux/macOS parity is addressed for administrative tasks.
GitHub Create Pull Request
Communication Services Chat Hero Sample ...les/communication-services/samples/chat-hero-sample.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions Windows-specific terminals (PowerShell, Windows Terminal, Command Prompt) first when instructing users to open a shell to clone the repository, with only a vague 'or equivalent' for non-Windows platforms. No explicit Linux/macOS terminal examples or instructions are provided, but the actual commands are cross-platform.
Recommendations
  • Explicitly mention Linux/macOS terminals (e.g., 'Open an instance of PowerShell, Windows Terminal, Command Prompt, Terminal (macOS), or a Linux shell...').
  • Provide a note confirming that all commands work on Linux/macOS and suggest using the native terminal.
  • If there are platform-specific steps or files, clarify them for Linux/macOS users.
  • Consider listing terminals in a neutral or alphabetical order to avoid implicit prioritization.
GitHub Create Pull Request
Communication Services Include file ...ices/samples/includes/call-automation-ai-javascript.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by instructing users to open a PowerShell window to run the application, without mentioning Linux/macOS terminal alternatives or providing cross-platform instructions. The prerequisites and setup steps do not reference Windows-specific tools, but the 'Run the application' section assumes a Windows environment and PowerShell usage.
Recommendations
  • Replace 'Open a new PowerShell window' with 'Open a terminal or command prompt window' to be inclusive of Linux/macOS users.
  • Explicitly state that the npm commands can be run in any terminal (PowerShell, Command Prompt, Terminal.app, bash, etc.).
  • Provide example commands for Linux/macOS users if there are any platform-specific differences.
  • Ensure links and instructions do not default to Windows tabs unless necessary.
GitHub Create Pull Request
Communication Services Using ACS UI library JavaScript bundles with Teams Call Queues and Auto Attendants ...tutorials/calling-widget/calling-widget-js-tutorial.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation shows a minor Windows bias by presenting Windows command prompt instructions before macOS equivalents in the 'Creating the project' section. However, all commands and tooling are cross-platform, and Linux is implicitly supported (though not explicitly mentioned). There are no Windows-only tools, PowerShell-heavy examples, or missing Linux instructions.
Recommendations
  • Explicitly mention Linux alongside macOS when providing platform-specific instructions.
  • Provide Linux-specific command examples if there are any subtle differences (e.g., shell syntax, package managers).
  • Use inclusive phrasing such as 'On Linux/macOS' instead of just 'For macOS'.
  • Consider listing platform instructions in alphabetical order or grouping them together to avoid perceived priority.
GitHub Create Pull Request
Communication Services Include file ...services/samples/includes/call-automation-ai-python.md
Low 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 exhibits minor Windows bias, primarily in the prerequisites section where links default to Windows-specific tabs or pivots, and in the absence of explicit Linux/macOS instructions or examples. However, most commands and instructions are cross-platform and do not rely on Windows-only tools.
Recommendations
  • Ensure prerequisite links do not default to Windows tabs; provide direct parity for Linux/macOS setup steps.
  • Explicitly mention that all CLI commands (pip, devtunnel) work on Linux/macOS, and provide any necessary platform-specific notes.
  • Include examples or screenshots for Linux/macOS environments where relevant.
  • Clarify that running Python scripts and using dev tunnels is supported on all major platforms.
GitHub Create Pull Request
Communication Services Contact centers with Azure Communication Services ...les/communication-services/tutorials/contact-center.md
Low 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 exhibits a mild Windows bias, primarily in the way quickstart links and code tabs default to Windows/UWP platforms and programming languages, with no explicit Linux/macOS examples or parity. References to platform-specific tabs (e.g., 'windows', 'uwp', 'platform-azp') are shown first or exclusively, and there are no instructions or examples tailored for Linux or macOS environments.
Recommendations
  • Add explicit Linux/macOS quickstart links and tabs where platform-specific instructions are given.
  • Ensure code samples and setup instructions include Linux/macOS equivalents, especially for SDK usage and environment setup.
  • When listing platform options, present them in a neutral order (e.g., 'Windows, Linux, macOS') or group by functionality rather than OS.
  • Clarify which features and SDKs are cross-platform and provide guidance for non-Windows users where relevant.
GitHub Create Pull Request
Communication Services Sign an HTTP Request with C# ...tion-services/tutorials/includes/hmac-header-csharp.md
Low 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 shows a mild Windows bias by listing Windows tools (cmd, PowerShell) before Bash when describing how to run dotnet commands. It also assumes the use of Visual Studio, which is primarily a Windows IDE, and does not mention cross-platform alternatives like VS Code or JetBrains Rider. There are no explicit Linux/macOS-specific instructions or troubleshooting notes, and no mention of platform-specific issues that may arise (e.g., certificate stores, environment setup). However, the actual code and commands are cross-platform, and Linux users can follow along with minor adjustments.
Recommendations
  • List Bash (Linux/macOS) before or alongside cmd/PowerShell when describing console usage.
  • Mention cross-platform IDEs such as Visual Studio Code or JetBrains Rider in prerequisites.
  • Add a note confirming that all dotnet CLI commands and code samples work on Linux and macOS.
  • Include troubleshooting tips for Linux/macOS users (e.g., permissions, environment variables, package installation).
GitHub Create Pull Request
Communication Services Calling capabilities for Teams users ...cation-services/concepts/interop/teams-user-calling.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. Windows is listed as a primary platform in feature tables, and references to Microsoft Entra and Graph API link to PowerShell modules, which are Windows-centric tools. There are no explicit Linux examples or mentions of Linux desktop support, and Windows terminology is used preferentially. However, the SDK itself is cross-platform (JavaScript, Android, iOS), and most features are not exclusive to Windows.
Recommendations
  • Add explicit references to Linux desktop support in feature tables and introductory sections.
  • Include links to Microsoft Graph API documentation for REST and CLI usage, not just PowerShell.
  • Where platform-specific APIs are mentioned, clarify Linux/macOS equivalents or limitations.
  • Avoid listing Windows before other platforms in tables and descriptions; consider alphabetical or usage-based ordering.
  • Provide Linux/macOS-specific troubleshooting or integration notes if applicable.
GitHub Create Pull Request
Communication Services Teams Phone extensibility overview ...epts/interop/tpe/teams-phone-extensibility-overview.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the 'Emergency calling' section, where Teams admins are instructed to configure emergency calling policies using the TAC portal and/or PowerShell cmdlets. PowerShell is a Windows-centric tool, and its mention without Linux/macOS alternatives suggests a preference for Windows administration. No explicit Linux/macOS examples or equivalent tools are referenced, and Windows administrative patterns (PowerShell) are mentioned before any cross-platform or web-based alternatives.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as using Microsoft Teams Admin Center (web portal) or cross-platform CLI tools where available.
  • Explicitly mention if PowerShell cmdlets can be run on PowerShell Core (which is cross-platform), and provide installation guidance for non-Windows environments.
  • Add examples or links for performing Teams Phone administration tasks using REST APIs, Graph API, or other cross-platform methods.
  • Clarify which administrative steps can be performed via browser-based portals, reducing reliance on Windows-specific tools.
GitHub Create Pull Request
Communication Services Teams Phone extensibility FAQ .../concepts/interop/tpe/teams-phone-extensibility-faq.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the section on emergency calling configuration, which references the Teams Admin Center (TAC) portal and PowerShell cmdlets as the methods for configuration. These tools are Windows-centric, with PowerShell examples and workflows typically tailored to Windows environments. No Linux/macOS alternatives (such as CLI, REST API, or cross-platform scripting) are mentioned, and Windows tools are referenced first and exclusively. However, most of the page is conceptual and does not provide platform-specific code or step-by-step instructions.
Recommendations
  • Include Linux/macOS-compatible configuration methods, such as using Microsoft Graph API, Azure CLI, or cross-platform PowerShell Core.
  • Explicitly mention whether PowerShell cmdlets can be run on Linux/macOS via PowerShell Core, and provide examples if so.
  • Add links or references to cross-platform tools or documentation for Teams administration.
  • When listing configuration options, avoid listing Windows tools first or exclusively; provide parity in examples and instructions.
GitHub Create Pull Request
Communication Services Send email with SMTP and XOAuth2 using .NET ...kstarts/email/send-email-smtp/send-email-smtp-oauth.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page shows a mild 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/macOS-specific instructions or troubleshooting notes, and all examples are generic .NET/C# code, which is cross-platform. However, the absence of Linux/macOS-specific guidance or parity checks (e.g., package installation, environment setup) may create minor friction for non-Windows users.
Recommendations
  • List Bash (Linux/macOS) first or equally alongside cmd/PowerShell when referencing console environments.
  • Add explicit notes or troubleshooting tips for Linux/macOS users (e.g., installing .NET Core, MailKit on Linux/macOS).
  • Include a short section confirming that the instructions work on Linux/macOS and mention any platform-specific caveats.
  • Provide links to .NET installation guides for Linux/macOS.
  • Clarify that the instructions are cross-platform and highlight any OS-specific differences if applicable.
GitHub Create Pull Request
Communication Services Pricing for Teams interop scenarios ...ion-services/concepts/pricing/teams-interop-pricing.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias by mentioning the Teams Desktop client and Windows/Chrome browser before other platforms, and by referencing PowerShell cmdlets (Set-CsPhoneNumberAssignment) for license assignment without offering Linux/macOS alternatives. No explicit Linux/macOS examples or parity guidance are provided.
Recommendations
  • Include explicit examples or instructions for Linux and macOS users, such as how to assign Teams Phone licenses via Azure CLI, REST API, or other cross-platform tools.
  • Mention Teams Desktop client availability and parity on Linux/macOS, or clarify any platform-specific limitations.
  • When referencing command-line tools (e.g., PowerShell), provide alternative methods for non-Windows environments, or link to cross-platform documentation.
  • Ensure scenario descriptions do not default to Windows or Windows-first language; use neutral phrasing or rotate platform order.
GitHub Create Pull Request
Communication Services include file ...tion-services/quickstarts/chat/includes/chat-csharp.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Visual Studio is listed as a prerequisite without mention of cross-platform alternatives. The package installation example uses PowerShell syntax, and Windows-centric tools (cmd, PowerShell) are mentioned before Bash. There are no explicit Linux/macOS setup instructions or examples, and the documentation does not clarify that the .NET SDK and CLI commands are cross-platform.
Recommendations
  • Mention that Visual Studio Code and other editors are cross-platform alternatives to Visual Studio.
  • Provide explicit Linux/macOS instructions for prerequisites and setup, including package installation and running the application.
  • Show Bash/zsh equivalents for all command-line examples, especially for package installation (e.g., 'dotnet add package' in Bash).
  • Clarify that the Azure CLI and .NET SDK are cross-platform and can be used on Linux/macOS.
  • List Bash before or alongside cmd/PowerShell when referencing console windows.
GitHub Create Pull Request
Communication Services include file ...s/quickstarts/router/includes/router-quickstart-net.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
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 all command-line examples use the generic 'console' tag without explicit Linux/macOS instructions. There are no Linux/macOS-specific notes, troubleshooting, or environment setup details. The focus is on .NET, which is cross-platform, but the documentation does not demonstrate parity by showing Linux/macOS workflows or addressing platform-specific concerns.
Recommendations
  • Explicitly mention Linux/macOS consoles (e.g., Terminal, Bash, zsh) alongside Windows options.
  • Provide example commands and screenshots for Linux/macOS environments, including package installation and running the app.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, .NET installation).
  • Clarify that the .NET SDK and commands work cross-platform, and link to .NET installation guides for Linux/macOS.
  • Ensure that references to command-line tools do not prioritize Windows environments.
GitHub Create Pull Request
Communication Services include file ...ces/quickstarts/rooms/includes/rooms-quickstart-net.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by mentioning Windows console environments (cmd, PowerShell) before Bash, and by providing only .NET/C# examples, which are most commonly associated with Windows development. However, the commands used (dotnet CLI) and the code samples are cross-platform and can be used on Linux/macOS as well. There are no explicit Windows-only tools or instructions, but Linux/macOS users may feel secondary due to ordering and lack of explicit parity examples.
Recommendations
  • List Bash (Linux/macOS) before or alongside cmd/PowerShell when mentioning console windows.
  • Explicitly state that all dotnet CLI commands and code samples work on Linux and macOS.
  • Provide example output or screenshots from Linux/macOS terminals.
  • Mention installation steps for .NET Core on Linux/macOS, or link to OS-specific instructions.
  • Clarify that NuGet and dotnet CLI are cross-platform tools.
GitHub Create Pull Request
Communication Services Messaging Connect overview ...mmunication-services/concepts/sms/messaging-connect.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page does not provide any OS-specific command-line or scripting examples, but in the SDK tutorial section, only C# (.NET) and JavaScript examples are given, with no mention of Linux/macOS-specific tools, shell commands, or SDK usage patterns. The C# example implicitly prioritizes Windows/.NET environments, and the absence of Python or Java examples (not yet supported, but mentioned as 'coming soon') means Linux users have less parity. There are no references to Powershell, Windows-only tools, or explicit Windows-centric instructions, but the ordering and example selection favor Windows-first development.
Recommendations
  • Add explicit Linux/macOS usage notes, such as how to use the SDKs in those environments.
  • When Python and Java SDKs become available, include examples for those languages, as they are popular on Linux/macOS.
  • Provide CLI or REST API examples using curl or bash to demonstrate cross-platform usage.
  • Clarify that the JavaScript SDK works on Node.js across platforms, and that .NET Core can run on Linux/macOS.
  • Avoid implying Windows-first by listing cross-platform examples before or alongside Windows-centric ones.
GitHub Create Pull Request
Communication Services include file ...nication-services/samples/includes/web-calling-hero.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page shows a mild Windows bias by listing Windows-specific terminals (PowerShell, Windows Terminal, Command Prompt) first when instructing users to open a shell to clone the repository. No explicit Linux/macOS examples or terminal recommendations are given, though the instructions themselves are cross-platform. There is no evidence of Windows-only tools or missing Linux/macOS examples for critical steps.
Recommendations
  • Explicitly mention Linux/macOS terminals (e.g., Bash, Terminal.app, GNOME Terminal) alongside Windows options when instructing users to open a shell.
  • Add a note confirming that all commands (git, npm, az CLI) work on Linux/macOS and provide links to installation instructions for these platforms.
  • Consider providing OS-agnostic instructions or grouping shell/terminal recommendations by platform.
GitHub Create Pull Request
Communication Services Include file ...services/samples/includes/call-automation-ai-python.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation shows a minor Windows bias by linking to resource creation guides with Windows tabs selected by default and mentioning PowerShell and command prompt before Unix terminal when describing how to run the Python sample. However, Linux/macOS users are not blocked and can follow the instructions with minimal friction.
Recommendations
  • Ensure all resource creation links default to a neutral or platform-agnostic tab, or explicitly mention Linux/macOS instructions alongside Windows.
  • When listing ways to run commands, use 'Unix terminal, PowerShell, or command prompt' or simply 'terminal' to avoid Windows-first phrasing.
  • Add explicit notes or examples for Linux/macOS users where platform-specific steps may differ, especially in setup or troubleshooting sections.
GitHub Create Pull Request
Communication Services Subscribe to events in Job Router ...cation-services/how-tos/router-sdk/subscribe-events.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation shows minor Windows bias in the quick-start section, where Windows shells (cmd, PowerShell) are mentioned before Bash when instructing users to create a new C# application. All provided code and commands are cross-platform, and there are no Windows-only tools or examples, but the ordering of shell references gives Windows precedence.
Recommendations
  • List Bash (Linux/macOS) first or equally alongside cmd/PowerShell when referencing console windows.
  • Explicitly state that all commands and code samples work on Linux, macOS, and Windows.
  • Add a note or section confirming Linux/macOS compatibility for the quick-start steps.
GitHub Create Pull Request
Communication Services include file ...uickstarts/email/includes/send-email-async-sync-net.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily provides instructions and examples for using the Azure Communication Services Email client library with .NET, but it shows subtle Windows bias. Console examples mention 'cmd' and 'PowerShell' before 'Bash', and there are no explicit Linux/macOS-specific instructions or troubleshooting notes. All examples use .NET CLI commands, which are cross-platform, but the documentation does not demonstrate or acknowledge Linux/macOS environments beyond mentioning Bash as a possible console. There are no Linux-specific code snippets, screenshots, or notes about platform differences.
Recommendations
  • Explicitly mention Linux/macOS compatibility in prerequisites and instructions.
  • Provide Linux/macOS-specific examples, such as using Bash or zsh, and show environment variable setup for those shells.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, path differences).
  • Add screenshots or terminal output examples from Linux/macOS environments.
  • List Bash/zsh before Windows consoles when mentioning terminal options, or present them together.
GitHub Create Pull Request
Communication Services Using ACS UI library JavaScript bundles with Teams Call Queues and Auto Attendants ...tutorials/calling-widget/calling-widget-js-tutorial.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and macOS commands for creating a project directory, but lists the Windows command first. No other Windows-specific tools, patterns, or examples are present. All other instructions and code samples are cross-platform and use standard tools (Node.js, VS Code, npx http-server) available on Linux/macOS/Windows.
Recommendations
  • List platform-specific commands in parallel or alphabetical order (e.g., Linux/macOS first, or side-by-side).
  • Explicitly mention Linux as a supported platform where macOS is referenced.
  • Include a Linux-specific command example for creating directories (even though it matches macOS).
  • Add a note confirming that all steps work on Linux, macOS, and Windows.
GitHub Create Pull Request
Communication Services include file ...arts/email/send-email-advanced/includes/prepend-net.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-specific console environments (cmd, PowerShell) before Bash when describing how to create a new C# application. All command-line instructions use generic 'dotnet' commands, which are cross-platform, but there are no Linux/macOS-specific examples or notes. No Windows-only tools or PowerShell scripts are used, but the absence of explicit Linux/macOS instructions or troubleshooting tips may create minor friction for non-Windows users.
Recommendations
  • Explicitly mention Linux/macOS terminal environments alongside Windows (e.g., 'In a console window (such as cmd, PowerShell, Terminal, or Bash)').
  • Add notes or examples for Linux/macOS users, such as verifying .NET installation or setting environment variables.
  • Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, path differences).
  • Ensure screenshots or references to file paths are platform-neutral or provide alternatives.
GitHub Create Pull Request
← Previous Page 13 of 15 Next →