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 126-150 of 656 flagged pages
Communication Services Microsoft Teams shared line appearance ...pts/interop/teams-user/teams-shared-line-appearance.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (Teams PowerShell) for delegate assignment and listing them before any Linux alternatives. There are no Linux-specific instructions or examples for managing shared line appearance, and the only command-line tool mentioned is PowerShell, which is primarily a Windows technology. The prerequisites and platform capabilities do not mention Linux or cross-platform CLI options, and the guidance assumes use of Microsoft Teams Client or Teams PowerShell, both of which are Windows-centric.
Recommendations
  • Include instructions or examples for assigning delegates using cross-platform tools, such as Azure CLI or REST APIs, if available.
  • Explicitly mention whether Teams PowerShell can be used on Linux (via PowerShell Core), and provide Linux-specific setup steps if possible.
  • Add parity by listing Linux-compatible methods for managing shared line appearance, or clarify platform limitations.
  • Where possible, provide examples using generic scripting or automation tools that work across Windows, Linux, and macOS.
  • Ensure that any references to tools or clients are accompanied by notes about their platform compatibility.
GitHub Create Pull Request
Communication Services Calling capabilities for Teams users ...cation-services/concepts/interop/teams-user-calling.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing 'Windows' as a primary platform in feature tables, with no mention of Linux desktop support or parity. Windows is presented as a distinct platform alongside JavaScript, Android, and iOS, but Linux is omitted entirely. Additionally, references to Microsoft Entra and PowerShell modules (e.g., /powershell/module/microsoft.graph.users/get-mguser) reinforce Windows-centric tooling. There are no Linux-specific examples, instructions, or mentions of Linux compatibility, leaving Linux users uncertain about support or usage.
Recommendations
  • Add explicit Linux desktop support information to feature tables, or clarify if Linux is unsupported.
  • Provide Linux-specific examples, instructions, or troubleshooting guidance where relevant.
  • Reference cross-platform tools and APIs (e.g., Microsoft Graph REST API) before or alongside Windows/PowerShell tools.
  • Include parity notes for Linux users, such as alternative methods for device management or authentication.
  • If Linux is not supported, clearly state this in the documentation to avoid ambiguity.
GitHub Create Pull Request
Communication Services Teams Phone extensibility overview ...epts/interop/tpe/teams-phone-extensibility-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in its references to Teams administration and provisioning. It mentions the use of PowerShell cmdlets and the TAC (Teams Admin Center) portal for configuration and policy assignment, with no mention of Linux-compatible alternatives or cross-platform CLI tools. There are no examples or guidance for Linux users, nor are Linux administration patterns or tools referenced. The documentation assumes a Windows-centric environment for Teams Phone extensibility setup and management.
Recommendations
  • Include cross-platform CLI examples, such as Azure CLI or REST API calls, for provisioning and policy management.
  • Explicitly mention whether PowerShell cmdlets can be run on Linux/macOS (via PowerShell Core), and provide installation guidance if so.
  • Add references to Linux-compatible tools or workflows for Teams administration, or clarify any limitations.
  • Provide parity in examples and instructions for both Windows and Linux environments, especially for tasks like license assignment, policy configuration, and resource provisioning.
  • Where GUI tools (TAC portal) are mentioned, clarify browser compatibility and platform independence.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates Windows bias in the prerequisites section by referencing Teams deployment and user enablement steps that rely on Windows-specific tools and patterns. Specifically, it links to Teams installation instructions (which are Windows-centric) and directs users to enable Enterprise Voice via PowerShell, a Windows-only tool, without mentioning Linux alternatives or cross-platform options. No Linux equivalents or parity guidance are provided for these steps.
Recommendations
  • Include instructions or links for Teams deployment on non-Windows platforms, such as macOS and Linux, if available.
  • Provide alternative methods for enabling Teams Phone and Enterprise Voice for users who do not have access to PowerShell, such as using the Teams Admin Center web interface.
  • Explicitly state platform requirements or limitations for steps that are Windows-only, and suggest workarounds or alternatives for Linux users.
  • Add a note clarifying that PowerShell is a Windows tool and provide guidance for Linux users (e.g., using Azure Cloud Shell or web-based admin portals where possible).
