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 1-25 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/api-management/developer-portal-alternative-processes-self-host.md
...nt/developer-portal-alternative-processes-self-host.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows/Azure-centric tooling and workflows. It exclusively references Azure CLI, Azure Functions Core Tools, and Azure CDN, with no mention of Linux-specific commands, alternative non-Microsoft tools, or cross-platform deployment patterns. All examples and instructions assume the use of Azure and its ecosystem, which is more familiar to Windows users, and there are no explicit Linux or open-source alternatives provided.
Recommendations
- Include explicit Linux shell command examples where appropriate, such as using bash or zsh.
- Mention and provide examples for deploying to non-Azure static hosts (e.g., AWS S3, Google Cloud Storage, Netlify, or generic Nginx/Apache servers).
- Reference open-source or cross-platform alternatives to Azure Functions, such as AWS Lambda, Google Cloud Functions, or self-hosted serverless frameworks.
- Provide parity in tooling instructions, such as using generic npm scripts and curl commands, and clarify that Azure CLI and Azure Functions Core Tools are cross-platform.
- List Azure and non-Azure CDN options equally, or at least mention that other CDN providers (Cloudflare, Fastly, etc.) are supported.
- Add a section or notes clarifying that all steps can be performed on Linux, macOS, and Windows, and highlight any OS-specific considerations.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/configure-language-dotnet-framework.md
...les/app-service/configure-language-dotnet-framework.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by focusing exclusively on Windows-based deployment and configuration patterns for ASP.NET apps in Azure App Service. All examples and instructions assume a Windows environment (e.g., Kudu CMD/PowerShell, Windows file paths, Visual Studio tooling), with no equivalent Linux-based guidance or examples. Linux scenarios are only mentioned in passing, without actionable steps or parity in documentation.
Recommendations
- Add equivalent Linux-based instructions and examples for each configuration task, especially for scenarios where ASP.NET apps are hosted on Linux App Service plans or custom Linux containers.
- Provide Linux shell (bash) commands and file paths alongside Windows CMD/PowerShell examples, particularly for tasks like inspecting installed runtimes or accessing diagnostic logs.
- Include guidance for deploying and configuring ASP.NET apps using cross-platform tools (e.g., dotnet CLI, VS Code) in addition to Visual Studio.
- Clarify which instructions apply only to Windows App Service plans and provide clear, parallel sections for Linux where applicable.
- Reference Linux-specific troubleshooting and diagnostic tools (e.g., Kudu Bash, Linux logs location) where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-conditional-access-dev-tunnels-service.md
...v-box/how-to-conditional-access-dev-tunnels-service.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong Windows bias by exclusively using PowerShell (specifically Microsoft.Graph PowerShell) for all command-line instructions, referencing Windows-specific tools and installation steps, and omitting any Linux or cross-platform alternatives. There are no examples or guidance for performing these tasks on Linux or macOS, and the workflow assumes a Windows environment throughout.
Recommendations
- Provide equivalent instructions using cross-platform tools such as Azure CLI, Microsoft Graph CLI, or REST API calls, which can be run on Linux, macOS, and Windows.
- Explicitly mention platform compatibility for each step, and offer alternative commands for Linux/macOS users where possible.
- Include installation and usage instructions for required tools (e.g., Microsoft Graph CLI, Azure CLI) on Linux and macOS.
- Add notes or callouts highlighting any steps that are Windows-specific, and suggest workarounds or alternatives for non-Windows environments.
- Consider reordering or parallelizing instructions so that Linux/macOS alternatives are presented alongside Windows/PowerShell examples, rather than only after or not at all.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/troubleshooting/find-error-code.md
...re-resource-manager/troubleshooting/find-error-code.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently presents Windows/PowerShell examples and tools before their cross-platform or Linux equivalents. PowerShell is given a prominent, detailed section before Azure CLI, and Visual Studio Code (a Microsoft product) is the only code editor mentioned for syntax validation. There are no Linux-specific examples, shell commands, or references to Linux-native editors or troubleshooting tools. The structure and tool recommendations implicitly prioritize Windows and Microsoft-centric workflows.
Recommendations
- Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI examples first in some sections to avoid implicit prioritization of Windows/PowerShell.
- Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide example shell commands using Bash syntax where appropriate.
- Include references to popular Linux-native editors (e.g., Vim, Emacs, nano) and how to use them for ARM/Bicep syntax validation, or at least acknowledge their use.
- Clarify that Visual Studio Code is available cross-platform, and suggest alternative editors for Linux users.
- Add troubleshooting tips or examples that are specific to Linux environments, such as file path conventions or common shell errors.
- Ensure that all screenshots and output examples are either neutral or include Linux terminal examples where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/interop/enable-interoperability-teams.md
...ices/concepts/interop/enable-interoperability-teams.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing the PowerShell cmdlet (Set-CsPhoneNumberAssignment) for enabling Enterprise Voice, without providing equivalent instructions or examples for Linux or cross-platform environments. The documentation assumes the use of Windows tooling and does not mention alternative methods or scripts that could be used on Linux or macOS.
Recommendations
- Provide equivalent CLI or REST API instructions for enabling Enterprise Voice, suitable for Linux and macOS users.
- Include examples using cross-platform tools such as Azure CLI or Microsoft Graph API where possible.
- Explicitly mention platform requirements for PowerShell cmdlets and offer guidance for non-Windows users (e.g., using PowerShell Core on Linux/macOS, or alternative approaches).
- Ensure that Linux/macOS instructions are presented alongside Windows instructions, not as an afterthought.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/send-email-advanced/includes/attachments-net.md
.../email/send-email-advanced/includes/attachments-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by using a Windows-style file path (C:\Users\Documents\attachment.pdf) in the code example, omitting any Linux or cross-platform file path alternatives. There is no mention of Linux or macOS environments, nor are there instructions or examples for running the sample on non-Windows systems. The sample code and instructions implicitly assume a Windows environment.
Recommendations
- Provide file path examples for both Windows (C:\Users\Documents\attachment.pdf) and Linux/macOS (/home/user/Documents/attachment.pdf) to illustrate cross-platform usage.
- Explicitly mention that the .NET SDK and sample code are cross-platform and can be run on Windows, Linux, and macOS.
- Add a note or section on running the sample on Linux/macOS, including any environment-specific considerations.
- Use environment-agnostic methods for file paths in code samples, such as Path.Combine or Path.DirectorySeparatorChar.
- Include screenshots or terminal output examples from Linux/macOS where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/schema-registry-concepts.md
.../main//articles/event-hubs/schema-registry-concepts.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it is generally cross-platform in its SDK and language coverage, it specifically highlights PowerShell (a Windows-centric tool) as a method for managing schemas, and provides a PowerShell example link alongside Azure CLI. There is no mention of Linux-native tools or shell scripting alternatives, and PowerShell is listed after Azure CLI, but before any mention of Bash or Linux shell equivalents. No explicit Linux or Bash examples are provided for schema management.
Recommendations
- Add explicit Bash or Linux shell examples for schema management tasks, such as using Azure CLI from a Bash shell.
- Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Consider providing sample scripts or walkthroughs for Linux environments (e.g., using Bash, zsh, or other common Linux shells).
- If PowerShell is mentioned, also mention PowerShell Core (cross-platform) and clarify its availability on Linux.
- Ensure parity in documentation by including Linux-native tooling or scripting options wherever Windows/PowerShell is referenced.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-about-virtual-network-gateways.md
...ssroute/expressroute-about-virtual-network-gateways.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for gateway subnet creation, referencing PowerShell and REST API resources exclusively, and omitting equivalent Azure CLI (cross-platform) or ARM template examples. The technical resources section lists only PowerShell cmdlets and REST APIs, with no mention of Azure CLI commands, which are widely used on Linux and macOS. This focus on PowerShell and lack of Linux-native tooling or examples may hinder accessibility for non-Windows users.
Recommendations
- Add Azure CLI examples alongside PowerShell for all configuration steps, especially for gateway subnet creation.
- Include references to Azure CLI documentation and command syntax in the technical resources section.
- Where PowerShell is mentioned, provide equivalent Azure CLI commands and note their cross-platform compatibility.
- Consider adding ARM template or Bicep examples for infrastructure-as-code parity.
- Review all code snippets and ensure that both Windows (PowerShell) and cross-platform (CLI) users are equally supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-virtual-machine-overview.md
...nline/azure-stack-edge-gpu-virtual-machine-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is emphasized as a primary management and deployment interface, with multiple references to PowerShell scripts and cmdlets for VM operations. Windows-specific tools and extensions (such as password reset via PowerShell) are highlighted, and Windows image preparation is mentioned before Linux. While Linux is referenced, there are fewer explicit Linux-focused examples or instructions, and Linux parity in examples and tooling is lacking.
Recommendations
- Provide equivalent Linux CLI/bash examples alongside PowerShell for all VM management and deployment tasks.
- Ensure that Linux image preparation and deployment guides are as detailed and as prominently linked as Windows guides.
- Include Linux-specific extensions or management tools where relevant, and document their usage.
- Avoid presenting Windows tools or workflows (e.g., PowerShell) as the default or only option; present cross-platform alternatives (e.g., Azure CLI, REST API) first or equally.
- Add explicit Linux management scenarios and troubleshooting steps, not just generic or Windows-focused ones.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-set-azure-resource-manager-password.md
...ure-stack-edge-gpu-set-azure-resource-manager-password.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Azure PowerShell for command-line instructions, with all CLI examples and scripts using PowerShell cmdlets and syntax. There are no examples or instructions for performing the same tasks using Bash, Azure CLI, or Linux-native tools. The only non-PowerShell method described is via the Azure Portal, which is platform-agnostic, but all scripting and automation guidance is Windows/PowerShell-centric.
Recommendations
- Add equivalent instructions and examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
- Provide Bash shell script examples for Linux users, especially for steps involving secure string handling and API calls.
- Explicitly mention that the Azure Cloud Shell supports both Bash and PowerShell, and show how to perform the task in both environments.
- Where PowerShell modules are referenced, note their availability and usage on Linux/macOS or provide alternatives.
- Ensure that screenshots and sample outputs are not exclusively from Windows environments, or supplement with Linux terminal examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-mini-r-deploy-checklist.md
...box-online/azure-stack-edge-mini-r-deploy-checklist.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing Windows-specific tools and update mechanisms (e.g., WSUS, Windows Update server) without mentioning Linux equivalents or alternatives. There are no explicit Linux or cross-platform examples for device management, network readiness, or update configuration. Additionally, the documentation refers to Windows tools and patterns first or exclusively, with no mention of Linux-based workflows.
Recommendations
- Include instructions or references for Linux users, such as how to configure static IPs, DNS, and NTP servers using Linux tools (e.g., nmcli, netplan, systemd-timesyncd).
- Mention Linux-compatible update mechanisms or clarify if the device is Windows-only, and if not, provide guidance for Linux environments.
- When referencing tools like WSUS or Windows Update, add notes about alternatives for non-Windows environments, or state if these are not applicable.
- Provide cross-platform examples for network readiness checks, such as using curl, ping, or traceroute from Linux/macOS.
- Ensure that any device management steps that can be performed from Linux or macOS are documented alongside Windows instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-troubleshoot-virtual-machine-gpu-extension-installation.md
...roubleshoot-virtual-machine-gpu-extension-installation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation shows moderate Windows bias: PowerShell is used as the default code block language even for Linux commands, Windows-specific troubleshooting steps are often more detailed or appear first, and Windows tools/paths are referenced explicitly. Linux guidance is present but sometimes less detailed or lacks parity in example depth and clarity.
Recommendations
- Use the appropriate code block language for each OS (e.g., 'bash' for Linux shell commands, not 'powershell').
- Ensure Linux and Windows troubleshooting steps are equally detailed and presented in parallel where possible.
- When referencing log file locations or tools, provide both Linux and Windows equivalents together, or alternate which OS is mentioned first.
- Add explicit Linux command examples where only Windows/PowerShell commands are shown, and vice versa.
- Avoid using Windows-centric terminology (e.g., 'deploy the template') without clarifying Linux alternatives or providing cross-platform instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-mini-r-deploy-configure-network-compute-web-proxy.md
...edge-mini-r-deploy-configure-network-compute-web-proxy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the section about changing Kubernetes pod and service subnets, where only a PowerShell cmdlet (`Set-HcsKubeClusterNetworkInfo`) is mentioned for configuration. There are no Linux or cross-platform CLI alternatives provided, and the documentation assumes access to a PowerShell interface on the device. No Linux-specific tools, commands, or examples are given for network configuration or management.
Recommendations
- Provide equivalent Linux/bash command-line instructions or clarify if the device's management interface is only accessible via PowerShell.
- If the device supports SSH or Linux shell access, include examples using standard Linux networking tools (e.g., `nmcli`, `ip`, `ifconfig`, or configuration file edits).
- Explicitly state platform requirements and limitations (e.g., 'PowerShell is required for this operation; Linux is not supported'), if applicable.
- Where possible, offer cross-platform alternatives (e.g., REST API calls, Azure CLI commands) for configuration tasks.
- Add a note or section addressing Linux/macOS users, guiding them on how to perform equivalent tasks or clarifying any platform restrictions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-mini-r-deploy-configure-certificates-vpn-encryption.md
...ge-mini-r-deploy-configure-certificates-vpn-encryption.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exhibits a Windows bias by referencing BitLocker (a Windows-only encryption tool), instructing VPN configuration via PowerShell (Windows-centric), and omitting any Linux-specific tools, commands, or examples. There are no instructions or parity for Linux users, such as using OpenSSL for certificates or Linux-native encryption solutions. The only scripting example referenced is PowerShell, and BitLocker is assumed as the encryption-at-rest solution, with no mention of alternatives for non-Windows environments.
Recommendations
- Provide Linux-specific instructions for certificate management, such as using OpenSSL commands to generate and manage certificates.
- Include VPN configuration steps using cross-platform or Linux-native tools (e.g., strongSwan, OpenVPN) alongside or instead of PowerShell.
- Mention and document Linux-compatible encryption-at-rest solutions (e.g., LUKS/dm-crypt) if supported, or clarify if BitLocker is mandatory and why.
- Ensure all command-line examples are provided for both Windows (PowerShell/Command Prompt) and Linux (Bash/shell) environments.
- Explicitly state platform requirements and, if Windows-only tools are required, offer guidance for Linux users (such as using a Windows VM or container, or alternative approaches).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-j-series-deploy-configure-compute.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-j-series-deploy-configure-compute.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates subtle Windows bias by referencing Windows tools (File Explorer, Storage Explorer) as the default way to interact with shares and view data, without providing Linux equivalents or examples. The only explicit command-line example is for rsync (a Linux tool), but the verification steps and screenshots assume a Windows environment. There are no Linux-specific instructions or screenshots for accessing shares or verifying data transfer.
Recommendations
- Provide equivalent Linux instructions and screenshots for accessing SMB/NFS shares (e.g., using Nautilus, Dolphin, or the mount command).
- Mention and demonstrate how to use Linux-native tools (such as smbclient, mount, or rsync) for verifying data movement and share access.
- When referencing Storage Explorer, clarify that it is cross-platform and provide installation/use instructions for Linux.
- Avoid assuming File Explorer as the default; instead, offer parallel steps for both Windows and Linux users.
- Include a note or section explicitly addressing Linux users, outlining any differences or additional steps required.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/mqtt-publish-and-subscribe-cli.md
.../articles/event-grid/mqtt-publish-and-subscribe-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the certificate generation section, where instructions and commands are tailored for Windows users (e.g., opening Command Prompt, using Win+R, referencing %USERPROFILE%), and all example commands are presented in PowerShell syntax. There are no equivalent Linux/macOS shell commands or environment instructions provided for generating certificates or running the sample code, despite the cross-platform nature of the Azure CLI and MQTT tooling.
Recommendations
- Provide parallel instructions and command examples for Linux/macOS users, including shell (bash) commands for certificate generation and file path references.
- Avoid Windows-specific environment instructions (e.g., 'Win+R', '%USERPROFILE%') or supplement them with Linux/macOS equivalents (e.g., '~' for home directory).
- Include notes or sections explicitly addressing Linux/macOS users, especially in areas like certificate management and running sample code.
- If using PowerShell commands, also provide bash/zsh equivalents where possible.
- Clarify that the Azure CLI and MQTT tooling are cross-platform, and ensure all steps are accessible from any supported OS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-mini-r-deploy-set-up-device-update-time.md
...ure-stack-edge-mini-r-deploy-set-up-device-update-time.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-based tools and defaults (e.g., Windows Server Update Services, time.windows.com), and by omitting Linux equivalents or examples. Update and time server configuration instructions only mention Microsoft and Windows services, with no mention of Linux-based update or NTP servers, nor any cross-platform considerations.
Recommendations
- Include examples and instructions for configuring Linux-based update servers (such as using a local Linux repository or update mirror) where applicable.
- When discussing NTP servers, suggest cross-platform public NTP servers (e.g., pool.ntp.org) alongside time.windows.com, and clarify that any standards-compliant NTP server can be used.
- Mention that WSUS is a Windows-specific solution and provide guidance for environments where Linux patch management is used.
- Add notes or examples for users managing devices in predominantly Linux environments, including relevant tools and configuration patterns.
- Avoid setting Windows-specific defaults (such as time.windows.com) without also listing neutral or Linux-friendly alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-mini-r-system-requirements.md
...-online/azure-stack-edge-mini-r-system-requirements.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by referencing the PowerShell interface and providing command-line examples only in the context of PowerShell. There are no equivalent Linux shell (bash) commands or instructions, and the monitoring/management tooling is described solely in terms of PowerShell access. This may make it less accessible or clear for Linux users.
Recommendations
- Provide equivalent Linux shell (bash) command examples alongside PowerShell commands for monitoring and management tasks.
- Clarify whether the 'dkr' commands can be run from a Linux shell, and if so, provide explicit Linux usage instructions.
- Mention and document any Linux-compatible management interfaces or tools, if available.
- Ensure that references to management interfaces (such as PowerShell) are balanced with Linux alternatives, or clearly state if only Windows is supported.
- Include a section or callout for Linux users, outlining any differences or additional steps required.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-2-system-requirements.md
...x-online/azure-stack-edge-pro-2-system-requirements.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits a moderate Windows bias. The only explicit command-line example references the PowerShell cmdlet `Set-HcsMacAddressPool`, with no mention of a Linux equivalent or alternative. The troubleshooting link for Kubernetes issues also points to a PowerShell interface, suggesting Windows-centric tooling. There are no Linux shell or CLI examples, and Windows tools are mentioned without parity for Linux users.
Recommendations
- Wherever PowerShell cmdlets are referenced (e.g., `Set-HcsMacAddressPool`), provide equivalent Linux commands or clarify if such functionality is not available on Linux.
- Include Linux shell/CLI examples alongside PowerShell commands for device management and troubleshooting.
- Explicitly mention if certain management interfaces or tools are Windows-only, and provide guidance or workarounds for Linux users.
- Ensure that documentation links for troubleshooting and management cover both Windows and Linux scenarios.
- Review included content (from INCLUDES) to ensure Linux parity in all referenced tables and sections.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-2-deploy-checklist.md
...abox-online/azure-stack-edge-pro-2-deploy-checklist.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (such as WSUS and the public Windows Update server) and omitting Linux equivalents or alternatives. There are no examples or instructions for Linux or cross-platform environments, and Windows-centric terminology is used without mention of Linux-compatible solutions.
Recommendations
- Include instructions or references for using Linux-compatible update servers (e.g., apt, yum, or local Linux package mirrors) alongside WSUS.
- Mention or provide examples for configuring device settings (such as static IP, NTP, and certificates) from both Windows and Linux environments.
- Avoid assuming the use of Windows laptops for device connection; explicitly state that any OS (Windows, Linux, macOS) with configurable IPv4 settings can be used.
- Where Windows tools or services are mentioned (e.g., Windows Update, WSUS), add notes or links for Linux equivalents or clarify if the device is OS-agnostic in those respects.
- Ensure parity in troubleshooting and setup steps for both Windows and Linux users, possibly by adding a 'Platform considerations' section.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-2-deploy-configure-certificates.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-2-deploy-configure-certificates.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (such as Azure PowerShell and Windows Server Update Services), showing certificate download examples in Windows File Explorer, and omitting Linux-based certificate management or installation instructions. There are no Linux or cross-platform command-line examples, and Windows patterns are mentioned before or instead of Linux equivalents.
Recommendations
- Include Linux-based examples for certificate installation and management, such as using OpenSSL for certificate conversion and installation.
- Provide instructions for importing certificates on Linux clients (e.g., using update-ca-certificates or trust anchors).
- Mention cross-platform tools (e.g., Azure CLI, OpenSSL) alongside or before Windows-specific tools like PowerShell.
- Show screenshots or file explorer examples from Linux environments in addition to Windows.
- Reference Linux equivalents for Windows Server Update Services (WSUS) scenarios, or clarify if certain steps are Windows-only.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-2-deploy-configure-compute.md
...ine/azure-stack-edge-pro-2-deploy-configure-compute.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page shows a Windows bias by referencing the use of the PowerShell cmdlet `Set-HcsMacAddressPool` for configuring MAC addresses, without providing equivalent Linux commands or guidance. No Linux shell or cross-platform alternatives are mentioned for this step, and the only CLI example is Windows-specific. The rest of the tutorial relies on the web UI, which is platform-agnostic, but the only command-line example is Windows-centric.
Recommendations
- Provide Linux or cross-platform alternatives for the PowerShell cmdlet, such as equivalent commands using SSH and standard Linux networking tools (e.g., ip, ifconfig, or nmcli), if supported by the device.
- Explicitly state whether the configuration steps can be performed from Linux/macOS clients, and provide instructions if so.
- Where only PowerShell is supported, clarify this limitation and suggest workarounds for non-Windows users (e.g., using PowerShell Core on Linux, or accessing the device via the web UI).
- Ensure future documentation includes both Windows and Linux command-line examples for all device management tasks, or clearly notes platform restrictions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-mini-r-use-wifi-profiles.md
...ox-online/azure-stack-edge-mini-r-use-wifi-profiles.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively providing instructions and examples for exporting Wi-Fi profiles using Windows-specific tools (netsh via Command Prompt), referencing Windows 10 client behavior, and linking to Windows-specific Intune documentation. There are no examples or instructions for performing equivalent tasks on Linux or macOS, nor are cross-platform tools or methods mentioned.
Recommendations
- Add equivalent instructions for exporting Wi-Fi profiles on Linux (e.g., using nmcli, wpa_cli, or by copying relevant files from /etc/NetworkManager/system-connections/ or /etc/wpa_supplicant/).
- Include macOS instructions for exporting Wi-Fi profiles (e.g., using security or networksetup commands).
- When referencing external documentation, provide links to cross-platform or Linux/macOS-specific resources where available.
- Avoid assuming the administrator's workstation is Windows; clarify that the process can be performed from any supported OS and provide parity in examples.
- If XML profile formats differ between platforms, document the differences and provide conversion guidance.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-2-deploy-set-up-device-update-time.md
...zure-stack-edge-pro-2-deploy-set-up-device-update-time.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 referencing Windows-centric tools and defaults, such as Windows Server Update Services (WSUS), Microsoft Update server, and time.windows.com as the default NTP server. There are no mentions of Linux equivalents (e.g., Linux update mirrors, chrony/ntpd, or pool.ntp.org), nor are there examples or guidance for users in Linux-centric environments. The documentation assumes a Windows-based infrastructure for update and time services, and does not provide parity for Linux users.
Recommendations
- Include examples and guidance for configuring update servers using Linux-based solutions (e.g., apt/yum repositories, local Linux mirrors).
- Mention and provide examples of using public and Linux-friendly NTP servers (e.g., pool.ntp.org) alongside time.windows.com.
- Clarify that WSUS and Microsoft Update are Windows-specific, and suggest alternatives for environments where Linux is prevalent.
- Where possible, provide cross-platform instructions or note any platform-specific requirements.
- Explicitly state if the device or service only supports Windows-based update/time infrastructure, or provide workarounds for Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-r-deploy-checklist.md
...abox-online/azure-stack-edge-pro-r-deploy-checklist.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools (e.g., WSUS, Windows Update server), omitting Linux equivalents or alternatives, and generally assuming a Windows-centric environment for device management and updates. There are no explicit Linux or cross-platform instructions, examples, or tool mentions, especially regarding update servers and network readiness tools.
Recommendations
- Include references to Linux-compatible update mechanisms (e.g., mention that Linux-based update servers or repositories can be used if supported, or clarify if only Windows Update/WSUS is supported).
- Provide examples or guidance for Linux users, such as how to configure network settings or connect to the device from a Linux laptop.
- Mention cross-platform or open-source network readiness tools if available, or clarify OS requirements for the Azure Stack Edge Network Readiness Tool.
- Avoid assuming Windows as the default environment; explicitly state if certain features/tools are Windows-only and suggest alternatives or workarounds for Linux users.