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 176-200 of 656 flagged pages
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/sdk-options.md ...rticles/communication-services/concepts/sdk-options.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the SDK platform support section, where Windows platforms are listed first and in greater detail, especially for .NET and Calling SDKs. Windows-specific technologies (UWP, WinUI3, .NET Native, C++/WinRT) are highlighted, and unpackaged Windows apps are discussed. Linux and macOS support is mentioned only as part of .NET Standard/Core compatibility, with no specific examples or details. There are no Linux-specific usage examples, troubleshooting, or platform notes, and no mention of Linux tools or patterns (e.g., bash, curl, CLI usage) in REST API sections.
Recommendations
  • Add explicit Linux and macOS platform support details for each SDK, including minimum versions and distributions tested.
  • Provide Linux-specific examples for SDK installation and usage, such as using bash, curl, or Linux package managers.
  • Include troubleshooting and best practices sections for Linux environments, similar to those provided for Windows and mobile platforms.
  • Mention Linux tools (e.g., curl, wget, jq) for REST API usage alongside Postman.
  • Ensure parity in platform ordering and detail, listing Linux and macOS platforms before or alongside Windows where appropriate.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/guest/monitor-logs-metrics.md ...ervices/concepts/interop/guest/monitor-logs-metrics.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing Microsoft-centric tools such as Teams Admin Center and Teams Call Quality Dashboard, which are primarily accessed via web or Windows environments. There are no examples or guidance for accessing logs or metrics using Linux-native tools, CLI, or cross-platform methods. The documentation assumes administrative workflows through graphical interfaces typical of Windows, with no mention of Linux or cross-platform alternatives.
Recommendations
  • Include examples of accessing Azure logs and metrics using cross-platform tools such as Azure CLI, PowerShell Core (which runs on Linux), or REST APIs.
  • Provide instructions for viewing or exporting Teams logs and metrics using command-line tools available on Linux, such as curl or az CLI.
  • Mention whether Teams Admin Center and Call Quality Dashboard are accessible from Linux browsers and clarify any platform limitations.
  • Add parity by referencing log analysis tools and workflows common in Linux environments, such as using jq for JSON logs, or integrating with syslog.
  • Explicitly state that the procedures are platform-agnostic where applicable, or provide alternative steps for Linux users if differences exist.
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-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 strong Windows bias by exclusively referencing PowerShell modules and cmdlets for configuration and policy management, and by listing 'Teams Admin Center or PowerShell' as the only tools for administrative tasks. There are no examples or mentions of Linux-native tools, CLI alternatives, or cross-platform scripting options. The documentation assumes the use of Windows-centric administration patterns, with no guidance for Linux administrators or parity in example commands.
Recommendations
  • Include equivalent CLI or REST API examples for all PowerShell commands, highlighting cross-platform usage.
  • Explicitly mention and provide examples for managing Teams and Azure Communication Services from Linux or macOS environments.
  • Reference Microsoft Graph API and Azure CLI as alternatives to PowerShell for configuration and policy management.
  • Add a section or note clarifying cross-platform support and administrative options for non-Windows users.
  • Ensure that tool and example listings do not default to Windows-first; present cross-platform options in parallel or before Windows-specific ones.
