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 201-225 of 656 flagged pages
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
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows-specific console environments (cmd, PowerShell) before Bash when describing how to create a new C# application. There are no explicit Linux or macOS-specific instructions or troubleshooting notes, and all examples use .NET and MailKit, which are cross-platform, but the terminal instructions and environment references are Windows-centric. There is no mention of Linux package managers, shell differences, or platform-specific considerations for Linux users.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms for .NET and MailKit.
  • Provide Linux/macOS-specific instructions, such as using Terminal, and reference common package managers (e.g., apt, yum, brew) for installing .NET.
  • List Bash/Terminal before or alongside cmd/PowerShell when describing console environments.
  • Add troubleshooting notes for Linux/macOS users (e.g., permissions, environment variables, SSL/TLS issues).
  • Include a note or section confirming that the instructions work on Linux/macOS and highlight any platform-specific caveats.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/events/includes/register-provider-powershell.md ...starts/events/includes/register-provider-powershell.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation exclusively provides PowerShell commands for registering the Event Grid resource provider, which are primarily used on Windows. There are no examples or instructions for performing the same task using cross-platform tools such as Azure CLI or Bash, nor is there mention of Linux or macOS workflows. This creates a Windows-centric bias and may hinder Linux users.
Recommendations
  • Add equivalent Azure CLI commands for registering and checking the Event Grid resource provider status.
  • Include Bash shell examples to demonstrate cross-platform compatibility.
  • Explicitly mention that PowerShell commands are for Windows, and provide guidance for Linux/macOS users.
  • Consider listing Azure CLI examples before or alongside PowerShell to avoid Windows-first bias.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/events/includes/create-event-subscription-powershell.md ...vents/includes/create-event-subscription-powershell.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell commands and Windows-centric tooling (e.g., PowerShell, Az modules) for all examples and instructions. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform scripting. The documentation implicitly assumes the user is on Windows or using PowerShell, which may alienate Linux and macOS users.
Recommendations
  • Provide equivalent Azure CLI (az) command examples for all operations (create, list, update, delete event subscriptions).
  • Explicitly mention that PowerShell commands can be run cross-platform, but also provide Bash or shell script examples where appropriate.
  • Add a 'Platform compatibility' note clarifying which tools are available on which OS, and link to installation instructions for Linux/macOS.
  • Reorganize sections so that cross-platform tools (e.g., Azure CLI) are presented before or alongside PowerShell examples.
  • Include troubleshooting or environment setup notes for Linux users, such as package dependencies or shell differences.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/includes/create-resource-powershell.md ...ces/quickstarts/includes/create-resource-powershell.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively uses PowerShell commands and examples, which are most commonly associated with Windows environments. There is no mention of Linux-specific tools, shell commands, or Azure CLI equivalents, and all instructions and code samples are presented in PowerShell syntax. This creates a bias towards Windows users and may hinder Linux users from following the documentation effectively.
Recommendations
  • Provide equivalent Azure CLI commands for all resource management steps, as Azure CLI is cross-platform and widely used on Linux.
  • Include instructions and examples for installing and using the Azure CLI on Linux and macOS.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell usage is required, and provide installation instructions.
  • Present both PowerShell and CLI examples side-by-side, or offer a toggle for users to select their preferred shell/environment.
  • Review links and referenced documentation to ensure Linux parity, such as linking to Linux-specific resource group management guides.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/microsoft-entra-id-authentication-integration.md ...ntity/microsoft-entra-id-authentication-integration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by referencing Windows-centric tools (Azure portal, Microsoft Entra admin center) and providing examples using Azure CLI and Microsoft Graph REST API without clarifying cross-platform compatibility. There are no explicit Linux-specific instructions, nor are Linux command-line or automation patterns (e.g., bash scripting) mentioned. The use of Azure CLI is cross-platform, but the documentation does not make this clear, and the portal-based steps assume a graphical interface typical of Windows environments. No Linux-specific examples or alternatives (such as shell scripts or Linux desktop tools) are provided.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide installation instructions for Linux users.
  • Include Linux-specific command-line examples, such as using curl for REST API calls, or bash scripts for automation.
  • Mention alternative access methods for users who may not have access to the Azure portal GUI, such as using Azure CLI or REST API for resource management and permission assignment.
  • Add notes or sections highlighting any differences or considerations for Linux users, such as authentication flows or environment setup.
  • Ensure parity in example ordering, presenting cross-platform or Linux alternatives alongside or before Windows/portal-based instructions.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/manage-teams-identity.md ...nication-services/quickstarts/manage-teams-identity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 bias toward Windows environments, particularly in the administrator troubleshooting section. PowerShell is exclusively used for command-line examples, and there is no mention of Linux or cross-platform alternatives (such as Bash, Azure CLI, or platform-neutral instructions) for managing service principals or installing required tools. The troubleshooting steps and installation instructions assume a Windows environment and do not provide guidance for Linux or macOS users.
