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 226-250 of 656 flagged pages
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/teams-user/teams-shared-line-appearance.md ...pts/interop/teams-user/teams-shared-line-appearance.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 Windows bias by referencing Teams PowerShell for delegate assignment and mentioning the Microsoft Teams Client (which is primarily used on Windows). There are no Linux-specific instructions, examples, or tool mentions for managing shared line appearance. The prerequisites and guidance focus on Windows-centric tools and do not provide parity for Linux users.
Recommendations
  • Add instructions or examples for assigning delegates using cross-platform tools, such as the Teams web client or any available REST APIs.
  • Explicitly state whether delegate assignment can be performed on Linux or macOS, and provide guidance for those platforms if possible.
  • If PowerShell is required, mention PowerShell Core and its compatibility with Linux/macOS, or provide alternative methods for non-Windows users.
  • Include Linux-specific troubleshooting or usage notes where applicable.
  • Ensure that all platform support statements (e.g., SDK support) clarify Linux/macOS status, not just Windows.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/send-email-async-sync-net.md ...uickstarts/email/includes/send-email-async-sync-net.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (cmd, PowerShell) before mentioning Bash, and by providing only .NET/C# examples and commands. There are no explicit Linux or cross-platform shell examples (e.g., bash, zsh), nor are Linux-specific instructions or troubleshooting steps provided. All code samples and package installation instructions use the dotnet CLI, which is cross-platform, but the narrative and examples implicitly assume a Windows environment.
Recommendations
  • Explicitly mention that all dotnet CLI commands work on Linux and macOS, not just Windows.
  • Provide Linux/macOS-specific instructions for tasks such as environment variable setup, running commands in Bash/zsh, and file path conventions.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, dependency installation).
  • List Bash/zsh as the first example shell, or present all shell options equally (e.g., 'In a terminal (cmd, PowerShell, Bash, zsh)...').
  • Add links or notes for installing .NET Core on Linux/macOS, including package manager commands (apt, yum, brew, etc.).
  • Ensure sample code and instructions are tested and verified on Linux/macOS as well as Windows.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-smtp/includes/send-email-smtp-powershell.md ...send-email-smtp/includes/send-email-smtp-powershell.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 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', or Python scripts. The documentation assumes the user is on Windows and does not address how to perform the same task on Linux or macOS.
Recommendations
  • Add equivalent instructions and examples for Linux and macOS, such as using 'sendmail', 'mailx', or Python's smtplib.
  • Include cross-platform code samples (e.g., Python, Node.js) for sending email via SMTP.
  • Explicitly mention platform requirements and provide guidance for users on non-Windows systems.
  • List both Windows and Linux tools for storing credentials and sending emails, and present them in parallel sections.
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-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 bias toward Windows environments by providing only PowerShell-based instructions for administrative tasks, such as creating service principals and installing modules. There are no equivalent CLI or shell examples for Linux/macOS users. The troubleshooting and setup steps assume access to PowerShell and the Microsoft Graph PowerShell module, which are native to Windows and require extra steps or workarounds on other platforms. No mention is made of Azure CLI, Bash, or cross-platform alternatives, and Windows tooling is presented first and exclusively.
Recommendations
  • Provide equivalent instructions using Azure CLI or Microsoft Graph API via Bash/curl for Linux/macOS users.
  • Add cross-platform examples for administrative tasks, such as creating service principals and granting permissions.
  • Explicitly mention that PowerShell commands can be run on Linux/macOS (with installation steps), or offer alternatives.
  • Reorder examples or provide parallel instructions so that Windows and Linux/macOS users are equally supported.
  • Include troubleshooting steps for non-Windows environments, such as installing PowerShell Core or using REST APIs.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing Windows-specific setup instructions and PowerShell commands for installing Node.js, nvm, and npm, while omitting equivalent instructions for Linux or macOS. The workspace creation example uses a Windows file path, and there is no mention of Linux tools or terminal commands. The link for nvm/npm setup is Windows-specific, and no alternative is given for other platforms. The documentation does not provide parity for Linux/macOS users in the initial environment setup steps.