GitHub Create Pull Request
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-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 demonstrates Windows bias by referencing Teams PowerShell and the Microsoft Teams Client (both Windows-centric tools) as the only methods for assigning delegates. There are no Linux or cross-platform alternatives mentioned, nor are Linux-specific instructions or examples provided. The prerequisites and enablement steps focus on Windows tools first, and do not acknowledge Linux or non-Windows environments. Additionally, the note about platform support lists Windows explicitly but does not clarify Linux support, potentially implying Windows as the default or primary platform.
Recommendations
  • Include instructions or examples for assigning delegates using cross-platform tools, such as Azure CLI or REST APIs, if available.
  • Explicitly mention Linux support status for shared line appearance and provide guidance for Linux users.
  • Add parity in examples by providing Linux shell (bash) or platform-agnostic steps alongside PowerShell/Windows instructions.
  • Clarify whether the Microsoft Teams Client is available on Linux and, if not, suggest alternatives for Linux users.
  • Ensure that documentation does not assume Windows as the default platform and addresses cross-platform scenarios equally.
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-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 through its references to Teams administration via the TAC portal and PowerShell cmdlets, with no mention of Linux-compatible alternatives or cross-platform CLI tools. There are no examples or guidance for Linux or macOS administrators, and all provisioning and policy management instructions assume a Windows-centric environment. This may hinder adoption or ease of use for organizations and developers working on non-Windows platforms.
Recommendations
  • Include examples and instructions for Teams administration using cross-platform tools, such as Microsoft Graph API or Azure CLI, which are available on Linux and macOS.
  • Explicitly mention that PowerShell cmdlets are Windows-specific and provide alternative methods for Linux users.
  • Add a section or callout for Linux/macOS administrators, outlining how to perform key provisioning and policy management tasks without relying on Windows-only tools.
  • Ensure that future documentation and quickstarts provide parity in examples for both Windows and Linux environments, especially for command-line and automation tasks.
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-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 Windows bias primarily in the troubleshooting steps for Microsoft Entra App permission issues, where only PowerShell commands and instructions are provided. There are no equivalent examples or guidance for Linux/macOS users (e.g., using Azure CLI, Bash, or cross-platform tools). The documentation assumes access to PowerShell and Windows-specific modules, and does not mention alternatives or parity for non-Windows environments.
Recommendations
  • Provide equivalent troubleshooting steps using Azure CLI or Microsoft Graph API via Bash or cross-platform shell environments.
  • Include explicit instructions or examples for Linux/macOS users, such as using Azure CLI or REST API calls.
  • Mention that PowerShell is available cross-platform, but clarify installation steps for non-Windows systems.
  • List both Windows and Linux/macOS options side-by-side, or note platform-specific requirements where relevant.
  • Avoid assuming users have access to Windows tools by default; offer alternatives wherever possible.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias by referencing Windows-specific tools and patterns, such as the Set-CsPhoneNumberAssignment PowerShell cmdlet, and by mentioning the Teams desktop client (implicitly Windows) before other platforms. There is a lack of Linux-specific examples, tools, or instructions, and no mention of Linux command-line alternatives or parity for administrative tasks.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using Azure CLI, REST API, or cross-platform PowerShell Core) for administrative tasks like phone number assignment.
  • Explicitly mention cross-platform compatibility for Teams desktop client, clarifying support for Linux if available.
  • Include examples or scenarios using Linux clients (e.g., Teams on Linux, browser on Linux) in pricing scenarios.
  • Reference Linux tools and workflows where applicable, and avoid assuming Windows as the default environment for administration.
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-09 00:34
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 primarily through its reliance on Microsoft Teams PowerShell cmdlets for critical administrative steps, such as enabling federation and external access policies. These steps are presented without Linux or cross-platform alternatives, and PowerShell is referenced as the default tool for tenant configuration. Additionally, the administrative setup and resource management instructions assume familiarity with Windows-centric tools and patterns, with no mention of Linux equivalents or CLI alternatives.
Recommendations
  • Provide Azure CLI or REST API equivalents for all PowerShell-based administrative steps, especially for tenant federation and external access policy configuration.
  • Explicitly mention cross-platform options for administrative tasks, including links to Linux-compatible tools or scripts where available.
  • Reorder instructions or add parallel guidance so that Linux/macOS users are not required to use Windows tools or PowerShell, ensuring equal accessibility.
  • Include examples or references for performing prerequisite steps (such as resource management and configuration) using Linux-friendly approaches.
  • Add a note clarifying which steps are platform-agnostic and which require Windows-specific tooling, with guidance for non-Windows environments.
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-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 Windows bias in several ways. In the quick-start section, the console window examples list Windows shells (cmd, PowerShell) before Bash, and no Linux-specific instructions or troubleshooting are provided. All code samples use .NET/C#, which is cross-platform, but the environment setup and instructions implicitly prioritize Windows. There are no explicit Linux or macOS examples, nor any mention of platform-specific considerations for non-Windows users.
Recommendations
  • Explicitly mention Linux and macOS support in the prerequisites and quick-start sections.
  • Provide Linux/macOS-specific instructions for creating and running the .NET application (e.g., using Bash, zsh, or terminal on those platforms).
  • Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, package installation).
  • List Bash or Linux terminal before or alongside Windows shells when referencing console windows.
  • Add a note that the .NET SDK and Azure tools are cross-platform, and link to installation guides for Linux/macOS.
  • Consider providing a sample using a language or SDK more common on Linux (e.g., Python) if supported.
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-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 demonstrates a strong Windows bias. All development and deployment instructions are centered around Visual Studio, a Windows-centric IDE, with no mention of Linux alternatives (such as VS Code, JetBrains Rider, or command-line workflows). Package installation is shown only with 'dotnet add package' (using PowerShell syntax), and deployment steps rely on Visual Studio's GUI. There are no Linux-specific instructions, nor any mention of cross-platform development environments or CLI-based deployment. Screenshots and workflow descriptions assume use of Windows tools and patterns throughout.
Recommendations
  • Add instructions for Linux users, including how to install .NET Core and Bot Framework SDK on Linux.
  • Provide examples for deploying the bot and chat app using the Azure CLI or GitHub Actions, not just Visual Studio.
  • Include package installation commands for Bash/zsh shells (e.g., 'dotnet add package' in a Linux terminal).
  • Mention and provide steps for using cross-platform editors like VS Code.
  • Clarify that the SDKs and tools are cross-platform, and explicitly state which steps are OS-agnostic.
  • Add screenshots or terminal output examples from Linux environments.
  • Ensure troubleshooting and next steps sections include Linux-specific guidance.
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-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 Windows bias by referencing Teams meeting policy management via PowerShell (a Windows-centric tool) and linking to a PowerShell module as the primary method for enabling breakout rooms. There are no Linux or cross-platform alternatives mentioned for Teams policy management, nor are there examples or instructions for non-Windows environments. The SDK support table lists 'Windows' as a platform but does not provide parity or examples for Linux or macOS clients.
Recommendations
  • Include instructions or links for managing Teams meeting policies using cross-platform tools (e.g., Microsoft Graph API, web portal) alongside PowerShell.
  • Explicitly mention whether breakout room features can be managed or accessed from Linux or macOS environments, and provide relevant examples if possible.
  • Expand the SDK support table to clarify support for Linux and macOS clients, or add examples for those platforms if supported.
  • Avoid referencing Windows-specific tools (like PowerShell) as the sole method for administrative tasks; always provide alternatives or note platform limitations.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Teams PowerShell for delegate assignment, mentioning Windows tools before any Linux alternatives, and omitting Linux-specific instructions or examples. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform methods for managing Teams Shared Line Appearance.
