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 51-75 of 656 flagged pages
Communication Services Set up and create access tokens for Teams users ...nication-services/quickstarts/manage-teams-identity.md
High 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 bias towards Windows environments, particularly in the administrator troubleshooting section. PowerShell is exclusively used for command-line examples, with no mention of Linux or cross-platform alternatives. Instructions for installing and using the Microsoft Graph module are Windows/PowerShell-centric, and there are no Bash, Azure CLI, or Linux-native equivalents provided. The troubleshooting steps and tooling references assume a Windows environment, which may hinder Linux users or those on other platforms.
Recommendations
  • Provide equivalent command-line instructions using Azure CLI and/or Bash for Linux/macOS users.
  • Mention cross-platform alternatives to PowerShell, such as running commands in Bash or using REST APIs directly.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and offer guidance for non-Windows environments.
  • Include links or references to documentation for Linux/macOS setup of required tools (e.g., Microsoft Graph CLI, Azure CLI).
  • Ensure that all code samples and troubleshooting steps have Linux/macOS parity, or explicitly state platform requirements.
GitHub Create Pull Request
Communication Services References - How to collect verbose log from browsers ...lling/references/how-to-collect-browser-verbose-log.md
High 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 exclusively provides instructions and examples for collecting verbose logs from browsers on Windows, using Windows file paths, command syntax, and tools. There are no Linux or macOS equivalents, nor any mention of how to perform the same task on those platforms.
Recommendations
  • Add Linux/macOS instructions for launching Edge/Chrome with verbose logging, including example command lines using typical executable paths (e.g., /usr/bin/google-chrome).
  • Specify where logs are saved on Linux/macOS and how to locate them.
  • Mention any platform-specific differences in command-line arguments or log file locations.
  • Present examples for all major platforms, or clearly indicate platform-specific instructions.
GitHub Create Pull Request
Communication Services Plan user experience for virtual appointments ...oncepts/interop/virtual-visits/plan-user-experience.md
High Priority View Details →
Scanned: 2026-01-11 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 by referencing the Teams Admin Center and PowerShell as the primary methods for configuration, without mentioning Linux-compatible alternatives or command-line tools. No Linux-specific examples or cross-platform guidance are provided for managing Teams or Azure Communication Services settings.
Recommendations
  • Include Linux-compatible methods for Teams configuration, such as using Microsoft Graph API or web-based admin portals.
  • Provide examples of managing Teams settings via cross-platform tools (e.g., bash scripts, REST API calls) alongside PowerShell.
  • Explicitly mention platform compatibility for all administrative tools and clarify which options are available on Linux and macOS.
  • Add guidance for developers and administrators working in Linux environments, ensuring parity in instructions and tooling.
GitHub Create Pull Request
Communication Services Enable interoperability with Teams ...ices/concepts/interop/enable-interoperability-teams.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively referencing PowerShell cmdlets (Set-CsPhoneNumberAssignment) for configuration, and by mentioning Windows-centric tools and patterns without providing equivalent Linux or cross-platform alternatives. There are no examples or instructions for performing these tasks on Linux or macOS systems, nor is there guidance for using platform-agnostic methods (such as REST APIs or Azure CLI).
Recommendations
  • Provide equivalent instructions using Azure CLI or REST API, which are cross-platform.
  • Include Linux/macOS shell examples for relevant configuration steps.
  • Mention PowerShell as one option, but present platform-agnostic methods first or alongside.
  • Clarify whether the configuration steps can be performed from non-Windows environments, and provide guidance if so.
  • Add a note about prerequisites or platform requirements for each method.
GitHub Create Pull Request
Communication Services Enable interoperability in your Teams tenant ...s/includes/enable-interoperability-for-teams-tenant.md
High Priority View Details →
Scanned: 2026-01-11 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 exclusively uses PowerShell commands and Windows-centric tooling (MicrosoftTeams PowerShell module) for enabling interoperability in Teams. There are no references to Linux or cross-platform alternatives, nor guidance for users on non-Windows systems. The instructions assume access to PowerShell and administrative privileges, which are typically associated with Windows environments.
Recommendations
  • Provide equivalent instructions for Linux and macOS users, such as using PowerShell Core (pwsh) on those platforms.
  • Clarify whether the MicrosoftTeams PowerShell module is supported on PowerShell Core and, if so, provide installation and usage steps for non-Windows systems.
  • Mention prerequisites for non-Windows environments (e.g., installing PowerShell Core, module compatibility).
  • If GUI or web-based alternatives exist for these administrative tasks, reference them as cross-platform options.
  • Explicitly state OS requirements and offer troubleshooting tips for users on Linux/macOS.
