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 26-50 of 656 flagged pages
Communication Services Add a bot to your chat app ...uickstarts/chat/quickstart-botframework-integration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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 exhibits a Windows bias by consistently referencing Visual Studio (a Windows-centric IDE) for development and deployment steps, providing only Windows-oriented instructions and screenshots, and omitting Linux equivalents or alternatives. There are no examples using Linux-friendly tools (such as VS Code, CLI-only workflows, or Linux deployment commands), and all code and deployment instructions assume a Windows environment. Package installation is shown with dotnet and Powershell, but not with Linux shell commands. No mention is made of Linux or cross-platform development environments.
Recommendations
  • Add instructions and screenshots for using VS Code or other cross-platform editors, including CLI-only workflows.
  • Include Linux shell equivalents for commands (e.g., use 'bash' for dotnet commands, show how to install .NET Core on Linux).
  • Provide deployment steps using Azure CLI on Linux, not just Visual Studio publish dialogs.
  • Mention and link to Linux installation guides for prerequisites (e.g., .NET Core, Bot Framework SDK).
  • Clarify that the SDKs and tools are cross-platform, and explicitly state Linux is supported.
  • Add troubleshooting and FAQ sections for common Linux-specific issues (e.g., permissions, environment setup).
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates a Windows bias primarily through its reliance on Windows-centric tools and patterns. The prerequisite for assigning Teams meeting policy links directly to a PowerShell module, which is a Windows-specific tool, and does not mention or provide Linux/macOS alternatives (such as Microsoft Graph API or Teams admin center web interface). The documentation references Windows tools first and exclusively, with no parity for Linux users in administrative tasks. There are no Linux-specific examples or guidance for managing Teams policies or breakout rooms.
Recommendations
  • Provide alternative instructions for assigning Teams meeting policies using cross-platform tools such as Microsoft Graph API or the Teams admin center web interface.
  • Include examples or links for managing breakout rooms from non-Windows environments (Linux/macOS).
  • Clarify which steps are platform-agnostic and which require Windows, and offer parity wherever possible.
  • Add explicit notes or sections for Linux/macOS users to ensure they are not excluded from administrative or development 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-12 00:00
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 as a method for assigning delegates, without mentioning Linux or cross-platform alternatives. Windows tools and patterns (e.g., PowerShell, Teams Client) are mentioned exclusively or first, and there are no examples or guidance for Linux users. The SDK support table lists 'Windows' as a platform, but does not mention Linux or provide parity. No Linux-specific instructions or examples are provided.
Recommendations
  • Include Linux-compatible methods for assigning delegates, such as using Microsoft Graph API or cross-platform CLI tools.
  • Provide explicit Linux examples or instructions alongside PowerShell/Windows steps.
  • Clarify SDK/platform support for Linux and add relevant documentation if available.
  • Avoid referencing Windows tools exclusively; mention alternatives or note platform limitations.
  • Add a section addressing cross-platform usage and considerations for Linux administrators.
GitHub Create Pull Request
Communication Services include file ...tion-services/quickstarts/chat/includes/chat-csharp.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows tools (Visual Studio) as a prerequisite without mentioning Linux alternatives, using PowerShell for package installation, and referencing Windows console environments (cmd, PowerShell) before Bash. There are no explicit Linux instructions or examples for installing dependencies or running the sample, and the development workflow assumes a Windows-centric environment.
Recommendations
  • Include Linux development environment options in prerequisites, such as VS Code or JetBrains Rider.
  • Provide explicit Bash and Linux shell examples for package installation (e.g., use 'dotnet add package' in Bash, not PowerShell).
  • List Bash and Linux terminal environments before or alongside Windows ones when giving instructions.
  • Clarify that the .NET CLI commands work cross-platform and provide troubleshooting tips for Linux users.
  • Mention Linux-specific requirements or dependencies if any (e.g., mono, .NET SDK installation on Linux).
  • Add links to Linux setup guides for .NET and Azure CLI.