Recommendations
  • Add explicit instructions and examples for installing Node.js, nvm, and npm on Linux and macOS, including relevant shell commands.
  • Provide cross-platform file path examples (e.g., ~/ACS/CallingApp for Linux/macOS).
  • Include links to official nvm/npm setup guides for Linux and macOS.
  • When showing terminal commands, clarify which shell is being used (PowerShell, Bash, etc.) and provide alternatives.
  • Ensure screenshots and instructions for Visual Studio Code are platform-neutral or include platform-specific notes where behavior differs.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/includes/enable-interoperability-for-teams-tenant.md ...s/includes/enable-interoperability-for-teams-tenant.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 exclusively uses PowerShell commands and Windows-centric tooling (MicrosoftTeams PowerShell module) for enabling interoperability in Teams tenants. There are no examples or guidance for Linux or macOS users, nor are cross-platform alternatives (such as Azure CLI, Bash, or REST API) mentioned. The instructions assume the user is on Windows and using PowerShell, with no consideration for non-Windows environments.
Recommendations
  • Provide equivalent instructions for Linux and macOS users, including how to install and use the MicrosoftTeams module on those platforms if supported.
  • Mention and demonstrate cross-platform alternatives such as Azure CLI, Bash scripts, or REST API calls where possible.
  • Clarify platform requirements and note any limitations or prerequisites for non-Windows users.
  • Reorder or supplement examples so that Linux/macOS methods are presented alongside or before Windows-specific instructions.
  • Add troubleshooting tips for common issues encountered on Linux/macOS (e.g., module installation, authentication).
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/enable-interoperability-teams.md ...ices/concepts/interop/enable-interoperability-teams.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 exclusively referencing PowerShell cmdlets (Set-CsPhoneNumberAssignment) for configuration, which are Windows-centric tools. There are no examples or instructions for performing equivalent tasks on Linux or macOS, nor are cross-platform alternatives mentioned. The guidance assumes familiarity with Windows/PowerShell environments and does not address Linux users' needs.
Recommendations
  • Provide equivalent instructions using Azure CLI or REST API, which are cross-platform.
  • Include Linux/macOS-specific setup steps or examples where relevant.
  • Mention and link to cross-platform tools before or alongside Windows/PowerShell tools.
  • Clarify whether PowerShell cmdlets can be run on PowerShell Core (pwsh) on Linux/macOS, and provide guidance if so.
  • Add a section addressing interoperability setup from non-Windows environments.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/teams-user-calling.md ...cation-services/concepts/interop/teams-user-calling.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 listing 'Windows' as a primary supported platform alongside JavaScript, Android, and iOS, but does not mention Linux as a supported platform or provide any Linux-specific guidance. Additionally, references to Microsoft Entra and Microsoft Graph link to PowerShell modules, reinforcing a Windows-centric approach. There are no Linux desktop examples, tools, or explicit statements about Linux support or limitations.
Recommendations
  • Explicitly state Linux support status for the Calling SDK (e.g., whether Linux desktop is supported via Electron, Web, or not at all).
  • If Linux is supported (e.g., via web or Electron), add a 'Linux' column to the feature matrix and provide parity information.
  • Include Linux-specific instructions or examples where relevant, such as device management or screen sharing on Linux.
  • Reference cross-platform or Linux-native tools/APIs (not just PowerShell or Windows-specific modules) for authentication and integration.
  • If Linux is not supported, clearly state this in the documentation to avoid ambiguity.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-overview.md ...epts/interop/tpe/teams-phone-extensibility-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 a Windows bias primarily through its references to Teams administration and provisioning tasks being performed via the TAC portal and PowerShell cmdlets, with no mention of Linux equivalents or cross-platform alternatives. The only administrative tools mentioned are Windows-centric (PowerShell and TAC portal), and there are no examples or guidance for performing these tasks on Linux or macOS systems. The documentation also assumes familiarity with Windows-based workflows and does not provide parity for Linux administrators or developers.
