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 651-656 of 656 flagged pages
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/access-tokens/access-token-az-cli.md
...identity/includes/access-tokens/access-token-az-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides parity between Windows, macOS, and Linux for environment variable setup, but consistently lists Windows instructions and tabs before macOS and Linux. All CLI examples use Azure CLI, which is cross-platform, and there are no PowerShell-specific or Windows-only tools used. However, the ordering of OS instructions may subtly prioritize Windows users.
Recommendations
- Rotate the order of OS tabs or list Linux/macOS first in some sections to avoid implicit prioritization of Windows.
- Explicitly state that all CLI commands work identically across Windows, macOS, and Linux.
- Consider combining macOS and Linux instructions when they are identical, or clarify any differences.
- Ensure that any references to editors (e.g., Visual Studio) are accompanied by cross-platform alternatives (e.g., VS Code, JetBrains Rider) where relevant.
Create Pull Request
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/chat-hero-sample.md
...les/communication-services/samples/chat-hero-sample.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation refers to opening 'PowerShell, Windows Terminal, Command Prompt, or equivalent' when instructing users to open a terminal, listing Windows-specific tools first and not naming any Linux or macOS terminals. No explicit Linux or macOS examples or tools are mentioned, but the instructions are otherwise cross-platform (Node.js, npm, git, Azure CLI).
Recommendations
- Explicitly mention Linux and macOS terminal options (e.g., 'Terminal (macOS), GNOME Terminal (Linux), PowerShell, Windows Terminal, Command Prompt, or equivalent').
- Provide assurance that all commands (git, npm, Azure CLI) work on Linux/macOS as well as Windows.
- Consider adding a short section or note confirming cross-platform compatibility and calling out any OS-specific considerations.
- If screenshots or file paths are shown, include examples for both Windows and Linux/macOS where they differ.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/local-preview-mirroring.md
...kstarts/voice-video-calling/local-preview-mirroring.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides platform-specific instructions for Windows, Android, and iOS, but does not mention or provide guidance for Linux or other desktop platforms. This omission may leave Linux users without clear instructions or support for the feature.
Recommendations
- Add a Linux-specific section or clarify Linux support status for local preview mirroring.
- If the feature is not available on Linux, explicitly state this to inform users.
- If parity is possible, provide instructions or code samples for Linux desktop environments (e.g., using Electron, web, or native Linux clients).
- Ensure future documentation includes Linux alongside Windows, Android, and iOS in platform pivots.
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 mentions Windows-specific consoles (cmd, PowerShell) before Bash when describing how to run commands, which may suggest a Windows-first perspective. However, all command-line and code examples are cross-platform (Java, Maven) and do not rely on Windows-only tools or patterns. There are no PowerShell-specific scripts, Windows-only tools, or missing Linux examples.
Recommendations
- When listing console options, use neutral or alphabetical order (e.g., 'Bash, cmd, or PowerShell') to avoid implying a Windows-first workflow.
- Explicitly state that all commands work on Windows, Linux, and macOS, and provide any OS-specific notes if needed.
- Consider including a short section or note confirming cross-platform compatibility for the setup and execution steps.
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 page exhibits a mild 'windows_first' bias in the prerequisites section, where the link for creating an Azure Communication Services resource includes a '?tabs=windows' query parameter and references 'platform-azp', suggesting a default or primary focus on Windows. No explicit Linux or cross-platform instructions or examples are provided, but the rest of the documentation is platform-neutral JavaScript/TypeScript code.
Recommendations
- Ensure that prerequisite links and quickstart guides reference both Windows and Linux (and macOS) tabs or provide a neutral/default tab.
- Explicitly mention that the JavaScript SDK and code samples are cross-platform and can be used on Windows, Linux, and macOS environments.
- Where platform-specific setup is referenced (such as resource creation), provide equivalent instructions or links for Linux and macOS users.
- Audit all quickstart and resource links to avoid defaulting to Windows-specific tabs or instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/router/includes/router-quickstart-java.md
.../quickstarts/router/includes/router-quickstart-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows consoles (cmd, PowerShell) before Bash when describing how to run commands, which subtly prioritizes Windows environments. However, all command-line instructions use cross-platform tools (Maven, Java), and no OS-specific commands or tools are used. There are no PowerShell-specific scripts, Windows-only tools, or missing Linux examples.
Recommendations
- List Bash (or 'terminal') before cmd/PowerShell when mentioning consoles, or simply state 'in a terminal or command prompt' to avoid OS prioritization.
- Explicitly state that all commands work on Windows, Linux, and macOS.
- If possible, provide example outputs or troubleshooting notes for both Windows and Linux/macOS environments.
- Ensure that any future instructions involving environment variables, file paths, or scripts include both Windows and Linux/macOS syntax.