Recommendations
  • Provide equivalent command-line instructions using Azure CLI, which is cross-platform, for service principal creation and management.
  • Include Bash or shell script examples for Linux/macOS users alongside PowerShell commands.
  • Mention installation steps for Microsoft Graph and other required packages on Linux/macOS, not just PowerShell/Windows.
  • Clarify which steps are platform-agnostic and which require OS-specific tooling, and provide alternatives where possible.
  • Add notes or links to official documentation for Linux/macOS users on how to perform Azure AD administrative tasks.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/phone-numbers-net.md ...es/quickstarts/telephony/includes/phone-numbers-net.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. It mentions Windows-specific terminals (cmd, PowerShell) before Bash, and does not provide any Linux-specific instructions or examples (such as shell commands for environment variable setup or package installation). All terminal commands are generic but assume familiarity with Windows environments. There are no explicit Linux or macOS examples, nor any mention of platform-specific differences or troubleshooting.
Recommendations
  • Explicitly mention Linux/macOS terminals (e.g., Bash, zsh) alongside Windows terminals in all relevant sections.
  • Provide Linux/macOS-specific instructions for setting environment variables (e.g., export AZURE_CLIENT_SECRET=...) and running commands.
  • Include troubleshooting notes for common cross-platform issues (e.g., file path differences, permissions).
  • Ensure parity in examples by showing both Windows (cmd/PowerShell) and Linux/macOS (Bash) syntax where relevant.
  • Reference installation methods for .NET Core on Linux/macOS (e.g., apt-get, brew) in the prerequisites.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-access-teams-phone.md ...ts/tpe/teams-phone-extensibility-access-teams-phone.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 referencing Windows-specific tools and workflows, such as the Microsoft 365 admin center and the MicrosoftTeams PowerShell module, without providing Linux equivalents or alternatives. The instructions for enabling Teams users and obtaining resource account IDs are tailored to Windows environments, and there are no examples or guidance for performing these steps on Linux or cross-platform tools. REST API and SDK usage is platform-neutral, but administrative setup steps are Windows-centric.
Recommendations
  • Add instructions for enabling Teams users using cross-platform tools (e.g., Microsoft Graph API, Azure CLI) instead of only referencing the Microsoft 365 admin center.
  • Provide Linux-friendly alternatives to PowerShell cmdlets, such as equivalent Graph API calls or Azure CLI commands, for obtaining resource account IDs.
  • Explicitly mention that administrative steps can be performed on any OS using browser-based portals or REST APIs, and link to platform-agnostic documentation where possible.
  • Include examples and guidance for performing all administrative and setup tasks from Linux or macOS environments, ensuring parity with Windows instructions.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-quickstart.md ...uickstarts/tpe/teams-phone-extensibility-quickstart.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias, particularly in administrative and provisioning steps. All command-line examples for Teams administration use PowerShell cmdlets and reference modules (e.g., MicrosoftTeamsPowerShell, Az.BotService) that are primarily Windows-centric. There are no Linux or cross-platform alternatives provided for these steps, and the use of Teams Admin Center and Microsoft 365 Admin Center further reinforces a Windows/GUI-first approach. The Azure CLI is mentioned, but only in the context of installing PowerShell modules. No bash, shell, or Linux-native instructions are given, and the documentation does not clarify whether these steps can be performed on Linux or macOS environments.
