Resiliency

20
Total Pages
17
Linux-Friendly Pages
3
Pages with Bias
15.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

10 issues found
Showing 1-10 of 10 flagged pages
Resiliency Tutorial - Manage your resiliency estate efficiently using Resiliency in Azure Copilot ...icles/resiliency/tutorial-manage-data-using-copilot.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias towards Windows environments by consistently referencing PowerShell scripts as the primary automation method, especially for tasks such as triggering backups, modifying security levels, and deleting vaults. While 'CLI' is mentioned alongside PowerShell in some places, actual examples, screenshots, and downloadable scripts are exclusively PowerShell-based. There are no explicit Linux shell (bash) or Azure CLI script examples, nor is there guidance for Linux users. The ordering and phrasing also tend to mention PowerShell before CLI, reinforcing a Windows-centric approach.
Recommendations
  • Provide equivalent Azure CLI (az) command examples for all tasks currently demonstrated with PowerShell scripts.
  • Include downloadable bash scripts or instructions for Linux/macOS users where automation is referenced.
  • Ensure screenshots and walkthroughs show both PowerShell and CLI options, with clear parity.
  • When listing command tool options, alternate the order (e.g., 'CLI/PowerShell') or clarify cross-platform support.
  • Add explicit notes or sections for Linux/macOS users, including troubleshooting and environment setup guidance.
  • Review and update Copilot script generation to offer both PowerShell and Azure CLI options for all supported operations.
GitHub Create Pull Request
Resiliency Tutorial - Manage your resiliency estate efficiently using Resiliency in Azure Copilot ...icles/resiliency/tutorial-manage-data-using-copilot.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation consistently references PowerShell scripts and Windows-centric command-line tooling as the primary or sole automation method for tasks such as triggering backups, modifying security levels, and deleting vaults. There are no explicit examples or mentions of Linux-native tools (such as Bash, Azure CLI on Linux, or shell scripts), nor are Linux command-line patterns provided alongside PowerShell. The phrase 'Command tools (PowerShell/CLI)' is used, but only PowerShell scripts are shown in screenshots and download options, suggesting a Windows-first approach and a lack of Linux parity.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for all automation tasks, especially for triggering backups, modifying vault security, and deleting vaults.
  • Explicitly mention Linux support and clarify which scripts or commands can be run on Linux systems.
  • Include screenshots or walkthroughs showing the use of Azure CLI on Linux or macOS, not just PowerShell on Windows.
  • When offering downloadable scripts, provide both PowerShell (.ps1) and Bash (.sh) versions, or clarify how to adapt them for Linux environments.
  • List CLI options in a neutral order (e.g., 'CLI/PowerShell') and avoid implying PowerShell is the default or preferred choice.
  • Add troubleshooting and configuration guidance for Linux users, including common issues and environment setup.
GitHub Create Pull Request
Resiliency https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resiliency/tutorial-manage-data-using-copilot.md ...icles/resiliency/tutorial-manage-data-using-copilot.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation consistently references PowerShell scripts as the primary or sole command-line automation method, with no explicit examples or guidance for Linux users (e.g., Bash, Azure CLI on Linux, or shell scripting). When command-line options are mentioned, PowerShell is listed first or exclusively, and downloadable scripts are always PowerShell format. There is no mention of Linux-specific tools, nor are there examples or instructions for Linux environments, leading to a clear Windows/PowerShell bias.
Recommendations
  • Provide equivalent Bash or Azure CLI (cross-platform) script examples alongside PowerShell scripts for all automation steps.
  • Explicitly mention Linux support and clarify which features and scripts work on Linux, macOS, and Windows.
  • When offering downloadable scripts, allow users to choose between PowerShell and Bash/Azure CLI formats.
  • In sections referencing 'Command tools (PowerShell/CLI)', ensure CLI examples are present and not just PowerShell.
  • Add screenshots or walkthroughs showing usage from Linux terminals where relevant.
  • Review all automation and scripting guidance to ensure Linux parity and highlight any platform-specific limitations.
GitHub Create Pull Request
Resiliency https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resiliency/tutorial-manage-data-using-copilot.md ...icles/resiliency/tutorial-manage-data-using-copilot.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias toward Windows environments, primarily through the repeated use of PowerShell scripts as the default automation method for Copilot actions (such as triggering backups, deleting vaults, and modifying security levels). While 'CLI' is mentioned alongside PowerShell in some places, all concrete script examples and downloadable automation are PowerShell-based, with no Bash, Azure CLI, or Linux shell examples provided. The documentation does not show parity for Linux users or those who prefer cross-platform command-line tools, and Windows-centric tools are referenced first or exclusively throughout the page.
Recommendations
  • Provide equivalent Azure CLI (az) and Bash script examples for all actions currently demonstrated with PowerShell scripts.
  • Explicitly mention cross-platform compatibility for automation scripts and clarify which steps can be performed on Linux/macOS systems.
  • When listing command-line options, present Azure CLI and Bash examples before or alongside PowerShell to avoid Windows-first bias.
  • Include screenshots or walkthroughs using Linux terminals and tools where appropriate.
  • Add notes or sections for Linux users, highlighting any differences or additional steps required.
  • Ensure downloadable scripts are available in both PowerShell and Bash/Azure CLI formats.
