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 351-367 of 367 flagged pages
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/play-audio-how-to-python.md
...s/call-automation/includes/play-audio-how-to-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild Windows bias in the virtual environment activation instructions, where the Windows command is presented first and with more explicit guidance. The prerequisites link also uses a Windows-specific tab by default. However, most of the content is platform-neutral and uses Python code examples that work on both Windows and Linux.
Recommendations
- Present virtual environment activation instructions for Windows and Unix/Linux in parallel, or list Unix/Linux first to balance representation.
- Ensure prerequisite links and quickstarts do not default to Windows tabs or mention Windows before Linux; provide equal visibility for Linux/macOS instructions.
- Explicitly mention that all Python code examples are cross-platform, and note any platform-specific caveats if they exist.
- Where external tools are referenced (e.g., Speech synthesis with Audio Content Creation tool), clarify platform compatibility or provide alternatives if any are Windows-only.
Create Pull Request
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/play-audio-quickstart-java.md
...call-automation/includes/play-audio-quickstart-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page shows evidence of Windows bias primarily in the prerequisites section, where the link to creating an Azure Communication Services resource uses a Windows-specific tab and query parameter ('tabs=windows'). There are no explicit Linux or cross-platform instructions or examples, and no mention of Linux-specific tools or patterns. However, the rest of the page uses Java and Maven commands, which are cross-platform, and does not provide PowerShell or Windows-only command-line examples.
Recommendations
- Update prerequisite links to use neutral or cross-platform tabs (e.g., avoid '?tabs=windows').
- Explicitly mention that all Maven and Java commands work on Linux, macOS, and Windows.
- Where applicable, provide links or instructions for creating Azure resources using CLI or portal in a way that is platform-agnostic.
- Add a note in the prerequisites clarifying that the steps and tools are supported on Linux, macOS, and Windows.
- Review other linked quickstarts and ensure Linux parity in examples and instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/recognize-how-to-python.md
...os/call-automation/includes/recognize-how-to-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally provides cross-platform instructions and Python code examples, but there is a minor Windows bias in the 'Prerequisites' and 'Activate your virtual environment' sections. Windows instructions and links are presented before Unix/Linux equivalents, and the resource creation link defaults to a Windows tab. However, Linux activation commands are present, and all code samples are OS-agnostic.
Recommendations
- Present Unix/Linux and Windows instructions side-by-side or in a neutral order, rather than listing Windows first.
- Avoid defaulting resource creation links to Windows tabs; provide a neutral or platform-agnostic default, or clearly indicate both options.
- Where platform-specific commands are required, consider using tabbed content or clear headings for each OS.
- Review all links and references to ensure Linux/macOS users are equally supported and not required to adapt Windows-centric instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/recognize-action-quickstart-java.md
...utomation/includes/recognize-action-quickstart-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a subtle Windows bias in the prerequisites section, where the link to creating an Azure Communication Services resource uses a Windows-specific tab and pivot by default ('?tabs=windows&pivots=platform-azp'). No explicit Linux or cross-platform instructions are provided, and the documentation does not mention Linux-specific considerations or alternative commands/tools. However, the main quickstart and code samples are platform-neutral (Java/Maven), and do not use Windows-only tools or PowerShell.
Recommendations
- Update prerequisite links to default to a neutral or cross-platform tab/pivot, or explicitly mention Linux/macOS instructions alongside Windows.
- Add a note clarifying that the Java/Maven commands work on Linux, macOS, and Windows, and provide any OS-specific setup tips if relevant.
- Ensure all referenced quickstart/resource creation guides include Linux/macOS steps and screenshots, not just Windows.
- Review other linked documentation for similar Windows-first pivots and update to ensure parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/recognize-how-to-js.md
...ow-tos/call-automation/includes/recognize-how-to-js.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a mild 'windows_first' bias. In the prerequisites, the link to creating an Azure Communication Services resource includes a 'tabs=windows' parameter, and the only platform-specific mention is for Windows. There are no explicit Linux or macOS instructions or examples, but the rest of the guide uses cross-platform JavaScript/Node.js commands and code samples.
Recommendations
- Update prerequisite links to either be platform-neutral or provide tabs for Windows, Linux, and macOS, ensuring Linux users are equally supported.
- Explicitly mention that the instructions and commands (npm, node) work on Linux and macOS as well as Windows.
- If there are any platform-specific steps (e.g., environment variables, file paths), provide Linux/macOS equivalents alongside Windows.
- Review all quickstart and resource links to ensure they do not default to Windows instructions when Linux options are available.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-android.md
...osed-captions/closed-captions-teams-interop-android.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation shows a subtle Windows bias in the prerequisites section, where resource creation links use the 'windows' tab by default and the URL contains '?tabs=windows'. However, the main technical content is platform-neutral Java code, and there are no explicit Windows-only tools, PowerShell examples, or missing Linux equivalents.
Recommendations
- Update prerequisite links to use platform-neutral or user-detecting tabs, or provide explicit Linux/macOS options alongside Windows.
- Ensure that quickstart and resource creation documentation referenced from this page includes Linux and macOS instructions equally and does not default to Windows.
- Consider adding a note clarifying that the SDK and features are cross-platform, and provide links to Linux/macOS setup guides if available.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-ios.md
...s/closed-captions/closed-captions-teams-interop-ios.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a subtle Windows bias by referencing Windows first in the resource creation link (with '?tabs=windows' in the URL), and by not mentioning or providing parity for Linux or macOS in the prerequisites or resource creation steps. However, all code samples are platform-neutral (Swift/iOS), and there are no explicit Windows-only tools or PowerShell examples.
Recommendations
- Update prerequisite links to either be platform-neutral or provide explicit tabs/sections for Linux and macOS, not just Windows.
- In the resource creation step, mention or link to instructions for Linux and macOS users, ensuring all platforms are equally represented.
- Review all quickstart and reference links to ensure they do not default to Windows and provide parity for Linux/macOS.
- Add a note clarifying that the instructions and features are available cross-platform where applicable, or specify any platform limitations.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/chat/includes/chat-az-cli.md
...tion-services/quickstarts/chat/includes/chat-az-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally provides parity between Windows, macOS, and Linux for environment variable setup, with clear tabs for each OS. However, there is a notable Windows-first bias: Windows instructions and links are consistently presented before Linux/macOS equivalents. For example, the Azure CLI installation link points to the Windows-specific page, and in environment variable setup, Windows is always listed first.
Recommendations
- Present OS options in a neutral or rotating order (e.g., Linux, macOS, Windows) rather than always listing Windows first.
- In the prerequisites, provide a general Azure CLI installation link or links for all major OSes, not just Windows.
- Ensure that all examples and instructions are equally detailed for Linux and macOS, and consider highlighting cross-platform commands where possible.
- Where possible, use language that does not assume Windows as the default environment.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/access-tokens/access-token-net.md
...ts/identity/includes/access-tokens/access-token-net.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page shows mild Windows bias by listing Windows command-line environments (cmd, PowerShell) before Bash when instructing users to run .NET CLI commands. However, all actual commands shown are cross-platform and there are no PowerShell-specific scripts, Windows-only tools, or missing Linux examples. The instructions and code samples are generally OS-agnostic.
Recommendations
- List Bash (or 'terminal') before Windows environments (cmd, PowerShell) when mentioning command-line usage to avoid implying Windows primacy.
- Explicitly state that all CLI commands are cross-platform and can be run on Windows, Linux, or macOS.
- Consider including a short note or section confirming Linux/macOS compatibility for the steps, especially for environment variable usage and .NET SDK installation.
- If any platform-specific issues exist (e.g., environment variable syntax differences), provide examples for both Windows and Linux/macOS.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/active-directory/service-principal-net.md
...ity/includes/active-directory/service-principal-net.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a mild 'windows_first' bias by listing Windows terminal options (Command Prompt, PowerShell) before Bash when instructing users to open a terminal. All other instructions and code samples are platform-agnostic, relying on .NET Core/SDK and not using Windows-specific tools or patterns. There are no PowerShell-specific commands, nor are there missing Linux examples, but the ordering subtly prioritizes Windows environments.
Recommendations
- When mentioning terminal options, list Bash (or 'Bash or other Unix shells') before or alongside Command Prompt and PowerShell to avoid implying Windows is the default or preferred environment.
- Explicitly state that all commands work cross-platform (Windows, Linux, macOS) to reinforce parity.
- Where possible, provide example output or troubleshooting notes for both Windows and Linux terminals, especially if there are known differences.
- Consider linking to .NET cross-platform documentation or prerequisites for Linux users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/rooms/includes/rooms-quickstart-call-web.md
...uickstarts/rooms/includes/rooms-quickstart-call-web.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a subtle Windows bias by mentioning the Microsoft Installer (MSI) as the method to install Node.js, which is a Windows-specific installer, without referencing Linux/macOS installation methods. No explicit PowerShell or Windows-only commands are present, and most instructions use cross-platform tools (npm, npx, webpack). However, the installation prerequisite could confuse or exclude Linux/macOS users.
Recommendations
- Mention cross-platform installation options for Node.js, such as using package managers like apt (Linux), brew (macOS), or direct downloads for all platforms.
- Provide links or brief instructions for installing Node.js on Linux and macOS alongside the MSI reference.
- Clarify that all command-line instructions (npm, npx, mkdir, cd) are valid for Windows, Linux, and macOS terminals.
- Avoid referencing platform-specific installers unless alternatives are also provided.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/rooms/includes/rooms-quickstart-java.md
...es/quickstarts/rooms/includes/rooms-quickstart-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation exhibits a minor 'windows_first' bias in the section instructing users to open a console window, where 'cmd' and 'PowerShell' (Windows shells) are mentioned before 'Bash' (common on Linux/macOS). All other instructions and code samples are cross-platform (Java/Maven), and there are no Windows-specific tools, commands, or exclusive PowerShell examples. No Linux-specific instructions or examples are missing, but the ordering subtly prioritizes Windows environments.
Recommendations
- When listing console environments, use a neutral or alphabetical order (e.g., 'Bash, cmd, or PowerShell') or explicitly state that any terminal (cmd, PowerShell, Bash, Terminal, etc.) can be used.
- Where possible, clarify that all commands are cross-platform and work on Windows, Linux, and macOS.
- If there are any platform-specific steps (e.g., setting environment variables, installing Maven), provide both Windows and Linux/macOS instructions or links.
- Consider adding a note at the start of the 'Set up' section confirming that the instructions are valid for all major operating systems.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/phone-numbers-az-cli.md
...quickstarts/telephony/includes/phone-numbers-az-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation shows a mild Windows bias by presenting the Windows installation link for Azure CLI first and listing the Windows environment variable instructions before macOS and Linux. However, command-line examples use Azure CLI, which is cross-platform, and Linux/macOS instructions are present.
Recommendations
- Provide a platform-neutral Azure CLI installation link or mention all platforms equally in the prerequisites.
- Rotate or randomize the order of OS tabs (Windows, macOS, Linux) for environment variable setup, or default to a platform-neutral view.
- Explicitly state that all CLI commands work on Windows, macOS, and Linux to reinforce cross-platform parity.
- Where possible, use language that does not imply Windows is the default or primary platform.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-resource-id.md
...ces/quickstarts/voice-video-calling/get-resource-id.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only a screenshot-based method for finding the Azure Resource ID, without any command-line examples. It does not mention or provide instructions for Linux users (e.g., using Azure CLI), nor does it provide PowerShell or Windows-specific instructions, but the absence of Linux/CLI examples may disadvantage non-Windows users.
Recommendations
- Add Azure CLI command-line instructions for finding the Resource ID, which work cross-platform (Windows, Linux, macOS).
- If providing PowerShell examples, ensure equivalent Azure CLI examples are also included.
- Clarify that the Resource ID can be obtained via the Azure Portal (as shown) or via command-line tools, and provide both methods.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/closed-captions/closed-captions-javascript.md
...includes/closed-captions/closed-captions-javascript.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation shows a mild Windows bias in the prerequisites section, where the link to creating an Azure Communication Services resource includes a 'tabs=windows' parameter and the URL suggests a Windows-first or Windows-only quickstart. There are no explicit Linux or cross-platform instructions or examples, and no mention of Linux tools or environments. However, the main content is JavaScript code, which is inherently cross-platform.
Recommendations
- Ensure that prerequisite links and quickstarts include Linux (and macOS) tabs or instructions, not just Windows.
- Remove or generalize the 'tabs=windows' parameter in documentation links, or add equivalent Linux/macOS tabs.
- Explicitly state that the instructions and code samples are cross-platform and can be used on Linux, macOS, and Windows.
- Where platform-specific setup is required (e.g., for SDK installation or environment setup), provide Linux-specific guidance alongside Windows instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/calling-widget/calling-widget-js-tutorial.md
...tutorials/calling-widget/calling-widget-js-tutorial.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild 'windows_first' bias by presenting Windows command prompt instructions before macOS equivalents. However, it does provide both Windows and macOS/Linux commands for project setup, and all other instructions (Node, VS Code, running the app) use cross-platform commands. There are no PowerShell-specific examples, exclusive Windows tools, or missing Linux examples.
Recommendations
- Present macOS/Linux commands before or alongside Windows commands to avoid implying Windows is the primary platform.
- Explicitly mention Linux in command examples (e.g., 'For macOS and Linux, use this command:').
- Where possible, use language such as 'terminal' instead of 'command prompt' to be more platform-neutral.
- Ensure that all instructions and troubleshooting steps are validated on Linux, and add Linux-specific notes if any differences exist.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/voice-video-calling/diagnostic-options-tag.md
...utorials/voice-video-calling/diagnostic-options-tag.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page primarily presents telemetry examples and user agent strings where the Windows platform is mentioned first and exclusively (e.g., 'Mozilla/5.0 (Windows NT 10.0; Win64; x64)'). There are no explicit Linux or cross-platform examples, and the only OS context shown is Windows. However, there are no Windows-specific tools, PowerShell commands, or instructions that would further increase the bias.
Recommendations
- Include user agent string examples from Linux and macOS clients to demonstrate cross-platform support.
- Explicitly mention that the SDK and telemetry tagging work on all supported platforms, not just Windows.
- If platform-specific behaviors exist, document them for Linux and macOS as well.
- Add a note or section clarifying that the instructions and examples are applicable regardless of the operating system.