Cloud Shell
38
Total Pages
21
Linux-Friendly Pages
17
Pages with Bias
44.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
36 issues found
Showing 26-36 of 36 flagged pages
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/security/how-to-support-multiple-users.md
.../cloud-shell/security/how-to-support-multiple-users.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides only Azure Portal (GUI) instructions for managing storage accounts and file shares, without any command-line examples. There are no examples using Azure CLI, Bash, or PowerShell, but the lack of Linux (CLI) examples is notable given that Cloud Shell is often used in Bash environments. The instructions follow a GUI workflow, which is more familiar to Windows users, and do not mention or prioritize Linux-native tools or workflows.
Recommendations
- Add Azure CLI (az) command-line examples for increasing file share quota and assigning roles, as these are cross-platform and commonly used in Linux environments.
- Explicitly mention that the steps can be performed in both Bash and PowerShell Cloud Shell environments, and provide equivalent CLI commands.
- If possible, provide PowerShell examples as well, but ensure that Azure CLI (Bash-friendly) examples are given equal or higher prominence.
- Clarify that the Azure Portal is platform-agnostic, but supplement GUI instructions with CLI alternatives to support Linux users.
- Consider adding a section or callout for automation using scripts, which is a common pattern for Linux users.
Create Pull Request
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, but PowerShell is consistently presented as an equal option to Bash, and in some cases, PowerShell-specific features (like the Azure drive and Get-AzCommand) are described in detail without Linux/macOS equivalents. The 'Next steps' section lists PowerShell before CLI, and screenshots/prompts refer to PowerShell alongside Bash, potentially giving Windows tools and patterns prominence.
Recommendations
- Ensure Bash/Azure CLI examples are presented first or in parallel with PowerShell, especially in introductory sections.
- Where PowerShell-specific features are described (e.g., Azure drive navigation), add notes about CLI/Linux equivalents or clarify that these features are PowerShell-only.
- In 'Next steps', alternate or randomize the order of CLI and PowerShell links to avoid implicit prioritization.
- Add explicit mention that Bash/CLI is cross-platform and may be preferable for Linux/macOS users.
- Include screenshots showing both Bash and PowerShell selection, or clarify that both shells are available on all platforms.
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 provides both Azure CLI (Bash) and Azure PowerShell examples for most command-line tasks, but PowerShell examples are consistently presented alongside or immediately after CLI examples, and PowerShell-specific features (like the Azure drive and Get-AzCommand) are highlighted. The 'Next steps' section lists PowerShell before CLI, and some advanced PowerShell navigation is described without Linux/Bash equivalents. There are no outright missing Linux examples, but the ordering and depth of PowerShell coverage suggest a mild Windows bias.
Recommendations
- Alternate the order of CLI and PowerShell examples, or present CLI (Bash) examples first to better reflect cross-platform usage.
- Provide Bash/Linux equivalents for advanced PowerShell navigation (e.g., show how to explore resources using CLI commands or file system navigation).
- Ensure that tips and advanced usage sections cover both Bash and PowerShell features equally.
- In 'Next steps', list CLI and PowerShell resources in parallel or alternate their order.
Low 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 references to Azure PowerShell and related documentation appear before Bash or Azure CLI in several places. The access points list puts Azure PowerShell documentation before Azure CLI, and the text editor section emphasizes deployment through Azure PowerShell and Azure CLI, with PowerShell mentioned first. There are no explicit Linux-only examples or tools highlighted, and the documentation does not provide specific Bash/Linux usage examples or parity details.
Recommendations
- Alternate the order of Bash and PowerShell mentions to avoid implicit prioritization.
- Provide explicit Bash/Linux usage examples and reference Bash documentation alongside PowerShell.
- Highlight Linux-specific tools or workflows available in Cloud Shell.
- Ensure that CLI documentation is referenced before or alongside PowerShell documentation.
- Clarify that both Bash and PowerShell are fully supported and provide parity details.
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 parity, referencing both Bash and PowerShell environments and providing copy/paste shortcuts for Windows, macOS, and Linux. However, in the 'Copy and paste' section, Windows instructions are listed first, which is a minor example of Windows-first ordering. No Windows-specific tools, patterns, or exclusive examples are present elsewhere.
Recommendations
- List platform instructions in alphabetical order (e.g., Linux, macOS, Windows) or group them in a way that does not prioritize Windows.
- Continue to ensure all features and instructions are described for all supported platforms.
- Explicitly mention Linux and macOS compatibility in introductory sections to reinforce parity.
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
Summary
The documentation generally presents both Azure PowerShell and Azure CLI options for resource group and virtual network creation, but PowerShell examples and links are consistently listed before CLI equivalents. The alternate way to get the Azure Container Instance ID provides both PowerShell and CLI commands, but PowerShell is shown first. There are no Windows-only tools or patterns, and Linux/macOS users can follow all instructions, but the ordering and emphasis may subtly favor Windows users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples and links, or present CLI examples first to improve parity for Linux/macOS users.
- Explicitly state that both CLI and PowerShell are cross-platform, and provide guidance for users on non-Windows platforms.
- Where possible, include Bash shell examples for common tasks, especially in sections referencing command-line usage.
- Add a note clarifying that all steps can be completed on Linux/macOS using the Azure CLI.
Cloud Shell
Azure Cloud Shell Frequently Asked Questions (FAQ)
.../blob/main/articles/cloud-shell/faq-troubleshooting.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page displays mild Windows bias. Windows tools (PowerShell, Microsoft Edge, nslookup) are mentioned explicitly and sometimes before their Linux/macOS equivalents. PowerShell examples are provided alongside Bash, but Windows-centric troubleshooting steps (e.g., using Edge/Chrome Developer Tools via F12) are described in detail, while Linux/macOS alternatives are referenced only generically. Windows copy/paste shortcuts are listed first. However, Linux examples are present, and most instructions are cross-platform.
Recommendations
- Provide explicit instructions for accessing Developer Tools in Firefox and Safari, not just Edge/Chrome.
- List copy/paste shortcuts in a neutral order or group by OS family.
- Include Linux/macOS equivalents for tools like nslookup (e.g., dig) and clarify that commands work across platforms.
- Ensure troubleshooting steps and screenshots include Linux/macOS scenarios where applicable.
- Balance PowerShell and Bash examples, and clarify which shell is used in each context.
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 presents both Bash (Azure CLI) and PowerShell examples, but PowerShell is mentioned alongside Bash from the start, and PowerShell-specific instructions and links are given equal prominence. There is a slight tendency to mention PowerShell and Windows-centric tools first or equally, rather than prioritizing Linux-native workflows or tools. However, Linux users are not blocked from completing any tasks, as Azure CLI (Bash) examples are provided throughout.
Recommendations
- Consider listing Bash/Azure CLI examples before PowerShell in each section to reflect the default shell for many Linux/macOS users.
- Add explicit notes clarifying that both Bash and PowerShell are available on Cloud Shell, and that Bash/Azure CLI is cross-platform.
- Ensure that screenshots and instructions do not imply a preference for PowerShell or Windows tools.
- Provide additional context or tips for Linux/macOS users, such as file path conventions or shell-specific behaviors.
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
Summary
The documentation generally presents Azure Portal (GUI), Azure CLI, and Azure PowerShell as options for resource creation and management. However, in several sections, PowerShell is listed before CLI, and the alternate way to get the Azure Container Instance ID presents the PowerShell example first. This ordering may subtly favor Windows users. There are no sections that are strictly Windows-only, and Linux/macOS users can use the Azure CLI for all operations. No Windows-specific tools or patterns are exclusively mentioned, and Linux parity is generally maintained.
Recommendations
- List Azure CLI examples before PowerShell examples to better reflect cross-platform usage.
- Ensure that all command-line examples are provided for both Azure CLI and PowerShell, with equal prominence.
- Explicitly mention that Azure CLI is available on Windows, Linux, and macOS to reinforce cross-platform support.
- Where screenshots or instructions reference the Azure Portal, clarify that the portal is web-based and OS-agnostic.
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 maintains cross-platform neutrality, but in the 'Copy and paste' section, Windows instructions are listed first, followed by macOS and Linux. No PowerShell-heavy examples or exclusive mention of Windows tools are present, and Linux parity is maintained in most areas. However, the order of platform instructions may subtly prioritize Windows.
Recommendations
- List platform instructions in alphabetical order (Linux, macOS, Windows) or group them in a way that does not imply priority.
- Where platform-specific instructions are given, ensure equal detail and visibility for Linux and macOS.
- Explicitly mention Linux/Bash features or differences where relevant, not just as an afterthought.
- Continue to avoid exclusive use of Windows tools or PowerShell examples unless necessary, and always provide Bash/Linux equivalents.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/using-the-shell-window.md
...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, referencing both Bash and PowerShell environments and providing copy/paste shortcuts for Windows, macOS, and Linux. However, in the 'Copy and paste' section, Windows instructions are listed first, which may indicate a subtle 'windows_first' bias. No exclusive use of Windows tools, missing Linux examples, or PowerShell-heavy content was found.
Recommendations
- Alternate the order of platform instructions (e.g., sometimes list Linux or macOS first) to avoid implicit prioritization of Windows.
- Explicitly state that Cloud Shell supports both Bash (Linux) and PowerShell equally in the introduction.
- Where possible, provide parity in examples and screenshots for both Bash and PowerShell environments.
- Ensure that all platform-specific instructions (e.g., keyboard shortcuts) are equally detailed and visible.