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 1726-1750 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-alias-appservice.md
...e-docs/blob/main//articles/dns/dns-alias-appservice.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Windows as the operating system in all examples for App Service plans and web apps. There are no Linux-based examples or guidance, and the runtime stack is limited to .NET Core, which is cross-platform but the OS context is always Windows. No Linux-specific instructions, screenshots, or considerations are provided.
Recommendations
- Include examples of creating App Service plans and web apps using Linux as the operating system, alongside or alternating with Windows examples.
- Provide guidance for selecting different runtime stacks (such as Node.js, Python, Java) that are commonly used on Linux.
- Add notes or sections highlighting any differences or considerations when using Linux-based App Service plans.
- Ensure that tables and walkthroughs show both Windows and Linux options to promote parity.
- If there are any platform-specific limitations or features, clearly document them for both Windows and Linux.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-pools-to-simplified-compute-node-communication-model-migration-guide.md
...ified-compute-node-communication-model-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally avoids platform-specific instructions, but in the FAQ, RDP (a Windows protocol) is mentioned before SSH (the Linux equivalent), and no explicit Linux or Windows command-line examples are provided. The agent binaries are named for both platforms, but the Windows version (.exe) is listed after the Linux version. There are no Linux-specific tools or patterns mentioned, but the order and phrasing suggest a slight Windows-first bias.
Recommendations
- When mentioning remote connectivity, list SSH before RDP or mention both together (e.g., 'SSH or RDP connectivity...').
- Include explicit Linux and Windows examples or clarify that the process is identical for both platforms.
- If referencing agent binaries, list both platforms in parallel (e.g., 'Microsoft.BatchClusters.Agent (Linux) and Microsoft.BatchClusters.Agent.exe (Windows)').
- Consider adding a section or examples that address Linux-specific scenarios or tools, if relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/manage-private-endpoint-connections.md
.../articles/batch/manage-private-endpoint-connections.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents PowerShell examples before Azure CLI examples, which may suggest a Windows-first bias. The PowerShell section is also more prominently labeled and detailed, while the CLI section, though present, is listed after. There are no explicit Linux-only tools or shell examples (e.g., bash scripting), but the ordering and prominence favor Windows/PowerShell users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid implying Windows is the primary platform.
- Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS).
- Include bash-specific examples or notes for Linux users, such as using export for environment variables or referencing shell compatibility.
- Balance the level of detail and explanation between PowerShell and CLI sections.
- Consider adding a table or section comparing both approaches for parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-pool-node-error-checking.md
...main//articles/batch/batch-pool-node-error-checking.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. It specifically mentions the Windows pool setting 'enableAutomaticUpdates' and its default behavior, but does not provide equivalent information or guidance for Linux pools. There are no OS-specific troubleshooting examples, and the only OS-specific configuration discussed is for Windows. No Linux-specific errors, settings, or considerations are mentioned, and no examples are given for Linux start tasks or node management.
Recommendations
- Add a section describing Linux pool behaviors, such as how OS updates are handled for Linux nodes, and any relevant configuration options (e.g., package update management).
- Include examples or troubleshooting tips that are specific to Linux nodes, such as common issues with Linux start tasks, file permissions, or package installation failures.
- Where OS-specific settings are discussed (e.g., 'enableAutomaticUpdates' for Windows), provide a parallel explanation for Linux pools, or explicitly state if there is no equivalent.
- Ensure that any references to log files, remote access, or disk management include both Windows and Linux approaches (e.g., RDP vs SSH, file paths, log locations).
- If possible, provide example error messages or scenarios that are unique to Linux pools, to help users troubleshoot across both platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-service-workflow-features.md
...ain//articles/batch/batch-service-workflow-features.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page describes the Azure Batch workflow and resources in a platform-neutral way, but there are subtle signs of Windows bias. The 'Next steps' section lists the .NET client library (primarily associated with Windows) before Python, and there is no mention of Linux-specific tools, shell scripts, or command-line examples. No explicit Linux or cross-platform command-line examples are provided, and Batch Explorer (a GUI tool) is highlighted without alternatives for Linux users.
Recommendations
- Provide explicit Linux and cross-platform examples, such as using Bash scripts or Linux command-line tools for interacting with Azure Batch.
- List Python (a cross-platform language) before .NET in the 'Next steps' section to avoid implying Windows-first development.
- Mention or link to Linux-compatible tools for managing Batch resources, such as Azure CLI or REST API usage from Bash.
- Clarify the cross-platform availability of Batch Explorer or suggest alternatives for Linux users if needed.
- Include examples or documentation links for deploying and running workloads on Linux compute nodes, not just Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-pool-create-event.md
...s/blob/main//articles/batch/batch-pool-create-event.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Summary
The documentation page demonstrates a Windows-first bias, especially in the description of OS families (which only lists Windows Server versions) and the deprecated 'cloudServiceConfiguration' section, which is entirely Windows-centric. The 'virtualMachineConfiguration' section references a 'windowsConfiguration' property but does not mention or provide parity for Linux-specific configuration. While VM size links are provided for both Linux and Windows, the overall tone and examples favor Windows, and Linux configuration options are not described.
Recommendations
- Add a 'linuxConfiguration' section under 'virtualMachineConfiguration' to document Linux-specific settings, mirroring the detail given to 'windowsConfiguration'.
- In the 'cloudServiceConfiguration' section, clarify that it is Windows-only and provide a parallel explanation for Linux users (e.g., direct them to use 'virtualMachineConfiguration' with Linux images).
- When listing OS families or versions, explicitly mention Linux options or clarify their applicability.
- Ensure that all examples and configuration tables provide parity for both Windows and Linux, including links to relevant Linux documentation where appropriate.
- Consider including a sample 'virtualMachineConfiguration' for a Linux pool, showing how to specify a Linux image and any relevant configuration.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/tutorial-code.md
...ocs/blob/main//articles/digital-twins/tutorial-code.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The tutorial consistently refers to using a 'console window' and provides all command-line examples in a generic 'cmd/sh' block, but does not provide any Linux- or macOS-specific instructions, troubleshooting, or environment notes. There are tips and notes for Visual Studio (a Windows-centric IDE), but no equivalent guidance for Linux editors or tools. The documentation implicitly assumes a Windows environment or at least Windows patterns, with no explicit Linux parity.
Recommendations
- Explicitly mention that all commands work on Linux/macOS terminals as well as Windows Command Prompt/PowerShell.
- Provide Linux/macOS-specific notes where appropriate (e.g., file paths, terminal commands, environment variable setting).
- Include troubleshooting tips for common Linux/macOS issues (such as permissions or .NET SDK installation differences).
- Offer editor/IDE tips for Linux users (e.g., VS Code, JetBrains Rider) alongside Visual Studio notes.
- Clarify that the .NET SDK and Azure Digital Twins tools are cross-platform, and link to platform-specific installation guides where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/error-handling.md
...azure-docs/blob/main//articles/batch/error-handling.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally maintains OS neutrality but demonstrates subtle Windows bias in the 'Connect to compute nodes' section by mentioning RDP/Windows nodes before SSH/Linux nodes. Additionally, when discussing troubleshooting (e.g., examining event logs), it references generic 'event logs' without clarifying Linux equivalents, and does not provide explicit Linux command-line or log file examples. There are no PowerShell-heavy or Windows-tools-only examples, but Linux-specific troubleshooting steps are underrepresented.
Recommendations
- In the 'Connect to compute nodes' section, present SSH/Linux connection instructions before or alongside RDP/Windows, or alternate order in different documentation sections.
- When discussing troubleshooting (e.g., examining event logs), explicitly mention Linux log locations (such as /var/log/syslog or /var/log/messages) and provide example commands (e.g., 'cat', 'less', or 'journalctl') for Linux nodes.
- Add Linux-specific examples for common troubleshooting tasks, such as retrieving stdout/stderr files using Linux command-line tools or SDKs.
- Ensure that all API and portal instructions are clearly labeled for both Windows and Linux, and provide parity in examples and screenshots where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-private-zone-terraform.md
.../blob/main//articles/dns/dns-private-zone-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on creating Windows virtual machines, with no mention or example of Linux VM creation. While both Azure CLI and PowerShell are provided for verification steps, the core scenario is Windows-specific, and there are no Linux VM equivalents or guidance for users who may prefer or require Linux environments.
Recommendations
- Include parallel instructions and Terraform code samples for creating Linux virtual machines alongside Windows VMs.
- Update the checklist and scenario description to mention both Windows and Linux VM creation, or clarify if the quickstart is intentionally Windows-only.
- Provide guidance or links for users who want to adapt the scenario for Linux VMs.
- Ensure that examples and terminology are inclusive of both Windows and Linux environments to better serve cross-platform users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-virtual-network.md
...ocs/blob/main//articles/batch/batch-virtual-network.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates subtle Windows bias by listing Windows-specific ports (RDP/3389) before Linux equivalents (SSH/22) in several places, and by not providing any Linux-specific command-line examples or guidance. While the document is mostly platform-neutral, it lacks parity in examples and guidance for Linux users, especially regarding remote access and management patterns.
Recommendations
- When mentioning remote access ports, alternate the order or list Linux (SSH/22) first in some sections to avoid the appearance of Windows-first bias.
- Include explicit Linux command-line examples (e.g., using Azure CLI or Bash) alongside any PowerShell or portal instructions, especially for common tasks like creating VNets or Batch pools.
- Add references or links to Linux-specific tools and workflows for managing Azure Batch pools and networking.
- Clarify that both Windows and Linux nodes are supported equally, and provide guidance or examples for both platforms where relevant (e.g., remote access, troubleshooting, file mounts).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-private-resolver-get-started-template.md
...icles/dns/dns-private-resolver-get-started-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell deployment instructions, but the PowerShell example is given equal prominence to the CLI, and no explicit Linux shell (bash) or cross-platform scripting examples are provided. The use of PowerShell, which is traditionally associated with Windows, may indicate a slight Windows bias, especially since many Linux users would expect bash or shell examples. However, the CLI example is cross-platform, which helps mitigate this bias.
Recommendations
- Explicitly label the Azure CLI example as suitable for Linux/macOS/Windows to clarify its cross-platform nature.
- Consider providing a bash-specific example or note for Linux users, especially for environment variable handling and command syntax.
- If PowerShell is included, clarify that it is available cross-platform, or provide a note for Linux users on how to install/use PowerShell if desired.
- Ensure that any references to tools or commands are not Windows-specific unless necessary, and provide Linux equivalents or clarifications where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/jobs-and-tasks.md
...azure-docs/blob/main//articles/batch/jobs-and-tasks.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains cross-platform language, but there are subtle signs of Windows bias. In the section on specifying the command line for tasks, the Windows example (cmd.exe) is given before the Linux example (/bin/sh). Additionally, the 'robocopy' tool (Windows-specific) is mentioned as an example for copying files in a start task, with no Linux equivalent provided. No explicit Linux examples or tools are omitted, but Windows patterns and tools are mentioned first or exclusively in some cases.
Recommendations
- When providing command line examples, alternate the order or provide Linux examples first in some sections to balance representation.
- When mentioning Windows-specific tools like 'robocopy', also mention common Linux equivalents such as 'cp' or 'rsync', and provide example commands for both platforms.
- Where possible, include both Windows and Linux script/application examples in all relevant sections.
- Review for other subtle ordering or phrasing that may imply Windows is the default or primary platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/managed-identity-pools.md
...cs/blob/main//articles/batch/managed-identity-pools.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains cross-platform parity, but there is a subtle Windows bias in the order of examples and the scripting focus. In the section on obtaining managed identity tokens, the Windows/PowerShell example is presented before the Linux/Bash example, and the PowerShell script is slightly more detailed. However, both platforms are ultimately covered. The rest of the documentation avoids platform-specific tooling and provides instructions that are applicable to both Windows and Linux environments.
Recommendations
- Present Linux/Bash and Windows/PowerShell examples in parallel or alternate the order to avoid always listing Windows first.
- Ensure that example scripts for both platforms are equally detailed and prominent.
- Where possible, provide explicit notes or examples for both Windows and Linux when discussing configuration steps, not just scripting.
- Consider including CLI-based examples (e.g., Azure CLI) for pool creation and management, which are cross-platform, to further reduce reliance on platform-specific SDKs or tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/network-security-perimeter.md
...lob/main//articles/batch/network-security-perimeter.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides step-by-step instructions for associating an Azure Batch account with a network security perimeter using the Azure portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, which may indicate a slight Windows-first bias. Additionally, the PowerShell section is detailed and uses Azure PowerShell cmdlets, which are most commonly used on Windows, though they are available cross-platform. There are no Linux-specific shell (e.g., Bash) or scripting examples, and no mention of Linux tools or patterns.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is natively cross-platform and preferred by many Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding Bash script examples or guidance for automation on Linux systems.
- If PowerShell is included, clarify that Azure PowerShell is available cross-platform, and provide installation links for Linux/macOS users.
- Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., avoid showing only Windows-style UI elements if possible).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/quick-create-template.md
...ocs/blob/main//articles/batch/quick-create-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily describes deploying an Azure Batch account using the Azure portal, with only a brief mention of alternative methods (Azure PowerShell, Azure CLI, REST API) at the end of the deployment section. The linked 'Deploy templates' documentation is referenced with a URL that includes 'deploy-powershell', suggesting a Windows/PowerShell-first approach. There are no explicit Linux or cross-platform command-line examples (e.g., Azure CLI), nor are Linux tools or workflows mentioned directly in the main flow.
Recommendations
- Provide explicit Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and widely used on Linux.
- When referencing alternative deployment methods, list Azure CLI before or alongside Azure PowerShell to avoid Windows-first ordering.
- Include links to both Azure CLI and PowerShell deployment documentation, or to a neutral landing page that covers both.
- Add a section or callout specifically for Linux/macOS users, highlighting cross-platform tools and workflows.
- Avoid referencing documentation pages with 'powershell' in the URL as the default or only next step; instead, use a more inclusive or generic resource.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/simplified-node-communication-pool-no-public-ip.md
...tch/simplified-node-communication-pool-no-public-ip.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains cross-platform neutrality, but in the troubleshooting section, the Windows (PowerShell) command for TCP connectivity testing (Test-TcpConnection) is listed before the Linux equivalent (nc), and the Windows command is labeled with a comment, suggesting a slight 'windows_first' and 'powershell_heavy' bias. No other examples or instructions are specifically Windows-only, and both Azure CLI and PowerShell are mentioned as options for VNet preparation. There are no missing Linux examples, but the order and labeling of commands could be improved for parity.
Recommendations
- Present Linux and Windows command-line examples in parallel, or alternate their order in different sections to avoid always listing Windows first.
- Use neutral language such as 'On Windows' and 'On Linux' rather than '# Windows' and '# Linux' in code blocks.
- Where both Azure CLI and PowerShell are mentioned, provide explicit example commands for both platforms, or link to relevant documentation for each.
- Consider including a note at the start of the troubleshooting section that all commands are available for both Windows and Linux, and provide links to further resources for each platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/business-process-tracking/set-up-continuous-integration-deployment.md
...s-tracking/set-up-continuous-integration-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by exclusively referencing Visual Studio Code (VS Code) and its UI, and by omitting any mention of Linux or macOS-specific instructions or considerations. All terminal and command-line instructions are generic, but the workflow assumes the use of VS Code's GUI features (menus, context menus) and does not provide alternative instructions for Linux users (e.g., using different editors, handling file paths, or using CLI-only workflows). There are no PowerShell-specific commands, but the lack of Linux/macOS parity in examples and tool references is notable.
Recommendations
- Include explicit instructions or notes for Linux and macOS users, such as how to perform tasks in VS Code on those platforms or using alternative editors/CLI workflows.
- Provide examples of command-line operations that are platform-agnostic, and clarify any differences in file paths or tool usage between Windows and Linux/macOS.
- Mention prerequisites for Linux/macOS (e.g., installing VS Code, required extensions, or dependencies) and verify that all steps work cross-platform.
- Where GUI actions are described (e.g., right-click menus in VS Code), provide equivalent command-line alternatives for users who may not use the GUI.
- Clarify that all Git commands are cross-platform, and note any platform-specific authentication or credential manager differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/certification/edge-secured-core-devices.md
...n//articles/certification/edge-secured-core-devices.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page lists only devices certified for Edge Secured-core, and every device in the table is shown with a Windows OS (specifically Windows 10/11 IoT Enterprise). There are no Linux-based devices or examples, and no mention of Linux support or equivalents. This presents a clear Windows-first bias and omits Linux entirely.
Recommendations
- Include Linux-based Edge Secured-core certified devices if any exist, or clarify if certification is currently Windows-only.
- Add a section explaining OS support and certification scope, including any plans for Linux or other OS support.
- If Linux support is not available, provide guidance or links for users seeking Linux-compatible secure edge devices.
- Ensure future updates consider parity in listing and describing devices for all supported operating systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cdn/cdn-create-new-endpoint.md
...ocs/blob/main//articles/cdn/cdn-create-new-endpoint.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples. There are no references to Windows-specific tools (such as PowerShell), but there is also a lack of parity for Linux users, as no CLI (Azure CLI or Bash) examples are given. The absence of CLI instructions can be seen as a subtle 'windows_first' bias, since many Microsoft/Azure docs historically default to GUI or Windows-centric workflows.
Recommendations
- Add Azure CLI examples for creating a CDN profile and endpoint, which work cross-platform (Windows, Linux, macOS).
- Include Bash shell command examples for Linux users.
- Where possible, provide both portal (GUI) and CLI instructions side by side.
- Explicitly mention that the CLI instructions are platform-agnostic to encourage use by Linux and macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/certification/overview.md
...ure-docs/blob/main//articles/certification/overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by explicitly stating support for Windows IoT Enterprise and Azure Sphere OS, while relegating Linux support to a future roadmap. No Linux-specific examples, requirements, or tools are mentioned, and the focus is on Microsoft-centric operating systems.
Recommendations
- Clearly outline the timeline and roadmap for Linux support, including any preview or beta programs.
- Include examples or requirements relevant to Linux-based devices, even if support is limited or upcoming.
- Mention equivalent Linux security features or tools where possible, to help Linux device builders prepare.
- Ensure that future updates provide parity in documentation, examples, and tooling for both Windows and Linux platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-private-resolver-get-started-terraform.md
...cles/dns/dns-private-resolver-get-started-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell tab is presented second, and both examples are given equal prominence. However, there is a subtle Windows bias: PowerShell is a Windows-centric tool, and no explicit Linux shell (bash) or cross-platform scripting examples are provided. There are no explicit Linux-specific commands, nor is there mention of running these commands in a Linux environment. The use of PowerShell variable assignment syntax ($var=...) may confuse Linux users. The documentation does not mention or show Linux-specific tools or workflows.
Recommendations
- Add explicit bash/Linux shell examples for verification steps, using standard bash variable assignment and command syntax.
- Clarify that Azure CLI commands can be run on Windows, Linux, or macOS, and provide instructions for each where relevant.
- If PowerShell is included, also include bash equivalents, especially for variable assignment and command usage.
- Consider listing bash/Linux shell examples first, as Terraform users are often on Linux/macOS.
- Mention cross-platform compatibility of Terraform and Azure CLI in the prerequisites or introduction.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-shell/vnet/how-to-use-private-endpoint-storage.md
...loud-shell/vnet/how-to-use-private-endpoint-storage.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation exclusively uses Azure Portal (GUI) instructions, which are platform-agnostic but implicitly favor Windows users due to the historical association of the Azure Portal with Windows environments. There are no command-line examples (such as Azure CLI or PowerShell), and there is no mention of Linux-specific tools or workflows. The lack of CLI examples is a missed opportunity to support Linux users, who often prefer or require command-line instructions.
Recommendations
- Add Azure CLI examples for each major step (disabling public access, creating private endpoints, configuring DNS).
- Explicitly mention that all steps can be performed from any OS using the Azure Portal, but provide command-line alternatives for users on Linux and macOS.
- Include sample bash scripts or shell commands where appropriate.
- If PowerShell examples are later added, ensure Azure CLI or bash equivalents are always provided alongside.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/advanced-messaging/logs.md
...unication-services/concepts/advanced-messaging/logs.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation does not provide any platform-specific examples or commands, but it implicitly assumes Azure Portal and Azure Monitor usage patterns, which are often documented with a Windows-first perspective. There are no explicit Linux or cross-platform CLI examples, nor is there mention of Linux tooling or shell commands.
Recommendations
- Add cross-platform command-line examples (e.g., Azure CLI, Bash) for enabling and querying logs.
- Include instructions or references for viewing logs using Linux tools (such as jq, grep, or less) in addition to Azure Portal.
- Ensure that any future examples or screenshots represent both Windows and Linux environments equally.
- Explicitly mention that all steps can be performed from any OS, not just Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-shell/get-started/classic.md
...blob/main//articles/cloud-shell/get-started/classic.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Bash (Linux) and PowerShell (Windows) options for using Azure Cloud Shell, but there is a subtle Windows bias: PowerShell is often mentioned alongside or before Bash, and PowerShell-specific features (like the Azure drive and Get-AzCommand) are described in more detail than Bash equivalents. The 'Next steps' section lists PowerShell before CLI, and some advanced PowerShell navigation patterns are shown without Linux/Bash analogs.
Recommendations
- Ensure Bash/Linux examples and features are given equal prominence and detail as PowerShell/Windows ones.
- When listing shell options or next steps, alternate the order or explicitly state that both are equally supported.
- For advanced PowerShell features (like the Azure drive), provide Bash/Linux equivalents or note their absence.
- Add more Bash/Linux-specific tips or navigation patterns where possible to match the depth of PowerShell coverage.
- Review screenshots and UI instructions to ensure they are not Windows-centric and are equally applicable to Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-shell/release-notes.md
...-docs/blob/main//articles/cloud-shell/release-notes.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page shows a moderate Windows bias, primarily through frequent and prominent mentions of PowerShell and Azure PowerShell updates, as well as the use of PowerShell-specific tabs in referenced links. While Linux tools and updates are mentioned (e.g., Azure Linux base image, Inspektor Gadget), Windows-centric tools and patterns (such as PowerShell) are consistently listed first or highlighted, and there is a lack of explicit Bash or Linux shell examples or tabs.
Recommendations
- Provide equal emphasis on Bash/Linux shell updates and tools alongside PowerShell, especially in tool update lists.
- When referencing documentation links (such as 'Get started with Azure Cloud Shell ephemeral sessions'), ensure both PowerShell and Bash/Linux tabs are available and linked.
- Include explicit examples or notes for both PowerShell and Bash/Linux usage where relevant, to ensure parity.
- Avoid listing Windows/PowerShell tools or updates before their Linux equivalents unless there is a technical reason.
- Highlight Linux-specific changes (such as the Azure Linux base image) with the same prominence as Windows/PowerShell changes.