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 401-425 of 656 flagged pages
Communication Services Contact centers with Azure Communication Services ...les/communication-services/tutorials/contact-center.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in its use of 'tabs=windows' and 'tabs=uwp' in quickstart links, with no equivalent Linux/macOS examples or pivots. Windows platforms and tools are referenced first or exclusively in several places, making it less clear how Linux/macOS users should proceed.
Recommendations
  • Add explicit Linux/macOS pivots/examples to all quickstart and reference links, ensuring parity in setup and usage instructions.
  • Avoid using 'tabs=windows' or 'tabs=uwp' as the default or only example; provide platform-neutral or cross-platform instructions where possible.
  • Include notes or sections clarifying how Linux/macOS users can complete the same tasks, especially for SDK usage and environment setup.
  • Ensure that any referenced tools (e.g., Azure portal, SDKs) are described in a way that highlights cross-platform compatibility.
GitHub Create Pull Request
Communication Services Migrating from Twilio Conversations Chat to Azure Communication Services Chat C# ...orials/includes/twilio-to-acs-chat-android-tutorial.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
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 primarily in the prerequisites and setup sections. Visual Studio is listed as the required IDE without mention of cross-platform alternatives, and the package installation example uses PowerShell syntax ('dotnet add package'), which is typically associated with Windows. There are no explicit Linux/macOS setup instructions or examples, and no mention of Linux-friendly development environments or CLI usage outside of Azure CLI. The order and language of examples assume a Windows development environment, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit instructions for Linux/macOS users in the prerequisites, such as recommending VS Code or JetBrains Rider as cross-platform IDEs.
  • Clarify that 'dotnet add package' works on Linux/macOS terminals and provide a Bash/zsh example.
  • Mention that Azure CLI is cross-platform and provide installation links for Linux/macOS.
  • Add a note that all C# code samples are OS-agnostic and can be run on any platform with .NET installed.
  • Consider reordering examples or providing parallel instructions for Windows and Linux/macOS where setup or tooling differs.
GitHub Create Pull Request
Communication Services Migrating from Twilio Conversations Chat to Azure Communication Services Chat C# ...torials/includes/twilio-to-acs-chat-csharp-tutorial.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the prerequisites and setup sections. Visual Studio is listed as the only IDE, and the package installation example uses PowerShell syntax (dotnet CLI) without mentioning Linux/macOS alternatives or cross-platform editors. No Linux/macOS-specific instructions or parity notes are provided, and Windows tools/patterns are presented first or exclusively.
Recommendations
  • Add instructions for installing the .NET SDK and Azure Communication Services Chat package on Linux/macOS, including terminal/bash examples.
  • Mention cross-platform IDEs such as VS Code or JetBrains Rider alongside Visual Studio.
  • Clarify that the dotnet CLI works on Windows, Linux, and macOS, and provide shell/bash examples where appropriate.
  • Include notes or links for Linux/macOS users regarding environment setup, especially for Azure CLI usage and authentication.
  • Explicitly state platform compatibility for all tools and SDKs referenced.
GitHub Create Pull Request
Communication Services Teams Phone extensibility provisioning .../interop/tpe/teams-phone-extensibility-provisioning.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses on Teams Phone extensibility provisioning and authorization, but all procedural references (such as cmdlets and admin roles) assume a Windows-centric environment. There are no examples or guidance for Linux or cross-platform administration, and Windows terminology (cmdlet, Teams Admin) is used exclusively. No Linux shell, CLI, or cross-platform tool examples are provided.
Recommendations
  • Include equivalent Linux shell (bash) or Azure CLI examples for provisioning and authorization steps.
  • Clarify whether the described cmdlets and admin tools are available cross-platform, and provide links or instructions for Linux/macOS users.
  • Mention and document any cross-platform tools (e.g., Azure CLI, Microsoft Graph API via REST) that can be used for these tasks.
  • Avoid using Windows-specific terminology (such as 'cmdlet') without also referencing cross-platform alternatives.
  • Add a section explicitly addressing cross-platform support and any limitations for Linux or macOS administrators.