Recommendations
  • Provide Linux and macOS equivalents for delegate assignment, such as Azure CLI or Bash scripts.
  • Include cross-platform instructions and examples, ensuring parity for non-Windows users.
  • Explicitly mention whether features or tools (like Teams PowerShell) are available or supported on Linux and macOS.
  • Add troubleshooting or notes for Linux users regarding limitations or alternative approaches.
  • Reorder instructions to present cross-platform or OS-neutral methods first, followed by OS-specific tools.
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-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 listing Windows-specific tools (Visual Studio) as a prerequisite, using PowerShell for package installation, and referencing Windows consoles (cmd, PowerShell) before Bash. There are no explicit Linux or cross-platform alternatives for key steps such as IDE setup or package installation, and no mention of Linux-specific considerations or troubleshooting.
Recommendations
  • List cross-platform IDEs (e.g., VS Code, JetBrains Rider) alongside Visual Studio in prerequisites.
  • Provide Linux-specific instructions for installing the .NET SDK and running dotnet commands.
  • Use generic 'terminal' or 'shell' terminology instead of 'cmd, PowerShell' and mention Bash equally.
  • Show package installation commands using 'dotnet add package' in a generic shell, not PowerShell-specific syntax.
  • Include troubleshooting notes for common Linux issues (e.g., permissions, environment setup).
  • Add explicit statements that all commands work on Linux, macOS, and Windows, or highlight any platform-specific differences.
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-09 00:34
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 (such as PowerShell, app.config/web.config, and setx) are mentioned first or exclusively in several places. The Azure CLI installation link defaults to Windows, and PowerShell is given its own example section. The configuration examples for environment variables start with Windows, and Windows-specific tooling (Visual Studio, app.config/web.config) is referenced before Linux/macOS equivalents. Linux and macOS examples are present but are secondary.
Recommendations
  • Ensure Linux and macOS examples are presented with equal prominence and ordering as Windows examples.
  • Provide cross-platform installation instructions for Azure CLI, not just a Windows link.
  • Mention Linux/macOS equivalents (e.g., configuration files, editors) alongside Windows tools like Visual Studio and app.config/web.config.
  • Avoid giving PowerShell its own section unless Bash or other shells are equally represented.
  • Consider grouping environment variable instructions in a way that does not prioritize Windows (e.g., alphabetical or by usage statistics).
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by including PowerShell as a primary example, referencing Windows-based DNS management in the 'Other (General)' CNAME section, and linking to Microsoft 365 DNS guides that often assume Windows environments. There is no explicit mention of Linux-specific tools or workflows (such as Bash, dig, or Linux DNS management), and Windows-centric tools and terminology are presented before or instead of Linux equivalents.
Recommendations
  • Add explicit Linux/Bash examples for domain/DNS management, such as using dig, nsupdate, or editing BIND zone files.
  • Include instructions or links for managing DNS records on Linux-based DNS servers (e.g., BIND, Unbound, dnsmasq).
  • Ensure parity between PowerShell and Bash/Azure CLI examples, and clarify cross-platform compatibility for Azure CLI commands.
  • Replace or supplement 'Windows-based DNS' links with guides for Linux-based DNS management.
  • Review and update documentation to mention Linux tools and workflows wherever Windows tools are referenced.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by providing PowerShell examples and mentioning the .NET management client library, both of which are Windows-centric tools. The inclusion of PowerShell as a dedicated pivot and the early mention of .NET (commonly associated with Windows development) reinforce this bias. Although Azure CLI is included (which is cross-platform), there is no explicit mention or example of Linux-specific tools, shell commands, or workflows. The ordering and emphasis on Windows tools and patterns suggest a preference for Windows environments.
