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 1801-1825 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/includes/manage-teams-identity-net.md
...ices/quickstarts/includes/manage-teams-identity-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references Windows-specific consoles (cmd, PowerShell) before Bash, and does not provide any Linux/macOS-specific instructions or examples for environment variable setup, editor usage, or running the application. All instructions are generic but implicitly assume familiarity with Windows environments.
Recommendations
- When listing consoles, mention Bash (Linux/macOS) first or equally with cmd/PowerShell.
- Provide explicit examples for setting environment variables on Linux/macOS (e.g., export AAD_CLIENT_ID=...).
- Include notes or examples for opening and editing files using common Linux/macOS editors (e.g., nano, vim, code).
- Clarify that the .NET SDK and all commands work cross-platform, and provide any OS-specific caveats if necessary.
- Add a section or callout for running the application on Linux/macOS, including any differences in output or troubleshooting tips.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-dns-fallback.md
...e-docs/blob/main//articles/dns/private-dns-fallback.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias primarily by using Windows command prompt syntax (C:\>) in all DNS resolution examples and referencing Windows tools (nslookup, dig) from a Windows shell. There are no explicit Linux shell examples, and the instructions for running DNS queries assume a Windows environment, even though the tools used (dig, nslookup) are available on Linux as well.
Recommendations
- Provide parallel Linux shell examples (e.g., using $ prompt and Linux command syntax) alongside Windows examples for DNS queries.
- Explicitly mention that tools like dig and nslookup are available on both Windows and Linux, and show example commands for both platforms.
- When instructing users to open a command prompt, clarify that this can be either Windows Command Prompt, PowerShell, or a Linux terminal.
- Include screenshots or output samples from both Windows and Linux environments where relevant.
- Avoid using only Windows-style paths and prompts (C:\>) in code blocks; use a neutral or dual-platform approach.
Azure Docs
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 Windows-specific Azure CLI installation instructions and not mentioning or linking to Linux or macOS installation guides. All CLI examples are generic and cross-platform, but the installation step assumes a Windows environment, which may confuse or exclude Linux users.
Recommendations
- Provide links to Azure CLI installation instructions for all major platforms (Windows, Linux, macOS), or use a platform-neutral link.
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS terminals.
- Avoid using Windows-specific tabs or links as the default or only option in prerequisites.
- Consider adding a short section or note for Linux/macOS users to clarify parity and any minor differences (if any).
Azure Docs
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 not mentioning or linking to Linux or macOS equivalents. All command-line examples use the Azure CLI, which is cross-platform, but the lack of explicit Linux/macOS installation guidance may hinder non-Windows users.
Recommendations
- Provide installation instructions or links for Azure CLI on Linux and macOS alongside the Windows link.
- Explicitly state that all Azure CLI commands work on Windows, Linux, and macOS.
- Consider adding a 'Platform' note or table to clarify cross-platform compatibility.
- If referencing Cloud Shell, mention that it is accessible from any OS via browser.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/sms/includes/receive-sms-no-code.md
...rvices/quickstarts/sms/includes/receive-sms-no-code.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively describes workflows using Logic Apps and Power Automate, both of which are Microsoft-centric tools with a strong association to Windows environments. There are no examples or mentions of Linux-native tools, CLI-based workflows, or cross-platform alternatives for handling Azure Communication Services events. All screenshots and step-by-step instructions are tailored to the Power Automate/Logic Apps GUI, with no parity for Linux users who may prefer scripting or open-source automation tools.
Recommendations
- Include alternative examples using cross-platform tools such as Azure CLI, Azure Functions, or scripting languages (e.g., Python) to handle Event Grid events and respond to SMS messages.
- Provide sample code or workflows for Linux environments, such as using Bash scripts, curl, or open-source automation/orchestration tools (e.g., Apache Airflow, Node-RED).
- Mention and link to documentation for Azure Event Grid integration with non-Microsoft automation platforms.
- Clarify that Logic Apps and Power Automate are not the only options, and suggest equivalent approaches for users on Linux or those preferring code-first solutions.
Azure Docs
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 samples and instructions, which are cross-platform in theory, but all environment variable instructions and workflow descriptions implicitly assume a Windows-centric approach. There are no explicit Linux/macOS shell examples for setting environment variables, and the Azure portal navigation instructions do not mention platform differences. There is no mention of Linux-specific tooling or command-line usage, and no parity in example commands for Linux users.
Recommendations
- Add explicit shell (bash/zsh) examples for setting environment variables on Linux/macOS, alongside any Windows/PowerShell equivalents.
- Clarify that .NET Core SDK and the Azure SDK are cross-platform, and provide links or notes for Linux/macOS installation instructions.
- When instructing users to set environment variables, provide both Windows (setx, PowerShell) and Linux/macOS (export, .bashrc) command examples.
- If referencing Azure CLI or other tools, ensure Linux usage is demonstrated or at least mentioned.
- Explicitly state that all code samples are cross-platform and can be run on Linux, macOS, or Windows, and note any OS-specific caveats if present.
Azure Docs
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by recommending the Microsoft Installer (MSI) for Node.js installation, which is specific to Windows, and does not mention Linux installation methods or provide Linux-specific guidance. All command-line examples are generic and cross-platform, but the only installation method referenced is Windows-centric. There are no explicit Linux or macOS instructions or troubleshooting notes.
Recommendations
- Provide Linux and macOS installation instructions for Node.js alongside the Windows MSI recommendation, such as using package managers like apt, yum, or Homebrew.
- Explicitly state that the command-line instructions work on Linux, macOS, and Windows, and note any OS-specific differences if applicable.
- Add a note or section for Linux/macOS users on installing dependencies and running the sample, including any permissions or environment considerations.
- Avoid referencing Windows-specific installers or tools without offering equivalent options for other platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/tpe/teams-phone-extensibility-access-teams-phone.md
...ts/tpe/teams-phone-extensibility-access-teams-phone.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by describing user enablement for Teams exclusively via the Microsoft 365 admin center web UI (a workflow most familiar to Windows/Office admins) and referencing the MicrosoftTeams PowerShell cmdlet (Get-CsOnlineApplicationInstance) as the only concrete method for retrieving the Resource Account ObjectId. There are no Linux-specific instructions or CLI alternatives, and the documentation does not mention cross-platform tools such as Azure CLI or REST-based alternatives for these steps.
Recommendations
- Provide equivalent Linux-friendly instructions for enabling a user for Teams, such as using Azure CLI, Microsoft Graph API, or cross-platform PowerShell Core.
- When referencing PowerShell cmdlets (e.g., Get-CsOnlineApplicationInstance), also describe how to retrieve the same information using REST APIs or CLI tools available on Linux/macOS.
- Explicitly mention that REST API calls can be made from any platform and provide example commands using curl or HTTPie.
- Review all prerequisite and setup steps to ensure that no step assumes a Windows-only environment or toolset.
- Where possible, add notes or examples for Linux/macOS users to ensure parity and inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/sms/includes/send-sms-net.md
...tion-services/quickstarts/sms/includes/send-sms-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-specific terminals (cmd, PowerShell) before Bash when describing how to run commands. However, the actual commands shown (dotnet CLI) are cross-platform and no Windows-only tools or patterns are used. There are no Linux-specific instructions or examples, but Linux is implicitly supported.
Recommendations
- List Bash (or 'terminal') before cmd/PowerShell, or mention all platforms equally (e.g., 'In a terminal, such as Bash, cmd, or PowerShell...').
- Explicitly state that all commands work on Windows, Linux, and macOS.
- Provide example screenshots or terminal prompts for both Windows and Linux/macOS environments.
- Mention any OS-specific considerations, if applicable (e.g., environment variable setting syntax).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/tutorial-alias-pip.md
...ure-docs/blob/main//articles/dns/tutorial-alias-pip.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The tutorial exclusively demonstrates the creation and configuration of a Windows Server virtual machine, including detailed steps for installing IIS via the Windows GUI and using RDP. There are no examples or instructions for deploying or configuring a Linux-based web server, nor are there any references to Linux tools or command-line methods. All server-side steps assume a Windows environment, which may alienate users who prefer or require Linux-based solutions.
Recommendations
- Add parallel instructions for creating a Linux virtual machine (e.g., Ubuntu) in Azure, including steps for installing a web server such as Apache or Nginx.
- Provide both Windows and Linux examples for connecting to the VM (e.g., RDP for Windows, SSH for Linux).
- Include screenshots or command-line snippets relevant to Linux environments.
- Explicitly mention that the tutorial can be followed with either Windows or Linux VMs, and provide links to relevant Azure documentation for both.
- Consider restructuring the tutorial so that OS selection is an early step, with subsequent instructions branching for Windows and Linux users.
Azure Docs
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. The Azure CLI installation link points only to Windows instructions, omitting direct links or guidance for Linux or macOS. In the environment variable section, Windows instructions are presented first, followed by macOS and Linux, which may reinforce a Windows-centric perspective. There are no PowerShell-specific examples, but Linux users may find the installation and environment setup less accessible due to missing or less prominent Linux guidance.
Recommendations
- Provide installation links for Azure CLI for all major platforms (Windows, Linux, macOS) in the prerequisites section, or use a platform-neutral link.
- Rotate or randomize the order of OS-specific tabs (Windows, macOS, Linux) or default to the user's detected OS if possible.
- Ensure Linux and macOS instructions are as detailed and prominent as Windows instructions.
- Consider including a brief note that all CLI commands work cross-platform, and highlight any OS-specific differences if they exist.
Azure Docs
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
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides instructions and a screenshot for finding the Azure Resource ID, but does not include any command-line examples or platform-specific guidance. There are no CLI examples (such as Azure CLI or PowerShell), but the screenshot approach is more familiar to Windows users. There is no mention of Linux or cross-platform command-line methods, which may disadvantage Linux users.
Recommendations
- Add Azure CLI examples for retrieving the Resource ID, which work on all platforms (Windows, Linux, macOS).
- If providing PowerShell examples, ensure equivalent Bash/Azure CLI commands are included and presented first or equally.
- Explicitly mention that the Azure Portal is web-based and accessible from any OS, but supplement with CLI instructions for automation and parity.
- Include screenshots or instructions for both GUI and command-line methods.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/tutorial-alias-tm.md
...zure-docs/blob/main//articles/dns/tutorial-alias-tm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The tutorial exclusively uses Windows Server virtual machines for the web server setup, including detailed steps for installing IIS via the Windows GUI and RDP. There are no examples or instructions for deploying Linux-based VMs or using common Linux web servers (e.g., Apache, Nginx). All hands-on server configuration is Windows-centric, and no Linux parity is provided.
Recommendations
- Provide parallel instructions for creating Linux virtual machines (e.g., Ubuntu) and installing a web server such as Apache or Nginx.
- Include CLI-based examples for Linux (e.g., using SSH, apt, systemctl) alongside the Windows RDP/IIS steps.
- Show how to edit the default web page on a Linux server (e.g., editing /var/www/html/index.html) as an alternative to the IIS example.
- When presenting steps for creating VMs, offer both Windows and Linux options, or explicitly state that either OS can be used.
- Add a note or section explaining how to adapt the tutorial for Linux users, ensuring cross-platform applicability.
Azure Docs
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
Windows Tools
Summary
The documentation page shows mild Windows bias by referencing Windows-specific content and tools before or instead of Linux equivalents. The 'Clean up resources' section links to a resource clean-up guide with a Windows tab in the URL, and there is no mention of Linux or cross-platform CLI options for resource management. Platform pivots are present for web, iOS, Android, and Windows, but Linux is not represented as a first-class platform.
Recommendations
- Include Linux as a platform pivot if supported, or clarify platform support explicitly.
- In the 'Clean up resources' section, provide examples using cross-platform tools such as Azure CLI or Azure Portal, not just Windows-specific instructions.
- Ensure that links and tabs do not default to Windows unless it is the only supported platform; otherwise, provide parity for Linux/macOS users.
- Audit included content (e.g., closed-captions-windows.md) to ensure Linux users are not excluded from relevant instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/get-started-with-video-calling.md
.../voice-video-calling/get-started-with-video-calling.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides platform-specific quickstart sections for web, Android, iOS, Windows, and Unity, but does not mention or provide examples for Linux. Additionally, the 'clean up resources' section links to instructions specifically for Windows, with no mention of Linux or cross-platform alternatives.
Recommendations
- Add a Linux-specific quickstart section or clarify if the web or another platform guide is suitable for Linux users.
- In the 'clean up resources' section, provide instructions or links for Linux users (e.g., using Azure CLI on Linux, Bash commands, or cross-platform tools).
- Ensure that all platform pivots include Linux where applicable, or explicitly state platform limitations.
- Avoid linking only to Windows-specific tabs or instructions; provide parity for Linux and other operating systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/includes/closed-captions/closed-captions-ios.md
...alling/includes/closed-captions/closed-captions-ios.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias in the prerequisites and resource management sections. Links and instructions for creating and cleaning up Azure Communication Services resources reference Windows-specific tabs or pivots first (e.g., '?tabs=windows'), and there are no explicit Linux or cross-platform instructions or examples provided. However, the main code samples are iOS/Swift-specific and do not show Windows-specific code or tools.
Recommendations
- Update prerequisite and resource management links to include Linux or cross-platform tabs/pivots, or provide neutral links that do not default to Windows.
- Explicitly mention Linux/macOS options where relevant, especially in resource creation and cleanup steps.
- If platform-specific instructions are necessary, provide parity by including Linux/macOS equivalents alongside Windows instructions.
- Audit other referenced quickstarts and ensure they do not default to Windows-only instructions or examples.
Azure Docs
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 demonstrates a subtle Windows bias by linking to resource creation and cleanup guides that use Windows as the default or only example (e.g., URLs with '?tabs=windows' and references to 'platform-azp'). There are no explicit Linux or cross-platform instructions or examples provided, and the documentation does not clarify whether the steps are platform-agnostic or if Linux/macOS users should follow different instructions.
Recommendations
- Provide equivalent Linux/macOS instructions or clarify that the steps are platform-agnostic where appropriate.
- Update links to resource creation and cleanup guides to either default to a neutral tab or explicitly mention and link to Linux/macOS instructions.
- Add a note in the prerequisites and cleanup sections indicating support for Linux/macOS, or provide links to relevant documentation for those platforms.
- Review all quickstart and reference links to ensure they do not default to Windows-only tabs or pivots, and offer parity for Linux users.
Azure Docs
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 mild Windows bias by recommending the MSI installer for Node.js in the prerequisites, which is a Windows-specific installation method, and does not mention Linux installation methods or provide parity in setup instructions. No explicit Linux commands or package manager instructions are given, and the only installation method referenced is Windows-centric.
Recommendations
- In the prerequisites, provide Linux installation instructions for Node.js, such as using apt, yum, or nvm, alongside the MSI installer for Windows.
- Explicitly state that the instructions are cross-platform and that all commands (npm, npx, etc.) work on Linux, macOS, and Windows.
- Wherever a Windows-specific tool or installer is mentioned (like MSI), add the equivalent for Linux and macOS, or link to the official Node.js installation guide covering all platforms.
- Add a note or section confirming that the sample app and setup steps are valid for Linux and macOS users, and provide troubleshooting tips for common cross-platform issues.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/includes/teams-user/teams-user-android.md
...ideo-calling/includes/teams-user/teams-user-android.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references enabling Teams Phone features via PowerShell, which is a Windows-centric tool, and does not provide Linux alternatives or mention cross-platform options for managing Teams users. No explicit Linux or cross-platform management instructions are given.
Recommendations
- Provide equivalent instructions for enabling Teams Phone features using cross-platform tools (e.g., Azure Cloud Shell, Teams Admin Center web UI) or clarify if PowerShell Core on Linux/macOS is supported.
- Mention and link to any available Linux-compatible Teams administration tools.
- Explicitly state whether the PowerShell steps can be performed on non-Windows platforms, and if not, suggest alternatives.
- Ensure that all prerequisite steps (such as licensing and enabling users) are accessible to Linux users, or provide guidance on how to achieve parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/includes/teams-user/teams-user-ios.md
...ce-video-calling/includes/teams-user/teams-user-ios.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references enabling Teams Phone features via PowerShell, which is a Windows-centric tool, and links to instructions that are primarily Windows-focused. There is no mention of Linux or cross-platform alternatives for managing Teams user settings, and the PowerShell approach is presented as the default method.
Recommendations
- Provide alternative instructions for enabling Teams Phone features using cross-platform tools, such as the Microsoft Teams admin center web UI, where possible.
- Explicitly mention whether PowerShell steps can be performed on PowerShell Core on macOS/Linux, or provide guidance for non-Windows users.
- Add clarifying notes or links for Linux/macOS users to ensure parity in setup steps.
- Where administrative tasks are required, list web-based or cross-platform options before or alongside Windows/PowerShell-specific instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/tutorial-alias-rr.md
...zure-docs/blob/main//articles/dns/tutorial-alias-rr.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only Windows-centric instructions and examples. The testing section references 'command prompt' and uses 'nslookup' without clarifying cross-platform usage or offering Linux/macOS alternatives. No Linux shell or tool examples (such as dig or Linux terminal instructions) are provided, and the workflow assumes a Windows environment.
Recommendations
- Include Linux/macOS equivalents for command-line instructions, such as using 'dig' or 'host' in addition to 'nslookup'.
- Clarify that 'nslookup' is available on multiple platforms, and provide sample commands for both Windows Command Prompt and Linux/macOS terminals.
- Avoid referring to 'command prompt' generically; specify 'Windows Command Prompt' and add instructions for 'Linux terminal' or 'macOS Terminal'.
- Where screenshots or UI steps are platform-agnostic (web portal), clarify that the steps are the same across operating systems.
- Explicitly mention that the DNS tools used are available on all major platforms, or provide installation instructions if not present by default.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/includes/raw-media/raw-media-access-android.md
...calling/includes/raw-media/raw-media-access-android.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally Android/Java-focused, but there is a notable Windows bias in the 'ScreenShare Video' section, where it explicitly references 'Windows APIs' for frame capture and states 'Because the Windows system generates the frames...'. No equivalent mention or guidance is provided for Linux or macOS systems, nor is there a general cross-platform approach described for screen capture. This implicitly prioritizes Windows and may exclude or confuse Linux developers.
Recommendations
- Provide platform-agnostic guidance for screen capture, or explicitly mention how to implement screen sharing on Linux (and macOS) alongside Windows.
- If Windows-specific APIs are referenced, also include equivalent Linux (e.g., X11, PipeWire, GStreamer) and macOS (e.g., AVFoundation) approaches or at least acknowledge their existence.
- Clarify whether the SDK supports screen sharing on non-Windows platforms, and if not, state this limitation clearly.
- Avoid language that assumes Windows as the default system (e.g., 'Because the Windows system generates the frames...') in cross-platform documentation.
- Add sample code or external references for Linux/macOS screen capture if possible, or link to community resources.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/mqtt-publish-and-subscribe-portal.md
...ticles/event-grid/mqtt-publish-and-subscribe-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows a Windows-first bias in the certificate generation section, where instructions specifically mention opening a command prompt in the Windows user profile folder and reference Windows-specific actions (e.g., 'Win+R type %USERPROFILE%'). No equivalent Linux or macOS instructions or examples are provided for certificate generation or file path conventions. The rest of the guide is platform-neutral, especially when using MQTTX, which is cross-platform.
Recommendations
- Provide parallel instructions for Linux and macOS users in the certificate generation section, including terminal commands and typical file paths (e.g., '~/').
- Avoid Windows-specific shortcuts or, if mentioned, also provide equivalents for other operating systems (e.g., explain how to open a terminal in Linux/macOS).
- Clarify that the step CLI and MQTTX are cross-platform, and provide installation links or commands for Linux and macOS.
- Where file paths are referenced, show both Windows and Unix-style examples.
- Consider including a note or table summarizing OS-specific steps for all platforms supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/samples/chat-hero-sample.md
...les/communication-services/samples/chat-hero-sample.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by listing Windows-specific terminals (PowerShell, Windows Terminal, Command Prompt) first and explicitly, while only mentioning 'or equivalent' for non-Windows environments. There are no explicit Linux/macOS terminal or tool references, and no Linux/macOS-specific instructions or examples are provided. However, the actual commands (git, npm, az CLI) are cross-platform.
Recommendations
- Explicitly mention Linux and macOS terminals (e.g., 'Terminal on macOS or Linux') alongside Windows terminals.
- Provide example commands or screenshots from Linux/macOS environments where appropriate.
- Clarify that all CLI commands work cross-platform and provide any OS-specific notes if needed (e.g., path separators, file editing instructions).
- Avoid using Windows-specific terminology like 'PowerShell' or 'Command Prompt' exclusively; use more inclusive phrasing such as 'Open a terminal (e.g., PowerShell, Command Prompt, Terminal on macOS/Linux)'.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/samples/includes/csharp-auth-hero.md
...nication-services/samples/includes/csharp-auth-hero.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page primarily references a C# sample and links to deployment guides and architecture documents that are likely Windows-centric, given the use of C# and the absence of any mention of Linux or cross-platform tooling. There are no explicit Linux examples, nor are there references to Linux-specific tools or instructions, which may make it less approachable for Linux users.
Recommendations
- Add explicit instructions or examples for deploying and running the sample on Linux environments.
- Include references to cross-platform tools and frameworks (e.g., .NET Core/5/6+ which are cross-platform) and clarify compatibility.
- Provide shell (bash) command examples alongside any PowerShell or Windows command examples.
- Mention any Linux prerequisites or differences in setup, if applicable.
- Ensure that linked guides and samples include Linux deployment steps or troubleshooting tips.