Recommendations
  • Include instructions and examples for Teams administration using cross-platform tools, such as Microsoft Graph API, which can be used from Linux, macOS, and Windows.
  • Explicitly mention that PowerShell is available on Linux and macOS, and provide installation guidance for non-Windows platforms.
  • Provide CLI or REST API alternatives for tasks currently described as requiring PowerShell or TAC portal.
  • Add notes or sections highlighting platform-agnostic approaches to provisioning, policy assignment, and other administrative tasks.
  • Ensure that all code samples and administrative workflows are demonstrated using both Windows and Linux environments where possible.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/virtual-visits/plan-user-experience.md ...oncepts/interop/virtual-visits/plan-user-experience.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 and Teams Admin Center as the primary tools for configuration discovery, without mentioning Linux equivalents or cross-platform alternatives. No examples or guidance are provided for Linux users, and Windows-centric tools are mentioned first and exclusively.
Recommendations
  • Include instructions for accessing Teams configuration via cross-platform tools, such as Azure CLI or Microsoft Graph API, which are available on Linux.
  • Explicitly mention that PowerShell is available on Linux, or provide Linux-specific installation and usage notes.
  • Provide examples for configuration discovery and management using tools that work on both Windows and Linux (e.g., Graph API, Azure CLI).
  • Avoid listing Windows tools first; present cross-platform options equally or in parallel.
  • Add a section or note addressing Linux/macOS users and their options for Teams administration.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/guest/security.md ...munication-services/concepts/interop/guest/security.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 patterns, such as the Microsoft Teams admin center and PowerShell, as the primary means for administrators to manage external user policies. There are no mentions of Linux equivalents, cross-platform command-line tools, or alternative management options for non-Windows environments. The documentation assumes familiarity with Windows tools and does not provide guidance for Linux administrators.
Recommendations
  • Include examples or instructions for managing Teams external user policies using cross-platform tools or REST APIs, if available.
  • Explicitly mention whether PowerShell commands can be run on Linux/macOS using PowerShell Core, and provide relevant examples.
  • Reference Azure CLI or other platform-agnostic management tools where possible.
  • Add a section or note on how Linux administrators can perform equivalent tasks, or clarify if certain features are Windows-only.
  • Ensure parity in documentation by listing both Windows and Linux management options, or stating limitations clearly.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/pricing/teams-interop-pricing.md ...ion-services/concepts/pricing/teams-interop-pricing.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates Windows bias primarily through exclusive mention of Windows-specific tools and workflows, such as the Set-CsPhoneNumberAssignment PowerShell cmdlet for Teams Phone features. There are no Linux or cross-platform equivalents provided for administrative tasks, and example scenarios reference Windows environments (e.g., 'Windows, Chrome browser') before or instead of Linux. All client references are to Teams desktop, web, and mobile clients, which are available on multiple platforms, but administrative and setup instructions are Windows-centric.
Recommendations
  • Provide Linux and cross-platform alternatives for administrative tasks, such as using Microsoft Graph API or Azure CLI for license assignment and configuration.
  • Include examples or references for performing Teams Phone setup and management on Linux or macOS environments.
  • When mentioning client environments in scenarios, ensure parity by referencing Linux desktop clients or browser usage on Linux, not just Windows.
  • Document any limitations or differences for Linux users explicitly, and offer guidance for achieving equivalent functionality.
  • Where PowerShell is referenced, add equivalent commands or scripts using cross-platform tools (e.g., Azure CLI, REST API).
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-faq.md .../concepts/interop/tpe/teams-phone-extensibility-faq.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 Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through its exclusive mention of PowerShell cmdlets and the Teams Admin Center (TAC) portal for configuration tasks, without referencing Linux-compatible alternatives or cross-platform command-line tools. No Linux-specific examples, tools, or configuration patterns are provided, and Windows-centric administration methods are mentioned first and exclusively.
Recommendations
  • Include Linux-compatible configuration instructions, such as using Microsoft Graph API or cross-platform CLI tools, alongside PowerShell and TAC portal steps.
  • Provide examples of managing Teams Phone extensibility from Linux or macOS environments, highlighting any platform-agnostic approaches.
  • Explicitly mention whether PowerShell cmdlets can be run on Linux (via PowerShell Core), and provide guidance for installation and usage on non-Windows platforms.
  • Add references to cross-platform tools (e.g., Azure CLI, REST APIs) where applicable for administrative tasks.
  • Ensure that examples and instructions are presented in a platform-neutral order, or provide both Windows and Linux/macOS options side by side.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-troubleshooting.md ...terop/tpe/teams-phone-extensibility-troubleshooting.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 exhibits Windows bias, particularly in troubleshooting steps that require administrative actions. PowerShell is the only CLI tool referenced for Microsoft Entra service principal creation, with no mention of Linux/macOS alternatives (such as Azure CLI or cross-platform scripting). The instructions and examples assume a Windows environment, omitting guidance for users on Linux or macOS. This can hinder non-Windows users from following the troubleshooting steps effectively.
