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 551-575 of 656 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions Windows-specific console environments (cmd, PowerShell) before Bash, and does not provide any Linux/macOS-specific instructions or examples. All commands and environment variable usage are shown in a cross-platform way, but there is no explicit guidance for Linux/macOS users regarding environment variable setup or editor usage.
Recommendations
- List Bash (Linux/macOS) first or equally when mentioning console environments.
- Provide explicit instructions or examples for setting environment variables on Linux/macOS (e.g., export ENTRA_CLIENT_ID=...).
- Mention common Linux/macOS editors (e.g., nano, vim) alongside generic 'text editor'.
- Clarify that all dotnet CLI commands work cross-platform and link to platform-specific setup guides if needed.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions Windows console environments (cmd, PowerShell) before Bash, and all command-line examples use generic 'console' blocks without platform-specific guidance. There are no Linux/macOS-specific instructions, troubleshooting, or environment variable setup examples. The documentation implicitly assumes parity but does not provide explicit Linux/macOS guidance or validation.
Recommendations
- Explicitly mention Linux/macOS environments alongside Windows in setup instructions.
- Provide examples of setting environment variables on Linux/macOS (e.g., export AAD_CLIENT_ID=...) and how to run dotnet commands in Bash/zsh.
- Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, .NET SDK installation paths).
- Ensure that all steps are validated on Linux/macOS and note any platform-specific caveats.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references Windows-specific console windows (cmd, PowerShell) before Bash, and all command-line examples use the generic 'dotnet' CLI without showing any OS-specific nuances. There are no explicit Linux/macOS examples, nor are there notes about platform-specific differences or requirements. The documentation does not mention Linux tools or patterns, and the sample code is exclusively for .NET/C#, which is cross-platform but often associated with Windows development. No PowerShell-specific commands are present, but the overall tone and ordering favor Windows environments.
Recommendations
- Explicitly mention Linux/macOS compatibility in the prerequisites and setup sections.
- List Bash or terminal as the first example when referencing console windows, or provide separate instructions for Windows (cmd/PowerShell) and Linux/macOS (Bash/Terminal).
- Add notes or examples for installing .NET and running dotnet commands on Linux/macOS, including any platform-specific caveats.
- Clarify that the sample code and SDK are cross-platform, and provide links to Linux/macOS installation guides for .NET.
- If there are any platform-specific requirements for Azure Communication Services, document them.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform, referencing .NET Core SDK and using generic 'console window' and 'terminal' terminology. However, in the section 'Create a new C# application', Windows-specific shells (cmd, PowerShell) are mentioned before Bash, which is a minor Windows-first bias. All command-line examples use 'dotnet', which is cross-platform, and no Windows-only tools or patterns are present. There are no missing Linux/macOS examples, and the instructions are applicable to all platforms.
Recommendations
- List Bash (or 'terminal') before Windows shells (cmd, PowerShell) when mentioning console environments to avoid Windows-first impression.
- Explicitly state that all commands work on Windows, Linux, and macOS.
- Consider adding a note or example showing the use of environment variables on Linux/macOS (e.g., setting COMMUNICATION_SERVICES_CONNECTION_STRING in Bash).
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows-specific consoles ('cmd, PowerShell') before Linux ('Bash') when describing where to run commands, but otherwise provides cross-platform instructions and examples. All commands and code samples use Java and Maven, which are platform-agnostic. No Windows-only tools, PowerShell scripts, or missing Linux/macOS equivalents are present.
Recommendations
- List Bash (Linux/macOS) before Windows consoles when describing where to run commands, or use neutral phrasing such as 'in a terminal window (e.g., Bash, cmd, PowerShell)'.
- Explicitly state that all commands are cross-platform and can be run on Windows, Linux, or macOS.
- Provide a brief note confirming Maven and Java are supported on all major operating systems.
Communication Services
Quickstart - Manage a room call
...cation-services/quickstarts/rooms/manage-rooms-call.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild Windows bias by linking to a 'Rooms quickstart' with the query parameter '?tabs=windows', suggesting Windows as the default or primary platform for further guidance. However, all code samples are cross-platform (C#, Java, JavaScript, Python) and do not use Windows-specific tools, shells, or patterns. There are no PowerShell examples, nor exclusive references to Windows-only utilities. Linux/macOS users are not blocked from completing any tasks, but may experience minor friction due to Windows being presented as the default in some links.
Recommendations
- Ensure that quickstart and concept links use neutral tab defaults (e.g., '?tabs=cli' or no tab parameter) or provide explicit parity for Linux/macOS users.
- Where platform-specific instructions exist, present Linux/macOS options alongside or before Windows options.
- Review all linked pages to confirm Linux/macOS parity and avoid Windows-first presentation.
- Add a note clarifying that all SDK code samples are cross-platform and not dependent on Windows.
- If CLI instructions are referenced, ensure both Azure CLI and PowerShell are covered equally.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows-specific consoles (cmd, PowerShell) before Bash when describing where to run commands, and generally lists Windows environments first. However, all commands and code samples use cross-platform .NET CLI and C#, which work equally on Windows, Linux, and macOS. No Windows-only tools or patterns are present, and Linux/macOS users can follow all steps without issue.
Recommendations
- List Bash (Linux/macOS) before or alongside cmd/PowerShell when mentioning console options.
- Explicitly state that all commands work on Linux/macOS as well as Windows.
- Provide brief notes or links for Linux/macOS users where relevant (e.g., installing .NET Core on Linux).
Communication Services
Quickstart - Teams interop calls on Azure Communication Services
...video-calling/get-started-teams-interop-group-calls.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by referencing Windows-centric tools and patterns first, particularly in the prerequisites section. The requirement for Teams users to be 'Enterprise Voice enabled' links to a PowerShell-based guide, and the Teams deployment link points to a Windows installer. However, the main code samples and instructions are platform-agnostic (JavaScript/HTML), and there are no critical steps that are Windows-only.
Recommendations
- Provide explicit instructions or links for enabling Teams Enterprise Voice using cross-platform methods (e.g., Azure CLI, Graph API, or web portal), not just PowerShell.
- Include Linux/macOS-specific guidance for Teams deployment if relevant (or clarify if Teams deployment is platform-agnostic).
- Where PowerShell is referenced, mention alternative approaches for non-Windows users.
- Ensure all referenced documentation (e.g., enabling Enterprise Voice) includes Linux/macOS parity.
Communication Services
Access a user's Teams Phone separate from their Teams client
...ts/tpe/teams-phone-extensibility-access-teams-phone.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates mild Windows bias. The only explicit tooling example for obtaining a Resource Account GUID references the MicrosoftTeams PowerShell cmdlet (Get-CsOnlineApplicationInstance), a Windows-centric tool. The user enablement instructions are written for the Microsoft 365 admin center, which is web-based but often assumes Windows environments. No Linux/macOS equivalents or alternatives are mentioned for PowerShell commands, and Windows tools are referenced before any cross-platform REST or SDK approaches.
Recommendations
- Provide Linux/macOS alternatives for PowerShell commands, such as using Microsoft Graph API via curl or other cross-platform tools.
- Explicitly mention that REST API calls and SDK usage are platform-agnostic and can be performed from any OS.
- Add examples for obtaining Resource Account GUIDs using Graph API (with curl, httpie, or similar) alongside PowerShell.
- Clarify that the admin center is web-based and accessible from any OS/browser.
- Where Windows tools are referenced, add notes or links to equivalent Linux/macOS workflows.
Communication Services
Quickstart - Make a call to Teams user from an iOS app
...ce-video-calling/includes/teams-user/teams-user-ios.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias in the prerequisites section, where enabling Teams Phone features for users is described only via PowerShell (a Windows-centric tool). The link to Teams deployment also points to a Windows-focused installation guide. No Linux/macOS alternatives or parity are mentioned for these administrative steps, though the main tutorial is iOS-focused and platform-neutral.
Recommendations
- Provide Linux/macOS alternatives for Teams administration tasks, such as enabling Enterprise Voice, if available (e.g., via Microsoft 365 admin portal or cross-platform CLI).
- Clarify whether PowerShell steps can be performed using PowerShell Core on Linux/macOS, or provide links to relevant documentation.
- Include notes or links for Teams deployment on non-Windows platforms if possible.
- Explicitly state which steps are Windows-only and offer guidance for users on other operating systems.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page shows a minor Windows bias in the instructions for opening a terminal: it lists PowerShell, Windows Terminal, and Command Prompt before mentioning 'equivalent' terminals, implicitly prioritizing Windows tools. No explicit Linux/macOS examples or tools are provided, but all commands and steps are cross-platform (git, npm, Azure CLI).
Recommendations
- Explicitly mention Linux/macOS terminal options (e.g., 'Terminal on macOS or Linux') alongside Windows tools.
- Provide assurance that all commands (git, npm, Azure CLI) work on Linux/macOS and note any platform-specific caveats if present.
- Consider listing terminal options in a neutral order, e.g., 'Open a terminal (PowerShell, Windows Terminal, Command Prompt, Terminal on macOS or Linux, etc.)...'
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by referencing PowerShell specifically when instructing users to open a terminal and run commands. The instructions state 'Open a new PowerShell window' rather than using platform-neutral language or providing Linux/macOS alternatives. Additionally, some prerequisite links default to Windows tabs, which may subtly prioritize Windows users.
Recommendations
- Replace 'Open a new PowerShell window' with platform-neutral instructions such as 'Open a terminal window' or provide separate instructions for Windows (PowerShell), Linux (bash), and macOS (Terminal).
- Ensure all command-line examples use cross-platform syntax, or explicitly note platform differences where relevant.
- Where documentation links default to Windows tabs, add clear navigation or mention for Linux/macOS users.
- Consider adding a section or callout for Linux/macOS users to clarify any platform-specific steps or requirements.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exhibits mild Windows bias, primarily in the prerequisites section where links to resource creation use Windows-specific tabs and pivots. There is no explicit mention of Linux/macOS alternatives or examples in the setup or run instructions, though the commands themselves are cross-platform. The documentation does not provide Linux/macOS-specific guidance or troubleshooting, and Windows is implicitly prioritized.
Recommendations
- Ensure resource creation links default to platform-neutral or provide clear Linux/macOS tabs/pivots.
- Explicitly state that all commands (pip, devtunnel, python) work on Linux/macOS, and provide any platform-specific notes if needed.
- Add Linux/macOS-specific setup or troubleshooting steps if there are known differences (e.g., devtunnel installation, permissions).
- Avoid using Windows-specific terminology (e.g., 'command prompt') without mentioning Linux/macOS equivalents (e.g., 'terminal').
Communication Services
Sign an HTTP Request with C#
...tion-services/tutorials/includes/hmac-header-csharp.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by listing Windows tools (cmd, PowerShell) before Bash when describing how to run dotnet commands. It also assumes the use of Visual Studio, which is primarily a Windows IDE, without mentioning cross-platform alternatives like VS Code or JetBrains Rider. There are no explicit Linux/macOS-specific instructions or troubleshooting notes, and the examples do not address platform-specific differences in .NET development environments.
Recommendations
- List Bash first or equally alongside cmd/PowerShell when describing console usage.
- Mention cross-platform IDEs such as Visual Studio Code or JetBrains Rider as alternatives to Visual Studio.
- Add a note confirming that all steps work on Linux/macOS, and provide troubleshooting tips for those platforms if needed.
- Include explicit instructions for installing .NET SDK on Linux/macOS.
- Clarify that the 'dotnet' CLI and code samples are cross-platform.
Communication Services
Using ACS UI library JavaScript bundles with Teams Call Queues and Auto Attendants
...tutorials/calling-widget/calling-widget-js-tutorial.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and macOS commands for creating a project folder, but lists the Windows command first. No Windows-specific tools, patterns, or examples are otherwise present; all instructions and code samples are cross-platform and use standard tools (Node.js, VS Code, npx http-server) available on Linux/macOS/Windows. There are no PowerShell-specific examples, nor are Windows-only tools or patterns mentioned.
Recommendations
- Present platform-specific commands in parallel or in alphabetical order (e.g., macOS/Linux first, then Windows, or vice versa), or combine them when possible.
- Explicitly mention Linux support alongside macOS and Windows when listing prerequisites and commands.
- Add a Linux-specific command example for folder creation (even though it matches macOS), to reinforce parity.
- Where 'terminal or command prompt' is mentioned, clarify that 'terminal' applies to Linux/macOS and 'command prompt' to Windows.
Communication Services
Contact centers with Azure Communication Services
...les/communication-services/tutorials/contact-center.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias, primarily in the form of Windows-first examples and links. Many quickstart and reference links use 'tabs=windows' or 'tabs=uwp', and there is a lack of explicit Linux/macOS examples or instructions. No PowerShell or Windows-only tools are mentioned directly, but the pattern of defaulting to Windows in code and setup links may create friction for Linux/macOS users.
Recommendations
- Add explicit Linux/macOS examples and setup instructions alongside Windows examples.
- Ensure quickstart links and code samples include Linux/macOS tabs or pivots where applicable.
- Avoid using 'windows' as the default tab in documentation tables; rotate or randomize the order, or use a neutral default.
- Mention cross-platform compatibility and provide troubleshooting notes for non-Windows environments.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows consoles (cmd, PowerShell) before Bash when describing how to run Maven commands, but otherwise provides cross-platform instructions and examples. No Windows-only tools, PowerShell scripts, or missing Linux/macOS equivalents are present.
Recommendations
- List Bash (Linux/macOS) before Windows consoles (cmd, PowerShell) when mentioning terminal options.
- Explicitly state that all commands work on Linux/macOS as well as Windows.
- Consider adding a note or example showing the commands being run in a Linux/macOS terminal to reinforce parity.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by listing Windows console environments (cmd, PowerShell) before Bash, and by providing only .NET/C# code samples and dotnet CLI commands without explicit Linux/macOS-specific instructions or troubleshooting. However, the commands and code are generally cross-platform, and there are no Windows-only tools or patterns.
Recommendations
- Explicitly mention that all dotnet CLI commands work on Linux/macOS as well as Windows.
- Provide example terminal commands using Bash/zsh syntax where appropriate (e.g., directory navigation, environment variable setup).
- Add a note or section for Linux/macOS users about installing .NET Core and running dotnet commands.
- Ensure troubleshooting steps or common issues for Linux/macOS environments are referenced if relevant.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows-specific consoles (cmd, PowerShell) before Bash when instructing users to create a new C# application. However, all commands shown are cross-platform and there are no Windows-only tools or examples. No PowerShell-specific commands or Windows-only patterns are present, and Linux/macOS users can follow all steps without friction.
Recommendations
- List Bash (or 'terminal') before Windows consoles (cmd, PowerShell) to avoid implying Windows primacy.
- Explicitly state that all commands work on Windows, Linux, and macOS.
- Add a note clarifying that the instructions are cross-platform and provide links to platform-specific .NET installation guides if needed.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references Windows-specific console environments (cmd, PowerShell) before mentioning Bash, and all code samples and instructions are focused on .NET and C#, which are cross-platform but traditionally associated with Windows. There are no Linux/macOS-specific instructions, troubleshooting, or environment setup details, and no explicit Linux/macOS terminal examples are provided.
Recommendations
- Explicitly mention Linux/macOS compatibility in the prerequisites and setup sections.
- Provide Linux/macOS-specific instructions or notes for installing .NET (e.g., using apt, yum, or Homebrew).
- List Bash or Linux/macOS terminal examples before or alongside Windows examples.
- Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, path differences).
- Clarify that all commands are cross-platform and provide links to .NET installation guides for Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows-specific terminals (PowerShell, Windows Terminal, Command Prompt) first when instructing users to open a shell to clone the repository, with only a vague 'or equivalent' for other platforms. No explicit Linux/macOS terminal examples or instructions are provided, but the rest of the instructions (git, npm, Azure CLI) are cross-platform.
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., 'Open an instance of PowerShell, Windows Terminal, Command Prompt, Terminal on macOS, or a Linux shell...').
- Provide example commands for Linux/macOS users where relevant.
- Ensure that any tooling or setup steps are described in a platform-neutral way, or provide platform-specific notes as needed.
Communication Services
Using ACS UI library JavaScript bundles with Teams Call Queues and Auto Attendants
...tutorials/calling-widget/calling-widget-js-tutorial.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation shows a minor Windows bias by presenting Windows command prompt instructions before macOS equivalents when creating the project directory. However, all other instructions and examples (Node, VS Code, running the app) are cross-platform and do not favor Windows-specific tools or patterns.
Recommendations
- Present platform instructions together or in parallel, rather than listing Windows first.
- Explicitly mention Linux in command examples, as Linux and macOS terminal commands are typically identical.
- Add a note clarifying that all commands work on Linux, macOS, and Windows (with PowerShell or Command Prompt).
Communication Services
Enable Closed captions with Teams Interoperability
...on-services/concepts/interop/enable-closed-captions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation references Windows as a supported platform before Linux/macOS and mentions Teams policies with links to PowerShell modules, which are Windows-centric tools. There are no explicit Linux/macOS examples or references to equivalent tools or policies for those platforms.
Recommendations
- Explicitly mention Linux and macOS as supported platforms where applicable.
- Provide examples or references for managing Teams policies using cross-platform tools (e.g., Microsoft Graph API) instead of only PowerShell.
- Include parity in SDK usage instructions for Linux/macOS environments.
- Clarify any platform-specific limitations or requirements for Linux/macOS users.
Communication Services
Teams Phone extensibility FAQ
.../concepts/interop/tpe/teams-phone-extensibility-faq.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias, primarily by referencing PowerShell cmdlets and the Teams Admin Center (TAC) portal as the main methods for configuring emergency calling policies. These tools are Windows-centric, and no Linux/macOS equivalents or cross-platform alternatives are mentioned. Additionally, Windows tools are referenced before any general or platform-neutral guidance, and there are no examples or instructions for Linux or macOS users.
Recommendations
- Include instructions or examples for configuring Teams policies using platform-agnostic methods, such as Microsoft Graph API or web-based portals accessible from any OS.
- Explicitly mention whether PowerShell cmdlets can be run on Linux/macOS (using PowerShell Core), and provide guidance for those platforms if supported.
- Add notes or links for Linux/macOS users on how to perform equivalent administrative tasks.
- Where possible, avoid referencing Windows-specific tools first; present platform-neutral options before platform-specific ones.
Communication Services
Pricing for Teams interop scenarios
...ion-services/concepts/pricing/teams-interop-pricing.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates mild Windows bias by consistently referencing the 'Teams Desktop client' (implicitly Windows) and mentioning Windows-specific environments (e.g., 'Windows, Chrome browser') in scenarios. There is also a reference to PowerShell cmdlets for license assignment, which are Windows-centric tools. No explicit Linux/macOS examples, tools, or parity guidance are provided.
Recommendations
- Explicitly mention cross-platform availability of Teams clients (Windows, macOS, Linux) in tables and scenarios.
- Provide examples or notes for using Teams and Azure Communication Services on Linux and macOS, including supported browsers and SDKs.
- Include alternative methods for license assignment (e.g., Microsoft Graph API, Azure CLI) alongside PowerShell cmdlets.
- Avoid referencing Windows environments exclusively in scenarios; use neutral language or include Linux/macOS variants.