GitHub Create Pull Request
Communication Services Security for communication as Teams external user ...munication-services/concepts/interop/guest/security.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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-centric tools and administration patterns, such as PowerShell and the Microsoft Teams admin center, as the primary means of managing security and external user policies. There are no mentions of Linux equivalents, cross-platform CLI tools, or guidance for non-Windows environments. The documentation assumes familiarity with Windows administration paradigms and omits examples or instructions for Linux or macOS users.
Recommendations
  • Include examples and instructions for managing Teams and Azure Communication Services security from Linux and macOS environments, such as using cross-platform CLI tools (e.g., Azure CLI, Microsoft Graph API).
  • Provide parity in administrative guidance by referencing cross-platform management options before or alongside Windows-specific tools like PowerShell.
  • Explicitly mention platform compatibility for all tools and interfaces, and link to documentation for Linux/macOS usage where available.
  • Add examples of configuring security policies using REST APIs or other platform-agnostic methods.
  • Review and update documentation to ensure that Windows-specific tools are not presented as the only or primary option, and that Linux users are not excluded from administrative scenarios.
GitHub Create Pull Request
Communication Services Calling capabilities for Teams users ...cation-services/concepts/interop/teams-user-calling.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 primarily through its platform support table, which lists 'Windows' as a distinct platform but omits Linux desktop support entirely. There are no Linux-specific examples, tools, or mentions, and the only desktop OS referenced is Windows. Additionally, links to Microsoft Entra and Graph API reference PowerShell modules, further reinforcing a Windows-centric approach. The absence of Linux desktop parity in feature tables and lack of Linux tooling or examples suggests the documentation is tailored for Windows environments.
Recommendations
  • Add explicit Linux desktop support information to the platform and feature tables, clarifying which features are available on Linux.
  • Include Linux-specific examples and usage patterns, such as command-line or shell instructions, alongside or before Windows/Powershell examples.
  • Reference Linux tools and APIs where appropriate, such as dbus, ALSA/PulseAudio for device management, or provide guidance for integrating with Linux desktop environments.
  • Clarify any limitations or workarounds for Linux users, and provide troubleshooting steps or links to Linux-specific documentation.
  • Ensure parity in documentation structure, so Linux users are not left out of platform support or integration guidance.
GitHub Create Pull Request
Communication Services Teams Phone extensibility FAQ .../concepts/interop/tpe/teams-phone-extensibility-faq.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and administrative patterns. Specifically, configuration of emergency calling policies is described as being performed in the Teams Admin Center (a web portal) or with PowerShell cmdlets, with no mention of Linux-compatible alternatives. There are no examples or guidance for Linux-based administration, nor are cross-platform command-line tools or REST API options discussed. Windows tools and patterns are mentioned exclusively and before any Linux equivalents (which are absent).
Recommendations
  • Provide Linux-compatible examples for administrative tasks, such as using Microsoft Graph API or Azure CLI for policy configuration.
  • Explicitly mention whether PowerShell cmdlets can be run on Linux (via PowerShell Core), and provide relevant examples if so.
  • Include cross-platform alternatives for Teams administration, such as REST API calls or scripts that work on both Windows and Linux.
  • Add documentation links or sections for Linux users, clarifying how to perform key tasks without relying on Windows-only tools.
  • Ensure that examples and instructions do not assume the use of Windows unless strictly necessary, and offer parity for Linux environments.
