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 326-350 of 656 flagged pages
Communication Services Security for communication as Teams external user ...munication-services/concepts/interop/guest/security.md
Medium Priority View Details →
Scanned: 2026-01-14 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 moderate Windows bias by referencing PowerShell and the Microsoft Teams admin center as primary tools for administration, without mentioning Linux/macOS alternatives. Windows-centric tools and patterns are presented first and exclusively, with no guidance for Linux or cross-platform management. This may create friction for non-Windows users, especially administrators who do not use Windows environments.
Recommendations
  • Include equivalent Linux/macOS administration methods, such as Azure CLI, REST APIs, or cross-platform scripting options.
  • Explicitly mention whether PowerShell commands can be run on Linux/macOS, or provide Bash/CLI examples where possible.
  • Add notes or links to cross-platform tools for managing Teams and Azure Communication Services.
  • Clarify if the Teams admin center is accessible via web browsers on all platforms.
GitHub Create Pull Request
Communication Services Calling capabilities for Teams users ...cation-services/concepts/interop/teams-user-calling.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page lists platform support for Teams Calling SDK features, with Windows as a distinct column and frequent references to Microsoft-specific technologies (e.g., Microsoft Entra, Microsoft Graph, Teams). There is a subtle Windows bias: Windows is listed as a primary platform, and links to Microsoft tools (such as PowerShell modules) are present, but there are no explicit Linux/macOS examples or mentions of Linux-specific tools or patterns. The documentation does not provide parity for Linux users in terms of examples or troubleshooting guidance, though the JavaScript column may implicitly cover cross-platform scenarios.
Recommendations
  • Add explicit Linux/macOS columns or sections to the feature matrix to clarify support and limitations for those platforms.
  • Provide Linux/macOS-specific setup, troubleshooting, and usage examples, especially for authentication and device management.
  • Include references to Linux/macOS tools and APIs where relevant, not just Microsoft/Windows-centric ones.
  • Clarify whether the JavaScript SDK is fully supported and tested on Linux/macOS desktop environments.
  • Avoid referencing only Windows tools (e.g., PowerShell) in links or instructions; offer alternatives for other platforms.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates moderate Windows bias by referencing Teams PowerShell as a method for assigning delegates and mentioning Windows in the context of platform support. Linux/macOS equivalents (such as CLI or GUI alternatives) are not discussed, and PowerShell is presented as a primary tool for configuration, which may create friction for non-Windows users.
Recommendations
  • Include Linux/macOS-compatible instructions for assigning delegates, such as using the Teams web client or any available cross-platform CLI tools.
  • Clarify whether PowerShell commands can be run on Linux/macOS (via PowerShell Core), and provide explicit examples for those platforms if possible.
  • List GUI/web-based methods before or alongside PowerShell to avoid Windows-first impression.
  • Explicitly state platform limitations and offer alternatives or workarounds for unsupported platforms.
GitHub Create Pull Request
Communication Services Teams Phone extensibility FAQ .../concepts/interop/tpe/teams-phone-extensibility-faq.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Emergency calling configuration is described as being performed via the Teams Admin Center (TAC) portal or with PowerShell cmdlets, with no mention of Linux/macOS alternatives or CLI tools. Windows-centric tools (PowerShell, TAC portal) are referenced exclusively and first, and there are no examples or guidance for Linux or cross-platform administration. This may create friction for Linux/macOS users who need to configure or automate Teams Phone extensibility features.
Recommendations
  • Explicitly mention whether PowerShell cmdlets can be run on Linux/macOS (using PowerShell Core), or provide equivalent CLI/REST API instructions.
  • Include examples for configuring emergency calling and other administrative tasks using cross-platform tools (e.g., Azure CLI, REST API, Graph API).
  • Clarify if the Teams Admin Center portal is fully supported on non-Windows browsers and platforms.
  • Add Linux/macOS-specific notes or troubleshooting tips for common administrative scenarios.
GitHub Create Pull Request
Communication Services Teams Phone extensibility overview ...epts/interop/tpe/teams-phone-extensibility-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools and patterns, such as the Teams Admin Center (TAC portal) and PowerShell cmdlets, for configuration and policy assignment. These Windows tools are mentioned as primary methods for administrative tasks, with no mention of Linux/macOS alternatives or cross-platform CLI options. There are no explicit Linux/macOS examples, and the documentation assumes familiarity with Windows administration paradigms.
Recommendations
  • Include cross-platform CLI alternatives (such as Azure CLI or Microsoft Graph API) for administrative tasks currently described with PowerShell or TAC portal.
  • Add explicit Linux/macOS usage notes or examples for provisioning, configuration, and SDK usage.
  • Clarify which steps can be performed from non-Windows environments, and provide links to platform-neutral documentation.
  • Where PowerShell is referenced, also mention equivalent REST API or CLI commands for Linux/macOS users.
