Cloud Shell

19
Total Pages
9
Linux-Friendly Pages
10
Pages with Bias
52.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (14)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/vnet/how-to-use-private-endpoint-storage.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/new-ui-shell-window.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/release-notes.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/features.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation page for Azure Cloud Shell exhibits a moderate Windows bias. While it acknowledges the Linux foundation of Cloud Shell and lists many Linux tools, it gives prominent and repeated attention to PowerShell features (such as the Azure drive and PowerShell-specific modules), lists Windows/PowerShell tools and examples before or more prominently than their Linux equivalents, and highlights Microsoft-centric (often Windows-first) tools. Some features, such as the Azure drive, are described only for PowerShell with no Bash/Linux equivalent mentioned.
Recommendations:
  • Provide equivalent Bash/Linux examples or features alongside PowerShell-specific features (e.g., explain how to navigate Azure resources in Bash, if possible).
  • Balance the order of tool listings so that Linux/Bash tools are not always listed after PowerShell/Windows tools.
  • Highlight cross-platform capabilities and clarify when features are PowerShell-only versus available in Bash.
  • Include more Bash/Linux-centric usage scenarios and examples, especially for Azure resource management.
  • Where PowerShell modules are listed, consider also listing popular Bash/Linux tools or scripts for the same tasks.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/faq-troubleshooting.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a moderate Windows bias. PowerShell and Windows-specific features (such as the Azure: drive and PowerShell provider) are discussed in detail, with Windows/PowerShell examples and terminology often appearing before or instead of Linux equivalents. Some troubleshooting and usage scenarios focus on Windows tools or workflows, and Linux/Bash examples are less prominent or missing in some sections.
Recommendations:
  • Ensure that for every PowerShell example, an equivalent Bash/Linux example is provided and given equal prominence.
  • When discussing features like the Azure: drive (PowerShell-specific), clarify their absence or alternatives in Bash/Linux environments.
  • In sections where browser developer tools are referenced, include instructions for Firefox and Linux browsers, not just Edge/Chrome (which are more common on Windows/macOS).
  • When listing keyboard shortcuts, consider listing Linux before or alongside Windows, or group them without implied priority.
  • Review troubleshooting steps to ensure they are platform-agnostic or provide platform-specific guidance for both Windows and Linux users.
  • Highlight any differences in experience or limitations for Linux users explicitly, so expectations are clear.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/cloud-shell-predictive-intellisense.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation is heavily focused on PowerShell and its modules (PSReadLine, Az.Tools.Predictor), with all examples and instructions using PowerShell cmdlets and concepts. There are no references to Bash or Linux-native shells, nor are there equivalent examples for users who might use Bash in Azure Cloud Shell. The documentation assumes the user is operating in a PowerShell environment, which is more closely associated with Windows, and does not mention or provide parity for Linux/Bash users.
Recommendations:
  • Add equivalent instructions and examples for Bash users in Azure Cloud Shell, such as how to enable or configure command prediction features in Bash (e.g., using 'bash-preexec', 'bash-completion', or 'fzf').
  • Explicitly state at the beginning that the instructions are specific to PowerShell and provide links or references to documentation for Bash users.
  • Where possible, provide side-by-side examples for both PowerShell and Bash to ensure Linux users are equally supported.
  • Mention any limitations or differences in predictive features between PowerShell and Bash in Azure Cloud Shell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/get-started/classic.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/using-the-shell-window.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/faq-troubleshooting.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation displays a moderate Windows bias. PowerShell and Windows-specific concepts (such as the Azure: drive and PowerShell provider) are explained in detail, with Windows copy/paste shortcuts listed first and PowerShell examples provided alongside Bash. Windows tools and browser instructions (Edge/Chrome) are prioritized, while Linux is mentioned but less emphasized. Some features, like the Azure: drive, are described only in the context of PowerShell, with no Linux/Unix shell equivalent discussed.
Recommendations:
  • Ensure Linux/Bash examples are always provided alongside PowerShell, and consider listing Bash examples first or equally.
  • When describing features like the Azure: drive, clarify their relevance (or lack thereof) for Bash/Linux users.
  • Provide Linux-specific troubleshooting steps or notes where applicable, not just Windows/PowerShell-centric guidance.
  • Balance browser instructions to include Firefox/Linux-specific steps, not just Edge/Chrome.
  • Where Windows tools or patterns are mentioned, ensure Linux equivalents are also explained (e.g., file system access, command-line tools).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/features.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation page demonstrates a moderate Windows bias, primarily through a heavy emphasis on PowerShell features (such as the Azure drive and numerous PowerShell modules), listing Windows-centric tools (like Exchange Online PowerShell, Microsoft Graph PowerShell, and SqlServer PowerShell modules), and often mentioning PowerShell before Bash or Linux equivalents. While Linux tools and shells are acknowledged, the documentation gives more prominence to PowerShell and Windows-oriented workflows.
Recommendations:
  • Provide equivalent Bash/Linux examples for features highlighted with PowerShell (e.g., show how to navigate Azure resources using Azure CLI in Bash, not just Azure drive in PowerShell).
  • Balance the listing of tools by including more Linux-native or cross-platform tools alongside PowerShell modules (e.g., mention Azure CLI and Bash scripts before or alongside PowerShell cmdlets).
  • Clarify which features are exclusive to PowerShell and which are available in Bash, and provide guidance for Linux users where functionality differs.
  • Include more Linux/Bash-focused productivity and scripting examples, especially in sections where PowerShell is featured.
  • Reorder tool and feature lists to alternate or group by platform, rather than consistently leading with PowerShell/Windows tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/cloud-shell-predictive-intellisense.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation is heavily focused on PowerShell and its modules (PSReadLine, Az.Tools.Predictor), with all examples and instructions provided exclusively in PowerShell syntax. There is no mention of Bash or Linux shell equivalents, nor are alternative tools or predictive features for non-PowerShell environments discussed. The guidance assumes the user is operating within a PowerShell-centric workflow, which, while available in Azure Cloud Shell, does not address users who prefer or require Bash or other Unix shells.
Recommendations:
  • Add equivalent examples and instructions for Bash users in Azure Cloud Shell, such as how to enable or configure command prediction features (e.g., bash-completion, fish shell suggestions, or other relevant tools).
  • Explicitly mention the availability (or lack) of predictive IntelliSense features in Bash or other shells within Cloud Shell, and provide links or references to documentation for those environments.
  • Balance the documentation structure so that both PowerShell and Bash/Linux users can easily find relevant information, possibly by splitting sections or providing parallel instructions.
  • If predictive features are not available in Bash, state this clearly and suggest any workarounds or alternative productivity tools for Linux shell users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/persisting-shell-storage.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation provides detailed PowerShell command examples (Get-CloudDrive, Dismount-CloudDrive) for managing Azure Cloud Shell storage, but does not include equivalent Bash or Linux shell commands. The only explicit command-line examples are in PowerShell, and the section 'Use PowerShell commands' is present without a corresponding 'Use Bash commands' section. This creates a Windows/Powershell bias and may disadvantage users of the Bash environment in Cloud Shell.
Recommendations:
  • Add equivalent Bash/Azure CLI command examples for all PowerShell commands shown (e.g., show how to get file share info and unmount clouddrive using Bash/Azure CLI).
  • Include a 'Use Bash commands' section parallel to the 'Use PowerShell commands' section.
  • When introducing command-line examples, present both PowerShell and Bash/Azure CLI commands side-by-side or indicate which environment each applies to.
  • Review the documentation for any other sections where only Windows/Powershell tools or patterns are mentioned, and add Linux/Bash equivalents where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-shell/release-notes.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.