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 376-400 of 656 flagged pages
Communication Services Tutorial - Teams Shared Line Appearance ...ices/how-tos/cte-calling-sdk/shared-line-appearance.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits a moderate Windows bias. It references Teams PowerShell as a method for assigning delegates and lists 'Windows' in the SDK support table, but does not mention or provide Linux/macOS equivalents or examples. The instructions for assigning delegates prioritize Microsoft Teams Client and Teams PowerShell, both of which are primarily Windows-centric tools.
Recommendations
  • Include instructions or examples for assigning delegates using cross-platform tools or APIs, if available.
  • Clarify whether Teams PowerShell can be used on macOS/Linux (via PowerShell Core), and provide guidance for those platforms.
  • Explicitly state platform limitations for the Teams Client and PowerShell, and suggest alternatives for Linux/macOS users.
  • Add Linux/macOS-specific notes or examples where relevant, especially in sections discussing tooling.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation shows a notable Windows bias, especially in the authorization step, where only PowerShell cmdlets (Set-CsTeamsAcsFederationConfiguration, Set-CsExternalAccessPolicy) are mentioned for tenant and user policy configuration. There are no Linux/macOS equivalents or CLI/portal alternatives provided for these critical steps. The rest of the guide is cross-platform, with code samples for multiple languages, but the initial setup assumes access to Windows/PowerShell tools.
Recommendations
  • Provide Azure CLI or REST API equivalents for the PowerShell-only configuration steps.
  • Include instructions for performing tenant/user policy configuration via the Azure Portal or Teams Admin Center, if available.
  • Explicitly mention platform requirements for steps that are Windows/PowerShell-only, and suggest workarounds for Linux/macOS users.
  • Add links or references to cross-platform tools or scripts where possible.
GitHub Create Pull Request
Communication Services include file ...tion-services/quickstarts/chat/includes/chat-csharp.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. Visual Studio is listed as a required prerequisite without mention of cross-platform alternatives. The package installation example uses PowerShell syntax, and Windows shells (cmd, PowerShell) are mentioned before Bash. No Linux/macOS-specific instructions or troubleshooting are provided, and the overall workflow assumes a Windows development environment.
Recommendations
  • List Visual Studio Code and .NET CLI as cross-platform alternatives in prerequisites.
  • Provide explicit instructions for installing the SDK/package on Linux/macOS (e.g., using Bash or zsh).
  • Mention Bash and other Unix shells before or alongside Windows shells when giving command-line instructions.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, path differences).
  • Clarify that all .NET CLI commands work on Linux/macOS and provide sample screenshots or terminal outputs from those platforms.
GitHub Create Pull Request
Communication Services Add a bot to your chat app ...uickstarts/chat/quickstart-botframework-integration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. It consistently references Windows-specific tools (Visual Studio), provides instructions and screenshots for Visual Studio and Azure Portal, and omits Linux/macOS equivalents or alternatives. Command-line instructions use 'dotnet' and 'powershell' syntax but do not clarify cross-platform compatibility or provide Linux/macOS-specific guidance. There are no examples or deployment instructions for Linux/macOS environments, such as using VS Code, CLI-only workflows, or alternative deployment methods. This creates friction for non-Windows users attempting to follow the quickstart.
Recommendations
  • Add explicit instructions for Linux/macOS users, including how to install .NET Core and use the 'dotnet' CLI for all steps.
  • Provide examples using VS Code or other cross-platform editors, not just Visual Studio.
  • Include deployment instructions using Azure CLI and GitHub Actions, which work on Linux/macOS.
  • Clarify that 'dotnet' commands are cross-platform and provide any necessary Linux/macOS prerequisites.
  • Add screenshots or terminal output examples from Linux/macOS environments.
  • Mention package managers (e.g., apt, brew) for installing .NET Core on Linux/macOS.
GitHub Create Pull Request
Communication Services Prerequisites ...des/create-azure-managed-domain-resource-powershell.md
Medium Priority View Details →
Scanned: 2026-01-13 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/macOS users, such as using Azure CLI, Bash, or cross-platform tools. This creates friction for non-Windows users who may not have PowerShell installed or prefer native Linux tooling.
Recommendations
  • Add equivalent Azure CLI examples for all resource management tasks (create, update, list, delete).
  • Explicitly mention cross-platform installation and usage of PowerShell if it is required, or provide alternatives.
  • Include a section or note for Linux/macOS users, clarifying supported tools and providing relevant commands.
  • Where possible, use platform-neutral terminology and avoid assuming PowerShell as the default.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation shows some Windows bias, particularly in the DNS record section, where the 'Other (General)' CNAME record link points to a guide for 'windows-based DNS', with no explicit Linux or cross-platform DNS server instructions. Additionally, the platform pivots include PowerShell (Windows-centric) and Azure CLI, but do not clarify Linux-specific steps or provide parity for Linux-native DNS management. Windows tools and patterns are referenced before Linux equivalents, and Linux/macOS users may need to infer their steps.