Recommendations
  • Provide equivalent Azure CLI commands for service principal creation and management, which work across Windows, Linux, and macOS.
  • Include notes or examples for Linux/macOS users, clarifying how to perform required actions without PowerShell.
  • Avoid assuming administrative tools (like PowerShell) are available; mention prerequisites or alternatives for non-Windows platforms.
  • Where possible, present cross-platform solutions first, or at least in parallel with Windows-specific instructions.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/teams-interop-call-automation.md ...w-tos/call-automation/teams-interop-call-automation.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 configuration, with no mention of Linux/macOS alternatives or cross-platform CLI options. The prerequisites and steps assume access to Windows-centric tools and administrative patterns. While the code samples are cross-platform, the administrative setup is Windows-first and PowerShell-heavy.
Recommendations
  • Include equivalent instructions for configuring Teams federation and external access using Microsoft Teams Admin Center (web UI), which is accessible from any OS.
  • Provide guidance for using Microsoft Graph API or Azure CLI for tenant-level and user-level configuration, if available, to support Linux/macOS users.
  • Explicitly state whether PowerShell cmdlets can be run on PowerShell Core on Linux/macOS, and provide installation instructions if so.
  • Add notes or links to cross-platform administrative tools and patterns where possible.
  • Review all prerequisite steps to ensure they do not assume a Windows environment, and clarify any platform-specific requirements.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/cte-calling-sdk/shared-line-appearance.md ...ices/how-tos/cte-calling-sdk/shared-line-appearance.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 Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Teams PowerShell and Microsoft Teams Client (Windows-centric tools) for delegate assignment, without mentioning or providing equivalent Linux/macOS methods or examples. The prerequisites list Teams PowerShell before any alternative, and no Linux-specific instructions or examples are given for managing shared line appearance. The SDK support table includes a Windows column but omits Linux/macOS, and the page lacks parity in cross-platform guidance.
Recommendations
  • Add instructions or examples for assigning delegates using Teams on Linux/macOS, if supported.
  • Clarify whether Teams PowerShell can be run on Linux/macOS (via PowerShell Core), and provide relevant guidance.
  • Include Linux/macOS in the SDK support table, or explicitly state platform limitations.
  • Provide parity in tooling recommendations, mentioning cross-platform alternatives where available.
  • Ensure that examples and instructions are not Windows-first, and offer equal visibility to Linux/macOS workflows.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/breakoutrooms.md ...nication-services/how-tos/calling-sdk/breakoutrooms.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows a Windows bias by referencing Windows-specific tools (PowerShell) for Teams meeting policy configuration, linking to PowerShell documentation before mentioning any cross-platform alternatives, and omitting Linux equivalents or examples for administrative tasks. There are no Linux-specific instructions or parity for managing Teams meeting policies or breakout rooms.
