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 151-175 of 367 flagged pages
Communication Services Quickstart - Make a call to Teams user from an iOS app ...ce-video-calling/includes/teams-user/teams-user-ios.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools and patterns (such as PowerShell for enabling Teams users), linking to Windows-centric deployment guides, and omitting Linux/macOS equivalents or alternatives for critical setup steps. No Linux/macOS-specific instructions or parity are provided for Teams deployment or user enablement.
Recommendations
  • Provide Linux/macOS alternatives for enabling Teams users (e.g., using Microsoft Graph API or cross-platform CLI tools instead of PowerShell).
  • Include links or instructions for Teams deployment on Linux/macOS, if available.
  • Clearly indicate which steps are Windows-only and suggest workarounds or alternatives for non-Windows users.
  • Ensure that prerequisite steps are achievable on all major platforms, or provide platform-specific guidance.
GitHub Create Pull Request
Communication Services Detect sensitive data using Azure AI ...ion-services/samples/email-detect-sensitive-content.md
Medium 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 demonstrates a Windows bias by providing Windows-specific commands (e.g., reg query for .NET check), referencing Windows terminals (cmd, PowerShell) before Bash, and omitting Linux/macOS equivalents for environment setup and verification steps. All code samples are in C#, which is cross-platform, but setup instructions and tooling references prioritize Windows environments.
Recommendations
  • Provide Linux/macOS equivalents for .NET installation and verification (e.g., use 'dotnet --list-sdks' or 'which dotnet').
  • List Bash or terminal instructions before or alongside Windows-specific ones, not after.
  • Include notes or steps for setting environment variables on Linux/macOS (e.g., export LANGUAGE_KEY=...).
  • Add troubleshooting steps for common Linux/macOS issues (e.g., permissions, path differences).
  • Clarify that all steps are cross-platform where applicable, and explicitly mention platform differences.
GitHub Create Pull Request
Communication Services Automate email resource management ...nication-services/samples/email-resource-management.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page displays a notable Windows bias. PowerShell commands are given for resource cleanup, with no equivalent Bash or Linux shell examples. The CLI examples are present but are not consistently provided for all tasks (e.g., domain deletion is only shown in PowerShell). The structure and example ordering prioritize Windows/PowerShell tools and workflows, making it less accessible for Linux/macOS users.
Recommendations
  • Provide Bash/Azure CLI examples for all resource management tasks, including domain deletion.
  • Ensure that CLI examples are shown alongside PowerShell examples, not just for some operations.
  • Clearly indicate cross-platform compatibility and usage patterns for each command.
  • Consider reordering examples so that platform-neutral or CLI commands are shown first, or side-by-side.
GitHub Create Pull Request
Communication Services include file ...ludes/email-resource-management-azurecli-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on PowerShell scripting and Windows-specific patterns. All code samples are written in PowerShell, and instructions reference Windows command prompts and PowerShell-specific commands (e.g., Write-Host, Start-Sleep, ConvertFrom-Json). Prerequisite links and checks are Windows-centric, and there are no Bash, shell, or Linux/macOS scripting equivalents provided. This creates friction for Linux/macOS users, who must adapt the logic to their own shell environments.
Recommendations
  • Provide equivalent Bash/shell script examples for Linux/macOS users, using standard shell scripting and jq for JSON parsing.
  • Add instructions for checking prerequisites (Azure CLI, authentication) on Linux/macOS, including links to non-Windows installation guides.
  • Clarify that Azure CLI commands are cross-platform and show how to use them in Bash or zsh.
  • Avoid using PowerShell-specific constructs (e.g., Write-Host, try/catch, Start-Sleep) in generic CLI automation guides, or provide alternatives.
  • Include a section or toggle for Linux/macOS users, showing how to perform each step in their environment.
GitHub Create Pull Request
Communication Services include file ...mples/includes/email-resource-management-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Azure PowerShell, with all examples and instructions provided exclusively in PowerShell syntax. The prerequisites and environment checks reference Windows tools and patterns (e.g., command prompt, PowerShell version check), and there are no equivalent instructions or examples for Linux/macOS users (such as Bash, Azure CLI, or cross-platform shell usage). This creates friction for non-Windows users, who must adapt the instructions or seek alternative tooling.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and work natively on Linux/macOS.
  • Include environment checks and installation instructions for Azure CLI and PowerShell Core (pwsh), which run on Linux/macOS.
  • Add notes or sections clarifying how Linux/macOS users can perform each step, including authentication and DNS record management.
  • Explicitly state PowerShell Core compatibility and provide guidance for running scripts on non-Windows platforms.
  • Consider reordering or parallelizing examples so Linux/macOS instructions are not secondary.
