Communication Services

2083
Total Pages
1869
Linux-Friendly Pages
214
Pages with Bias
10.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

367 issues found
Showing 1-25 of 367 flagged pages
Communication Services Teams Phone Extensibility ...uickstarts/tpe/teams-phone-extensibility-quickstart.md
High Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias, particularly in administrative and provisioning steps. All command-line examples for Teams administration use PowerShell cmdlets and modules, which are native to Windows. There are no Linux/macOS equivalents or guidance for cross-platform alternatives. The Azure CLI section also mixes in PowerShell modules, and instructions for installing modules (e.g., Install-Module) are Windows-centric. The Teams Admin Center and Microsoft 365 Admin Center are referenced, but all automation and scripting is shown via PowerShell. No Bash, shell, or Linux-native tooling is mentioned, and the order of presentation always assumes Windows/PowerShell as the default environment.
Recommendations
  • Provide equivalent Bash or shell scripts for provisioning steps, especially for Azure CLI and bot registration.
  • Document how to use Teams PowerShell modules on Linux/macOS via PowerShell Core, including installation steps and caveats.
  • Explicitly state cross-platform requirements and limitations for each administrative step.
  • Add notes or sections for Linux/macOS users, including troubleshooting and alternative workflows.
  • Where possible, use Azure CLI commands instead of PowerShell for resource provisioning, as Azure CLI is cross-platform.
  • Clarify which steps require Windows-only tools and suggest remote or web-based alternatives (e.g., Teams Admin Center web UI).