GitHub Create Pull Request
Communication Services Create a Communication Services resource in Azure Communication Services ...-services/quickstarts/create-communication-resource.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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-specific instructions and tools (e.g., PowerShell, setx, app.config/web.config) are presented first or exclusively in several sections. The Azure CLI installation link defaults to Windows, and examples use PowerShell syntax. Linux and macOS instructions are present but are secondary, and some configuration file references (app.config/web.config) are Windows/.NET-centric.
Recommendations
  • Present platform instructions in parallel or randomized order, rather than always listing Windows first.
  • Include Linux/macOS equivalents for all configuration and tooling examples (e.g., mention .env files, systemd environment files, or other common Linux patterns for storing secrets).
  • Provide links to Azure CLI installation for all platforms, not just Windows.
  • Balance SDK examples by including samples for Python, Java, or Node.js, which are popular on Linux/macOS.
  • When referencing configuration files, mention cross-platform alternatives (e.g., .env, environment variables, secrets managers) alongside Windows-specific files.
  • Avoid PowerShell-specific syntax in CLI examples unless explicitly in a PowerShell section; use bash/zsh syntax for Linux/macOS sections.
GitHub Create Pull Request
Communication Services Add custom verified email domains ...vices/quickstarts/email/add-custom-verified-domains.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways. PowerShell is given its own dedicated section, and the only DNS management guide for 'Other (General)' links to a Windows-based DNS guide, with no mention of Linux-based DNS servers (e.g., BIND). There are no explicit Linux command-line examples or references to Linux-native tools for DNS management. The ordering of pivots and examples tends to favor Windows technologies and tools, with Windows/PowerShell options listed before Linux alternatives or not at all.
Recommendations
  • Add explicit Linux/BIND DNS management instructions and links for users managing their own DNS on Linux servers.
  • Include Linux shell (bash) examples for relevant Azure CLI commands, clarifying cross-platform usage.
  • Provide parity in documentation for Linux-native tools (e.g., dig, nsupdate) alongside Windows/PowerShell examples.
  • Ensure that 'Other (General)' DNS instructions include both Windows and Linux server scenarios.
  • Review ordering of pivots and examples to avoid implicit prioritization of Windows tools.
GitHub Create Pull Request
Communication Services Create and manage Email Communication Service resource in Azure Communication Services ...ickstarts/email/create-email-communication-resource.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by including PowerShell as a primary platform pivot, listing it alongside Azure portal, .NET, and Azure CLI. PowerShell is a Windows-centric tool, and its inclusion as a first-class example suggests prioritization of Windows workflows. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash), nor are there examples tailored for Linux users. The documentation does not clarify cross-platform compatibility for the .NET or Azure CLI instructions, and the ordering of pivots places PowerShell before any Linux-specific alternatives.
Recommendations
  • Add explicit Bash or Linux shell examples where applicable, especially for resource management via Azure CLI.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide platform-specific notes if there are differences.
  • Include instructions or pivots for Linux-native tools or environments, such as Bash scripts or references to Linux package managers.
  • Reorder platform pivots to avoid implicit prioritization of Windows tools (e.g., list Azure CLI before PowerShell).
  • Add a section or note on cross-platform compatibility for all management options, ensuring Linux users are equally supported.
GitHub Create Pull Request
Communication Services Prerequisites ...es/create-custom-managed-domain-resource-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 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 using Azure CLI, Bash, or cross-platform scripting. The documentation assumes a Windows environment and does not mention alternative tools or workflows available on Linux or macOS.
Recommendations
  • Provide equivalent Azure CLI examples for all resource management operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Add a 'Platform compatibility' note clarifying that PowerShell Core is available on Linux and macOS, but also recommend Azure CLI for non-Windows users.
  • Reorder sections or provide parallel instructions so that Linux/macOS tools (Azure CLI, Bash) are presented alongside or before Windows-specific tools.
  • Include installation instructions for Azure CLI and/or PowerShell Core on Linux/macOS.
  • Explicitly mention that all operations can be performed from any OS using Azure CLI, and link to relevant CLI documentation.