GitHub Create Pull Request
Communication Services Tutorial - Prepare a web app for Azure Communication Services (Node.js) ...communication-services/tutorials/building-app-start.md
Medium 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 exhibits a Windows bias in several areas. The instructions for installing Node.js, nvm, and npm explicitly reference a Windows-specific tutorial and provide PowerShell commands for nvm usage, with no mention of Linux or macOS equivalents. The example project folder path uses Windows-style paths (e.g., C:\Users\Documents\ACS\CallingApp), and screenshots and workflow descriptions assume a Windows environment. There are no Linux/macOS-specific instructions or terminal commands, nor are cross-platform differences discussed.
Recommendations
  • Add explicit instructions and example commands for installing Node.js, nvm, and npm on Linux and macOS, including links to official guides.
  • Provide bash/zsh shell commands alongside PowerShell commands for nvm usage.
  • Use platform-agnostic or dual examples for file paths (e.g., show both C:\Users\... and ~/ACS/CallingApp).
  • Include notes or sections highlighting any platform-specific differences or considerations.
  • Ensure screenshots and workflow descriptions are relevant for all major platforms, or clarify when steps differ.
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
Medium 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 demonstrates a Windows bias primarily through its use of PowerShell for package installation and its assumption of Visual Studio as the development environment. The installation example is given only in PowerShell, with no Linux/macOS alternative (such as bash or dotnet CLI). Visual Studio is referenced as the required IDE, which is most common on Windows. No mention is made of Linux/macOS compatible tools or workflows, and Windows-centric tools are presented first and exclusively.
Recommendations
  • Provide Linux/macOS equivalents for package installation, e.g., using 'dotnet add package' in bash or zsh.
  • Mention cross-platform IDEs such as VS Code or JetBrains Rider as alternatives to Visual Studio.
  • Clarify that Azure CLI commands work on Linux/macOS and provide shell examples where appropriate.
  • Explicitly state platform compatibility for SDKs and tools.
  • Add notes or sections for Linux/macOS setup and troubleshooting.
GitHub Create Pull Request
Communication Services What's new in Azure Communication Services ...blob/main/articles/communication-services/whats-new.md
Medium 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 frequently references Windows and Microsoft-centric platforms (Teams, Windows, Power BI, etc.) and often lists Windows as a supported platform before mentioning others. Some features and SDKs are described as available for Windows, Android, and iOS, but Linux is rarely mentioned explicitly. There are no Linux-specific examples, and code samples do not address Linux environments or tools. Windows tools (Power BI, Teams admin tools) are referenced for monitoring and analytics, with no mention of Linux alternatives.
Recommendations
  • Explicitly list Linux as a supported platform where applicable, or clarify limitations.
  • Provide Linux/macOS-specific code samples and instructions, especially for SDK usage and deployment.
  • Include parity for monitoring and analytics tools (e.g., alternatives to Power BI or Teams admin tools for Linux users).
  • Avoid listing Windows first in platform support statements; use alphabetical or neutral ordering.
  • Reference cross-platform tools and patterns where possible, and avoid assuming Windows as the default environment.
GitHub Create Pull Request
Communication Services Tutorial - Teams Shared Line Appearance ...ices/how-tos/cte-calling-sdk/shared-line-appearance.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (Teams PowerShell) for delegate assignment and listing the Microsoft Teams Client (primarily a Windows application) before alternatives. There are no explicit Linux/macOS instructions or examples for delegate assignment, and the prerequisites section prioritizes Windows-centric tooling. The SDK support table does not mention Linux or macOS platforms, focusing only on Windows and mobile platforms.
Recommendations
  • Add instructions for assigning delegates using Teams on Linux/macOS, if supported.
  • Include examples or guidance for using cross-platform CLI tools (e.g., Azure CLI, REST APIs) for delegate management.
  • Clarify platform support in the SDK table, explicitly mentioning Linux/macOS where applicable.
  • Provide parity in examples and tool recommendations, ensuring Linux/macOS users are not excluded.
GitHub Create Pull Request
Communication Services Microsoft Teams shared line appearance ...pts/interop/teams-user/teams-shared-line-appearance.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits Windows bias by referencing Teams PowerShell as a method for assigning delegates, without mentioning Linux/macOS alternatives or parity. The prerequisite steps and tooling guidance focus on Microsoft Teams Client and Teams PowerShell, both of which are Windows-centric. No Linux or cross-platform command-line options are provided, and Windows tools are mentioned before any platform-neutral alternatives.
Recommendations
  • Explicitly state whether Teams PowerShell is available and supported on Linux/macOS, or provide alternative methods for non-Windows users.
  • Include examples or instructions for assigning delegates using platform-neutral tools (e.g., Graph API, web interfaces) if available.
  • Clarify any limitations for Linux/macOS users in the prerequisites and provide guidance for achieving parity.
  • Reorder or balance tool mentions so that Windows tools are not always listed first, and highlight cross-platform options where possible.