Recommendations
  • Add explicit Linux shell (bash) examples or workflows where appropriate.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • Include references to Linux-native tools or scripts for resource management.
  • Balance the order of pivots/examples so that Windows and Linux options are presented equally.
  • Mention cross-platform compatibility in introductory sections to avoid implicit Windows preference.
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-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 exclusively uses PowerShell commands and references the Azure Az PowerShell Module for all resource management tasks. There are no examples or mentions of equivalent Linux-friendly tools (such as Azure CLI, Bash, or REST API), and the workflow assumes a Windows/PowerShell environment. This creates a strong Windows bias and may hinder users on Linux or macOS platforms.
Recommendations
  • Provide equivalent Azure CLI examples for all resource management operations.
  • Mention cross-platform alternatives (Azure CLI, REST API, SDKs) in the prerequisites and throughout the documentation.
  • Clarify that PowerShell is available on Linux and macOS, but highlight platform-agnostic approaches.
  • Add notes or sections for Linux/macOS users, including installation instructions for Azure CLI and PowerShell Core.
  • Ensure that all command-line examples are presented in both PowerShell and Azure CLI formats, or link to relevant cross-platform documentation.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-sender-username-resource-powershell.md ...includes/create-sender-username-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 exclusively uses PowerShell commands and references the Azure Az PowerShell Module for all operations, with no mention of Azure CLI, Bash, or Linux-native tools. All examples and instructions are tailored to PowerShell, which is traditionally a Windows-centric tool, and there is no guidance for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all operations (login, resource creation, management, deletion).
  • Include installation instructions for Azure CLI and note cross-platform compatibility.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or provide Bash script alternatives.
  • Reorder examples so that cross-platform tools like Azure CLI are presented before or alongside PowerShell.
  • Add a section addressing platform compatibility and recommending tools for Linux/macOS users.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-email-resource-powershell.md ...rts/email/includes/create-email-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 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 using Azure CLI, Bash, or cross-platform tools. The documentation assumes the use of Windows tools and patterns, potentially excluding or confusing users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all resource management tasks (creating, updating, listing, and deleting resources).
  • Include installation instructions for Azure CLI on Linux and macOS, alongside PowerShell.
  • Clearly indicate which commands are platform-specific and provide cross-platform alternatives where possible.
  • Reorder examples or provide parallel sections for PowerShell and CLI/Bash to avoid Windows-first bias.
  • Mention that Azure PowerShell is available cross-platform, but highlight CLI as a common choice for Linux users.
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-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 bias toward Windows environments and tooling. It references Windows-specific consoles (cmd, PowerShell) before mentioning Bash, and all code samples and instructions use .NET and C#, which are traditionally Windows-centric. There are no Linux-specific instructions, examples, or troubleshooting tips, and no mention of Linux package managers or shell environments beyond a brief nod to Bash. The documentation assumes familiarity with Windows patterns and does not provide parity for Linux users.
Recommendations
  • Explicitly mention Linux and macOS compatibility for .NET Core and Azure SDKs.
  • Include Linux-specific instructions for installing .NET Core (e.g., apt, yum, snap commands).
  • Provide examples of running commands in Linux shells (e.g., bash, zsh) and clarify any differences.
  • Add troubleshooting tips for common Linux issues (e.g., permissions, environment variables).
  • List prerequisites for Linux environments, such as required dependencies or configuration steps.
  • Ensure that sample code and instructions are platform-agnostic, or provide platform-specific notes where necessary.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/send-email-powershell.md ...es/quickstarts/email/includes/send-email-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 is heavily biased towards Windows and PowerShell. All examples use Azure PowerShell, and prerequisite checks explicitly mention Windows PowerShell. There are no instructions or examples for Linux or cross-platform alternatives such as Azure CLI, Bash, or SDK usage. Windows tools and patterns are mentioned exclusively, with no parity for Linux users.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include Bash or shell script examples for common tasks such as sending email or checking prerequisites.
  • Mention installation and usage steps for Azure PowerShell on Linux and macOS, or clarify cross-platform support.
  • Provide guidance for using Azure SDKs (e.g., Python, Node.js) to send emails, which are platform-agnostic.
  • Rephrase prerequisite checks to avoid assuming Windows-only environments (e.g., 'In a terminal, run...').
  • Ensure all features and steps are documented for both Windows and Linux users, with clear parity.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/send-email-net.md ...-services/quickstarts/email/includes/send-email-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 bias towards Windows environments and tooling. All code samples and instructions are exclusively for C#/.NET, with commands and workflows centered around the dotnet CLI. Terminal examples mention 'cmd, PowerShell, or Bash', but all commands are platform-agnostic and do not provide explicit Linux or macOS instructions. There are no Linux-specific examples, troubleshooting steps, or references to Linux tools or patterns. The documentation assumes familiarity with Windows-centric development environments and does not address cross-platform considerations or potential issues on Linux.