GitHub Create Pull Request
Communication Services Teams Phone extensibility Troubleshooting ...terop/tpe/teams-phone-extensibility-troubleshooting.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias, especially in the troubleshooting steps for Microsoft Entra App permission issues. All command-line instructions use PowerShell and Microsoft Graph PowerShell modules, with no mention of Linux or cross-platform alternatives. The guidance assumes the use of Windows tools and patterns, such as starting PowerShell as administrator and installing PowerShell modules, without providing equivalent instructions for Linux or macOS environments. There are no bash, Azure CLI, or REST API examples, and Windows-centric steps are presented first and exclusively.
Recommendations
  • Provide equivalent troubleshooting steps using Azure CLI, bash, or REST API for Linux/macOS users.
  • Include cross-platform instructions for connecting to Microsoft Entra ID and creating service principals.
  • Explicitly state platform requirements for each example and offer alternatives where possible.
  • Add notes or links to Microsoft Graph API documentation for users who prefer scripting outside PowerShell.
  • Ensure all administrative steps (such as license assignment) are described in a platform-neutral way, or provide parallel instructions for Linux/macOS.
GitHub Create Pull Request
Communication Services Teams controls for Teams external user ...ervices/concepts/interop/guest/teams-administration.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively referencing PowerShell modules and cmdlets for configuration and policy management, mentioning the Teams Admin Center (a web tool but often Windows-centric in enterprise use), and omitting any Linux or cross-platform CLI alternatives. No examples or guidance are provided for Linux administrators or those using non-Windows environments to manage Teams settings, and all technical links point to Windows-based tooling first and exclusively.
Recommendations
  • Include equivalent instructions for managing Teams policies and configurations using cross-platform tools, such as Azure CLI, Microsoft Graph API, or REST API, which can be used from Linux and macOS.
  • Explicitly mention platform requirements for PowerShell and Teams Admin Center, and provide guidance for Linux users (e.g., using PowerShell Core on Linux, or web-based admin tools).
  • Add examples and links for Linux-compatible management approaches, such as installing PowerShell Core on Linux, or using Graph API scripts in bash or Python.
  • Where possible, present cross-platform or web-based solutions before or alongside Windows-specific tools, to avoid implying Windows is the default or only supported platform.
GitHub Create Pull Request
Communication Services Microsoft Teams shared line appearance ...pts/interop/teams-user/teams-shared-line-appearance.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by referencing Teams PowerShell and Microsoft Teams Client (both Windows-centric tools) for delegate assignment, without mentioning Linux equivalents or alternatives. There are no examples or instructions for Linux users, and Windows tools are presented as the default or only option.
Recommendations
  • Include instructions or examples for assigning delegates using cross-platform tools (e.g., via Graph API, if available) or clarify platform limitations.
  • Explicitly mention whether Linux and macOS users can perform delegate assignment, and provide guidance if possible.
  • If PowerShell is required, note its availability on Linux and macOS, and provide installation and usage instructions for those platforms.
  • Add a section comparing platform-specific capabilities and limitations, ensuring Linux users are informed about what is and isn't possible.
  • Consider referencing web-based or REST API alternatives where available, to improve accessibility for non-Windows users.
GitHub Create Pull Request
Communication Services Teams Phone extensibility overview ...epts/interop/tpe/teams-phone-extensibility-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-centric tools and patterns, such as PowerShell cmdlets and the TAC (Teams Admin Center) portal, for administrative tasks like assigning emergency calling policies. There are no Linux or cross-platform alternatives mentioned for these operations, nor are there examples for Linux-based administration. The documentation assumes the use of Microsoft 365 identity and Teams client, which are primarily Windows-focused, and omits guidance for Linux environments or CLI tools that could be used on non-Windows platforms.
Recommendations
  • Include Linux and cross-platform alternatives for administrative tasks, such as using Microsoft Graph API or Azure CLI, with example commands.
  • Provide explicit examples for provisioning and policy assignment using tools available on Linux/macOS, not just PowerShell or TAC.
  • Clarify which features and SDKs are usable from Linux environments, and provide guidance for developers/admins working outside Windows.
  • Add a section or notes highlighting cross-platform compatibility and any limitations for non-Windows users.
  • Where PowerShell is referenced, also provide equivalent REST API or CLI instructions.