GitHub Create Pull Request
Communication Services Enable interoperability with Teams ...ices/concepts/interop/enable-interoperability-teams.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exclusively references the PowerShell Set-CsPhoneNumberAssignment cmdlet for enabling Enterprise Voice, with no mention of Linux/macOS-compatible alternatives or cross-platform CLI options. This creates friction for users on non-Windows platforms, as PowerShell and Teams PowerShell modules are primarily supported on Windows.
Recommendations
  • Provide equivalent instructions using cross-platform Azure CLI or REST API if available.
  • Explicitly mention whether PowerShell commands can be run on Linux/macOS (e.g., via PowerShell Core), and provide installation guidance if so.
  • Include links or examples for non-Windows environments, or clarify platform limitations.
  • Consider adding a table or section comparing Windows and Linux/macOS setup steps.
GitHub Create Pull Request
Communication Services Security for communication as Teams external user ...munication-services/concepts/interop/guest/security.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It references PowerShell and the Microsoft Teams admin center as the primary tools for configuring security policies for Teams external users, without mentioning Linux/macOS equivalents or alternatives. Windows-centric tools are presented first and exclusively, which may create friction for Linux/macOS administrators.
Recommendations
  • Include instructions or references for managing Teams policies using cross-platform tools, such as Microsoft Graph API, which can be accessed from Linux/macOS.
  • Clarify whether PowerShell commands can be run on Linux/macOS (using PowerShell Core), and provide examples or links for non-Windows environments.
  • Mention and link to any web-based admin portals that are accessible from all platforms.
  • Add explicit notes or sections for Linux/macOS users, outlining supported management options and any limitations.
GitHub Create Pull Request
Communication Services Teams controls for Teams external user ...ervices/concepts/interop/guest/teams-administration.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation consistently references PowerShell modules and cmdlets for configuration and policy management, which are primarily Windows-centric tools. The Teams Admin Center is also mentioned, but no Linux/macOS equivalents or cross-platform CLI alternatives are provided. All example links and tool references for administrative actions (e.g., setting policies, configuring federation) are to PowerShell documentation, and there are no Bash, Azure CLI, or REST API examples. This creates friction for Linux/macOS administrators, who may not have access to PowerShell or prefer platform-native tools.
Recommendations
  • Provide Azure CLI or REST API equivalents for all PowerShell-based configuration and policy management tasks.
  • Explicitly mention cross-platform options for administrative tasks, such as using PowerShell Core on Linux/macOS, or direct Graph API calls.
  • Include example commands for Linux/macOS environments where possible, or clarify platform requirements for each tool.
  • Add a section on cross-platform administration, outlining best practices for non-Windows users.
GitHub Create Pull Request
Communication Services Prerequisites ...es/create-custom-managed-domain-resource-powershell.md
Medium 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 references the Azure Az PowerShell Module for all resource management tasks. There are no CLI, Bash, or cross-platform examples provided, and no mention of Linux/macOS alternatives. This creates friction for users on non-Windows platforms, as PowerShell is not the default shell and may require additional installation/configuration.
Recommendations
  • Add equivalent Azure CLI commands for all resource management tasks.
  • Explicitly mention that PowerShell Core is available cross-platform, and provide installation instructions for Linux/macOS.
  • Present both PowerShell and CLI/Bash examples side-by-side where possible.
  • Include notes on platform compatibility for the Az PowerShell Module.
GitHub Create Pull Request
Communication Services Send an email using SMTP ...s/quickstarts/email/send-email-smtp/send-email-smtp.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a dedicated section for sending email via Windows PowerShell, a Windows-specific tool, but does not offer equivalent Linux/macOS command-line examples (e.g., using sendmail, mailx, or swaks). This creates a bias toward Windows users and omits guidance for Linux/macOS users who may not have access to PowerShell.
Recommendations
  • Add a section or pivot for Linux/macOS command-line email sending, using common tools such as sendmail, mailx, swaks, or Python scripts.
  • Ensure that examples for all major platforms (Windows, Linux, macOS) are provided and easily discoverable.
  • Clarify platform requirements for each method, so users know which instructions apply to their OS.
