Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 951-975 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/scope-level/overview-azure-hybrid-benefit-scope.md
...ing/scope-level/overview-azure-hybrid-benefit-scope.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows-first bias by exclusively referencing Windows Server and SQL Server on Windows, with no mention of Linux-based SQL Server deployments or Linux tools. All examples and links (such as registering SQL VMs with the IaaS extension) are specific to Windows, and there is no guidance for users running SQL Server on Linux VMs in Azure. The documentation assumes a Windows-centric environment, omitting Linux parity in both conceptual and procedural content.
Recommendations
- Include explicit references to SQL Server on Linux, clarifying whether Azure Hybrid Benefit applies equally to Linux-based SQL Server VMs.
- Provide examples and links for registering and managing SQL Server on Linux VMs, including any differences in the IaaS extension or management process.
- Mention Linux-based tools and workflows where relevant, or clarify if only Windows environments are supported.
- Add a section or note addressing Linux users, outlining any limitations or additional steps required for Linux-based SQL Server deployments.
- Ensure that all procedural steps and tables consider both Windows and Linux scenarios, or explicitly state if a feature is Windows-only.
Create Pull Request
Azure Docs
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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits mild Windows bias. While it mentions Bash alongside cmd and PowerShell, the phrasing consistently lists Windows shells first, and there are no explicit Linux/macOS-specific instructions or troubleshooting notes. All command-line examples use the generic 'dotnet' CLI, which is cross-platform, but there are no Linux/macOS terminal screenshots, nor are there any notes about platform-specific differences (e.g., file paths, environment variables, or permissions). The documentation assumes familiarity with Windows-centric tools and patterns, and does not address Linux-specific considerations.
Recommendations
- Alternate the order of shell mentions (e.g., 'Bash, PowerShell, or cmd') or explicitly state that all commands work on Windows, Linux, and macOS.
- Include at least one terminal screenshot or code block showing commands run in a Linux/macOS terminal.
- Add a note clarifying that the .NET CLI and all code samples are cross-platform, and provide links to Linux/macOS installation instructions for .NET if not already present.
- Mention any known platform-specific issues (e.g., file permissions, path separators) if applicable.
- Consider adding a troubleshooting section for common Linux/macOS issues (e.g., 'dotnet' not found, permissions).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/sms/includes/send-sms-java.md
...ion-services/quickstarts/sms/includes/send-sms-java.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Command Prompt and PowerShell examples for creating and running the Java application, but does not include any Linux or macOS-specific shell (e.g., Bash) examples. The order of presentation lists Windows tools (Command Prompt, PowerShell) first and exclusively, omitting common Linux/Mac equivalents. This may make the documentation less accessible to users on non-Windows platforms.
Recommendations
- Add Bash (or generic Unix shell) command examples alongside Command Prompt and PowerShell for all command-line instructions.
- Present examples in a platform-neutral order or group them together (e.g., 'Windows (Command Prompt/PowerShell)', 'Linux/macOS (Bash)').
- Explicitly mention that the instructions are cross-platform and provide any necessary notes for Linux/macOS users (e.g., differences in path separators, environment variables, or prerequisites).
- Where possible, use platform-agnostic terminology such as 'terminal' or 'shell' instead of 'command window'.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-reverse-dns.md
...re-docs/blob/main//articles/dns/private-reverse-dns.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides a reverse DNS workflow in Azure Private DNS but only demonstrates DNS resolution testing using a Windows command prompt (nslookup with C:\> prompt and PowerShell formatting). There are no Linux or cross-platform command-line examples, and the only example of DNS resolution is shown in a Windows context. This may lead Linux or macOS users to feel excluded or unsure how to perform equivalent operations.
Recommendations
- Include Linux/macOS command-line examples for DNS resolution, such as showing nslookup or dig usage in a bash shell (e.g., $ nslookup 10.1.2.5 or $ dig -x 10.1.2.5).
- Present both Windows and Linux/macOS examples side-by-side or in sequence, ensuring parity.
- Avoid using only Windows-style prompts (C:\>) and PowerShell formatting; use generic or platform-neutral formatting where possible.
- Explicitly mention that the DNS resolution steps can be performed from any OS with appropriate DNS tools, not just Windows.
- If screenshots are used, consider including at least one from a Linux terminal to demonstrate inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-dns-migration-guide.md
...blob/main//articles/dns/private-dns-migration-guide.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell. All automation and migration steps are provided exclusively as PowerShell scripts, with instructions to run them in an 'elevated PowerShell window.' There are no equivalent Bash, Azure CLI, or Linux-native instructions or scripts. Prerequisites and installation steps assume a Windows environment, and there is no mention of how Linux or macOS users should perform the migration. While Azure CLI is briefly mentioned for listing zones, the actual migration process is only documented for PowerShell/Windows users.
Recommendations
- Provide equivalent Bash or shell script for Linux/macOS users, or at least document how to run the migration using Azure CLI or SDKs on non-Windows platforms.
- Include explicit instructions for Linux/macOS environments, such as how to install required modules or run scripts.
- If the migration script is PowerShell-only, clarify whether it can be run using PowerShell Core on Linux/macOS, and provide installation steps for those platforms.
- List both Windows and Linux instructions in parallel where possible, or at least acknowledge and guide non-Windows users.
- Avoid assuming the use of 'elevated PowerShell window' as the only method; provide sudo-based alternatives for Linux/macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/telephony/includes/phone-numbers-net.md
...es/quickstarts/telephony/includes/phone-numbers-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it mentions Bash alongside cmd and PowerShell, the order consistently lists Windows shells first. There are no Linux- or macOS-specific instructions, troubleshooting notes, or examples, and no mention of platform-specific differences in environment variable setup or running the application. All command-line examples use the generic 'dotnet' CLI, which is cross-platform, but there is an implicit assumption of familiarity with Windows tools and patterns.
Recommendations
- Explicitly mention Linux and macOS in all places where terminal or shell usage is discussed, and provide example commands for Bash/zsh where appropriate.
- When listing shells, alternate or randomize the order, or use 'such as Bash, PowerShell, or cmd' to avoid Windows-first ordering.
- Add a section or note on setting environment variables for authentication on Linux/macOS (e.g., 'export AZURE_CLIENT_SECRET=...') as well as Windows (e.g., 'set AZURE_CLIENT_SECRET=...').
- Include troubleshooting tips or links for common Linux/macOS issues (such as permissions, .NET installation, or path problems).
- Ensure that all instructions are validated on Linux and macOS, and explicitly state cross-platform compatibility where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/tpe/teams-phone-extensibility-answer-teams-calls.md
...ts/tpe/teams-phone-extensibility-answer-teams-calls.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively providing PowerShell commands for Teams resource account management and DevTunnel setup, with no equivalent Bash or cross-platform CLI examples. References to Teams PowerShell modules and Windows-centric tools are made without mention of Linux alternatives or guidance for non-Windows users.
Recommendations
- Provide equivalent Bash or Azure CLI examples for all PowerShell commands, especially for associating Teams resource accounts and managing DevTunnels.
- Explicitly mention whether the PowerShell commands can be run on PowerShell Core on Linux/macOS, or provide alternatives if not.
- Include links or instructions for Linux/macOS users to install and use required tools (e.g., Teams PowerShell module, DevTunnel) on their platforms.
- Reorganize sections to present cross-platform or platform-neutral approaches first, or in parallel, rather than leading with Windows-specific tooling.
- Add a note clarifying platform support and any limitations for non-Windows environments.
Azure Docs
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
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exclusively provides C#/.NET code samples and references the .NET SDK, which is most commonly associated with Windows development environments. There are no examples or instructions for Linux users, such as using .NET on Linux, nor are there any cross-platform shell or CLI examples. The documentation implicitly assumes a Windows-centric workflow and toolchain.
Recommendations
- Include explicit instructions and examples for running the .NET SDK and sample code on Linux (e.g., using dotnet CLI on Ubuntu).
- Add bash or shell command equivalents for any setup or execution steps, not just C# code.
- Mention that .NET Core/.NET 5+ is cross-platform and provide guidance for Linux and macOS users.
- If any file paths, environment variables, or dependencies are platform-specific, provide both Windows and Linux/macOS variants.
- Consider including a Docker example for running the sample app in a cross-platform containerized environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/incoming-audio-low-volume.md
...ideo-calling/audio-issues/incoming-audio-low-volume.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation specifically references Windows system tools (volume mixer, app volume settings) and provides a screenshot of the Windows volume mixer, without mentioning or illustrating equivalent controls on Linux or macOS. There are no Linux-specific troubleshooting steps or screenshots, and the only OS-specific guidance is for Windows.
Recommendations
- Add equivalent instructions and screenshots for adjusting system and application volume on popular Linux desktop environments (e.g., GNOME, KDE).
- Mention macOS system volume and per-app volume controls where applicable.
- Rephrase OS-specific guidance to be inclusive, e.g., 'On Windows, check the volume mixer; on Linux, check your system's sound settings; on macOS, check the Sound preferences.'
- Provide links or references to official documentation for adjusting audio settings on Linux and macOS.
- If using screenshots, provide parallel images for Linux and macOS, or use generic illustrations where possible.
Azure Docs
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
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-centric tools and patterns, such as requiring Teams users to be 'Enterprise Voice enabled' via PowerShell, and linking to Microsoft documentation that is typically Windows-focused. There are no explicit Linux or cross-platform instructions or examples, and the prerequisite steps and tooling references (e.g., Azure portal, PowerShell) assume a Windows environment. There are no Linux-specific caveats, nor are alternative Linux-friendly methods mentioned for tasks like enabling Teams features or retrieving user IDs.
Recommendations
- Provide Linux-equivalent instructions for enabling Teams features (e.g., using Microsoft Graph API or cross-platform CLI instead of PowerShell).
- Explicitly mention that the JavaScript sample and build steps (using npx/webpack) are cross-platform, and provide any Linux-specific notes if needed.
- Include links or references to Linux-compatible tools for managing Teams users and Azure resources.
- Clarify that the Azure portal and Graph API are accessible from any OS, and provide screenshots or instructions from non-Windows environments where possible.
- Avoid assuming PowerShell as the default tool for Teams administration; mention alternatives such as Azure CLI, Microsoft Graph CLI, or Bash scripts.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/tpe/teams-phone-extensibility-quickstart.md
...uickstarts/tpe/teams-phone-extensibility-quickstart.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a significant Windows bias. All command-line examples for provisioning bots and Teams resources use PowerShell cmdlets (e.g., New-CsOnlineApplicationInstance, Set-CsOnlineApplicationInstance, Connect-MicrosoftTeams), and there are no equivalent Bash, Linux shell, or cross-platform CLI examples. The instructions assume the use of Windows-based tools (PowerShell, Teams PowerShell module, Azure PowerShell modules) and reference the Teams Admin Center, which is primarily accessed via a browser but is often associated with Windows environments. There is no mention of Linux or macOS alternatives, nor any guidance for users on non-Windows platforms.
Recommendations
- Provide equivalent Bash or Azure CLI commands for all PowerShell cmdlets where possible, especially for resource provisioning and bot registration.
- Explicitly state platform requirements for each tool or command, and note any cross-platform compatibility (e.g., Azure CLI is cross-platform, but Teams PowerShell module may require Windows/PowerShell Core).
- Include guidance or links for installing and using PowerShell Core on Linux/macOS if PowerShell is required.
- Where Teams Admin Center or Microsoft 365 Admin Center is referenced, clarify that these are web-based and accessible from any OS.
- Add a section or callouts for Linux/macOS users, outlining any differences or additional steps needed.
- If certain operations are only possible on Windows, clearly state this limitation and, if possible, provide workarounds or alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/includes/get-started/get-started-unity.md
...ideo-calling/includes/get-started/get-started-unity.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by emphasizing Windows-specific development patterns and tools. The prerequisites require the Unity Editor with the Universal Windows Platform workload, and package installation instructions reference the 'Windows tab' in Unity Editor and the Microsoft Mixed Reality Feature Tool, which is Windows-centric. There is no mention of Linux or macOS alternatives or guidance for cross-platform development, and no Linux-specific instructions or troubleshooting are provided.
Recommendations
- Add explicit instructions for installing and running Unity Editor on Linux and macOS, including any required workloads or caveats.
- Clarify whether the Azure Communication Services Calling SDK for Unity supports Linux and macOS, and if there are any platform-specific limitations.
- When referencing UI elements like the 'Windows tab' in Unity Editor, provide equivalent navigation for Linux/macOS or clarify if it is Windows-only.
- If the Mixed Reality Feature Tool is Windows-only, suggest alternative package installation methods for Linux/macOS users (e.g., manual package import, Unity Package Manager via manifest editing).
- Include troubleshooting tips or known issues for non-Windows platforms.
- Review all tool and workflow mentions to ensure parity or at least clear guidance for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/includes/teams-auto-attendant/teams-auto-attendant-android.md
...s/teams-auto-attendant/teams-auto-attendant-android.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a bias toward Windows by exclusively referencing the Teams Admin Center (a web tool often associated with Windows environments) for administrative tasks, omitting any mention of cross-platform or Linux-friendly alternatives such as PowerShell, CLI, or REST API methods for managing Teams Auto Attendants. There are no Linux-specific instructions or examples for setup or management tasks, and the documentation assumes use of the Teams Admin Center as the primary interface, which may not be optimal or accessible for Linux users.
Recommendations
- Provide alternative instructions for managing Teams Auto Attendants using PowerShell, Microsoft Graph API, or Azure CLI, which are cross-platform and can be used on Linux.
- Explicitly mention that the Teams Admin Center is web-based and accessible from any OS, but also offer command-line or API-based workflows for users who prefer or require non-GUI solutions.
- Include Linux-specific notes or examples where relevant, especially for tasks like obtaining resource account information or interacting with Azure services.
- Ensure that any tooling or setup steps (such as obtaining access tokens or managing Teams resources) include both GUI and CLI/API options, with parity in documentation and examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-dns-getstarted-cli.md
.../blob/main//articles/dns/private-dns-getstarted-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a clear Windows bias in the testing and verification steps. All virtual machine creation examples use Windows images, and all instructions for configuring firewalls and testing DNS resolution are provided exclusively for Windows (PowerShell commands, Windows-specific firewall rules, and Windows command prompt outputs). There are no Linux VM creation examples, nor are there instructions for configuring or testing on Linux VMs. The documentation assumes the user is working in a Windows environment for all post-provisioning steps.
Recommendations
- Add parallel Linux examples for VM creation (e.g., using --image UbuntuLTS) alongside the Windows examples.
- Provide instructions for configuring the firewall to allow ICMP on Linux VMs (e.g., using ufw or firewalld).
- Include Linux command-line examples for testing DNS resolution (e.g., using ping and dig/host commands in a bash shell).
- Show sample output from Linux shells as well as Windows PowerShell.
- Explicitly mention that the steps apply to both Windows and Linux, and provide guidance for both environments throughout the quickstart.
Azure Docs
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
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily in the prerequisites and setup sections. It recommends the Windows MSI installer for Node.js, links to resource creation instructions with a Windows-specific tab, and does not mention or provide Linux-specific installation or setup guidance. There are no Linux/macOS-specific instructions or troubleshooting notes, and the documentation assumes parity in terminal/console commands without explicitly confirming compatibility or providing alternatives.
Recommendations
- In the prerequisites, provide installation instructions for Node.js on Linux and macOS (e.g., using package managers like apt, yum, or Homebrew), not just the Windows MSI installer.
- When linking to Azure resource creation documentation, ensure the default or first tab is platform-neutral or provide explicit Linux/macOS instructions/tabs.
- Explicitly state that all terminal/console commands are cross-platform, or provide platform-specific notes if there are differences.
- Include troubleshooting tips or notes for Linux/macOS users, especially regarding permissions, camera/microphone access, and running local servers.
- Avoid language or links that default to Windows unless there is a technical reason; otherwise, present all platforms equally.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/includes/teams-call-queue/teams-call-queue-android.md
.../includes/teams-call-queue/teams-call-queue-android.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation assumes and references Microsoft-centric tools and workflows (Teams Admin Center, Microsoft Graph Explorer, Azure CLI), and does not mention or provide alternatives for Linux or cross-platform environments. All instructions for administrative tasks are given using web-based Microsoft portals or tools that are primarily designed for Windows environments, with no mention of Linux command-line or open-source alternatives. There are no PowerShell-specific examples, but the documentation is Windows-first in its approach to management and setup.
Recommendations
- Explicitly mention that Teams Admin Center and Microsoft Graph Explorer are web-based and accessible from any OS/browser, to clarify cross-platform compatibility.
- If possible, provide CLI-based alternatives (e.g., using Microsoft Graph API via curl or HTTPie) for finding the Call Queue Object ID, with example commands that work on Linux/macOS.
- For Azure CLI commands, confirm and note that Azure CLI is cross-platform and works on Linux/macOS, and provide any OS-specific installation or usage notes if needed.
- Where screenshots are used, consider including notes or alternative instructions for users on Linux who may not have the same UI experience.
- Add a section or callout summarizing cross-platform compatibility and any OS-specific considerations for all required tools and steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/includes/teams-user/teams-user-javascript.md
...o-calling/includes/teams-user/teams-user-javascript.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a mild Windows bias. In the prerequisites, enabling Teams Phone for users explicitly references a PowerShell-based process and links to a PowerShell-specific Microsoft documentation page, with no mention of Linux or cross-platform alternatives. There are no Linux-specific instructions or examples, and the only system-level tooling referenced is Windows-centric (PowerShell). The rest of the guide is platform-neutral JavaScript and web development, but the initial setup assumes a Windows environment.
Recommendations
- Provide Linux/macOS alternatives or clarify if the PowerShell steps can be performed using cross-platform PowerShell Core.
- Explicitly state whether the Teams Phone enablement step can be completed on non-Windows platforms, and link to any available CLI or web portal alternatives.
- Add a note in the prerequisites about cross-platform compatibility for all setup steps, especially those involving Teams user configuration.
- If possible, provide links or instructions for Linux users to perform equivalent administrative tasks (e.g., using Azure CLI, Microsoft 365 admin center, or PowerShell Core on Linux).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/includes/teams-call-queue/teams-call-queue-ios.md
...ling/includes/teams-call-queue/teams-call-queue-ios.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Microsoft/Windows-centric tools and workflows. It exclusively references Microsoft Teams Admin Center, Microsoft Graph Explorer, and Azure CLI, with no mention of Linux-specific tools or alternative cross-platform approaches. The instructions for administrative tasks (such as creating call queues and finding object IDs) are tied to web portals and tools that are primarily designed for or most commonly used in Windows environments. There are no Linux command-line or open-source alternatives provided for these steps, and the documentation assumes familiarity with the Microsoft ecosystem.
Recommendations
- Provide equivalent instructions for Linux users, such as using Microsoft Graph API via curl or other cross-platform REST clients instead of relying solely on Graph Explorer.
- Clarify that Teams Admin Center is a web-based tool accessible from any OS, and provide screenshots or notes for non-Windows browsers if relevant.
- Where Azure CLI is used, explicitly note that it is cross-platform and provide installation instructions for Linux/macOS.
- If any PowerShell or Windows-specific commands are required, always provide bash or shell equivalents.
- Highlight any steps that are OS-agnostic, and avoid implying that Windows is required unless it truly is.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/includes/video-calling/video-calling-unity.md
...-calling/includes/video-calling/video-calling-unity.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by emphasizing Windows-specific tools and workflows, such as requiring the Universal Windows Platform (UWP) workload for Unity, referencing the Windows tab in Unity Editor, and recommending the Microsoft Mixed Reality Feature Tool (which is Windows-only). There is no mention of Linux or macOS alternatives, nor guidance for non-Windows users, despite Unity and the Azure CLI being cross-platform. The documentation assumes a Windows development environment throughout.
Recommendations
- Clarify platform support for the Azure Communication Services Calling SDK for Unity, explicitly stating whether Linux and macOS are supported or not.
- If cross-platform is supported, provide installation and setup instructions for Linux and macOS, including any required dependencies or differences in workflow.
- When referencing tools (e.g., Mixed Reality Feature Tool), specify their platform compatibility and suggest alternatives or workarounds for Linux/macOS users.
- Avoid phrases like 'found under the Windows tab' without clarifying if this is present on other platforms, or provide equivalent navigation steps for Linux/macOS.
- Include screenshots or notes for non-Windows platforms where UI or workflow differs.
- If UWP is required and only available on Windows, state this limitation clearly at the start of the prerequisites section.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/includes/teams-call-queue/teams-call-queue-javascript.md
...cludes/teams-call-queue/teams-call-queue-javascript.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing the Teams Admin Center (a web tool, but often associated with Windows environments), providing resource creation links with Windows pivots, and omitting any Linux-specific instructions or troubleshooting. There are no explicit Linux or cross-platform setup notes, and the only environmental references (such as 'command window') use Windows terminology. No Linux shell or PowerShell commands are present, but the absence of Linux-specific guidance or parity is notable.
Recommendations
- Explicitly state that all command-line instructions (e.g., mkdir, npm install, npx webpack serve) are cross-platform and work on Linux, macOS, and Windows.
- Replace 'command window' with 'terminal' or 'command-line interface (CLI)' to use platform-neutral language.
- If any steps (such as Teams Admin Center access or resource creation) differ on Linux or macOS, provide alternative instructions or clarify that the process is web-based and OS-agnostic.
- In the prerequisites, avoid linking to resource creation docs with a Windows-specific pivot or tab; ensure parity for Linux users.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, package installation, browser compatibility).
- If screenshots are shown, consider including ones from non-Windows browsers or environments to reinforce cross-platform support.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/education-hub/faq.md
...cs/azure-docs/blob/main//articles/education-hub/faq.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively listing Microsoft and Windows-centric developer tools (e.g., Visual Studio, Hyper-V, Windows Server, SQL Server, Visio, etc.) and by referencing Windows 10/11 virtual machines as a specific benefit. There are no mentions of Linux-based tools, distributions, or examples, nor are there instructions or guidance for Linux users. The product lists and benefits focus on Windows technologies, and even when cross-platform tools like Visual Studio Code are mentioned, there is no explicit mention of Linux compatibility or usage.
Recommendations
- Include Linux-based developer tools or explicitly mention support for Linux distributions where applicable (e.g., Ubuntu, CentOS).
- Provide examples or guidance for deploying Linux virtual machines alongside Windows VMs.
- List open-source or cross-platform alternatives in the product lists, and clarify which tools are available for Linux.
- Add instructions or links for Linux users on how to access, install, or use the provided software.
- Ensure parity in documentation by referencing both Windows and Linux environments where relevant, especially in sections about software downloads, VM deployment, and developer tooling.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/speaker-issue.md
...ting/voice-video-calling/audio-issues/speaker-issue.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by specifically mentioning and illustrating Windows volume mixer settings as a troubleshooting step, without providing equivalent guidance or screenshots for Linux (or macOS) users. The only concrete example of system-level troubleshooting is for Windows, and there is no mention of how to check or adjust audio settings on Linux systems. This may leave Linux users without clear instructions for resolving similar issues.
Recommendations
- Add parallel instructions and screenshots for checking and adjusting audio output and application volume on common Linux desktop environments (e.g., GNOME, KDE).
- Mention Linux (and macOS) system settings alongside Windows when discussing system volume and app-specific volume controls.
- Use neutral language such as 'On Windows, check the volume mixer; on Linux, check the system sound settings...' to ensure all platforms are addressed equally.
- Include references or links to official documentation for audio troubleshooting on Linux and macOS.
- If possible, provide a table or section summarizing how to check audio output settings on Windows, Linux, and macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/resources/troubleshooting/voice-video-calling/references/how-to-collect-diagnostic-audio-recordings.md
...ferences/how-to-collect-diagnostic-audio-recordings.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing build instructions and prerequisites only for Windows (e.g., Visual Studio 2022, Windows-specific Chromium build instructions, and .exe file references). There are no equivalent instructions or tool recommendations for Linux or macOS users, and the only example commands and file paths are Windows-centric.
Recommendations
- Add equivalent build instructions for Linux (and optionally macOS), including required packages (e.g., gcc, clang, make) and platform-specific steps.
- Reference the official Chromium/Linux build instructions and depot_tools setup for Linux.
- Clarify that the unpack_aecdump utility can be built and run on Linux, and provide example commands and expected output file names (e.g., unpack_aecdump instead of unpack_aecdump.exe).
- List Linux prerequisites (e.g., Python 3, build-essential, depot_tools) alongside Windows prerequisites.
- Where file paths or executable names differ by platform, provide both (e.g., unpack_aecdump.exe for Windows, unpack_aecdump for Linux/macOS).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/resources/troubleshooting/voice-video-calling/references/how-to-collect-browser-verbose-log.md
...lling/references/how-to-collect-browser-verbose-log.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides instructions and command-line examples for collecting verbose logs on Windows, referencing Windows file paths, executables, and tools (e.g., cmd.exe, C:\ paths). There are no examples or instructions for Linux or macOS users, and only Windows-specific browser executable locations are mentioned.
Recommendations
- Add equivalent instructions and command-line examples for Linux (and optionally macOS), including typical executable paths (e.g., /usr/bin/google-chrome or /usr/bin/microsoft-edge) and file locations.
- Mention how to open a terminal and run the browser with the required flags on Linux/macOS.
- Specify the default log file locations for non-Windows platforms.
- Ensure that references to browser internals pages (e.g., chrome://webrtc-internals) are platform-agnostic.
- Consider providing a table or section that covers all major platforms side-by-side for parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/tutorial-dns-private-resolver-failover.md
...articles/dns/tutorial-dns-private-resolver-failover.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a significant Windows bias. All DNS server configuration examples are provided exclusively for Windows Server using PowerShell and the Windows DNS console. There are no equivalent instructions or examples for configuring DNS forwarding on Linux-based DNS servers (such as BIND or dnsmasq), nor are Linux command-line examples provided. The only command-line example for DNS queries (nslookup) is cross-platform, but the context and screenshots are Windows-centric. The documentation assumes the administrator is using Windows tools and environments, and does not mention or guide Linux users.
Recommendations
- Add equivalent instructions for configuring conditional forwarders on popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound), including example configuration snippets.
- Provide Linux command-line examples for DNS queries (e.g., using dig or host in addition to nslookup).
- Explicitly mention that the procedure applies to both Windows and Linux DNS servers, and provide links or references to relevant Linux documentation.
- Where possible, present Windows and Linux procedures in parallel or in separate clearly-labeled sections to ensure parity.
- Include screenshots or terminal output from Linux environments where appropriate.