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 1951-1975 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-overview.md
...ticles/databox-online/azure-stack-edge-gpu-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page references BitLocker for encryption, which is a Windows-specific technology, without mentioning Linux alternatives. There are no explicit examples or instructions for Linux users, nor is there mention of Linux-native encryption or management tools. The documentation does not provide parity in tool references or examples for Linux environments.
Recommendations
- When mentioning BitLocker for encryption, also reference Linux-compatible encryption solutions (e.g., LUKS/dm-crypt) if supported, or clarify if only BitLocker is available.
- Include examples or notes on how Linux users can interact with the device, especially for common tasks like mounting SMB/NFS shares, managing encryption, or accessing the local web UI.
- If management or diagnostics tools are Windows-specific, provide Linux alternatives or clarify cross-platform compatibility.
- Ensure that protocol and tooling documentation (e.g., for file transfer, device management) includes both Windows and Linux workflows where applicable.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/authenticate-application.md
.../main//articles/event-hubs/authenticate-application.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing the Azure portal and .NET samples first, and by not providing explicit Linux or cross-platform command-line examples for authentication or role assignment. While Azure CLI is mentioned in the related content, the main body of the documentation and code samples focus on .NET and Java, with no explicit Linux shell or cross-platform scripting examples. There are no PowerShell-heavy sections, but the absence of Linux-specific guidance or parity in examples is notable.
Recommendations
- Include explicit Linux and cross-platform examples for authentication and role assignment, such as using Azure CLI commands in the main documentation body.
- Provide sample code and walkthroughs using Python or Node.js SDKs, which are popular on Linux, alongside .NET and Java.
- When referencing the Azure portal, also mention that the steps are applicable regardless of OS, and provide CLI alternatives for all portal actions.
- Add a section or callout that demonstrates how to perform all steps (registration, secret creation, role assignment, token acquisition) using only command-line tools available on Linux.
- Ensure that links to Azure CLI documentation are as prominent as those for PowerShell and the Azure portal.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/authenticate-managed-identity.md
...//articles/event-hubs/authenticate-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by linking to instructions for enabling managed identities specifically on Windows VMs and omitting equivalent Linux VM instructions. There are no Linux-specific examples or guidance for enabling managed identities or deploying sample applications on Linux-based environments. The sample application and code are .NET/C# focused, which is more common in Windows environments, and there is no parity in showing how to perform the same tasks on Linux VMs or with Linux-centric tools.
Recommendations
- Add parallel instructions and links for enabling managed identities on Linux VMs, such as linking to 'Configure managed identities on Azure VMs (Linux)' documentation.
- Include Linux-based sample application deployment steps, or at least mention that the process is similar for Linux App Service or containerized workloads.
- Provide code samples or references for other common Linux-friendly languages (e.g., Python) and frameworks.
- When referencing enabling managed identities, present both Windows and Linux options together, or in a neutral order, to avoid a Windows-first impression.
- Clarify that managed identities and authentication flows are supported equally on Linux and Windows, and provide explicit guidance for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/apache-kafka-migration-guide.md
...n//articles/event-hubs/apache-kafka-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Azure portal workflows and connection string formats that are more familiar to Windows users. There are no explicit Linux or cross-platform command-line examples (e.g., using Azure CLI, Bash, or Linux tools), nor is there guidance for Linux users on verifying Event Hub messages outside the Azure portal. The documentation assumes use of the Azure portal for verification, which may be less common in Linux-centric workflows.
Recommendations
- Add equivalent Linux-friendly instructions for verifying Event Hub messages, such as using Azure CLI or command-line tools (e.g., az eventhubs eventhub show or similar commands).
- Provide cross-platform examples for obtaining connection strings and FQDNs, including CLI and scripting options for Linux users.
- Explicitly mention that the configuration steps apply equally to Linux and Windows environments, and include sample commands or scripts for both platforms where relevant.
- Include screenshots or walkthroughs for both the Azure portal and command-line alternatives to ensure parity for users who prefer not to use a GUI.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-dedicated-overview.md
...//articles/event-hubs/event-hubs-dedicated-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias by referencing the 'nslookup' command with a Windows-centric example (using a .windows.net namespace) and mentioning PowerShell as an option for checking Azure Resource Manager properties, with no explicit mention of Linux equivalents or cross-platform alternatives. The documentation also refers to the Azure portal and ARM templates, which are cross-platform, but in the context of command-line tools, Windows tools are mentioned first or exclusively.
Recommendations
- When referencing command-line tools like 'nslookup', clarify that it is available on both Windows and Linux, and provide example commands for both platforms.
- When suggesting the use of PowerShell, also mention Azure CLI as a cross-platform alternative, and provide equivalent commands.
- Avoid using Windows-specific namespaces (e.g., .windows.net) in examples unless necessary, or provide Linux/neutral examples as well.
- Explicitly state when a tool or method is cross-platform, and provide instructions or examples for both Windows and Linux environments where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-management-libraries.md
...articles/event-hubs/event-hubs-management-libraries.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation is focused exclusively on .NET (C#) and does not provide any Linux-specific or cross-platform code samples. While it mentions Azure CLI (which is cross-platform) as one way to create a service principal, the primary sample code and all references are for .NET, which is more commonly associated with Windows environments. There are no examples for Linux-native languages or tools (such as Python, Java, or Bash), nor is there mention of running the sample code on Linux or in a cross-platform way.
Recommendations
- Add equivalent sample code in at least one Linux-native language (e.g., Python or Java) using the respective Azure SDKs.
- Explicitly mention that the .NET SDK and sample code can be run on Linux (using .NET Core/5/6+), and provide instructions or notes for doing so.
- Include Bash or Azure CLI script examples for common management tasks, such as creating namespaces or event hubs, to demonstrate cross-platform command-line usage.
- Balance the order of tool references: when listing ways to create a service principal, do not mention PowerShell before Azure CLI, or alternate the order to avoid Windows-first perception.
- Provide links to documentation or samples for other languages/platforms (e.g., Python, Java, JavaScript) if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-messaging-exceptions.md
...articles/event-hubs/event-hubs-messaging-exceptions.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation is focused exclusively on .NET APIs and exception types, which are most commonly used in Windows environments. There are no examples, troubleshooting steps, or references for Linux or cross-platform usage, nor are there mentions of equivalent patterns or tools for Linux users. All exception references are to .NET/Windows-centric libraries, and there is no guidance for users working with Event Hubs from Linux or non-.NET stacks.
Recommendations
- Add equivalent exception documentation for other supported SDKs/platforms (e.g., Java, Python, Node.js), which are commonly used on Linux.
- Include troubleshooting steps and examples that are relevant for Linux environments, such as using CLI tools (Azure CLI, Bash scripts) instead of only .NET APIs.
- Where configuration or monitoring is discussed (e.g., checking metrics, scaling), provide instructions for both Azure Portal (GUI) and command-line tools (Azure CLI, PowerShell), and ensure Linux-friendly CLI examples are present.
- Explicitly mention cross-platform support and link to documentation for other operating systems and languages.
- If .NET is required, clarify that .NET Core/.NET 5+ is cross-platform and provide Linux installation and usage notes where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-java-get-started-send.md
...rticles/event-hubs/event-hubs-java-get-started-send.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates a mild Windows bias. While the Java code and Azure concepts are cross-platform, the only terminal output examples use Windows command prompt syntax (e.g., 'cmd' code blocks, 'Press enter to stop.'), and there is no mention of Linux or macOS environments, shells, or equivalent instructions. The Azure portal and tools referenced are cross-platform, but the lack of explicit Linux/macOS parity in terminal instructions and output is a subtle form of Windows-first bias.
Recommendations
- Include terminal output examples for both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh), or use generic shell output where possible.
- When instructing users to 'Press enter to stop,' clarify that this applies to all platforms, or provide equivalent instructions for Linux/macOS terminals.
- If using code blocks for terminal output, use a neutral language (e.g., 'console' or 'shell') instead of 'cmd' unless the example is truly Windows-specific.
- Explicitly state that the Java code and instructions are cross-platform, and provide any necessary notes for Linux/macOS users (e.g., how to run the Java application from a bash shell).
- Where tools or UI steps are mentioned (e.g., Azure portal), confirm that they are accessible from all major platforms, or provide alternatives if not.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-quickstart-stream-large-messages.md
...nt-hubs/event-hubs-quickstart-stream-large-messages.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by referencing the Azure portal and .NET SDKs (which are traditionally Windows-centric) without mentioning or providing parity for Linux tools, command-line interfaces, or SDKs commonly used on Linux. There are no examples or references for Linux users, such as using Azure CLI, Bash, or Python SDKs, and the only code reference is for .NET, which is often associated with Windows development.
Recommendations
- Include examples using cross-platform tools such as Azure CLI or Azure PowerShell (with explicit mention of Linux compatibility).
- Provide code samples or references for SDKs popular on Linux, such as Python, Java, or Node.js, alongside .NET.
- Mention and link to documentation for using Event Hubs from Linux environments, including relevant setup instructions.
- Clarify that the Azure portal and SDKs are accessible from any OS, and provide explicit instructions for Linux users where workflows may differ.
- Add a section or note highlighting Linux compatibility and any OS-specific considerations for configuring or using Event Hubs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-quickstart-kafka-enabled-event-hubs.md
...hubs/event-hubs-quickstart-kafka-enabled-event-hubs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exhibits a Windows bias by instructing users to create a Windows virtual machine as a prerequisite and only providing guidance and links for configuring managed identity on a Windows VM. There are no instructions or examples for Linux-based environments, nor are there alternative setup steps for non-Windows users. All screenshots and portal instructions are Windows-centric, and there is no mention of Linux equivalents or cross-platform considerations.
Recommendations
- Provide parallel instructions for setting up both Windows and Linux virtual machines, including links to relevant Azure documentation for Linux VMs.
- Include guidance and examples for configuring managed identities and running the Kafka producer/consumer on Linux VMs.
- Add notes or sections that clarify cross-platform compatibility, and ensure that all command-line instructions are platform-agnostic (or provide both Windows and Linux shell examples where differences exist).
- Update the prerequisites section to mention that either Windows or Linux VMs can be used, and provide installation steps for Java, Maven, and Git on both platforms.
- Where screenshots are used, consider including Linux terminal or Azure Portal views from a Linux VM context.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/includes/event-hubs-connectivity.md
...rticles/event-hubs/includes/event-hubs-connectivity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides command-line instructions exclusively using Windows tools (nslookup from 'command prompt') and does not mention or provide examples for Linux or macOS users. There are no PowerShell-specific commands, but the guidance assumes a Windows environment by default and omits equivalent Linux/macOS instructions.
Recommendations
- Include Linux/macOS equivalents for command-line instructions (e.g., specify 'open a terminal and run nslookup ...' or provide both Windows Command Prompt and Bash syntax).
- Explicitly mention that the nslookup command works on Windows, Linux, and macOS, and provide context for users on each platform.
- Wherever 'command prompt' is referenced, clarify with 'command prompt or terminal' to be inclusive of non-Windows environments.
- If any troubleshooting steps require platform-specific tools, provide alternatives for Linux/macOS (e.g., dig, host) alongside Windows tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/bgp-communities.md
...cs/blob/main//articles/expressroute/bgp-communities.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation does not provide any platform-specific configuration examples, but the only 'Next steps' link refers to configuring BGP communities using the Azure portal, a graphical tool more commonly associated with Windows workflows. There are no command-line examples (neither PowerShell nor CLI), but the absence of Linux CLI or cross-platform instructions means Linux users may not have clear guidance. The documentation implicitly favors Windows/portal-based management patterns.
Recommendations
- Add step-by-step instructions for configuring BGP communities using Azure CLI, which is cross-platform and widely used on Linux.
- Include sample scripts or commands for both PowerShell and Bash (Azure CLI) to ensure parity.
- Explicitly mention that the Azure portal is accessible from any OS, but also provide alternatives for users who prefer or require command-line automation.
- Link to documentation for both Azure PowerShell and Azure CLI configuration of BGP communities, if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/sdks.md
...Docs/azure-docs/blob/main//articles/event-hubs/sdks.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by listing .NET (a Microsoft-centric and historically Windows-first technology) SDKs and packages at the top of all tables and providing a dedicated section for .NET packages, including references to the Windows-only .NET Framework and the legacy WindowsAzure.ServiceBus library. There are no explicit Linux or cross-platform command-line examples, and Windows-specific terminology (such as .NET Framework and WindowsAzure) is used without equivalent Linux/Unix context.
Recommendations
- Reorder SDK tables to avoid always listing .NET/.NET Standard first; consider alphabetical order or rotating the order in different sections.
- Add a section or callout highlighting cross-platform compatibility for all SDKs, especially clarifying which libraries are fully cross-platform.
- Where Windows-specific libraries (e.g., WindowsAzure.ServiceBus) are mentioned, explicitly note their platform limitations and suggest alternatives for Linux users.
- Include examples or references to using the SDKs on Linux/macOS, such as installation instructions or sample commands for those platforms.
- Balance the depth of .NET-specific sections with equivalent detail for Java, Python, and other cross-platform SDKs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-qos.md
...s/blob/main//articles/expressroute/expressroute-qos.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by linking only to guidance for configuring QoS policies on Windows 10 clients, with no mention of Linux or cross-platform configuration methods. There are no examples or references for Linux-based QoS configuration, nor are any Linux tools or commands discussed.
Recommendations
- Include references or links to documentation on configuring DSCP markings and QoS policies on Linux clients (e.g., using 'tc', 'iptables', or 'firewalld').
- Provide example commands or configuration snippets for both Windows and Linux platforms.
- Explicitly mention that QoS configuration is required on all client platforms, and provide parity in guidance for non-Windows environments.
- Where possible, link to official Microsoft or community documentation for Linux-based Skype for Business/Teams clients regarding QoS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/quickstart-create-expressroute-vnet-bicep.md
...ressroute/quickstart-create-expressroute-vnet-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, validation, and cleanup steps. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented in parallel tabs throughout. There is no explicit mention of Linux or Bash shell usage, and no examples using native Linux tools or shell patterns. The documentation does not clarify that Azure CLI is cross-platform or provide any Linux-specific guidance, which may implicitly bias the page toward Windows users.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and are recommended for cross-platform use.
- Consider presenting Azure CLI examples first, as it is the most platform-agnostic tool.
- Add a note or section for Linux/macOS users, clarifying that PowerShell is optional and not required.
- If relevant, provide Bash shell script examples or mention that the CLI commands can be run in Bash.
- Review the language to ensure it does not assume a Windows environment or tools by default.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/cross-connections-api-development.md
...cles/expressroute/cross-connections-api-development.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation includes command-line examples that reference Windows file paths (e.g., C:\Users\Admin\Documents...) and the use of ARMClient, but does not provide equivalent examples or guidance for Linux or macOS users. There are no PowerShell-specific commands, but the exclusive use of Windows-style paths and lack of cross-platform CLI instructions indicates a Windows bias.
Recommendations
- Provide equivalent command-line examples using Linux/macOS file paths (e.g., /home/user/Documents/...) alongside Windows examples.
- Clarify whether ARMClient is available and supported on Linux/macOS, and provide installation/use instructions for those platforms if applicable.
- Include Azure CLI examples, which are cross-platform, for authentication and API calls where possible.
- Avoid using only Windows-style paths in documentation; use environment-agnostic placeholders or show both Windows and Unix-style paths.
- Explicitly mention that the APIs and tools can be used from any OS, and link to relevant cross-platform tool documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/rate-limit.md
...re-docs/blob/main//articles/expressroute/rate-limit.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation exclusively describes configuration via the Azure Portal (web UI) and does not provide any command-line examples. There are no references to Windows-specific tools like PowerShell or Windows-only patterns, but the lack of CLI examples (such as Azure CLI or Azure PowerShell) means that Linux users do not see parity in instructions. The documentation implicitly assumes a GUI-first workflow, which is more common in Windows environments, and does not mention or prioritize cross-platform command-line alternatives.
Recommendations
- Add Azure CLI examples for enabling/disabling rate limiting, as Azure CLI is cross-platform and widely used on Linux.
- If applicable, provide Azure PowerShell examples, but ensure Azure CLI examples are given equal or higher prominence.
- Explicitly mention that all steps can be performed via the Azure CLI or PowerShell, and provide links to relevant command reference documentation.
- Include a section or callout for users who prefer automation or non-GUI workflows, outlining how to perform these tasks from the command line.
- Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid referencing Windows-only UI elements or terminology).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/external-attack-surface-management/understanding-dashboards.md
...-attack-surface-management/understanding-dashboards.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page for Microsoft Defender EASM dashboards demonstrates a mild Windows bias. The only explicit tool mentioned for working with exported CSV data is Microsoft Excel, and its limitations are discussed in detail, with only a generic suggestion to 'try opening the file in another program' if issues arise. No Linux-specific tools or workflows are mentioned, and the only example of a third-party tool is a Microsoft product. There are no command-line examples, scripts, or references to PowerShell, Bash, or OS-specific procedures, but the documentation assumes familiarity with Microsoft-centric environments and tools.
Recommendations
- When discussing CSV exports, mention popular Linux-compatible tools (e.g., LibreOffice Calc, csvkit, or command-line utilities like awk/cut) alongside Microsoft Excel.
- Provide explicit guidance or examples for opening and manipulating CSV files on Linux and macOS, not just Windows.
- If discussing limitations of Microsoft Excel, also mention any known limitations or advantages of common Linux tools.
- Wherever possible, avoid assuming the user is on Windows; use neutral language and include cross-platform tool recommendations.
- If screenshots or UI references are OS-specific, clarify if the experience is the same across platforms or note any differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/deploy-bicep.md
...zure-docs/blob/main//articles/firewall/deploy-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively deploys Windows Server virtual machines in its example environment and does not mention or provide options for Linux VMs. All VM-related instructions and context are Windows-centric, and there is no discussion of Linux alternatives or parity.
Recommendations
- Include examples and instructions for deploying Linux virtual machines alongside or instead of Windows Server VMs in the Bicep template.
- Explicitly mention that either Windows or Linux VMs can be used, and provide parameterization or guidance for both OS types.
- In the description and walkthrough, refer to 'virtual machines' generically or clarify that both Windows and Linux are supported.
- If scripts or commands are OS-specific, provide Linux/SSH examples and not just Windows/PowerShell ones.
- Consider adding a section or note on how to adapt the template for Linux VM deployment, including adminUsername/adminPassword vs. SSH key authentication.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall-manager/quick-secure-virtual-hub-terraform.md
...firewall-manager/quick-secure-virtual-hub-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes deploying and testing with Windows Server 2019 virtual machines, with no mention of Linux VM options or examples. The test scenario assumes Windows environments, and there are no instructions or guidance for Linux users.
Recommendations
- Include parallel instructions and Terraform code samples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine).
- Describe how to test firewall rules from a Linux VM, including example commands (e.g., using curl or wget).
- Explicitly mention that the scenario works with both Windows and Linux VMs, and provide guidance for both.
- If jump server and workload server roles are described, show how to implement these with Linux as well as Windows.
- Ensure that troubleshooting and cleanup steps are not OS-specific, or provide both Windows and Linux variants where necessary.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall-manager/secure-cloud-network.md
...ain//articles/firewall-manager/secure-cloud-network.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The tutorial exclusively uses Windows Server for VM deployment and only demonstrates testing via Remote Desktop Protocol (RDP) and Internet Explorer, with no mention of Linux-based alternatives or SSH-based access. This creates a Windows-centric experience and omits guidance for users deploying Linux servers or using Linux-native tools.
Recommendations
- Include parallel instructions for deploying a Linux VM (e.g., Ubuntu) alongside the Windows Server example, including relevant configuration steps.
- Provide examples for connecting to Linux VMs using SSH, and for testing firewall rules with Linux-native browsers (e.g., Firefox, Chromium) or command-line tools (e.g., curl, wget).
- When demonstrating firewall rules, add examples for Linux protocols and ports (e.g., SSH on port 22) and show how to test connectivity from a Linux VM.
- In testing sections, offer both RDP (Windows) and SSH (Linux) scenarios, and avoid assuming the use of Internet Explorer or other Windows-only tools.
- Use neutral language when referring to operating systems, and avoid defaulting to Windows unless the feature is Windows-specific.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/deploy-firewall-basic-portal-policy.md
...ticles/firewall/deploy-firewall-basic-portal-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses Windows Server as the example operating system for the workload VM, and all testing instructions (such as RDP and Internet Explorer) are Windows-specific. There are no Linux VM deployment instructions or Linux-based test scenarios, and the only alternative mentioned is Azure PowerShell, which is also Windows-centric. No Linux tools or patterns are referenced.
Recommendations
- Add parallel instructions for deploying a Linux-based workload VM (e.g., Ubuntu or CentOS) alongside the Windows example.
- Include Linux-specific testing steps, such as connecting via SSH and using curl or wget to test outbound access, and using dig or nslookup for DNS testing.
- Mention both RDP (for Windows) and SSH (for Linux) as remote access methods in the DNAT rule section.
- Reference Azure CLI as an alternative to Azure PowerShell for command-line automation, and provide links or examples.
- Ensure that screenshots or UI steps are not OS-specific where possible, or provide both Windows and Linux perspectives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/deploy-terraform.md
...-docs/blob/main//articles/firewall/deploy-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively deploys Windows Server virtual machines in the example environment and does not mention or provide guidance for deploying Linux VMs. All VM-related steps and resources are focused on Windows, with no Linux equivalents or parity. There are no explicit PowerShell or Windows tool commands, but the bias is present in the infrastructure choices and lack of Linux representation.
Recommendations
- Include parallel instructions and Terraform resource examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine) alongside or as alternatives to the Windows VM steps.
- Mention both Windows and Linux VM options in the scenario description and checklist, making it clear that either can be used.
- Provide example Terraform code snippets for both Windows and Linux VM creation, or show how to parameterize the OS type.
- If possible, add a section or note on how to adapt the sample to deploy Linux VMs, including any differences in configuration (e.g., SSH keys vs. passwords).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/fqdn-tags.md
...s/azure-docs/blob/main//articles/firewall/fqdn-tags.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Summary
The documentation page demonstrates a Windows-centric bias by focusing primarily on FQDN tags related to Windows and Microsoft services, such as WindowsUpdate, WindowsDiagnostics, WindowsVirtualDesktop, Windows365, and CitrixHdxPlusForWindows365. The majority of examples and tag descriptions are tailored to Windows or Microsoft-specific products, with little to no mention of Linux-specific services, tools, or use cases. There are no Linux-oriented examples, tags, or references, and the documentation implicitly assumes a Windows-centric environment.
Recommendations
- Include examples or references to FQDN tags that are relevant to Linux-based services or workloads (e.g., popular Linux distributions' update servers, Linux-based management or monitoring services).
- Provide guidance or examples for scenarios where Linux VMs or services are protected by Azure Firewall, such as allowing outbound access for package repositories (apt, yum, etc.).
- Balance the documentation by mentioning both Windows and Linux use cases where appropriate, especially in examples and tag descriptions.
- If FQDN tags for Linux services are not currently available, explicitly state this and provide alternative guidance for Linux administrators.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/idps-signature-categories.md
...b/main//articles/firewall/idps-signature-categories.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias. Several categories (e.g., ActiveX, Exploit, Web Server) reference Microsoft/Windows-specific technologies or tools (such as Microsoft ActiveX, Microsoft Windows, and Microsoft IIS) before or alongside their cross-platform or Linux equivalents. However, the page does mention non-Windows technologies (e.g., Apache, NGINX, CURL, WGET) and does not provide command-line examples or instructions that are Windows-specific. There are no PowerShell-heavy sections or missing Linux examples, but the ordering and emphasis sometimes place Windows technologies first.
Recommendations
- When listing technologies or software (e.g., in the Web Server category), alternate the order or list Linux/open-source options first to avoid implicit prioritization of Windows technologies.
- For categories referencing Windows-specific technologies (e.g., ActiveX, Microsoft Windows exploits), ensure similar attention is given to Linux/macOS equivalents where relevant (e.g., mention Linux-specific vulnerabilities or controls).
- Where possible, provide balanced context or examples that include both Windows and Linux/Unix tools, especially in sections discussing exploits or server software.
- Review category descriptions for implicit prioritization and rephrase to present a more platform-neutral perspective.