GitHub Create Pull Request
Communication Services Enable Closed captions with Teams Interoperability ...on-services/concepts/interop/enable-closed-captions.md
Medium 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 references Teams policies with links to PowerShell modules (Set-CsTeamsMeetingPolicy, Set-CsTeamsCallingPolicy), which are primarily managed via Windows-centric tools. There is no mention of Linux equivalents or cross-platform management options for these policies. Additionally, the supported SDKs list 'Windows' before other platforms, and there are no Linux-specific examples or guidance provided.
Recommendations
  • Include information about managing Teams policies via cross-platform tools (e.g., Microsoft Graph API) alongside or instead of PowerShell references.
  • Add explicit mention of Linux support for Azure Communication Services SDKs, if available, and provide Linux-specific usage examples.
  • Ensure that platform lists (e.g., supported SDKs) do not prioritize Windows unless there is a technical reason, and clarify parity across platforms.
  • Where PowerShell or Windows tools are referenced, provide alternatives or note limitations for non-Windows users.
GitHub Create Pull Request
Communication Services Messaging Connect overview ...mmunication-services/concepts/sms/messaging-connect.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page demonstrates a subtle Windows bias by exclusively referencing the Azure portal (a web UI most commonly used on Windows) for provisioning and management steps, and by omitting any Linux-specific or cross-platform command-line examples (such as Azure CLI, Bash, or PowerShell). All SDK code samples are in C# and JavaScript, with no mention of Linux-friendly languages or tools (e.g., Python, Bash, Azure CLI). There is no guidance for Linux users on how to perform provisioning or management tasks outside the portal, nor are there any examples using Linux-native tools.
Recommendations
  • Add Azure CLI and/or Bash examples for provisioning Messaging Connect numbers and sending SMS, alongside or before portal instructions.
  • Include Python SDK examples once available, and mention their roadmap.
  • Explicitly state that all steps can be performed from any OS, and provide parity for Linux/macOS users in instructions and screenshots.
  • Reference cross-platform tools (e.g., Azure CLI, REST API) in the developer experience section, not just the portal.
  • Add troubleshooting and configuration notes relevant to Linux environments (e.g., environment variables, authentication setup).
GitHub Create Pull Request
Communication Services Subscribe to events in Job Router ...cation-services/how-tos/router-sdk/subscribe-events.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias in its quick-start instructions. When instructing users to create a new C# application, it lists 'cmd, PowerShell, or Bash' as possible console windows, but the order places Windows tools first. More importantly, all code and command-line examples use .NET (dotnet CLI) and C#, which are cross-platform but are more familiar to Windows users. There are no Linux- or macOS-specific instructions, nor are there any examples using Linux-native tools or scripting languages (e.g., Python, Bash scripts) for subscribing to or consuming events. The documentation does not mention or demonstrate Linux-specific patterns or troubleshooting.
Recommendations
  • Explicitly state that all dotnet CLI commands and C# code are fully cross-platform and supported on Linux and macOS as well as Windows.
  • When listing console options, rotate or randomize the order, or explicitly say 'cmd, PowerShell (Windows), or Bash (Linux/macOS)'.
  • Provide at least one example using a Linux-native scripting language (e.g., Python) to consume messages from Azure Storage Queue, or link to such examples.
  • Include troubleshooting notes or tips for Linux users (e.g., installing dotnet SDK on Linux, permissions for Bash, etc.).
  • Consider adding a section or callout highlighting parity and support for Linux and macOS environments.
GitHub Create Pull Request
Communication Services include file ...s/quickstarts/router/includes/router-quickstart-net.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by listing Windows console environments (cmd, PowerShell) before Bash when describing where to run commands. All command-line instructions use the 'dotnet' CLI, which is cross-platform, but there are no Linux-specific examples, troubleshooting notes, or references to Linux package managers. The documentation does not mention Linux-specific considerations or provide parity for Linux users beyond the generic mention of Bash.
Recommendations
  • List Bash (Linux/macOS) before or alongside cmd/PowerShell when mentioning console environments.
  • Add explicit instructions or troubleshooting notes for Linux users, such as permissions, environment setup, or common issues.
  • Include references to Linux package managers (e.g., apt, yum) for installing .NET, or link to official .NET installation guides for Linux.
  • Provide sample output screenshots or terminal commands from a Linux environment to demonstrate parity.
  • Clarify that the instructions are cross-platform and highlight any platform-specific differences where relevant.