GitHub Create Pull Request
Communication Services SDKs and REST APIs for Azure Communication Services ...rticles/communication-services/concepts/sdk-options.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Platform support details for .NET and Calling SDKs are Windows-centric, listing Windows versions and tools first and in more detail, with Linux and Mac mentioned only as part of .NET Standard support and without specific guidance or examples. There are no Linux-specific usage examples, troubleshooting steps, or parity in platform support explanations. Windows tools and deployment patterns (UWP, WinUI3) are described in detail, while Linux equivalents are not covered.
Recommendations
  • Add explicit Linux platform support details, including supported distributions and troubleshooting steps for Linux environments.
  • Provide Linux-specific examples and usage patterns, such as command-line instructions for SDK installation and REST API usage on Linux.
  • Ensure platform support tables and lists mention Linux and Mac platforms with the same level of detail as Windows.
  • Include guidance for deploying and running SDKs and REST API clients on Linux, including common issues and solutions.
  • Avoid listing Windows tools and patterns first; present platform support in a neutral or alphabetical order.
GitHub Create Pull Request
Communication Services Chat Hero Sample ...les/communication-services/samples/chat-hero-sample.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows terminals (PowerShell, Windows Terminal, Command Prompt) first and exclusively in the instructions for opening a terminal, without mentioning Linux or macOS equivalents (such as Bash, Terminal, or iTerm). There are no Linux-specific setup instructions or examples, and the workflow assumes familiarity with Windows tools and patterns.
Recommendations
  • Explicitly mention Linux and macOS terminal options (e.g., Bash, Terminal, iTerm) alongside Windows terminals.
  • Add notes or examples for Linux/macOS users, such as file path conventions and environment setup differences.
  • Ensure instructions (such as editing appsettings.json) clarify that the process is the same across platforms, or highlight any platform-specific steps.
  • Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, npm compatibility).
GitHub Create Pull Request
Communication Services Tutorial - Integrate Microsoft Teams breakout rooms ...nication-services/how-tos/calling-sdk/breakoutrooms.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through its exclusive reference to Windows-centric tools (such as PowerShell for Teams meeting policy management) and the absence of Linux equivalents or cross-platform alternatives. The documentation links only to PowerShell modules for policy configuration, without mentioning or providing examples for Linux or macOS administrators. There are no CLI or REST API alternatives discussed, and no Linux-specific instructions or examples are provided.
Recommendations
  • Include cross-platform alternatives for Teams meeting policy management, such as Microsoft Graph API or Azure CLI, with example commands for Linux/macOS.
  • Add explicit instructions or examples for Linux and macOS environments where administrative tasks are required.
  • Where PowerShell is referenced, clarify whether the same functionality is available via other tools, and provide links or code samples for those.
  • Review SDK support tables to ensure that Linux desktop environments are considered and documented if supported.
  • Add a section addressing platform parity and how users on non-Windows systems can accomplish required tasks.
GitHub Create Pull Request
Communication Services Tutorial - Teams Shared Line Appearance ...ices/how-tos/cte-calling-sdk/shared-line-appearance.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Teams PowerShell and Microsoft Teams Client (Windows-centric tools) as the primary methods for assigning delegates, without mentioning Linux or cross-platform alternatives. No Linux-specific instructions, examples, or equivalent tooling are provided, and the SDK support table lists 'Windows' as a platform but does not mention Linux or macOS. The order of presentation also places Windows tools before any potential cross-platform options.
Recommendations
  • Include instructions or examples for assigning delegates using cross-platform tools (e.g., Azure CLI, REST API, or web interfaces) if available.
  • Explicitly mention the availability (or lack) of Linux/macOS support for Teams PowerShell and Teams Client, and suggest alternatives for non-Windows users.
  • Add SDK support information for Linux and macOS platforms in the support table.
  • Provide parity in examples and tooling references for Linux users, or clarify platform limitations where Windows-only tools are referenced.