Recommendations
  • Add explicit instructions or links for managing DNS records on Linux-based DNS servers (e.g., BIND, Unbound), not just Windows DNS.
  • Ensure that 'Other (General)' DNS instructions are platform-neutral or provide both Windows and Linux/macOS guides.
  • If PowerShell is shown, also provide Bash or shell script equivalents for Linux/macOS users.
  • Clarify in the Azure CLI section that it works on Linux/macOS and provide any OS-specific notes if needed.
GitHub Create Pull Request
Communication Services Prerequisites ...es/create-custom-managed-domain-resource-powershell.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module for all resource management tasks. 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
  • Add equivalent Azure CLI commands for all resource management steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and provide installation instructions if PowerShell usage is required.
  • Include Bash script examples or note how to adapt the commands for Linux/macOS environments.
  • Reorder examples or provide parallel instructions so that Windows and Linux/macOS users are equally supported.
  • Clarify any platform-specific limitations or requirements for the Az.Communication module.
GitHub Create Pull Request
Communication Services Prerequisites ...includes/create-sender-username-resource-powershell.md
Medium Priority View Details →
Scanned: 2026-01-13 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/macOS users (e.g., Bash, Azure CLI), and the documentation does not mention cross-platform alternatives or considerations. This creates friction for non-Windows users who may not have PowerShell installed or prefer native Linux/macOS tooling.
Recommendations
  • Add equivalent Azure CLI commands for all operations (login, resource creation, management, deletion).
  • Explicitly mention that PowerShell Core is available on Linux/macOS and provide installation instructions if PowerShell is required.
  • Include Bash or shell script examples where possible.
  • Clarify whether the Az.Communication module is supported on PowerShell Core across platforms.
  • Reorder examples or provide tabs for Windows (PowerShell) and Linux/macOS (CLI/Bash) to ensure parity.
GitHub Create Pull Request
Communication Services include file ...-services/quickstarts/email/includes/send-email-net.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
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-specific consoles (cmd, PowerShell) before Bash, and by omitting explicit Linux/macOS instructions or examples. All code samples and commands are shown in a cross-platform manner (using dotnet CLI), but there is no guidance or troubleshooting specific to Linux/macOS environments. The documentation does not mention Linux package managers, shell differences, or platform-specific issues, and it assumes familiarity with Windows tools and workflows.
Recommendations
  • Explicitly mention Linux/macOS compatibility in all relevant sections.
  • Provide Linux/macOS-specific instructions for installing .NET Core (e.g., using apt, yum, brew).
  • List Bash and other Unix shells before or alongside Windows consoles when referencing terminal usage.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, environment variable setup).
  • Include sample commands for setting environment variables on Linux/macOS (e.g., export COMMUNICATION_SERVICES_CONNECTION_STRING=...)
  • Reference platform-agnostic editors (e.g., VS Code, nano, vim) in addition to 'text editor'.
GitHub Create Pull Request
Communication Services include file ...es/quickstarts/email/includes/send-email-powershell.md
Medium Priority View Details →
Scanned: 2026-01-13 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 biased towards Windows and PowerShell. All examples use Azure PowerShell, and instructions explicitly reference Windows PowerShell. There are no examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI, or cross-platform scripting). The prerequisite check and installation steps assume a Windows environment and PowerShell usage, with no mention of alternatives for other platforms.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and works on Linux/macOS.
  • Explicitly mention how to install and use Azure PowerShell on Linux/macOS (e.g., via pwsh), or provide Bash examples.
  • Reorder sections or add notes to clarify that Azure Communication Services can be used from Linux/macOS, and provide parity in guidance.
  • Include troubleshooting or environment setup notes for non-Windows users.
  • Reference cross-platform documentation for Azure PowerShell and CLI.
