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 2151-2175 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/energy-data-services/tutorial-manifest-ingestion.md
...es/energy-data-services/tutorial-manifest-ingestion.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses Postman (a cross-platform GUI tool) for all examples and instructions, without providing any command-line alternatives (such as curl or HTTPie) that are commonly used on Linux systems. There are no explicit Windows-only tools or patterns, but the lack of CLI examples may disadvantage Linux users who prefer or require terminal-based workflows.
Recommendations
- Provide equivalent command-line examples using curl or HTTPie for each API interaction, alongside the Postman instructions.
- Explicitly mention that Postman is available on Windows, macOS, and Linux to reassure users of cross-platform support.
- Include a section or appendix on how to perform the same manifest ingestion tasks using shell scripts or CLI tools, which are popular in Linux environments.
- If any screenshots or instructions are OS-specific, clarify or provide alternatives for Linux users.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/waf-app-gateway.md
.../blob/main//articles/container-apps/waf-app-gateway.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses Azure Portal (GUI) instructions and does not provide any command-line examples for either Windows (PowerShell/CLI) or Linux (Bash/CLI). However, this omission results in a bias of missing Linux parity, as many cross-platform users expect CLI (az CLI, Bash) instructions, especially for automation or Linux-first workflows. No Windows-specific tools or patterns are present, but the lack of CLI coverage is a form of implicit bias.
Recommendations
- Add Azure CLI (az) command examples for all major steps, such as creating DNS zones, Application Gateway, backend pools, and configuring WAF. These CLI examples should be written in a cross-platform way (Bash syntax) to ensure Linux and macOS users are supported.
- Where possible, provide both Portal and CLI instructions side-by-side or in tabs, so users can choose their preferred workflow.
- Explicitly mention that all steps can be performed via CLI and link to relevant CLI documentation.
- If PowerShell is to be included, ensure Bash/az CLI equivalents are always present and not secondary.
- Highlight any steps that are only possible via the Portal, and provide workarounds or alternatives for CLI users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/costs/cost-allocation-introduction.md
...nagement-billing/costs/cost-allocation-introduction.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions the Azure portal, PowerShell, CLI, and REST API as management interfaces for subscriptions and resource groups. However, in both cases, 'PowerShell' is listed before 'CLI', which may subtly prioritize Windows-centric tooling over cross-platform or Linux-native options. No explicit Linux-only examples or tools are missing, but the ordering could suggest a Windows-first perspective.
Recommendations
- List CLI before PowerShell when describing cross-platform management options, as Azure CLI is available on Windows, Linux, and macOS, while PowerShell is more strongly associated with Windows.
- Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Where possible, provide example commands for both PowerShell and Azure CLI, or at least ensure that CLI examples are as prominent as PowerShell ones.
- Consider adding a short note or table summarizing which tools are available on which platforms to reinforce parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/transport-layer-security-enforce-minimum-version.md
...id/transport-layer-security-enforce-minimum-version.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also does not include any command-line examples or tooling references at all (Windows or Linux). However, the absence of any examples means there is a missed opportunity to demonstrate parity between Windows (e.g., PowerShell, Azure CLI on Windows) and Linux (e.g., Bash, Azure CLI on Linux). This could be considered a 'missing_linux_example' bias, as Linux users are not explicitly supported or acknowledged.
Recommendations
- Add explicit examples using cross-platform tools such as Azure CLI, showing how to set the MinimumTlsVersion property from both Windows (PowerShell or CMD) and Linux (Bash).
- If scripting examples are added, ensure both PowerShell and Bash versions are provided, or use Azure CLI commands that work identically on both platforms.
- Mention that Azure CLI and Azure PowerShell are available on both Windows and Linux, and provide guidance for both environments.
- Include troubleshooting tips or notes relevant to both Windows and Linux clients when connecting to Event Grid with specific TLS versions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/configure-firewall-namespaces.md
...//articles/event-grid/configure-firewall-namespaces.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page exclusively describes configuring IP firewall settings for Azure Event Grid namespaces using the Azure Portal UI, with no command-line examples provided. There is no mention of Windows-specific tools, but there is also a lack of parity for Linux users as no CLI (Azure CLI, Bash) or PowerShell examples are given. This omission may disadvantage users who prefer or require command-line or automation approaches, particularly those on Linux or macOS.
Recommendations
- Add Azure CLI examples for configuring IP firewall settings, as the CLI is cross-platform and widely used on Linux.
- If relevant, provide Bash script examples for automating firewall configuration.
- If PowerShell examples are added, ensure they are accompanied by equivalent Azure CLI or Bash examples to maintain platform neutrality.
- Explicitly mention that the Azure Portal is accessible from any OS, but highlight command-line alternatives for automation and scripting needs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/understand/review-customer-agreement-bill.md
...t-billing/understand/review-customer-agreement-bill.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes how to review billing and usage information using the Azure Portal web interface. There are no command-line examples, scripts, or tool references for any platform (Windows, Linux, or macOS). However, there is an implicit bias in that no mention is made of CLI-based workflows (such as Azure CLI or PowerShell), which are commonly used on Linux and cross-platform environments. This omission may disadvantage Linux users who prefer or require non-GUI, scriptable solutions.
Recommendations
- Add examples for reviewing billing and usage information using the Azure CLI, which is cross-platform and widely used on Linux.
- If PowerShell examples are added, ensure equivalent Azure CLI examples are provided and presented with equal prominence.
- Mention and link to documentation for programmatic access to billing data (e.g., using REST APIs or SDKs), which are platform-agnostic.
- Explicitly state that the Azure Portal is web-based and accessible from any OS, but also provide alternative workflows for users who prefer command-line or automated solutions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/configure-private-endpoints-pull.md
...rticles/event-grid/configure-private-endpoints-pull.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes how to configure private endpoints for Azure Event Grid namespaces using the Azure Portal GUI, with no command-line examples or references to OS-specific tools. There are no explicit Windows or PowerShell examples, but the lack of CLI (az CLI, Bash, or PowerShell) instructions means Linux users are not provided with parity for automation or terminal-based workflows.
Recommendations
- Add equivalent instructions for configuring private endpoints using the Azure CLI (az), which is cross-platform and commonly used on Linux.
- If relevant, provide examples using Azure PowerShell and clearly indicate that these are optional and not required for Linux users.
- Include Bash shell command examples for common tasks where scripting is appropriate.
- Ensure that any screenshots or references to file paths, shell prompts, or tools are either OS-neutral or include both Windows and Linux variants.
- Explicitly mention that the Azure Portal can be accessed from any OS, but provide automation alternatives for users who prefer or require CLI-based workflows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/how-to/disable-autoscaling.md
...ain//articles/cyclecloud/how-to/disable-autoscaling.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page provides no examples or instructions for disabling or enabling autoscaling, and does not mention any platform-specific tools or commands. However, the absence of any Linux (or Windows) examples means Linux users are not directly supported.
Recommendations
- Add explicit examples for both Windows (e.g., PowerShell commands) and Linux (e.g., Bash/CLI commands) to demonstrate how to disable and enable autoscaling.
- Ensure that any platform-specific instructions are paired with their equivalents for the other major platforms.
- If only one platform is supported, clearly state this and provide guidance for users on unsupported platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cyclecloud/how-to/configure-autoscaling.md
...n//articles/cyclecloud/how-to/configure-autoscaling.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any OS-specific examples, but it also omits any mention of Linux or cross-platform command-line instructions. There are no references to Windows tools or PowerShell, but the lack of Linux-specific examples or parity in instructions (such as CLI commands or Linux configuration paths) could be considered a subtle bias by omission.
Recommendations
- Add explicit examples or notes for configuring autoscaling via the command line on both Linux and Windows platforms.
- Include references to both Windows and Linux environments where relevant, such as file paths or environment variables.
- Provide sample commands for common Linux shells (e.g., Bash) in addition to any GUI instructions.
- Clarify that the instructions apply equally to both Windows and Linux clusters, or specify any differences if they exist.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/create-view-manage-namespaces.md
...//articles/event-grid/create-view-manage-namespaces.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes how to create, view, and manage Azure Event Grid namespaces using the Azure portal, with no mention of command-line tools or scripts. There are no examples or instructions for performing these tasks using cross-platform tools such as Azure CLI, Bash, or PowerShell. This omission results in a bias toward GUI-based workflows, which may be more familiar to Windows users, and leaves out Linux-first or automation-focused users who prefer or require CLI-based instructions.
Recommendations
- Add equivalent instructions for creating, viewing, and managing namespaces using the Azure CLI, which is cross-platform and widely used on Linux.
- Provide sample commands for common tasks (create, view, update, delete) using Azure CLI and, if relevant, PowerShell, ensuring both are presented with parity.
- Include notes or links to documentation for automating these tasks via scripts (Bash, PowerShell) for users who do not use the Azure portal.
- Structure the documentation so that CLI and portal instructions are presented side-by-side or in clearly separated sections, making it easy for users on any platform to follow.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/airflow-import-dags-blob-storage.md
...icles/data-factory/airflow-import-dags-blob-storage.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific command-line examples or tooling, but it references uploading files to Azure Blob Storage without specifying or demonstrating how to do so from different platforms. There are no explicit Windows-only tools or PowerShell commands, but the lack of any Linux (or cross-platform CLI) examples constitutes a subtle bias by omission.
Recommendations
- Add explicit examples for uploading files to Azure Blob Storage using cross-platform tools such as Azure CLI (az storage blob upload) and/or Python SDK.
- If GUI instructions are provided (such as via Azure Portal), clarify that these steps are platform-agnostic.
- Include command-line upload instructions for both Windows (PowerShell, Command Prompt) and Linux/macOS (Bash), or use cross-platform commands wherever possible.
- Mention that the Azure CLI and SDKs are available on all major platforms and provide installation links.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-troubleshoot-azure-data-lake.md
...data-factory/connector-troubleshoot-azure-data-lake.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific troubleshooting steps, commands, or examples. However, in the one instance where a tool is mentioned ('network monitor (netmon) trace'), only the Windows-specific tool is referenced, with no mention of Linux or cross-platform alternatives. There are no PowerShell or Windows command-line examples, but the lack of Linux tooling or instructions may disadvantage Linux users.
Recommendations
- When suggesting network tracing, mention cross-platform tools such as tcpdump or Wireshark, and provide brief instructions or references for both Windows and Linux environments.
- If any troubleshooting steps require command-line actions (e.g., checking permissions, network connectivity), provide both Windows (PowerShell/CMD) and Linux (bash) command examples.
- Explicitly state when a tool or step is Windows-only, and offer Linux equivalents where possible.
- Review all troubleshooting steps for implicit assumptions about the user's OS, and ensure Linux users are equally supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/continuous-integration-delivery-linked-templates.md
...ry/continuous-integration-delivery-linked-templates.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, commands, or tooling, but it also does not mention or demonstrate Linux or cross-platform CLI usage. There are no explicit Windows or PowerShell examples, but the lack of any platform-specific guidance or parity (e.g., CLI commands, script examples for Linux shells) may leave Linux users without clear instructions for common deployment tasks.
Recommendations
- Add explicit examples using Azure CLI commands that work cross-platform (Windows, Linux, macOS) for uploading templates and generating SAS tokens.
- Include sample scripts for both PowerShell and Bash (or other common Linux shells) for tasks such as uploading templates to storage and passing parameters.
- Clarify that the instructions are platform-agnostic where possible, or provide notes on any platform-specific considerations.
- Link to documentation on using Azure CLI and AzCopy for Linux users when referencing storage account operations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/format-delimited-text.md
...b/main//articles/data-factory/format-delimited-text.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a subtle Windows bias in the ordering and defaults of certain properties. For example, the default row delimiter for writing is '\r\n' (Windows-style) in Copy activity, and the documentation references Windows-centric encodings (e.g., WINDOWS-1252) before mentioning more cross-platform encodings. However, there are no explicit Windows-only tools, PowerShell examples, or exclusive references to Windows patterns. Linux and cross-platform compatibility are mentioned, but Windows conventions are often presented as defaults or first.
Recommendations
- Explicitly mention both Windows (\r\n) and Linux (\n) line endings as equally valid defaults, and clarify when each is used.
- Provide examples or notes for handling delimited text files with Linux-style line endings, especially in Copy activity and data flow scenarios.
- When listing encodings, group cross-platform encodings (like UTF-8, UTF-16) before platform-specific ones, or clarify platform relevance.
- Add a section or note about interoperability with Linux-based tools and environments, such as Hadoop or Unix file systems.
- If possible, include example configurations or scripts for both Windows and Linux environments, especially where file paths or delimiters may differ.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/event-grid-namespace-managed-identity.md
...es/event-grid/event-grid-namespace-managed-identity.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes how to enable managed identity for an Event Grid namespace using the Azure Portal GUI, with no mention of command-line tools or scripts. There are no examples or instructions for performing these actions using cross-platform tools such as Azure CLI or Azure PowerShell, which would allow Linux and macOS users to follow along without relying on the portal.
Recommendations
- Add step-by-step instructions for enabling managed identity using Azure CLI, which is cross-platform and widely used on Linux.
- If relevant, provide Azure PowerShell examples, but ensure Azure CLI examples are given equal or greater prominence.
- Explicitly mention that the Azure Portal is platform-agnostic, but also provide non-GUI alternatives for automation and scripting.
- Include links to official Azure CLI documentation for managed identities and Event Grid namespaces.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/monitor-data-factory-reference.md
...rticles/data-factory/monitor-data-factory-reference.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation is generally platform-neutral, focusing on Azure Data Factory monitoring schemas and log attributes. However, there is a subtle Windows bias in the section describing SSIS package executions, where only Windows-based tools (SQL Server Data Tools, SQL Server Management Studio, SQL Server Agent) are mentioned as invocation methods for SSIS executions. No Linux or cross-platform alternatives are referenced.
Recommendations
- Where SSIS execution tools are mentioned (e.g., SQL Server Data Tools, SQL Server Management Studio, SQL Server Agent), clarify their platform support and, if possible, mention any cross-platform or Linux-compatible alternatives (such as Azure Data Studio, Azure CLI, or REST API).
- If there are no Linux equivalents for certain SSIS operations, explicitly state this to inform users of platform limitations.
- Review referenced tooling and invocation methods throughout the documentation to ensure Linux and cross-platform options are included wherever available.
- Consider adding a section or note on how to monitor or invoke Data Factory and SSIS activities from Linux environments, using supported SDKs, CLI, or REST APIs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/event-schema-communication-services.md
...cles/event-grid/event-schema-communication-services.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation mentions using the Azure portal or Azure CLI to subscribe to events but does not provide any concrete examples or command-line instructions for either Windows (e.g., PowerShell) or Linux (e.g., Bash). However, the absence of any platform-specific examples or references means there is no explicit Windows bias, but there is a lack of parity in that no Linux-specific guidance or examples are provided.
Recommendations
- Add explicit Azure CLI command examples for subscribing to events, using Bash syntax to demonstrate Linux compatibility.
- If PowerShell or Windows-specific instructions are ever added, ensure equivalent Bash/Linux examples are included.
- Mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- Consider including troubleshooting tips or environment setup notes for both Windows and Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-control-flow-portal.md
.../articles/data-factory/tutorial-control-flow-portal.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Notepad as the default text editor for creating files and omitting any mention of Linux or cross-platform alternatives. No Linux-specific tools or workflows are suggested, and there are no command-line examples (such as Bash or PowerShell) for file creation or upload. However, the overall workflow is largely platform-agnostic, as it is centered around the Azure Portal UI and Azure services.
Recommendations
- When instructing users to create a text file, suggest cross-platform editors (e.g., 'Use a text editor such as Notepad (Windows), nano (Linux), or TextEdit (macOS) to create input.txt').
- Provide optional command-line examples for file creation and upload using Bash (Linux/macOS) and PowerShell (Windows), especially for steps like uploading files to Azure Blob Storage.
- Explicitly state that the Azure Portal and Azure Storage Explorer are available on Windows, macOS, and Linux, and provide links to platform-specific installation instructions.
- Avoid assuming the user's operating system; use neutral language when referring to local tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-share/how-to-revoke-share-subscription.md
...rticles/data-share/how-to-revoke-share-subscription.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific instructions or examples, but it also does not mention or show parity for Linux or cross-platform command-line approaches. The instructions are entirely GUI-based and do not reference Windows-specific tools, but the absence of CLI or scripting examples (such as Azure CLI, PowerShell, or Bash) may disadvantage Linux users who prefer or require non-GUI workflows.
Recommendations
- Add Azure CLI examples for revoking a share subscription, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- If PowerShell examples are added, ensure equivalent Bash or Azure CLI examples are provided.
- Explicitly mention that the described steps are performed via the Azure Portal, which is accessible from any OS, to clarify platform neutrality.
- Consider including automation or scripting options for users who may not use the GUI.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/handler-event-grid-namespace-topic.md
...icles/event-grid/handler-event-grid-namespace-topic.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples for either Windows (PowerShell/CLI) or Linux (Bash/CLI). However, this results in a lack of parity for users who prefer or require CLI-based workflows, which are especially common in Linux environments. There are no references to Windows-specific tools, but the absence of CLI examples can be considered an implicit bias, as Linux users often expect and rely on command-line instructions.
Recommendations
- Add Azure CLI examples for all major steps (creating system topics, enabling managed identity, assigning roles, creating event subscriptions) alongside the portal instructions.
- Ensure that CLI examples are cross-platform (work on both Windows and Linux shells).
- Explicitly mention that all steps can be performed via CLI and provide links to relevant CLI documentation.
- If PowerShell is referenced in other related docs, ensure Bash/Azure CLI equivalents are also present.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-reset-password-portal.md
...-edge-gpu-deploy-virtual-machine-reset-password-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents the Windows VM password reset steps before the Linux VM steps, despite both processes being nearly identical. There are no exclusive Windows tools, PowerShell commands, or missing Linux examples, but the ordering may subtly prioritize Windows users.
Recommendations
- Alternate the order of Windows and Linux sections in different documentation pages, or present both procedures in parallel (e.g., side-by-side tabs or tables) to avoid implicit prioritization.
- Explicitly state that the steps are identical for both OS types at the beginning, reducing perceived bias.
- Ensure that any references to command-line or scripting methods (e.g., PowerShell) in related articles also include Linux equivalents (e.g., Bash, CLI) for parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-secure-erase-certificate.md
...nline/azure-stack-edge-gpu-secure-erase-certificate.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only Azure Portal (web UI) instructions for erasing data and downloading the Secure Erase Certificate. There are no command-line examples or references for either Windows (e.g., PowerShell) or Linux (e.g., Bash/CLI), but the absence of any CLI instructions means Linux users do not receive parity for automation or scripting. No Windows-specific tools are mentioned, but the lack of Linux examples is a bias of omission.
Recommendations
- Add CLI-based instructions for erasing data and downloading the Secure Erase Certificate, using both PowerShell (for Windows) and Bash/Azure CLI (for Linux).
- Explicitly mention if these operations can only be performed via the Azure Portal, or provide REST API/CLI alternatives for cross-platform automation.
- Include example commands for both Windows and Linux environments where applicable, ensuring parity in documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/configure-expressroute-private-peering.md
...expressroute/configure-expressroute-private-peering.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal GUI for all instructions and does not provide any command-line examples. There are no references to Windows-specific tools or PowerShell, but there is also a complete absence of CLI-based instructions (such as Azure CLI or Azure PowerShell), which are important for Linux users and automation. This omission results in a bias by not addressing the needs of users who prefer or require command-line interfaces, especially those on Linux or macOS.
Recommendations
- Add parallel step-by-step instructions using the Azure CLI for each major task (e.g., creating ExpressRoute circuits, configuring private peering, creating and linking gateways).
- Where relevant, provide both Azure PowerShell and Azure CLI examples, and clearly indicate which commands are cross-platform.
- Explicitly mention that the Azure CLI is available on Windows, Linux, and macOS, and provide installation links.
- For verification steps (such as checking route tables or ARP tables), include CLI commands that can be run from Linux or macOS environments.
- Ensure that all automation and scripting examples are available in both PowerShell and Bash/Azure CLI formats.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-python-get-started-send.md
...icles/event-hubs/event-hubs-python-get-started-send.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild Windows bias by consistently referring to 'command prompt' and recommending Visual Studio Code, both of which are more closely associated with Windows environments. The instructions for running commands use generic terms like 'command prompt' and 'launch a command prompt', which can be interpreted as Windows-centric. However, all code and shell commands are cross-platform, and there are no PowerShell-specific commands or Windows-only tools mentioned. Linux and macOS users are not explicitly addressed, and there are no Linux-specific examples or terminal references.
Recommendations
- Use neutral, cross-platform terminology such as 'terminal' or 'command line' instead of 'command prompt'.
- Explicitly mention that the instructions and commands work on Windows, Linux, and macOS.
- When recommending editors, suggest a broader set of cross-platform editors (e.g., 'Visual Studio Code, PyCharm, or any editor of your choice').
- Where appropriate, provide example commands for both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh), especially for environment setup or navigation.
- Add a note clarifying that the Python and Azure CLI commands are cross-platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/transport-layer-security-enforce-minimum-version.md
...bs/transport-layer-security-enforce-minimum-version.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples, commands, or tooling for configuring the minimum TLS version for Event Hubs namespaces. However, it also does not provide any Linux or cross-platform examples, nor does it mention platform-specific tools (such as PowerShell, Azure CLI, or Bash). This omission may disadvantage Linux users or those seeking command-line automation, as there is no guidance on how to perform these tasks from non-Windows environments.
Recommendations
- Add explicit examples using Azure CLI, which is cross-platform and commonly used on both Windows and Linux.
- If PowerShell examples are added in the future, ensure that equivalent Bash or Azure CLI examples are also provided.
- Mention and link to platform-agnostic tools and documentation (such as Azure CLI) before or alongside any Windows-specific tools.
- Include a section or note clarifying that all configuration steps can be performed from any OS using the Azure Portal or Azure CLI.