GitHub Create Pull Request
Communication Services include file ...ices/quickstarts/includes/manage-teams-identity-net.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation refers to 'console window (such as cmd, PowerShell, or Bash)', listing Windows shells first and omitting Linux-specific examples or instructions. All command-line examples use generic 'dotnet' commands, but there is no mention of Linux-specific tools, shells, or environment setup. There are no examples of how to run or configure the application on Linux, nor any troubleshooting or notes for Linux users.
Recommendations
  • Explicitly mention Linux shells (e.g., Bash, Zsh) first or equally alongside Windows shells.
  • Provide Linux-specific instructions or notes, such as how to set environment variables in Bash (e.g., export AAD_CLIENT_ID=...) and how to run the application on Linux.
  • Include troubleshooting tips for common Linux issues (e.g., permissions, .NET SDK installation).
  • Add a section or note on cross-platform compatibility, clarifying that the instructions work on both Windows and Linux, and highlight any platform-specific differences.
GitHub Create Pull Request
Communication Services Send email with SMTP and XOAuth2 using .NET ...kstarts/email/send-email-smtp/send-email-smtp-oauth.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by listing Windows-specific console environments ('cmd', 'PowerShell') before Linux equivalents ('Bash') and not providing any Linux-specific instructions or examples. All code and tooling references are platform-neutral (.NET Core, MailKit), but the guidance and examples do not address Linux-specific setup, troubleshooting, or alternative workflows.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms in prerequisites and instructions.
  • Provide Linux/macOS-specific terminal commands and environment setup steps alongside Windows examples.
  • Include troubleshooting notes or tips for common Linux issues (e.g., permissions, package installation).
  • List Bash (or other Linux shells) first or equally when referencing console windows.
  • Clarify that .NET Core and MailKit are cross-platform and provide links to Linux/macOS installation guides.
GitHub Create Pull Request
Communication Services include file ...entity/includes/entra-id/support-entra-id-users-net.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions Windows-specific consoles (cmd, PowerShell) before Bash, and does not provide any Linux-specific instructions or examples for environment variable setup, text editor usage, or running the application. All examples and tooling are generic to .NET, but the workflow assumes familiarity with Windows environments.
Recommendations
  • Explicitly mention Linux and macOS consoles (e.g., Terminal, zsh, bash) alongside Windows ones.
  • Provide examples of setting environment variables in Linux/macOS (e.g., export ENTRA_CLIENT_ID=...) as well as Windows (set ENTRA_CLIENT_ID=...).
  • Suggest cross-platform text editors (e.g., nano, vim, VS Code) for editing Program.cs.
  • Clarify that all dotnet CLI commands work on Linux/macOS and Windows.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, SDK installation).
GitHub Create Pull Request
Communication Services Additional Prerequisites ...ity/includes/active-directory/service-principal-cli.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page consistently references Windows-specific resources and examples, particularly in the section about enabling managed identities for Azure resources. All linked quickstart articles are for Windows VMs, and there are no equivalent Linux VM examples or instructions. The guidance for setting environment variables is generic, but the overall setup flow and linked resources prioritize Windows environments, omitting Linux-specific instructions and parity.
Recommendations
  • Include links to equivalent quickstart guides for Linux VMs for managed identity configuration using Azure portal, PowerShell, CLI, ARM templates, and SDKs.
  • Add explicit examples or notes for setting environment variables in Linux shells (e.g., export commands for Bash/Zsh).
  • Ensure that all instructions and references are platform-neutral or provide parallel steps for both Windows and Linux environments.
  • Mention Linux development environments (e.g., VS Code on Linux, JetBrains IDEs) alongside Windows-specific tools like Visual Studio.