GitHub Create Pull Request
Communication Services include file ...tion-services/quickstarts/chat/includes/chat-csharp.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows tools (Visual Studio) as a prerequisite without mentioning Linux alternatives, presenting PowerShell as the default for package installation, and referencing Windows console environments (cmd, PowerShell) before Bash. There is a lack of explicit Linux instructions or examples, and no mention of Linux IDEs or editors.
Recommendations
  • Include Linux-friendly prerequisites, such as VS Code or JetBrains Rider, and instructions for installing .NET SDK on Linux.
  • Provide package installation commands using Bash or generic shell syntax, not just PowerShell.
  • List Bash or Linux terminal environments before or alongside Windows ones when giving console instructions.
  • Add notes about running the sample code on Linux, including any platform-specific considerations.
  • Ensure links to IDEs or tools include cross-platform options.
GitHub Create Pull Request
Communication Services Create a Communication Services resource in Azure Communication Services ...-services/quickstarts/create-communication-resource.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation shows evidence of Windows bias, primarily by presenting Windows-specific instructions and tools before Linux equivalents, using PowerShell and Windows console commands prominently, and referencing Windows tools (e.g., Visual Studio, setx) before alternatives. While Linux/macOS instructions are present, they are often listed after Windows and sometimes lack parity in detail or context.
Recommendations
  • Present platform instructions in parallel or in a neutral order (e.g., alphabetical or grouped together), rather than listing Windows first.
  • Ensure Linux/macOS examples are as detailed and context-rich as Windows examples, including references to common Linux editors and IDEs.
  • Avoid using Windows-specific tools (e.g., setx, Visual Studio) as the default or primary example; provide equivalent Linux/macOS tools and editors.
  • Where possible, use cross-platform commands (e.g., az CLI) and clarify platform-specific differences only when necessary.
  • Explicitly mention Linux and macOS support in introductory sections to reinforce parity.
GitHub Create Pull Request
Communication Services Add custom verified email domains ...vices/quickstarts/email/add-custom-verified-domains.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page shows evidence of Windows bias. It includes a dedicated PowerShell section and references to Windows-based DNS management in the 'Other (General)' CNAME records guide. There is no explicit mention of Linux command-line tools or examples for DNS management, and the only OS-specific DNS guide is for Windows. The inclusion of PowerShell as a primary automation option further emphasizes Windows-centric tooling, while Linux alternatives (such as Bash, dig, or nsupdate) are absent.
Recommendations
  • Add Linux-specific examples for DNS record management, such as using BIND, nsupdate, or editing /etc/bind/zones files.
  • Provide parity for PowerShell by including Bash/Azure CLI scripts for common tasks.
  • Include a general guide for managing DNS records on Linux-based DNS servers.
  • Reference cross-platform tools (e.g., Azure CLI) before or alongside Windows/PowerShell options.
  • Ensure that documentation links for 'Other (General)' DNS management cover both Windows and Linux environments.
GitHub Create Pull Request
Communication Services Prerequisites ...des/create-azure-managed-domain-resource-powershell.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module, which is traditionally associated with Windows environments. There are no examples or instructions for Linux users, such as using Azure CLI or Bash. The documentation assumes familiarity with Windows tooling and does not mention cross-platform alternatives or provide parity for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI examples for all operations (login, module installation, resource creation, management, and deletion).
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or provide Bash script examples.
  • Include a section on cross-platform usage, clarifying which commands/tools work on Windows, Linux, and macOS.
  • Reference Linux-specific documentation or guides where appropriate.
  • Avoid assuming the use of Windows paths (e.g., 'PS C:\>') and use generic prompts or platform-neutral examples.
GitHub Create Pull Request
Communication Services Prerequisites ...rts/email/includes/create-email-resource-powershell.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell commands and references Windows-centric tools and patterns (e.g., PS prompt, PowerShell modules). There are no examples or instructions for Linux or macOS users, such as Azure CLI or Bash equivalents. The documentation assumes a Windows environment throughout, which may hinder accessibility for users on other platforms.
Recommendations
  • Provide equivalent Azure CLI commands for all resource management tasks.
  • Include installation instructions for Azure CLI on Linux/macOS.
  • Add Bash or shell script examples alongside PowerShell commands.
  • Clearly indicate cross-platform compatibility of Azure tools.
  • Reorganize sections to present both Windows and Linux/macOS options in parallel, or note platform-specific steps where necessary.
