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 1-25 of 96 flagged pages
Cloud Shell
Predictive IntelliSense in Azure Cloud Shell
...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 given in PowerShell syntax. There is no mention of Bash or Linux shell equivalents, nor any guidance for users who may prefer or require Bash in Azure Cloud Shell. The documentation assumes the use of PowerShell-specific tools and patterns, which may exclude or confuse Linux/Bash users.
Recommendations
- Add equivalent instructions and examples for Bash users in Azure Cloud Shell, including how to enable, configure, or disable predictive features (if available) in Bash.
- Explicitly state that the features described are specific to PowerShell, and clarify what options exist for Bash users.
- Provide links or references to documentation about Bash shell customization and prediction features, if any.
- Consider including a comparison table showing feature parity (or lack thereof) between PowerShell and Bash in Azure Cloud Shell.
- Ensure that introductory sections acknowledge both PowerShell and Bash as supported shells in Azure Cloud Shell.
Create Pull Request
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 Windows bias by providing only PowerShell command examples (Get-CloudDrive, Dismount-CloudDrive) for managing Cloud Shell storage, with no equivalent Bash or Linux shell commands shown. The 'Use PowerShell commands' section is prominent, and there is no mention of Linux tools or CLI patterns, nor are Linux/Bash equivalents presented alongside or before the Windows/PowerShell examples.
Recommendations
- Add equivalent Bash or Azure CLI examples for all PowerShell commands shown, such as using 'az storage share show' or 'az cloud-shell' commands.
- Include a 'Use Bash commands' or 'Use Azure CLI' section parallel to the PowerShell section.
- Present both Windows/PowerShell and Linux/Bash examples side-by-side, or alternate which platform is presented first.
- Mention Linux tools and patterns (e.g., shell scripting, use of environment variables) where relevant.
- Clarify that Cloud Shell supports both Bash and PowerShell, and provide guidance for users of each.
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 .NET (Windows-centric tools) are consistently highlighted in release notes, often listed before or alongside Linux tools. The example in November 2025 mentions Windows keyboard shortcuts first and specifically calls out Windows before Linux. There is a lack of explicit Linux shell (bash/zsh) examples or references, and some package/tool updates (e.g., Azure PowerShell, .NET) are more relevant to Windows users. While Linux tools are present (e.g., Inspektor Gadget, Azure Linux base image), the documentation tends to foreground Windows tools and patterns.
Recommendations
- Include explicit examples and references for Linux shells (bash, zsh) and tools in release notes.
- When listing tool updates, alternate the order or group by platform relevance (e.g., Azure PowerShell for Windows, bash tools for Linux).
- Provide parity in shortcut documentation, mentioning Linux and Windows equally and simultaneously.
- Add more details about Linux-specific changes, tools, and patterns to balance the coverage.
- Ensure that links and references include Linux-focused documentation where available.
Cloud Shell
Azure Cloud Shell Frequently Asked Questions (FAQ)
.../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. Windows and PowerShell examples are presented before Linux/Bash equivalents in several sections, such as copy/paste shortcuts and personal data management. Troubleshooting steps reference Microsoft Edge and Chrome developer tools before mentioning alternatives. PowerShell-specific features (like the Azure: drive) are described in detail, while Linux/Bash equivalents are less emphasized. There is limited mention of Linux-specific tools or troubleshooting patterns.
Recommendations
- Present Bash/Linux examples before or alongside PowerShell/Windows examples to ensure parity.
- Include explicit references to Linux troubleshooting tools and browser developer tools (e.g., instructions for Firefox and Safari).
- Expand explanations of Bash/Linux features (such as file system access, shell behaviors) to match the detail given for PowerShell.
- Where Windows-specific tools or patterns are mentioned, provide Linux equivalents (e.g., alternatives to PowerShell providers, Linux file system navigation).
- Ensure that screenshots and step-by-step instructions are available for Linux environments and browsers.
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 demonstrates a moderate Windows bias. PowerShell is frequently highlighted, with features like the Azure drive ('Azure:') described only for PowerShell and not for Bash. Many Microsoft service integrations are listed as PowerShell modules, and examples for listing installed modules are given for PowerShell before Bash. Several tools are Windows-centric (e.g., Exchange Online PowerShell, Office 365 CLI, Microsoft Graph PowerShell, SqlServer PowerShell modules), and there is a lack of equivalent Linux/Bash examples or parity in feature descriptions. The documentation often mentions PowerShell and Windows tools first or exclusively, while Linux/Bash alternatives are less emphasized or missing.
Recommendations
- Provide equivalent Bash examples for features currently described only for PowerShell, such as Azure resource navigation.
- List Bash/Linux commands alongside PowerShell commands when describing how to view installed modules and packages.
- Highlight open source and Linux-native tools with equal prominence as Microsoft/Windows-centric tools.
- Add examples and documentation for managing Azure resources using Bash and Azure CLI, not just PowerShell.
- Ensure that feature descriptions do not prioritize Windows/PowerShell tools and modules over Linux/Bash alternatives.
- Include links to Linux/Bash documentation where relevant, similar to the links provided for PowerShell modules.
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 shows moderate Windows bias. Azure PowerShell and Windows-specific tools are consistently highlighted alongside Azure CLI, with PowerShell version updates listed in every release note. The only explicit mention of keyboard shortcuts lists Windows first, and PowerShell-related links and features are prominent. Linux tools are mentioned less frequently and often as secondary notes. There are no Linux-specific command examples or tool usage instructions, and references to Linux tools (e.g., Apparmor, Inspektor Gadget) are brief and less emphasized.
Recommendations
- Include Linux-specific examples and tool usage instructions where relevant.
- Balance tool change notes by highlighting both PowerShell and Bash/CLI updates equally.
- When listing keyboard shortcuts or features, present Linux and Windows options together or alternate their order.
- Add references and links to Linux documentation and equivalents for tools and features.
- Explicitly mention and document Linux-first tools and patterns where applicable.
Cloud Shell
Azure Cloud Shell Frequently Asked Questions (FAQ)
.../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. Windows and PowerShell examples are presented before Linux/Bash equivalents in several places, such as copy/paste shortcuts and commands for managing personal data. Troubleshooting steps and browser tool instructions prioritize Microsoft Edge and Google Chrome, with Edge (a Microsoft product) mentioned first. PowerShell-specific features (like the Azure: drive) are described in detail, while Linux/Bash equivalents are less emphasized or absent.
Recommendations
- Alternate the order of examples so that Linux/Bash instructions appear before or alongside Windows/PowerShell ones.
- Provide equivalent Linux/Bash examples for all PowerShell-specific instructions, especially in troubleshooting and data management sections.
- Include instructions for accessing browser developer tools in Linux browsers (e.g., Firefox on Linux) and mention Linux-specific considerations where relevant.
- When describing features like the Azure: drive, clarify what Bash users see or provide analogous information for Bash.
- Ensure that tool installation and troubleshooting steps mention Linux/Bash commands and patterns explicitly, not just PowerShell or Windows approaches.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page for Azure Cloud Shell demonstrates a moderate Windows bias. PowerShell features and tools (such as the Azure drive and PowerShell cmdlets) are described in detail, with Windows-centric tools and modules (e.g., Exchange Online PowerShell, Microsoft Graph PowerShell, SqlServer PowerShell) listed prominently. Examples and instructions often reference PowerShell first or exclusively, with less emphasis on Bash/Linux equivalents. Some features, like the Azure drive, are only described for PowerShell, with no mention of similar navigation for Bash. There are also missing Linux/Bash examples for certain tasks, such as resource navigation and module listing.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell-specific features and examples, such as resource navigation and management.
- List Bash/Linux commands before or alongside PowerShell commands to avoid Windows-first ordering.
- Include Linux-native tools and workflows with equal prominence to Windows/PowerShell tools.
- Add examples for managing Azure resources using Bash and Azure CLI, not just PowerShell cmdlets.
- Clarify which features are exclusive to PowerShell and suggest Linux alternatives where possible.
- Expand documentation on open source and Linux tools to match the detail given to PowerShell modules.
Cloud Shell
Predictive IntelliSense in Azure Cloud Shell
...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 is no mention of Bash or Linux shell equivalents, nor any guidance for users who might use Bash in Azure Cloud Shell. The documentation assumes the user is working in a PowerShell environment, which is more closely associated with Windows, and does not provide parity for Linux users.
Recommendations
- Add equivalent examples and instructions for Bash users in Azure Cloud Shell, such as how to enable or configure command prediction features in Bash (e.g., using bash-completion, fzf, or other tools).
- Explicitly state that the features described are specific to PowerShell, and provide links or references to similar features for Bash or other shells.
- Include a section comparing PowerShell and Bash experiences in Cloud Shell, highlighting feature parity and differences.
- Mention and provide instructions for configuring shell profiles in Bash (e.g., .bashrc, .bash_profile) alongside PowerShell profile instructions.
- Ensure that documentation for Azure Cloud Shell covers both major shell environments equally, or clearly indicates when content is shell-specific.
Cloud Shell
Get started with Azure Cloud Shell
.../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 examples for both Azure CLI (Bash) and Azure PowerShell, but PowerShell is given equal prominence to Bash, and several sections (such as command listing and navigation) use PowerShell-specific patterns and terminology (e.g., 'Azure drive', 'cd Azure:/...'). The 'Next steps' section lists PowerShell before CLI, and screenshots and instructions reference the Azure portal, which is more commonly used in Windows environments. There is no explicit Linux bias or parity, and some PowerShell examples use Windows-centric navigation (e.g., drive notation).
Recommendations
- Ensure Bash/Azure CLI examples are given equal or greater prominence than PowerShell, especially in introductory sections.
- Add Linux-specific notes or examples where navigation or file paths differ (e.g., clarify that 'Azure:/' drive notation is PowerShell-specific and not available in Bash).
- Alternate the order of CLI and PowerShell examples to avoid implicit prioritization.
- Include screenshots or instructions for accessing Cloud Shell from non-Windows platforms (e.g., Azure CLI from Linux/macOS terminals).
- Clarify that the Azure portal is cross-platform and provide links or instructions for using Cloud Shell outside the portal (e.g., via direct CLI or SSH).
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 Windows bias by providing PowerShell-specific commands (Get-CloudDrive, Dismount-CloudDrive) without equivalent Bash or Linux shell examples. The section 'Use PowerShell commands' is prominent and no Linux/Unix command alternatives are mentioned, despite Cloud Shell supporting Bash. The documentation assumes familiarity with PowerShell and Windows-centric tooling, omitting guidance for Linux users.
Recommendations
- Add equivalent Bash or Azure CLI examples for all PowerShell commands (e.g., show how to get clouddrive info and unmount using Bash or az CLI).
- Include a 'Use Bash commands' section alongside 'Use PowerShell commands' to provide parity.
- Ensure terminology and instructions are not exclusively PowerShell-focused; reference both shells where appropriate.
- Where output paths or commands are shown, clarify differences between Bash and PowerShell environments if any exist.
- Review the page for other implicit Windows assumptions and address them to improve cross-platform accessibility.
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 Windows bias by providing only PowerShell command examples (Get-CloudDrive, Dismount-CloudDrive) for managing Cloud Shell storage, with no equivalent Bash or Linux shell commands shown. The 'Use PowerShell commands' section is prominent, and no Linux tools or CLI patterns are mentioned, leaving Linux users without guidance for performing the same tasks.
Recommendations
- Add equivalent Bash or Azure 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' or 'Use Azure CLI' section alongside the PowerShell section to ensure parity.
- Mention Linux shell patterns and tools where appropriate, such as using 'az storage' commands.
- Present both Windows and Linux examples together, or alternate which platform is shown first, to avoid 'windows_first' bias.
Cloud Shell
Azure Cloud Shell Frequently Asked Questions (FAQ)
.../blob/main/articles/cloud-shell/faq-troubleshooting.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits mild Windows bias. In several sections, Windows-specific tools and patterns (such as PowerShell and Windows key combinations) are mentioned first or exclusively. PowerShell examples are given alongside Bash, but the PowerShell provider ('Azure: drive') is described in detail, while Linux equivalents are not. Troubleshooting steps reference Microsoft Edge and Google Chrome developer tools before mentioning alternatives, and Windows-centric terminology (e.g., 'Azure: drive', 'PowerShell provider') is used without clear Linux/Bash parallels.
Recommendations
- Present Bash/Linux examples before or alongside PowerShell/Windows examples to ensure parity.
- Describe Linux/Bash equivalents for features like the 'Azure: drive' or clarify their absence.
- Include troubleshooting steps for Firefox and other Linux-friendly browsers, not just Edge/Chrome.
- When listing key combinations, rotate the order or start with Linux/macOS to avoid Windows-first bias.
- Where PowerShell-specific features are discussed, explicitly state their scope and offer Bash alternatives or note if none exist.
Cloud Shell
Predictive IntelliSense in Azure Cloud Shell
...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. There are no references to Bash or Linux shell equivalents, nor any mention of how predictive IntelliSense or similar features might work in non-PowerShell environments within Azure Cloud Shell. The documentation assumes users are working in PowerShell and does not provide parity for Linux users.
Recommendations
- Add equivalent examples and instructions for Bash users in Azure Cloud Shell, such as how to enable, configure, or disable command prediction features (e.g., bash-completion, fish shell suggestions).
- Mention whether predictive IntelliSense is available or planned for Bash or other shells in Azure Cloud Shell, and provide links or guidance for those environments.
- Clarify at the beginning that the instructions are PowerShell-specific, and offer navigation or links to documentation for Linux/Bash users.
- Include a comparison table or section outlining feature availability and configuration steps for both PowerShell and Bash environments in Azure Cloud Shell.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page for Azure Cloud Shell demonstrates a moderate Windows bias. PowerShell features and tools are emphasized, such as the Azure drive (Azure:) and numerous PowerShell modules for Microsoft services. Windows-centric tools like Exchange Online PowerShell, Microsoft Graph PowerShell, and SqlServer PowerShell modules are listed prominently. Examples and instructions often reference PowerShell first or exclusively, with fewer or less detailed Linux/Bash equivalents. Some features, such as Azure drive navigation, are described only for PowerShell, with no Bash/Linux alternative provided.
Recommendations
- Provide Bash/Linux equivalents for features like Azure drive navigation, or clarify if such features are PowerShell-only.
- Balance examples and instructions by giving equal prominence to Bash commands and Linux tools alongside PowerShell.
- List Linux/Bash tools and modules with the same level of detail as PowerShell modules for Microsoft services.
- Add explicit Bash/Linux examples for common tasks, such as listing installed modules or managing Azure resources.
- Clarify which features are available in Bash, PowerShell, or both, to help users on non-Windows platforms understand parity.
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 .NET (Windows-centric tools) are consistently highlighted in release notes, often listed alongside or before Linux-native tools. The link references and examples tend to favor PowerShell and Windows tools, with limited mention of Linux-specific alternatives or usage patterns. While there is some Linux coverage (e.g., Azure Linux base image, Inspektor Gadget), Windows tools and patterns are more prominent and often appear first.
Recommendations
- Include explicit Bash and Linux command examples where PowerShell commands are mentioned.
- Balance tool updates by highlighting Linux-native tools (e.g., Bash, zsh, Linux package managers) alongside Windows-centric ones.
- Provide equal coverage and placement for Linux and Windows tools in release notes and documentation links.
- Add more context or examples for Linux users, such as installation and usage instructions for common Linux packages.
- When referencing UI shortcuts or features, ensure Linux and Windows instructions are presented together and with equal prominence.
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 as available shell experiences, but repeatedly foregrounds Azure PowerShell and Windows-centric tools/documentation. Examples and links prioritize PowerShell and Windows tools (e.g., Azure PowerShell documentation, Visual Studio Code extension) before Linux equivalents. There is no explicit example or link for Bash usage or Linux-specific documentation, and the integrated editor is described in terms of Azure CLI or PowerShell, omitting Bash or Linux workflows.
Recommendations
- Add explicit examples and links for Bash usage and Linux workflows in Cloud Shell.
- Mention Linux tools and documentation alongside or before Windows/PowerShell equivalents.
- Provide parity in references to Azure CLI and Bash documentation, not just PowerShell.
- Describe the integrated editor in terms of both Bash and PowerShell workflows.
- Include a section or examples for common Linux command-line tools available in Cloud Shell.
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), which are traditionally associated with Windows environments. All examples, configuration instructions, and references are PowerShell-specific, with no mention of Bash, Linux-native shells, or equivalent features/tools for non-PowerShell users. There are no examples or guidance for users who might prefer Bash or other Linux shells in Azure Cloud Shell.
Recommendations
- Add equivalent examples and instructions for Bash users, such as how to enable or configure command prediction features in Bash (e.g., bash-completion, fish shell suggestions).
- Explicitly mention whether Predictive IntelliSense is available or not for Bash or other shells in Azure Cloud Shell.
- Provide links to documentation for configuring shell profiles and command suggestions in Linux shells.
- Clarify in the introduction that the features described are specific to PowerShell, and offer guidance for users of other shells.
- Consider including a comparison table showing feature parity 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
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits mild Windows bias. In several sections, Windows-specific tools and patterns (such as PowerShell, the Azure: drive, and Windows-first browser troubleshooting steps) are mentioned before their Linux equivalents. PowerShell examples are provided alongside Bash, but the Azure: drive is described only in the context of PowerShell. Troubleshooting steps for browser developer tools focus on Microsoft Edge and Chrome, with other browsers referenced only via a link. Windows keyboard shortcuts are listed first. Linux is mentioned, but often after Windows and macOS, and some features (like the Azure: drive) are not explained for Bash users.
Recommendations
- Ensure Linux/Bash examples are provided for all features described, especially where PowerShell or Windows tools are mentioned.
- Present examples and instructions in a platform-neutral order, or alternate which platform is listed first.
- Where features are Windows/PowerShell-specific (e.g., Azure: drive), clarify their absence or alternatives for Linux/Bash users.
- Expand troubleshooting steps to include explicit instructions for Linux browsers and environments, not just Windows tools.
- Balance the number and depth of PowerShell and Bash examples 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 exhibits a moderate Windows bias, primarily through the prominence of PowerShell examples and features, frequent mention of Windows-centric tools, and a tendency to introduce Windows/PowerShell options before Linux/Bash equivalents. The Azure drive feature is described only for PowerShell, and several Microsoft service integrations are PowerShell-specific. There is a lack of Bash/Linux-specific examples for Azure resource navigation and management, and some tool lists and instructions prioritize PowerShell commands over Bash alternatives.
Recommendations
- Provide equivalent Bash/Linux examples for Azure resource navigation (e.g., how to browse resources with Azure CLI in Bash).
- Balance the presentation of PowerShell and Bash by introducing Bash options first or side-by-side with PowerShell.
- Highlight Linux-native tools and workflows alongside Windows/PowerShell ones, especially for Azure management.
- Include examples and documentation for managing Microsoft services (e.g., Office 365, Exchange Online, Microsoft Graph) using non-PowerShell tools where available.
- Clarify when features are exclusive to PowerShell or Windows tools, and suggest Linux alternatives if possible.
- Expand the 'Preinstalled tools' and 'Productivity tools' sections to equally showcase both Linux and Windows/PowerShell tools.
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 demonstrates a moderate Windows bias. Azure PowerShell and related Windows-centric tools are consistently highlighted in release notes, often listed alongside or before Linux equivalents (e.g., Azure CLI). There is frequent mention of PowerShell-specific updates and features, while Linux-specific tools and patterns are less emphasized or only mentioned in passing. The use of PowerShell and .NET (traditionally Windows technologies) is prominent, and links often default to PowerShell tabs or documentation. Although Linux tools (e.g., Inspektor Gadget, Apparmor) are mentioned, they are less central and sometimes discussed only in the context of removal or deprecation.
Recommendations
- Ensure that Linux-specific tools and updates are given equal prominence in release notes, not just mentioned when removed or deprecated.
- Provide explicit Bash or Linux shell examples and documentation links alongside PowerShell references.
- When listing tool updates, alternate the order between Windows and Linux tools, or group by platform to avoid implicit prioritization.
- Add more details about Linux-specific improvements, features, and patterns in Cloud Shell, including links to relevant documentation.
- Avoid defaulting documentation tabs and links to PowerShell; offer parallel Bash/Linux tabs and examples.
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 page demonstrates Windows bias by exclusively providing PowerShell command examples (Get-CloudDrive, Dismount-CloudDrive) for managing Cloud Shell storage, with no equivalent Bash or Linux shell commands shown. The 'Use PowerShell commands' section is prominent, and there is no mention of Linux tools or CLI patterns, nor are Linux/Bash alternatives presented alongside or before the Windows/PowerShell examples.
Recommendations
- Add equivalent Bash/Azure CLI examples for all PowerShell commands (e.g., show how to get clouddrive info and unmount using Bash or az CLI).
- Include a 'Use Bash/Azure CLI commands' section parallel to the PowerShell section.
- Ensure that introductory and instructional text references both PowerShell and Bash/Azure CLI options, not just PowerShell.
- Where possible, present Linux/Bash examples before or alongside PowerShell examples to avoid implicit prioritization of Windows tooling.
- Mention any differences or limitations between PowerShell and Bash experiences in Cloud Shell.
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 and SSH, but does not provide Linux-specific examples or mention Linux-native tools (e.g., Bash, SSH-agent, SCP, etc.). PowerShell is highlighted as a management tool, which may suggest a Windows-centric approach. No explicit Linux commands or patterns are shown, and the examples and terminology lean towards Windows/PowerShell usage.
Recommendations
- Add explicit examples of using Linux-native tools (e.g., Bash, SSH, SCP) within Cloud Shell in a private virtual network.
- Clarify that both Bash and PowerShell are available in Cloud Shell, and provide parity in examples for both shells.
- Mention Linux-specific scenarios, such as managing Linux VMs or using Linux command-line utilities, alongside Windows/PowerShell scenarios.
- Ensure that references to remoting and management tools include both PowerShell (for Windows) and SSH/Bash (for Linux) to avoid platform bias.
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 commands. There are no references to Bash, Linux-native shells, or equivalent features/tools for non-Windows environments, despite Azure Cloud Shell supporting Bash. The documentation assumes use of PowerShell and its profile system, which is specific to Windows and PowerShell environments.
Recommendations
- Add equivalent examples and instructions for Bash users, including how to enable, configure, or disable predictive suggestions in Bash (e.g., via bash-completion or other plugins).
- Mention and compare any similar predictive features available in Bash or other Linux shells, if applicable.
- Clarify at the beginning that the page is PowerShell-specific, and provide links or references to documentation for Bash users.
- Where profile configuration is discussed, provide analogous instructions for Bash (e.g., editing .bashrc or .bash_profile).
- If Azure Cloud Shell supports predictive features in Bash, document those features and how to use them.
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 page demonstrates Windows bias by providing only PowerShell command examples (Get-CloudDrive, Dismount-CloudDrive) for managing Cloud Shell storage, without any Bash or Linux shell equivalents. The section 'Use PowerShell commands' is prominent, and no Linux/Unix commands or patterns are mentioned, despite Cloud Shell supporting both Bash and PowerShell environments. This may disadvantage Linux users or those using Bash in Cloud Shell.
Recommendations
- Add equivalent Bash command examples for all PowerShell commands (e.g., show how to get clouddrive info and unmount using Bash/Azure CLI).
- Include a section titled 'Use Bash commands' or 'Use Azure CLI' alongside 'Use PowerShell commands'.
- Ensure that instructions and examples are presented for both PowerShell and Bash, or clarify which environments the commands apply to.
- Mention Linux tools or patterns where relevant, and avoid implying that PowerShell is the default or only option.