GitHub Create Pull Request
Communication Services Teams Phone extensibility Troubleshooting ...terop/tpe/teams-phone-extensibility-troubleshooting.md
Medium Priority View Details →
Scanned: 2026-01-14 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 demonstrates a notable Windows bias in the troubleshooting steps for resolving Microsoft Entra App permission issues. All command-line instructions are provided exclusively using PowerShell, a Windows-centric tool, with no mention of Linux/macOS alternatives (such as Azure CLI, Microsoft Graph CLI, or REST API). The instructions also reference installing PowerShell modules, which is not directly applicable to Linux/macOS users without additional context or instructions. Other troubleshooting sections focus on web portals and licensing, which are platform-neutral, but the critical service principal creation step is Windows-only.
Recommendations
  • Provide equivalent instructions using Azure CLI, Microsoft Graph CLI, or REST API for Linux/macOS users.
  • Explicitly mention platform compatibility for PowerShell commands and modules.
  • Add notes or links for Linux/macOS users on how to install and use PowerShell Core, if necessary.
  • Where possible, present cross-platform examples side-by-side, or at least clarify which steps are platform-specific.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation demonstrates a moderate Windows bias, primarily in the authorization step, where only Windows-centric tools (PowerShell cmdlets) are referenced for tenant configuration. These cmdlets (Set-CsTeamsAcsFederationConfiguration, Set-CsExternalAccessPolicy) are typically run in Windows environments and no Linux/macOS alternatives or guidance are provided. The rest of the documentation is cross-platform, with code samples for multiple languages and no OS-specific instructions, but the initial setup may create friction for non-Windows users.
Recommendations
  • Provide explicit instructions or alternatives for running Microsoft Teams PowerShell cmdlets on Linux/macOS (e.g., using PowerShell Core, Azure Cloud Shell, or REST API equivalents if available).
  • Mention and link to platform-agnostic methods for tenant configuration, such as using Microsoft Graph API or Azure Portal UI where possible.
  • Clarify whether the PowerShell steps can be performed in Azure Cloud Shell (browser-based, cross-platform) and provide guidance.
  • Add notes or sections for Linux/macOS users outlining any prerequisites or limitations for administrative tasks.
  • Consider reordering or parallelizing instructions so that platform-agnostic methods are presented before or alongside Windows-specific tools.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. All code and deployment examples use Visual Studio and .NET Core, with instructions and screenshots focused on Windows tooling. Package installation is shown using PowerShell syntax. There are no Linux/macOS-specific instructions, nor are alternative tools (e.g., VS Code, CLI-based deployment) discussed. The prerequisites list only Visual Studio, omitting cross-platform editors. This creates friction for Linux/macOS users who may not have access to Visual Studio or prefer other development environments.
Recommendations
  • Add instructions for using VS Code or other cross-platform editors.
  • Include CLI-based deployment steps (e.g., using Azure CLI, dotnet CLI) for bot and chat app deployment.
  • Provide Linux/macOS-specific setup guidance, including package installation and environment configuration.
  • Show package installation using 'dotnet' CLI (e.g., 'dotnet add package ...') instead of PowerShell.
  • Add screenshots or terminal examples from Linux/macOS environments.
  • Clarify that .NET Core and Bot Framework SDK are cross-platform and provide links to relevant documentation.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page displays a moderate Windows bias. It mentions assigning delegates using the Microsoft Teams Client or Teams PowerShell, both of which are primarily Windows-centric tools. No Linux/macOS alternatives or CLI examples are provided. The prerequisites and instructions reference Windows tools first and exclusively, potentially creating friction for Linux/macOS users.
Recommendations
  • Include instructions or examples for assigning delegates using cross-platform tools, such as Teams web client or REST APIs, if available.
  • Explicitly state whether Teams PowerShell can be used on Linux/macOS (via PowerShell Core), and provide installation guidance if so.
  • Add notes or links for Linux/macOS users on how to perform equivalent actions.
  • Where possible, provide parity in examples and tool recommendations for all supported platforms.