GitHub Create Pull Request
Communication Services Register the Event Grid resource provider ...starts/events/includes/register-provider-powershell.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
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 performing the same task using Azure CLI or other cross-platform tools, making it less accessible for Linux and macOS users.
Recommendations
  • Add equivalent Azure CLI commands for registering and checking the Event Grid resource provider status.
  • Explicitly mention that PowerShell is Windows-centric and provide guidance for non-Windows users.
  • Consider reordering or presenting cross-platform examples before or alongside PowerShell examples.
GitHub Create Pull Request
Communication Services include file ...send-email-smtp/includes/send-email-smtp-powershell.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides instructions and code 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 (e.g., Python, curl, swaks, or mailx) mentioned. This creates friction for non-Windows users attempting to follow the guide.
Recommendations
  • Add equivalent Linux/macOS examples using common tools such as Python (smtplib), curl, swaks, or mailx.
  • Explicitly mention cross-platform alternatives to PowerShell for sending SMTP email.
  • Reorder examples so that cross-platform solutions are presented first or alongside Windows-specific instructions.
  • Clarify which steps are Windows-specific and provide links or instructions for Linux/macOS users.
GitHub Create Pull Request
Communication Services Additional Prerequisites ...ity/includes/active-directory/service-principal-cli.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by listing Windows-specific setup articles first and exclusively (e.g., Azure portal, PowerShell, CLI, ARM template, SDK—all with 'windows-vm' in the link), and does not mention or link to Linux/macOS equivalents for enabling managed identities. The environment variable instructions are platform-neutral, but the guidance for setup and authentication is Windows-centric.
Recommendations
  • Add equivalent setup articles and links for Linux and macOS environments (e.g., configuring managed identities for Linux VMs).
  • Include Linux/macOS-specific examples for setting environment variables, such as using 'export' in bash/zsh, and mention how to persist them.
  • Ensure that CLI instructions clarify cross-platform compatibility and, where relevant, provide OS-specific notes.
  • Reorder or balance example links so that Linux/macOS options are presented alongside or before Windows options.
GitHub Create Pull Request
Communication Services Prerequisites ...ces/quickstarts/includes/create-resource-powershell.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell commands and Windows-centric tooling (e.g., Az PowerShell Module), with no mention or examples for Linux/macOS users. There are no Bash, Azure CLI, or cross-platform instructions, and all examples are shown in Windows PowerShell syntax and context.
Recommendations
  • Add equivalent Azure CLI (az) commands for all resource management tasks.
  • Explicitly mention that PowerShell Core is available cross-platform, or clarify if Windows PowerShell is required.
  • Provide Bash or shell examples for Linux/macOS users.
  • Include notes or sections for Linux/macOS prerequisites and installation steps.
  • Reorder examples so that cross-platform tools (Azure CLI) are presented first or alongside PowerShell.
GitHub Create Pull Request
Communication Services Set up and create access tokens for Teams users ...nication-services/quickstarts/manage-teams-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias, particularly in the administrator troubleshooting section. PowerShell is used exclusively for critical tasks such as installing modules and creating service principals, with no mention of Linux/macOS alternatives (e.g., Azure CLI, Bash). The troubleshooting steps and examples assume access to PowerShell and Windows tools, and do not provide parity for Linux/macOS users. This could create friction for non-Windows administrators attempting to complete these steps.
Recommendations
  • Provide equivalent Azure CLI or Bash commands for service principal creation and module installation.
  • Explicitly mention cross-platform alternatives for all PowerShell commands, or clarify platform requirements.
  • Add troubleshooting instructions for Linux/macOS environments, including how to install and use Microsoft Graph and Azure CLI.
  • Reorder examples or add notes to ensure Linux/macOS users are not left behind in critical steps.
GitHub Create Pull Request
Communication Services Answer Teams Phone calls from Call Automation ...ts/tpe/teams-phone-extensibility-answer-teams-calls.md
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias. Key setup steps, such as creating a Teams Resource account and associating it with Azure Communication Services, are shown exclusively using PowerShell commands and reference Windows-centric tools. The DevTunnel setup is also presented only with PowerShell commands, with no mention of Linux/macOS equivalents or cross-platform CLI alternatives. There are no Linux/macOS-specific instructions or examples, and Windows/PowerShell tools are mentioned first and exclusively.
Recommendations
  • Provide equivalent command-line instructions for Linux/macOS environments, such as using Azure CLI, Bash, or cross-platform PowerShell Core.
  • Clarify whether DevTunnel and Teams PowerShell modules are supported on Linux/macOS, and if so, provide installation and usage examples for those platforms.
  • Add notes or links to platform-specific documentation for Linux/macOS users.
  • Where possible, use REST API or Azure CLI examples instead of (or in addition to) PowerShell, to ensure cross-platform compatibility.