Recommendations
  • Provide equivalent Linux/macOS instructions for all PowerShell-based steps, using Azure CLI, Microsoft Graph API, or REST endpoints where possible.
  • Explicitly state OS requirements and cross-platform compatibility for administrative tools and modules.
  • Include bash or shell script examples alongside PowerShell for provisioning and resource management tasks.
  • Reference Linux-friendly tools (e.g., Azure CLI, Graph API) before or alongside Windows/PowerShell tools.
  • Clarify whether Teams Admin Center and Microsoft 365 Admin Center can be accessed from non-Windows platforms and provide guidance for Linux users.
  • Add notes or links to official documentation on using PowerShell Core on Linux/macOS if PowerShell is required.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-answer-teams-calls.md ...ts/tpe/teams-phone-extensibility-answer-teams-calls.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exhibits a Windows bias by providing only PowerShell commands for key setup steps (such as creating and associating Teams resource accounts), referencing Windows-centric tools (PowerShell, Set-CsOnlineApplicationInstance), and omitting equivalent Linux or cross-platform CLI instructions. The DevTunnel example also uses PowerShell syntax, and there is no mention of Bash, Azure CLI, or cross-platform alternatives. This may hinder Linux or macOS users from following the guide without additional research.
Recommendations
  • Provide equivalent Bash or Azure CLI commands for all PowerShell examples, especially for Teams resource account creation and association.
  • Clarify whether the PowerShell modules used are available on Linux/macOS, and if so, provide installation and usage instructions for those platforms.
  • When referencing tools like DevTunnel, specify if they are cross-platform and show command-line usage in both PowerShell and Bash.
  • Avoid assuming the user is on Windows; use neutral, cross-platform language and examples where possible.
  • Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-user/teams-user-ios.md ...ce-video-calling/includes/teams-user/teams-user-ios.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates Windows bias in the prerequisites section by referencing Teams deployment and user enablement steps that rely on Windows-centric tools and workflows, such as the Teams Phone license enablement via PowerShell and linking to Windows-focused deployment guides. No Linux alternatives or parity are mentioned for these administrative steps, and the documentation assumes the use of Windows tooling for Teams management.
Recommendations
  • Provide equivalent Linux or cross-platform instructions for Teams user enablement, such as using Microsoft Graph API or web-based admin portals.
  • Include links or examples for Teams deployment and user management that do not require Windows or PowerShell, highlighting any available REST APIs or platform-agnostic tools.
  • Explicitly state platform requirements for administrative steps and suggest alternatives for non-Windows environments.
  • Add a note clarifying that the iOS app development steps are platform-neutral, but administrative prerequisites may require Windows, and offer guidance for Linux users.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-teams-interop-group-calls.md ...video-calling/get-started-teams-interop-group-calls.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns, such as requiring Teams users to be 'Enterprise Voice enabled' via PowerShell, and linking to Teams deployment instructions that are Windows-centric. There are no Linux-specific instructions or examples for enabling Teams features, nor is there mention of Linux alternatives for administrative tasks. The page assumes familiarity with Windows tooling and does not provide parity for Linux administrators.
Recommendations
  • Provide Linux-compatible instructions for enabling Teams features, such as using Microsoft 365 admin center or cross-platform CLI tools where available.
  • Include explicit notes or examples for Linux users, especially for steps that currently reference PowerShell or Windows-only tools.
  • Reference cross-platform alternatives (e.g., Azure CLI, Microsoft Graph API, web portals) before or alongside Windows/PowerShell methods.
  • Clarify whether administrative steps (like enabling Enterprise Voice) can be performed via web UI or other non-Windows tools, and link to those instructions.
  • Audit all prerequisite and setup steps to ensure Linux users are not excluded or forced to use Windows tooling.
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
High Priority View Details →
Scanned: 2026-01-09 00:34
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 section, where enabling Teams Phone features for users is referenced via a link to a PowerShell-based guide, with no mention of Linux-compatible alternatives or cross-platform tools. The Teams deployment link also points to a Windows-centric installation guide. No Linux-specific instructions, examples, or parity notes are provided for these steps, and the documentation implicitly assumes a Windows environment for Teams administration.
Recommendations
  • Include Linux-compatible instructions or references for enabling Teams Phone features, such as using Microsoft 365 admin center web UI or any available cross-platform CLI tools.
  • Add notes clarifying whether the administrative steps (e.g., enabling Enterprise Voice) can be performed from non-Windows platforms, and provide links to relevant documentation if possible.
  • Where PowerShell is referenced, mention that PowerShell Core is available on Linux and macOS, and provide installation instructions or usage notes for those platforms.
  • Ensure that all setup steps (Teams deployment, user enablement) are platform-neutral or provide explicit Linux/macOS alternatives.
  • Consider adding a section or callout for Linux/macOS users outlining any differences or additional steps required.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/references/how-to-collect-browser-verbose-log.md ...lling/references/how-to-collect-browser-verbose-log.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides instructions and command-line examples for collecting verbose logs from browsers on Windows, using Windows file paths and tools. There are no examples or guidance for Linux or macOS users, and only Windows-specific executable paths are mentioned.