GitHub Create Pull Request
Communication Services include file ...send-email-smtp/includes/send-email-smtp-smtpclient.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows-specific console environments (cmd, PowerShell) before Bash when describing where to run commands. All code examples use C#/.NET, which is cross-platform but traditionally associated with Windows. There are no explicit Linux or macOS-specific instructions, troubleshooting, or examples, and no mention of platform-specific issues or alternatives. The documentation does not provide parity for Linux users in terms of environment setup, command-line usage, or platform-specific notes.
Recommendations
  • List Bash or Linux terminal first or equally when describing where to run commands.
  • Add explicit instructions or troubleshooting notes for Linux/macOS users (e.g., package installation, permissions, firewall settings).
  • Include example commands for Linux/macOS environments, such as using terminal commands to install .NET or run the application.
  • Mention any platform-specific caveats, such as differences in handling SSL certificates or environment variables.
  • Clarify that .NET Core and SmtpClient are cross-platform and provide links to Linux/macOS documentation where relevant.
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-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 provides examples for sending email via SMTP using SmtpClient (typically .NET, often Windows-centric) and Windows PowerShell, but does not include Linux-specific tools or examples (such as using sendmail, mailx, or Python scripts on Linux). The inclusion of 'Windows Powershell' as a dedicated section and the absence of Linux command-line or scripting alternatives demonstrates a bias towards Windows environments.
Recommendations
  • Add examples using common Linux tools (e.g., sendmail, mailx, swaks) for sending email via SMTP.
  • Include a Python example that works cross-platform, with installation instructions for Linux.
  • Provide guidance for configuring SMTP on Linux systems, including authentication and TLS.
  • Ensure that examples and instructions are clearly labeled for both Windows and Linux users.
  • Consider adding a section comparing Windows and Linux approaches, highlighting platform-specific nuances.
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 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 examples or guidance for sending email via SMTP from Linux or macOS environments, nor are cross-platform tools (such as curl, swaks, or Python scripts) mentioned. The documentation assumes the user is on Windows and familiar with Windows-specific tooling.
Recommendations
  • Add equivalent SMTP email sending examples for Linux and macOS, using tools such as swaks, curl, or Python's smtplib.
  • Include instructions for storing credentials securely on non-Windows platforms.
  • Present cross-platform examples side-by-side, or clearly indicate platform-specific sections.
  • Mention alternative tools and approaches for users who do not have access to PowerShell or prefer open-source solutions.
GitHub Create Pull Request
Communication Services Prerequisites ...rts/email/includes/create-email-resource-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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell commands and examples, which are native to Windows. There is no mention of equivalent Azure CLI or Bash commands, nor any guidance for Linux or macOS users. The prerequisites and instructions assume the use of Windows tools and patterns, creating a strong Windows bias.
Recommendations
  • Add Azure CLI examples alongside PowerShell commands for all operations (resource creation, management, deletion).
  • Include installation instructions for Azure CLI and note cross-platform compatibility.
  • Explicitly mention that Azure CLI and Bash can be used on Linux and macOS, and provide sample commands.
  • Reorder sections or add notes to clarify that both PowerShell and CLI approaches are supported and provide parity.
  • Consider adding a table comparing PowerShell and CLI commands for common tasks.
GitHub Create Pull Request
Communication Services Prerequisites ...includes/create-sender-username-resource-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 uses PowerShell commands and references the Azure Az PowerShell Module, which is primarily associated with Windows environments. There are no examples or instructions for Linux users (e.g., Bash, Azure CLI), and Windows-centric tools and patterns are mentioned without Linux equivalents. This creates a bias towards Windows and may hinder Linux users from following the guide.
Recommendations
  • Provide equivalent Azure CLI examples for all operations (login, resource creation, management, deletion).
  • Explicitly mention cross-platform compatibility of Azure PowerShell, or clarify if steps are Windows-only.
  • Add instructions for installing and using Azure CLI on Linux/macOS.
  • Reorder prerequisites and examples to present cross-platform tools (e.g., Azure CLI) before or alongside PowerShell.
  • Include notes or links for Linux/macOS users to ensure parity and accessibility.