Recommendations
  • Add explicit Linux/macOS instructions, including terminal commands and environment setup steps.
  • Include troubleshooting notes for common Linux issues (e.g., permissions, environment variables, .NET installation).
  • Provide examples of running the code on Linux (e.g., Ubuntu) and macOS, including screenshots or terminal output.
  • Reference Linux package managers (e.g., apt, yum, brew) for installing .NET Core.
  • Clarify any platform-specific differences in behavior, especially for environment variables and file paths.
  • Ensure parity in sample code and documentation for both Windows and Linux/macOS users.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/inline-attachments-powershell.md ...ail-advanced/includes/inline-attachments-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 is heavily biased towards Windows and PowerShell. All examples use PowerShell syntax, and instructions explicitly reference Windows PowerShell. There are no examples or guidance for Linux or macOS users, nor any mention of cross-platform alternatives such as Azure CLI or Bash. The installation instructions and prerequisite checks are Windows-centric, and no Linux tools or patterns are discussed.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and works on Linux/macOS.
  • Provide Bash or shell script examples for sending emails using Azure Communication Services.
  • Clarify that Azure PowerShell can be installed and used on Linux/macOS, and provide installation instructions for those platforms.
  • Include prerequisite checks and module installation steps for Linux/macOS environments.
  • Reorder or balance the documentation so that Windows and Linux/macOS instructions/examples are presented equally.
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-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 provides instructions and examples for sending email via SMTP using PowerShell and the Send-MailMessage cmdlet, which are native to Windows environments. There are no examples or guidance for Linux or cross-platform tools, such as using Python, curl, or other SMTP clients commonly available on Linux. The documentation assumes the user is on Windows and familiar with PowerShell, omitting Linux equivalents and alternative approaches.
Recommendations
  • Add Linux-specific examples using common tools such as 'sendmail', 'mailx', or 'mutt'.
  • Provide cross-platform code samples, e.g., using Python's smtplib or Node.js libraries.
  • Include instructions for storing credentials securely on Linux systems.
  • Mention alternative SMTP clients and utilities available on Linux and macOS.
  • Reorganize the documentation to present both Windows and Linux approaches side-by-side or in parallel sections.
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-smtpclient.md ...send-email-smtp/includes/send-email-smtp-smtpclient.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 terminals (cmd, PowerShell) before Bash when describing where to run commands, and does not provide any Linux-specific instructions or examples. All code samples and instructions are generic but implicitly target Windows environments, with no mention of Linux-specific considerations (e.g., package installation, environment setup, or troubleshooting). There are no examples using Linux tools or patterns, nor any explicit guidance for Linux users.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms where applicable.
  • Provide Linux-specific instructions for installing .NET Core (e.g., using apt, yum, or Homebrew).
  • List Bash or Linux terminal first or equally alongside Windows terminals.
  • Include troubleshooting notes for Linux users (e.g., firewall, SSL/TLS issues, permissions).
  • Add examples for running the sample on Linux (e.g., using Bash, verifying dependencies, running the application).
  • Clarify any platform-specific differences in environment setup or usage.
GitHub Create Pull Request
← Previous Page 8 of 27 Next →