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 326-350 of 367 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits minor Windows bias by listing Windows-specific consoles (cmd, PowerShell) before Bash when describing how to create a new C# application. All terminal instructions use generic 'console window' language, but examples and instructions do not explicitly show Linux/macOS equivalents (e.g., shell commands, environment variable setup, or .NET installation steps for non-Windows platforms). No Linux-specific issues or troubleshooting are mentioned.
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., Bash, Terminal.app) alongside Windows consoles.
- Provide .NET installation instructions or links for Linux/macOS users.
- Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, SSL/TLS configuration).
- Show environment variable setup examples for SMTP credentials on Linux/macOS.
- Clarify that the code and commands work cross-platform and highlight any platform-specific caveats.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows terminals (Command Prompt, PowerShell) before Bash when instructing users to open a terminal. However, all commands shown are cross-platform .NET CLI commands, and no Windows-specific tools or patterns are used. There are no PowerShell-specific examples, nor are any Linux/macOS steps missing.
Recommendations
- List Bash (or 'terminal') before Windows-specific shells to avoid implying Windows primacy.
- Explicitly state that all commands work on Windows, Linux, and macOS.
- Consider adding a note or table clarifying cross-platform compatibility for the .NET CLI commands.
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 does not provide any Linux/macOS-specific instructions or examples. All commands and setup steps are generic to .NET, but the initial mention of Windows tools and lack of explicit Linux/macOS guidance creates a subtle Windows-first bias.
Recommendations
- List Bash (Linux/macOS) before or alongside cmd/PowerShell when referencing console windows.
- Explicitly state that all commands work on Linux/macOS and provide any necessary notes for those platforms (e.g., environment variable setup).
- Add a section or note for Linux/macOS users, such as how to install the .NET SDK and run dotnet commands on those platforms.
- Include example commands for setting environment variables on Linux/macOS (e.g., export ENTRA_CLIENT_ID=...) in addition to Windows (set ENTRA_CLIENT_ID=...).
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions Windows console environments (cmd, PowerShell) before Bash, and does not provide any Linux/macOS-specific instructions or examples. All commands and code are platform-neutral, but the narrative and examples are slightly Windows-centric. There is no mention of Linux/macOS environment variable setup, nor any troubleshooting or platform-specific notes for non-Windows users.
Recommendations
- Explicitly mention Bash and terminal environments for Linux/macOS alongside Windows tools.
- Provide example commands for setting environment variables on Linux/macOS (e.g., export AAD_CLIENT_ID=...) and clarify any differences in usage.
- Add a note confirming that the .NET SDK and all commands work cross-platform, and link to platform-specific installation guides if necessary.
- Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, path differences).
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, but otherwise provides cross-platform instructions using .NET CLI commands that work on Windows, Linux, and macOS. No Windows-only tools or examples are present, and Linux/macOS users are not blocked from completing the tutorial.
Recommendations
- List Bash (Linux/macOS) before Windows consoles (cmd, PowerShell) when describing where to run commands, or mention all platforms equally.
- Explicitly state that all commands work on Windows, Linux, and macOS.
- Add a note confirming that the instructions are platform-agnostic.
- Provide links or tips for installing .NET Core SDK on Linux/macOS, if not already present.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists Windows command-line environments (Command Prompt, PowerShell) before Bash when describing how to create a C# application. There is a subtle prioritization of Windows tools in the phrasing, though the actual commands shown are cross-platform. No Linux-specific examples, troubleshooting, or environment notes are provided.
Recommendations
- List Bash (Linux/macOS) first or alongside Windows command-line environments to signal equal support.
- Explicitly mention that all dotnet CLI commands work on Linux/macOS and provide links to platform-specific .NET installation guides.
- Add a short section or note on any Linux/macOS-specific considerations (e.g., file permissions, path formats, package managers).
- Include troubleshooting tips for common Linux/macOS issues (e.g., missing dependencies, environment variables).
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 PowerShell-specific commands, Windows-only tools, or missing Linux/macOS examples are present.
Recommendations
- List Bash (Linux/macOS) before Windows consoles (cmd, PowerShell) when describing command-line usage, or mention all platforms equally.
- Explicitly state that all commands are cross-platform and work on Windows, Linux, and macOS.
- Add a note confirming Maven and Java are available 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 provides code samples for C#, Java, JavaScript, and Python, covering all major platforms. However, there is a subtle Windows bias in the link to enable PSTN dial-out capability, which points to a quickstart with '?tabs=windows' in the URL, suggesting Windows is the default or primary platform. There are no explicit PowerShell examples, Windows-only tools, or instructions, and all SDK usage is cross-platform. The ordering of languages (C# first) may also reflect a minor Windows-first bias.
Recommendations
- Ensure that links to further documentation do not default to Windows tabs; provide parity for Linux/macOS tabs or make the default tab platform-neutral.
- Explicitly mention cross-platform compatibility for SDKs and APIs, reassuring Linux/macOS users.
- If there are platform-specific setup steps (e.g., for CLI, environment variables, or prerequisites), provide equivalent instructions for Linux/macOS.
- Consider rotating or randomizing the order of code samples, or defaulting to a neutral language (e.g., JavaScript or Python) to avoid implicit Windows-first impressions.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references Windows-specific consoles (cmd, PowerShell) before mentioning Bash, and does not provide any Linux/macOS-specific instructions or troubleshooting. All command-line examples use generic dotnet CLI commands, which are cross-platform, but there is a subtle Windows-first ordering and no explicit Linux/macOS parity checks or notes.
Recommendations
- List Bash (Linux/macOS) first or equally alongside cmd/PowerShell when referencing console windows.
- Include explicit notes or troubleshooting for Linux/macOS users, such as permissions, environment variable setup, or file path differences.
- Add a section confirming compatibility and any OS-specific caveats for Linux/macOS.
- Provide example commands for setting environment variables on Linux/macOS (e.g., export AZURE_CLIENT_SECRET=...) in addition to Windows examples.
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 displays a mild Windows bias in the prerequisites section, where enabling Teams Phone and Enterprise Voice for users is linked to a PowerShell-based guide, and the Teams deployment link points to a Windows-centric installation page. However, the main code samples and instructions are platform-agnostic (JavaScript/HTML), and the workflow for running the sample uses cross-platform tools (npx/webpack). There are no explicit Linux/macOS examples or references, and Windows/PowerShell tools are mentioned before any Linux alternatives.
Recommendations
- Add explicit instructions or links for enabling Teams Phone/Enterprise Voice using cross-platform tools or the Teams admin portal, if available.
- Include a note or section clarifying that the sample and setup steps work on Linux/macOS, and provide troubleshooting tips for those platforms.
- Where PowerShell is referenced, mention alternative methods (e.g., Teams admin center UI) for non-Windows users.
- Ensure links to Teams deployment cover Linux/macOS installation options if available.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page shows minor Windows bias in the instructions for opening a terminal, listing Windows tools (PowerShell, Windows Terminal, Command Prompt) first and only mentioning 'equivalent' for other platforms. No Linux/macOS-specific examples or tools are named, but all commands and steps are cross-platform (Node.js, npm, Azure CLI).
Recommendations
- Explicitly mention Linux/macOS terminal options (e.g., 'Terminal', 'bash', 'zsh') alongside Windows tools.
- Provide a brief note confirming all commands work on Linux/macOS, or highlight any platform-specific differences if present.
- Add links or references to installing Node.js and Azure CLI on Linux/macOS.
- Consider listing terminal options in a neutral order (e.g., 'Open a terminal (PowerShell, Windows Terminal, Command Prompt, Terminal, bash, zsh, etc.)').
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 a mild Windows bias, primarily in the form of Windows-first examples and links. Many quickstart and scenario links use Windows as the default tab or pivot, and there is a lack of explicit Linux/macOS examples or instructions. No PowerShell or Windows-only tools are mentioned, but the documentation does not demonstrate Linux parity in its examples or guidance.
Recommendations
- Ensure that all quickstart and scenario links include Linux/macOS tabs or pivots where applicable.
- Provide explicit Linux/macOS examples alongside Windows ones, especially for SDK usage, setup, and environment configuration.
- Avoid using Windows as the default or first example in tables and links; alternate or present all platforms equally.
- Add notes or sections addressing any platform-specific differences for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation shows mild Windows bias by instructing users to open a PowerShell window to run the application, without mentioning Linux/macOS terminal alternatives. Additionally, some prerequisite links default to Windows tabs, implying Windows-first orientation. However, most setup and commands (e.g., dev tunnel, npm) are cross-platform and not inherently Windows-specific.
Recommendations
- Replace 'Open a new PowerShell window' with 'Open a terminal window (PowerShell, Command Prompt, Terminal, or shell of your choice)' to be inclusive of Linux/macOS users.
- Ensure prerequisite links and instructions mention or link to Linux/macOS setup steps where available.
- Add a note clarifying that all commands (npm, devtunnel) work on Linux/macOS terminals as well.
- If any platform-specific steps exist, provide equivalent instructions for Linux/macOS.
Communication Services
Sign an HTTP Request with C#
...tion-services/tutorials/includes/hmac-header-csharp.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-specific tools (Visual Studio) as the only IDE in prerequisites and mentioning Windows console environments (cmd, PowerShell) before Bash. However, the actual code and commands (dotnet CLI) are cross-platform, and Linux/macOS users can follow the steps without significant friction.
Recommendations
- Mention cross-platform IDEs (e.g., VS Code, JetBrains Rider) alongside Visual Studio in prerequisites.
- List Bash (or terminal) before or alongside cmd/PowerShell when referencing console windows.
- Explicitly state that all steps and tools (dotnet CLI, HttpClient) work on Linux and macOS.
- Add a note clarifying that the tutorial is platform-agnostic and can be completed on Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows command-line tools (cmd, PowerShell) before Bash when describing how to run commands, which may suggest a Windows-first bias. However, all command-line examples use 'dotnet' CLI commands, which are cross-platform, and there are no PowerShell-specific scripts or Windows-only tools used. No Linux-specific examples or instructions are provided, but the instructions are generally applicable to both Windows and Linux environments.
Recommendations
- List Bash (Linux/macOS) before Windows tools (cmd, PowerShell) when describing command-line usage, or mention all platforms equally.
- Explicitly state that all dotnet CLI commands work on Linux/macOS as well as Windows.
- Provide example environment variable setting commands for both Windows (set, $env:) and Linux/macOS (export).
- Add a note or section confirming Linux/macOS compatibility and any platform-specific considerations.
- Include troubleshooting tips for Linux/macOS users if any common issues are known.
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 provides code samples for C#, Java, JavaScript, and Python, with no explicit Windows-only tools or PowerShell usage. However, there is evidence of Windows bias in the form of Windows-first navigation: the link to enabling PSTN dial-out in rooms points to a quickstart with '?tabs=windows', suggesting Windows is the default or primary platform. There is no mention of Linux-specific instructions, nor are Linux or cross-platform CLI examples provided for setup or configuration tasks.
Recommendations
- Ensure that all quickstart and how-to links use neutral or platform-agnostic tabs (e.g., '?tabs=azcli' or provide both Windows and Linux tabs).
- Add explicit instructions or examples for Linux environments, such as using Bash, Azure CLI, or other cross-platform tools for setup and configuration.
- Review linked pages to confirm Linux parity in examples and instructions, and update navigation to avoid defaulting to Windows.
- Where platform-specific steps are required, provide side-by-side instructions for both Windows and Linux users.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows-specific console environments ('Command Prompt, PowerShell') before Linux/Bash when describing how to run commands. However, all command-line examples use cross-platform .NET CLI commands and do not show Windows-only tools or PowerShell scripts. There are no Linux-specific examples or tools mentioned, but the instructions are generally applicable to both platforms.
Recommendations
- List Bash (Linux/macOS) before Command Prompt/PowerShell, or mention all platforms equally (e.g., 'in a console window such as Bash, Command Prompt, or PowerShell').
- Explicitly state that the .NET CLI commands work on Windows, Linux, and macOS.
- Add a note or section confirming Linux/macOS compatibility, and provide troubleshooting tips for those platforms if relevant.
- If platform-specific differences exist (e.g., environment variables, file paths), include examples for both Windows and Linux.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/analytics/logs/call-summary-updates-log-schema.md
...epts/analytics/logs/call-summary-updates-log-schema.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page generally avoids explicit platform bias in its instructions and examples. However, there is a subtle Windows-first bias in the sample data: the only explicit OS version shown in the P2P call example is 'Windows 10.0.17763 Arch: x64', and this appears before any other OS examples. Other platforms (Darwin/macOS, Android) only appear later in group call examples. No Linux-specific OS version is shown in any sample data, nor is Linux mentioned in the text or examples. There are no PowerShell-specific instructions or Windows-only tools referenced, but the ordering of OS examples and omission of Linux may give the impression of Windows primacy.
Recommendations
- Add at least one sample call log with a Linux-based 'osVersion' (e.g., 'Linux 5.4.0-104-generic; Arch: x64') to demonstrate Linux support.
- When listing sample data, rotate or randomize the order of OS examples, or explicitly include all major platforms (Windows, macOS, Linux, Android, iOS) in the first set of examples.
- In the 'osVersion' property description, explicitly mention that Linux and other OSes are supported and provide example values.
- Review other documentation pages linked from this one to ensure Linux is represented in instructions and troubleshooting guides.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/call-automation/play-ai-action.md
...on-services/concepts/call-automation/play-ai-action.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples, commands, or tools. However, it references the 'Audio Content Creation tool' for creating WAV files, which is a Microsoft tool that may not be available or easily usable on Linux. There are no explicit instructions or examples for Linux users, nor are alternative Linux-compatible tools mentioned for audio file creation.
Recommendations
- Include examples or recommendations for creating compatible WAV files using common Linux tools (e.g., ffmpeg, sox, Audacity).
- Clarify whether the 'Audio Content Creation tool' is cross-platform or provide Linux alternatives.
- Add a section or note acknowledging how Linux users can prepare audio files for use with Azure Communication Services.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/includes/best-practices-native.md
...on-services/concepts/includes/best-practices-native.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides platform-specific guidance for iOS, Android, and Windows, but does not mention Linux at all. There are no examples, requirements, or instructions for using the Calling Native SDK on Linux platforms, nor is Linux discussed as a supported or unsupported platform. This omission may lead Linux developers to feel excluded or uncertain about SDK compatibility.
Recommendations
- Explicitly state whether Linux is supported or unsupported as a platform for the Calling Native SDK.
- If Linux is supported, add a dedicated section for Linux with minimum requirements, permission configuration, and relevant examples, similar to the iOS, Android, and Windows sections.
- If Linux is not supported, clarify this in the 'Supported platforms' section to avoid ambiguity.
- Where possible, provide parity in examples and troubleshooting steps for Linux users (e.g., how to configure permissions, manage logs, or handle device access on Linux).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/notifications.md
...icles/communication-services/concepts/notifications.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not exhibit explicit Windows bias in terms of command-line examples or tool recommendations. All provided command-line examples use the 'armclient' tool, which is a cross-platform CLI and not specific to Windows or PowerShell. There are no Windows-specific tools, PowerShell scripts, or references to Windows-first patterns. However, there is a lack of explicit Linux/macOS examples or mentions, which may leave Linux users uncertain about platform compatibility or alternative workflows.
Recommendations
- Explicitly state that the 'armclient' tool and Azure portal steps are cross-platform and supported on Windows, Linux, and macOS.
- If there are any platform-specific prerequisites or installation steps for 'armclient', provide links or instructions for all major operating systems.
- Add a note confirming that all command-line instructions are valid on Linux/macOS terminals, or provide alternative commands if any step differs.
- Where screenshots or UI instructions are given, clarify that the Azure portal experience is consistent across platforms and browsers.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/handle-events-with-event-processor.md
.../call-automation/handle-events-with-event-processor.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only C# code examples and does not reference any Windows-specific tools, PowerShell, or Windows-only patterns. However, it lacks any mention of Linux environments, alternative shells, or cross-platform considerations. There are no explicit instructions or examples for Linux users, nor is there guidance on running the code outside of a Windows context.
Recommendations
- Add explicit statements clarifying that the event processor and SDK are cross-platform (if applicable), and can be used on Linux, macOS, and Windows.
- Include Linux-specific instructions or examples, such as running the code on .NET Core in a Linux environment, or deploying the webhook endpoint on a Linux server.
- Mention any platform requirements or differences, if they exist, for hosting the webhook endpoint or running the Azure Communication Services SDK.
- If the code is platform-agnostic, state this clearly to reassure Linux users.
- Provide sample commands for running or deploying the application on Linux (e.g., using dotnet CLI on Ubuntu).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/recognize-ai-action-how-to-java.md
...automation/includes/recognize-ai-action-how-to-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild Windows bias by referencing Windows first in prerequisite links (e.g., resource creation tabs default to 'windows'), but otherwise provides cross-platform Java and Maven instructions that are equally applicable to Linux and macOS. There are no exclusive Windows tools, PowerShell scripts, or missing Linux examples in the main content.
Recommendations
- Ensure that prerequisite links and quickstart guides do not default to 'windows' tabs or provide clear instructions for Linux/macOS users.
- Explicitly mention that all terminal and Maven commands work on Linux, macOS, and Windows.
- Where possible, provide links or notes for Linux/macOS equivalents when referencing platform-specific instructions or UI elements.
- Review tabbed content in linked resources to ensure Linux and macOS parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/play-audio-how-to-js.md
...w-tos/call-automation/includes/play-audio-how-to-js.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation exhibits a mild 'windows_first' bias in the prerequisites section, where links to Azure resource creation include a '?tabs=windows' parameter and reference 'tabs=windows' before any mention of other platforms. However, the rest of the documentation is platform-neutral, focusing on JavaScript and Node.js, which are cross-platform technologies. There are no PowerShell-specific examples, Windows-only tools, or missing Linux equivalents in the main content.
Recommendations
- Update prerequisite links to either default to platform-neutral pages or explicitly provide tabs/links for both Windows and Linux (and macOS) users.
- Ensure that any referenced quickstarts or guides do not default to Windows instructions, or clearly indicate how Linux users can follow along.
- If platform-specific setup is required (e.g., for Node.js installation), provide instructions or links for both Windows and Linux.
- Review all documentation links for platform-specific query parameters and adjust to be inclusive.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/mute-participants-how-to-java.md
...l-automation/includes/mute-participants-how-to-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation exhibits a mild 'windows_first' bias by linking to resource creation instructions with a '?tabs=windows' parameter and 'pivots=platform-azp', suggesting Windows as the default or primary platform. However, all code and command-line instructions (Maven, Java, XML) are cross-platform and do not use Windows-specific tools or shell commands. No explicit PowerShell or Windows-only command examples are present, and the instructions are generally applicable to Linux and macOS as well.
Recommendations
- Ensure that links to Azure resource creation guides either default to a neutral or platform-agnostic tab, or explicitly mention and provide Linux/macOS alternatives.
- If platform-specific instructions are necessary, provide Linux/macOS equivalents alongside Windows instructions, or clarify that the steps are cross-platform.
- Audit all quickstart and prerequisite links to avoid defaulting to Windows-specific tabs or pivots.
- Explicitly state in the prerequisites or introduction that the instructions are valid for all major operating systems.