Data Share

64
Total Pages
62
Linux-Friendly Pages
2
Pages with Bias
3.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

7 issues found
Showing 1-7 of 7 flagged pages
Data Share Tutorial: Share outside your org - Azure Data Share ...-docs/blob/main/articles/data-share/share-your-data.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides Azure Portal, Azure CLI, and PowerShell instructions for all major steps. However, the PowerShell examples and references are notably Windows-centric, including file path examples (e.g., D:\testFiles) and references to local memory, which are specific to Windows environments. PowerShell is presented as a primary automation option alongside Azure CLI, but there is no mention of Bash, shell scripting, or Linux/macOS-specific workflows. Additionally, the PowerShell tab is present before any mention of Linux alternatives, and some instructions (such as uploading files) use Windows-style paths and patterns.
Recommendations
  • Add Bash or shell script examples for Linux/macOS users, especially for file upload and automation tasks.
  • Use platform-neutral file path examples (e.g., /home/user/testFiles/textfile.csv) alongside Windows paths.
  • Clarify that PowerShell Core is cross-platform and provide instructions for using it on Linux/macOS.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide any necessary setup steps.
  • Consider reordering examples so that platform-neutral (CLI) instructions appear before Windows-specific (PowerShell) ones.
GitHub Create Pull Request
Data Share Tutorial: Accept & receive data - Azure Data Share ...ob/main/articles/data-share/subscribe-to-data-share.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides parallel instructions for Azure Portal, Azure CLI, and PowerShell. However, PowerShell examples and terminology are prominent throughout, and PowerShell is a Windows-centric tool. Several example commands reference Windows file paths (e.g., D:\testFiles), and PowerShell is presented as a primary automation method. There is no mention of Bash or Linux-native scripting for local automation, nor are Linux/macOS-specific considerations (such as file path formats or shell differences) addressed. PowerShell is described as usable in Azure Cloud Shell (which supports Bash), but local usage examples are Windows-specific.
Recommendations
  • Add Bash shell examples alongside PowerShell for all automation steps, especially for local scripting.
  • When showing file upload examples, use cross-platform file paths (e.g., /home/user/testFiles/textfile.csv) or clarify platform differences.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and provide guidance for those environments.
  • Avoid presenting PowerShell as the default or primary scripting tool; give equal prominence to Bash/CLI workflows.
  • Include notes or links for Linux/macOS users regarding prerequisites, environment setup, and troubleshooting.
GitHub Create Pull Request
Data Share Tutorial: Share outside your org - Azure Data Share ...-docs/blob/main/articles/data-share/share-your-data.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell, with PowerShell examples and references to Windows file paths (e.g., D:\testFiles) and tools. PowerShell is a Windows-centric tool, and the file upload example assumes a Windows filesystem. There is no explicit Linux/macOS shell example (e.g., Bash), nor are Linux-specific considerations (like file paths or shell commands) addressed. The order of examples often places PowerShell before or alongside CLI, and the PowerShell section references running commands locally or in Azure Cloud Shell, but the local example is Windows-oriented.
Recommendations
  • Add explicit Bash/Linux/macOS shell examples for all CLI steps, including file upload (e.g., using az storage blob upload or equivalent).
  • Replace or supplement Windows file path examples (e.g., D:\testFiles) with Linux/macOS equivalents (e.g., /home/user/testFiles).
  • Clarify that Azure CLI commands work cross-platform and provide guidance for Linux/macOS users where differences exist.
  • Mention Linux/macOS prerequisites or considerations, such as installing Azure CLI or using Azure Cloud Shell from non-Windows environments.
  • Reorder examples to present CLI/Bash before PowerShell, or provide parity in example ordering.