GitHub Create Pull Request
Communication Services Prerequisites ...es/create-custom-managed-domain-resource-powershell.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows 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 guidance for Linux users, such as using Azure CLI, Bash, or cross-platform tools. The documentation assumes familiarity with Windows-centric tools and patterns, potentially excluding or confusing users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all resource management tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include installation instructions for Azure CLI alongside PowerShell, and clarify which tools are supported on each OS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, but provide CLI/Bash alternatives for parity.
  • Reorder examples so that cross-platform tools (e.g., Azure CLI) are presented first or alongside PowerShell to avoid Windows-first bias.
  • Add a section or note addressing Linux/macOS users, with links to relevant documentation for their platforms.
GitHub Create Pull Request
Communication Services Prerequisites ...includes/create-sender-username-resource-powershell.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows 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. No examples or guidance are provided for Linux users, such as using Azure CLI or Bash, and Windows-centric tools and patterns are mentioned first and exclusively throughout the page.
Recommendations
  • Add equivalent Azure CLI examples for all operations (login, resource creation, update, listing, deletion) to support Linux and macOS users.
  • Explicitly mention cross-platform options (e.g., Azure CLI, Bash) in the prerequisites and instructions.
  • Clarify which commands are cross-platform and provide installation instructions for Linux/macOS where relevant.
  • Reorder sections or provide parallel examples so that Linux/macOS options are not secondary to Windows/PowerShell.
  • Add notes or links to documentation for using these tools on non-Windows platforms.
GitHub Create Pull Request
Communication Services include file ...uickstarts/email/includes/send-email-async-sync-net.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a bias towards Windows environments and tooling. Examples and instructions are exclusively for C#/.NET, with all commands using the 'dotnet' CLI and references to Windows-centric consoles (cmd, PowerShell) before Bash. There are no Linux-specific instructions, troubleshooting notes, or parity examples for Linux users. The documentation assumes familiarity with Windows tools and patterns, and does not mention cross-platform considerations for .NET or Azure SDK usage.
Recommendations
  • Explicitly mention that the .NET SDK and 'dotnet' CLI are cross-platform and provide installation instructions for Linux (e.g., apt-get, yum, snap).
  • List Bash and Linux terminal examples before or alongside Windows (cmd, PowerShell) examples.
  • Include troubleshooting notes for common Linux issues (e.g., permissions, environment variable setup).
  • Provide links to Linux-specific documentation for .NET and Azure Communication Services.
  • Clarify any OS-specific differences in environment variable setup, file paths, or execution commands.
  • Add sample code or quickstart instructions for Linux users, including screenshots or terminal output from a Linux environment.
GitHub Create Pull Request
Communication Services include file ...-services/quickstarts/email/includes/send-email-net.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a bias toward Windows environments and tooling. All examples and instructions are exclusively for .NET/C# and use commands (dotnet new, dotnet build, dotnet run) that are most commonly associated with Windows development. The console window examples mention cmd and PowerShell before Bash, and there are no Linux-specific instructions, troubleshooting steps, or alternative code samples (e.g., for Linux shell environments, Mono, or cross-platform editors). There is no mention of Linux package managers, nor any explicit guidance for Linux users.
Recommendations
  • Add explicit Linux instructions and examples, such as using Bash and Linux terminals.
  • Include troubleshooting tips for common Linux issues (e.g., permissions, environment variables).
  • Mention cross-platform editors (e.g., VS Code) and how to run .NET code on Linux.
  • Provide parity in command examples (e.g., show dotnet commands in both Windows cmd/PowerShell and Linux Bash contexts).
  • Reference Linux package managers (apt, yum) for installing .NET Core if not already present.
  • Clarify that the .NET SDK and Azure Communication Services Email client library are cross-platform and provide links to Linux-specific installation guides.