Recommendations
  • Add equivalent instructions and command-line examples for Linux (and optionally macOS), using appropriate browser executable paths and file locations.
  • Mention how to locate browser executables on Linux (e.g., /usr/bin/google-chrome or /usr/bin/microsoft-edge).
  • Specify the default log file locations for Linux and macOS.
  • Clarify any differences in command-line arguments or behavior between platforms.
  • Ensure that troubleshooting steps are presented for all major platforms, not just Windows.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-chat-csharp-tutorial.md ...torials/includes/twilio-to-acs-chat-csharp-tutorial.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by recommending Visual Studio as the required IDE, providing only PowerShell/dotnet CLI installation instructions, and omitting Linux-specific setup or tooling. There are no Linux or cross-platform alternatives mentioned for development environment setup, nor are there examples using Linux-native tools or shell commands. The Azure CLI example is cross-platform, but the overall setup and instructions assume a Windows-centric workflow.
Recommendations
  • Explicitly mention that Azure Communication Services SDKs and Azure CLI are cross-platform and can be used on Linux and macOS.
  • Provide installation instructions using bash/zsh for Linux/macOS users, e.g., 'dotnet add package' in a bash shell.
  • Suggest alternative IDEs such as VS Code or JetBrains Rider, which are available on Linux and macOS, instead of only Visual Studio.
  • Include notes or sections on setting up the development environment on Linux (e.g., installing .NET SDK, configuring environment variables).
  • Ensure that all command-line examples are presented in a way that is platform-agnostic or provide both Windows (PowerShell) and Linux/macOS (bash) variants.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/references/how-to-collect-diagnostic-audio-recordings.md ...ferences/how-to-collect-diagnostic-audio-recordings.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing build instructions and prerequisites exclusively for Windows (Visual Studio 2022, Windows-specific depot_tools instructions, .exe output), without mentioning or providing equivalent steps for Linux or macOS. There are no Linux or cross-platform examples for building or running the unpack_aecdump tool, and the documentation refers to Windows tools and patterns throughout.
Recommendations
  • Add build instructions for Linux and macOS, including required packages and dependencies (e.g., gcc/clang, Python, depot_tools setup for Unix-like systems).
  • Provide Linux/macOS command-line examples for building and running unpack_aecdump (e.g., outputting unpack_aecdump instead of unpack_aecdump.exe).
  • Reference cross-platform documentation for depot_tools and Chromium build environments.
  • Clarify which steps are platform-specific and which are universal, and present them in parallel or in a platform-neutral order.
  • Include troubleshooting notes for common issues on Linux/macOS (e.g., permissions, missing dependencies).
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/email-detect-sensitive-content.md ...ion-services/samples/email-detect-sensitive-content.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns first (e.g., 'cmd', 'PowerShell', registry queries), providing commands and instructions that are tailored to Windows environments, and omitting equivalent Linux examples for key steps such as checking .NET installation. The use of Windows registry queries and the lack of explicit Linux alternatives for environment setup and verification further reinforce this bias.
Recommendations
  • Provide Linux-specific instructions and examples alongside Windows ones, especially for prerequisite checks (e.g., use 'dotnet --list-sdks' or 'which dotnet' for .NET verification on Linux).
  • Avoid referencing Windows tools (such as registry queries) exclusively; offer cross-platform alternatives.
  • Explicitly mention and show examples for Bash and other Linux shells when discussing terminal commands.
  • Clarify that environment variable setup and usage may differ between Windows (cmd/PowerShell) and Linux (bash/zsh), and provide sample commands for both.
  • Ensure screenshots and navigation instructions in the Azure portal are not OS-specific unless necessary.
  • Where possible, use generic, cross-platform terminology (e.g., 'terminal' instead of 'command window') and provide parity in all code and setup examples.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-azure-openai-js.md ...es/samples/includes/call-automation-azure-openai-js.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation shows a Windows bias by referencing PowerShell, Windows terminal, and command prompt first and exclusively in instructions for running the sample. There are no explicit Linux or macOS terminal examples, nor are cross-platform shell commands or tools mentioned. The instructions assume familiarity with Windows-specific environments and do not provide parity for Linux users.