GitHub Create Pull Request
Communication Services Pricing for Teams interop scenarios ...ion-services/concepts/pricing/teams-interop-pricing.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (e.g., PowerShell cmdlet Set-CsPhoneNumberAssignment) for administrative tasks, mentioning the Teams Desktop client (implicitly Windows) before other platforms, and providing no Linux-specific examples or administrative guidance. There is an absence of Linux command-line or management alternatives, and the examples and scenarios focus on Windows clients and tools.
Recommendations
  • Provide Linux equivalents for administrative tasks, such as using Azure CLI, REST API, or cross-platform scripting for license assignment and configuration.
  • Include examples and scenarios featuring Teams clients on Linux (e.g., Teams web client on Ubuntu/Chrome, or Electron-based desktop client on Linux).
  • Mention cross-platform tools and workflows before or alongside Windows-specific ones, ensuring parity in documentation structure.
  • Reference platform-neutral management options (e.g., Graph API, Azure Portal) where possible, and clarify when a tool is Windows-only.
  • Add explicit notes or tables indicating platform support for Teams clients and administrative tools.
GitHub Create Pull Request
Communication Services Azure Communication Services Call Automation how-to for adding Microsoft Teams User into an existing call ...w-tos/call-automation/teams-interop-call-automation.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a Windows bias primarily in the authorization step, where only PowerShell cmdlets (Set-CsTeamsAcsFederationConfiguration, Set-CsExternalAccessPolicy) are referenced for tenant and user policy configuration. These are Windows-centric tools, with no mention of Linux-compatible alternatives or cross-platform approaches (e.g., Azure CLI, REST API). The initial configuration steps assume access to Microsoft Teams PowerShell and Skype for Business PowerShell modules, which are not natively available on Linux. The rest of the guide is programming-language agnostic and does not show OS bias, but the critical setup phase is Windows-centric.
Recommendations
  • Provide Linux-compatible alternatives for tenant and user policy configuration, such as Azure CLI commands or REST API equivalents if available.
  • Explicitly mention whether the PowerShell cmdlets can be run in Azure Cloud Shell (which is cross-platform) or provide instructions for using remote management from non-Windows environments.
  • Add a note or section for Linux/macOS users on how to perform the authorization steps, including any prerequisites or limitations.
  • Where possible, link to documentation for cross-platform tools and clarify OS requirements for administrative tasks.
  • Consider reordering or parallelizing instructions so that Windows and Linux approaches are presented side-by-side, rather than Windows-first.
GitHub Create Pull Request
Communication Services Tutorial - Integrate Microsoft Teams breakout rooms ...nication-services/how-tos/calling-sdk/breakoutrooms.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias primarily through references to Windows-specific tools and patterns. The prerequisite for setting Teams meeting policy links directly to a PowerShell module, which is a Windows-centric tool, without mentioning or providing Linux/macOS alternatives. There are no examples or guidance for managing Teams policies from non-Windows platforms, nor is there mention of cross-platform CLI tools or REST API alternatives. The SDK support table lists 'Windows' as a platform, but does not clarify Linux support or provide parity information.
Recommendations
  • Include instructions or references for managing Teams meeting policies using cross-platform tools, such as Microsoft Graph API or Azure CLI, which work on Linux and macOS.
  • Provide explicit examples for Linux/macOS users where administrative actions are required (e.g., setting policies, managing breakout rooms).
  • Clarify SDK/platform support for Linux in the support tables, and add Linux-specific guidance if available.
  • Avoid linking exclusively to PowerShell documentation; instead, offer alternatives or mention that PowerShell Core is available cross-platform.
  • Add a note or section addressing platform differences and how Linux users can achieve the same outcomes.
GitHub Create Pull Request
Communication Services Prerequisites ...des/create-azure-managed-domain-resource-powershell.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module, which is primarily associated with Windows environments. There are no examples or instructions for Linux users, such as using Azure CLI or Bash. The documentation assumes familiarity with Windows tools and patterns, and does not mention cross-platform alternatives or provide parity for Linux/macOS users.
Recommendations
  • Provide equivalent Azure CLI examples for all operations (login, module installation, resource creation, management, and deletion).
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or clarify platform compatibility.
  • Include Bash script examples where appropriate.
  • Add a section outlining cross-platform options and recommend tools for Linux/macOS users.
  • Ensure that links to resource management and tagging documentation include CLI and REST API options, not just PowerShell.
