Cloud Shell
19
Total Pages
4
Linux-Friendly Pages
15
Pages with Bias
78.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
96 issues found
Showing 26-50 of 96 flagged pages
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 release notes frequently mention Azure PowerShell and .NET, which are traditionally Windows-centric tools, and provide version updates for them alongside Azure CLI. The documentation references PowerShell-specific tabs and links, and in some cases, Windows shortcuts (e.g., Ctrl+V) are mentioned before Linux equivalents. There is little explicit mention of Linux-specific tools or patterns, and Linux examples are generally not provided or are secondary to Windows/PowerShell ones.
Recommendations
- Include explicit Linux/Bash examples and tool updates alongside PowerShell and Windows tools.
- Provide parity in shortcut documentation, mentioning Linux and Windows equally and simultaneously.
- Add references and links to Linux-specific documentation (e.g., Bash tabs, Linux command-line usage).
- Highlight Linux-native tools and workflows where relevant, not just Windows-centric ones.
- Ensure that deprecated or added packages are described in terms of their impact on both Linux and Windows users.
Create Pull Request
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 First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits mild Windows bias. In several sections, Windows and PowerShell examples or tools are mentioned first or exclusively, such as in copy/paste key combinations (Windows listed first), browser developer tools instructions (Microsoft Edge and Chrome detailed, others referenced externally), and the use of PowerShell-specific features like the Azure: drive. PowerShell command examples are provided alongside Bash, but Windows-centric terminology and tools (e.g., nslookup, F12 for DevTools) are prioritized or explained in more detail than their Linux equivalents.
Recommendations
- Alternate the order of operating system references so Linux is sometimes listed first.
- Provide explicit instructions and screenshots for accessing Developer Tools in Firefox and Safari, not just Edge/Chrome.
- Include Linux-specific troubleshooting steps or tools where appropriate (e.g., mention dig as an alternative to nslookup).
- Expand on Bash/Linux shell features and limitations in parity with PowerShell explanations (e.g., clarify virtual drives or resource access in Bash).
- Ensure all command examples are given for both Bash and PowerShell, and consider including zsh or other common shells.
- Review terminology to avoid Windows-centric language (e.g., use 'command prompt' or 'terminal' instead of 'PowerShell prompt' when not strictly necessary).
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/overview.md
.../azure-docs/blob/main/articles/cloud-shell/overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page mentions both Bash and PowerShell as available shell experiences in Azure Cloud Shell, but references to Azure PowerShell and its documentation are given equal prominence to Azure CLI. However, there is a subtle bias toward Windows/PowerShell: PowerShell is mentioned alongside Bash as a primary option, and links to Azure PowerShell documentation are provided. There are no explicit Linux-specific examples, tools, or workflows highlighted, and the list of access points and features does not mention Linux-native tools or patterns. The text refers to the graphical editor and deployment through Azure CLI or Azure PowerShell, but does not mention Linux scripting or utilities. The permissions section does clarify that the user account has regular Linux permissions, but overall, Linux-specific usage is underrepresented.
Recommendations
- Add explicit Linux/Bash examples or workflows to balance PowerShell references.
- Include links to Linux-specific documentation or tutorials for Azure Cloud Shell.
- Highlight popular Linux tools available in Cloud Shell and provide examples of their usage.
- Mention Linux-native scripting patterns and how they can be leveraged in Cloud Shell.
- Ensure that Bash and Linux usage are given equal prominence to PowerShell throughout the documentation.
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
Missing Linux Example
Summary
The documentation page for Azure Cloud Shell features exhibits a moderate Windows bias. PowerShell is frequently highlighted, with unique features (such as the Azure drive) described only for PowerShell and not for Bash. Many Microsoft-specific tools and modules (e.g., Exchange Online PowerShell, Microsoft Graph PowerShell, SqlServer PowerShell modules) are listed, while equivalent Linux-native or cross-platform alternatives are not mentioned. Examples and instructions often reference PowerShell first or exclusively, and there is a lack of Bash/Linux-specific usage examples for Azure resource navigation and management.
Recommendations
- Provide equivalent Bash examples for features currently described only for PowerShell, such as Azure resource navigation.
- List Linux-native or cross-platform tools alongside Microsoft/PowerShell-specific tools, and clarify their usage in Cloud Shell.
- Ensure that instructions and examples are presented in a balanced way, alternating between Bash and PowerShell where possible.
- Highlight open source and Linux-native productivity and management tools with equal prominence to Microsoft/PowerShell tools.
- Add explicit Bash command examples for common Azure management tasks, not just PowerShell cmdlets.
- Clarify which features are available in both Bash and PowerShell, and note any limitations or differences.
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 provides both Bash (Azure CLI) and PowerShell examples, but PowerShell is mentioned as an equal alternative throughout, and some examples (such as listing commands for WebApps) use PowerShell-specific constructs (e.g., 'Azure:/My Subscription/WebApps') that are only available in PowerShell. The 'Next steps' section lists PowerShell before CLI, and the use of PowerShell cmdlets and navigation patterns may be unfamiliar or inaccessible to Linux users. There is a subtle Windows-first bias in ordering and tool emphasis.
Recommendations
- Ensure that Azure CLI (Bash) examples are presented before PowerShell examples, especially in introductory sections.
- Avoid PowerShell-specific navigation patterns (e.g., 'Azure:/My Subscription/WebApps') unless a CLI equivalent is provided and explained.
- In 'Next steps', list CLI and PowerShell resources in alphabetical order or alternate their order between documentation pages.
- Explicitly mention that Bash/CLI is cross-platform and highlight Linux compatibility where relevant.
- Add notes or tips for Linux users where PowerShell examples may not apply or require additional setup.
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 mentions PowerShell remoting as a key benefit and refers to command-line tools generically, but does not provide explicit examples or mention Linux-specific tools or patterns (such as SSH, Bash, or Linux-native management workflows). The emphasis on PowerShell and lack of Linux-focused examples or terminology suggests a Windows bias.
Recommendations
- Explicitly mention Linux-native tools and workflows, such as Bash, SSH, and Linux command-line utilities, alongside PowerShell.
- Provide examples or scenarios for both Windows (PowerShell) and Linux (Bash/SSH) users to ensure parity.
- Clarify that Cloud Shell supports both Bash and PowerShell environments, and highlight use cases for each.
- Include references to Linux management patterns and tools where relevant, not just Windows-centric ones.
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 concepts. There are no references to Bash or Linux-native shells, nor are there equivalent examples for users who might use Bash in Azure Cloud Shell. The documentation assumes the user is operating in a PowerShell environment, which is more closely associated with Windows, and does not mention or provide parity for Linux/Bash users.
Recommendations
- Add equivalent instructions and examples for Bash users in Azure Cloud Shell, such as how to enable or configure command prediction features in Bash (e.g., using 'bash-preexec', 'bash-completion', or 'fzf').
- Explicitly state at the beginning that the instructions are specific to PowerShell and provide links or references to documentation for Bash users.
- Where possible, provide side-by-side examples for both PowerShell and Bash to ensure Linux users are equally supported.
- Mention any limitations or differences in predictive features between PowerShell and Bash in Azure Cloud Shell.
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
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Windows-specific features (such as the Azure: drive and PowerShell provider) are discussed in detail, with Windows/PowerShell examples and terminology often appearing before or instead of Linux equivalents. Some troubleshooting and usage scenarios focus on Windows tools or workflows, and Linux/Bash examples are less prominent or missing in some sections.
Recommendations
- Ensure that for every PowerShell example, an equivalent Bash/Linux example is provided and given equal prominence.
- When discussing features like the Azure: drive (PowerShell-specific), clarify their absence or alternatives in Bash/Linux environments.
- In sections where browser developer tools are referenced, include instructions for Firefox and Linux browsers, not just Edge/Chrome (which are more common on Windows/macOS).
- When listing keyboard shortcuts, consider listing Linux before or alongside Windows, or group them without implied priority.
- Review troubleshooting steps to ensure they are platform-agnostic or provide platform-specific guidance for both Windows and Linux users.
- Highlight any differences in experience or limitations for Linux users explicitly, so expectations are clear.
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 page for Azure Cloud Shell exhibits a moderate Windows bias. While it acknowledges the Linux foundation of Cloud Shell and lists many Linux tools, it gives prominent and repeated attention to PowerShell features (such as the Azure drive and PowerShell-specific modules), lists Windows/PowerShell tools and examples before or more prominently than their Linux equivalents, and highlights Microsoft-centric (often Windows-first) tools. Some features, such as the Azure drive, are described only for PowerShell with no Bash/Linux equivalent mentioned.
Recommendations
- Provide equivalent Bash/Linux examples or features alongside PowerShell-specific features (e.g., explain how to navigate Azure resources in Bash, if possible).
- Balance the order of tool listings so that Linux/Bash tools are not always listed after PowerShell/Windows tools.
- Highlight cross-platform capabilities and clarify when features are PowerShell-only versus available in Bash.
- Include more Bash/Linux-centric usage scenarios and examples, especially for Azure resource management.
- Where PowerShell modules are listed, consider also listing popular Bash/Linux tools or scripts for the same tasks.
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
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation displays a moderate Windows bias. PowerShell and Windows-specific concepts (such as the Azure: drive and PowerShell provider) are explained in detail, with Windows copy/paste shortcuts listed first and PowerShell examples provided alongside Bash. Windows tools and browser instructions (Edge/Chrome) are prioritized, while Linux is mentioned but less emphasized. Some features, like the Azure: drive, are described only in the context of PowerShell, with no Linux/Unix shell equivalent discussed.
Recommendations
- Ensure Linux/Bash examples are always provided alongside PowerShell, and consider listing Bash examples first or equally.
- When describing features like the Azure: drive, clarify their relevance (or lack thereof) for Bash/Linux users.
- Provide Linux-specific troubleshooting steps or notes where applicable, not just Windows/PowerShell-centric guidance.
- Balance browser instructions to include Firefox/Linux-specific steps, not just Edge/Chrome.
- Where Windows tools or patterns are mentioned, ensure Linux equivalents are also explained (e.g., file system access, command-line tools).
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 page demonstrates a moderate Windows bias, primarily through a heavy emphasis on PowerShell features (such as the Azure drive and numerous PowerShell modules), listing Windows-centric tools (like Exchange Online PowerShell, Microsoft Graph PowerShell, and SqlServer PowerShell modules), and often mentioning PowerShell before Bash or Linux equivalents. While Linux tools and shells are acknowledged, the documentation gives more prominence to PowerShell and Windows-oriented workflows.
Recommendations
- Provide equivalent Bash/Linux examples for features highlighted with PowerShell (e.g., show how to navigate Azure resources using Azure CLI in Bash, not just Azure drive in PowerShell).
- Balance the listing of tools by including more Linux-native or cross-platform tools alongside PowerShell modules (e.g., mention Azure CLI and Bash scripts before or alongside PowerShell cmdlets).
- Clarify which features are exclusive to PowerShell and which are available in Bash, and provide guidance for Linux users where functionality differs.
- Include more Linux/Bash-focused productivity and scripting examples, especially in sections where PowerShell is featured.
- Reorder tool and feature lists to alternate or group by platform, rather than consistently leading with PowerShell/Windows tools.
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 provided exclusively in PowerShell syntax. There is no mention of Bash or Linux shell equivalents, nor are alternative tools or predictive features for non-PowerShell environments discussed. The guidance assumes the user is operating within a PowerShell-centric workflow, which, while available in Azure Cloud Shell, does not address users who prefer or require Bash or other Unix shells.
Recommendations
- Add equivalent examples and instructions for Bash users in Azure Cloud Shell, such as how to enable or configure command prediction features (e.g., bash-completion, fish shell suggestions, or other relevant tools).
- Explicitly mention the availability (or lack) of predictive IntelliSense features in Bash or other shells within Cloud Shell, and provide links or references to documentation for those environments.
- Balance the documentation structure so that both PowerShell and Bash/Linux users can easily find relevant information, possibly by splitting sections or providing parallel instructions.
- If predictive features are not available in Bash, state this clearly and suggest any workarounds or alternative productivity tools for Linux shell users.
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
Windows First
Missing Linux Example
Summary
The documentation provides detailed PowerShell command examples (Get-CloudDrive, Dismount-CloudDrive) for managing Azure Cloud Shell storage, but does not include equivalent Bash or Linux shell commands. The only explicit command-line examples are in PowerShell, and the section 'Use PowerShell commands' is present without a corresponding 'Use Bash commands' section. This creates a Windows/Powershell bias and may disadvantage users of the Bash environment in Cloud Shell.
Recommendations
- Add equivalent Bash/Azure CLI command examples for all PowerShell commands shown (e.g., show how to get file share info and unmount clouddrive using Bash/Azure CLI).
- Include a 'Use Bash commands' section parallel to the 'Use PowerShell commands' section.
- When introducing command-line examples, present both PowerShell and Bash/Azure CLI commands side-by-side or indicate which environment each applies to.
- Review the documentation for any other sections where only Windows/Powershell tools or patterns are mentioned, and add Linux/Bash equivalents where appropriate.
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 PowerShell-specific commands (Get-CloudDrive, Dismount-CloudDrive) for managing Cloud Shell storage, without equivalent Bash or Linux shell examples. The only command-line examples are PowerShell, and the section 'Use PowerShell commands' is prominent, with no mention of Bash or Linux alternatives. This creates friction for Linux/macOS users who may prefer or require Bash-based workflows.
Recommendations
- Add equivalent Bash/CLI examples for all PowerShell commands (e.g., show how to get clouddrive info and unmount using Bash/Azure CLI).
- Include a 'Use Bash commands' section alongside 'Use PowerShell commands', or present both together.
- Clarify which commands are available in Bash vs PowerShell, and link to relevant cross-platform documentation.
- Ensure that examples and instructions are not Windows-centric, and provide parity for Linux/macOS users.
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, such as PSReadLine, Az.Tools.Predictor, and PowerShell profiles. All examples and instructions use PowerShell syntax and tools, with no mention of Bash, Linux shells, or equivalent features for non-PowerShell environments. This creates friction for Linux/macOS users who may use Bash or other shells in Azure Cloud Shell.
Recommendations
- Add equivalent instructions and examples for Bash users in Azure Cloud Shell, such as how to enable, configure, or disable command prediction features in Bash (e.g., bash-completion, fish shell suggestions).
- Explicitly state that the features described are PowerShell-specific and provide links or references to documentation for Bash or other shells available in Cloud Shell.
- Include a comparison table or section outlining feature parity between PowerShell and Bash in Cloud Shell, especially regarding command prediction and customization.
- Mention how Linux/macOS users can access and customize similar features in their preferred shell environments.
Cloud Shell
Azure Cloud Shell Frequently Asked Questions (FAQ)
.../blob/main/articles/cloud-shell/faq-troubleshooting.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page provides both Bash and PowerShell examples, but there is a notable emphasis on Windows-specific tools and patterns. The 'Azure:' drive is described only in the context of PowerShell, and browser troubleshooting steps prioritize Microsoft Edge and Google Chrome, with screenshots from Edge. PowerShell examples are given equal prominence to Bash, but Windows terminology and tools (e.g., 'Azure:' drive, PowerShell provider) are mentioned before or exclusively compared to Linux equivalents.
Recommendations
- Add explicit Linux/macOS equivalents for PowerShell-specific features, such as describing how Linux users interact with Azure resources in Cloud Shell.
- Provide troubleshooting steps and screenshots for Firefox and Safari, not just Microsoft Edge and Chrome.
- Clarify whether features like the 'Azure:' drive are available in Bash, and if not, suggest Linux-native alternatives.
- Ensure Bash/Linux examples are presented first or in parallel with PowerShell/Windows examples.
- Include more Linux/macOS-specific troubleshooting tips where relevant.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page shows moderate Windows bias. PowerShell is frequently referenced, with features like the Azure drive ('Azure:') described only for PowerShell, and several Microsoft service integrations are PowerShell module-centric. Windows/PowerShell tools and patterns are often mentioned before or more prominently than Linux equivalents, and some examples (like listing installed modules) are PowerShell-first. However, the page does acknowledge Bash and Linux tools, and Cloud Shell itself runs on Azure Linux.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell-specific features and commands, especially for Azure resource navigation and module listing.
- Clarify which features are exclusive to PowerShell and which are available in Bash, and offer alternative workflows for Bash users.
- Balance the order of tool presentation (e.g., list Bash and PowerShell commands together or alternate which comes first).
- Add explicit examples and documentation for Linux/Bash users, especially for Azure resource management and integration with Microsoft services.
- Highlight open source and Linux-native tools as much as Microsoft/Windows-centric ones.
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 Azure PowerShell and .NET updates alongside Azure CLI, with PowerShell versions and features consistently mentioned. Some links and references use PowerShell tabs or focus on Windows-centric tools. Windows keyboard shortcuts are described first, and Windows-specific tools (e.g., msodbcsql18, mssql-tools18) are mentioned without clear Linux alternatives. However, there is some Linux representation, such as references to Azure Linux and Linux-specific tools like Inspektor Gadget.
Recommendations
- Include explicit Linux/macOS equivalents for all tools and features, especially where Windows tools are mentioned.
- Provide parity in example commands and documentation links (e.g., include Bash and PowerShell tabs in all guides).
- When describing features like keyboard shortcuts, list Linux/macOS options first or equally.
- Clarify when tools are cross-platform or provide alternatives for non-Windows users.
- Highlight Linux-specific changes and tools with equal prominence as Windows/PowerShell updates.
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 and its modules (PSReadLine, Az.Tools.Predictor), which are traditionally associated with Windows environments. All examples and instructions use PowerShell cmdlets, with no mention of Bash, Linux shell equivalents, or how predictive IntelliSense features might work for non-PowerShell users. The guidance assumes users are working in PowerShell, omitting any consideration for those using Bash or other shells in Azure Cloud Shell.
Recommendations
- Add equivalent instructions and examples for Bash users, including how to enable or configure command prediction features (e.g., bash-completion, fish shell suggestions).
- Clarify whether predictive IntelliSense is available for Bash or other shells in Azure Cloud Shell, and if not, explicitly state this limitation.
- Provide links or references to documentation for shell customization in Linux environments.
- If PowerShell is the only supported shell for predictive IntelliSense, make this clear at the beginning of the documentation.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits moderate Windows bias, primarily through a strong emphasis on PowerShell features (such as the Azure drive and numerous PowerShell modules), listing Windows-centric tools (e.g., Exchange Online PowerShell, Office 365 CLI, Microsoft Graph PowerShell) and presenting PowerShell examples and features before Bash/Linux equivalents. While Cloud Shell runs on Azure Linux and supports Bash, the documentation frequently highlights PowerShell-specific capabilities and Microsoft ecosystem tools, which may create friction for Linux/macOS users seeking parity or non-PowerShell workflows.
Recommendations
- Provide Bash/Linux equivalents for PowerShell-specific features, such as Azure drive navigation and resource discovery.
- Balance examples and tool listings by presenting Bash/Linux commands and workflows alongside PowerShell ones.
- Explicitly mention how Linux/macOS users can access or replicate PowerShell-centric features, or clarify any limitations.
- List Linux tools and productivity features before or alongside Windows/PowerShell tools to reinforce parity.
- Add more examples and documentation for open source and cross-platform tools, especially in critical management scenarios.
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 command examples (Get-CloudDrive, Dismount-CloudDrive) for managing Azure Cloud Shell storage, but does not offer equivalent Bash or Linux shell commands. The examples and command references are Windows-centric, and Linux/macOS users are left without guidance for performing the same tasks in Bash, despite Cloud Shell supporting both Bash and PowerShell environments.
Recommendations
- Include Bash shell equivalents for all PowerShell commands (e.g., show how to get file share info and unmount clouddrive in Bash).
- Present both Bash and PowerShell examples side-by-side or clarify which environment each applies to.
- Explicitly mention that Cloud Shell supports Bash and PowerShell, and provide navigation for users of each.
- Avoid presenting only PowerShell commands in sections that apply to all users.
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-centric tools like Azure PowerShell and .NET are consistently highlighted in tool updates, and PowerShell is referenced frequently. While Linux tools and changes (e.g., Azure Linux base image, Inspektor Gadget) are mentioned, Windows tools and patterns (PowerShell, .NET) are often listed first or with more detail. The note about keyboard shortcuts mentions Windows before Linux, and some links default to PowerShell tabs. There are no explicit Linux command examples or references to Bash, and Linux-specific tools are less emphasized.
Recommendations
- Include Bash and Linux CLI examples or references alongside PowerShell updates.
- Balance tool change lists by mentioning Linux-native tools and updates with equal prominence.
- When describing features (e.g., keyboard shortcuts), present Linux/macOS information first or equally.
- Add links and documentation tabs for Bash/Linux where PowerShell is referenced.
- Highlight Linux-specific improvements and tools in release notes, not just Windows-centric ones.
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 examples for both Azure CLI (Bash) and Azure PowerShell, but PowerShell is consistently presented alongside or immediately after CLI, and some advanced examples (such as navigating the Azure drive and using Get-AzCommand) are only shown for PowerShell. The 'Next steps' section lists PowerShell before CLI, suggesting a slight preference for Windows/PowerShell users. There are no Linux-specific tools, patterns, or troubleshooting tips, and the document does not mention platform-specific differences or considerations for Linux users.
Recommendations
- Ensure parity by providing advanced Azure CLI examples similar to those given for PowerShell (e.g., context-specific command discovery).
- Alternate the order of CLI and PowerShell examples or present them in parallel tabs to avoid implicit prioritization.
- Add notes or tips for Linux users, such as file path conventions, shell environment differences, or troubleshooting steps.
- Include links to Linux-specific documentation or resources in the 'Next steps' section.
- Explicitly state that both Bash and PowerShell are fully supported and highlight any differences in usage or capabilities.
Cloud Shell
Get started with Azure Cloud Shell using persistent storage
...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 Azure Cloud Shell, but PowerShell is mentioned equally or slightly more prominently. Examples and tips are provided for both Azure CLI (Bash) and Azure PowerShell, but PowerShell-specific features (such as the Azure drive and context-specific commands) are described in more detail. The 'Next steps' section lists Azure PowerShell before Azure CLI, suggesting a subtle Windows-first ordering.
Recommendations
- Ensure equal depth and detail for both Bash/Azure CLI and PowerShell examples, including advanced Bash usage where applicable.
- Alternate the order of presenting Bash/Azure CLI and PowerShell examples to avoid implicit prioritization.
- Highlight Linux/Bash-specific features or tips, such as file system navigation, scripting, or integration with other Linux tools.
- In the 'Next steps' section, list Azure CLI and Azure PowerShell in alphabetical order or alternate their order across documentation pages.
- Where PowerShell-specific features (e.g., Azure drive) are mentioned, consider providing Bash/Linux equivalents or explicitly noting their absence.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions both Bash and PowerShell as available shell experiences in Azure Cloud Shell, but PowerShell and Azure PowerShell cmdlets are referenced before Bash and Azure CLI in several places. The access points list puts Azure PowerShell documentation before Azure CLI documentation, and deployment examples mention Azure PowerShell before Azure CLI. This ordering subtly prioritizes Windows-centric tools and workflows, which may imply a bias toward Windows users.
Recommendations
- Alternate the order of Bash/Azure CLI and PowerShell references to avoid implying priority.
- Ensure examples and documentation links for both Bash/Azure CLI and PowerShell are provided equally and in parallel.
- Explicitly mention Linux-friendly workflows and tools (e.g., scripting with Bash, using Linux utilities) alongside PowerShell examples.
- In lists, avoid consistently listing Windows/PowerShell tools before Linux/Bash equivalents.
- Highlight that Cloud Shell runs on a Linux host and that Bash is a first-class experience.