GitHub Create Pull Request
Resiliency Tutorial - Manage your resiliency estate efficiently using Resiliency in Azure Copilot ...icles/resiliency/tutorial-manage-data-using-copilot.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation frequently references PowerShell scripts and provides them as the primary or sole automation method for tasks such as triggering backups, increasing security levels, and deleting vaults. There is little to no mention of Linux/macOS-specific tools or examples, and when command-line options are discussed, PowerShell is listed first or exclusively. Azure CLI is mentioned only generically, with no concrete CLI examples or scripts provided. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer bash/CLI workflows.
Recommendations
  • Provide Azure CLI (az) command examples alongside PowerShell scripts for all automation tasks.
  • Explicitly mention Linux/macOS compatibility and provide bash script equivalents where possible.
  • When offering downloadable scripts, offer both PowerShell (.ps1) and bash (.sh) versions.
  • List CLI options before or alongside PowerShell to avoid Windows-first ordering.
  • Add notes or links for installing Azure CLI and using it on Linux/macOS.
GitHub Create Pull Request
Resiliency Tutorial - Manage your resiliency estate efficiently using Resiliency in Azure Copilot ...icles/resiliency/tutorial-manage-data-using-copilot.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation consistently references PowerShell scripts as the default or only command-line automation method, especially for tasks like triggering backups, modifying security levels, and deleting vaults. There is little to no mention of Bash, Azure CLI, or Linux/macOS-specific instructions or examples. When command-line tools are referenced, PowerShell is listed first or exclusively. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Bash/CLI workflows.
Recommendations
  • Provide Azure CLI (az) command examples alongside PowerShell scripts for all automation tasks.
  • Explicitly mention Linux/macOS compatibility for command-line operations and scripts.
  • When offering downloadable scripts, allow users to choose between PowerShell and Bash/CLI formats.
  • List command-line options in a neutral order (e.g., 'CLI/PowerShell') rather than 'PowerShell/CLI'.
  • Include screenshots or walkthroughs from Linux/macOS environments where relevant.
GitHub Create Pull Request
Resiliency Create vaults to back up and replicate resources ...re-docs/blob/main/articles/resiliency/backup-vaults.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by mentioning Windows-centric backup tools (System Center Data Protection Manager, Windows Server, Azure Backup Server) exclusively when describing Recovery Services vaults. These Windows tools are listed before any Linux equivalents or general-purpose solutions, and there is no mention of Linux-native backup or replication tools. The examples and workflow descriptions do not provide parity for Linux environments, nor do they reference Linux-specific backup scenarios beyond a brief mention of 'IaaS virtual machines (Linux or Windows)'.
Recommendations
  • Include references to Linux-native backup and replication tools that integrate with Azure Recovery Services vaults, such as Azure Backup for Linux VMs, or third-party Linux backup solutions.
  • Provide examples or workflows for creating vaults specifically for Linux workloads, highlighting any differences or considerations.
  • Mention Linux backup scenarios (e.g., file-level backup, application-consistent backup for Linux workloads) alongside Windows scenarios.
  • Ensure that documentation lists Linux and Windows tools and patterns with equal prominence, or in a neutral order.
  • Add links to documentation or guides for Linux users on how to use Recovery Services vaults and Backup vaults.
GitHub Create Pull Request
Resiliency https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resiliency/backup-vaults.md ...re-docs/blob/main/articles/resiliency/backup-vaults.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits Windows bias by mentioning Windows-centric backup tools (System Center Data Protection Manager, Windows Server, Azure Backup Server) before Linux equivalents and by listing Windows workloads and tools more prominently. There is a lack of Linux-specific backup tool references, and the examples and screenshots do not demonstrate parity for Linux users.
Recommendations
  • Include references to Linux backup tools and workflows (e.g., Azure Backup for Linux VMs, integration with Linux-native backup solutions).
  • Present Linux and Windows workloads equally when describing supported vault types and use cases.
  • Add examples or screenshots that show Linux VM backup scenarios.
  • Mention Linux-specific considerations or best practices for vault creation and backup.
  • Ensure that documentation does not assume Windows-first environments and highlights cross-platform support.
GitHub Create Pull Request
Resiliency https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resiliency/quick-understand-protection-estate.md ...icles/resiliency/quick-understand-protection-estate.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation exclusively describes using the Azure portal UI and Azure Resource Graph (ARG) for identifying protected/unprotected resources, but does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash). While no explicit Windows-only tools are mentioned, the absence of Linux/CLI examples and the focus on portal-based workflows may disadvantage Linux users or those preferring cross-platform automation.
Recommendations
  • Add Azure CLI examples for querying protectable and protected resources using Azure Resource Graph, ensuring commands work on both Windows and Linux.
  • If PowerShell examples are added, ensure equivalent Bash/Azure CLI examples are provided and presented with equal prominence.
  • Explicitly mention that ARG queries can be run from any platform using Azure CLI or REST API, not just via the portal.
  • Include screenshots or terminal snippets from both Windows and Linux environments if command-line workflows are shown.
GitHub Create Pull Request
Resiliency https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resiliency/backup-vaults.md ...re-docs/blob/main/articles/resiliency/backup-vaults.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-centric backup tools (System Center Data Protection Manager, Windows Server, Azure Backup Server) before mentioning Linux workloads, and by referencing Windows tools exclusively when describing Recovery Services vault support. There are no Linux-specific backup tool examples or parity in tool mentions.
Recommendations
  • Explicitly mention Linux backup tools or patterns supported by Recovery Services vaults, such as Azure Backup for Linux VMs or integration with Linux-native backup solutions.
  • List Linux workloads and tools alongside Windows equivalents when describing supported scenarios, rather than focusing on Windows tools first.
  • Provide example workflows or screenshots for both Linux and Windows environments, ensuring parity in guidance.
  • Clarify that Recovery Services vaults support both Linux and Windows VMs equally, and highlight any Linux-specific considerations or features.
GitHub Create Pull Request