Recommendations
  • Explicitly mention Linux and macOS terminals (e.g., Bash, Terminal.app) alongside PowerShell and Windows terminal.
  • Provide example commands and instructions for Linux/macOS environments where appropriate.
  • Avoid using Windows-specific terminology first; use neutral, cross-platform language such as 'Open a terminal window' instead of 'Open PowerShell'.
  • Include any platform-specific caveats or steps for Linux/macOS users, such as different environment variable syntax or permissions.
  • Ensure all tools and steps (e.g., dev tunnels, npm install) are confirmed to work on Linux/macOS and document any differences.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/chat-hero-sample.md ...les/communication-services/samples/chat-hero-sample.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows-specific terminals (PowerShell, Windows Terminal, Command Prompt) first and exclusively in the instructions for opening a terminal. There are no explicit mentions or examples for Linux or macOS terminal usage, nor are there instructions tailored for those platforms. The page also refers to PowerShell and Windows tools before mentioning generic or cross-platform alternatives, and does not provide parity for Linux users in terms of setup or troubleshooting.
Recommendations
  • Explicitly mention Linux and macOS terminals (e.g., 'Open a terminal such as PowerShell, Windows Terminal, Command Prompt, Terminal (macOS), or a Linux shell').
  • Provide Linux/macOS-specific instructions or notes where relevant, such as file path conventions or environment setup.
  • Include troubleshooting tips for Linux/macOS users if there are known platform-specific issues.
  • Ensure that all CLI commands are cross-platform or provide platform-specific alternatives if needed.
  • Avoid listing Windows tools first or exclusively; use neutral language such as 'Open a terminal' and then list examples for all major platforms.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/email-resource-management.md ...nication-services/samples/email-resource-management.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by prioritizing PowerShell examples and commands, referencing Windows-centric tools, and omitting equivalent Linux/bash examples. The clean-up instructions provide PowerShell commands exclusively for deleting Email Communication Services and Domain resources, with no bash/Azure CLI alternatives shown for Linux users. The structure and included samples also suggest a preference for Windows/PowerShell workflows.
Recommendations
  • Add bash/Azure CLI examples for all resource management and clean-up steps, especially for deleting Email Communication Services and Domain resources.
  • Ensure that Linux-compatible commands are presented alongside or before PowerShell commands, to provide parity and avoid Windows-first bias.
  • Clearly indicate platform applicability for each example, and use zone pivots to separate Windows and Linux instructions.
  • Review included files (e.g., email-resource-management-powershell.md) to verify that Linux alternatives are present and equally detailed.
  • Consider adding a table or section comparing Windows and Linux workflows for common tasks, to help users choose the best approach for their environment.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/email-resource-management-azurecli-powershell.md ...ludes/email-resource-management-azurecli-powershell.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All code samples and automation instructions are written in PowerShell, which is natively a Windows shell and not the default on Linux systems. Prerequisite checks and installation links are Windows-centric, with explicit references to PowerShell and Windows installation tabs. There are no Bash or Linux shell examples, nor any mention of how to adapt the scripts for Linux or macOS environments, despite Azure CLI being cross-platform.
Recommendations
  • Provide equivalent Bash shell examples for all PowerShell scripts, especially for Azure CLI usage, variable initialization, and error handling.
  • Include Linux/macOS installation instructions and links for Azure CLI and PowerShell, not just Windows.
  • Clarify which commands are cross-platform (Azure CLI) and which are Windows-specific (PowerShell), and suggest alternatives for Linux users.
  • Add a section or callout explaining how to run the automation on Linux/macOS, including how to translate PowerShell constructs to Bash or other shells.
  • Consider using only Azure CLI commands in examples, or provide both PowerShell and Bash variants, to ensure parity and accessibility for all users.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/email-resource-management-powershell.md ...mples/includes/email-resource-management-powershell.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses Azure PowerShell for all automation and scripting examples, with no mention of cross-platform alternatives such as Azure CLI, Bash, or Linux shell scripting. The prerequisites and setup instructions reference PowerShell and Windows-centric command patterns (e.g., checking PowerShell installation via command prompt), and the only tool referenced for Azure resource management is Azure PowerShell. There are no Linux-specific instructions, nor is there any indication that the scripts or tools are cross-platform.