GitHub Create Pull Request
Communication Services include file ...es/quickstarts/email/includes/send-email-powershell.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses Azure PowerShell for all examples and instructions, with explicit references to Windows PowerShell and Windows-specific module installation. There are no examples or guidance for using Linux or cross-platform tools (such as Azure CLI or REST API), nor any mention of Linux shell equivalents. The documentation assumes a Windows environment and does not address Linux users or provide parity for non-Windows platforms.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Provide REST API or SDK (e.g., Python, Node.js) examples for sending emails, which are platform-agnostic.
  • Include installation instructions for Azure PowerShell on Linux and macOS, or clarify cross-platform support.
  • Explicitly mention that the functionality is available on non-Windows platforms, if applicable, and provide troubleshooting tips for Linux users.
  • Reorder prerequisites and examples to avoid Windows-first bias, and ensure Linux users are addressed equally.
GitHub Create Pull Request
Communication Services include file ...ail-advanced/includes/inline-attachments-powershell.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses Windows PowerShell for all examples and instructions, with no mention of Linux or cross-platform alternatives. Prerequisite checks and module installation steps are described only for Windows PowerShell, and there are no Bash, Azure CLI, or other Linux-friendly examples. The page assumes the user is on Windows and familiar with PowerShell, which may exclude Linux and macOS users.
Recommendations
  • Add equivalent instructions and examples for Linux and macOS users, using Bash and/or Azure CLI.
  • Clarify whether the Azure PowerShell module is supported on non-Windows platforms and provide installation steps for those platforms if applicable.
  • Include cross-platform code samples, or at least mention how to adapt PowerShell scripts for PowerShell Core on Linux/macOS.
  • List prerequisites and checks for Linux and macOS environments, such as verifying module installation in PowerShell Core or using Azure CLI.
  • Consider providing a table or section comparing Windows and Linux/macOS setup steps for Azure Communication Services email sending.
GitHub Create Pull Request
Communication Services Enable interoperability in your Teams tenant ...s/includes/enable-interoperability-for-teams-tenant.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell commands and references Windows-centric tools (MicrosoftTeams PowerShell module), with no mention of Linux-compatible alternatives or cross-platform instructions. All examples and setup steps assume a Windows environment, omitting guidance for Linux or macOS users.
Recommendations
  • Provide equivalent instructions for Linux and macOS users, such as using Azure CLI or cross-platform PowerShell Core.
  • Clarify whether the MicrosoftTeams PowerShell module can be installed and used on non-Windows platforms, and provide installation steps if possible.
  • Include notes or sections on platform compatibility and any limitations for Linux/macOS users.
  • Offer alternative command-line examples (e.g., Bash, Azure CLI) where feasible.
  • Explicitly state prerequisites for each platform and link to relevant cross-platform documentation.
GitHub Create Pull Request
Communication Services Teams Phone extensibility FAQ .../concepts/interop/tpe/teams-phone-extensibility-faq.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (Teams Admin Center portal and PowerShell cmdlets) as the primary or only methods for configuration, particularly for emergency calling policies. No Linux equivalents or cross-platform alternatives are mentioned, and Windows-centric administration patterns are presented first and exclusively. There are no examples or instructions for Linux users, nor is there guidance for cross-platform administration.
Recommendations
  • Include instructions or examples for configuring Teams Phone extensibility features using cross-platform tools, such as Microsoft Graph API, which can be used from Linux and macOS.
  • Explicitly mention whether PowerShell cmdlets can be run on Linux/macOS (using PowerShell Core), and provide relevant guidance if so.
  • Add references to cross-platform administration options, such as web-based portals or REST APIs, and clarify their availability and parity with Windows tools.
  • Where possible, provide Linux/macOS-specific examples or note any limitations for non-Windows environments.
  • Review all tool and pattern mentions to ensure Linux parity and avoid presenting Windows tools as the only or default option.
GitHub Create Pull Request
Communication Services Plan user experience for virtual appointments ...oncepts/interop/virtual-visits/plan-user-experience.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation references Microsoft Teams Admin Center and PowerShell as primary methods for configuration, both of which are Windows-centric tools. No Linux equivalents or cross-platform alternatives are mentioned, and examples or guidance for Linux users are absent. The order of presentation also places Windows tools first, reinforcing a Windows-first perspective.
Recommendations
  • Include instructions or references for configuring Teams using cross-platform tools, such as Microsoft Graph API, CLI, or web interfaces accessible from Linux.
  • Explicitly mention whether PowerShell commands can be run on Linux (e.g., via PowerShell Core) and provide Linux-specific examples where possible.
  • Add parity by listing Linux-friendly methods for managing Teams policies and configurations, such as using REST APIs or web portals.
  • Ensure that examples and tool references are balanced between Windows and Linux environments, or clarify platform requirements where applicable.