GitHub Create Pull Request
Communication Services Overview ...ity/includes/active-directory/service-principal-net.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by listing Windows terminals (Command Prompt, PowerShell) before Bash when instructing users to open a terminal. There are no explicit Linux-specific instructions, troubleshooting, or examples, and no mention of Linux package managers or environment setup. All commands are cross-platform (dotnet CLI), but the documentation does not provide parity for Linux users beyond mentioning Bash in passing.
Recommendations
  • List Bash (or Linux terminal) first when mentioning terminal options, or present all platforms equally.
  • Add explicit instructions for Linux users, such as verifying .NET SDK installation via package managers (e.g., apt, yum) and environment setup.
  • Include troubleshooting steps for common Linux issues (e.g., permissions, environment variables).
  • Clarify that all commands are cross-platform and provide links to .NET installation guides for Linux.
  • Consider adding a note or section on running the sample in Linux environments, including any OS-specific caveats.
GitHub Create Pull Request
Communication Services include file ...ces/quickstarts/includes/telemetry-app-insights-net.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation refers to 'cmd, PowerShell, or Bash' as possible console windows, but lists Windows shells first and does not provide any Linux-specific instructions, examples, or troubleshooting. All command-line examples use generic 'dotnet' commands without platform-specific notes, and there is no mention of Linux tools, editors, or environment setup. The guidance assumes parity but does not demonstrate it.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms in prerequisites and setup steps.
  • Provide Linux/macOS-specific instructions or notes where relevant (e.g., environment variable setup, file permissions, common editors like nano/vim).
  • Include troubleshooting tips for common Linux issues (e.g., SDK installation, PATH configuration).
  • List Bash before or alongside Windows shells to avoid Windows-first ordering.
  • Add example commands for setting environment variables in Bash/zsh (e.g., export COMMUNICATION_SERVICES_CONNECTION_STRING=...) and running the app.
  • Reference cross-platform editors (VS Code, nano, vim) when suggesting how to edit Program.cs.
GitHub Create Pull Request
Communication Services Answer Teams Phone calls from Call Automation ...ts/tpe/teams-phone-extensibility-answer-teams-calls.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. Key setup steps, such as creating a Teams resource account and associating it with Azure Communication Services, rely exclusively on PowerShell commands and reference PowerShell modules. The DevTunnel setup is shown only with PowerShell commands, with no mention of Linux/macOS alternatives or CLI parity. There are no Linux/macOS-specific instructions or examples, and Windows tooling is presented first and exclusively.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as Azure CLI or Bash commands where possible.
  • Reference cross-platform tools for DevTunnel setup, or clarify if the PowerShell commands work on Linux/macOS (e.g., via PowerShell Core).
  • Offer guidance for creating and managing Teams resource accounts via REST API or other cross-platform methods if available.
  • Explicitly state platform requirements and limitations for each step.
  • Add Linux/macOS examples alongside Windows/PowerShell ones, or at least link to platform-specific guides.
GitHub Create Pull Request
Communication Services Quickstart - How to call to Teams user from an Android app ...ideo-calling/includes/teams-user/teams-user-android.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references enabling Teams Phone features via PowerShell and links to Windows-centric Teams deployment guides, without mentioning Linux/macOS alternatives or parity. No Linux/macOS-specific instructions or examples are provided for Teams administration tasks, which may create friction for non-Windows users.
Recommendations
  • Include instructions or links for managing Teams users and licenses via cross-platform tools (e.g., Microsoft 365 admin center web UI) or clarify PowerShell Core support on Linux/macOS.
  • Explicitly state whether Teams Phone license and Enterprise Voice enabling can be performed from non-Windows platforms, and provide relevant guidance.
  • Add notes or sections for Linux/macOS users on how to complete prerequisite steps, especially where PowerShell or Windows-only tools are referenced.
