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 101-125 of 656 flagged pages
Communication Services include file ...ludes/email-resource-management-azurecli-powershell.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based automation examples and instructions. All code samples use PowerShell syntax and constructs (e.g., Write-Host, try/catch, functions, variable assignment), which are native to Windows and not directly usable 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 provided. This limits accessibility for users on Linux or macOS, who would need to translate the logic to Bash or another shell.
Recommendations
  • Provide equivalent Bash shell scripts for all automation steps, using standard Bash syntax and constructs (e.g., echo, if/else, functions, error handling).
  • Include Linux/macOS installation instructions and links for Azure CLI and PowerShell, not just Windows.
  • Clearly indicate which examples are for Windows/PowerShell and which are for Linux/Bash, ideally presenting both side by side.
  • Avoid using PowerShell-specific constructs in generic Azure CLI examples; use plain CLI commands where possible.
  • Add a section explaining cross-platform compatibility and how users can adapt scripts for their OS.
GitHub Create Pull Request
Communication Services include file ...nication-services/samples/includes/web-calling-hero.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows-specific terminals (PowerShell, Windows Terminal, Command Prompt) first and exclusively in the instructions for cloning the repository, without mentioning Linux or macOS equivalents (e.g., Bash, Terminal). There are no explicit Linux/macOS examples or instructions, and the troubleshooting and setup steps do not address cross-platform differences. The use of PowerShell as the default example further reinforces the Windows-centric approach.
Recommendations
  • Explicitly mention Linux/macOS terminals (e.g., Bash, Terminal, zsh) alongside Windows terminals in setup instructions.
  • Provide Linux/macOS-specific examples or notes where commands or file paths may differ.
  • Include troubleshooting steps relevant to Linux/macOS environments.
  • Clarify that the instructions are cross-platform where applicable, or provide platform-specific sections if needed.
GitHub Create Pull Request
Communication Services Tutorial - Prepare a web app for Azure Communication Services (Node.js) ...communication-services/tutorials/building-app-start.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways. Node.js, nvm, and npm installation instructions and links are Windows-specific, with explicit reference to a Windows tutorial and PowerShell commands for nvm usage. There are no Linux or macOS equivalents provided for these steps, nor are cross-platform installation instructions or terminal commands shown. Folder creation examples use Windows paths (e.g., C:\Users\Documents\ACS\CallingApp), and screenshots and workflow descriptions assume a Windows environment. Linux and macOS users are not given guidance for their platforms, which may hinder their onboarding experience.
Recommendations
  • Provide equivalent installation instructions for Node.js, nvm, and npm for Linux and macOS, including appropriate shell commands (bash/zsh) and links to official documentation for those platforms.
  • Include examples of folder creation and file paths using Linux/macOS conventions (e.g., ~/ACS/CallingApp) alongside Windows examples.
  • When showing terminal commands, use generic shell prompts (e.g., $) or provide both PowerShell and bash/zsh versions where relevant.
  • Add screenshots or workflow notes for Visual Studio Code usage on Linux/macOS, or clarify that the steps are cross-platform.
  • Avoid referencing only Windows-specific documentation or tools; ensure parity by mentioning and linking to Linux/macOS resources as well.
GitHub Create Pull Request
Communication Services Migrating from Twilio Conversations Chat to Azure Communication Services Chat C# ...orials/includes/twilio-to-acs-chat-android-tutorial.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by requiring Visual Studio as a prerequisite, using PowerShell for package installation, and omitting Linux or cross-platform alternatives. The initial setup and tooling instructions are Windows-centric, and there are no explicit mentions or examples for Linux users.
Recommendations
  • List cross-platform IDEs (e.g., Visual Studio Code, JetBrains Rider) or .NET CLI as alternatives to Visual Studio in prerequisites.
  • Provide Linux/macOS equivalents for package installation commands (e.g., 'dotnet add package' in a generic shell, not PowerShell).
  • Explicitly state that the SDK and examples work on Linux/macOS if applicable, and mention any platform-specific considerations.
  • Include instructions for installing .NET SDK on Linux/macOS, or link to official .NET cross-platform installation guides.
  • Avoid using PowerShell-specific syntax or, if used, provide equivalent Bash/zsh commands.