GitHub Create Pull Request
Communication Services Send email with SMTP and XOAuth2 using .NET ...kstarts/email/send-email-smtp/send-email-smtp-oauth.md
High Priority View Details →
Scanned: 2026-01-11 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 bias towards Windows environments. It references Windows-specific tools (cmd, PowerShell) before mentioning Bash, and does not provide any Linux/macOS-specific instructions or troubleshooting. All terminal commands are generic, but the examples and instructions implicitly prioritize Windows usage patterns. There are no Linux-specific package installation or environment setup instructions, nor any mention of platform differences in .NET or MailKit usage.
Recommendations
  • Explicitly mention Linux/macOS environments alongside Windows in all terminal instructions.
  • Provide Linux/macOS-specific setup steps, such as package installation commands (e.g., using apt, yum, or Homebrew for .NET).
  • Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, SSL certificates, firewall settings).
  • List Bash first or equally with cmd/PowerShell when referencing console windows.
  • Add a note about cross-platform compatibility of MailKit and .NET, and link to platform-specific documentation where relevant.
GitHub Create Pull Request
Communication Services include file ...send-email-smtp/includes/send-email-smtp-powershell.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides instructions and examples using PowerShell and the Send-MailMessage cmdlet, which are native to Windows. There are no Linux or cross-platform alternatives mentioned, such as using 'sendmail', 'mailx', 'mutt', or Python scripts. The focus on PowerShell and Windows tools may hinder Linux users from following the guide.
Recommendations
  • Add equivalent instructions and examples for Linux users, such as using 'sendmail', 'mailx', or Python's smtplib.
  • Mention cross-platform tools and approaches before or alongside Windows-specific ones.
  • Provide guidance on storing credentials securely on Linux systems.
  • Clarify which steps are OS-specific and offer alternatives for non-Windows environments.
GitHub Create Pull Request
Communication Services Register the Event Grid resource provider ...starts/events/includes/register-provider-powershell.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation exclusively provides PowerShell commands for registering the Event Grid resource provider, which are primarily used on Windows. There are no examples for Linux users (e.g., Azure CLI or Bash), and Windows tooling is implicitly prioritized. This creates a bias towards Windows users and may hinder Linux users from following the instructions easily.
Recommendations
  • Add equivalent Azure CLI commands for registering and checking the Event Grid resource provider status, which work cross-platform (Linux, macOS, Windows).
  • Explicitly mention that PowerShell is Windows-centric and provide guidance for Linux/macOS users.
  • Consider listing Azure CLI examples before or alongside PowerShell to avoid implicit prioritization of Windows tools.
  • Include a note or table comparing PowerShell and CLI usage for this task.
GitHub Create Pull Request
Communication Services Include file ...es/samples/includes/call-automation-azure-openai-js.md
High Priority View Details →
Scanned: 2026-01-11 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 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 terminal commands or tools mentioned. The instructions assume familiarity with Windows environments and do not provide parity for Linux users.
Recommendations
  • Explicitly mention Linux/macOS terminals (e.g., Bash, Terminal.app) alongside Windows options.
  • Provide example commands for Linux/macOS environments where relevant.
  • Avoid referencing PowerShell or Windows terminal first; use neutral language such as 'Open a terminal window.'
  • If any commands differ between platforms, include both sets of instructions.
  • Add a note clarifying that the instructions apply to all major operating systems, and link to platform-specific setup guides if available.
GitHub Create Pull Request
Communication Services Tutorial - Teams Shared Line Appearance ...ices/how-tos/cte-calling-sdk/shared-line-appearance.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates Windows bias by referencing Teams PowerShell and Microsoft Teams Client (both Windows-centric tools) as the primary methods for assigning delegates. No Linux or cross-platform alternatives are mentioned for these administrative tasks. The prerequisites and instructions focus on Windows tools and do not provide equivalent guidance for Linux users, nor do they mention Linux-compatible methods or examples.
Recommendations
  • Include instructions or examples for assigning delegates using cross-platform tools, such as Microsoft Graph API, which can be used from Linux.
  • Explicitly mention whether Teams PowerShell is available and supported on Linux, and provide installation/usage steps if so.
  • Add Linux-specific guidance or alternatives for administrative tasks currently described with Windows tools.
  • Ensure that future documentation provides parity in examples and tool references for both Windows and Linux users.