GitHub Create Pull Request
Communication Services Teams Phone Extensibility ...uickstarts/tpe/teams-phone-extensibility-quickstart.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias, primarily through exclusive use of PowerShell cmdlets and references to Windows-centric tools (e.g., Teams PowerShell, Azure PowerShell modules, Teams Admin Center). All administrative and provisioning examples are given using PowerShell commands, with no mention of Linux/macOS equivalents or cross-platform alternatives. The Azure CLI is referenced, but only in the context of installing PowerShell modules. There are no bash, shell, or Linux-native command examples, and no guidance for non-Windows users on how to perform these tasks.
Recommendations
  • Provide equivalent examples using Azure CLI and Microsoft Graph API for provisioning and managing Teams Resource Accounts, as these are cross-platform.
  • Explicitly state platform requirements for PowerShell-based steps, and offer alternatives for Linux/macOS users (e.g., using Graph API, Azure CLI, or REST calls).
  • Include bash or shell script examples where possible, especially for steps that can be accomplished via REST or CLI.
  • Clarify which steps require Windows-only tools and suggest workarounds or alternative workflows for non-Windows environments.
  • Add a section or callout for Linux/macOS users, describing how to complete key tasks without relying on Windows tools.
GitHub Create Pull Request
Communication Services Quickstart - Make a call to Teams user from an iOS app ...ce-video-calling/includes/teams-user/teams-user-ios.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias in the prerequisites section, where enabling Teams Phone features for users is described only via a PowerShell-based process, with no mention of Linux/macOS-compatible alternatives. The Teams deployment link also points to a Windows-centric installation guide. However, the remainder of the quickstart is focused on iOS development and does not reference Windows-specific tools or workflows.
Recommendations
  • Provide Linux/macOS-compatible instructions for enabling Teams Phone features, or clarify if these steps can only be performed on Windows.
  • Include links to cross-platform or web-based administration tools (e.g., Microsoft 365 Admin Center) for managing Teams users and licenses.
  • Explicitly state platform requirements for administrative steps, so Linux/macOS users are aware of any limitations.
  • If PowerShell is required, suggest alternatives such as running PowerShell Core on Linux/macOS, or using remote administration.
GitHub Create Pull Request
Communication Services References - How to collect diagnostic audio recordings ...ferences/how-to-collect-diagnostic-audio-recordings.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively providing build instructions for the unpack_aecdump tool using Windows-specific prerequisites (Visual Studio 2022, Windows depot_tools instructions) and referencing the output as a Windows executable (.exe). No Linux or macOS build instructions, prerequisites, or usage examples are provided, which may hinder non-Windows users from completing the task.
Recommendations
  • Add Linux/macOS build instructions for unpack_aecdump, including required packages and toolchains (e.g., GCC/Clang, Python, depot_tools setup for Unix).
  • Reference the output binary as platform-agnostic (e.g., unpack_aecdump or unpack_aecdump.exe/unpack_aecdump depending on OS).
  • Include example commands for running unpack_aecdump on Linux/macOS.
  • Mention any platform-specific caveats or dependencies for non-Windows users.
  • Reorder or parallelize instructions so that Windows and Linux/macOS users see relevant information simultaneously.
GitHub Create Pull Request
Communication Services Detect sensitive data using Azure AI ...ion-services/samples/email-detect-sensitive-content.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools and patterns first (e.g., 'cmd', 'PowerShell', registry queries), and omits Linux/macOS equivalents for key setup steps. The initial prerequisite check uses a Windows registry command to verify .NET installation, with no mention of how to perform this check on Linux or macOS. Console examples list Windows shells before Bash, and all code samples are in C#/.NET, which is cross-platform but the setup instructions assume a Windows environment.
Recommendations
  • Provide Linux/macOS equivalents for .NET installation checks (e.g., 'dotnet --info' or package manager commands).
  • List Bash or Linux/macOS terminal options alongside or before Windows shells when referencing console windows.
  • Include notes or examples for Linux/macOS users in all setup and environment variable instructions.
  • Clarify that the C#/.NET code is cross-platform and provide links or brief instructions for running on Linux/macOS.
  • Avoid Windows registry commands unless alternatives are given for other platforms.
GitHub Create Pull Request
Communication Services Automate email resource management ...nication-services/samples/email-resource-management.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by prioritizing PowerShell examples and commands, which are native to Windows. The clean-up instructions provide PowerShell commands for deleting Email Communication Services and Domain resources, but do not offer equivalent Azure CLI or bash examples for Linux/macOS users. The structure and ordering also place PowerShell and Windows-centric tooling before cross-platform alternatives.
Recommendations
  • Provide Azure CLI or bash equivalents for all resource deletion commands currently shown only in PowerShell.
  • Ensure that Linux/macOS-friendly instructions are included and clearly labeled alongside Windows/PowerShell examples.
  • Consider reordering examples so that cross-platform tools (Azure CLI, Python) are presented first or in parallel with PowerShell.
  • Explicitly state platform compatibility for each command or script.