GitHub Create Pull Request
Communication Services include file ...tion-services/quickstarts/chat/includes/chat-csharp.md
Medium Priority View Details →
Scanned: 2026-01-14 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 moderate Windows bias. Visual Studio is listed as a prerequisite without mention of cross-platform alternatives, and PowerShell is used in the package installation example. While some commands (dotnet CLI) are cross-platform, references to Windows tools and environments (cmd, PowerShell) are given before Bash, and Linux/macOS-specific instructions or alternatives are missing. There are no explicit Linux/macOS setup or troubleshooting notes.
Recommendations
  • Mention cross-platform IDEs (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
  • Provide explicit Bash/Linux/macOS command examples for package installation and running the app.
  • List Bash and Linux/macOS terminal options before or alongside Windows (cmd, PowerShell) in setup instructions.
  • Add notes about .NET SDK installation on Linux/macOS.
  • Include troubleshooting tips for Linux/macOS users if relevant.
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-14 00:00
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-specific tools (PowerShell, setx) and patterns are presented first or exclusively in some sections, such as environment variable setup and CLI installation. PowerShell is used for CLI examples, and Windows instructions are often listed before Linux/macOS equivalents. However, Linux/macOS instructions are present and reasonably complete, so Linux users can follow along with some friction.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, not after.
  • Use generic shell/CLI examples (bash) where possible, or provide equal prominence to bash and PowerShell.
  • Link to cross-platform CLI installation guides, not just Windows-specific ones.
  • Avoid using Windows-specific tools (e.g., setx) as the primary example for environment variables; show bash/zsh examples first or equally.
  • Ensure all code blocks are labeled appropriately for platform clarity.
GitHub Create Pull Request
Communication Services Prerequisites ...des/create-azure-managed-domain-resource-powershell.md
Medium Priority View Details →
Scanned: 2026-01-14 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 or Bash. Windows tools and patterns are mentioned exclusively and first, creating friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI examples for all operations (login, resource creation, management, deletion).
  • Explicitly mention cross-platform support and provide guidance for Linux/macOS users.
  • Include Bash or shell script examples where appropriate.
  • Clarify whether the Az PowerShell Module can be used on Linux/macOS, and if so, provide installation instructions for those platforms.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways: PowerShell is presented as a primary automation option, and DNS record instructions for 'Other (General)' link to a Windows-based DNS guide, with no mention of Linux/BIND or macOS equivalents. Windows tools and patterns are referenced, and Linux/macOS-specific guidance is missing. The order of pivots and examples tends to favor Windows technologies (Azure portal, PowerShell) before Linux-friendly options (Azure CLI).
Recommendations
  • Add explicit instructions or links for managing DNS records using Linux tools (e.g., BIND, `dig`, `nsupdate`) and macOS equivalents.
  • Provide parity in examples for Linux/macOS users, such as shell commands for DNS configuration and verification.
  • Reorder pivots or examples so that cross-platform tools (Azure CLI) are shown before or alongside Windows-specific tools (PowerShell).
  • Clarify that PowerShell is available cross-platform, but also offer bash/zsh alternatives where appropriate.
  • Replace or supplement the 'Other (General)' DNS guide with instructions for Linux-based DNS servers.
GitHub Create Pull Request
Communication Services include file ...ail-advanced/includes/inline-attachments-powershell.md
Medium Priority View Details →
Scanned: 2026-01-14 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 PowerShell syntax and commands, and the prerequisite explicitly refers to 'windows powershell'. There are no Linux/macOS equivalents, nor is there mention of cross-platform alternatives such as Azure CLI or Bash. This creates friction for non-Windows users and may prevent them from completing the task without significant adaptation.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI, which is cross-platform.
  • Clarify whether the Azure PowerShell module can be used on Linux/macOS (with PowerShell Core), and provide installation instructions for those platforms.
  • Include Bash or shell script examples for file handling and email sending where possible.
  • Rephrase prerequisites and checks to be platform-neutral (e.g., 'in a terminal' instead of 'in a windows powershell').
  • Add notes or links for Linux/macOS users about how to adapt the PowerShell commands or use alternative tools.
GitHub Create Pull Request
Communication Services Prerequisites ...rts/email/includes/create-email-resource-powershell.md
Medium Priority View Details →
Scanned: 2026-01-14 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 or Bash, and Windows tooling is mentioned first and exclusively. This creates friction for non-Windows users and may prevent them from easily following the guide.
Recommendations
  • Add equivalent Azure CLI examples for all resource management tasks (e.g., az communication email commands).
  • Include installation instructions for Azure CLI on Linux/macOS.
  • Clearly state cross-platform options at the beginning of the documentation.
  • Provide Bash or shell script examples where appropriate.
  • Reorganize examples so that Windows and Linux/macOS instructions are presented with equal prominence.
GitHub Create Pull Request
Communication Services Prerequisites ...includes/create-sender-username-resource-powershell.md
Medium Priority View Details →
Scanned: 2026-01-14 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 guidance for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform alternatives. The documentation assumes familiarity with Windows tooling and does not mention Linux-specific installation or usage patterns.
Recommendations
  • Add equivalent Azure CLI commands for all operations (login, resource creation, update, listing, deletion).
  • Include installation instructions for Azure CLI and Az.Communication module on Linux/macOS.
  • Provide Bash or shell script examples alongside PowerShell.
  • Explicitly state cross-platform compatibility of the Az PowerShell module, if applicable, or guide users to alternatives.
  • Reorder examples to present cross-platform (CLI) options before or alongside PowerShell.
GitHub Create Pull Request
Communication Services include file ...-services/quickstarts/email/includes/send-email-net.md
Medium Priority View Details →
Scanned: 2026-01-14 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 console environments (cmd, PowerShell) before mentioning Bash, and by omitting explicit Linux/macOS instructions or examples. All code samples and commands are .NET/C# focused, which is cross-platform, but there are no examples or troubleshooting notes tailored for Linux/macOS users. The instructions assume familiarity with Windows tools and patterns, such as the Azure portal navigation, without clarifying differences for other platforms.
Recommendations
  • Explicitly mention Linux/macOS compatibility for all commands and steps, especially for .NET CLI usage.
  • Provide Linux/macOS-specific instructions for environment variable setup, file editing, and running commands.
  • List Bash (and other Unix shells) first or equally alongside Windows consoles when referring to terminal usage.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, path differences, dependency installation).
  • Include sample screenshots or terminal outputs from Linux/macOS environments.