GitHub Create Pull Request
Communication Services include file ...send-email-smtp/includes/send-email-smtp-powershell.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 exclusively provides instructions and examples using PowerShell and the Send-MailMessage cmdlet, which are native to Windows. There are no Linux or macOS equivalents, such as examples using 'sendmail', 'mailx', or Python's smtplib, nor is there mention of how to perform the same task on non-Windows platforms.
Recommendations
  • Add equivalent instructions and examples for Linux/macOS users, such as using 'sendmail', 'mailx', or Python scripts.
  • Include cross-platform SMTP examples (e.g., using Python's smtplib or curl).
  • Explicitly mention platform requirements and alternatives for non-Windows users.
  • Reorder or parallelize examples so Linux/macOS instructions are not secondary to Windows.
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-12 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 native to Windows. There are no examples or instructions for Linux/macOS users, such as using Azure CLI or REST API. This creates friction for non-Windows users and may prevent them from completing the task without additional research.
Recommendations
  • Add equivalent Azure CLI commands for registering and checking the Event Grid resource provider, as Azure CLI is cross-platform.
  • Include a note clarifying that PowerShell commands are Windows-specific and provide alternatives for Linux/macOS.
  • Consider providing REST API examples for maximum platform neutrality.
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 command-line examples for collecting verbose logs from browsers on Windows, referencing Windows file paths and executables. There are no examples or guidance for Linux or macOS users, nor are alternative commands or log locations mentioned for those platforms.
Recommendations
  • Add equivalent instructions and command-line examples for Linux and macOS, including typical executable paths (e.g., /usr/bin/google-chrome) and log file locations.
  • Mention platform-specific differences in command syntax, file paths, and permissions.
  • Clarify whether the described logging flags and procedures work identically on non-Windows platforms.
  • Provide troubleshooting tips for Linux/macOS users, such as how to locate browser executables and logs.
GitHub Create Pull Request
Communication Services References - How to collect diagnostic audio recordings ...ferences/how-to-collect-diagnostic-audio-recordings.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 page demonstrates Windows bias by providing build instructions and prerequisites exclusively for Windows (Visual Studio 2022, Windows depot_tools guide), referencing only the Windows build of unpack_aecdump.exe, and omitting Linux/macOS equivalents or instructions. No examples or guidance are given for building or running the tool on Linux or macOS, which may hinder non-Windows users from completing the task.
Recommendations
  • Add build instructions for Linux and macOS, including required packages and dependencies (e.g., gcc/clang, Python, depot_tools for Unix).
  • Reference official Chromium documentation for building rtc_tools/unpack_aecdump on Linux/macOS.
  • Provide example commands for building and running unpack_aecdump on Linux/macOS (e.g., ./unpack_aecdump audio_debug.5.aecdump).
  • Clarify cross-platform compatibility of the unpack_aecdump tool.
  • List Linux/macOS prerequisites (e.g., build-essential, Python, depot_tools) alongside Windows equivalents.
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 06:20
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 tools (MicrosoftTeams PowerShell module) for enabling interoperability in Teams. There are no examples or guidance for Linux or macOS users, nor are alternative cross-platform methods mentioned. The instructions assume access to PowerShell and administrative privileges typical of Windows environments.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as using PowerShell Core (pwsh) on those platforms.
  • Clarify whether the MicrosoftTeams PowerShell module is supported on PowerShell Core for non-Windows OS, and provide installation steps if so.
  • If the module is not supported cross-platform, suggest alternative approaches (e.g., Azure CLI, REST API, or web portal) for Linux/macOS users.
  • Explicitly state OS requirements and limitations at the start of the documentation.
  • Include example commands for both Windows and Linux/macOS environments where possible.
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 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a notable Windows bias in the troubleshooting steps for resolving Microsoft Entra App permission issues. The only provided method for creating a service principal is via PowerShell, with explicit instructions to install the Microsoft Graph PowerShell module and run PowerShell commands. No equivalent CLI, Bash, or cross-platform instructions are given, and there is no mention of how to perform these steps on Linux or macOS. The rest of the document is neutral, but this critical section may block non-Windows users.
Recommendations
  • Provide Azure CLI or Microsoft Graph API examples for creating service principals, which work on Linux, macOS, and Windows.
  • Explicitly mention cross-platform alternatives and link to relevant documentation for Linux/macOS users.
  • Reorder examples so that cross-platform tools (e.g., Azure CLI, REST API) are shown before or alongside PowerShell.
  • Add a note clarifying PowerShell Core is available on Linux/macOS, but also provide installation instructions and alternatives.
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 06:20
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 significant Windows bias. All development and deployment instructions are centered around Visual Studio (Windows-only), .NET Core (with examples only in C#), and PowerShell/dotnet CLI commands. There are no Linux/macOS-specific instructions, nor any mention of alternative development environments or deployment workflows for non-Windows platforms. Screenshots and UI walkthroughs are exclusively from the Windows Azure portal and Visual Studio. No Linux or macOS equivalents, such as VS Code, CLI-based workflows, or cross-platform deployment methods, are provided.
Recommendations
  • Add instructions and examples for Linux/macOS users, including using VS Code or JetBrains Rider as alternative IDEs.
  • Include CLI-based deployment steps using Azure CLI or GitHub Actions, rather than relying solely on Visual Studio publishing.
  • Provide .NET installation guidance for Linux/macOS, and clarify that dotnet CLI commands work cross-platform.
  • Show equivalent shell commands (bash/zsh) alongside PowerShell examples.
  • Include screenshots or descriptions for cross-platform tools and workflows.
  • Explicitly state which steps are platform-agnostic and which are Windows-specific, and offer alternatives where possible.
GitHub Create Pull Request
Communication Services include file ...es/quickstarts/email/includes/send-email-powershell.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 setup and usage instructions rely exclusively on Azure PowerShell, with explicit references to running commands in 'windows PowerShell'. There are no examples or guidance for Linux/macOS users, nor any mention of cross-platform alternatives such as Azure CLI or REST API. The installation instructions link to Windows-specific PowerShell installation, and all code samples use PowerShell syntax and Windows-centric file handling.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and supported on Linux/macOS.
  • Provide REST API or SDK (e.g., Python, Node.js) examples for sending email via Azure Communication Services.
  • Clarify whether the PowerShell module can be used on Linux/macOS (with PowerShell Core), and provide installation steps for those platforms if supported.
  • Rephrase 'In a windows PowerShell' to 'In PowerShell' and clarify cross-platform compatibility.
  • Ensure links to installation instructions include Linux/macOS options.
GitHub Create Pull Request
Communication Services include file ...ail-advanced/includes/inline-attachments-powershell.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 instructions reference Windows PowerShell specifically. There are no Linux/macOS equivalents, nor any mention of cross-platform alternatives such as Azure CLI or REST API. The installation instructions and prerequisite checks assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent instructions and examples for Azure CLI, which is cross-platform.
  • Include notes or sections for Linux/macOS users, specifying how to install and use the Azure Communication Services module outside Windows.
  • Provide REST API or SDK examples (e.g., Python, Node.js) for sending emails, which are platform-agnostic.
  • Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS and provide installation steps if so.
  • Reorder examples or provide tabs for Windows/PowerShell and Linux/CLI/SDK usage to improve parity.
GitHub Create Pull Request
Communication Services Prerequisites ...ces/quickstarts/includes/create-resource-powershell.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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/macOS users, such as using Azure CLI or Bash. The use of Windows-style command prompts (PS C:\>) and the lack of cross-platform guidance create a strong Windows bias.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all resource management tasks.
  • Include Bash or shell examples for Linux/macOS users.
  • Clarify which commands and modules are cross-platform, and note any platform-specific limitations.
  • Reorder examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
  • Explicitly mention installation steps for Linux/macOS environments.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides instructions and command-line examples for collecting verbose logs from browsers on Windows, using Windows file paths and executables. There are no examples or guidance for Linux or macOS users, and only Windows-specific tools and patterns are mentioned.
Recommendations
  • Add equivalent instructions and command-line examples for Linux and macOS, including typical executable paths (e.g., /usr/bin/google-chrome) and file locations.
  • Clarify any differences in command-line arguments or log file locations for non-Windows platforms.
  • Include screenshots or terminal examples for Linux/macOS where appropriate.
  • Mention platform-specific considerations, such as permissions or sandboxing differences.
GitHub Create Pull Request
Communication Services include file ...ludes/email-resource-management-azurecli-powershell.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based automation scripts and examples. All code samples use PowerShell syntax and constructs (e.g., Write-Host, try/catch, functions, variable assignment), which are not natively supported on Linux/macOS shells. Prerequisite checks and installation links reference Windows-specific instructions first, and there are no equivalent Bash or cross-platform shell examples. This creates friction for Linux/macOS users who cannot directly use the provided scripts.
Recommendations
  • Provide equivalent Bash shell scripts for all automation tasks, using standard Bash syntax and constructs.
  • Include Linux/macOS installation instructions for Azure CLI and PowerShell, or clarify cross-platform support.
  • Explicitly state which parts of the script are Windows/PowerShell-only and offer alternatives for other platforms.
  • Consider using only Azure CLI commands in examples, as Azure CLI is cross-platform, and avoid PowerShell-specific scripting unless necessary.
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-10 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 tools (MicrosoftTeams PowerShell module) for enabling interoperability in Teams. There are no examples or instructions for Linux or macOS users, nor are alternative CLI tools or cross-platform methods mentioned. The instructions assume the use of PowerShell and administrative privileges typical of 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 how to install it on non-Windows systems.
  • Include examples using Azure CLI or REST API if available, which are cross-platform.
  • Explicitly mention any platform limitations or requirements for the described steps.
  • Add troubleshooting notes for common issues encountered on Linux/macOS (e.g., module installation, authentication prompts).
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-10 00:00
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 by referencing the Teams Admin Center (TAC) portal and PowerShell cmdlets as the methods for configuring emergency calling support, without mentioning equivalent Linux-friendly tools or CLI alternatives. Windows-centric tools are presented as the default or only options for administrative tasks, and there are no examples or guidance for Linux environments or cross-platform command-line usage.
Recommendations
  • Include instructions for configuring Teams Phone extensibility features using cross-platform tools such as Microsoft Graph API, Azure CLI, or REST APIs.
  • Provide Linux-compatible examples for administrative tasks, such as using bash scripts or platform-neutral CLI commands.
  • Explicitly mention whether PowerShell cmdlets can be run on Linux (via PowerShell Core), and provide guidance for Linux users.
  • Add references to platform-agnostic management options and clarify any limitations or requirements for non-Windows environments.
  • Ensure that documentation does not assume the use of Windows-only tools and offers parity for Linux and macOS administrators.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing the Teams Admin Center and PowerShell as the primary tools for configuration, without mentioning Linux-compatible alternatives or providing cross-platform examples. The guidance assumes access to Windows-centric administration tools and does not address how Linux users can perform equivalent tasks.
Recommendations
  • Include instructions or examples for configuring Teams tenant using cross-platform tools, such as Microsoft Graph API or web-based portals.
  • Explicitly mention whether Teams Admin Center is accessible via web browser on Linux and provide links or notes for Linux users.
  • Provide parity by listing Linux-compatible methods for managing Teams policies and configurations, such as using REST APIs or CLI tools available on Linux.
  • Avoid referencing PowerShell exclusively; if PowerShell is required, note how it can be installed and used on Linux, or offer alternative approaches.
  • Add examples or notes clarifying how Linux administrators can achieve the same outcomes as those using Windows tools.
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-10 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 the Microsoft Teams Client as the primary methods for assigning delegates, without mentioning Linux equivalents or alternatives. There are no examples or instructions for Linux users, and the prerequisite steps and tooling are Windows-centric. The note about platform support lists Windows explicitly, but does not clarify Linux support or provide parity information.
Recommendations
  • Include instructions or examples for assigning delegates using cross-platform tools, such as Azure CLI, REST API, or Graph API, if available.
  • Explicitly state whether Linux users can perform the same actions, and provide guidance or workarounds if direct support is missing.
  • Add references to Linux-compatible tools or scripts where possible, and ensure that examples are not exclusively PowerShell-based.
  • Clarify platform support for shared line appearance, including Linux and macOS, in the relevant sections.
  • Consider reordering examples or instructions so that platform-neutral or cross-platform methods are presented before Windows-specific ones.
GitHub Create Pull Request
Communication Services Teams Phone extensibility Troubleshooting ...terop/tpe/teams-phone-extensibility-troubleshooting.md
High Priority View Details →
Scanned: 2026-01-10 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. Only PowerShell commands are provided, with explicit instructions to use PowerShell and install the Microsoft Graph module—both Windows-centric tools. There are no equivalent examples or guidance for Linux or cross-platform environments (e.g., Azure CLI, Bash, or REST API). The troubleshooting workflow assumes access to Windows tools and does not mention alternatives for Linux or macOS users.
Recommendations
  • Provide equivalent troubleshooting steps using Azure CLI, Bash, or REST API for Linux/macOS users.
  • Include cross-platform instructions and examples alongside PowerShell commands.
  • Mention and link to documentation for non-Windows environments where possible.
  • Clarify which steps are Windows-specific and offer alternatives for other operating systems.
  • Consider reordering examples so that cross-platform tools (e.g., Azure CLI) are presented before or alongside PowerShell.
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-10 00:00
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 Windows-specific tools (e.g., PowerShell for Teams meeting policy management) and linking to Windows-centric documentation before mentioning or providing Linux alternatives. There are no examples or instructions for managing Teams policies or breakout rooms using Linux-native tools, nor is there mention of cross-platform command-line options. The SDK support table lists 'Windows' as a platform but does not clarify parity or provide Linux desktop guidance.
Recommendations
  • Include instructions or references for managing Teams meeting policies using cross-platform tools such as Microsoft Graph API, which can be used on Linux and macOS.
  • Provide explicit Linux/macOS examples for any command-line or scripting steps, especially for administrative tasks.
  • Clarify SDK support for Linux desktop environments and add relevant documentation or links.
  • Avoid linking exclusively to Windows PowerShell documentation; offer alternatives or mention that PowerShell Core is available cross-platform.
  • Add a section or notes on how Linux users can perform equivalent operations, ensuring parity in administrative and developer workflows.
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-10 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 a Windows bias by referencing Teams PowerShell and Microsoft Teams Client (both Windows-centric tools) as the primary methods for assigning delegates. No Linux equivalents or cross-platform CLI alternatives are mentioned. The SDK support table lists 'Windows' as a platform but does not mention Linux or macOS, nor does it provide parity in examples or tooling for non-Windows environments.
Recommendations
  • Include instructions or examples for assigning delegates using cross-platform tools, such as Azure CLI or REST APIs, if available.
  • Explicitly mention Linux and macOS support status in the SDK support table, and provide guidance for those platforms.
  • If PowerShell is required, clarify whether PowerShell Core (which runs on Linux/macOS) is supported, and provide installation and usage instructions for those platforms.
  • Offer alternative methods for managing Teams features that do not rely on Windows-only tools.
  • Ensure that all examples and prerequisites are platform-agnostic or provide parallel instructions for Linux/macOS users.
GitHub Create Pull Request
Communication Services include file ...-services/quickstarts/email/includes/send-email-net.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on .NET and C#, with all code samples and instructions tailored to the .NET SDK. Command-line instructions mention 'cmd, PowerShell, or Bash', but examples use Windows-centric tools and patterns (dotnet CLI, Program.cs, Console.WriteLine) without providing Linux-specific guidance or parity for alternative platforms. There are no Linux-specific examples, troubleshooting steps, or mentions of Linux tools/environments. The documentation assumes a Windows development environment and omits guidance for Linux users beyond generic references to 'your operating system'.
Recommendations
  • Add explicit Linux and macOS instructions for installing .NET Core and running dotnet commands, including package managers (apt, yum, brew).
  • Include sample code and instructions for using the Email SDK in other languages/platforms (e.g., Python, Java, Node.js) to improve cross-platform parity.
  • Provide troubleshooting steps and environment setup guidance for Linux users, including permissions, environment variables, and common issues.
  • Reference Linux-specific terminals and editors (e.g., GNOME Terminal, nano, vim) alongside Windows tools.
  • Clarify that the .NET SDK and Azure Communication Services can be used on Linux and macOS, and link to official cross-platform documentation.
GitHub Create Pull Request
Communication Services include file ...send-email-smtp/includes/send-email-smtp-powershell.md
High Priority View Details →
Scanned: 2026-01-10 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 PowerShell examples and references the Windows-specific Send-MailMessage utility, with no mention of Linux-compatible tools or cross-platform alternatives. There are no examples for Linux users (e.g., using sendmail, mailx, or Python scripts), and Windows tools are presented as the default approach.
Recommendations
  • Add equivalent Linux examples using common tools such as sendmail, mailx, or Python's smtplib.
  • Include cross-platform code samples (e.g., Python, Node.js) that work on both Windows and Linux.
  • Explicitly mention Linux compatibility and provide instructions for Linux users.
  • Present Windows and Linux examples side-by-side, or clarify which platforms each example supports.
  • Avoid assuming PowerShell is available by default; note installation requirements for non-Windows platforms.
GitHub Create Pull Request
Communication Services Send an email using SMTP ...s/quickstarts/email/send-email-smtp/send-email-smtp.md
High Priority View Details →
Scanned: 2026-01-10 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 provides examples for sending email via SMTP using SmtpClient (typically .NET, often associated with Windows) and Windows PowerShell, but does not include equivalent Linux or cross-platform command-line examples (e.g., using 'sendmail', 'mailx', or 'curl'). Windows-specific tools and patterns are emphasized, and Linux alternatives are missing.
Recommendations
  • Add Linux-specific examples, such as using 'sendmail', 'mail', 'mailx', or 'curl' to send emails via SMTP.
  • Include cross-platform scripting examples (e.g., Python, Node.js) that work on both Windows and Linux.
  • Explicitly mention Linux tools and provide step-by-step instructions for common Linux distributions.
  • Balance the order of examples so that Windows and Linux approaches are presented equally or in parallel.
GitHub Create Pull Request
Communication Services Prerequisites ...es/create-custom-managed-domain-resource-powershell.md
High Priority View Details →
Scanned: 2026-01-10 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 references the Azure Az PowerShell Module for all resource management tasks, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI, Bash, or REST API. This creates a strong Windows bias, as PowerShell is primarily associated with Windows environments, and Linux users may not have PowerShell installed or prefer native tools.
Recommendations
  • Add equivalent Azure CLI examples for all resource management operations (e.g., az communication email-domain create, update, list, delete).
  • Mention that PowerShell is available cross-platform, but clarify installation steps for Linux and macOS if PowerShell is required.
  • Provide Bash or shell script examples where appropriate, especially for DNS record updates or verification steps.
  • Reference REST API documentation for users who prefer direct API calls.
  • Reorder sections or add parallel examples so that Linux-friendly tools (Azure CLI, Bash) are presented alongside or before PowerShell examples.
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-10 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 or instructions for Linux/macOS users, such as using Azure CLI or Bash. This creates a Windows-centric experience and may hinder users on other platforms.
Recommendations
  • Add equivalent Azure CLI commands (e.g., 'az provider register --namespace Microsoft.EventGrid') for cross-platform compatibility.
  • Include Bash or shell examples where appropriate.
  • Clearly indicate that PowerShell is one option and provide alternatives for Linux/macOS users.
  • Consider reordering examples so that cross-platform tools (like Azure CLI) are presented before or alongside PowerShell.
GitHub Create Pull Request
← Previous Page 1 of 15 Next →