GitHub Create Pull Request
Communication Services Teams Phone extensibility Troubleshooting ...terop/tpe/teams-phone-extensibility-troubleshooting.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias primarily in the troubleshooting steps for Microsoft Entra App permissions, where only PowerShell commands and modules are provided for resolving service principal issues. There are no equivalent instructions or examples for Linux or cross-platform environments (e.g., Azure CLI, Bash, or REST API). The use of PowerShell and references to installing PowerShell modules assume a Windows environment and administrator privileges, potentially excluding users on Linux or macOS. Additionally, the troubleshooting workflow for licensing and admin tasks is centered around the Microsoft 365 Admin Center, which is web-based but often referenced in Windows-centric enterprise contexts.
Recommendations
  • Provide equivalent troubleshooting steps using Azure CLI, Microsoft Graph API, or Bash scripts that work on Linux/macOS.
  • Include cross-platform instructions for connecting to Microsoft Entra ID and creating service principals, such as using az ad sp create or Microsoft Graph REST API.
  • Add notes clarifying that PowerShell commands can be run on Linux/macOS with PowerShell Core, or provide links to installation guides for non-Windows platforms.
  • Where possible, present cross-platform tools and examples before or alongside Windows/PowerShell instructions.
  • Review other troubleshooting steps for implicit Windows assumptions and add Linux/macOS alternatives where relevant.
GitHub Create Pull Request
Communication Services Pricing for Teams interop scenarios ...ion-services/concepts/pricing/teams-interop-pricing.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation demonstrates Windows bias by referencing Windows-specific tools (e.g., PowerShell cmdlets like Set-CsPhoneNumberAssignment) and mentioning the Teams Desktop client (implicitly Windows) before other platforms. The instructions for enabling Teams Phone features rely on PowerShell, with no Linux or cross-platform alternatives provided. Examples and scenarios mention Windows explicitly (e.g., 'Windows, Chrome browser') and do not provide parity for Linux users or administrators.
Recommendations
  • Provide equivalent instructions for Linux and macOS administrators, such as using Microsoft Graph API or Azure CLI for license assignment and configuration.
  • Clarify that Teams Desktop client is available on multiple platforms and provide explicit examples for Linux and macOS clients.
  • Avoid referencing Windows-specific tools (e.g., PowerShell) as the only method for configuration; include cross-platform alternatives.
  • Ensure that usage scenarios and cost calculations mention Linux and macOS clients where applicable, not just Windows.
  • Add documentation links and examples for Linux-compatible management tools and SDKs.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a Windows bias primarily through the exclusive use of PowerShell cmdlets (Set-CsTeamsAcsFederationConfiguration, Set-CsExternalAccessPolicy) for tenant and user policy configuration, without mentioning or providing equivalent Linux/macOS alternatives or guidance. The prerequisite steps and administrative instructions assume access to Windows-based tools, and no cross-platform command-line examples (such as Azure CLI, Bash, or REST API alternatives) are provided for these critical setup steps. The programming language examples themselves are cross-platform, but the administrative setup is Windows-centric.
Recommendations
  • Provide Azure CLI or REST API equivalents for PowerShell cmdlets used in tenant and user policy configuration, or clarify if these operations are only possible via PowerShell.
  • Explicitly mention platform requirements for administrative steps, and offer guidance for Linux/macOS users (e.g., using Azure Cloud Shell, remote PowerShell, or web-based portals).
  • Add notes or links to documentation on performing administrative tasks via the Azure Portal or Microsoft Teams Admin Center, which are accessible from any OS.
  • Ensure that all critical setup steps have cross-platform instructions or alternatives, especially for environments where PowerShell is not available.
GitHub Create Pull Request
← Previous Page 6 of 27 Next →