Recommendations
  • Provide equivalent instructions for configuring Teams meeting policies using cross-platform tools, such as Microsoft Graph API, which can be used from Linux/macOS.
  • Include examples or links for Linux/macOS users to manage Teams policies and breakout rooms, ensuring administrative steps are not Windows/PowerShell-exclusive.
  • Clearly indicate when a procedure is Windows-only and offer alternatives for other platforms where possible.
  • Add a section on managing breakout rooms using platform-agnostic methods (e.g., REST APIs, CLI tools) to improve parity.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/router-sdk/subscribe-events.md ...cation-services/how-tos/router-sdk/subscribe-events.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 primarily in the 'Quick-start: Receive Event Grid events via an Azure Storage Queue' section. It refers to 'cmd, PowerShell, or Bash' as possible console windows, listing Windows shells first and not providing any Linux-specific instructions or examples. All code samples and instructions are focused on .NET and C#, which are cross-platform, but there are no explicit Linux or macOS instructions, nor are Linux tools or patterns mentioned. There are no Linux-specific troubleshooting notes, nor are Linux command-line patterns (such as shell scripts or environment variable usage) shown.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms in prerequisites and instructions.
  • Provide Linux/macOS-specific instructions for running the sample (e.g., using Terminal, setting environment variables, installing .NET SDK on Linux).
  • Include Linux shell script equivalents or usage examples where appropriate.
  • List Bash (or Terminal) before Windows shells when enumerating console options, or mention all platforms equally.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, dependency installation).
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/chat/quickstart-botframework-integration.md ...uickstarts/chat/quickstart-botframework-integration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Visual Studio Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing Visual Studio for development and deployment steps, providing only Windows-centric tooling and workflows (e.g., Visual Studio, Command Prompt), and omitting Linux alternatives or examples. There are no instructions for using Linux-native tools (such as VS Code, dotnet CLI on Linux, or Azure CLI on Linux), nor are there deployment steps for Linux environments. All code samples and screenshots are tailored to Windows/Visual Studio users, leaving Linux developers without guidance.
Recommendations
  • Add explicit instructions and examples for Linux users, such as using VS Code or JetBrains Rider for development.
  • Include steps for deploying bots and chat apps using the dotnet CLI and Azure CLI on Linux/macOS.
  • Provide screenshots and walkthroughs for Linux environments (e.g., Ubuntu terminal, VS Code on Linux).
  • Mention cross-platform compatibility of the .NET SDK and clarify that development and deployment can be performed on Linux and macOS.
  • Offer PowerShell and Bash equivalents for package installation and CLI commands.
  • List prerequisites for Linux (e.g., apt-get install dotnet-sdk-3.1, VS Code installation) alongside Windows prerequisites.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-custom-managed-domain-resource-powershell.md ...es/create-custom-managed-domain-resource-powershell.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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module for all resource management tasks. There are no examples or instructions for using Azure CLI, Bash, or other cross-platform tools. This creates a strong Windows bias, as PowerShell is natively available on Windows and less commonly used on Linux/macOS systems. The documentation does not mention or provide parity for Linux users, nor does it offer alternative command-line examples.
Recommendations
  • Add equivalent Azure CLI examples for all resource management tasks (e.g., az communication email-domain create, az communication email-domain update, etc.).
  • Include a section on installing and using Azure CLI on Linux/macOS.
  • Mention that PowerShell Core is available cross-platform, but clarify usage differences if any.
  • Present both PowerShell and CLI examples side-by-side, or allow users to select their preferred shell.
  • Explicitly state platform compatibility for each tool and provide links to relevant installation guides for Linux/macOS.
  • Consider adding Bash script examples for common operations.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/create-communication-resource.md ...-services/quickstarts/create-communication-resource.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and patterns (e.g., PowerShell, setx, app.config/web.config) are mentioned first or exclusively in several sections. The Azure CLI installation link defaults to Windows, and environment variable instructions start with Windows. There is heavy use of PowerShell and .NET examples, with Linux/macOS equivalents presented after or less prominently. Windows-centric configuration files (app.config/web.config) are referenced without mentioning Linux alternatives (e.g., .env files).
