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 1976-2000 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/remote-work-support.md
...cs/blob/main//articles/firewall/remote-work-support.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on Windows-based virtual desktop infrastructure (VDI) and Azure Virtual Desktop, highlighting features like multi-session Windows 10/11 and Remote Desktop Services (RDS). There is no mention of Linux-based VDI solutions, Linux client support, or examples relevant to non-Windows environments. All examples and scenarios assume a Windows-centric deployment.
Recommendations
- Include information about securing Linux-based VDI solutions or clients with Azure Firewall, if supported.
- Mention whether Azure Firewall can be used to protect non-Windows virtual desktops or remote work scenarios involving Linux/macOS endpoints.
- Provide examples or references for configuring Azure Firewall in environments that include Linux virtual machines or mixed-OS deployments.
- Clarify if Azure Virtual Desktop or similar Azure services support Linux desktops, and if so, add relevant guidance.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/threat-intel.md
...zure-docs/blob/main//articles/firewall/threat-intel.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a hosts file modification example specifically for Windows (C:\Windows\System32\drivers\etc\hosts) and does not mention how to perform the equivalent operation on Linux or macOS. No Linux or cross-platform instructions are given for this common task, and Windows is the only OS referenced in the example.
Recommendations
- Include equivalent instructions for modifying the hosts file on Linux (e.g., /etc/hosts) and macOS.
- Use cross-platform language when describing file paths and system operations, or provide OS-specific sections for clarity.
- Explicitly mention that the steps apply to all major operating systems, not just Windows.
- Where possible, provide command-line examples that work on both Windows (e.g., PowerShell) and Linux/macOS (e.g., bash), or note the differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/quick-create-multiple-ip-terraform.md
...rticles/firewall/quick-create-multiple-ip-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by focusing exclusively on deploying and accessing Windows Server virtual machines, with no mention of Linux VMs or Linux-specific use cases. The NAT rules and password generation are tailored for Windows, and there are no parallel Linux examples or instructions. Additionally, the only referenced scenario for remote access is RDP to Windows servers, with no SSH/Linux guidance.
Recommendations
- Include parallel instructions and Terraform resources for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine).
- Demonstrate NAT/firewall rules for SSH access to Linux VMs, alongside the existing RDP/Windows examples.
- Show how to generate random passwords or SSH keys for Linux VMs.
- Reference both Windows and Linux remote access scenarios (RDP and SSH) in the checklist and verification steps.
- Provide links to both Windows and Linux-focused follow-up documentation or tutorials.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/tutorial-firewall-deploy-portal.md
...//articles/firewall/tutorial-firewall-deploy-portal.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation exclusively uses Windows Server as the example operating system for the test virtual machine, and all testing instructions (such as RDP and Internet Explorer) are Windows-centric. There are no Linux-based examples or instructions, and Linux tools or patterns are not mentioned. This creates a bias toward Windows users and omits guidance for Linux administrators.
Recommendations
- Include parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) alongside the Windows example.
- Provide Linux-specific testing steps, such as connecting via SSH and using a browser like Firefox or Chrome to test outbound access.
- Mention both RDP (for Windows) and SSH (for Linux) as remote access methods.
- When discussing DNS configuration, include instructions for setting DNS servers on a Linux VM's network interface or within the OS.
- Ensure that all example commands and screenshots are provided for both Windows and Linux environments where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/tutorial-firewall-deploy-portal-policy.md
...les/firewall/tutorial-firewall-deploy-portal-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The tutorial demonstrates a Windows bias by exclusively using a Windows Server virtual machine for the workload example and providing instructions only for connecting via Remote Desktop (RDP) and using Microsoft Edge. There are no Linux VM deployment instructions, nor are there examples for connecting to or testing from a Linux-based workload. The documentation assumes the user is familiar with Windows environments and omits Linux alternatives.
Recommendations
- Include parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) as the workload server, alongside the Windows Server example.
- Provide guidance for connecting to the Linux VM (e.g., using SSH) and testing firewall rules from a Linux environment (e.g., using curl or wget to test outbound access).
- Show how to configure DNS settings on a Linux VM's network interface, or provide a note/link to relevant Linux configuration steps.
- When describing test steps, include both RDP (for Windows) and SSH (for Linux) connection methods, and browser-based as well as command-line (curl/wget) testing.
- Explicitly state that the tutorial can be followed with either Windows or Linux workload VMs, and provide links to Azure documentation for both OS types.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/tutorial-firewall-dnat-policy.md
...in//articles/firewall/tutorial-firewall-dnat-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The tutorial exclusively uses Windows Server as the example operating system for the workload VM, specifically instructing users to deploy 'Windows Server 2016 Datacenter' and to test connectivity using Remote Desktop (RDP). There are no instructions or examples for deploying a Linux VM, nor are there alternative Linux-compatible test methods (such as SSH) provided. This presents a Windows-first bias and omits Linux parity in both deployment and testing steps.
Recommendations
- Provide parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu Server) alongside the Windows example.
- Include Linux-specific test steps, such as connecting via SSH to the Linux VM, and mention the relevant port (22) and protocol.
- When describing DNAT rule creation, show examples for both RDP (Windows, port 3389) and SSH (Linux, port 22), clarifying how to configure each.
- Explicitly state that the tutorial applies to both Windows and Linux workloads, and that users can choose either OS based on their needs.
- Consider alternating the order of examples or presenting both OS options together to avoid a 'Windows-first' impression.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/tutorial-protect-firewall-ddos.md
...n//articles/firewall/tutorial-protect-firewall-ddos.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The tutorial exclusively uses Windows Server as the example operating system for the workload VM, and the testing instructions reference Remote Desktop and Internet Explorer, both Windows-specific tools. There are no Linux equivalents or instructions provided, and Linux is not mentioned as an option for the workload VM or for testing the firewall.
Recommendations
- Include instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) as an alternative to Windows Server in the 'Create a virtual machine' section.
- Provide Linux-specific guidance for connecting to the VM (e.g., using SSH instead of Remote Desktop) and for testing outbound connectivity (e.g., using curl or wget to test access to allowed/blocked FQDNs).
- Mention both Windows and Linux options in all relevant sections, and ensure parity in examples and testing steps.
- Avoid referencing Windows-only tools (like Internet Explorer) as the sole method for testing; suggest cross-platform browsers or command-line tools.
- Add a note or table summarizing differences or considerations for Linux vs. Windows VMs in this scenario.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/create-front-door-portal.md
...b/main//articles/frontdoor/create-front-door-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively providing instructions and examples for deploying Web Apps on Windows, with no mention of Linux as an operating system option. The 'Operating System' field is set to 'Windows' by default, and the App Service Plan is referred to as 'Windows Plan.' There are no examples or guidance for users wishing to deploy on Linux, nor are there any cross-platform command-line examples (e.g., Azure CLI, Bash, PowerShell).
Recommendations
- Provide parallel instructions and screenshots for deploying Web Apps on Linux, including selecting 'Linux' as the operating system and choosing a runtime stack available on Linux (e.g., Node.js, Python, .NET Core).
- Use neutral terminology such as 'App Service Plan' instead of 'Windows Plan' unless specifically referring to a Windows-only feature.
- Include Azure CLI examples for resource creation and management, which are cross-platform and can be run on Windows, Linux, or macOS.
- Explicitly mention that App Service supports both Windows and Linux, and guide users to choose the appropriate OS for their workload.
- If possible, provide a tabbed or side-by-side format for Windows and Linux instructions, ensuring parity in the steps and screenshots.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firmware-analysis/quickstart-upload-firmware-using-python.md
...re-analysis/quickstart-upload-firmware-using-python.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation does not show explicit Windows-only commands or tools, but it demonstrates bias by omitting any Linux- or macOS-specific instructions or examples. The only CLI command shown is az login, which is cross-platform, but there are no notes or examples about running the script on Linux or macOS, nor are there any troubleshooting tips or environment setup steps for non-Windows users. The documentation implicitly assumes a Windows environment by not addressing cross-platform concerns.
Recommendations
- Add explicit notes that the instructions and Python script are cross-platform and can be run on Windows, Linux, or macOS.
- Include example terminal commands for both Windows (cmd/PowerShell) and Linux/macOS (bash) where relevant, such as for checking Python version or running the script.
- Mention any OS-specific dependencies or troubleshooting steps (e.g., installing pip or Python on Linux/macOS).
- Clarify that the Azure CLI (az) is available on all major platforms and provide installation links for each.
- Add a section or callout for common issues or differences when running the script on Linux or macOS (e.g., file permissions, Python environment setup).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/create-front-door-terraform.md
...ain//articles/frontdoor/create-front-door-terraform.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation provides a quickstart for creating Azure Front Door using Terraform but exclusively demonstrates the creation of an App Service app using the azurerm_windows_web_app resource. There are no examples or mentions of Linux-based App Service equivalents (e.g., azurerm_linux_web_app), and the only App Service example is Windows-specific. No shell or CLI commands are shown, so there is no explicit PowerShell or Windows command-line bias, but the resource selection itself is Windows-centric.
Recommendations
- Include parallel examples or instructions for creating an App Service app using azurerm_linux_web_app to ensure Linux users are equally supported.
- Explicitly mention that the sample uses a Windows App Service and provide guidance or links for users who wish to deploy a Linux App Service.
- Consider providing a toggle or side-by-side code samples for both Windows and Linux App Service deployments.
- Review referenced sample code and ensure Linux parity is present or clearly linked.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/how-to/assign-configuration/rest-api.md
...-configuration/how-to/assign-configuration/rest-api.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references the Windows PowerShell Get-AzAccessToken cmdlet as the only method for obtaining an Azure access token, without mentioning Linux or cross-platform alternatives. No Linux-specific tools or authentication flows are described, and there are no Linux shell (bash) examples for authentication.
Recommendations
- Include instructions for obtaining an Azure access token using cross-platform tools such as Azure CLI (az account get-access-token), which works on Linux, macOS, and Windows.
- Provide example commands for authentication using bash or zsh shells, not just PowerShell.
- When referencing tools, mention cross-platform options first or alongside Windows-specific tools.
- Explicitly state that cURL examples are cross-platform, and provide any necessary Linux-specific notes (e.g., quoting, line continuation differences).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/origin-authentication-with-managed-identities.md
...tdoor/origin-authentication-with-managed-identities.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page provides only portal-based, GUI instructions and screenshots, which are implicitly Windows-centric due to the Azure Portal's design and typical usage patterns. There are no CLI (az), PowerShell, Bash, or Linux-native instructions or examples. The absence of cross-platform command-line instructions (such as Azure CLI or Bash scripts) means Linux users or those working in headless/server environments are not equally supported. Additionally, the documentation does not mention or prioritize Linux tools or workflows.
Recommendations
- Add equivalent Azure CLI (az) command examples for all major steps, including enabling managed identity, assigning roles, and associating identities with origin groups.
- Include Bash script snippets for automation scenarios, which are common in Linux environments.
- Explicitly mention that all operations can be performed via CLI or REST API, and provide links to relevant documentation.
- If PowerShell examples are added, ensure they are accompanied by Azure CLI/Bash equivalents and presented in parallel, not with Windows-first ordering.
- Add a section or note clarifying cross-platform support and how Linux/macOS users can perform these tasks without the Azure Portal.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/refstring.md
.../azure-docs/blob/main//articles/frontdoor/refstring.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides only a Microsoft Edge (Windows) browser example for capturing the Reference String from HTTP response headers, with no mention of Linux tools or cross-platform alternatives such as curl, wget, or browser-agnostic instructions. This prioritizes Windows tooling and omits guidance for Linux or non-Windows users.
Recommendations
- Add examples for capturing HTTP response headers using command-line tools available on Linux (e.g., curl, wget, httpie).
- Include instructions for using browser developer tools in Chrome and Firefox, which are available on Linux, macOS, and Windows.
- Present cross-platform methods (such as using curl) before or alongside Windows-specific/browser-specific instructions.
- Explicitly mention that the Reference String can be obtained from any browser's developer tools, not just Microsoft Edge.
- Add a section or tab for Linux users to ensure parity and inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/standard-premium/how-to-enable-private-link-apim.md
...or/standard-premium/how-to-enable-private-link-apim.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides three platform pivots: Portal, PowerShell, and CLI. The PowerShell (Windows-centric) section is presented before the CLI (cross-platform) section, and detailed PowerShell examples are given. However, the CLI section is present and provides parity in steps and detail. There are no exclusive Windows tools or missing Linux examples, but the ordering and prominence of PowerShell may suggest a slight Windows-first bias.
Recommendations
- Consider placing the Azure CLI section before the PowerShell section to reflect the CLI's cross-platform nature and reduce perceived Windows-first bias.
- Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and clarify that users can choose either based on their environment.
- Ensure that all examples and instructions are equally detailed in both PowerShell and CLI sections.
- If possible, add a short note at the start of the technical sections highlighting the cross-platform availability of the CLI and PowerShell tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/how-to-enable-private-link-application-gateway.md
...door/how-to-enable-private-link-application-gateway.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents three main pivots: Portal, PowerShell, and Azure CLI. The PowerShell (Windows-centric) section is given equal prominence to the CLI, but is listed before the CLI in the zone_pivot_groups and in the page structure. There are no Linux shell (bash) or cross-platform scripting examples outside of Azure CLI, and PowerShell is emphasized as a primary automation method. There are no explicit Linux-specific instructions or troubleshooting notes, nor are there references to Linux tools or environments.
Recommendations
- Ensure that the Azure CLI section is given equal or higher prominence than PowerShell, as CLI is cross-platform and preferred by many Linux users.
- Add explicit bash shell examples or scripts for common operations, especially for steps that involve string manipulation or resource ID construction.
- Include troubleshooting notes or tips relevant to Linux environments (e.g., file permissions, path differences, CLI installation on Linux).
- Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and provide links to Linux installation guides.
- Where PowerShell is mentioned, note that PowerShell Core is cross-platform, but also provide bash alternatives where possible.
- Consider adding a table or section comparing PowerShell and CLI usage, highlighting cross-platform compatibility.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/frontdoor/troubleshoot-issues.md
...s/blob/main//articles/frontdoor/troubleshoot-issues.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references Windows-specific tools (Fiddler) and omits Linux equivalents in troubleshooting steps. While one example uses OpenSSL (a cross-platform tool), there are no PowerShell or CMD-specific commands, but the mention of Fiddler without alternatives and the lack of Linux/CLI tool suggestions indicate a mild Windows bias.
Recommendations
- When mentioning Fiddler, also suggest Linux/macOS alternatives such as mitmproxy, curl, or Wireshark.
- For browser developer tools, clarify that all major browsers on all platforms provide similar functionality.
- Where command-line examples are given (e.g., using OpenSSL), ensure that instructions are clear for both Windows and Linux users (e.g., note installation methods or path differences if relevant).
- Review all tool recommendations to ensure cross-platform parity, and provide at least one Linux-friendly option for each troubleshooting step involving external tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/blueprints/concepts/sequencing-order.md
...les/governance/blueprints/concepts/sequencing-order.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by referencing PowerShell as the only CLI tool for creating blueprint artifacts, without mentioning cross-platform or Linux-native alternatives such as Azure CLI. The only command-line example provided is a PowerShell cmdlet, and there is no mention of Linux shell usage or parity in tooling.
Recommendations
- Include Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that both PowerShell and Azure CLI can be used to manage Azure Blueprints, and provide links to relevant documentation for both.
- Wherever a PowerShell cmdlet is referenced, provide the equivalent Azure CLI command (if available) or note any limitations.
- Avoid implying that PowerShell is the default or only way to interact with Azure Blueprints from the command line.
- Add a note clarifying that all JSON and REST API examples are platform-agnostic, and that users on Linux, macOS, and Windows have equivalent capabilities.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/blueprints/samples/azure-security-benchmark-foundation/deploy.md
.../samples/azure-security-benchmark-foundation/deploy.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation contains a single command-line example for listing available Log Analytics workspace regions, provided only in Azure PowerShell syntax. There are no equivalent examples or instructions for Bash, Azure CLI, or Linux environments. The rest of the documentation is GUI-focused and platform-neutral, but the only command-line guidance is Windows/Powershell-specific.
Recommendations
- Provide equivalent Azure CLI (az) examples alongside PowerShell commands, especially for tasks like listing available regions.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide syntax for both PowerShell and Bash where relevant.
- When referencing command-line operations, offer both PowerShell and Bash/Azure CLI snippets to ensure parity for Linux users.
- Review other documentation pages linked from this one to ensure they also provide cross-platform examples where command-line usage is discussed.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/how-to/assign-configuration/bicep.md
...ine-configuration/how-to/assign-configuration/bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides examples for creating machine configuration assignments using Bicep, but all concrete examples reference Windows virtual machines and Windows-specific built-in configurations (e.g., 'AzureWindowsBaseline'). There are no examples or references for Linux VMs or Linux-specific configurations, and the only built-in configuration shown is Windows-focused. This demonstrates a 'windows_first' approach and a lack of Linux parity in the examples.
Recommendations
- Add equivalent examples for Linux virtual machines, including how to assign configurations to Linux VMs using Bicep.
- Include at least one built-in configuration example for Linux (e.g., 'AzureLinuxBaseline') to demonstrate parity.
- When discussing built-in configurations, mention both Windows and Linux options, or provide a table of available configurations for both OS types.
- Ensure that the documentation makes it clear that both Windows and Linux machines are supported, and provide guidance or links for Linux-specific scenarios.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/machine-configuration/whats-new/agent.md
...es/governance/machine-configuration/whats-new/agent.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Windows and Linux release notes in parallel, but there is a subtle Windows bias. PowerShell is referenced as a primary tool for both platforms, and in the example for updating the Linux extension, the PowerShell example is given before the Azure CLI example. There are no Linux shell (bash) examples, and PowerShell is positioned as the default scripting language, even for Linux scenarios.
Recommendations
- Provide bash or native Linux shell command examples alongside or before PowerShell examples for Linux extension management.
- When presenting cross-platform instructions, alternate the order in which Windows and Linux examples are shown, or present them side-by-side.
- Clarify that PowerShell is optional on Linux and provide guidance for users who prefer native Linux tools.
- Review the documentation for other areas where Windows tools or patterns are presented as the default for Linux users, and add Linux-native alternatives where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/concepts/definition-structure-parameters.md
...nce/policy/concepts/definition-structure-parameters.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references the Windows PowerShell cmdlet 'Get-AzResourceProvider' as the method to determine valid resource types for the 'strongType' property, without mentioning an equivalent Azure CLI or REST API approach. This centers Windows/PowerShell tooling and patterns, potentially disadvantaging Linux or cross-platform users. No Linux-specific or cross-platform examples or tools are provided.
Recommendations
- Include Azure CLI equivalents (e.g., 'az provider show' or 'az provider list') alongside PowerShell cmdlets when describing how to discover resource types.
- Mention REST API alternatives for determining resource provider information, which are platform-agnostic.
- Avoid referencing only Windows/PowerShell tooling; always provide cross-platform options first or in parallel.
- Consider adding a note that both PowerShell and CLI/REST approaches are supported, with links to relevant documentation for each.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/management-groups/manage.md
.../main//articles/governance/management-groups/manage.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all management group operations, ensuring cross-platform command-line parity. However, PowerShell examples are consistently presented before Azure CLI examples, and some example outputs (such as object inspection) use Windows/PowerShell-specific conventions (e.g., PS C:\> prompt, object property navigation), which may be less familiar to Linux/macOS users. There are no explicit Linux-only tools or shell examples, and no mention of Bash scripting or Linux shell environments.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present them side-by-side, to avoid implying PowerShell is primary.
- Where example outputs are shown, provide equivalent Azure CLI output or note differences in output formatting between PowerShell and CLI.
- Include brief notes clarifying that both Azure PowerShell and Azure CLI are cross-platform and can be used on Windows, Linux, and macOS.
- Add links or references to Bash scripting or Linux shell usage where appropriate, especially for users automating with the Azure CLI.
- Avoid using Windows-specific prompts (e.g., PS C:\>) in example outputs unless necessary; if shown, provide equivalent CLI output for parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/concepts/initiative-definition-structure.md
...nce/policy/concepts/initiative-definition-structure.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation contains a reference to the Windows PowerShell cmdlet Get-AzResourceProvider as the only method for determining valid strongType resource types. There are no equivalent Linux/CLI/bash examples or references, and no mention of cross-platform tools before or alongside the PowerShell example.
Recommendations
- Provide Azure CLI equivalents for all PowerShell cmdlets mentioned (e.g., show how to use 'az provider show' or 'az provider list' to determine resource types for strongType).
- When referencing tools or commands, mention cross-platform options (such as Azure CLI) before or alongside Windows-specific tools like PowerShell.
- Include explicit examples or links for both Windows (PowerShell) and Linux/macOS (CLI/bash) users to ensure parity.
- Audit the documentation for other areas where only Windows tooling or patterns are referenced, and supplement with cross-platform alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/samples/pci-dss-3-2-1.md
...n//articles/governance/policy/samples/pci-dss-3-2-1.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page is generally neutral and focused on Azure Policy compliance mappings, but there is a notable Windows bias in the sections related to password policies and guest configuration. Multiple policies specifically target 'Windows machines' (e.g., password age, password length, password reuse), and there are policies for deploying the Windows Guest Configuration extension. There are no equivalent policies or examples for Linux machines, nor is there mention of how to achieve similar compliance for Linux VMs. This creates a gap for Linux users seeking parity in compliance monitoring and enforcement.
Recommendations
- Add equivalent Linux policies and controls for password management (e.g., minimum password length, password age, password reuse) and guest configuration.
- Include explicit mention of Linux support or limitations where only Windows is supported, so users are aware of platform gaps.
- Provide links or references to Linux guest configuration extensions and how to deploy them, if available.
- Where policies are Windows-specific, offer guidance or alternatives for Linux environments, or clarify if such policies are not currently available.
- Ensure future updates include parity for Linux VMs in compliance initiatives, especially for common controls like password policies and configuration management.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/governance/policy/samples/gov-cmmc-l3.md
...ain//articles/governance/policy/samples/gov-cmmc-l3.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation is largely platform-neutral, focusing on Azure Policy definitions and compliance mappings. However, there is evidence of Windows bias in the security tooling recommendations: several policies specifically reference Windows-only tools or extensions (e.g., Microsoft Antimalware for Azure, Microsoft IaaSAntimalware extension for Windows servers), and there are no equivalent Linux security tooling examples or explicit parity statements. No PowerShell-heavy or Windows-first command examples are present, but the lack of Linux-specific guidance or mention of Linux alternatives for antimalware/monitoring is a notable omission.
Recommendations
- Where Windows-specific security tools (e.g., Microsoft Antimalware, IaaSAntimalware extension) are referenced, add equivalent Linux guidance or explicitly state Linux alternatives (such as supported Linux antimalware agents or monitoring solutions).
- For each policy or extension that is Windows-only, clarify its platform scope and provide links to Linux documentation or recommended practices where available.
- Consider including a summary table or section listing both Windows and Linux supported security agents/extensions for common compliance controls.
- Review for other areas where only Windows-specific features are mentioned and ensure Linux parity or clear documentation of platform differences.