GitHub Create Pull Request
Data Share Tutorial: Accept & receive data - Azure Data Share ...ob/main/articles/data-share/subscribe-to-data-share.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. PowerShell examples are given equal prominence to Azure CLI, but PowerShell is a Windows-centric tool, and several examples (e.g., file upload using Set-AzStorageBlobContent) use Windows file paths (D:\testFiles\textfile.csv) without mentioning Linux/macOS equivalents. There is no explicit mention of Linux or macOS-specific instructions, nor are there Bash or shell script examples for local environments. The CLI examples are cross-platform, but the documentation does not clarify this, and PowerShell is presented as a primary automation option, which may create friction for Linux/macOS users.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and can be used on Linux/macOS/Windows.
  • Provide Bash or shell script equivalents for file upload and other operations, especially where PowerShell uses Windows file paths.
  • Include notes or examples for Linux/macOS users, such as using ~/testFiles/textfile.csv or /home/user/testFiles/textfile.csv for file paths.
  • Clarify that PowerShell Core is available on Linux/macOS, but provide guidance for users who prefer native shell environments.
  • Where possible, show CLI examples before PowerShell, or at least alternate the order to avoid Windows-first perception.
GitHub Create Pull Request
Data Share Tutorial: Share outside your org - Azure Data Share ...-docs/blob/main/articles/data-share/share-your-data.md
Low Priority View Details →
Scanned: 2026-01-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. While Azure CLI is cross-platform, PowerShell is traditionally associated with Windows, and some examples (such as file upload paths) use Windows-style paths (e.g., D:\testFiles\textfile.csv) without mentioning Linux/macOS equivalents. Additionally, PowerShell examples and references are given equal prominence to Azure CLI, and sometimes appear before CLI in the tab order, which may subtly prioritize Windows tooling. There are no explicit Linux/macOS examples (e.g., Bash, Linux file paths) for local file operations.
Recommendations
  • Add explicit Linux/macOS examples for file paths and local operations (e.g., use /home/user/testFiles/textfile.csv alongside D:\testFiles\textfile.csv).
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and highlight any OS-specific considerations.
  • Consider adding Bash examples for common operations, especially for file uploads to Azure Storage.
  • When showing PowerShell examples, note that PowerShell Core is available cross-platform, but provide guidance for Linux/macOS users where relevant.
  • Ensure tab order does not always put PowerShell before CLI, or clarify that CLI is the recommended cross-platform approach.
GitHub Create Pull Request
Data Share Tutorial: Share outside your org - Azure Data Share ...-docs/blob/main/articles/data-share/share-your-data.md
Low Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. While Azure CLI is cross-platform, the PowerShell examples and instructions are prominent, and some file path examples (e.g., 'D:\testFiles\textfile.csv') use Windows conventions. PowerShell is shown as a first-class option, and Windows-style file paths are used in upload examples, which may create friction for Linux/macOS users. However, Azure CLI is available and fully supported, mitigating most issues.
Recommendations
  • Add explicit notes that Azure CLI commands work on Linux/macOS and Windows.
  • When showing file upload examples, include Linux/macOS path examples (e.g., '/home/user/testFiles/textfile.csv') alongside Windows paths.
  • Clarify that PowerShell can be used on macOS/Linux via PowerShell Core, or recommend Azure CLI for those platforms.
  • Avoid using only Windows-style file paths in code samples; provide both formats or use generic placeholders.
  • Consider listing Azure CLI before PowerShell in tabbed examples to emphasize cross-platform parity.
GitHub Create Pull Request
Data Share Tutorial: Share outside your org - Azure Data Share ...-docs/blob/main/articles/data-share/share-your-data.md
Low Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides parallel examples for Azure Portal, Azure CLI, and PowerShell, but PowerShell is given equal prominence to Azure CLI and is described as usable both locally and in Azure Cloud Shell. Some PowerShell examples reference Windows file paths (e.g., D:\testFiles\textfile.csv), which may confuse Linux/macOS users. There is no explicit mention of Linux/macOS alternatives for file upload or local file path conventions. The CLI examples are cross-platform, but PowerShell's presence and Windows-centric file paths create minor friction for non-Windows users.
Recommendations
  • Clarify that PowerShell commands can be run in Azure Cloud Shell (which is cross-platform) and/or locally on any OS with PowerShell Core.
  • For file upload examples, provide Linux/macOS path examples (e.g., /home/user/testFiles/textfile.csv) alongside Windows paths.
  • Explicitly state that Azure CLI is fully cross-platform and recommend it for Linux/macOS users.
  • Add notes or links for installing PowerShell Core on Linux/macOS if users prefer PowerShell.
  • Where local file operations are shown, mention OS-specific conventions or provide alternative commands for Linux/macOS.
GitHub Create Pull Request