Communication Services
2083
Total Pages
1869
Linux-Friendly Pages
214
Pages with Bias
10.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
367 issues found
Showing 26-50 of 367 flagged pages
Communication Services
Send an email using Azure Communication Services
...communication-services/quickstarts/email/send-email.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page presents platform-specific pivots for Azure Portal, Azure CLI, .NET, JavaScript, Java, Python, Logic Apps, and PowerShell. PowerShell (a Windows-centric tool) is given its own pivot, and Windows tools (PowerShell, .NET) are represented prominently. There is no explicit mention of Linux shell examples (e.g., Bash), nor are Linux-specific tools or patterns highlighted. The ordering of pivots places Windows-centric options (PowerShell, .NET) before Linux-native alternatives, and there is no dedicated Linux section or parity for Linux command-line usage beyond Azure CLI.
Recommendations
- Add explicit Bash or Linux shell examples alongside PowerShell, especially for command-line operations.
- Ensure parity by providing Linux-specific troubleshooting steps and cleanup instructions.
- Reorder pivots or provide equal prominence to Linux-native tools (e.g., Bash, Azure CLI) before or alongside Windows-centric options.
- Mention cross-platform compatibility for SDKs and tools, clarifying usage on Linux systems.
- Include a dedicated section or pivot for Linux users, highlighting best practices and common patterns.
Create Pull Request
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively uses Azure PowerShell commands and modules for all examples and instructions, with no mention of Linux-native tools, Bash, Azure CLI, or cross-platform alternatives. The prerequisites and all code samples assume PowerShell usage, which is traditionally associated with Windows environments, and there is no guidance for Linux users or parity in tooling.
Recommendations
- Add equivalent Azure CLI examples for all operations (create, list, update, delete event subscriptions), as Azure CLI is cross-platform and widely used on Linux.
- Mention installation instructions for Azure CLI and/or Bash scripting alongside PowerShell in the prerequisites.
- Include notes or sections clarifying that PowerShell Core is available cross-platform, but also provide native Linux/Bash/CLI alternatives.
- Reorder or parallelize examples so that Linux-friendly tools (Azure CLI, Bash) are presented before or alongside PowerShell.
- Add troubleshooting or environment-specific notes for Linux users, such as authentication or module installation differences.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively uses PowerShell commands and references Windows-centric tooling (e.g., Azure Az PowerShell Module), with no mention or examples for Linux or cross-platform alternatives such as Azure CLI or Bash. All code samples and instructions are tailored for PowerShell, which is traditionally associated with Windows environments, and there is no guidance for users on Linux or macOS platforms.
Recommendations
- Add equivalent Azure CLI examples for all resource creation and management tasks.
- Explicitly mention cross-platform compatibility and provide instructions for Linux/macOS users.
- Include Bash shell examples where appropriate.
- Clarify when PowerShell commands can be run on non-Windows platforms (e.g., PowerShell Core on Linux/macOS), or suggest alternatives.
- Reorder sections to present cross-platform or CLI options before or alongside PowerShell instructions.
Communication Services
Set up and create access tokens for Teams users
...nication-services/quickstarts/manage-teams-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias towards Windows environments, particularly in the administrator troubleshooting section. PowerShell is the only command-line tool mentioned for resolving service principal issues, with no equivalent Bash or Azure CLI examples for Linux/macOS users. The instructions and troubleshooting steps assume the use of Windows tools and patterns, such as starting PowerShell as an administrator and installing PowerShell modules, without offering alternatives for non-Windows platforms. There is no mention of Linux or cross-platform approaches for these administrative tasks.
Recommendations
- Provide equivalent Azure CLI or Bash commands for service principal creation and troubleshooting steps, ensuring Linux/macOS users can follow along without PowerShell.
- Explicitly mention cross-platform alternatives where PowerShell is referenced, and clarify which steps are platform-agnostic.
- Add notes or sections indicating how to perform these administrative tasks on Linux and macOS, including installation and usage of required tools.
- Where possible, use Azure Portal or REST API instructions that are platform-independent.
- Review and update examples to ensure parity between Windows and Linux, especially in troubleshooting and setup steps.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides command-line examples specifically for Windows environments, listing Command Prompt and PowerShell commands, but does not include equivalent Linux/macOS shell examples (e.g., Bash). This prioritizes Windows usage and may hinder Linux users from following along easily.
Recommendations
- Add Bash (Linux/macOS) command examples alongside Command Prompt and PowerShell, especially for Maven commands.
- Explicitly mention that the commands work on Linux/macOS terminals and provide any necessary syntax adjustments (e.g., quoting).
- Ensure that all instructions referencing 'terminal or command window' clarify cross-platform compatibility.
- Consider listing Bash examples first or equally with Windows examples to avoid implicit prioritization.
Communication Services
Access a user's Teams Phone separate from their Teams client
...ts/tpe/teams-phone-extensibility-access-teams-phone.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation shows a Windows bias in several ways: the only explicit UI instructions for enabling Teams users refer to the Microsoft 365 admin center, which is primarily accessed via a web interface but is often associated with Windows environments. The only command-line tool mentioned for obtaining a Resource Account ObjectId is the MicrosoftTeams PowerShell cmdlet (Get-CsOnlineApplicationInstance), with no mention of equivalent Graph API or CLI commands for Linux/Mac users. There are no Linux-specific instructions, nor are cross-platform alternatives (such as Azure CLI or REST API examples) provided for steps that reference PowerShell.
Recommendations
- Include Linux/macOS-friendly instructions for enabling Teams users, such as using Microsoft Graph API or Azure CLI.
- When referencing PowerShell cmdlets, also provide equivalent REST API or CLI commands and examples.
- Explicitly mention that the admin center is web-based and accessible from any OS, to avoid implying a Windows-only workflow.
- Add examples using cross-platform tools for all steps currently covered only by Windows-centric tools.
- Review all steps for implicit Windows assumptions and clarify cross-platform compatibility where applicable.
Communication Services
Teams Phone Extensibility
...uickstarts/tpe/teams-phone-extensibility-quickstart.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias, particularly in the provisioning and administration steps for Teams Phone extensibility. Most command-line examples use PowerShell cmdlets and modules (e.g., Connect-MicrosoftTeams, New-CsOnlineApplicationInstance), which are native to Windows and not available or fully supported on Linux. The instructions for bot creation also reference Azure PowerShell modules and commands before mentioning Azure CLI, and do not provide Linux shell equivalents or guidance for cross-platform usage. There is no mention of Linux-specific tools, nor are there alternative examples for Linux environments. The use of Teams Admin Center and Microsoft 365 Admin Center further reinforces a Windows-centric workflow.
Recommendations
- Provide equivalent Linux/bash command examples for all PowerShell cmdlets, especially for Teams administration tasks. If not possible, clarify platform limitations.
- Highlight Azure CLI as the preferred cross-platform tool for bot and resource provisioning, and ensure all steps can be completed via CLI on Linux/macOS.
- Explicitly state platform requirements and limitations for PowerShell modules and Teams administration, and offer guidance for Linux users (e.g., using remote management, web portals, or REST APIs).
- Where GUI steps are described (Teams Admin Center, Microsoft 365 Admin Center), clarify that these are web-based and accessible from any OS.
- Add a section or callouts for Linux/macOS developers, summarizing the steps that can be performed on non-Windows platforms and providing links to relevant documentation.
Communication Services
Quickstart - Teams interop calls on Azure Communication Services
...video-calling/get-started-teams-interop-group-calls.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and patterns, such as linking to Teams deployment instructions that are Windows-focused, and mentioning PowerShell as the method for enabling Enterprise Voice for Teams users without providing equivalent Linux or cross-platform alternatives. There are no explicit Linux examples or instructions for Linux users, and Windows tools are referenced before any cross-platform or Linux options.
Recommendations
- Provide Linux-specific instructions or alternatives for Teams deployment and configuration, such as using Teams on Linux or web clients.
- Include cross-platform or Linux-friendly methods for enabling Enterprise Voice, such as using Microsoft Graph API or Azure CLI, instead of only referencing PowerShell.
- Clarify that the sample code and instructions are OS-agnostic where applicable, and explicitly mention compatibility with Linux and macOS.
- Add notes or links to documentation for running the sample on Linux (e.g., installing Node.js, using npx/webpack on Linux, browser compatibility).
- Ensure all referenced tools (e.g., Azure portal, Graph API) are described as accessible from any OS, and avoid implying Windows exclusivity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/analytics/logs/call-summary-log-schema.md
...ces/concepts/analytics/logs/call-summary-log-schema.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Example
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias in its sample data and examples. Specifically, the only explicit operating system shown in the sample call summary logs is 'Windows 10.0.17763 Arch: x64', while other OS examples are either 'null', 'Redacted', or non-Windows (Darwin/Android) but appear later. There are no Linux-specific examples or mentions, and Windows is the first and only desktop OS explicitly named in the P2P call example. No Linux tools, patterns, or instructions are referenced anywhere in the page.
Recommendations
- Include sample call summary logs with Linux endpoints, showing realistic Linux osVersion strings (e.g., 'Ubuntu 20.04 x86_64', 'Debian 11.2 x86_64').
- Explicitly mention Linux as a supported platform in relevant sections, especially where OS version is discussed.
- If there are platform-specific instructions or troubleshooting steps, provide parity for Linux users (e.g., how to collect logs or diagnose issues on Linux endpoints).
- Ensure that examples and sample data rotate or balance between Windows, Linux, and macOS endpoints to avoid implicit prioritization.
- Add a note clarifying that the service and SDK support multiple operating systems, including Linux, and link to platform compatibility documentation if available.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/email/email-domain-configuration-troubleshooting.md
...ts/email/email-domain-configuration-troubleshooting.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation consistently references the use of the 'nslookup' tool from the Windows CMD terminal for DNS record verification, without mentioning Linux or macOS equivalents (e.g., 'dig', 'host', or 'nslookup' on Unix shells). All command-line instructions and context are Windows-centric, and there are no examples or guidance for users on Linux or macOS platforms.
Recommendations
- Provide equivalent command-line instructions for Linux and macOS users, such as using 'dig' or 'nslookup' from a Unix shell.
- Explicitly mention that 'nslookup' is available on Linux and macOS, and show example commands for those environments.
- When listing steps, avoid specifying only 'Windows CMD terminal'; instead, use platform-neutral language or provide parallel instructions for each major OS.
- Include screenshots or sample outputs from Linux/macOS terminals where relevant.
- Consider a table or section summarizing DNS query commands across Windows, Linux, and macOS for user convenience.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/includes/best-practices-web.md
...ation-services/concepts/includes/best-practices-web.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed troubleshooting steps and behavioral explanations for Windows (Chrome/Edge) before mentioning macOS, and by referencing Windows-specific UI elements (e.g., desktop taskbar, right-click to quit). There are no examples or guidance for Linux users, and Linux is not mentioned in device or screen sharing sections where OS-specific behavior is discussed.
Recommendations
- Add explicit Linux examples and behavioral notes wherever OS-specific behavior is discussed (e.g., camera sharing, screen sharing).
- When listing OS-specific behaviors, include Linux alongside Windows and macOS, or clarify if behavior is identical.
- Avoid referencing only Windows UI elements (e.g., desktop taskbar, right-click to quit); provide equivalent instructions for Linux desktop environments or note differences.
- If there are no known Linux-specific issues, explicitly state that, to reassure Linux users.
- Ensure parity in troubleshooting steps and recommendations for all major platforms, including Linux.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/includes/enable-interoperability-for-teams-tenant.md
...s/includes/enable-interoperability-for-teams-tenant.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell commands and references the MicrosoftTeams PowerShell module, which is primarily a Windows tool. There are no examples or instructions for performing these tasks on Linux or macOS, nor is there mention of cross-platform alternatives. The instructions assume the reader is using Windows and PowerShell, and do not address Linux users or provide parity.
Recommendations
- Add instructions for installing and using the MicrosoftTeams module on Linux and macOS, including prerequisites such as PowerShell Core (pwsh) and any platform-specific considerations.
- Explicitly state that PowerShell Core is available cross-platform and provide guidance for Linux/macOS users to install and use it.
- Include example commands and installation steps for Linux distributions (e.g., using apt, yum, or snap to install PowerShell, then installing the MicrosoftTeams module).
- Mention any limitations or differences in behavior when using the MicrosoftTeams module on non-Windows platforms.
- Consider providing alternative methods (such as Azure CLI, REST API, or portal-based configuration) if available, to ensure broader accessibility.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/enable-interoperability-teams.md
...ices/concepts/interop/enable-interoperability-teams.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page provides instructions that exclusively reference the PowerShell Set-CsPhoneNumberAssignment cmdlet for enabling Enterprise Voice, which is a Windows-centric tool. There are no examples or guidance for performing the same operation using Linux or cross-platform tools, nor is there mention of alternative methods for non-Windows environments. The documentation implicitly assumes a Windows environment by referencing PowerShell and Teams PowerShell modules without Linux equivalents.
Recommendations
- Provide equivalent instructions or examples using Azure CLI, REST API, or other cross-platform tools where possible.
- Explicitly state if certain operations can only be performed on Windows, and suggest workarounds for Linux users (e.g., using Azure Cloud Shell).
- Add Linux/macOS-specific guidance or note the availability of Teams PowerShell modules on non-Windows platforms if supported.
- Reorder or supplement documentation to present cross-platform or OS-agnostic methods before Windows-specific tools.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/guest/security.md
...munication-services/concepts/interop/guest/security.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing the Microsoft Teams admin center and PowerShell as the primary (and only) methods for configuring security policies for Teams external users. There are no mentions of Linux-compatible tools, command-line alternatives, or cross-platform administration options. The documentation assumes the use of Windows-centric tools and does not provide parity for Linux administrators.
Recommendations
- Include examples or references for configuring Teams policies using cross-platform tools (e.g., Azure CLI, REST APIs) where possible.
- Explicitly state whether PowerShell modules are available and supported on Linux/macOS, and provide installation instructions if so.
- Mention any web-based or platform-agnostic administration options (such as the Teams admin center via browser) and clarify their OS compatibility.
- Add guidance or links for Linux administrators on how to perform equivalent security configurations.
- Review the documentation for other instances where only Windows tools are mentioned, and ensure Linux parity is addressed.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/guest/teams-administration.md
...ervices/concepts/interop/guest/teams-administration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing PowerShell modules and cmdlets for configuration and management tasks, and by listing the Teams Admin Center and PowerShell as the only tools for administrators. There are no examples or mentions of Linux-compatible tools, CLI alternatives, or cross-platform scripting. The documentation does not provide parity for Linux administrators or users, nor does it mention how to perform equivalent actions on non-Windows platforms.
Recommendations
- Include Azure CLI or Microsoft Graph API examples for all configuration tasks, especially where PowerShell is referenced.
- Explicitly mention cross-platform tools and workflows, such as the Teams Admin Center (web-based) or Graph API, and clarify their OS compatibility.
- Add Linux/macOS-specific instructions or notes where relevant, including how to install and use cross-platform PowerShell if it is required.
- Where only PowerShell is available, clarify that PowerShell Core is cross-platform and provide installation guidance for Linux/macOS.
- Consider providing bash or shell script equivalents for common administrative tasks, or at least reference their availability.
- Review all tool references to ensure Linux administrators are not excluded from management capabilities.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/teams-user/security.md
...ation-services/concepts/interop/teams-user/security.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft-centric tools and services (Teams, Azure, Entra ID) without mentioning Linux or cross-platform security practices. There are no examples or guidance for Linux users, and all security management is described via Azure Portal or Microsoft tools, which are typically Windows-first in their user experience.
Recommendations
- Include examples or references for managing security using cross-platform tools (e.g., Azure CLI, REST APIs) that are available on Linux.
- Mention how Linux users can interact with Azure Communication Services and Microsoft Entra ID, such as through command-line interfaces or SDKs.
- Provide parity in documentation by explicitly stating that security features and management are accessible from Linux environments, and link to relevant Linux or cross-platform guides.
- Avoid assuming the use of the Azure Portal or other Windows-centric GUIs as the default management method.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/teams-user/teams-shared-line-appearance.md
...pts/interop/teams-user/teams-shared-line-appearance.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Teams PowerShell as a method for assigning delegates, without mentioning or providing equivalent Linux-compatible alternatives. The only command-line tool mentioned is Teams PowerShell, which is primarily a Windows tool. There are no Linux or cross-platform command-line examples or references, and the documentation does not clarify if or how Linux users can perform these tasks.
Recommendations
- Provide Linux-compatible alternatives or clarify if Teams PowerShell can be used on Linux (e.g., via PowerShell Core).
- Include examples using cross-platform tools or REST APIs (such as Microsoft Graph API) for assigning delegates.
- Explicitly state platform requirements and limitations for administrative tasks, and offer guidance for Linux users.
- If no Linux alternative exists, document this limitation and suggest workarounds or feature requests.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-faq.md
.../concepts/interop/tpe/teams-phone-extensibility-faq.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell cmdlets and the Teams Admin Center (TAC) as the primary or only methods for configuration and management. There are no examples or mentions of Linux or cross-platform CLI tools for administering Teams Phone extensibility, nor are there instructions for performing equivalent tasks on Linux or macOS. The documentation assumes the use of Windows-centric tools and omits Linux alternatives.
Recommendations
- Include examples using cross-platform tools such as the Microsoft Teams CLI (if available) or Azure CLI for configuration tasks, especially for emergency calling policies.
- Explicitly mention whether PowerShell cmdlets can be run on PowerShell Core on Linux/macOS, or provide guidance for non-Windows users.
- Add instructions or references for managing Teams Phone extensibility from Linux or macOS environments, ensuring parity in administrative workflows.
- Where possible, provide REST API or Graph API examples for configuration, which are platform-agnostic.
- Clarify if any features are only available via Windows tools, and suggest workarounds or alternatives for Linux users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/virtual-visits/plan-user-experience.md
...oncepts/interop/virtual-visits/plan-user-experience.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (Teams Admin Center, PowerShell) as the primary methods for configuration, without mentioning or providing Linux equivalents or cross-platform alternatives. There are no examples or instructions for Linux users, and Windows tools are presented first and exclusively.
Recommendations
- Include cross-platform configuration options, such as Azure CLI or REST API examples, which work on Linux and macOS.
- Explicitly mention whether Teams Admin Center and PowerShell are available or supported on Linux, and provide guidance for Linux users if possible.
- Add examples or instructions using tools that are accessible from Linux environments, such as browser-based portals or platform-agnostic SDKs.
- Ensure that references to configuration tools do not assume a Windows environment; clarify platform requirements where necessary.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/virtual-visits/overview.md
...n-services/concepts/interop/virtual-visits/overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows and Microsoft-centric tools and workflows. All examples and architecture options are centered around Microsoft 365, Teams, Bookings, and Outlook, which are primarily Windows-oriented or Microsoft-first products. There is no mention of Linux equivalents, cross-platform alternatives, or guidance for non-Windows environments. The documentation assumes familiarity and usage of Microsoft tools, omitting any discussion of how Linux users or organizations might implement or interact with virtual appointments using Azure Communication Services.
Recommendations
- Include examples or guidance for Linux users, such as how to access Teams meetings or Bookings from Linux clients.
- Mention cross-platform alternatives or open standards for scheduling and communication, where applicable.
- Provide sample code or workflows that demonstrate integration with Azure Communication Services from Linux environments (e.g., using curl, bash, or Python instead of PowerShell).
- Clarify which features are available or supported on non-Windows platforms.
- Add a section addressing platform compatibility and considerations for organizations not using Microsoft 365 or Windows.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-troubleshooting.md
...terop/tpe/teams-phone-extensibility-troubleshooting.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias in the troubleshooting steps for resolving Microsoft Entra App permission issues. It exclusively provides PowerShell commands and instructions, assumes the use of PowerShell (a Windows-centric tool), and does not mention or provide equivalent instructions for Linux or macOS environments. There are no CLI or cross-platform alternatives (such as Azure CLI, Microsoft Graph CLI, or REST API) provided. The rest of the document is neutral, but the critical administrative steps are Windows/PowerShell-centric.
Recommendations
- Provide equivalent instructions using Azure CLI, Microsoft Graph CLI, or REST API, which are cross-platform and can be run on Linux, macOS, and Windows.
- Explicitly mention that PowerShell Core is available for Linux/macOS, or provide installation instructions for non-Windows environments.
- Add examples for Linux/macOS environments, including shell commands and package installation steps.
- Reorder or parallelize instructions so that cross-platform methods are presented first or alongside PowerShell examples.
- Add a note clarifying that the administrative steps can be performed from any OS, not just Windows, and link to relevant cross-platform tool documentation.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/pricing/teams-interop-pricing.md
...ion-services/concepts/pricing/teams-interop-pricing.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a Windows bias by referencing Windows-specific tools (e.g., PowerShell cmdlets), mentioning Windows desktop clients and tools before any Linux or cross-platform alternatives, and omitting Linux-specific instructions or examples. There are no examples or instructions for Linux users, and the only command-line tool referenced is a PowerShell cmdlet, which is Windows-centric.
Recommendations
- Provide equivalent instructions for Linux environments, such as using Azure CLI or REST API for license assignments instead of only PowerShell.
- Include explicit mention of Teams clients on Linux (e.g., Teams web client on Linux, or Teams desktop client if available) in all tables and scenarios.
- When referencing desktop clients, clarify cross-platform availability and provide parity in examples (e.g., show a user joining from a Linux desktop).
- If PowerShell is required, note how Linux users can use PowerShell Core or provide alternative commands.
- Add a pricing scenario where a user joins from a Linux device to demonstrate cross-platform support.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/voice-video-calling/manage-call-quality.md
...es/concepts/voice-video-calling/manage-call-quality.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily in the section about implementing Quality of Service (QoS), where it references Windows Group Policy objects as the method for packet marking and network prioritization. No equivalent Linux tools or methods (such as tc, iptables, or systemd-networkd) are mentioned. The documentation does not provide Linux-specific examples or guidance for QoS, and Windows tooling is mentioned first and exclusively. Other sections are generally cross-platform or platform-agnostic, but the lack of Linux parity in network configuration is a notable gap.
Recommendations
- Add Linux-specific guidance for implementing QoS, such as using tc, iptables, or firewalld to mark packets and prioritize network traffic.
- When discussing network configuration, mention both Windows and Linux approaches side by side, or provide platform-agnostic recommendations with links to OS-specific guides.
- Include examples or references for configuring QoS on common Linux distributions (e.g., Ubuntu, CentOS, Debian).
- Review other sections for potential implicit Windows bias and ensure that any OS-specific instructions are balanced with Linux equivalents.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-python.md
...tomation/includes/audio-streaming-quickstart-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias primarily in the prerequisites and reference links. The resource creation link uses a Windows-specific tab and URL parameter ('?tabs=windows'), and the WebSocket documentation link points to a Windows Azure Web Sites blog post. There are no explicit Linux or cross-platform instructions or examples, and no mention of Linux tools or environments. All code samples are Python and OS-agnostic, but supporting documentation and navigation favor Windows.
Recommendations
- Update prerequisite links to use neutral or platform-agnostic tabs/parameters (e.g., '?tabs=none' or provide both Windows and Linux options).
- Provide or link to equivalent Linux documentation for setting up WebSocket servers (e.g., using Nginx, Gunicorn, or other common Linux tools).
- Explicitly mention that the Python code samples are cross-platform and can be run on Linux, macOS, or Windows.
- Add a section or note describing how to set up the environment and run the examples on Linux (e.g., using systemd for service management, or common Linux Python environments).
- Where Windows-specific resources are referenced, provide Linux equivalents or alternatives.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/teams-interop-call-automation.md
...w-tos/call-automation/teams-interop-call-automation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation demonstrates a Windows bias primarily through its reliance on PowerShell cmdlets (e.g., Set-CsTeamsAcsFederationConfiguration, Set-CsExternalAccessPolicy) for administrative setup, which are Windows-centric tools. These are presented as the only method for tenant-level and user-level configuration, with no mention of Linux/macOS alternatives or cross-platform CLI options. The administrative steps and examples assume access to Windows tooling, and the order of presentation puts Windows/PowerShell methods first and exclusively.
Recommendations
- Provide equivalent instructions using cross-platform tools such as Azure CLI, Microsoft Graph API, or REST endpoints for tenant and user configuration, where possible.
- Explicitly mention whether PowerShell cmdlets can be run on PowerShell Core on Linux/macOS, or provide links to installation guides for non-Windows environments.
- Add examples or guidance for performing administrative setup from Linux/macOS, including any prerequisites or limitations.
- Clarify which steps require Windows-only tools and suggest alternatives or workarounds for Linux users.
- Review all administrative and setup instructions to ensure parity and accessibility for users on all major operating systems.