GitHub Create Pull Request
Communication Services include file ...es/quickstarts/email/includes/send-email-powershell.md
Medium Priority View Details →
Scanned: 2026-01-14 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 reference running commands in 'windows PowerShell'. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform scripting. The installation instructions and module usage are Windows-centric, and Linux alternatives are not mentioned.
Recommendations
  • Add equivalent instructions and examples for Linux/macOS users, such as using Azure CLI or cross-platform PowerShell (pwsh).
  • Clarify that Azure PowerShell can be installed and used on Linux/macOS, and provide installation steps for those platforms.
  • Include Bash or Azure CLI examples for sending emails, if supported.
  • Avoid language like 'In a windows PowerShell' and use 'In PowerShell' or specify platform-neutral instructions.
  • Explicitly mention platform compatibility for all tools and commands.
GitHub Create Pull Request
Communication Services Prerequisites ...vents/includes/create-event-subscription-powershell.md
Medium Priority View Details →
Scanned: 2026-01-14 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 Azure PowerShell commands for all tasks, with no mention of Azure CLI, Bash, or cross-platform alternatives. All examples and instructions are PowerShell-centric, which is primarily associated with Windows environments. There are no Linux/macOS-specific instructions or examples, and the prerequisite section only references PowerShell installation.
Recommendations
  • Add equivalent Azure CLI examples for all operations (create, list, update, delete event subscriptions).
  • Include installation instructions for Azure CLI and note its cross-platform compatibility.
  • Explicitly mention that PowerShell is available on Linux/macOS, or provide Bash script examples.
  • Reorder examples so that CLI or cross-platform options are presented first or alongside PowerShell.
  • Clarify any platform-specific limitations or differences.
GitHub Create Pull Request
Communication Services Subscribe to events ...ion-services/quickstarts/events/subscribe-to-events.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for Azure portal, Azure CLI, and PowerShell, but PowerShell is a Windows-centric tool and is presented as a primary option. There is no explicit mention of Linux/macOS alternatives for scripting (e.g., Bash), and the CLI example is not clearly prioritized over PowerShell. The .NET SDK is referenced, which is cross-platform, but no explicit Linux/macOS command-line patterns or examples are given.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and provide explicit Bash/Linux/macOS shell examples where relevant.
  • De-emphasize PowerShell as the primary scripting example, or provide Bash equivalents alongside PowerShell commands.
  • Add a section or note for Linux/macOS users, clarifying tool compatibility and offering platform-specific guidance.
  • Ensure that examples and instructions do not assume a Windows environment unless strictly necessary.
