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 251-275 of 367 flagged pages
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/entra-id/support-entra-id-users-net.md
...entity/includes/entra-id/support-entra-id-users-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by listing Windows console environments (cmd, PowerShell) before Bash when describing how to create a new C# application. There are no explicit Linux-specific instructions, examples, or troubleshooting notes, and no mention of Linux tools or patterns. All commands are platform-agnostic (dotnet CLI), but the lack of Linux-specific context or parity in examples may hinder Linux users.
Recommendations
- List Bash (Linux/macOS) before or alongside Windows consoles (cmd, PowerShell) when describing command-line usage.
- Add explicit notes or examples for Linux users, such as verifying .NET SDK installation on Linux, using environment variables in Bash, and opening files with Linux editors (e.g., nano, vim).
- Include troubleshooting tips for common Linux issues (e.g., permissions, path differences).
- Clarify that all commands work cross-platform and provide links to .NET installation guides for Linux and macOS.
- Mention Linux-specific package managers or installation steps if relevant.
Create Pull Request
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/includes/create-resource-az-cli.md
...ervices/quickstarts/includes/create-resource-az-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by linking only to the Windows-specific Azure CLI installation instructions and not mentioning or linking to Linux or macOS equivalents. All command-line examples use the Azure CLI, which is cross-platform, but there is no explicit mention or guidance for Linux or macOS users. The installation link and lack of platform parity in instructions may confuse or exclude non-Windows users.
Recommendations
- Provide installation links for Azure CLI on all supported platforms (Windows, Linux, macOS), or use a platform-agnostic link.
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS terminals.
- If there are any platform-specific considerations (e.g., shell differences), mention them or provide examples for Bash/zsh as well as PowerShell.
- Avoid using the 'azurepowershell-interactive' code block type if the commands are not PowerShell-specific; use a more neutral code block or clarify that the commands are shell-agnostic.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/includes/create-resource-net.md
...n-services/quickstarts/includes/create-resource-net.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides only C#/.NET code examples and instructions for interacting with Azure Communication Services, with no explicit mention of Linux-specific workflows, shell commands, or cross-platform considerations. Steps for setting environment variables and retrieving subscription IDs reference the Azure portal (web UI), which is platform-neutral, but there are no CLI examples (e.g., Azure CLI or Bash) that would be familiar to Linux users. All code assumes a Windows/.NET development environment, and there are no PowerShell-specific commands, but the lack of Linux/Bash equivalents or explicit cross-platform guidance results in a Windows-first and missing-Linux-example bias.
Recommendations
- Add Azure CLI (az) command examples for common tasks such as retrieving the subscription ID, creating service principals, and managing resource groups.
- Provide Bash shell commands for setting environment variables, in addition to the implicit Windows/PowerShell approach.
- Explicitly mention that the .NET SDK and examples work on Linux, and link to .NET Core installation instructions for Linux distributions.
- Include at least one end-to-end example using the Azure CLI and Bash to demonstrate parity for Linux users.
- Clarify that all portal-based instructions are platform-agnostic, and offer CLI alternatives where possible.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/network-security-perimeter.md
...ion-services/quickstarts/network-security-perimeter.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by linking exclusively to Windows installation instructions for Azure CLI and omitting Linux-specific guidance or examples. All command-line examples use Azure CLI, which is cross-platform, but there is no mention of Linux installation, shell usage, or parity checks. The page does not reference PowerShell or Windows-only tools directly, but the installation instructions and context assume a Windows-first audience.
Recommendations
- Add explicit instructions and links for installing Azure CLI on Linux and macOS, not just Windows.
- Clarify that all Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific notes if needed (e.g., quoting, environment variables).
- Include examples or screenshots using Linux shells (bash/zsh) and terminal environments.
- Review and update any referenced documentation links to ensure Linux parity and visibility.
- If mentioning Cloud Shell, clarify that it is OS-agnostic and available in browser for all platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/sms/includes/receive-sms-js.md
...on-services/quickstarts/sms/includes/receive-sms-js.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by instructing users to run the Azure Function locally using 'F5' in Visual Studio Code, a shortcut that is only available in the Windows/macOS GUI version of VS Code and not in headless or terminal-only Linux environments. There are no explicit Linux-specific instructions or terminal-based alternatives for running or debugging the function. However, the rest of the instructions (ngrok, Azure CLI) are cross-platform and use bash commands, which are Linux-friendly. No PowerShell or Windows-only tools are used, but the lack of Linux-specific guidance or parity in the local run/debug instructions is a notable omission.
Recommendations
- Add instructions for running the Azure Function locally using the command line (e.g., 'func start' or 'npm start') for Linux users who may not use the VS Code GUI.
- Clarify that 'F5' is a Visual Studio Code GUI shortcut and provide alternative steps for users on Linux or those using VS Code in a headless environment.
- Explicitly state that all CLI and ngrok commands work on Linux, and provide any Linux-specific troubleshooting tips if relevant.
- Consider adding a section or callout box for Linux users to ensure parity and inclusivity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/rooms/includes/rooms-quickstart-net.md
...ces/quickstarts/rooms/includes/rooms-quickstart-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page shows mild Windows bias. In the 'Create a new C# application' section, Windows shells (cmd, PowerShell) are mentioned before Bash, and no Linux-specific instructions or examples are provided. All command-line examples use the generic 'dotnet' CLI, which is cross-platform, but there are no explicit Linux or macOS instructions, troubleshooting tips, or environment-specific notes. The documentation assumes parity but does not demonstrate it.
Recommendations
- List Bash (Linux/macOS) before or alongside cmd/PowerShell when referencing console windows.
- Add explicit notes or sections for Linux/macOS users, such as verifying .NET installation, common permissions issues, or differences in environment setup.
- Include example commands for installing .NET Core on Linux/macOS, or link to relevant platform-specific installation guides.
- Provide troubleshooting tips for common Linux/macOS issues (e.g., executable permissions, path issues).
- Clarify that all dotnet CLI commands work identically on Linux/macOS, or call out any known differences.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/rooms/manage-rooms-call.md
...cation-services/quickstarts/rooms/manage-rooms-call.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by linking to quickstarts and conceptual documentation with Windows-specific tabs or pivots, such as 'tabs=windows' and 'platform-azcli'. There are no explicit Linux or cross-platform CLI examples, and no mention of Linux-specific tools or instructions. All code samples are language SDK-based and platform-agnostic, but supporting links and instructions default to Windows, omitting Linux parity.
Recommendations
- Add explicit Linux instructions and examples alongside Windows, especially for setup, CLI usage, and environment configuration.
- Ensure all quickstart and concept links include Linux tabs or pivots, or provide platform-neutral guidance.
- Mention cross-platform compatibility for SDKs and clarify any OS-specific requirements or differences.
- Where CLI or shell commands are referenced, provide both PowerShell (Windows) and Bash (Linux/macOS) examples.
- Audit all linked documentation to ensure Linux parity and avoid defaulting to Windows-first navigation.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/sms/includes/sms-opt-out-api-csharp.md
...ces/quickstarts/sms/includes/sms-opt-out-api-csharp.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides only a C# code sample and references the .NET Core SDK, which, while cross-platform, is more commonly associated with Windows development. There are no examples or instructions for using Linux-specific tools, shells, or scripting languages (e.g., Bash, curl), nor is there mention of how to run the sample on Linux or macOS. The documentation implicitly assumes a Windows-centric development environment.
Recommendations
- Add equivalent code samples or instructions using Bash and curl to demonstrate how to interact with the Opt-Out API from Linux environments.
- Explicitly mention that .NET Core SDK is cross-platform and provide guidance or links for installing and running it on Linux and macOS.
- Include examples using other common cross-platform languages (e.g., Python) to broaden accessibility.
- Ensure that any command-line instructions or environment setup steps are shown for both Windows (e.g., PowerShell, CMD) and Linux/macOS (e.g., Bash).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/number-lookup-net.md
...es/quickstarts/telephony/includes/number-lookup-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation uses generic terms like 'terminal or command window' but implicitly assumes a Windows-centric development environment by not providing explicit Linux (or macOS) shell examples or addressing platform-specific differences. All command-line instructions use .NET CLI commands, which are cross-platform, but there is no mention of Linux-specific considerations (e.g., shell syntax, environment variable setup, or package manager alternatives). The documentation does not provide any Linux- or macOS-specific guidance or examples, and the phrase 'command window' is more familiar to Windows users.
Recommendations
- Explicitly mention that all commands work on Windows, Linux, and macOS, and clarify that 'terminal' refers to Bash/zsh/etc. on Linux/macOS and 'command window' or 'PowerShell' on Windows.
- Provide Linux/macOS-specific notes where relevant, such as how to set environment variables (e.g., 'export VAR=VALUE' for Bash vs. 'set VAR=VALUE' for Windows CMD).
- Include example commands for both Windows and Linux/macOS where differences exist (e.g., path separators, environment variable syntax).
- Use more inclusive language, such as 'open a terminal (Command Prompt, PowerShell, or Bash)' instead of 'terminal or command window'.
- Add troubleshooting notes for common cross-platform issues (e.g., permissions, executable paths).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/voice-routing-sdk-csharp.md
...kstarts/telephony/includes/voice-routing-sdk-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by listing Windows shells (Command Prompt, PowerShell) before Bash when instructing users to open a console window. No Linux-specific tools or commands are missing, but the ordering and mention of Windows environments first may subtly prioritize Windows users. All command-line examples use .NET CLI, which is cross-platform, and no exclusive Windows tools are used.
Recommendations
- List Bash (Linux/macOS) first or equally with Command Prompt and PowerShell when mentioning console options.
- Explicitly state that all commands work on Linux, macOS, and Windows.
- Consider providing a short note or section for Linux/macOS users, confirming parity and any OS-specific considerations (such as package managers or environment setup).
- Use neutral phrasing such as 'In a terminal window (such as Bash, Command Prompt, or PowerShell)...' to avoid implicit prioritization.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/closed-captions/closed-captions-android.md
...ng/includes/closed-captions/closed-captions-android.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the prerequisites and resource management sections. Links to resource creation and cleanup explicitly reference Windows tabs or pivots, and there is no mention of Linux or cross-platform equivalents. All code examples are Android/Java-specific (which is neutral), but platform-specific instructions and links default to Windows, with no Linux guidance or parity.
Recommendations
- Update prerequisite and cleanup links to include Linux or cross-platform tabs/pivots, or provide explicit Linux instructions where relevant.
- Ensure that any platform-specific instructions (e.g., for Azure CLI, resource management) are presented for both Windows and Linux, or clarify when steps are platform-agnostic.
- Review and update quickstart/resource links to avoid defaulting to Windows, or provide a selector for the user's platform.
- Add a note clarifying that the steps are applicable to both Windows and Linux unless otherwise specified.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/custom-teams-endpoint/voice-video-calling-cte-javascript.md
...m-teams-endpoint/voice-video-calling-cte-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by recommending the MSI installer for Node.js and linking to resource creation instructions with a Windows-specific tab. There are no explicit Linux instructions or examples for installing Node.js, creating resources, or running the sample, even though all steps are cross-platform. The documentation does not mention Linux package managers or provide parity for Linux users.
Recommendations
- Provide Linux-specific instructions for installing Node.js (e.g., using apt, yum, or other package managers).
- Ensure resource creation links default to a neutral or cross-platform tab, or explicitly mention Linux/macOS options.
- Add notes or examples confirming that all steps work on Linux and macOS, and highlight any platform-specific differences if they exist.
- Avoid recommending Windows-only installers (MSI) without mentioning alternatives for other platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-teams-interop-group-calls.md
...video-calling/get-started-teams-interop-group-calls.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates a mild Windows bias. It references the Azure portal (which is cross-platform but often perceived as Windows-centric) and, more notably, requires Teams users to be 'Enterprise Voice enabled' with a link to a PowerShell-based guide. The Teams deployment link also points to a Microsoft documentation page that is Windows-focused. There are no explicit Linux or macOS-specific instructions, nor are there alternative command-line examples (e.g., Bash, Azure CLI) for enabling Teams features. However, the main code samples and instructions are platform-neutral (JavaScript, npx, browser-based), and no PowerShell or cmd commands are directly shown.
Recommendations
- Provide explicit instructions or links for enabling Teams features (like Enterprise Voice) using cross-platform tools such as Azure CLI or Microsoft Graph API, if available.
- Clarify that the Azure portal and Teams administration can be accessed from any OS/browser, not just Windows.
- If PowerShell is required, mention that PowerShell Core is available on Linux/macOS and provide installation guidance.
- Add notes or examples for Linux/macOS users where administrative tasks (e.g., Teams user setup) may differ.
- Ensure that all prerequisite links and instructions are inclusive of non-Windows environments, or at least acknowledge platform differences.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-video-constraints.md
...s/voice-video-calling/get-started-video-constraints.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides platform-specific guidance for Windows, Android, iOS, and Web, but does not include any examples or guidance for Linux. Additionally, 'Windows' is listed as a primary platform, while Linux is omitted, which may suggest a bias toward Windows environments.
Recommendations
- Add a dedicated Linux section or clarify Linux support, especially for desktop or web scenarios where Linux is relevant.
- If the Web/JavaScript example is intended to cover Linux, explicitly state this to avoid confusion.
- Ensure that Linux users are not excluded by providing parity in examples, troubleshooting, and platform pivots.
- Consider listing platforms in a neutral or alphabetical order to avoid implicit prioritization.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-with-closed-captions.md
...oice-video-calling/get-started-with-closed-captions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides platform-specific guidance for web, Windows, Android, and iOS, but omits Linux as a platform. Additionally, resource cleanup instructions reference Windows tabs and do not mention Linux equivalents, suggesting a Windows-first approach and missing Linux parity.
Recommendations
- Add a Linux-specific pivot or section if the SDK or service supports Linux clients.
- Include Linux examples for resource cleanup, such as CLI commands or instructions relevant to Linux environments.
- Ensure parity in sample links and next steps by providing Linux-relevant samples or guidance.
- Clarify platform support in the introduction, explicitly stating whether Linux is supported or not.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-with-real-time-text.md
...voice-video-calling/get-started-with-real-time-text.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page shows a mild Windows bias by listing Windows (C#) terminology and class names before Linux or cross-platform equivalents, and by using Windows-specific naming conventions (e.g., 'Details' vs. 'Info') in tables. There is no explicit mention of Linux or Linux-specific instructions, and the C# example is labeled as 'Windows', which may imply C# is only for Windows, even though .NET Core is cross-platform.
Recommendations
- Clarify that C#/.NET examples are cross-platform and not limited to Windows. Consider labeling the C# section as 'C# (.NET)' instead of 'Windows (C#)'.
- In naming convention tables, include Linux or cross-platform terminology if applicable, or clarify that the differences are between .NET and mobile SDKs, not OS-specific.
- Ensure that examples and terminology do not imply that certain languages or SDKs are exclusive to Windows when they are not.
- If there are Linux-specific considerations or examples (e.g., for .NET on Linux), include them to ensure parity.
- Review and update documentation to use platform-neutral language where possible, especially in class/property naming and section headers.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-with-voice-video-calling-custom-teams-client.md
...t-started-with-voice-video-calling-custom-teams-client.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides platform-specific quickstart guides for web, Windows, Android, and iOS, but does not mention or provide examples for Linux desktop environments. Additionally, resource cleanup instructions reference Windows tabs, with no mention of Linux equivalents, suggesting a Windows-first approach and a lack of Linux parity.
Recommendations
- Add explicit Linux desktop instructions or examples, especially for Electron or other common Linux desktop frameworks.
- Ensure resource cleanup instructions include Linux-specific tabs or CLI examples (e.g., Bash, Azure CLI on Linux).
- Review referenced samples and guides to confirm Linux compatibility and provide Linux-specific guidance where needed.
- Consider including a 'platform-linux' pivot zone alongside existing platform pivots.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/call-recording-samples/call-recording-csharp.md
...cludes/call-recording-samples/call-recording-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively provides C#/.NET code samples and instructs users to download the .NET SDK, which is traditionally associated with Windows development. There are no examples or instructions for Linux users, such as using .NET on Linux, alternative SDKs, or cross-platform CLI usage. No mention is made of Linux-specific tools, shell commands, or environment setup, and the documentation implicitly assumes a Windows-centric development environment.
Recommendations
- Explicitly mention that .NET and the Azure Communication Services SDK are cross-platform and can be used on Linux and macOS as well as Windows.
- Provide installation instructions for the .NET SDK on Linux (e.g., using apt-get, yum, or snap).
- Include code samples or instructions for running the sample app on Linux, such as using the dotnet CLI in a bash shell.
- Add troubleshooting tips or notes for Linux users, such as file permissions or environment variables.
- Reference Linux-compatible tools for event handling and webhooks, and clarify that Azure Event Grid and related APIs are OS-agnostic.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/call-recording-samples/call-recording-java.md
...includes/call-recording-samples/call-recording-java.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the file path example for downloading recordings, which uses Windows-style backslashes (e.g., '.\%s.%s'). There are no explicit Linux or cross-platform file path examples, nor is there mention of Linux-specific considerations or alternatives. All code samples and instructions are platform-neutral Java, but the only file system example assumes Windows conventions.
Recommendations
- Provide file path examples for both Windows (e.g., '.\\%s.%s') and Linux/macOS (e.g., './%s.%s') when showing how to save downloaded files.
- Add a note clarifying that the Path API in Java is cross-platform, and users should use platform-appropriate path separators.
- Explicitly mention that the sample code works on Linux/macOS as well as Windows, and highlight any OS-specific considerations (such as file permissions or path formats).
- Include troubleshooting tips for common Linux issues (e.g., permissions, case sensitivity, environment variables) if relevant.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/get-started/get-started-javascript.md
...calling/includes/get-started/get-started-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows a subtle Windows bias by recommending the Windows MSI installer for Node.js in the prerequisites, without mentioning Linux installation methods. No explicit Linux or cross-platform installation instructions are provided, and no Linux-specific considerations are discussed. All command-line instructions use generic 'console' or 'terminal' language, which is good, but the only installation method mentioned is Windows-centric.
Recommendations
- In the prerequisites, provide installation instructions or links for Node.js on Linux (e.g., using apt, yum, or nvm) alongside the Windows MSI installer.
- Explicitly state that the instructions are cross-platform and can be followed on Linux, macOS, or Windows.
- Where possible, use neutral language such as 'terminal' instead of 'command window', and clarify that all commands work in Bash, PowerShell, or CMD.
- Add a note or section for Linux users, mentioning any platform-specific considerations (e.g., installing build tools or dependencies for Node.js native modules).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/references/how-to-collect-call-info.md
...e-video-calling/references/how-to-collect-call-info.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation instructs users to obtain the ACS resource ID via the Azure Portal, which is a web-based GUI commonly used on Windows. There are no examples or instructions for obtaining this information via cross-platform tools (e.g., Azure CLI or REST API), and no mention of Linux-friendly methods. All screenshots and instructions assume use of the portal, which may not be ideal for Linux or CLI-centric users.
Recommendations
- Add instructions for obtaining the ACS resource ID using the Azure CLI (az communication) with example commands.
- Include REST API methods for retrieving resource IDs for users who prefer scripting or automation.
- Clarify that the Azure Portal is web-based and can be used from any OS, but provide parity with CLI/API examples.
- Ensure screenshots and instructions do not assume a specific OS unless necessary.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-ai-javascript.md
...ices/samples/includes/call-automation-ai-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation shows evidence of Windows bias by referencing Windows-specific tabs in prerequisite links and by instructing users to open a PowerShell window to run the application, without mentioning Linux or cross-platform alternatives (e.g., Bash, Terminal). There are no explicit Linux examples or instructions, and the default assumption is a Windows environment.
Recommendations
- Provide parallel instructions for Linux/macOS users, such as opening a terminal instead of PowerShell.
- Avoid referencing Windows-specific tabs or provide links that default to a neutral or cross-platform view.
- Explicitly state that the commands (e.g., npm run dev, devtunnel) work on all platforms and show examples in both PowerShell and Bash if there are differences.
- Mention any platform-specific prerequisites or troubleshooting steps for Linux/macOS users.
- Use neutral language like 'terminal' or 'command prompt' instead of 'PowerShell window' unless a Windows-only step is required.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-ai-csharp.md
...services/samples/includes/call-automation-ai-csharp.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias towards Windows by referencing Windows-specific tabs in prerequisite links and not providing explicit Linux instructions or examples. The setup and run instructions assume familiarity with .NET and do not mention cross-platform compatibility or provide Linux/macOS-specific guidance. There are no Linux-specific examples or troubleshooting tips, and the linked resources often default to Windows tabs.
Recommendations
- Ensure that all prerequisite links and quickstart guides include Linux/macOS tabs and that these are referenced or highlighted equally with Windows.
- Explicitly state that the sample can be run on Linux and macOS, and provide any platform-specific instructions if needed (e.g., installing .NET SDK on Linux).
- Include Linux/macOS shell commands or notes where relevant, especially for environment setup and running the application.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, path differences, .NET installation).
- Review linked documentation to ensure parity in instructions and examples for all supported platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-ai-python.md
...services/samples/includes/call-automation-ai-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows mild Windows bias, primarily by linking to resource creation guides with a '?tabs=windows' parameter and not explicitly providing Linux-specific instructions or examples. While the main setup and run instructions use cross-platform commands (pip, python, bash), there is no mention of Linux or macOS alternatives in the prerequisites or setup steps. The phrase 'run it from PowerShell, a command prompt, or a Unix terminal' is inclusive, but the linked resources default to Windows instructions.
Recommendations
- Provide explicit Linux/macOS tabs or links in prerequisite resource creation steps, or ensure links default to a neutral or platform-agnostic view.
- Add a note or section confirming that all commands work on Linux/macOS, and mention any platform-specific considerations.
- Where possible, include Linux/macOS screenshots or terminal output to reinforce parity.
- Review all links for '?tabs=windows' and either remove the tab parameter or add equivalent Linux/macOS tabs.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/audio-quality-enhancements/includes/web.md
...s/tutorials/audio-quality-enhancements/includes/web.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its browser support statements and lack of Linux-specific guidance. All examples and instructions focus on Chrome and Edge desktop browsers, which are most commonly used on Windows. There is no mention of Linux compatibility, Linux browsers (such as Firefox), or platform-specific considerations for Linux users. No Linux command-line or environment examples are provided, and the documentation does not address whether the features work on Linux systems or how to troubleshoot on Linux.
Recommendations
- Explicitly state whether audio effects features are supported on Linux desktop environments and browsers (e.g., Chrome on Ubuntu, Fedora, etc.).
- Add Linux-specific examples or troubleshooting steps, such as verifying support on Linux Chrome/Edge or handling permissions and device selection on Linux.
- Mention any known limitations or differences when using the SDK on Linux versus Windows (e.g., browser APIs, hardware support).
- Include guidance for Linux users on installing dependencies, configuring audio devices, or resolving common issues.
- Consider referencing or testing with Linux browsers beyond Chrome and Edge, such as Firefox, and document compatibility.