Cloud Shell
38
Total Pages
21
Linux-Friendly Pages
17
Pages with Bias
44.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
36 issues found
Showing 1-25 of 36 flagged pages
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. PowerShell is frequently mentioned and given special features (such as the Azure drive), with detailed instructions and examples focused on PowerShell before Bash. Many Microsoft-centric tools (e.g., Office 365 CLI, Exchange Online PowerShell, Microsoft Graph PowerShell, SqlServer PowerShell modules) are highlighted, and several sections list PowerShell modules and features without Linux/Bash equivalents or alternatives. The Azure drive feature is described only for PowerShell, with no mention of similar navigation for Bash. Some commands are listed as 'Bash or PowerShell', but PowerShell-specific commands are often given first or exclusively. There are few, if any, Bash-specific examples, and Linux tools are grouped in a short list without further explanation.
Recommendations
- Provide Bash-specific examples and instructions alongside PowerShell, especially for features like Azure drive navigation and resource management.
- List Linux/Bash tools and equivalents with the same level of detail as PowerShell modules, including links to documentation for Bash-based Azure management.
- Ensure that introductory and feature sections mention Bash and Linux tools first or equally, not just as secondary options.
- Highlight open source and cross-platform tools more prominently, and clarify their usage in both Bash and PowerShell environments.
- Add examples of common workflows using Bash, such as managing Azure resources with Azure CLI, scripting with Bash, and using Linux-native utilities.
- Where features are PowerShell-only (e.g., Azure drive), explicitly state this and suggest Linux/Bash alternatives or workarounds.
Create Pull Request
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page for Azure Cloud Shell mentions both Bash and PowerShell, but consistently lists PowerShell before Bash and provides links to Azure PowerShell documentation before Azure CLI (which is more commonly used on Linux). There are no explicit Linux-specific examples, tools, or usage patterns highlighted. The integrated editor is described only in terms of Azure CLI and PowerShell, with no mention of Linux-native editors or workflows. The page does not provide parity in examples or tool references for Linux users.
Recommendations
- Alternate the order of Bash and PowerShell mentions, or list Bash first in some sections to avoid implicit prioritization of Windows/PowerShell.
- Provide explicit examples or links for Linux workflows, such as using Bash scripts, Linux command-line tools, or integration with Linux-native editors (e.g., Vim, Nano).
- Include references to Linux documentation or guides for using Cloud Shell with Bash.
- Highlight the availability of Linux command-line tools in the preinstalled tools list and provide examples of their usage.
- Ensure that both Azure CLI and PowerShell are given equal prominence in links and examples.
Cloud Shell
Persist files in Azure Cloud Shell
.../main/articles/cloud-shell/persisting-shell-storage.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell environments. All command-line examples for managing Cloud Shell storage use PowerShell cmdlets (e.g., Get-CloudDrive, Dismount-CloudDrive) with no equivalent Bash or Linux shell commands provided. The 'Use PowerShell commands' section is prominent, and no Linux/Unix-specific tools or patterns are mentioned. This may disadvantage users who prefer or use the Bash environment in Azure Cloud Shell.
Recommendations
- Add equivalent Bash/Linux shell commands for all PowerShell examples, such as using Azure CLI (az) commands to manage clouddrive and storage.
- Include a 'Use Bash commands' section alongside the PowerShell section, demonstrating parity in functionality.
- When describing commands or workflows, present both PowerShell and Bash examples, or alternate which is presented first.
- Reference Linux/Unix patterns and tools where relevant, ensuring that documentation is inclusive for both Windows and Linux users.
Cloud Shell
Azure Cloud Shell release notes
...e-docs/blob/main/articles/cloud-shell/release-notes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell and Windows-centric tools are consistently highlighted alongside Azure CLI, with PowerShell versions and features mentioned in every release note. Windows-specific keyboard shortcuts are referenced before Linux equivalents, and some links default to PowerShell tabs. There is limited mention of Linux-specific tools or patterns, and Linux features are generally not emphasized or explained in parity with Windows/PowerShell features.
Recommendations
- Include Bash and Linux command examples and version updates alongside PowerShell in each release note.
- When referencing keyboard shortcuts, list Linux shortcuts first or equally with Windows, and clarify differences.
- Add more details about Linux-specific tools, utilities, and patterns available in Cloud Shell.
- Ensure documentation links and tabs default to a neutral or Linux shell option, not PowerShell.
- Explicitly mention updates or changes to Bash, Zsh, or other Linux shells if applicable.
- Highlight Linux container base image changes and their impact on available tools and workflows.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/cloud-shell-predictive-intellisense.md
...les/cloud-shell/cloud-shell-predictive-intellisense.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on PowerShell and its modules (PSReadLine, Az.Tools.Predictor), with all examples and instructions using PowerShell cmdlets and patterns. There are no examples or mentions of equivalent features or workflows for Bash or other Linux shells, despite Azure Cloud Shell supporting Bash. The editor instructions also assume PowerShell usage. This creates a bias toward Windows/PowerShell users and does not address Linux/Bash users' needs.
Recommendations
- Add equivalent examples and instructions for Bash users in Azure Cloud Shell, such as how to enable, configure, or disable predictive suggestions in Bash (e.g., using bash-completion, fish shell, or zsh with plugins).
- Mention and link to documentation about command-line completion and prediction features available in Bash or other Linux shells supported by Cloud Shell.
- Clarify early in the documentation that the described features are specific to PowerShell, and provide guidance or links for users who are using Bash.
- Include instructions for editing Bash profile files (e.g., .bashrc, .bash_profile) if relevant, and how to persist configuration changes for Bash users.
- Balance the documentation by presenting Bash/Linux shell options and tools alongside PowerShell/Windows tools where possible.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/features.md
.../azure-docs/blob/main/articles/cloud-shell/features.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation, while describing a Linux-based environment, frequently highlights PowerShell and Windows-centric tools and patterns. PowerShell features (such as the Azure drive and cmdlets) are given dedicated sections and detailed explanations, while Bash/Linux equivalents are not. Several Microsoft/Windows-oriented tools (e.g., Exchange Online PowerShell, Microsoft Graph PowerShell, SqlServer PowerShell modules) are listed prominently. In tool listing and examples, PowerShell is often mentioned before Bash, and some features (like the Azure drive) are only available in PowerShell, with no Linux/Bash equivalent described.
Recommendations
- Provide Bash/Linux equivalents for features highlighted in PowerShell (e.g., describe how to navigate Azure resources using Azure CLI in Bash, if possible).
- Balance the order of presentation: mention Bash and PowerShell together, or alternate which is listed first.
- Include more Linux-native tools and workflows in the 'Other Microsoft services' and 'Database tools' sections, or clarify if certain features are PowerShell-only.
- Add explicit Bash/Linux examples for common tasks, not just PowerShell cmdlets.
- Clearly indicate when a feature is exclusive to PowerShell and suggest Linux/Bash alternatives where possible.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/faq-troubleshooting.md
.../blob/main/articles/cloud-shell/faq-troubleshooting.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation shows some Windows bias, particularly in the order and emphasis of examples and tools. Windows browsers and PowerShell are mentioned first or exclusively in several sections, and Windows-specific tools (e.g., PowerShell, Microsoft Edge) are referenced more prominently than Linux equivalents. Linux is included, but often after Windows and macOS, and with less detail.
Recommendations
- Ensure Linux examples and tools are presented with equal prominence and detail as Windows and macOS. For example, mention Linux browsers and keyboard shortcuts first or in parallel.
- When referencing browser developer tools, include explicit instructions for Firefox and Linux browsers, not just Edge and Chrome.
- In sections where PowerShell is discussed, provide Bash or other shell equivalents where possible, or clarify when features are PowerShell-specific.
- Avoid using Windows tools or terminology (e.g., 'PowerShell provider', 'Azure: drive') without noting their platform specificity and providing Linux/Bash alternatives or explanations.
- Review the order of OS mentions in lists and examples to avoid always listing Windows first.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/get-started/classic.md
.../blob/main/articles/cloud-shell/get-started/classic.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation presents both Azure CLI (Bash) and Azure PowerShell examples, but there is a subtle Windows bias. PowerShell (traditionally Windows-centric) is given equal prominence to Bash, and in some sections, PowerShell-specific features (like the Azure drive and context navigation) are described in detail without Linux/Bash equivalents. The 'Next steps' section lists PowerShell before CLI, and some PowerShell examples use Windows-style paths and concepts. There are no explicit Linux-only examples or references to native Linux tools.
Recommendations
- Ensure Bash/Azure CLI examples are presented first, or alternate their order to avoid implicit prioritization.
- Where PowerShell-specific features (like the Azure drive) are mentioned, provide equivalent Bash/Linux navigation tips or explicitly state if no equivalent exists.
- Include references to native Linux tools or workflows where appropriate, such as using 'ls' or 'find' in Bash to explore the environment.
- In the 'Next steps' section, alternate or randomize the order of PowerShell and CLI links, or group them together as 'Choose your shell: PowerShell or Bash/CLI'.
- Explicitly mention that Cloud Shell supports both Linux (Bash) and Windows (PowerShell) environments, and clarify any differences in capabilities.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/persisting-shell-storage.md
.../main/articles/cloud-shell/persisting-shell-storage.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only PowerShell command examples (Get-CloudDrive, Dismount-CloudDrive), with no equivalent Bash or Linux shell commands. It references PowerShell cmdlets and does not mention or demonstrate how to perform the same tasks in Bash, even though Azure Cloud Shell supports both Bash and PowerShell environments. This creates a bias toward Windows/PowerShell users and leaves Linux/Bash users without guidance.
Recommendations
- Add equivalent Bash command examples (e.g., using Azure CLI commands like 'az storage share show', 'az storage share delete', or 'clouddrive' commands available in Bash Cloud Shell).
- Explicitly mention that Cloud Shell supports both Bash and PowerShell, and provide parallel instructions for both environments.
- Avoid using only PowerShell cmdlets when describing common tasks; always provide Linux/Bash alternatives.
- Review the documentation for other places where Windows-centric terminology or tools are used, and ensure Linux parity.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/release-notes.md
...e-docs/blob/main/articles/cloud-shell/release-notes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits a moderate Windows bias. Azure PowerShell and Windows-centric tools are consistently highlighted alongside Azure CLI, and PowerShell versioning is called out in every release note. The only explicit mention of keyboard shortcuts prioritizes Windows (Ctrl+V) before Linux (Ctrl+Shift+V), and links and references often default to PowerShell tabs or Windows tools. Linux-specific tools and patterns are mentioned less frequently and with less detail, though there are some references to Linux (e.g., Azure Linux, Inspektor Gadget).
Recommendations
- Provide Linux/Bash examples and tool updates with equal prominence as PowerShell.
- When mentioning keyboard shortcuts or UI features, list Linux and Windows options together or alternate the order.
- Include links to Linux/Bash documentation and tabs, not just PowerShell.
- Highlight Linux-native tools and changes with the same frequency and detail as Windows/PowerShell tools.
- Explicitly mention Linux compatibility or differences for major features and updates.
Cloud Shell
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
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a bias towards Windows by exclusively using Azure Portal (a GUI tool often associated with Windows workflows) for all steps, without providing any command-line examples (such as Azure CLI or Bash scripts) that are common in Linux environments. There are no Linux-specific instructions or parity for users who may prefer or require command-line automation, and the documentation does not mention cross-platform tools until after the portal steps, if at all.
Recommendations
- Add Azure CLI (az) command-line examples for each major step, such as disabling public access, creating the private endpoint, and configuring DNS. These commands work on both Linux and Windows.
- Include Bash script snippets for automation, which are especially useful for Linux users.
- Explicitly mention that the Azure Portal is cross-platform, but also provide guidance for users who prefer not to use a GUI.
- Ensure that any references to tools or workflows are balanced between GUI (Portal), PowerShell, and CLI/Bash.
- Consider adding a section or callout for Linux users, highlighting any differences or additional steps required.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/vnet/overview.md
...e-docs/blob/main/articles/cloud-shell/vnet/overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page references PowerShell remoting as a primary management method and does not provide explicit examples or mention of Linux-native tools (e.g., SSH, Bash scripting) beyond a brief mention of SSH. There are no Linux-specific command-line examples or references to Bash, and the focus on PowerShell remoting and tools may suggest a Windows-centric approach.
Recommendations
- Include explicit examples of using Linux-native tools (e.g., Bash, SSH, scp, sftp) from Cloud Shell to manage resources.
- Mention Bash scripting and Linux command-line utilities alongside PowerShell remoting in the benefits and usage sections.
- Add Linux-focused scenarios or use cases, such as connecting to Linux VMs or managing resources with Bash.
- Ensure that any references to command-line management are balanced between Windows (PowerShell) and Linux (Bash/SSH) tools.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/vnet/troubleshooting.md
...blob/main/articles/cloud-shell/vnet/troubleshooting.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses the Azure portal (a web GUI) for all troubleshooting steps, without providing any CLI-based alternatives (such as Azure CLI or PowerShell Core commands). This approach implicitly favors users familiar with Windows-centric workflows and does not address Linux-first or cross-platform users who may prefer or require command-line instructions. No Linux-specific tools or examples are mentioned, and there is no parity for users who may be automating or scripting these tasks.
Recommendations
- Add equivalent Azure CLI command examples for each portal-based step, especially for resource provider registration, role assignments, and resource inspection.
- Explicitly mention that all steps can be performed using Azure CLI or PowerShell Core, and provide links or references to relevant command-line documentation.
- Where screenshots are provided for the portal, consider adding CLI output examples or command snippets for Linux/macOS users.
- Ensure that terminology and instructions do not assume a GUI-first workflow, and clarify that all actions can be performed cross-platform.
- If any step is only possible via the portal, explicitly state this and provide a rationale.
Cloud Shell
Azure Cloud Shell release notes
...e-docs/blob/main/articles/cloud-shell/release-notes.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The release notes frequently highlight Windows-centric tools and patterns, such as Azure PowerShell and .NET, and often mention PowerShell and Windows-specific features before Linux equivalents. While the documentation does acknowledge Linux (e.g., Azure Linux base image, Inspektor Gadget), examples and references to Linux tools are less prominent. There are no explicit Linux command examples, and PowerShell is referenced more often than Bash. Some links and tabs default to PowerShell. The severity is moderate, as Linux users can still use Cloud Shell, but may need to infer or seek out Linux-specific guidance elsewhere.
Recommendations
- Provide Linux/Bash examples alongside PowerShell where relevant, especially in linked documentation.
- Mention Linux tools and workflows with equal prominence to Windows/PowerShell tools.
- When referencing commands or tabs, offer both Bash and PowerShell options, or default to a neutral choice.
- Highlight Linux-specific improvements and features in the same detail as Windows/PowerShell updates.
- Ensure deprecated package lists and installation instructions include Linux/Bash context.
Cloud Shell
Predictive IntelliSense in Azure Cloud Shell
...les/cloud-shell/cloud-shell-predictive-intellisense.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on PowerShell-specific features and commands (PSReadLine, Az.Tools.Predictor), with all examples and instructions provided in PowerShell syntax. There is no mention of Bash or other shells available in Azure Cloud Shell, nor any equivalent features or configuration steps for Linux/macOS users who may prefer Bash or other environments. The documentation assumes the user is working in PowerShell and does not acknowledge alternative shells.
Recommendations
- Add equivalent instructions and examples for Bash (and other supported shells) in Azure Cloud Shell, including how to enable, configure, or disable similar predictive features if available.
- Explicitly state that the features described are PowerShell-specific and provide guidance for users of other shells.
- Include links or references to documentation for configuring shell experience in Bash or other environments.
- Consider reordering or separating instructions so that Linux/macOS users can easily find relevant information for their preferred shell.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page for Azure Cloud Shell features displays a moderate Windows bias. PowerShell is frequently highlighted, with features such as the Azure drive (`Azure:`) described only for PowerShell and not for Bash. Many Microsoft service integrations (Exchange Online, Office 365, Microsoft Graph, PowerBI, SqlServer) are presented as PowerShell modules, with no mention of equivalent CLI or Bash tools. In several sections, PowerShell commands and modules are listed before Bash/Linux alternatives, and some features (like Azure drive navigation) are described exclusively for PowerShell users.
Recommendations
- Provide Bash equivalents for features like Azure drive navigation, or clarify if such features are PowerShell-only.
- List Bash/Linux examples and tools alongside or before PowerShell/Windows tools to balance presentation.
- Highlight cross-platform alternatives for Microsoft service management (e.g., REST APIs, CLI tools) where PowerShell modules are mentioned.
- Explicitly state when a feature is not available in Bash, and suggest alternative workflows for Linux/macOS users.
- Add more Linux-focused usage examples and workflows throughout the documentation.
Cloud Shell
Persist files in Azure Cloud Shell
.../main/articles/cloud-shell/persisting-shell-storage.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides detailed PowerShell examples for managing Azure Cloud Shell storage, including commands such as Get-CloudDrive and Dismount-CloudDrive. There are no equivalent Bash or Linux shell examples, nor are cross-platform alternatives mentioned. The PowerShell section is prominent and the only example-based guidance, which may create friction for Linux/macOS users who typically use Bash in Cloud Shell.
Recommendations
- Add equivalent Bash/Azure CLI examples for all PowerShell commands (e.g., show how to get clouddrive info and unmount using Bash/Azure CLI).
- Explicitly state that Cloud Shell supports both Bash and PowerShell, and clarify which commands apply to which shell.
- Present examples for both shells side-by-side or in separate sections, ensuring Linux/macOS users have clear guidance.
- Avoid implying PowerShell is the default or preferred shell unless it is, and clarify shell selection if relevant.
Cloud Shell
Predictive IntelliSense in Azure Cloud Shell
...les/cloud-shell/cloud-shell-predictive-intellisense.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on PowerShell and its modules (PSReadLine, Az.Tools.Predictor), with all examples and instructions using PowerShell cmdlets and patterns. There are no Bash or Linux shell equivalents provided, nor is there any mention of how predictive IntelliSense works (or does not work) in Bash within Azure Cloud Shell. The documentation assumes users are working in PowerShell, which is more common on Windows, and does not address Linux/macOS users who may prefer Bash or other shells.
Recommendations
- Add equivalent instructions and examples for Bash users in Azure Cloud Shell, including how to enable, configure, or disable any available predictive IntelliSense features.
- Explicitly state whether predictive IntelliSense is available for Bash or other shells in Cloud Shell, and provide links or guidance for those environments.
- If features are PowerShell-only, clarify this early in the documentation and suggest alternatives or workarounds for Linux/macOS users.
- Include a comparison table or section outlining feature parity between PowerShell and Bash in Azure Cloud Shell.
Cloud Shell
Azure Cloud Shell release notes
...e-docs/blob/main/articles/cloud-shell/release-notes.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page for Azure Cloud Shell release notes demonstrates a moderate Windows bias. Windows-specific tools (Azure PowerShell, .NET) are frequently highlighted, and PowerShell is referenced more often than Bash or Linux-native shells. Some links and examples default to PowerShell tabs or Windows-centric tools, while Linux equivalents (e.g., Bash, Linux-specific utilities) are less emphasized or mentioned later. However, there are also references to Linux tools and features, such as Inspektor Gadget and Azure Linux, indicating some cross-platform consideration.
Recommendations
- Include Bash/Linux shell examples and references alongside PowerShell, especially in links and instructions.
- Highlight Linux-native tools and workflows with equal prominence to Windows/PowerShell tools.
- Ensure that documentation tabs and links default to a neutral or cross-platform view, not PowerShell/Windows by default.
- Add explicit notes or sections for Linux/macOS users where workflows or tools differ.
- When listing tool updates, alternate or group by platform-neutral and platform-specific tools.
Cloud Shell
Get started with Azure Cloud Shell
.../blob/main/articles/cloud-shell/get-started/classic.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI (Bash) and Azure PowerShell examples, but PowerShell is consistently mentioned alongside Bash, and in some cases, PowerShell-specific features (such as the Azure drive and context navigation) are highlighted without Linux/Bash equivalents. The 'Next steps' section lists PowerShell before CLI, suggesting a Windows-first orientation. There are no Linux-specific tools or workflows mentioned, and the Bash/CLI examples are limited to Azure CLI, which is cross-platform but does not showcase Linux-native patterns.
Recommendations
- Ensure that Bash/Azure CLI examples are as detailed as PowerShell examples, including navigation and context management.
- Alternate the order of CLI and PowerShell examples to avoid implicit prioritization.
- Include Linux-native patterns or tips (e.g., using environment variables, piping, or shell scripting) where relevant.
- Add a 'Next steps' link for Bash scripting or Linux command-line usage in Cloud Shell.
- Explicitly mention that Azure CLI works natively on Linux and macOS, and provide examples of integrating with common Linux tools.
Cloud Shell
Get started with Azure Cloud Shell ephemeral sessions
...lob/main/articles/cloud-shell/get-started/ephemeral.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Bash (Azure CLI) and PowerShell examples, but PowerShell is mentioned alongside Bash as a first-choice shell, and PowerShell examples are given equal prominence throughout. In some cases, PowerShell-specific features (such as the 'Azure:' drive and 'Get-AzCommand') are described, which do not have Linux/Bash equivalents. The 'Next steps' section lists PowerShell before CLI, suggesting a slight Windows-first ordering.
Recommendations
- Ensure Bash/Azure CLI examples are presented first, or alternate the order to avoid perceived prioritization.
- Clearly indicate which features are exclusive to PowerShell/Windows and provide equivalent guidance for Bash/Linux users where possible.
- Add notes or sections highlighting Linux/Bash-specific workflows or tools, especially where PowerShell features are described.
- In 'Next steps', alternate or randomize the order of PowerShell and CLI links to avoid implicit prioritization.
- Where screenshots or instructions reference PowerShell-specific UI elements or behaviors, provide parallel Bash/Azure CLI visuals or explanations.
Cloud Shell
Deploy Azure Cloud Shell in a virtual network with quickstart templates
...docs/blob/main/articles/cloud-shell/vnet/deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally presents Azure CLI and Azure PowerShell as equivalent options for resource creation and management, but in several places, PowerShell is mentioned before CLI (e.g., in lists and links). The alternate way to get the Azure Container Instance ID gives the PowerShell command before the CLI command. There are no Linux-specific tools or patterns mentioned, and no explicit Bash scripting examples are provided. The documentation does not exclusively focus on Windows, but there is a subtle ordering bias favoring PowerShell/Windows tools over CLI/Linux equivalents.
Recommendations
- Present Azure CLI and PowerShell examples in parallel, alternating which comes first, or group them together under neutral headings.
- Include explicit Bash scripting examples where relevant, especially for steps that could be automated.
- When listing options (portal, CLI, PowerShell), alternate the order or use alphabetical ordering to avoid implicit prioritization.
- Add notes clarifying that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Where screenshots or UI references are given, clarify if they are platform-agnostic or provide Linux/macOS equivalents if any differences exist.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/get-started/new-storage.md
...b/main/articles/cloud-shell/get-started/new-storage.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Bash (Linux) and PowerShell (Windows) options for Cloud Shell, but PowerShell is often mentioned alongside or immediately after Bash, and some examples (such as the 'Azure drive' and 'Get-AzCommand') are PowerShell-specific features not available in Bash. The 'Next steps' section lists PowerShell before CLI, subtly prioritizing Windows tools.
Recommendations
- Ensure that Bash (Linux) examples are presented first or in parallel with PowerShell examples, especially in introductory sections.
- Avoid referencing PowerShell-specific features (like the Azure drive) without Linux/Bash equivalents or clearly marking them as PowerShell-only.
- In the 'Next steps' section, alternate the order of PowerShell and CLI links or group them together to avoid implicit prioritization.
- Where possible, provide Bash/Linux equivalents for any PowerShell-specific workflows or commands.
- Explicitly state that both Bash and PowerShell are fully supported, and clarify any differences in capabilities or features.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/overview.md
.../azure-docs/blob/main/articles/cloud-shell/overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page for Azure Cloud Shell presents both Bash and PowerShell as available shell options, but PowerShell is consistently mentioned alongside or before Bash, and links to Azure PowerShell documentation are given equal prominence to Azure CLI. The integrated editor is described in the context of Azure CLI or Azure PowerShell, with no mention of Bash scripting or Linux-native tools. There are no explicit Linux-only examples or tools highlighted, and the documentation does not provide parity in discussing Linux workflows or tools.
Recommendations
- Explicitly mention Bash and Linux-native tools (e.g., sed, grep, vim, nano) as available and supported in Cloud Shell.
- Provide links to Bash scripting documentation or Linux command-line guides alongside PowerShell references.
- When listing access points or features, alternate the order of Bash and PowerShell to avoid implicit prioritization.
- In the editor section, mention editing and running Bash scripts as a first-class scenario.
- Add examples or references that showcase Linux command-line workflows in Cloud Shell.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/vnet/deployment.md
...docs/blob/main/articles/cloud-shell/vnet/deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for key operations (resource group and virtual network creation, getting Container Instance ID), but PowerShell is consistently mentioned before CLI in lists and examples. This ordering, along with the explicit mention of PowerShell in command examples and links, suggests a subtle Windows-first bias. There are no Linux-specific tools or patterns referenced, and Bash is only mentioned as a shell choice, not in example commands.
Recommendations
- Alternate the order of Azure CLI and PowerShell examples and links, or list CLI first to balance representation.
- Explicitly mention Linux environments and Bash usage in command examples where relevant.
- Include screenshots or walkthroughs using Bash/CLI on Linux, not just PowerShell or portal UI.
- Add notes clarifying that all CLI commands work on Linux, macOS, and Windows.
- Where possible, provide Bash script snippets for automation alongside PowerShell equivalents.