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 1401-1425 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/how-to/develop-custom-package/6-sign-package.md
...ration/how-to/develop-custom-package/6-sign-package.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows-first bias by presenting Windows/Powershell instructions and examples before Linux equivalents. The primary signing workflow is described using Powershell cmdlets and Windows certificate tools, with Linux instructions following and still relying on Powershell for the signing step. The certificate export/import examples and references are also Windows-centric, and Azure Policy/Key Vault links are Windows-focused.
Recommendations
- Present Linux and Windows instructions in parallel sections or with equal prominence, rather than listing Windows first.
- Provide native Linux command-line examples for all steps, including package signing, certificate/key generation, and installation, using standard Linux tools (e.g., OpenSSL, GPG, update-ca-certificates) without requiring Powershell.
- Include Linux-focused references and links (e.g., to Azure Linux VM documentation, Linux Key Vault setup).
- Clarify which steps require Powershell and offer alternatives for Linux users who may not have Powershell installed.
- Ensure that all parameter documentation and examples are equally detailed for both platforms.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/whats-new/migrating-from-dsc-extension.md
...onfiguration/whats-new/migrating-from-dsc-extension.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page is heavily focused on Windows and PowerShell-based workflows. All examples and migration steps reference PowerShell DSC, Windows PowerShell versions, and Windows-specific tools and concepts. There is no mention of Linux equivalents, nor are Linux-specific scenarios or commands provided. The guidance assumes the reader is working in a Windows environment, and Linux support or differences are not addressed.
Recommendations
- Include explicit guidance for Linux VMs, such as how to check for DSC extension usage on Linux (if supported), and clarify any differences in extension names or behaviors.
- Provide examples using Bash or other Linux-native tools where applicable, or clarify if only PowerShell is supported on Linux.
- Discuss any differences in how machine configuration and DSC extension work on Linux versus Windows, including supported features and limitations.
- Mention the required PowerShell versions and modules for Linux, and provide installation instructions or references for Linux environments.
- Add a section or callouts for Linux users to ensure parity and clarify platform-specific considerations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/management-groups/create-management-group-dotnet.md
...ce/management-groups/create-management-group-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Windows-specific instructions and examples. The execution command uses a Windows-style executable (mgCreate.exe) and PowerShell-style line continuations (`), with no mention of Linux or cross-platform alternatives. There are no Linux/macOS-specific instructions for running the .NET Core application, and the use of .exe implies a Windows environment. Additionally, the cleanup instructions reference deleting folders in a way that assumes Windows conventions.
Recommendations
- Include Linux/macOS-specific instructions for running the .NET Core application (e.g., using 'dotnet mgCreate.dll' or './mgCreate' for self-contained deployments).
- Provide examples using both Windows and Linux/macOS command-line syntax, including appropriate line continuations (e.g., '\' for bash).
- Clarify that .NET Core is cross-platform and that the steps apply to all supported OSes, with any OS-specific differences clearly called out.
- Update cleanup instructions to mention Linux/macOS folder deletion commands (e.g., 'rm -rf mgCreate').
- Avoid using only .exe in examples; mention .dll or platform-appropriate executables for .NET Core apps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/concepts/definition-structure-alias.md
...vernance/policy/concepts/definition-structure-alias.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as a primary method for discovering policy aliases, providing more detailed PowerShell examples (including advanced filtering), and mentioning PowerShell before Azure CLI. The CLI section is less detailed and lacks parity with the PowerShell examples. There is no mention of Linux-specific tools or shell scripting, and the PowerShell examples assume familiarity with Windows tooling.
Recommendations
- Ensure that Azure CLI examples are as detailed as the PowerShell ones, including advanced filtering (e.g., how to find modifiable aliases using CLI/jq).
- Alternate the order of PowerShell and CLI sections, or present them side-by-side to avoid implying one is preferred.
- Explicitly mention that both PowerShell and CLI are cross-platform, and provide context for users on Linux/macOS.
- Include Bash or shell scripting examples where appropriate, especially for filtering or processing output.
- Avoid language that assumes PowerShell is the default or primary tool for all users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/assign-policy-rest-api.md
...//articles/governance/policy/assign-policy-rest-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by primarily referencing PowerShell-specific syntax (such as the use of backticks for escaping), mentioning PowerShell and Windows tools (Visual Studio Code, Git Bash) before Linux-native equivalents, and not providing explicit Linux/Bash-native command examples. While it notes that Bash shells like Git Bash can be used, it does not show concrete Bash/Linux-native command lines or address differences in escaping and file referencing in Bash versus PowerShell. This may confuse or disadvantage Linux users.
Recommendations
- Provide explicit Bash/Linux-native command examples alongside PowerShell examples, especially for commands where escaping or syntax differs.
- Document the differences in file referencing and escaping between PowerShell and Bash (e.g., use of @request-body.json in Bash vs `@request-body.json in PowerShell).
- Mention Linux-native shells (such as Ubuntu Bash, macOS Terminal) and editors (such as nano, vim) in prerequisites, not just Git Bash and Visual Studio Code.
- Where PowerShell-specific syntax is discussed, provide the equivalent Bash/Linux syntax in parallel.
- Consider using a tabbed interface or side-by-side examples for Windows/PowerShell and Linux/Bash users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/concepts/effect-modify.md
...//articles/governance/policy/concepts/effect-modify.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing Azure PowerShell as the only method for retrieving modifiable policy aliases, without mentioning or providing equivalent Azure CLI (cross-platform) or REST API examples. No Linux-specific or cross-platform command-line examples are provided, and the only tool-specific guidance is for PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, especially for retrieving modifiable aliases (e.g., using 'az policy alias list').
- Mention REST API alternatives where applicable for cross-platform automation.
- Ensure that tool-specific instructions (such as PowerShell) are always accompanied by Azure CLI or REST API equivalents, and present them in a neutral order (e.g., CLI first, or both together).
- Explicitly state that all examples are cross-platform where possible, or clarify any platform-specific limitations.
- Audit other sections for implicit Windows assumptions and add Linux or cross-platform context as needed.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/how-to/export-resources.md
.../articles/governance/policy/how-to/export-resources.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for exporting Azure Policy resources. However, the PowerShell section is prominent and detailed, and PowerShell is a Windows-centric tool (despite cross-platform support, it is still most familiar to Windows users). There is no mention of Linux-specific shell commands or workflows (e.g., Bash, jq, curl), nor are there examples showing how to process or export data in a Linux-native way. The 'Export to CSV' section references the Azure portal, which is platform-agnostic, but does not address command-line or automation scenarios on Linux.
Recommendations
- Add Linux-native command-line examples, such as using Azure CLI with Bash and jq to process and export policy resources.
- Explicitly mention that Azure CLI is cross-platform and provide examples that demonstrate usage on Linux/macOS terminals.
- Include sample scripts or one-liners for exporting to CSV or JSON using standard Linux tools.
- Balance the prominence of PowerShell by ensuring CLI and Linux-native workflows are equally represented and described.
- Where PowerShell is mentioned, clarify that it is available cross-platform, but also provide alternatives for users who prefer not to use PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/how-to/migrate-from-automanage-best-practices.md
...olicy/how-to/migrate-from-automanage-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific tools and examples, such as Windows Admin Center and Microsoft Antimalware for Windows Server, while providing limited or less detailed guidance for Linux systems. Windows-related features and extensions are often mentioned first or exclusively, and Linux equivalents are sometimes only briefly referenced without equivalent depth or examples.
Recommendations
- Provide Linux-specific examples and configuration steps alongside Windows examples for all relevant features (e.g., antimalware, admin tools).
- When listing policies or extensions, present Windows and Linux options together or alternate their order to avoid Windows-first bias.
- Include references to Linux-native tools or extensions (e.g., ClamAV, Linux diagnostics) where appropriate, and explain how to manage them via Azure Policy.
- Expand documentation on Linux VM management, such as using SSH, Linux package managers, or Linux-specific monitoring/backup agents.
- For sections like Windows Admin Center, mention and link to equivalent Linux management options (e.g., Azure Serial Console, SSH, Azure CLI for Linux).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/how-to/programmatically-create.md
...es/governance/policy/how-to/programmatically-create.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows and PowerShell tools and instructions. PowerShell is introduced and explained before Azure CLI, and the prerequisite steps focus on Windows-centric tools (e.g., ARMClient, PowerShell module) and provide a Windows-specific Azure CLI installation link. There are no explicit Linux or macOS installation instructions or examples, and some commands (such as PowerShell) are not cross-platform by default. The use of ARMClient, which is not natively available on Linux, further reinforces the bias.
Recommendations
- Provide Azure CLI installation instructions for Linux and macOS alongside the Windows link in the prerequisites.
- Clearly indicate that Azure PowerShell is cross-platform, or provide equivalent Bash or shell script examples for Linux/macOS users.
- Include Linux/macOS-specific notes or examples where file paths, environment variables, or command syntax may differ.
- Mention alternative tools to ARMClient that are natively available or easily installable on Linux/macOS, or provide Docker-based usage instructions.
- Ensure that all code snippets and instructions are tested and applicable on both Windows and Linux/macOS platforms, or clearly label any platform-specific steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/samples/built-in-packages.md
...rticles/governance/policy/samples/built-in-packages.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. Most examples and policy definitions are Windows-centric, with the majority of configurations and required modules targeting Windows features or tools. PowerShell Desired State Configuration (DSC) and Windows-specific modules are referenced throughout, with little to no equivalent detail or parity for Linux. Linux is mentioned in only a few entries, and Linux-specific modules or examples are sparse or missing. The introductory text also frames PowerShell and Windows as the primary context for guest configuration.
Recommendations
- Add more Linux-focused policy definitions and configuration examples to the table, ensuring Linux is represented in parity with Windows.
- Include links to Linux-specific modules or scripts where available, not just PowerShell DSC modules.
- Update the introductory text to explicitly mention both Windows and Linux, and describe how guest configuration applies to each platform.
- Where possible, provide equivalent Linux examples or references alongside Windows ones, rather than focusing almost exclusively on Windows.
- If certain features are Windows-only, clearly state this and provide guidance or alternatives for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/samples/canada-federal-pbmm.md
...icles/governance/policy/samples/canada-federal-pbmm.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas. Many policy definitions and audit controls are specific to Windows (e.g., auditing Windows Administrators group, password policies, secure communication protocols), while equivalent Linux controls are either missing or less detailed. Windows-specific Guest Configuration extensions and policies are listed and described in detail, with Linux equivalents only occasionally mentioned and often with less coverage. In several sections, Windows policies are listed before Linux ones, and some controls (such as password complexity, minimum/maximum password age, and secure communication protocols) are only described for Windows, with no Linux counterpart provided.
Recommendations
- Add equivalent Linux policy definitions and audit controls wherever Windows-specific ones are present (e.g., for password complexity, minimum/maximum password age, secure communication protocols, and administrators group membership).
- Ensure Linux Guest Configuration extension deployment and audit policies are described with the same level of detail as Windows.
- When listing both Windows and Linux controls, alternate the order or group them together to avoid always listing Windows first.
- Where a Windows-only policy is present, explicitly state if there is no Linux equivalent and, if possible, provide guidance or workarounds for Linux systems.
- Expand documentation to include Linux-specific security best practices and compliance checks to achieve parity with Windows coverage.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/concepts/policy-for-kubernetes.md
...es/governance/policy/concepts/policy-for-kubernetes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Azure CLI and Azure Portal are the primary tools shown for all management tasks, which are cross-platform, but there are several references to Azure PowerShell and Windows-specific domains (e.g., login.windows.net). PowerShell commands are provided alongside Azure CLI in some prerequisite steps, but there are no explicit Linux shell or Bash script examples for tasks that could be performed outside Azure CLI. The documentation assumes use of Azure CLI (which is cross-platform), but does not provide parity for Linux-native tools or workflows (e.g., no mention of native Linux package managers, systemd, or Linux-specific troubleshooting). Windows domains and terminology (e.g., login.windows.net, references to Windows pods) are mentioned before or more prominently than Linux equivalents. There is a lack of explicit Linux-first or Linux-native guidance, despite the fact that AKS and Kubernetes clusters are predominantly Linux-based.
Recommendations
- Where Azure PowerShell is mentioned, ensure that equivalent Bash or Linux-native commands are provided, or clarify that Azure CLI is cross-platform and preferred for Linux users.
- When listing domains or endpoints (e.g., login.windows.net), clarify if these are required regardless of OS, and provide context for Linux users.
- Add explicit notes or sections for Linux users, such as how to install Azure CLI using apt, yum, or other package managers, and how to troubleshoot using Linux-native tools.
- If referencing Windows pods or features, provide equal or greater detail for Linux pods, given that AKS clusters are Linux by default.
- Review the order of tool presentation: prefer Azure CLI (cross-platform) and kubectl (Linux-native) before mentioning Azure PowerShell or Windows-specific tools.
- Include troubleshooting steps or log collection examples using Linux-native commands (e.g., journalctl, systemctl) where relevant.
- If possible, provide example scripts or automation in Bash as well as PowerShell, especially for cluster management and policy assignment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/how-to/get-compliance-data.md
...ticles/governance/policy/how-to/get-compliance-data.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but PowerShell is given equal or greater prominence throughout, including detailed usage patterns (e.g., background jobs) that are specific to PowerShell and Windows environments. The PowerShell section is as detailed as the CLI section, and sometimes includes advanced usage (e.g., jobs) not mirrored for CLI. There is no mention of Linux-specific shells or scripting environments, and PowerShell is presented as a primary tool, which may bias the documentation toward Windows users. No explicit Linux examples or notes about running CLI commands in Bash or other Linux shells are present.
Recommendations
- Add explicit Bash/Linux shell examples alongside Azure CLI commands, including sample usage in Bash scripts.
- Clarify that Azure CLI commands are cross-platform and can be run in Bash, PowerShell, or other shells, and provide examples for both environments.
- Where advanced PowerShell usage is shown (e.g., jobs), provide equivalent Bash/Linux scripting patterns (e.g., backgrounding CLI commands with & or using nohup).
- Mention that Azure CLI is available on Linux, macOS, and Windows, and provide links or notes for installing and using it on Linux.
- Balance the order of presentation so that CLI and Bash/Linux examples are not always after PowerShell, and avoid giving PowerShell exclusive advanced usage coverage.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/how-to/author-policies-for-arrays.md
...governance/policy/how-to/author-policies-for-arrays.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias in the section on passing array parameters during policy assignment. It lists Azure CLI, Azure PowerShell, and REST API, but presents Azure CLI and PowerShell as the primary command-line interfaces, with PowerShell mentioned explicitly and no Linux-specific shell (e.g., Bash) or cross-platform scripting examples. There are no Linux- or Bash-specific examples or notes, and the guidance for the Azure portal's textbox separator uses a semicolon (;) without clarifying if this is consistent across all OS/browser combinations. The rest of the document is platform-neutral, focusing on JSON and Azure Policy syntax.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide Bash shell examples where appropriate.
- Clarify that Azure PowerShell is available on Linux and macOS, or provide Bash/Unix shell alternatives for PowerShell commands.
- Add a note on whether the semicolon (;) separator in the Azure portal is consistent across all platforms and locales.
- Where commands are referenced (e.g., az policy assignment create), provide both Windows (PowerShell/CMD) and Linux (Bash) command-line examples.
- Review other sections for implicit assumptions about the user's operating system and add clarifications or alternatives as needed.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/samples/rmit-malaysia.md
...n//articles/governance/policy/samples/rmit-malaysia.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. While the majority of the content is platform-agnostic (focused on Azure Policy definitions and compliance controls), there are several instances where Windows-specific tools, extensions, or features are mentioned without equivalent Linux references. For example, policies such as 'Deploy Log Analytics extension to Windows virtual machine scale sets' and 'Microsoft Antimalware for Azure should be configured to automatically update protection signatures' are specific to Windows VMs, with no mention of Linux alternatives. Additionally, Windows is sometimes mentioned first or exclusively in policy names and descriptions, while Linux is omitted or only referenced in a minority of cases.
Recommendations
- Wherever a Windows-specific policy or tool is mentioned (e.g., Log Analytics extension for Windows VMSS, Microsoft Antimalware), ensure that equivalent Linux policies/tools are also listed and described if available.
- If a policy applies to both Windows and Linux (e.g., Log Analytics agent), clarify this in the description and provide links or references for both platforms.
- Avoid listing Windows policies or tools before Linux equivalents unless there is a clear technical reason; consider grouping by platform or providing parallel examples.
- For policies or extensions that are only available for Windows, explicitly state this and, if possible, provide guidance or alternatives for Linux users.
- Review policy naming conventions to ensure Linux is not omitted where relevant (e.g., 'Deploy Log Analytics extension to Windows and Linux virtual machine scale sets').
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/samples/gov-irs-1075-sept2016.md
...les/governance/policy/samples/gov-irs-1075-sept2016.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. In several control areas (such as Separation of Duties, Least Privilege, and Authenticator Management), Windows-specific policies and controls are listed before their Linux equivalents, or Linux examples are less detailed or missing. There are multiple policies focused on Windows-specific tools and concepts (e.g., Administrators group, password complexity, Windows Guest Configuration extension), while equivalent Linux controls are less prominent or absent. Some controls have detailed Windows policies but lack parity for Linux, or Linux policies are listed after Windows ones.
Recommendations
- Ensure that for every Windows-specific policy or example, an equivalent Linux policy or example is provided and described with equal prominence and detail.
- When listing policies or controls that apply to both Windows and Linux, alternate the order or group them together to avoid always listing Windows first.
- Expand Linux coverage for areas where only Windows policies are present (e.g., password complexity, group membership auditing) by including or referencing equivalent Linux controls (such as /etc/sudoers, PAM configuration, etc.).
- Where Windows tools or concepts are mentioned (e.g., Administrators group), provide Linux equivalents (e.g., sudoers, user/group management) and link to relevant documentation.
- Audit the documentation for any missing Linux-specific security or compliance controls and add them to ensure full parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/samples/irs-1075-sept2016.md
...rticles/governance/policy/samples/irs-1075-sept2016.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. In several policy tables, Windows-specific policies (such as auditing Windows Administrators group membership or password policies) are present without equivalent Linux-focused policies. Where both Windows and Linux policies exist, Windows policies are often listed before Linux ones. There are more granular and numerous Windows-specific controls (e.g., password complexity, minimum/maximum age, encryption settings) compared to Linux, which is only covered by a few generic policies (e.g., passwordless accounts, passwd file permissions). Additionally, some policy descriptions and controls reference Windows tools or concepts (like the 'Administrators group') without Linux equivalents or guidance.
Recommendations
- Ensure Linux equivalents are provided for all Windows-specific policies, especially for password policies, group membership, and security settings.
- When listing both Windows and Linux policies, alternate the order or group them together to avoid always presenting Windows first.
- Expand Linux policy coverage to match the granularity of Windows controls (e.g., minimum/maximum password age, password complexity, group membership auditing).
- Where Windows-specific tools or concepts are mentioned (e.g., 'Administrators group'), provide Linux analogs (e.g., 'sudoers', 'wheel group') or note the difference.
- Consider adding explicit Linux examples or references in policy descriptions and documentation links.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/samples/pci-dss-4-0.md
...ain//articles/governance/policy/samples/pci-dss-4-0.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on Azure portal and Azure Policy UI, with some references to Windows-specific tools and policies (e.g., Guest Configuration extension for Windows VMs, password policies for Windows machines). There are several audit policies that specifically mention Windows machines and their password settings, but there are no equivalent Linux examples or explicit parity for Linux-based systems. The documentation does not provide cross-platform command-line or scripting examples (e.g., PowerShell vs. Bash/CLI), nor does it mention Linux tools or configuration patterns where relevant. This results in a bias toward Windows environments and leaves Linux users with less guidance.
Recommendations
- For every Windows-specific policy or example (such as password policies, Guest Configuration extension), provide equivalent Linux-focused guidance and examples.
- Include explicit references to Linux VM management, configuration, and compliance policies alongside Windows examples.
- Where Azure Policy or Guest Configuration supports both Windows and Linux, clarify the parity and provide links or documentation for both platforms.
- Add CLI/Bash examples or documentation for Linux users, not just portal or Windows-centric instructions.
- Review all audit and configuration policies to ensure Linux systems are equally covered and that documentation does not assume a Windows-only environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/linter-rule-use-stable-vm-image.md
...ource-manager/bicep/linter-rule-use-stable-vm-image.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides only Windows-based VM image examples ('WindowsServer', '2019-Datacenter'), with no mention or example of Linux images. This can give the impression that the rule or tool is primarily intended for Windows environments, and does not demonstrate parity for Linux users.
Recommendations
- Include equivalent Linux-based examples (e.g., using 'UbuntuServer' or 'CentOS' offers and skus) alongside or alternating with Windows examples.
- Explicitly mention that the rule applies to both Windows and Linux VM images.
- Where possible, provide a table or list of both Windows and Linux image references to illustrate the rule's applicability across platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/includes/digital-twins-tenant-solution-2.md
...ital-twins/includes/digital-twins-tenant-solution-2.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation provides a C# example and references Visual Studio and Visual Studio Code as tools for authentication configuration, both of which are traditionally associated with Windows environments (though VS Code is cross-platform). There are no examples or mentions of Linux-specific tools, command-line interfaces, or alternative editors, and no guidance for Linux users is provided.
Recommendations
- Include examples using cross-platform command-line tools such as Azure CLI or PowerShell Core (which runs on Linux) for setting authentication options.
- Mention and provide examples for configuring authentication in popular Linux editors (e.g., Vim, Emacs) or using environment variables.
- Clarify that Visual Studio Code is cross-platform, and provide Linux-specific setup instructions if relevant.
- Add explicit Linux/macOS instructions or notes to ensure parity for non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/managed-identity.md
...docs/blob/main//articles/frontdoor/managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes configuration via the Azure Portal UI, with no command-line examples provided. There is no mention of cross-platform CLI tools (such as Azure CLI or Azure PowerShell), nor are any Linux-specific instructions or examples included. While the page avoids explicit Windows/Powershell bias by not mentioning those tools, it implicitly favors Windows by omitting any Linux or CLI-based workflows, which are common in Linux environments.
Recommendations
- Add Azure CLI examples for all major configuration steps (enabling managed identity, assigning roles, configuring access policies, verifying access), as Azure CLI is cross-platform and widely used on Linux.
- If relevant, provide Azure PowerShell examples as well, but ensure Azure CLI examples are presented first or alongside them.
- Explicitly mention that all steps can be performed via CLI on Linux, macOS, and Windows, and link to relevant CLI documentation.
- Include a note or section for automation and scripting, highlighting cross-platform approaches.
- Where screenshots are used, consider including CLI output or code snippets as alternatives for users not using the Azure Portal.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-mini-r-deploy-connect.md
...tabox-online/azure-stack-edge-mini-r-deploy-connect.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation references the 'Azure Stack Network Readiness Checker tool' without specifying platform compatibility or providing Linux alternatives. Additionally, instructions for configuring the Ethernet adapter assume familiarity with Windows networking concepts and do not provide Linux-specific steps or examples.
Recommendations
- Explicitly state whether the Azure Stack Network Readiness Checker tool is available for Linux, and if not, provide equivalent Linux-compatible tools or manual steps.
- Include step-by-step instructions or command-line examples for configuring a static IP address on Linux systems (e.g., using nmcli, ifconfig, or editing /etc/network/interfaces).
- Ensure illustrations and terminology are inclusive of both Windows and Linux environments (e.g., referencing 'Network Connections' is Windows-specific; provide Linux GUI and CLI alternatives).
- Add a section or callout for macOS/Linux users to ensure parity and clarity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-mini-r-overview.md
...les/databox-online/azure-stack-edge-mini-r-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows subtle Windows bias by referencing BitLocker (a Windows-specific encryption tool) as part of the double encryption feature, and by linking to a VPN configuration guide that explicitly mentions PowerShell in the URL. There are no explicit Linux examples or Linux-specific tools mentioned, and Windows tools are referenced without Linux equivalents or alternatives.
Recommendations
- When mentioning BitLocker, also reference Linux-compatible disk encryption solutions (e.g., LUKS/dm-crypt) and clarify if/how they are supported.
- If PowerShell is required for VPN configuration, provide equivalent Linux command-line instructions (e.g., using Bash or Linux-native tools) or clarify platform support.
- Explicitly state whether Linux-based management or configuration is supported, and provide examples or links for Linux users.
- Ensure that protocol support (e.g., SMB, NFS) is described with parity for both Windows and Linux environments, including any platform-specific caveats or instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-2-technical-specifications-compliance.md
...e-stack-edge-pro-2-technical-specifications-compliance.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in the storage specifications section, where 'Storage Spaces Direct with mirroring' (a Windows Server technology) is referenced as the RAID configuration, with a link to Windows Server documentation. There is no mention of Linux-based storage technologies or parity for Linux users. No Linux alternatives or examples are provided, and the documentation assumes the use of Windows-native tools for storage management.
Recommendations
- Include information about whether Linux-based storage management or RAID solutions (such as mdadm, LVM, or ZFS) are supported or possible on Azure Stack Edge Pro 2 devices.
- If the device is Windows-only, explicitly state this in the documentation to clarify the intended audience.
- If Linux is supported, provide equivalent Linux tooling or configuration examples alongside Windows references.
- Reference both Windows and Linux documentation for storage and management tasks, or clarify any platform limitations.
- Consider adding a section on cross-platform compatibility and management options for users who may wish to integrate the device into heterogeneous environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-pro-r-configure-vpn-bcdr.md
...ox-online/azure-stack-edge-pro-r-configure-vpn-bcdr.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation does not provide any OS-specific command-line examples, but it implicitly assumes the use of Azure Portal and Azure tools, which are cross-platform. However, there is a lack of explicit Linux CLI or scripting examples (such as Azure CLI or Bash), and no mention of Linux-specific tools or workflows. This may disadvantage Linux users who prefer or require command-line automation.
Recommendations
- Add explicit examples using Azure CLI commands (az), which are cross-platform and commonly used on Linux.
- Include sample scripts or command-line workflows for both Windows (PowerShell) and Linux (Bash) environments.
- Mention that all configuration steps can be performed via Azure CLI or REST API, and provide links to relevant documentation.
- If any step requires a tool that is Windows-only (such as certain PowerShell modules), provide Linux alternatives or note the limitation.