Business Continuity Center

19
Total Pages
18
Linux-Friendly Pages
1
Pages with Bias
5.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (2)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/business-continuity-center/tutorial-manage-data-using-copilot.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation demonstrates a Windows bias by consistently referencing PowerShell scripts and 'Command tools (PowerShell/CLI)' as the primary or only command-line automation option. PowerShell is mentioned explicitly and repeatedly, while Linux-native tools or Bash examples are not provided. Where CLI is mentioned, it is always paired with PowerShell, and no explicit Linux/Bash command examples or screenshots are shown. There is no mention of Linux-specific workflows, and all automation appears to assume a Windows-centric environment.
Recommendations:
  • Provide explicit Bash/Azure CLI command examples alongside PowerShell, especially in sections where scripts are offered for download.
  • Include screenshots or instructions that demonstrate the process on Linux or macOS terminals, not just Windows/PowerShell environments.
  • When referencing 'Command tools (PowerShell/CLI)', clarify that Azure CLI is cross-platform and provide parity in examples for both Windows (PowerShell) and Linux/macOS (Bash).
  • Add a note or section for Linux users, highlighting any differences or additional steps required for common scenarios.
  • Ensure that downloadable scripts are available in both PowerShell (.ps1) and Bash (.sh) formats where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/business-continuity-center/tutorial-manage-data-using-copilot.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 repeatedly references PowerShell scripts and command-line tools as the primary or only automation method, with no explicit mention or examples of Linux shell (bash) equivalents. When command-line options are offered, 'PowerShell/CLI' is the phrasing used, but all screenshots and script references are PowerShell-centric. There are no bash, Azure CLI (in bash), or Linux-specific instructions or screenshots, and no mention of Linux environments or considerations.
Recommendations:
  • Provide explicit Azure CLI (bash) script examples alongside PowerShell scripts, especially for automation tasks like triggering backups or changing security settings.
  • When offering 'Command tools (PowerShell/CLI)' as an option, clarify and show both PowerShell and bash/Azure CLI usage, including screenshots or code blocks for each.
  • Include notes or sections addressing Linux/macOS users, specifying any differences or prerequisites for running scripts.
  • Ensure screenshots and downloadable scripts are available in both PowerShell and bash/Azure CLI formats.
  • Adopt neutral phrasing such as 'Azure CLI or PowerShell' rather than 'PowerShell/CLI', and avoid assuming PowerShell as the default automation tool.