GitHub Create Pull Request
Communication Services Migrating from Twilio Conversations Chat to Azure Communication Services Chat C# ...torials/includes/twilio-to-acs-chat-csharp-tutorial.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by requiring Visual Studio (a Windows-centric IDE) as a prerequisite, providing installation instructions using PowerShell (dotnet add package), and omitting any Linux-specific development environment guidance or CLI alternatives. There are no examples or notes for Linux or cross-platform development, and the only command-line example (dotnet add package) is shown in PowerShell syntax. The documentation assumes a Windows development environment throughout.
Recommendations
  • Add explicit instructions for Linux and macOS users, such as recommending VS Code or JetBrains Rider as alternatives to Visual Studio.
  • Provide package installation commands using generic shell syntax (e.g., bash) or clarify that 'dotnet add package' works cross-platform.
  • Include notes or sections on setting up the development environment on Linux (e.g., installing .NET SDK, using CLI editors).
  • Avoid assuming PowerShell as the default shell; show both PowerShell and bash/zsh equivalents where relevant.
  • Mention that Azure CLI and .NET SDK are cross-platform, and provide links or instructions for installation on Linux/macOS.
  • Review all code snippets and instructions to ensure they are not Windows-specific and clarify any platform dependencies.
GitHub Create Pull Request
Communication Services What's new in Azure Communication Services ...blob/main/articles/communication-services/whats-new.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows is mentioned explicitly as a supported platform before Linux or macOS in several SDK feature announcements (e.g., 'Calling SDKs for Android, iOS, and Windows'), and Windows is listed as a target for native apps and features. There are no explicit Linux or macOS examples, nor are Linux-specific tools or patterns referenced. Windows-centric terminology (e.g., 'Teams client', 'Power BI', 'Windows calling SDK') is used, and there is a lack of parity in code samples or platform-specific instructions for Linux users.
Recommendations
  • Include explicit references to Linux and macOS support wherever SDK/platform support is listed, not just Windows.
  • Provide Linux/macOS-specific examples or instructions, especially for SDK usage, deployment, and troubleshooting.
  • When listing supported platforms, avoid listing Windows first unless it is genuinely the only supported platform; use alphabetical order or group by mobile/desktop.
  • Add parity in code samples, showing how to use SDKs and APIs on Linux (e.g., with .NET Core, Node.js, or Python on Linux).
  • Reference Linux-compatible tools for analytics and troubleshooting (e.g., alternatives to Power BI, or instructions for using Azure portal/logs on Linux).
  • Clarify any platform limitations or differences, so Linux developers know what is or isn't supported.
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 page exclusively provides PowerShell-based instructions and examples for sending email via SMTP with Azure Communication Services. It references Windows-specific tools (Send-MailMessage, PSCredential) and does not mention or provide any equivalent Linux or cross-platform methods (such as using 'sendmail', 'mailx', 'swaks', or Python scripts). This creates a clear bias towards Windows environments and leaves Linux users without guidance.
Recommendations
  • Add Linux-compatible examples using common command-line tools (e.g., 'sendmail', 'mailx', 'swaks') or scripting languages (e.g., Python's smtplib).
  • Explicitly mention cross-platform alternatives and provide step-by-step instructions for both Windows and Linux users.
  • Include a note clarifying that PowerShell is available on Linux, but also provide native Linux tool examples for users who prefer them.
  • Structure the documentation so that Windows and Linux instructions are presented in parallel, or at least make it clear that both platforms are supported.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides explicit pivots for PowerShell and Azure CLI, but PowerShell is a Windows-centric tool and is listed as a primary example. There is no mention of Linux-specific shell examples (e.g., bash), and the troubleshooting and resource cleanup sections do not reference Linux command-line tools or patterns. The documentation implicitly prioritizes Windows tooling by including PowerShell as a main pivot and omitting Linux-native equivalents.
Recommendations
  • Add bash or shell script examples alongside PowerShell, especially for resource cleanup and automation tasks.
  • Explicitly mention Linux compatibility for Azure CLI commands and provide any necessary Linux-specific notes.
  • Ensure troubleshooting steps reference both Windows and Linux environments, including common Linux tools (e.g., curl, grep) for diagnostics.
  • Balance the order of pivots so that Windows and Linux tools/examples are presented with equal prominence.
  • Clarify cross-platform support for SDKs and command-line tools in introductory sections.
GitHub Create Pull Request
Communication Services include file ...send-email-smtp/includes/send-email-smtp-smtpclient.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 page demonstrates a Windows bias by listing Windows-specific consoles (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 Linux-specific instructions, troubleshooting tips, or examples (e.g., using Linux mail tools or .NET on Linux). The documentation does not mention Linux-specific considerations for .NET or SMTP usage.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms for .NET and Azure Communication Services.
  • Provide Linux/macOS-specific instructions for installing .NET Core, including package manager commands (e.g., apt, yum, brew).
  • Include example terminal commands using Bash and clarify that all commands work on Linux/macOS as well as Windows.
  • Add troubleshooting notes for common Linux-specific issues (e.g., firewall, SSL/TLS, permissions).
  • Consider including alternative code examples using platform-agnostic tools (e.g., Python's smtplib, sendmail) to demonstrate SMTP usage outside of .NET.
GitHub Create Pull Request
Communication Services Send email with SMTP and XOAuth2 using .NET ...kstarts/email/send-email-smtp/send-email-smtp-oauth.md
High Priority View Details →
Scanned: 2026-01-10 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 consoles (cmd, PowerShell) before Bash when suggesting where to run commands, and does not provide any Linux-specific instructions or examples. All terminal commands are generic, but there is no mention of Linux package managers or environment setup, nor are there troubleshooting notes for Linux users. The documentation assumes a Windows-centric workflow and omits Linux-specific considerations.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms in the prerequisites and instructions.
  • Provide Linux-specific setup instructions, such as using the terminal, installing .NET Core via apt/yum/brew, and any required dependencies.
  • Include troubleshooting notes for common Linux issues (e.g., permissions, firewall, package installation).
  • List Bash first or equally with cmd/PowerShell when referencing console windows.
  • Clarify that the instructions and code samples are cross-platform, and highlight any platform-specific differences.
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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides SMTP email sending examples using SmtpClient (typically .NET, often Windows-centric) and Windows PowerShell, but lacks Linux-specific examples or references to Linux tools (such as sendmail, mailx, or command-line SMTP clients). Windows tools and patterns are mentioned exclusively, and Linux alternatives are not addressed.
Recommendations
  • Add examples using Linux command-line tools (e.g., sendmail, mailx, swaks) for sending SMTP emails.
  • Include sample scripts for Linux shell environments (bash, sh) to demonstrate parity with PowerShell examples.
  • Explicitly mention cross-platform .NET usage, clarifying if SmtpClient works on Linux and how to configure it.
  • Provide guidance for configuring SMTP on Linux systems, including any required dependencies or setup steps.
  • Ensure that documentation sections for Linux are as detailed and prominent as those for Windows.
GitHub Create Pull Request
Communication Services Prerequisites ...vents/includes/create-event-subscription-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 page exclusively uses Azure PowerShell commands and modules for all examples and instructions, which are traditionally associated with Windows environments. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or other cross-platform tools. The prerequisites and all operational steps assume PowerShell usage, which may not be the default or preferred option for Linux or macOS users.
Recommendations
  • Add equivalent Azure CLI examples for all operations (create, list, update, delete event subscriptions).
  • Include installation instructions for Azure CLI alongside PowerShell, especially in the prerequisites.
  • Clarify that PowerShell is available cross-platform, but also provide Bash/CLI alternatives for Linux/macOS users.
  • Where possible, link to both PowerShell and CLI documentation for relevant commands.
  • Consider reordering or balancing examples so that neither Windows nor Linux is presented as the default or primary platform.
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 Azure CLI or Bash equivalents. This presents a clear Windows bias and may hinder users on other platforms.
Recommendations
  • Add equivalent Azure CLI commands for registering and checking the status of the Event Grid Resource Provider.
  • Include Bash shell examples for Linux/macOS users.
  • Present cross-platform instructions first, or side-by-side, rather than only PowerShell.
  • Explicitly mention platform compatibility for each command example.
GitHub Create Pull Request
Communication Services Subscribe to events ...ion-services/quickstarts/events/subscribe-to-events.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 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prominently featuring PowerShell as a primary method for subscribing to events, which is traditionally associated with Windows. The inclusion of PowerShell examples and references, without explicit mention of Linux shell equivalents (such as Bash), and the lack of Linux-specific instructions or examples, suggests a preference for Windows tools and workflows. The page also lists PowerShell before other cross-platform options, reinforcing a 'Windows-first' approach.
Recommendations
  • Add explicit Bash or shell script examples alongside PowerShell to ensure Linux users have parity.
  • Clarify that Azure CLI commands work cross-platform and provide Linux-specific usage notes where relevant.
  • Include instructions for using the .NET SDK on Linux, or mention other SDKs/languages popular on Linux.
  • Reorder examples so that cross-platform tools (Azure CLI, SDKs) are presented before Windows-specific tools like PowerShell.
  • Add a note or section highlighting Linux compatibility and any platform-specific considerations.
GitHub Create Pull Request
Communication Services Overview ...ity/includes/active-directory/service-principal-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 demonstrates a subtle Windows bias by listing Windows terminals (Command Prompt, PowerShell) before Bash when instructing users to open a terminal. There are no explicit Linux-specific instructions, troubleshooting tips, or alternative package management notes. All command-line examples use .NET CLI, which is cross-platform, but the documentation does not clarify Linux-specific nuances (e.g., permissions, environment variables, or differences in running C# apps on Linux). No Linux-exclusive tools or patterns are mentioned.
Recommendations
  • List Bash (or Linux terminal) first when suggesting terminal options, or mention Linux and macOS terminals explicitly.
  • Add notes about running .NET applications on Linux, such as prerequisites (e.g., installing .NET SDK on Ubuntu), file permissions, and environment variable configuration.
  • Include troubleshooting tips for common Linux issues (e.g., file execution permissions, dependency installation).
  • Provide explicit instructions or links for installing .NET SDK on Linux and macOS.
  • Clarify that the .NET CLI commands are cross-platform and provide assurance/examples for Linux users.
GitHub Create Pull Request
Communication Services Automate email resource management ...nication-services/samples/email-resource-management.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 page demonstrates a strong Windows bias by prioritizing PowerShell examples and commands, referencing Windows-centric tools, and omitting equivalent Linux/bash examples. The cleanup section provides PowerShell commands for resource deletion without offering bash or Azure CLI alternatives, and the platform pivots are Windows-first (PowerShell, Azure CLI PowerShell) before mentioning Python. There is no explicit guidance for Linux users or parity in example coverage.
Recommendations
  • Add bash/Azure CLI examples for all resource management and cleanup tasks, especially for resource and domain deletion.
  • Ensure that platform pivots include Linux/bash options and are presented with equal prominence as PowerShell/Windows options.
  • Where PowerShell commands are given, provide equivalent Azure CLI or bash commands side-by-side.
  • Explicitly mention Linux support and provide instructions for Linux users, including installation and usage notes for Azure CLI.
  • Review included files (e.g., email-resource-management-powershell.md) to ensure Linux parity in all walkthroughs and code samples.
GitHub Create Pull Request
Communication Services Include file ...es/samples/includes/call-automation-azure-openai-js.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 demonstrates a Windows bias by referencing PowerShell and Windows terminal first when describing how to run commands, and by instructing users to open PowerShell specifically for running the sample. There are no explicit examples or instructions for Linux or macOS terminals, and the language assumes familiarity with Windows tools and patterns. Linux and macOS equivalents are mentioned only as 'the equivalent', without concrete guidance.
Recommendations
  • Explicitly mention Linux and macOS terminals (e.g., Bash, Terminal.app) alongside PowerShell and Windows terminal.
  • Provide command examples that work on Linux/macOS, and clarify any differences in environment setup or command usage.
  • Avoid referencing PowerShell or Windows terminal first; use neutral language such as 'Open your terminal (PowerShell, Command Prompt, Bash, or Terminal.app)'.
  • Add a note or section for platform-specific instructions if any steps differ between Windows and Linux/macOS.
  • Ensure all referenced quickstart links and instructions include Linux/macOS tabs or pivots, not just Windows.
GitHub Create Pull Request
Communication Services include file ...mples/includes/email-resource-management-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 is heavily focused on Windows and PowerShell. All examples and automation scripts use Azure PowerShell cmdlets, with instructions referencing 'command prompt' and PowerShell-specific commands. There are no examples or guidance for Linux users, such as using Bash, Azure CLI, or cross-platform scripting. The prerequisites and setup steps assume a Windows environment and do not mention Linux alternatives or compatibility.
Recommendations
  • Provide equivalent Azure CLI examples for all major steps (resource creation, domain management, DNS configuration, verification, linking).
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, and provide installation instructions for those platforms.
  • Add a section or callouts for Linux/macOS users, including how to run scripts in Bash or with Azure CLI.
  • Where possible, use cross-platform terminology (e.g., 'terminal' instead of 'command prompt') and avoid Windows-centric language.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., authentication, DNS tools).
  • Consider providing downloadable script bundles for both PowerShell and Bash/Azure CLI.
GitHub Create Pull Request
Communication Services include file ...nication-services/samples/includes/web-calling-hero.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 page demonstrates a Windows bias in its setup instructions: it lists Windows-specific shells (PowerShell, Windows Terminal, Command Prompt) first and exclusively in the initial setup step, without mentioning Linux or macOS equivalents (such as Bash or Terminal). No Linux/macOS-specific instructions or troubleshooting are provided, and the tooling references (Visual Studio Code) are cross-platform but the shell examples are not. There are no explicit Linux or macOS command-line examples or environment notes.
Recommendations
  • Explicitly mention Linux and macOS terminals (e.g., Bash, Terminal) alongside Windows shells in setup instructions.
  • Add notes or examples for Linux/macOS users, such as confirming that the git and Azure CLI commands work identically on those platforms.
  • Include troubleshooting steps or environment notes for Linux/macOS, especially regarding HTTPS serving and port usage.
  • Consider adding a section or callout for cross-platform compatibility, clarifying any OS-specific differences in running or deploying the sample.
GitHub Create Pull Request
Communication Services Enable interoperability with Teams ...ices/concepts/interop/enable-interoperability-teams.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 only PowerShell cmdlets (Set-CsPhoneNumberAssignment) for configuration, which are primarily Windows-centric. No Linux or cross-platform alternatives are provided, and the instructions assume familiarity with Windows tooling and patterns. There is no mention of how to perform equivalent actions on Linux or macOS, nor are platform-agnostic REST API or CLI examples given.
Recommendations
  • Provide Azure CLI or REST API examples for assigning licenses and enabling Enterprise Voice, which are platform-agnostic.
  • Explicitly mention whether the PowerShell cmdlets can be run on Linux/macOS (e.g., via PowerShell Core), and provide installation instructions if so.
  • Include Linux/macOS-specific instructions or note any limitations for non-Windows users.
  • Reorder examples to present platform-neutral methods first, followed by platform-specific (Windows/PowerShell) instructions.
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-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 bias towards Windows environments by referencing Windows-centric tools (Azure portal, Microsoft Entra admin center) and providing examples using Azure CLI and Microsoft Graph REST API without clarifying Linux compatibility or offering explicit Linux shell examples. There is no mention of Linux-specific tools, nor are there instructions or screenshots for Linux users. The guidance assumes familiarity with Windows-based graphical interfaces and does not address command-line alternatives or platform differences.
Recommendations
  • Explicitly state that Azure CLI commands work cross-platform and provide example shell commands for Linux (e.g., bash).
  • Include instructions for performing key steps using Linux command-line tools where possible, such as using curl for REST API calls.
  • Add screenshots or walkthroughs for Linux users accessing the Azure portal and Microsoft Entra admin center from non-Windows environments.
  • Mention platform compatibility for SDKs and tools, clarifying any differences in setup or usage between Windows and Linux.
  • Where graphical interfaces are referenced, provide alternative command-line instructions suitable for Linux users.
GitHub Create Pull Request
Communication Services Security for communication as Teams external user ...munication-services/concepts/interop/guest/security.md
High Priority View Details →
Scanned: 2026-01-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 PowerShell and the Microsoft Teams admin center as primary tools for configuration, without mentioning Linux equivalents or cross-platform alternatives. All examples and administrative instructions are focused on Microsoft-centric (Windows) tools, with no guidance for Linux users or administrators. There is no mention of Linux-compatible management options, CLI tools, or cross-platform scripting, and the documentation assumes familiarity with Windows environments.
Recommendations
  • Include examples and instructions for managing Teams external user policies using cross-platform tools, such as Azure CLI or REST APIs, which work on Linux and macOS.
  • Explicitly mention whether administrative tasks (such as configuring policies) can be performed from Linux or macOS systems, and provide relevant guidance.
  • Add references to Linux-compatible security tools and workflows where applicable, such as using bash scripts or Linux-based management consoles.
  • Ensure that documentation does not assume the use of Windows-only tools (like PowerShell) and provides parity for users on other operating systems.
  • Provide links to platform-agnostic documentation or guides for managing Azure Communication Services and Teams security settings.
GitHub Create Pull Request
Communication Services Prerequisites ...ces/quickstarts/includes/create-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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses PowerShell commands and Windows-centric tooling (Az PowerShell Module), with no mention of Linux or cross-platform alternatives such as Azure CLI or Bash. All examples and instructions assume a Windows environment, and there are no Linux-specific notes or examples provided.
Recommendations
  • Add equivalent Azure CLI (az) commands for all resource creation and management steps, as Azure CLI is cross-platform and commonly used on Linux.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, or clarify if examples are Windows-only.
  • Provide Bash shell examples where appropriate, especially for scripting and automation tasks.
  • Include a section on installing and using Azure CLI on Linux/macOS, alongside the PowerShell instructions.
  • Ensure that documentation does not assume a Windows file path or shell prompt (e.g., 'PS C:\>'), and use generic prompts or note platform differences.
GitHub Create Pull Request
Communication Services include file ...ices/quickstarts/includes/manage-teams-identity-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 page demonstrates a Windows bias by referencing Windows-specific console environments (cmd, PowerShell) before mentioning Bash, and by omitting Linux/macOS-specific instructions or examples. All code and command-line examples use .NET CLI commands, which are cross-platform, but there are no explicit Linux/macOS terminal screenshots, environment variable setup instructions, or editor recommendations. The documentation assumes familiarity with Windows patterns and tools, and does not provide parity for Linux users.
Recommendations
  • Explicitly mention Linux/macOS environments alongside Windows (e.g., 'In a console window such as cmd, PowerShell, Terminal, or Bash...').
  • Provide Linux/macOS-specific instructions for setting environment variables (e.g., 'export AAD_CLIENT_ID=...' for Bash).
  • Include examples of opening and editing files using common Linux/macOS editors (e.g., nano, vim, VS Code).
  • Add notes or screenshots showing command execution in Linux/macOS terminals.
  • Clarify that the .NET CLI is cross-platform and provide installation links for Linux/macOS.
  • Avoid listing Windows tools first unless there is a technical reason.
GitHub Create Pull Request
Communication Services Teams controls for Teams external user ...ervices/concepts/interop/guest/teams-administration.md
High Priority View Details →
Scanned: 2026-01-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 by exclusively referencing PowerShell modules and cmdlets for configuration and policy management, and 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 approaches. The documentation assumes the use of Windows-based administration patterns and does not provide parity for Linux administrators.
Recommendations
  • Include Azure CLI or Microsoft Graph API examples for all configuration and policy management tasks, as these are cross-platform and work on Linux, macOS, and Windows.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, and provide installation guidance or links for non-Windows platforms.
  • Add Linux-specific instructions or notes where administrative actions are described, especially for tasks currently only shown with PowerShell.
  • Where possible, provide bash or shell script equivalents for common administrative actions.
  • Clarify tool availability and platform compatibility in the 'Tools' sections, noting which are Windows-only and which are cross-platform.
  • Consider reordering examples so that cross-platform or Linux-compatible methods are presented before or alongside Windows/PowerShell methods.
GitHub Create Pull Request
← Previous Page 5 of 27 Next →