Recommendations
  • Present Linux/macOS instructions and examples alongside or before Windows ones, rather than after.
  • Include Linux-specific configuration file examples (e.g., .env) in addition to app.config/web.config.
  • Provide Azure CLI installation links for Linux/macOS as well as Windows, or use a platform-neutral link.
  • Balance PowerShell and .NET examples with Bash/shell and Python examples where possible.
  • Ensure that all tooling and patterns mentioned have clear Linux/macOS equivalents, and highlight them equally.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/add-custom-verified-domains.md ...vices/quickstarts/email/add-custom-verified-domains.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 Windows First Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. PowerShell is presented as a primary automation option, and the only DNS management guide for 'Other (General)' points to a Windows-based DNS server. There are no explicit Linux or cross-platform DNS server instructions, and the documentation references Microsoft-centric tools and patterns throughout, with Windows-based approaches mentioned or implied before Linux equivalents (if any).
Recommendations
  • Add explicit Linux/BIND DNS server instructions for TXT and CNAME record management.
  • Include Bash or shell script examples alongside PowerShell for automation tasks.
  • Reference cross-platform tools (e.g., dig, nsupdate, web-based DNS panels) in 'Other (General)' DNS sections.
  • Ensure parity in example order: present Azure CLI and .NET examples before or alongside PowerShell.
  • Clarify that Azure CLI and .NET SDK are cross-platform and provide sample commands for Linux/macOS environments.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/chat/includes/chat-csharp.md ...tion-services/quickstarts/chat/includes/chat-csharp.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page shows evidence of Windows bias. Visual Studio is listed as a required prerequisite without mention of cross-platform alternatives (e.g., VS Code, JetBrains Rider). The package installation example uses PowerShell syntax, and there is no explicit Linux or macOS guidance for setup, tools, or environment. Console references mention cmd and PowerShell before Bash, and there are no Linux-specific troubleshooting or environment notes.
Recommendations
  • List cross-platform IDEs (e.g., VS Code, JetBrains Rider) alongside Visual Studio in prerequisites.
  • Provide package installation examples using both PowerShell and Bash (e.g., 'dotnet add package ...' works in both, but clarify shell usage).
  • Mention that all dotnet CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Include Linux/macOS-specific notes for environment setup, such as using Bash or zsh.
  • Add troubleshooting notes or links for common Linux/macOS issues (e.g., permissions, SDK installation).
  • Reorder references to shells so Bash is mentioned before or alongside cmd/PowerShell, or clarify that any shell can be used.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/create-email-communication-resource.md ...ickstarts/email/create-email-communication-resource.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 prominently featuring PowerShell as a management option, listing it as a distinct platform pivot alongside Azure portal, .NET, and Azure CLI. There is no explicit mention of Linux-specific tools or shell examples (e.g., Bash), nor are Linux workflows or compatibility discussed. The ordering and inclusion of PowerShell may lead users to perceive Windows as the primary or preferred environment, while Linux users may lack tailored guidance.
Recommendations
  • Add explicit Bash or Linux shell examples where applicable, especially in the Azure CLI section.
  • Clarify that Azure CLI commands work cross-platform and provide sample commands for both Windows (cmd/PowerShell) and Linux/macOS (Bash).
  • Include notes or sections on Linux prerequisites, environment setup, and troubleshooting.
  • Avoid listing PowerShell before cross-platform tools like Azure CLI, or group CLI and PowerShell together with clear cross-platform guidance.
  • Mention that .NET and Azure CLI are available on Linux and macOS, and provide links to installation instructions for those platforms.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-azure-managed-domain-resource-powershell.md ...des/create-azure-managed-domain-resource-powershell.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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module for all resource management tasks. There are no examples or instructions for Linux users, such as Bash, Azure CLI, or cross-platform alternatives. The documentation assumes the use of Windows tools and patterns, which may hinder accessibility for Linux or macOS users.
Recommendations
  • Provide equivalent Azure CLI examples for all resource management tasks (e.g., az communication email-domain create, az communication email-domain update, etc.).
  • Include installation instructions for Azure CLI and relevant modules on Linux and macOS.
  • Add notes clarifying cross-platform support and any differences in command usage or prerequisites.
  • Reorganize examples to present both PowerShell and CLI options side-by-side, or alternate which platform is shown first.
  • Reference documentation for Bash scripting and Linux terminal usage where appropriate.
GitHub Create Pull Request
← Previous Page 10 of 27 Next →