GitHub Create Pull Request
Communication Services Quickstart - How to call to Teams user from an Android app ...ideo-calling/includes/teams-user/teams-user-android.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references enabling Teams Phone users via a PowerShell command and links to Windows-centric deployment guides, without mentioning or providing Linux/macOS alternatives. No Linux/macOS-specific instructions or parity for Teams administration are given.
Recommendations
  • Add instructions or references for enabling Teams Phone users using Microsoft 365 admin center (web UI), which is cross-platform.
  • Clarify whether PowerShell commands can be run on Linux/macOS (using PowerShell Core), and provide guidance if so.
  • Include links to Teams deployment documentation that covers cross-platform scenarios, or explicitly state platform requirements.
  • Where possible, avoid assuming administrative tasks must be performed on Windows, and highlight web-based or cross-platform alternatives.
GitHub Create Pull Request
Communication Services Quickstart - Make a call to Teams user from a web app ...o-calling/includes/teams-user/teams-user-javascript.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias in the prerequisites section, where Teams Phone license enablement is referenced via a PowerShell-only link, and Teams deployment links to a Windows-centric guide. No Linux/macOS equivalents or alternative instructions are provided for these steps. The rest of the tutorial (JavaScript code, web app setup, and running via webpack) is cross-platform, but the initial setup assumes Windows tooling and patterns.
Recommendations
  • Provide Linux/macOS-compatible instructions or links for enabling Teams Phone and Enterprise Voice (e.g., via Microsoft Graph API or web portal).
  • Clarify whether PowerShell steps are required only for administrators and offer alternatives for non-Windows users.
  • Explicitly state that the JavaScript SDK and web app steps are cross-platform and can be run on Linux/macOS.
  • Add notes or sections for Linux/macOS users in the prerequisites, especially for Teams deployment and license enablement.
GitHub Create Pull Request
Communication Services Quickstart - Teams interop calls on Azure Communication Services ...video-calling/get-started-teams-interop-group-calls.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias: it references Windows-specific tools (PowerShell) for enabling Teams Phone features, links to Windows-centric Teams deployment guides, and does not provide Linux/macOS equivalents or alternatives for these steps. The code samples themselves are cross-platform (JavaScript for browser), but the prerequisites and setup steps assume a Windows environment and omit Linux/macOS guidance.
Recommendations
  • Provide Linux/macOS alternatives for enabling Teams Phone features (e.g., using Microsoft Graph API or CLI instead of PowerShell).
  • Include links to Teams deployment guides for Linux/macOS, or clarify platform requirements.
  • Explicitly state that the code samples (JavaScript/Node.js) are cross-platform and provide any necessary platform-specific setup instructions.
  • Add notes or examples for Linux/macOS users where Windows-specific tools (like PowerShell) are referenced.
GitHub Create Pull Request
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-13 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 mild Windows bias by referencing Windows-specific tools and patterns, such as requiring Teams users to be Enterprise Voice enabled via PowerShell, and linking to Windows-centric Teams deployment instructions. There are no Linux/macOS equivalents or alternative instructions provided for these steps, and Windows tools are mentioned first and exclusively.
Recommendations
  • Provide Linux/macOS alternatives for enabling Teams Enterprise Voice (e.g., via Microsoft Graph API or web portal, if available).
  • Include links or instructions for Teams deployment on Linux/macOS, or clarify platform requirements.
  • Explicitly state if certain steps (like PowerShell usage) are only possible on Windows, and suggest workarounds for non-Windows users.
  • Balance references to Windows tools with cross-platform or web-based methods where possible.
GitHub Create Pull Request
Communication Services References - How to collect diagnostic audio recordings ...ferences/how-to-collect-diagnostic-audio-recordings.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in the section on building and using the unpack_aecdump tool. Only Windows prerequisites (Visual Studio 2022, Windows-specific depot_tools instructions) are listed, and the build instructions reference a Windows build guide. The output binary is described as unpack_aecdump.exe, and no Linux or macOS build instructions, prerequisites, or usage examples are provided. This may hinder Linux/macOS users from building or running the tool.
Recommendations
  • Add Linux/macOS build instructions for unpack_aecdump, including required packages (e.g., build-essential, Python, depot_tools setup for Unix).
  • Reference Chromium's official Linux/macOS build guides alongside the Windows guide.
  • Clarify that unpack_aecdump can be built on Linux/macOS and provide example commands and expected output filenames (e.g., unpack_aecdump instead of unpack_aecdump.exe).
  • Include troubleshooting tips for common Linux/macOS build issues.
  • Provide usage examples for Linux/macOS (e.g., ./unpack_aecdump audio_debug.5.aecdump).