GitHub Create Pull Request
Communication Services include file ...uickstarts/email/includes/send-email-async-sync-net.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 Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific console environments (cmd, PowerShell) before mentioning Bash, and by providing only .NET/C# examples and commands. There are no Linux-specific instructions, examples, or troubleshooting notes, and no mention of Linux package managers or shell environments beyond a brief mention of Bash. All code samples and tooling instructions assume a Windows/.NET development environment.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms for .NET Core and Azure Communication Services Email SDK.
  • Provide Linux-specific instructions for installing .NET Core (e.g., using apt, yum, or Homebrew).
  • Include example commands for Bash and other Linux shells, and clarify any differences in environment variable setup or file paths.
  • Add troubleshooting notes for common Linux issues (e.g., permissions, firewall, dependency installation).
  • Reference cross-platform editors (e.g., VS Code) and clarify that the steps work on Linux and macOS as well as Windows.
  • Ensure parity in sample code and instructions for running and building the application on Linux/macOS terminals.
GitHub Create Pull Request
Communication Services include file ...es/quickstarts/email/includes/send-email-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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses Azure PowerShell for all examples and instructions, with explicit references to running commands in 'windows PowerShell'. There are no examples or guidance for Linux or cross-platform alternatives (such as Azure CLI or REST API). The installation instructions and code samples are all tailored to Windows/PowerShell users, and there is no mention of Linux-compatible tools or workflows.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux and macOS, and provide installation instructions for those platforms.
  • Include REST API or SDK (e.g., Python, Node.js) examples for sending emails, to support users on non-Windows platforms.
  • Rephrase instructions to avoid assuming a Windows environment (e.g., say 'in your terminal' instead of 'in a windows PowerShell').
  • Provide guidance on checking module installation and running commands on Linux/macOS terminals.
GitHub Create Pull Request
Communication Services include file ...arts/email/send-email-advanced/includes/prepend-net.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific consoles (cmd, PowerShell) before mentioning Bash, and by not providing any Linux-specific instructions or examples. All command-line instructions use the generic 'dotnet' CLI, but there are no explicit Linux shell or environment setup examples. The Azure portal is referenced for resource management, but no mention is made of CLI alternatives (such as Azure CLI) that are popular on Linux. There are no examples of Linux-specific patterns, nor guidance for Linux users regarding environment variables or file paths.
Recommendations
  • Explicitly mention Linux and macOS support in the prerequisites and instructions.
  • Provide example commands for Linux shells (e.g., Bash, zsh) alongside Windows (cmd, PowerShell).
  • Include guidance for setting environment variables on Linux (e.g., export COMMUNICATION_SERVICES_CONNECTION_STRING=...) and macOS.
  • Reference Azure CLI or other cross-platform tools for resource management as alternatives to the Azure portal.
  • Ensure file paths and editor instructions are platform-neutral or provide platform-specific notes.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, .NET installation differences).
GitHub Create Pull Request
Communication Services include file ...-services/quickstarts/email/includes/send-email-net.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 Powershell Heavy
Summary
The documentation page demonstrates a bias towards Windows environments and tooling. All code examples and instructions use C#/.NET, with commands such as dotnet new, dotnet build, dotnet add package, and dotnet run. Console references include 'cmd', 'PowerShell', and 'Bash', but no Linux-specific instructions, troubleshooting, or environment setup are provided. There are no Linux or cross-platform code samples, nor are there references to Linux package managers or shell environments beyond generic mentions. The documentation assumes familiarity with Windows development patterns and does not address Linux-specific nuances.
Recommendations
  • Add explicit Linux instructions for installing .NET Core and running the sample, including package manager commands (e.g., apt, yum, zypper).
  • Provide troubleshooting steps for common Linux issues (e.g., permissions, environment variables).
  • Include sample code or terminal output from a Linux shell (e.g., bash/zsh) to demonstrate parity.
  • Mention cross-platform editors (e.g., VS Code, Vim) and how to open/edit Program.cs on Linux.
  • Clarify that the .NET SDK and Azure Communication Services Email client library are cross-platform and provide links to Linux-specific documentation.
  • Add a section on running the sample in containers or on WSL for Windows users who want a Linux-like environment.
