Resource Mover
19
Total Pages
9
Linux-Friendly Pages
10
Pages with Bias
52.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
57 issues found
Showing 51-57 of 57 flagged pages
Resource Mover
Support matrix for moving Azure VMs to another region with Azure Resource Mover
.../resource-mover/support-matrix-move-region-azure-vm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows VM support before Linux VM support, listing Windows operating systems and requirements first. However, both platforms receive detailed, parity-focused coverage of supported OS versions, prerequisites, and limitations. No Windows-specific tools, PowerShell examples, or exclusive instructions are present; Linux support is comprehensive and includes kernel and filesystem details.
Recommendations
- Reorder sections so that Windows and Linux VM support are presented in parallel or alphabetically, rather than Windows first.
- Explicitly state that instructions and requirements apply equally to both platforms where possible.
- Add a short introductory note clarifying that both Windows and Linux are fully supported, and that the order of presentation does not imply priority.
- If any future examples or troubleshooting steps are added, ensure both Windows and Linux commands/tools are included.
Create Pull Request
Resource Mover
Move Azure VMs across regions with Azure Resource Mover
...esource-mover/tutorial-move-region-virtual-machines.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux VMs in the prerequisites and provides links to verify support for each. However, in the 'Prepare VMs' section, instructions for updating certificates are given for Windows first ('install the latest Windows updates'), while Linux instructions are generic and listed second ('follow distributor guidance'). No command-line examples (PowerShell, Bash, etc.) are provided for either platform, and the tutorial is entirely portal-based, minimizing platform-specific bias. The order of mention and specificity slightly favors Windows.
Recommendations
- List Linux instructions before or alongside Windows instructions to avoid implicit prioritization.
- Provide more detailed Linux guidance for updating certificates, possibly with example commands for common distributions.
- Ensure parity in specificity and actionable steps for both Windows and Linux users.
- If command-line options are added in future, include both PowerShell and Bash/Azure CLI examples.
Resource Mover
Move Azure VMs across regions with Azure Resource Mover
...esource-mover/tutorial-move-region-virtual-machines.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux VM support, but in the 'Prepare VMs' section, instructions for updating certificates are given for Windows first, with explicit steps ('install the latest Windows updates'), while Linux guidance is generic ('follow distributor guidance'). No command-line examples (PowerShell, Bash) are present, and no Windows-only tools are referenced. The ordering and specificity of instructions show a subtle Windows-first bias.
Recommendations
- Provide equally detailed steps for Linux VMs, such as specific commands to update certificates and CRLs (e.g., using apt, yum, or update-ca-certificates).
- Alternate the order of Windows and Linux instructions in sections where both are relevant, or present them in parallel.
- Include links to official Linux documentation for certificate management, similar to the Windows update guidance.
- If mentioning Windows update, also mention common Linux update commands (e.g., 'sudo apt update && sudo apt upgrade').
Resource Mover
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/manage-resources-created-move-process.md
...esource-mover/manage-resources-created-move-process.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also omits command-line guidance entirely. There is no mention of Windows tools, PowerShell, or Linux equivalents. However, the lack of CLI examples (such as Azure CLI or Bash) means Linux users are not explicitly supported, which is a subtle form of bias.
Recommendations
- Add step-by-step instructions using Azure CLI commands for resource review and deletion, which are platform-neutral and widely used on Linux.
- Include examples for both PowerShell and Bash where applicable, ensuring parity between Windows and Linux environments.
- Explicitly mention that the resource management steps can be performed via the Azure Portal, Azure CLI, or PowerShell, and link to relevant documentation for each method.
Resource Mover
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/tutorial-move-region-virtual-machines.md
...esource-mover/tutorial-move-region-virtual-machines.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild Windows bias in the 'Prepare VMs' section, where instructions for ensuring up-to-date certificates and CRLs are given for Windows VMs first, with explicit mention of installing Windows updates. Linux guidance is less specific, simply referring users to distributor documentation. No command-line examples (PowerShell, Bash, CLI) are provided for either platform, and no Windows-specific tools or patterns dominate the tutorial. However, the ordering and specificity of instructions favor Windows.
Recommendations
- Provide equally detailed instructions for Linux VMs, such as example commands for updating certificates and CRLs (e.g., using 'update-ca-certificates' or 'yum update ca-certificates').
- Alternate the ordering of Windows and Linux instructions, or present them side-by-side to avoid implicit prioritization.
- Include explicit Linux examples where Windows examples are given, ensuring parity in actionable guidance.
- Review other sections for similar ordering or specificity issues and adjust to present both platforms with equal clarity.
Resource Mover
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/tutorial-move-region-virtual-machines.md
...esource-mover/tutorial-move-region-virtual-machines.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains parity between Windows and Linux, but in the 'Prepare VMs' section, instructions for updating certificates are presented with Windows guidance first, followed by Linux. No command-line examples are given for either OS, and no PowerShell or Windows-specific tooling is used elsewhere. However, the order of presentation subtly prioritizes Windows.
Recommendations
- Present Windows and Linux instructions in parallel or alternate the order in which they are mentioned to avoid implicit prioritization.
- Where possible, provide explicit, concrete examples for both Windows (e.g., using Windows Update) and Linux (e.g., using apt, yum, or update-ca-certificates) to ensure clarity and parity.
- Review all sections to ensure that Linux is not consistently mentioned after Windows, and that both platforms receive equal prominence in prerequisites and procedural steps.
- If screenshots or UI elements are OS-specific, include examples for both Windows and Linux VMs where relevant.
Resource Mover
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/resource-mover/tutorial-move-region-virtual-machines.md
...esource-mover/tutorial-move-region-virtual-machines.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains parity between Windows and Linux, but in the 'Prepare VMs' section, instructions for updating certificates are presented with Windows guidance first and more detail ('install the latest Windows updates'), while Linux guidance is less explicit ('follow distributor guidance'). No command-line examples are given for either OS, and no Windows-specific tools or PowerShell commands are used elsewhere. However, the ordering and specificity of the Windows instruction indicate a subtle 'windows_first' bias.
Recommendations
- Provide equally detailed instructions for Linux VMs as for Windows VMs, such as specifying common commands (e.g., 'sudo apt update && sudo apt upgrade' for Ubuntu) to update certificates.
- When listing OS-specific instructions, alternate the order or present both together to avoid implying priority (e.g., 'On Windows VMs... On Linux VMs...').
- If referencing OS-specific requirements, link to authoritative documentation for both Windows and Linux procedures.
- Consider adding example commands or scripts for both Windows and Linux where applicable, to ensure parity and clarity.