GitHub Create Pull Request
Communication Services Azure Communication Services Call Automation how-to for adding Microsoft Teams User into an existing call ...w-tos/call-automation/teams-interop-call-automation.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation exhibits Windows bias primarily in the authorization step, where only Windows-centric tools (PowerShell cmdlets like Set-CsTeamsAcsFederationConfiguration and Set-CsExternalAccessPolicy) are mentioned for configuring Teams federation. These are traditionally managed via Windows PowerShell, with no mention of Linux/macOS alternatives or cross-platform CLI options. The rest of the guide is cross-platform, focusing on SDK usage in multiple languages, but the initial setup assumes access to Windows tools and administrative patterns.
Recommendations
  • Provide guidance for performing Teams federation configuration using cross-platform tools, such as Microsoft Teams Admin Center (web UI), or document if PowerShell Core on Linux/macOS is supported for these cmdlets.
  • Explicitly state platform requirements for administrative steps and offer alternatives for non-Windows users.
  • Include notes or links to documentation for running Microsoft 365 admin tasks on Linux/macOS, if available.
  • Clarify whether the required PowerShell modules are available on PowerShell Core (pwsh) for Linux/macOS, and provide installation instructions if so.
GitHub Create Pull Request
Communication Services Plan user experience for virtual appointments ...oncepts/interop/virtual-visits/plan-user-experience.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references Microsoft Teams Admin Center and PowerShell as the primary methods for learning and configuring Teams meeting settings, without mentioning Linux/macOS equivalents or alternatives. This suggests a Windows-first approach and reliance on Windows-specific tools, with no guidance for Linux users on how to perform these tasks.
Recommendations
  • Include instructions or references for configuring Teams via cross-platform tools (e.g., Microsoft Graph API, web-based Teams Admin Center) that work on Linux/macOS.
  • Explicitly state whether PowerShell commands can be run on PowerShell Core (pwsh) on Linux/macOS, and provide examples if possible.
  • Add Linux/macOS-specific notes or alternatives for any configuration steps that currently only mention Windows tools.
  • Ensure examples and tool recommendations are platform-neutral or include parity for Linux/macOS users.
GitHub Create Pull Request
Communication Services include file ...ion-services/quickstarts/sms/includes/send-sms-java.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Command Prompt and PowerShell examples for creating and running the Java application, but does not include explicit Linux/macOS shell (bash/zsh) examples. Windows-specific shells are mentioned first and exclusively, which may create friction for Linux/macOS users unfamiliar with PowerShell syntax or conventions.
Recommendations
  • Add explicit bash/zsh examples for all command-line instructions, especially for 'mvn archetype:generate' and 'mvn exec:java' commands.
  • Present shell examples in a cross-platform order (e.g., Bash first, then Windows Command Prompt, then PowerShell) or group them together with clear OS labels.
  • Clarify that the Maven commands are cross-platform and can be run in any terminal, but provide syntax for Linux/macOS shells.
  • Consider adding a note or table summarizing command syntax differences across platforms.
GitHub Create Pull Request
Communication Services include file ...mples/includes/email-resource-management-powershell.md
Medium 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 is heavily focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets and syntax. The prerequisites and environment checks reference Windows tools and patterns (e.g., command prompt, PowerShell version check), and there are no equivalent instructions or examples for Linux/macOS users (such as Bash, Azure CLI, or cross-platform scripting). This creates friction for non-Windows users and may prevent them from easily following the guide.
Recommendations
  • Add equivalent Azure CLI (az) examples for all major steps, including resource creation, DNS record management, and domain verification.
  • Update the prerequisites section to mention installation and usage of Azure PowerShell on Linux/macOS, or provide alternative instructions for Azure CLI.
  • Include environment checks and authentication steps for Linux/macOS (e.g., checking Azure CLI version, using Bash or zsh).
  • Clearly state that the script is PowerShell-specific and provide links or references to cross-platform alternatives.
  • Reorder or parallelize examples so that Linux/macOS instructions are presented alongside Windows/PowerShell instructions.
GitHub Create Pull Request
Communication Services Create a Communication Services resource in Azure Communication Services ...-services/quickstarts/create-communication-resource.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation shows a moderate Windows bias: Windows examples and tools (PowerShell, setx) are presented first or exclusively in some sections, and Windows-centric instructions (e.g., app.config/web.config, Visual Studio) are referenced before Linux/macOS equivalents. However, Linux/macOS instructions are present for environment variables and Azure CLI is cross-platform, so Linux users can complete all tasks.
Recommendations
  • Present Linux/macOS examples before or alongside Windows examples, not after.
  • Include explicit bash/zsh instructions for environment variables in the main flow, not only in tabs.
  • Reference cross-platform editors (e.g., VS Code) alongside Visual Studio.
  • Mention Linux/macOS config file equivalents (e.g., .env files) when discussing app.config/web.config.
  • Clarify that Azure CLI works on all platforms and link to non-Windows install guides.
  • Avoid using Windows-specific terminology (e.g., 'console window') without alternatives.