GitHub Create Pull Request
Communication Services include file ...ail-advanced/includes/inline-attachments-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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses Windows PowerShell for all examples and instructions, including installation and usage of the Azure Communication Services module. There is no mention of Linux, macOS, or cross-platform alternatives such as Azure CLI, Bash, or PowerShell Core. The prerequisite check and module installation steps are Windows/PowerShell-specific, and all code samples use PowerShell syntax. No Linux-specific tools, commands, or instructions are provided.
Recommendations
  • Add equivalent instructions and examples for Linux and macOS users, such as using PowerShell Core (pwsh) or Azure CLI.
  • Clarify that Azure PowerShell can be used cross-platform and provide installation steps for Linux and macOS.
  • Include Bash or Azure CLI examples for sending emails, if supported.
  • Update prerequisite checks to include Linux/macOS environments, e.g., checking module installation in PowerShell Core or Azure CLI.
  • Explicitly mention platform compatibility and provide guidance for non-Windows users.
GitHub Create Pull Request
Communication Services Send email with inline attachments ...d-email-advanced/send-email-with-inline-attachments.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides examples for multiple programming languages and tools, including Azure CLI and PowerShell. However, the inclusion of PowerShell as a distinct pivot and the absence of explicit Linux shell (bash) examples or references to Linux-native tools (such as bash scripts or shell commands) indicates a bias towards Windows environments. PowerShell is primarily associated with Windows, and its presence without a corresponding bash or Linux shell example suggests a Windows-first approach. Additionally, there are no troubleshooting or resource management instructions tailored for Linux users.
Recommendations
  • Add explicit bash or Linux shell examples alongside PowerShell, especially for command-line operations.
  • Include troubleshooting steps or resource management instructions relevant to Linux environments.
  • Ensure that references to command-line tools are balanced between Windows and Linux, mentioning both PowerShell and bash where appropriate.
  • Consider adding a 'programming-language-bash' or 'programming-language-linux-shell' pivot for parity.
  • Review and update any instructions or notes that assume a Windows environment to be more platform-neutral.
GitHub Create Pull Request
Communication Services Prerequisites ...vents/includes/create-event-subscription-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 page exclusively uses Azure PowerShell commands and modules for all examples and instructions, with no mention of Azure CLI, Bash, or Linux-native tools. The prerequisites and step-by-step guides assume PowerShell usage, which is most common on Windows. There are no Linux or cross-platform alternatives provided, and the documentation does not acknowledge non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for all operations (create, list, update, delete event subscriptions).
  • Include installation instructions for Azure CLI and note its cross-platform compatibility.
  • Explicitly mention that PowerShell is available on Linux and macOS, but provide Bash/CLI examples for users who prefer native Linux tools.
  • Reorder or parallelize examples so that Windows and Linux instructions are presented side-by-side or in separate tabs.
  • Reference documentation for both PowerShell and CLI tools in the 'Next steps' section.
