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 51-75 of 96 flagged pages
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 Azure CLI and Azure PowerShell examples in parallel, but PowerShell is consistently mentioned alongside Bash as the primary shell choice, and PowerShell examples are given equal prominence to CLI. The 'Next steps' section lists Azure PowerShell before Azure CLI, suggesting a slight Windows-first ordering. There is no explicit mention of Linux-specific tools or patterns, nor any examples tailored to Linux users beyond Bash/CLI.
Recommendations
- Alternate the order of Azure CLI and PowerShell examples to avoid implicit prioritization.
- List Azure CLI before Azure PowerShell in 'Next steps' to reflect its cross-platform nature.
- Add explicit notes or examples for Linux users, such as using native Linux shell features or integrating with common Linux tools.
- Clarify that Bash/CLI is fully supported on Windows, macOS, and Linux to reinforce parity.
- Consider including screenshots or instructions that reference Linux environments (e.g., terminal usage outside the Azure portal).
Create Pull Request
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 Cloud Shell, but PowerShell is mentioned alongside Bash at every step, and PowerShell examples are given equal prominence to Azure CLI (Bash) examples. There is a slight Windows-first bias in the 'Next steps' section, where 'Learn about Azure PowerShell' is listed before 'Learn about Azure CLI'. The documentation does not provide Linux-specific tools or workflows beyond Azure CLI, nor does it mention Linux file system patterns or utilities.
Recommendations
- Alternate the order of Bash/Azure CLI and PowerShell examples to avoid implicit prioritization.
- In 'Next steps', list 'Learn about Azure CLI' before 'Learn about Azure PowerShell' or present them together.
- Include examples or tips for Linux-specific workflows, such as using native Linux commands for file management in Cloud Shell.
- Explicitly mention that Bash in Cloud Shell provides a Linux environment and highlight Linux-native features or integrations.
- Consider adding a section on differences between Bash and PowerShell environments in Cloud Shell, especially for users coming from Linux backgrounds.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page for Azure Cloud Shell mentions both Bash and PowerShell as shell options, but references to Azure PowerShell and PowerShell cmdlets appear before Bash or Linux equivalents in several sections. The 'Multiple access points' and 'Authenticated and configured Azure workstation' sections list Azure PowerShell documentation and cmdlets before Azure CLI and Bash, suggesting a Windows-first and PowerShell-heavy bias. There are no explicit Bash or Linux command examples, and the integrated editor is described in the context of Azure CLI or PowerShell, not Bash.
Recommendations
- Alternate the order of mentioning Azure CLI/Bash and Azure PowerShell to avoid Windows-first bias.
- Provide explicit examples or references for Bash usage alongside PowerShell, including links to Bash documentation.
- Highlight Linux tools and workflows equally, such as mentioning text editors (vim, nano) and Linux command-line utilities available in Cloud Shell.
- Clarify that both Bash and PowerShell are fully supported and provide parity in features and documentation.
- Add a section or examples showing typical Linux/Bash usage scenarios in Cloud Shell.
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 both Azure PowerShell and Azure CLI options for resource creation, but in several instances, PowerShell is mentioned or linked before Azure CLI. In the 'Alternate way to get the Azure Container Instance ID' section, the PowerShell example is given before the Azure CLI example. Additionally, in the 'Create a virtual network' section, the PowerShell link precedes the CLI link. This ordering may subtly prioritize Windows/PowerShell users over Linux/CLI users, though both options are present. No exclusive use of Windows tools or missing Linux examples were found.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples and links throughout the documentation to avoid implicit prioritization.
- Where possible, provide both PowerShell and CLI examples side-by-side, or in a tabbed format, to make parity explicit.
- In sections where command-line examples are given, ensure that Azure CLI (cross-platform) is presented first or equally with PowerShell.
- Review screenshots and UI instructions to ensure they are not Windows-specific unless necessary.
- Explicitly state that both PowerShell and Azure CLI are supported and cross-platform, and clarify that users can choose either based on their environment.
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 consistently given equal prominence to Bash, and in some cases, PowerShell-specific features (such as the Azure drive and cmdlets) are described in more detail. The 'Next steps' section lists Azure PowerShell before Azure CLI, subtly prioritizing Windows tooling. There are no Linux-specific examples or references to Linux tools beyond Bash, and PowerShell features (like the Azure drive) are highlighted without Linux equivalents.
Recommendations
- Ensure that Bash/Linux examples are as detailed as PowerShell ones, especially where PowerShell-specific features (like the Azure drive) are described.
- Alternate the order of CLI and PowerShell examples to avoid implicit prioritization.
- Include references to Linux-specific tools or workflows where relevant, such as file manipulation or scripting within Bash.
- In 'Next steps', list Azure CLI and Azure PowerShell in alphabetical order or alternate their order in different documentation pages.
- Add a note clarifying that Bash is the default shell for many Linux users, and highlight any Bash-specific features or tips.
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 presents both Bash (Azure CLI) and PowerShell options for most command-line tasks, but PowerShell is frequently mentioned alongside or immediately after Bash, and some examples (such as navigating the Azure drive) are PowerShell-specific. The 'Next steps' section lists PowerShell before CLI, and screenshots and instructions do not highlight Linux-specific workflows or tools. There is a slight preference for Windows/PowerShell paradigms, with no explicit Linux-first or Linux-only examples.
Recommendations
- Alternate the order of Bash/Azure CLI and PowerShell examples to avoid implicit prioritization.
- Add explicit notes or examples for Linux users, such as using Bash scripting or Linux file paths.
- Include screenshots or instructions that show both Bash and PowerShell environments.
- Highlight any differences in experience between Bash and PowerShell in Cloud Shell, especially for Linux users.
- Ensure parity in advanced examples, such as file navigation, scripting, and environment customization, for both Bash and PowerShell.
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 both Azure PowerShell and Azure CLI options for resource creation, but in several places, PowerShell (commonly associated with Windows) is listed before Azure CLI. In the 'Alternate way to get the Azure Container Instance ID' section, the PowerShell example is given before the Azure CLI example. However, both tools are covered, and there are no exclusive Windows-only tools or missing Linux examples. The documentation does not show explicit bias in tool availability, but the ordering and occasional emphasis on PowerShell may subtly favor Windows users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples throughout the documentation, or present CLI examples first to better reflect cross-platform parity.
- Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS to avoid the perception that PowerShell is Windows-only.
- Where possible, provide Bash shell script examples alongside PowerShell, especially for command-line tasks.
- Ensure that screenshots and UI references do not assume a Windows environment (e.g., avoid showing only Windows-style UI elements if possible).
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
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 frequently mentioned alongside or immediately after CLI, and some sections (such as Next Steps) list PowerShell resources before CLI. There is a slight tendency to present Windows/PowerShell options as equally prominent or sometimes first, which may subtly reinforce Windows-centric usage patterns. However, Bash/CLI options are present throughout, and the shell selection is explicitly offered.
Recommendations
- Ensure that Azure CLI (Bash) examples are presented before PowerShell examples in each section to avoid Windows-first ordering.
- Add explicit notes clarifying that Bash/CLI is cross-platform and may be preferable for Linux/macOS users.
- Balance the 'Next steps' section by listing CLI and PowerShell resources together or alternating their order.
- Where screenshots or instructions reference PowerShell-specific features (such as the Azure drive), clarify their platform specificity and offer equivalent Bash/CLI workflows if available.
- Consider adding a short section explaining the differences between Bash and PowerShell environments, including platform compatibility.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/get-started/ephemeral.md
...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 consistently mentioned alongside or immediately after Bash, and PowerShell-specific features (like the Azure drive and Get-AzCommand) are highlighted. The 'Next steps' section lists PowerShell before CLI, and some examples (like navigating the Azure drive) are only shown for PowerShell, which is a Windows-centric tool, while no equivalent Linux-native navigation is provided.
Recommendations
- Alternate the order of Azure CLI and PowerShell examples to avoid consistently listing PowerShell second or first.
- Provide equivalent examples for Bash/Linux users where PowerShell-specific features are mentioned (e.g., navigating Azure resources via CLI or filesystem tools).
- Ensure that 'Next steps' links alternate or balance CLI and PowerShell resources, or group them together neutrally.
- Explicitly mention that both Bash and PowerShell are available in Cloud Shell, and clarify when examples are platform-specific.
- Add notes or examples for Linux-native tools or patterns where only PowerShell features are described.
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 Azure Cloud Shell, but PowerShell is frequently mentioned alongside or before Bash, and PowerShell-specific examples and terminology (e.g., Azure PowerShell cmdlets, 'Azure drive') are given equal prominence. There is a slight tendency to highlight Windows/PowerShell patterns and tools, such as referencing the 'Azure drive' and cmdlets, which are unique to PowerShell and Windows environments.
Recommendations
- Ensure Bash/Linux examples are presented first or with equal prominence as PowerShell examples.
- Add more context or explanations for Bash/Linux users, especially where PowerShell-specific features (like 'Azure drive') are mentioned.
- Include explicit references to Linux tools or workflows where possible, such as file system navigation or scripting in Bash.
- Balance the 'Next steps' section by linking to both Bash/Linux and PowerShell resources equally.
- Clarify that both Bash and PowerShell are fully supported and highlight any differences in capabilities or workflows.
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 page presents both Azure PowerShell and Azure CLI options for resource group and virtual network creation, but consistently lists Azure PowerShell before Azure CLI in both the text and link order. In the 'Alternate way to get the Azure Container Instance ID' section, the PowerShell example is given before the Azure CLI example. There are no Linux-specific examples or references to Linux tools, and the documentation does not mention platform-specific considerations for Linux users. The screenshots and instructions are focused on the Azure portal, which is platform-neutral, but command-line examples and ordering show a subtle Windows bias.
Recommendations
- Alternate the order of Azure CLI and PowerShell examples throughout the documentation, or list Azure CLI first to improve parity for Linux users.
- Explicitly mention that both Azure CLI and PowerShell are cross-platform, and clarify usage on Linux/macOS where relevant.
- Add a note or section highlighting Linux usage patterns, such as installing Azure CLI on Linux and running commands in Bash.
- Where possible, provide Bash script examples for multi-step operations, not just single CLI commands.
- Review all command-line instructions and ensure equal prominence and detail for Azure CLI and PowerShell, including troubleshooting steps for both environments.
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 when starting Cloud Shell, but consistently lists PowerShell alongside or immediately after Bash. Examples for Azure CLI (Linux-friendly) and Azure PowerShell (Windows-centric) are provided in parallel, but PowerShell is given equal prominence throughout, and some advanced PowerShell-specific features (like the Azure drive) are highlighted without Linux equivalents. The 'Next steps' section lists Azure PowerShell before Azure CLI, subtly prioritizing Windows tooling.
Recommendations
- Ensure Bash/Linux examples are presented first or in parallel, not after PowerShell.
- Add Linux/Bash equivalents for advanced PowerShell features (e.g., navigating resources with the Azure drive).
- Balance the order in 'Next steps' to list Azure CLI before or alongside Azure PowerShell.
- Explicitly mention that both Bash and PowerShell are fully supported and clarify any feature parity or differences.
- Where screenshots or instructions reference PowerShell-specific features, add notes or alternatives for Bash users.
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 presents both Azure CLI and Azure PowerShell options for resource group and virtual network creation, but consistently lists Azure PowerShell before Azure CLI in both the text and reference links. The alternate way to get the Azure Container Instance ID provides the PowerShell example first, followed by the Azure CLI example. There are no Linux-specific tools or shell examples (e.g., Bash scripts), and the documentation does not mention Linux or Windows explicitly, but the ordering and emphasis suggest a slight Windows/PowerShell bias.
Recommendations
- Alternate the order of Azure CLI and PowerShell examples and links, or present CLI examples first to improve parity for Linux users.
- Explicitly mention that both Azure CLI and PowerShell are cross-platform, and clarify which commands work natively on Linux and macOS.
- Include Bash script examples for common tasks, or reference Bash usage where appropriate.
- Add a note or section on using Cloud Shell from Linux environments, including any platform-specific considerations.
- Ensure screenshots and UI references do not assume Windows usage (e.g., avoid PowerShell-centric imagery unless balanced with CLI/Bash).
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/get-started/existing-storage.md
...n/articles/cloud-shell/get-started/existing-storage.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Bash (Azure CLI) and PowerShell options for interacting with Azure Cloud Shell, but PowerShell examples and references are given equal prominence to Bash, with some sections (such as 'Next steps') listing PowerShell before CLI. There is a slight tendency to mention or demonstrate PowerShell (a Windows-centric tool) at parity or before Linux-native alternatives, and some PowerShell-specific features (like the Azure drive) are described without Linux equivalents.
Recommendations
- Ensure that Bash/Azure CLI examples are presented first, or alternate the order to avoid implicit prioritization.
- Add explicit notes about Linux-native equivalents for features described only in PowerShell (e.g., navigating resources via file system paths).
- Where PowerShell-specific features are mentioned, clarify their availability or alternatives in Bash environments.
- In 'Next steps', list Azure CLI and Bash resources before PowerShell to avoid Windows-first perception.
- Consider including a brief explanation of the differences between Bash and PowerShell environments, especially for users on Linux.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI (Bash) and Azure PowerShell examples, but there is a subtle Windows bias: PowerShell is consistently mentioned alongside Bash, and sometimes appears first in lists and next steps. The 'Next steps' section lists PowerShell before CLI, and there is a notable focus on PowerShell-specific navigation (e.g., 'Azure drive', 'cd Azure:/...'), which is not paralleled with Bash/Linux equivalents. There are no explicit Linux-only examples or tools, and the documentation does not highlight Linux-native patterns or features.
Recommendations
- Alternate the order of Azure CLI (Bash) and PowerShell examples throughout the documentation to avoid always listing PowerShell first.
- In the 'Next steps' section, list Azure CLI before Azure PowerShell, or present them in parallel.
- Provide Bash/Linux-native navigation examples where PowerShell-specific navigation is shown (e.g., show how to list or navigate resources using Bash/CLI).
- Explicitly mention that Bash in Cloud Shell is a Linux environment and highlight any Linux-specific features or tips.
- Ensure screenshots and instructions are balanced between Bash and PowerShell, and avoid PowerShell-specific terminology unless also providing Bash equivalents.
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
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation shows a mild Windows bias, primarily through the consistent mention of Azure PowerShell alongside Azure CLI in every release note, and by referencing PowerShell-specific tools and links. Additionally, some documentation links and tabs default to PowerShell, and Windows/PowerShell tools are often listed before Linux-native or cross-platform alternatives. However, the document does acknowledge Linux (e.g., Azure Linux base image, Linux tools like Inspektor Gadget), and there are no outright missing Linux examples or exclusive use of Windows tools.
Recommendations
- Ensure that documentation links and tab defaults include both Bash and PowerShell options, or default to a neutral/cross-platform view.
- When listing tool updates, alternate the order of Azure CLI and Azure PowerShell, or group them as 'cross-platform' and 'PowerShell' to clarify parity.
- Provide explicit mention of Bash/Linux shell support and examples where relevant, especially in installation or usage instructions.
- Highlight Linux-native tools and changes with equal prominence as Windows/PowerShell tools.
- Audit all reference links to ensure they are not PowerShell-specific unless necessary, and provide equivalent Bash/Linux references when available.
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 presents both Bash and PowerShell as options in Azure Cloud Shell, but there is a subtle Windows bias. PowerShell and Azure PowerShell are mentioned alongside or before Bash and Azure CLI in several sections, 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 explicit mention of Bash scripting or Linux tooling. There are no explicit Linux command examples or references to Linux-specific tools, though it is noted that user permissions are those of a regular Linux user.
Recommendations
- Ensure that Bash and Azure CLI are mentioned before or alongside PowerShell in all relevant sections to avoid a 'Windows-first' impression.
- Include explicit references to Bash scripting and Linux command-line tools in the description of the Cloud Shell environment and editor.
- Provide links to Bash scripting or Linux command-line documentation, not just Azure CLI and PowerShell.
- When listing access points or features, alternate the order of Bash/Azure CLI and PowerShell to ensure parity.
- Add examples or references that highlight Linux tooling or workflows, such as using common Linux utilities within Cloud Shell.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation shows a mild Windows bias by consistently listing Azure PowerShell updates alongside Azure CLI updates, sometimes mentioning PowerShell first or with more detail. The link for 'Get started with Azure Cloud Shell ephemeral sessions' defaults to the PowerShell tab, and some references (such as release notes) link directly to PowerShell-specific pages. However, the content overall is fairly cross-platform, with explicit mention of Azure Linux and Linux-specific tools, and there are no exclusive Windows-only tools or examples.
Recommendations
- When referencing features or tools available in both Bash and PowerShell, alternate the order in which they are mentioned, or mention both equally.
- Provide links to both Bash and PowerShell documentation/tabs where possible, or use a neutral landing page.
- Ensure that examples, instructions, and references are not PowerShell-specific unless the feature is exclusive to PowerShell.
- Highlight Linux-specific changes or tools with the same prominence as Windows/PowerShell updates.
- In link references, avoid defaulting to PowerShell tabs unless contextually appropriate; consider using a selector or neutral default.
Cloud Shell
How to use the new user interface for Azure Cloud Shell
.../blob/main/articles/cloud-shell/new-ui-shell-window.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally treats Windows, Linux, and macOS equally, with explicit instructions for all three platforms in the copy/paste section. However, in the copy/paste instructions, Windows is listed first, followed by macOS and Linux, which is a minor example of 'windows_first' bias. No sections are Windows-only, and no Windows-specific tools or patterns are mentioned exclusively.
Recommendations
- List platform instructions in alphabetical order (Linux, macOS, Windows) or group them in a way that does not prioritize Windows.
- Continue to ensure all platform-specific instructions are present and equally detailed.
- Review other sections for subtle ordering bias and adjust for parity.
Cloud Shell
Get started with Azure Cloud Shell
.../blob/main/articles/cloud-shell/get-started/classic.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI (Bash) and Azure PowerShell examples, but PowerShell is consistently given equal prominence and sometimes appears first in sections and links. There is a slight bias toward Windows/PowerShell, such as listing PowerShell as a shell environment option alongside Bash, and including PowerShell-specific commands and navigation (e.g., 'Azure:/My Subscription/WebApps'). However, Linux/Bash users are not blocked from completing any tasks, as Azure CLI examples are provided throughout.
Recommendations
- Ensure Azure CLI (Bash) examples are presented first in each section to reflect the default shell for many Linux/macOS users.
- Add explicit notes clarifying that all CLI commands work in Bash on Linux/macOS, and that PowerShell is optional.
- Where PowerShell navigation is described (e.g., 'Azure:/My Subscription/WebApps'), provide equivalent Azure CLI navigation or clarify that this is a PowerShell-only feature.
- Balance the 'Next steps' links by listing Azure CLI resources before PowerShell, or grouping them together neutrally.
Cloud Shell
Get started with Azure Cloud Shell using persistent storage
...b/main/articles/cloud-shell/get-started/new-storage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash (Linux/macOS) and PowerShell (Windows) options for Cloud Shell, but PowerShell is consistently mentioned alongside or before Bash. Examples for Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) are given equal prominence, but some sections (such as the 'Next steps') list PowerShell before CLI, and PowerShell-specific navigation (like 'Azure:/My Subscription/WebApps') is described in detail, which is not applicable to Bash users. There is a slight preference for Windows/PowerShell tools and patterns.
Recommendations
- Alternate the order of Bash/Azure CLI and PowerShell examples to avoid implicit prioritization.
- Add equivalent Bash navigation examples for context-specific command discovery, if available.
- Ensure 'Next steps' links present CLI and PowerShell resources with equal visibility.
- Clarify which features or commands are exclusive to PowerShell and provide Bash/CLI alternatives where possible.
Cloud Shell
Get started with Azure Cloud Shell using existing storage
...n/articles/cloud-shell/get-started/existing-storage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples for most commands, maintaining reasonable parity. However, PowerShell is mentioned alongside Bash at every step, and in some sections (e.g., 'Next steps'), Azure PowerShell is listed before Azure CLI. The examples and screenshots do not show Linux-specific tools or workflows, and there is a slight tendency to present PowerShell options first or equally, which may subtly reinforce Windows-centric usage patterns.
Recommendations
- Ensure that Bash/Azure CLI examples are presented before PowerShell examples, especially in introductory sections.
- Include explicit references to Linux/macOS compatibility, such as mentioning that Bash/CLI works natively on these platforms.
- Add screenshots or notes showing Cloud Shell usage from Linux/macOS environments, not just the Azure Portal.
- Consider adding a brief section on differences or considerations for Linux/macOS users, such as file paths or shell behaviors.
- Balance 'Next steps' links by listing Azure CLI before PowerShell or presenting them together.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions both Bash and PowerShell as options in Azure Cloud Shell, but PowerShell is referenced first in several places (e.g., in the shell selection, examples, and links). The access points and integrated editor are described with a focus on Azure PowerShell and CLI, but PowerShell is often listed before Bash. There are no explicit Linux-only examples or tools highlighted, and the documentation does not provide Linux-specific usage patterns or parity details. However, it does clarify that the underlying environment is Linux and Bash is available.
Recommendations
- Alternate the order of Bash and PowerShell mentions to avoid implicit prioritization.
- Provide explicit examples or references for Bash usage alongside PowerShell.
- Highlight Linux-native tools and workflows available in Cloud Shell.
- Include links to Bash-specific documentation and usage guides.
- Clarify that the environment is Linux-based and describe any Linux-specific features or limitations.
Cloud Shell
Using the Azure Cloud Shell window
...ob/main/articles/cloud-shell/using-the-shell-window.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains cross-platform neutrality, describing Cloud Shell features in a UI-centric way. The only notable bias is in the 'Copy and paste' section, where Windows instructions are listed first, followed by macOS and Linux. No exclusive use of Windows tools, PowerShell, or missing Linux examples is present.
Recommendations
- Rotate or randomize the order of platform instructions (e.g., sometimes list Linux first).
- Explicitly state that all features are available on both Bash and PowerShell environments, and clarify any differences if they exist.
- Where platform-specific shortcuts are listed, consider grouping them in a table for parity and clarity.
Cloud Shell
Deploy Azure Cloud Shell in a virtual network with quickstart templates
...docs/blob/main/articles/cloud-shell/vnet/deployment.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation generally maintains cross-platform parity by referencing both Azure CLI and Azure PowerShell for resource creation tasks. However, there is a subtle Windows bias: PowerShell is often mentioned before Azure CLI, and the 'Alternate way to get the Azure Container Instance ID' section presents the PowerShell command before the Azure CLI command. There are no Linux- or macOS-specific instructions or screenshots, and the use of PowerShell as a primary example may create friction for non-Windows users. There are no Windows-only tools or instructions, but the ordering and emphasis slightly favor Windows/PowerShell users.
Recommendations
- Alternate the order of Azure CLI and PowerShell instructions throughout the documentation, or present Azure CLI first, as it is cross-platform.
- Explicitly state that both Azure CLI and PowerShell are supported on all major platforms (Windows, Linux, macOS).
- Where possible, provide screenshots or notes relevant to Linux/macOS users (e.g., terminal examples, CLI installation guidance).
- Add a brief section or note clarifying that all command-line examples work on Linux/macOS as well as Windows, especially for Azure CLI.
- Consider including Bash shell examples for common tasks, as Cloud Shell supports Bash.