GitHub Create Pull Request
Communication Services Create a Communication Services resource in Azure Communication Services ...-services/quickstarts/create-communication-resource.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and patterns (PowerShell, app.config/web.config, setx) are mentioned first or exclusively in several places. The environment variable section lists Windows first, and the CLI installation link defaults to Windows. There is heavy use of PowerShell/Windows-centric examples, while Linux/macOS equivalents are present but less emphasized or appear after Windows instructions. Some configuration file examples (app.config/web.config) are Windows/.NET-centric, with no mention of Linux-native config patterns.
Recommendations
  • Present Linux/macOS examples before or alongside Windows examples, not after.
  • Provide links to Azure CLI installation for Linux/macOS in addition to Windows.
  • Include Linux-native configuration file examples (e.g., .env, systemd service files) alongside app.config/web.config.
  • Balance the use of PowerShell with Bash or other cross-platform shell examples.
  • Ensure all instructions and screenshots are platform-neutral or provide alternatives for each OS.
GitHub Create Pull Request
Communication Services include file ...tion-services/quickstarts/chat/includes/chat-csharp.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by listing Windows tools (Visual Studio) as a prerequisite without mentioning Linux alternatives, using PowerShell for package installation, and referencing Windows console environments (cmd, PowerShell) before Bash. There are no explicit Linux-specific instructions or examples, and the documentation does not mention cross-platform editors or package managers.
Recommendations
  • List cross-platform IDEs/editors (e.g., VS Code, JetBrains Rider) alongside Visual Studio in prerequisites.
  • Provide package installation commands using both PowerShell and Bash (e.g., 'dotnet add package ...' in both shells), or clarify that the command works in both environments.
  • Mention Bash and Linux terminal environments equally alongside Windows cmd/PowerShell when describing console usage.
  • Include notes or troubleshooting tips for running the sample on Linux/macOS, such as .NET SDK installation instructions for those platforms.
  • Ensure links to sample code or further documentation clarify cross-platform compatibility.
GitHub Create Pull Request
Communication Services Add a bot to your chat app ...uickstarts/chat/quickstart-botframework-integration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 strong Windows bias. All development and deployment instructions center around Visual Studio (Windows-only or Windows-first IDE), .NET Core, and C# examples. Package installation uses PowerShell syntax. There are no Linux-specific instructions, nor are alternative Linux tools or workflows (such as VS Code, CLI-only, or Linux deployment methods) mentioned. All screenshots and step-by-step guides assume use of the Azure Portal and Visual Studio on Windows, with no parity for Linux or cross-platform development environments.
Recommendations
  • Add instructions for developing and deploying bots using cross-platform tools such as VS Code, JetBrains Rider, or CLI-only workflows.
  • Include Linux-specific steps for installing .NET Core, running dotnet commands, and deploying to Azure (e.g., using Azure CLI or GitHub Actions).
  • Provide package installation examples using bash/zsh shell syntax (e.g., dotnet CLI in bash, not PowerShell).
  • Offer alternative examples in other languages supported by Azure Communication Services (e.g., JavaScript/Node.js, Python) to reduce C#/.NET exclusivity.
  • Include screenshots or terminal output from Linux environments to demonstrate parity.
  • Explicitly mention platform compatibility and provide troubleshooting tips for Linux/macOS users.
GitHub Create Pull Request
Communication Services Create and manage Email Communication Service resource in Azure Communication Services ...ickstarts/email/create-email-communication-resource.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents platform-specific instructions using a pivot system, but Windows-centric tools (PowerShell, .NET) are given equal prominence to cross-platform options (Azure CLI). There is a notable emphasis on Windows tools, with PowerShell and .NET examples included alongside Azure CLI, but no explicit mention of Linux-specific tools or shell environments (e.g., Bash). The ordering and inclusion of PowerShell and .NET may suggest a Windows-first approach, and there is no reference to Linux package managers or shell scripting.
Recommendations
  • Add explicit Bash or Linux shell examples where appropriate, especially for resource creation and management.
  • Clarify that Azure CLI instructions are cross-platform and can be run on Linux, macOS, and Windows.
  • Consider including Linux-specific notes or troubleshooting tips for common issues encountered on non-Windows platforms.
  • Review the ordering of platform pivots to ensure that cross-platform tools (e.g., Azure CLI) are presented before Windows-specific tools.
  • Mention installation and usage instructions for Azure CLI on Linux and macOS, not just Windows.
GitHub Create Pull Request
← Previous Page 3 of 27 Next →