GitHub Create Pull Request
Communication Services Add custom verified email domains ...vices/quickstarts/email/add-custom-verified-domains.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 moderate Windows bias. Platform pivots include Azure Portal, Azure CLI, .NET, and PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to cross-platform options but no explicit mention of Linux shell equivalents. DNS record instructions for 'Other (General)' link to a guide for Windows-based DNS, with no Linux/BIND or macOS DNS management examples. The documentation references Microsoft 365 DNS guides, which often assume Windows environments. There are no explicit Linux/macOS command-line or tool examples for DNS management or domain verification.
Recommendations
  • Add explicit Linux/macOS shell examples (e.g., using dig, nsupdate, or editing BIND zone files) for DNS record management.
  • Provide parity for PowerShell by including Bash/Azure CLI scripts for all tasks.
  • Update 'Other (General)' DNS instructions to include guides for Linux-based DNS servers (e.g., BIND, Unbound) and macOS.
  • Clarify that Azure CLI is cross-platform and provide example commands for Linux/macOS environments.
  • Avoid linking only to Windows-based DNS guides; include vendor-neutral or Linux-focused resources.
GitHub Create Pull Request
Communication Services Prerequisites ...des/create-azure-managed-domain-resource-powershell.md
Medium 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 for all resource management tasks. There are no examples or instructions for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform alternatives. The documentation assumes the use of PowerShell, which is traditionally associated with Windows, and does not mention or prioritize Linux-compatible tools.
Recommendations
  • Add equivalent Azure CLI examples for all resource management tasks (login, module installation, resource creation, tagging, listing, deletion).
  • Explicitly mention cross-platform compatibility of PowerShell if relevant, or provide installation instructions for PowerShell on Linux/macOS.
  • Include a section or note for Linux/macOS users, outlining alternative workflows or tools.
  • Where possible, show both PowerShell and CLI examples side-by-side to improve accessibility.
GitHub Create Pull Request
Communication Services Prerequisites ...rts/email/includes/create-email-resource-powershell.md
Medium 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 references the Azure Az PowerShell module for all resource management tasks. There are no examples or instructions for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform tools. The documentation assumes a Windows environment and does not mention alternatives or parity for non-Windows platforms.
Recommendations
  • Provide equivalent Azure CLI examples for all resource management tasks, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Clearly state platform compatibility for each tool (e.g., note that Azure PowerShell is available on Linux/macOS via PowerShell Core, but Azure CLI may be preferred).
  • Add installation instructions for Azure CLI and PowerShell Core on Linux/macOS.
  • Reorder examples or provide parallel sections for both PowerShell and CLI, avoiding Windows-first presentation.
  • Mention any limitations or differences in experience between platforms, if applicable.
GitHub Create Pull Request
Communication Services Prerequisites ...includes/create-sender-username-resource-powershell.md
Medium 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 references the Azure Az PowerShell Module, which is most commonly used on Windows. There are no examples or instructions for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform alternatives. This creates friction for non-Windows users and may prevent them from completing the tasks without additional research.
Recommendations
  • Provide equivalent Azure CLI commands for all operations (login, resource creation, update, listing, deletion).
  • Explicitly mention that PowerShell Core is cross-platform, if applicable, and provide installation instructions for Linux/macOS.
  • Include Bash or shell script examples where relevant.
  • Clarify tool compatibility and recommend alternatives for Linux/macOS users.
GitHub Create Pull Request
Communication Services include file ...-services/quickstarts/email/includes/send-email-net.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by referencing Windows-centric tools (cmd, PowerShell) before Bash, and omits explicit Linux/macOS instructions or examples. All code and commands are platform-agnostic (dotnet CLI), but the narrative and examples assume a Windows environment, with no mention of Linux/macOS-specific considerations (such as environment variable setting, file paths, or terminal usage).
Recommendations
  • Explicitly mention Linux/macOS support in all sections, especially in prerequisites and instructions.
  • Provide Linux/macOS-specific examples for environment variable setup and terminal usage (e.g., export in Bash, path separators).
  • List Bash or Linux/macOS terminals first or equally alongside Windows tools (cmd, PowerShell) when referencing console windows.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, dotnet installation).
GitHub Create Pull Request
← Previous Page 7 of 15 Next →