GitHub Create Pull Request
Communication Services Additional Prerequisites ...ity/includes/active-directory/service-principal-cli.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page consistently references Windows-specific resources and examples first, such as links to configuring managed identities for Windows VMs via Azure Portal, PowerShell, CLI, ARM templates, and SDKs. There is a notable absence of Linux/macOS-specific instructions or parity in example ordering. The guidance for setting environment variables is generic, but the overall framing and linked resources are Windows-centric.
Recommendations
  • Include equivalent links and examples for Linux/macOS environments (e.g., configuring managed identities for Linux VMs).
  • Present cross-platform instructions and links in parallel, or alternate the order to avoid Windows-first bias.
  • Explicitly mention that the Azure CLI and environment variable steps apply equally to Linux/macOS, and provide any OS-specific caveats if relevant.
  • Add examples or notes for setting environment variables in Linux/macOS shells (e.g., export commands for Bash/zsh).
GitHub Create Pull Request
Communication Services Prerequisites ...ces/quickstarts/includes/create-resource-powershell.md
Medium Priority View Details →
Scanned: 2026-01-14 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 PowerShell modules, which are traditionally associated with Windows. There are no examples or instructions for using Azure CLI or Bash, which are more common on Linux/macOS. The documentation also links to PowerShell-specific resources and does not mention cross-platform alternatives or clarify PowerShell's availability on non-Windows systems.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples for all resource management tasks.
  • Explicitly state that PowerShell Core is available on Linux/macOS, if PowerShell must be used.
  • Provide links to Azure CLI documentation and reference CLI commands alongside PowerShell commands.
  • Reorder examples so that cross-platform tools (Azure CLI, Bash) are shown first or in parallel with PowerShell.
GitHub Create Pull Request
Communication Services include file ...ion-services/quickstarts/sms/includes/send-sms-java.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides command-line examples for both Windows Command Prompt and PowerShell, but does not include explicit Linux/macOS shell examples. Windows-specific shells are mentioned first and exclusively, which may create friction for Linux/macOS users who use Bash or other shells.
Recommendations
  • Add explicit Bash/Linux/macOS terminal examples alongside Command Prompt and PowerShell examples.
  • Clarify that the Maven commands work in Bash and other Unix-like shells, and provide sample syntax.
  • Reorder examples or present all platforms equally (e.g., 'Windows (Command Prompt), Windows (PowerShell), Linux/macOS (Bash)').
  • Note any platform-specific differences in command syntax or environment setup.
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-14 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 for associating Teams resource accounts and hosting DevTunnels are provided only with PowerShell commands, with no Linux/macOS CLI or shell alternatives. References to Teams resource account creation and management link exclusively to PowerShell modules, and no mention is made of Linux-compatible tools or workflows. Windows-centric tools and patterns are presented first and exclusively, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Bash/CLI commands for associating Teams resource accounts and hosting DevTunnels, or explicitly document cross-platform alternatives.
  • Include links to Linux/macOS compatible tools or instructions for creating Teams resource accounts and managing Azure DevTunnels.
  • Clarify platform requirements for PowerShell commands and offer installation guidance for PowerShell Core on Linux/macOS if necessary.
  • Add explicit notes or sections for Linux/macOS users to ensure parity and reduce ambiguity.
GitHub Create Pull Request
Communication Services Teams Phone Extensibility ...uickstarts/tpe/teams-phone-extensibility-quickstart.md
Medium Priority View Details →
Scanned: 2026-01-14 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 exhibits a notable Windows bias, primarily through exclusive use of PowerShell cmdlets and Windows-centric tools for provisioning Teams Resource Accounts and phone numbers. All administrative examples use PowerShell commands, with no mention of Linux/macOS alternatives (such as Bash, Azure CLI, or cross-platform scripting). Windows tools and patterns (e.g., Teams PowerShell, MicrosoftTeamsPowerShell, Teams Admin Center) are referenced exclusively or before any cross-platform options. There are no Linux/macOS-specific instructions or examples, which may impede non-Windows users from completing critical setup steps.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for all PowerShell cmdlets, especially for provisioning Teams Resource Accounts and assigning phone numbers.
  • Explicitly state platform requirements and offer guidance for Linux/macOS users (e.g., running PowerShell Core, using Azure CLI, or REST endpoints).
  • Add cross-platform installation instructions for required modules and tools.
  • Reorder examples to present cross-platform solutions first or alongside Windows-specific instructions.
  • Reference official Microsoft documentation for Teams administration via Azure CLI or REST API where available.
GitHub Create Pull Request
← Previous Page 14 of 27 Next →