GitHub Create Pull Request
Communication Services Automate email resource management ...nication-services/samples/email-resource-management.md
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias by providing PowerShell commands for resource cleanup and management, with no equivalent Bash/Linux shell examples. The CLI examples are labeled as 'Azure CLI PowerShell' and 'Azure CLI Python', but the actual cleanup commands for Email Communication Services and Domain resources are only shown in PowerShell syntax. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native shell environments.
Recommendations
  • Provide equivalent Azure CLI commands for all resource management and cleanup tasks, especially for Email Communication Services and Domain resources.
  • Clearly separate platform-specific instructions and ensure Linux/macOS users are not required to use PowerShell.
  • Add Bash or shell script examples alongside PowerShell, and clarify which commands are cross-platform.
  • Review included files (e.g., email-resource-management-powershell.md) to ensure Linux parity in examples.
GitHub Create Pull Request
Communication Services include file ...ludes/email-resource-management-azurecli-powershell.md
Medium Priority View Details →
Scanned: 2026-01-13 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 biased towards Windows and PowerShell. All code samples are written in PowerShell syntax, and instructions reference Windows-specific tools and installation paths. There are no Bash or Linux/macOS shell examples, nor any mention of how to adapt the scripts for non-Windows environments. Even Azure CLI installation links point to Windows-specific instructions first.
Recommendations
  • Provide equivalent Bash shell scripts for Linux/macOS users, using standard shell syntax and idioms.
  • Include installation instructions for Azure CLI and Azure PowerShell for Linux and macOS, with appropriate links.
  • Clarify which commands are cross-platform (e.g., Azure CLI) and which are Windows/PowerShell-specific.
  • If PowerShell is required, note that PowerShell Core is available on Linux/macOS and provide guidance for its installation and usage.
  • Present examples for both platforms side-by-side or clearly indicate platform-specific sections.
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-13 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 several ways: registry commands for .NET detection use Windows-specific tools, Windows consoles (cmd, PowerShell) are mentioned before Bash, and there are no explicit Linux/macOS instructions or examples for environment variable setup, .NET installation, or Azure CLI usage. All code samples and package instructions assume .NET/C#, which is cross-platform, but the setup and verification steps are Windows-centric.
Recommendations
  • Provide Linux/macOS equivalents for .NET installation and verification (e.g., use 'dotnet --info' instead of Windows registry queries).
  • List Bash and Linux/macOS terminal options before or alongside Windows (cmd, PowerShell) in instructions.
  • Include explicit instructions for setting environment variables on Linux/macOS (e.g., export LANGUAGE_KEY=...).
  • Add notes or examples for using Azure CLI on Linux/macOS where relevant.
  • Ensure screenshots and navigation instructions in Azure Portal are OS-agnostic or clarify any differences.
GitHub Create Pull Request
Communication Services include file ...mples/includes/email-resource-management-powershell.md
Medium Priority View Details →
Scanned: 2026-01-13 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 is heavily biased toward Windows and PowerShell. All examples and instructions use Azure PowerShell cmdlets and scripting, with no mention of Bash, Azure CLI, or cross-platform alternatives. The prerequisite check references a Windows command prompt and PowerShell, and the installation link is for Azure PowerShell on Windows. There are no Linux/macOS-specific instructions or examples, and no guidance on using Azure CLI or Bash for the same tasks.
Recommendations
  • Add equivalent Azure CLI (az) examples for all resource creation, domain management, and DNS configuration steps.
  • Clarify that Azure PowerShell is available cross-platform (Windows, Linux, macOS), and provide installation instructions for all OSes.
  • Include a prerequisite check for PowerShell Core (pwsh) and/or Azure CLI on Linux/macOS.
  • Provide Bash script samples or guidance for users who prefer shell scripting.
  • Reorder examples so that cross-platform tools (Azure CLI) are shown first or alongside PowerShell.
GitHub Create Pull Request
← Previous Page 16 of 27 Next →