GitHub Create Pull Request
Communication Services Subscribe to events ...ion-services/quickstarts/events/subscribe-to-events.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a primary method for subscribing to events, referencing Windows-centric tools (PowerShell, .NET SDK), and omitting explicit Linux shell examples. The Azure CLI is mentioned, but there is no clear parity in examples or guidance for Linux users, and the .NET SDK reference further reinforces a Windows-centric approach.
Recommendations
  • Add explicit Bash or Linux shell examples alongside PowerShell, especially in code snippets and step-by-step instructions.
  • Mention cross-platform compatibility for Azure CLI and .NET SDK, and provide guidance for using these tools on Linux and macOS.
  • Include references to other SDKs (e.g., Python, JavaScript) that are commonly used on Linux.
  • Reorder sections so that platform-neutral or Linux-friendly tools (like Azure CLI) are presented before Windows-specific tools (like PowerShell).
  • Clarify that PowerShell Core is cross-platform if recommending PowerShell, and provide installation instructions for Linux.
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 typically used on Windows. There are no examples or instructions for Linux or cross-platform tools such as Azure CLI, and no mention of alternatives for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI commands for registering and checking the status of the Event Grid resource provider, as Azure CLI is cross-platform and commonly used on Linux and macOS.
  • Include a note clarifying that PowerShell examples are for Windows users and provide guidance for users on other operating systems.
  • Consider reordering examples to present cross-platform tools (e.g., Azure CLI) before platform-specific ones (e.g., PowerShell) to avoid implicit prioritization of Windows.
  • Explicitly mention the availability of Azure CLI and provide installation links for users on Linux and macOS.
GitHub Create Pull Request
Communication Services Prerequisites ...ces/quickstarts/includes/create-resource-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 page exclusively uses PowerShell commands and Windows-centric tooling (Az PowerShell Module) for all examples and instructions. There are no Linux or cross-platform CLI examples (such as Azure CLI), nor is there mention of how to perform these tasks on Linux or macOS. The documentation assumes the use of PowerShell and Windows tools, which may not be available or preferred on non-Windows platforms.
Recommendations
  • Provide equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include installation instructions for Azure CLI and/or Az PowerShell on Linux and macOS, or link to relevant documentation.
  • Clearly indicate which commands and modules are Windows-specific and suggest alternatives for other platforms.
  • Reorder or balance examples so that Linux/macOS options are presented alongside or before Windows/PowerShell examples.
  • Add a section discussing platform compatibility and best practices for users on non-Windows systems.
GitHub Create Pull Request
Communication Services Set up and obtain access tokens for Microsoft Entra ID users ...ntity/microsoft-entra-id-authentication-integration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through its exclusive mention of Windows-centric tools (Azure portal, Microsoft Entra admin center) and patterns. While the Azure CLI is referenced (which is cross-platform), there are no explicit Linux-specific instructions, examples, or screenshots. The documentation assumes use of the Azure portal and admin center, which are web-based but often presented with a Windows-centric UI. There is no mention of Linux shell commands, environment setup, or alternative workflows for Linux users. No PowerShell examples are present, but the overall flow and tooling are Windows-oriented.
Recommendations
  • Add explicit Linux shell examples for relevant CLI commands, including environment setup and authentication.
  • Include notes or screenshots showing the Azure portal and admin center on Linux browsers to clarify cross-platform compatibility.
  • Mention that Azure CLI is cross-platform and provide troubleshooting tips for Linux users (e.g., installation, authentication).
  • If any steps can be performed via REST API or automation, provide curl/bash examples alongside Azure CLI.
  • Clarify that all steps can be performed on Linux and MacOS as well as Windows, and highlight any platform-specific caveats.
GitHub Create Pull Request
Communication Services include file ...ion-services/quickstarts/sms/includes/send-sms-java.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides command-line examples for both Command Prompt and PowerShell, which are Windows-specific shells, but does not provide any explicit Linux or macOS shell examples (e.g., Bash). The order of presentation is Windows-first, and there are no references to Linux tools, shells, or platform-specific instructions for non-Windows users.
Recommendations
  • Add Bash (Linux/macOS) command examples alongside Command Prompt and PowerShell examples for all CLI instructions.
  • Explicitly mention support for Linux/macOS platforms in the prerequisites and setup sections.
  • Include notes or sections on platform differences, such as file paths and shell syntax, where relevant.
  • Ensure parity in troubleshooting and environment setup instructions for Linux/macOS users.
GitHub Create Pull Request
← Previous Page 2 of 27 Next →