GitHub Create Pull Request
Communication Services include file ...ludes/email-resource-management-azurecli-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell. All code samples are written in PowerShell syntax, and the workflow is presented as a PowerShell script. Prerequisite checks and installation links are Windows-centric, with no mention of Linux/macOS equivalents or Bash scripting. There are no examples or guidance for running these automation steps on Linux or macOS, despite Azure CLI being cross-platform.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users, especially for Azure CLI commands.
  • Include installation instructions and prerequisite checks for Azure CLI and Azure PowerShell on Linux and macOS.
  • Clarify which steps are PowerShell-specific and which can be run in any shell, and offer alternatives where possible.
  • Reorder or balance examples so that Linux/macOS workflows are presented alongside or before Windows/PowerShell ones.
  • Use generic Azure CLI examples where possible, since CLI is cross-platform.
GitHub Create Pull Request
Communication Services Include file ...es/samples/includes/call-automation-azure-openai-js.md
Medium 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 frequently references Windows-specific tools and workflows, such as PowerShell and Windows terminal, and lists them before mentioning generic or Linux/macOS equivalents. The instructions for running commands and opening terminals are Windows-centric, with no explicit Linux/macOS examples or terminal references.
Recommendations
  • Explicitly mention Linux/macOS terminal usage alongside PowerShell and Windows terminal.
  • Provide example commands for bash/zsh where relevant, especially for steps like opening the terminal and running npm scripts.
  • Clarify that all commands (git, npm, devtunnel) work in Linux/macOS terminals and provide any necessary platform-specific notes.
  • Add screenshots or terminal prompts for Linux/macOS users to improve parity.
  • Avoid listing Windows tools first; use neutral language like 'Open a terminal (PowerShell, Command Prompt, Terminal, etc.)'.
GitHub Create Pull Request
Communication Services include file ...mples/includes/email-resource-management-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets and syntax. The prerequisite check and installation instructions reference PowerShell and Windows-specific guidance, with no mention of Bash, Azure CLI, or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the documentation implicitly assumes the user is running Windows or PowerShell Core.
Recommendations
  • Provide equivalent Azure CLI examples for all major steps (resource creation, DNS management, domain verification, linking).
  • Clarify that Azure PowerShell can run on Linux/macOS via PowerShell Core, and provide installation instructions for those platforms.
  • Include a section comparing PowerShell and Azure CLI, helping users choose the best tool for their OS.
  • Add explicit Bash/Azure CLI scripts for Linux/macOS users, or at least note how to adapt the PowerShell scripts for cross-platform use.
  • Update prerequisite checks to include Linux/macOS environments and instructions for verifying PowerShell Core or Azure CLI installation.
GitHub Create Pull Request
Communication Services Tutorial - Prepare a web app for Azure Communication Services (Node.js) ...communication-services/tutorials/building-app-start.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas: installation instructions for Node.js, nvm, and npm are Windows-specific and link only to Windows setup guides; PowerShell commands are provided for nvm usage without any equivalent bash/zsh instructions for Linux/macOS; file path examples use Windows conventions; and screenshots and workflow descriptions assume Windows environments. There are no explicit instructions or examples for Linux or macOS users, which may cause confusion or friction for those on non-Windows platforms.
Recommendations
  • Provide parallel instructions and examples for Linux and macOS, including links to official Node.js/nvm/npm setup guides for those platforms.
  • Include bash/zsh command examples for nvm usage alongside PowerShell commands.
  • Use platform-agnostic or dual file path examples (e.g., C:\... and ~/...) where appropriate.
  • Add notes or callouts clarifying any platform-specific steps, and ensure screenshots or UI references are relevant for all supported platforms.
  • Explicitly state that the tutorial is cross-platform and provide troubleshooting tips for common Linux/macOS issues.
GitHub Create Pull Request
← Previous Page 17 of 27 Next →