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 76-96 of 96 flagged pages
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, but in the 'Copy and paste' section, Windows instructions are listed first, followed by macOS and Linux. No other sections show Windows-specific bias, and examples or instructions are equally applicable to all platforms.
Recommendations
- List platform instructions in alphabetical order (Linux, macOS, Windows) or group them in a way that does not prioritize Windows.
- Ensure that any platform-specific instructions or caveats are equally detailed for Linux/macOS as for Windows.
- Continue to avoid Windows-only examples or tools unless absolutely necessary, and always provide Linux/macOS equivalents.
Create Pull Request
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 parity between Windows, Linux, and macOS, especially in sections like copy/paste shortcuts. However, in the 'Copy and paste' section, Windows instructions are listed first, followed by macOS and Linux, which is a minor example of Windows-first ordering. No exclusive use of Windows tools, PowerShell-heavy examples, or missing Linux equivalents are present.
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 any platform-specific limitations or differences where relevant.
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 First
Powershell Heavy
Windows Tools
Summary
The documentation displays mild Windows bias, with Windows examples and tools (such as PowerShell and Windows key combinations) often mentioned first or in greater detail. PowerShell-specific features (like the Azure: drive and PowerShell commands) are explained, while Linux equivalents are not discussed. However, Linux and macOS are acknowledged in copy/paste shortcuts and Bash examples are present.
Recommendations
- Alternate the order of OS examples so Linux/macOS are not always listed after Windows.
- Provide equivalent Linux/macOS/Bash examples for sections that currently only mention PowerShell or Windows tools (e.g., Azure: drive).
- Include troubleshooting steps for Linux/macOS environments where applicable, not just browser/Windows-centric instructions.
- Clarify when a feature or tool is PowerShell-specific and offer Bash alternatives or note their absence.
- Ensure screenshots and tool references (like Developer Tools) include Linux/macOS browsers and workflows.
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 mentioned alongside Bash, and in some sections, PowerShell commands are given equal prominence. The 'Next steps' section lists Azure PowerShell before Azure CLI, and PowerShell-specific features (like the Azure drive) are described in detail, which may be less relevant for Linux/macOS users. However, Azure CLI (Bash) examples are present throughout, and the initial shell selection includes Bash.
Recommendations
- List Azure CLI (Bash) examples and resources before PowerShell to better reflect cross-platform usage.
- Clarify which features (e.g., Azure drive navigation) are PowerShell-only and suggest CLI equivalents or note their absence.
- Add notes or links for Linux/macOS users about differences in shell experience and capabilities.
- Ensure parity in depth of explanation for both Bash and PowerShell sections.
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 all command-line tasks, maintaining parity. However, PowerShell is consistently presented alongside Bash, and in some sections, PowerShell examples and links are listed before or equally with CLI, which may subtly reinforce Windows-centric workflows. The Next Steps section lists PowerShell before CLI, and PowerShell-specific features (like the Azure drive) are described without noting their absence in Bash. There are no sections that are Windows-only, and Linux/macOS users can complete all tasks.
Recommendations
- Alternate the order of CLI and PowerShell examples, or list CLI first to avoid subtle Windows-first bias.
- Explicitly note when features (like the Azure drive) are PowerShell-specific and not available in Bash.
- Ensure Next Steps and resource links present CLI and PowerShell with equal prominence.
- Consider adding a brief note on platform neutrality, emphasizing that Cloud Shell supports both Bash (Linux/macOS) and PowerShell (Windows) environments.
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 options for Cloud Shell, but PowerShell examples and terminology are given equal prominence to Bash, and in some sections (e.g., Next Steps), PowerShell is listed before CLI. There is a slight tendency to mention Windows/PowerShell patterns first or equally, which may create friction for Linux/macOS users who primarily use Bash/CLI.
Recommendations
- Ensure Bash/Azure CLI examples are presented first, as Bash is the default shell for many Linux/macOS users.
- Add explicit notes clarifying that Bash/CLI is cross-platform and often preferred on Linux/macOS.
- In the Next Steps section, list Azure CLI resources before PowerShell, or group them together with clear platform guidance.
- Where screenshots or instructions reference PowerShell, provide parallel Bash/CLI visuals and steps.
- Consider a short section explaining shell choice implications for different operating systems.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions both Bash and PowerShell as Cloud Shell options, but PowerShell and Windows-centric tools (e.g., Azure PowerShell, Visual Studio Code) are referenced before Bash/Linux equivalents. The access points and examples prioritize Windows/PowerShell documentation links over Azure CLI (Bash) links. There are no explicit Linux-only examples or tools highlighted, and the integrated editor is described in terms of Azure CLI or PowerShell, without mention of Linux-native editors.
Recommendations
- Present Bash and PowerShell options with equal prominence, alternating which is listed first.
- Include explicit references to Linux-native tools and workflows (e.g., Vim, Nano, or other editors available in Cloud Shell).
- Add links to Azure CLI documentation before or alongside Azure PowerShell documentation.
- Highlight Linux/macOS compatibility and usage patterns where relevant.
- Provide example workflows for both Bash and PowerShell, ensuring 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
Missing Linux Example
Summary
The documentation generally maintains cross-platform parity but exhibits mild Windows bias in a few areas. In sections where both Azure CLI and PowerShell are referenced, PowerShell is often mentioned before CLI, and in the 'Alternate way to get the Azure Container Instance ID' section, the PowerShell example is given before the Azure CLI example. Additionally, the command-line examples do not explicitly mention Linux/macOS environments or provide Bash-specific context, and there are no screenshots or instructions tailored to non-Windows users.
Recommendations
- Present Azure CLI (cross-platform) examples before PowerShell examples, as CLI is more commonly used on Linux/macOS.
- Explicitly state that Azure CLI commands work on Linux/macOS/Windows, and PowerShell is available cross-platform but more familiar to Windows users.
- Include Bash shell context or notes for Linux/macOS users where appropriate.
- Add screenshots or instructions for Linux/macOS environments where UI or terminal differences may exist.
- Ensure parity in all command-line examples, and avoid defaulting to Windows-first ordering.
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, but in the 'Copy and paste' section, Windows instructions are presented first, followed by macOS and Linux. There are no exclusive Windows/Powershell examples or tools, and both Bash and PowerShell environments are mentioned equally. However, the ordering of platforms in the keyboard shortcut instructions reflects a subtle 'windows_first' bias.
Recommendations
- Present platform-specific instructions in alphabetical order (Linux, macOS, Windows) or group them in a way that does not always prioritize Windows.
- Where possible, provide parallel examples or notes for both Bash and PowerShell environments, especially if there are environment-specific behaviors.
- Explicitly mention Linux and macOS support in introductory sections to reinforce parity.
- Review other sections for subtle ordering or phrasing that may unintentionally prioritize Windows.
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 parity between Bash and PowerShell environments and provides platform-specific instructions for copy/paste operations. However, in the 'Copy and paste' section, Windows instructions are presented first, followed by macOS and Linux, which may suggest a subtle Windows-first bias. No PowerShell-heavy examples, exclusive mention of Windows tools, or missing Linux examples were found.
Recommendations
- Present platform instructions in alphabetical order (e.g., Linux, macOS, Windows) or group them together to avoid implicit prioritization.
- Ensure that examples and instructions for Bash and PowerShell are given equal prominence throughout the documentation.
- Explicitly mention Linux-specific behaviors or shortcuts where relevant, especially in sections discussing terminal interactions.
- Review other sections for subtle ordering biases and consider rotating or randomizing the order in which platforms are presented.
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 is generally cross-platform and neutral, but in the 'Copy and paste' section, Windows instructions are listed first, followed by macOS and then Linux. There are no missing Linux examples or exclusive references to Windows tools or PowerShell. The rest of the document uses neutral language and examples (e.g., Bash and PowerShell are both mentioned as Cloud Shell environments, file paths use Linux-style paths, and no Windows-specific tools are referenced).
Recommendations
- Rotate or randomize the order of platform-specific instructions (e.g., sometimes list Linux first, or group by popularity/usage statistics).
- Explicitly state that the order of instructions does not imply priority or importance.
- Where possible, provide side-by-side tables for platform-specific shortcuts to avoid perceived prioritization.
- Continue to ensure that both Bash and PowerShell are equally represented in examples and explanations.
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 parity, mentioning both Bash and PowerShell environments and providing copy/paste shortcuts for Windows, macOS, and Linux. However, in the 'Copy and paste' section, Windows shortcuts are listed first, which may indicate a subtle 'windows_first' bias in ordering. No exclusive use of Windows tools, missing Linux examples, or PowerShell-heavy content is present.
Recommendations
- List platform-specific instructions in alphabetical order (e.g., Linux, macOS, Windows) or group them in a way that does not prioritize Windows.
- Ensure that examples and instructions for Bash and PowerShell are presented with equal prominence throughout the documentation.
- Continue to explicitly mention Linux and macOS where relevant, especially for keyboard shortcuts and shell behaviors.
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, referencing both Bash and PowerShell environments and providing copy/paste shortcuts for Windows, macOS, and Linux. However, in the 'Copy and paste' section, Windows shortcuts are listed first, which may subtly prioritize Windows users. No exclusive use of Windows tools, PowerShell-heavy examples, or missing Linux examples were found.
Recommendations
- List platform-specific instructions in alphabetical order (e.g., Linux, macOS, Windows) or group them in a way that does not imply priority.
- Ensure that examples and instructions for Bash and PowerShell are presented with equal prominence throughout the documentation.
- Continue to provide explicit instructions for all supported platforms, avoiding implicit prioritization of any single OS.
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, referencing both Bash and PowerShell and providing copy/paste shortcuts for Windows, macOS, and Linux. However, in the 'Copy and paste' section, Windows instructions are listed first, which may subtly prioritize Windows users. No explicit Linux or Windows-only tools or patterns are mentioned, and both environments are acknowledged in the environment selector section.
Recommendations
- List platform-specific instructions in alphabetical order (e.g., Linux, macOS, Windows) or rotate the order to avoid implicit prioritization.
- Where possible, provide parallel examples or screenshots for both Bash and PowerShell environments to reinforce parity.
- Explicitly state that all features and instructions apply equally to both Bash and PowerShell unless there are exceptions.
- Continue to avoid referencing platform-specific tools or patterns unless necessary, and always provide Linux equivalents if Windows tools are mentioned.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/new-ui-shell-window.md
.../blob/main/articles/cloud-shell/new-ui-shell-window.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains parity between Bash and PowerShell environments, and provides copy/paste shortcuts for Windows, macOS, and Linux. However, in the 'Copy and paste' section, Windows instructions are listed first, followed by macOS and Linux, which is a subtle form of Windows-first ordering. No explicit PowerShell-heavy examples, Windows-only tools, or missing Linux examples are present. The overall content is neutral and cross-platform, but ordering could be improved for parity.
Recommendations
- List platform instructions in alphabetical order (e.g., Linux, macOS, Windows) to avoid implicit prioritization.
- Where possible, provide examples or screenshots for both Bash and PowerShell environments side-by-side.
- Explicitly mention that both Bash and PowerShell are supported equally throughout the documentation.
- Review other sections for subtle ordering or phrasing that may imply Windows preference and adjust for neutrality.
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, but in the 'Copy and paste' section, Windows instructions are listed first, followed by macOS and Linux. There are no PowerShell-heavy examples, exclusive mention of Windows tools, or missing Linux examples elsewhere. However, the ordering of OS instructions may subtly prioritize Windows users.
Recommendations
- Rotate or randomize the order of OS-specific instructions (e.g., sometimes list Linux first, or use alphabetical order) to avoid implicit prioritization.
- Where possible, provide parity in detail and clarity for all platforms.
- Explicitly state that Cloud Shell supports both Bash (Linux) and PowerShell (Windows) environments equally, and ensure examples and screenshots reflect both.
- Consider adding a brief note about the cross-platform nature of Cloud Shell at the beginning of the document.
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 and providing instructions that are not specific to any OS. However, in the 'Copy and paste' section, Windows instructions are listed first, followed by macOS and Linux, which may subtly prioritize Windows users. There are no exclusive Windows tools, PowerShell-heavy examples, or missing Linux examples elsewhere in the document.
Recommendations
- Present platform-specific instructions (such as keyboard shortcuts) in alphabetical order (Linux, macOS, Windows) or group them in a way that does not prioritize Windows.
- Where possible, provide parallel examples or screenshots for both Bash and PowerShell environments to reinforce parity.
- Explicitly mention that Cloud Shell supports both Linux (Bash) and Windows (PowerShell) environments equally in the introduction.
- Ensure that any future additions (such as troubleshooting or advanced usage) do not default to Windows-first patterns or tools.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/new-ui-shell-window.md
.../blob/main/articles/cloud-shell/new-ui-shell-window.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains platform neutrality, referencing both Bash and PowerShell environments and providing copy/paste instructions for Windows, macOS, and Linux. However, in the 'Copy and paste' section, Windows instructions are listed first, which may suggest a subtle Windows-first bias. There are no PowerShell-heavy examples, exclusive mention of Windows tools, or missing Linux examples elsewhere in the document.
Recommendations
- List platform instructions in alphabetical order (e.g., Linux, macOS, Windows) or group them in a way that does not prioritize Windows.
- Ensure that any future command-line examples or tool references provide parity between Bash/Linux and PowerShell/Windows environments.
- Explicitly mention Linux-specific behaviors or shortcuts where relevant, to reinforce equal support.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/new-ui-shell-window.md
.../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 exclusive Windows tools or PowerShell-heavy content is present, and Linux is not omitted from examples. The ordering in the keyboard shortcuts section may subtly prioritize Windows users.
Recommendations
- Rotate or randomize the order of platform-specific instructions (e.g., sometimes list Linux first, or group by usage context).
- Consider grouping all OS instructions together under a neutral heading, or use a table for parity.
- Review other sections for similar ordering and ensure Linux is not consistently listed last.
- Explicitly state that Cloud Shell is cross-platform and that all features are available regardless of the underlying OS.
Cloud Shell
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/vnet/how-to-use-private-endpoint-storage.md
...loud-shell/vnet/how-to-use-private-endpoint-storage.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only Azure Portal (GUI) instructions and does not include any command-line examples for connecting to a storage account using a private endpoint. There are no references to Windows-specific tools or PowerShell, but there is also a complete absence of CLI instructions (such as Azure CLI or Bash), which are commonly used on Linux and cross-platform environments. This omission can be considered a bias by omission, as it does not address the needs of users who prefer or require Linux or command-line workflows.
Recommendations
- Add Azure CLI (az) command-line examples for each major step, such as disabling public access, creating the private endpoint, and configuring DNS.
- Ensure that any scripts or commands provided are cross-platform (work on both Windows and Linux shells).
- Include Bash shell examples where relevant, especially for Cloud Shell users who may be using the Bash environment.
- Explicitly mention that the steps can be performed via CLI as well as the portal, and provide links to relevant CLI documentation.
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 avoids platform-specific bias, as it focuses on the Azure Cloud Shell interface, which is cross-platform. However, in the 'Copy and paste' section, Windows instructions are listed first, followed by macOS and Linux. No PowerShell-specific bias or exclusive mention of Windows tools is present, and Linux instructions are included where relevant.
Recommendations
- List copy/paste instructions in a neutral or alphabetical order (e.g., Linux, macOS, Windows) to avoid the perception of Windows-first bias.
- Where platform-specific shortcuts or behaviors are mentioned, ensure equal prominence and detail for Linux and macOS.
- Continue to avoid exclusive references to Windows tools or patterns, and ensure all examples and instructions are equally applicable to Bash/Linux and PowerShell/Windows environments.