Recommendations
  • Add equivalent Azure CLI examples for all major steps (resource creation, domain management, DNS configuration, domain verification, and linking).
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, and provide installation instructions for those platforms.
  • Provide Bash or shell script samples where appropriate, especially for DNS record management and automation.
  • Include a section comparing Azure PowerShell and Azure CLI, guiding users on when to use each and how to adapt scripts for non-Windows environments.
  • Update prerequisite checks to include Linux/macOS instructions (e.g., how to check for PowerShell or Azure CLI on those platforms).
  • Clarify any platform-specific limitations or considerations for users running scripts on Linux/macOS.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/building-app-start.md ...communication-services/tutorials/building-app-start.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 providing Windows-specific setup instructions and PowerShell commands for installing Node.js, nvm, and npm, while omitting equivalent Linux/macOS instructions. The folder creation example uses a Windows path, and there is no mention of Linux tools or terminal commands. The documentation references Windows setup guides and does not provide parity for Linux users in key setup steps.
Recommendations
  • Include Linux/macOS setup instructions for Node.js, nvm, and npm, such as using bash/zsh shell commands and linking to official Linux/macOS guides.
  • Provide Linux/macOS examples for folder creation and workspace setup (e.g., using ~/ACS/CallingApp).
  • Add terminal command examples for Linux/macOS (e.g., using bash instead of PowerShell).
  • Reference cross-platform documentation for all tools, not just Windows-specific pages.
  • Ensure screenshots and file paths reflect both Windows and Linux/macOS environments where relevant.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-chat-android-tutorial.md ...orials/includes/twilio-to-acs-chat-android-tutorial.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias primarily through its prerequisites and setup instructions. It exclusively recommends Visual Studio (a Windows-centric IDE) and provides only PowerShell/dotnet CLI commands for package installation, without mentioning Linux alternatives or cross-platform editors. There are no references to Linux tools, editors, or shell environments, and no examples for Linux-specific workflows. The Azure CLI example is cross-platform, but the overall guidance and examples assume a Windows development environment.
Recommendations
  • Include instructions for installing the SDK using Linux/macOS shells (e.g., bash/zsh), and clarify that 'dotnet' CLI works cross-platform.
  • Mention cross-platform IDEs such as VS Code, JetBrains Rider, or command-line editors, and provide links to their installation guides.
  • Add explicit notes that all code samples and CLI commands work on Linux and macOS, not just Windows.
  • Provide examples of setting up the development environment on Linux (e.g., using apt-get/yum for .NET SDK installation).
  • Avoid recommending only Windows-specific tools (Visual Studio, PowerShell) in the prerequisites; offer alternatives or clarify cross-platform options.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/guest/teams-administration.md ...ervices/concepts/interop/guest/teams-administration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by consistently referencing PowerShell modules and cmdlets for configuration and policy management, listing 'Teams Admin Center or PowerShell' as the primary tools for administrators, and linking to documentation under /powershell/module/teams and /powershell/module/skype. There are no examples or mentions of equivalent Linux tools, CLI commands, or cross-platform alternatives. The documentation assumes the use of Windows-based administration tools and does not address how Linux administrators can perform these tasks.
Recommendations
  • Include examples using cross-platform Microsoft Teams CLI tools, if available, or Azure CLI where possible.
  • Explicitly mention whether PowerShell cmdlets can be used on Linux/macOS via PowerShell Core, and provide installation guidance for non-Windows platforms.
  • Add references to REST API or Graph API alternatives for configuration and policy management, with sample requests.
  • Clarify which administrative tasks require Windows-only tools and which can be performed from Linux or macOS.
  • Provide parity in examples and tool recommendations for Linux administrators, including any limitations or workarounds.
GitHub Create Pull Request
← Previous Page 9 of 27 Next →