Migrate
203
Total Pages
70
Linux-Friendly Pages
133
Pages with Bias
65.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
918 issues found
Showing 476-500 of 918 flagged pages
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/add-server-credentials.md
...s/blob/main/articles/migrate/add-server-credentials.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation prioritizes Windows environments and tools, providing more detailed instructions and support for Windows credentials, domain integration (Active Directory), and SQL Server discovery (which is only supported on Windows). Linux support is mentioned but lacks equivalent depth, with some features (e.g., SQL Server and ASP.NET web app discovery) explicitly not supported for Linux. There are no Linux-specific examples or step-by-step instructions, and Windows authentication patterns (domain credentials, DPAPI) are described in detail before Linux alternatives.
Recommendations
- Provide Linux-specific examples and step-by-step instructions for adding credentials, including screenshots or command-line examples where appropriate.
- Clarify feature parity by explicitly stating which features are not supported on Linux and, where possible, provide timelines or alternatives.
- Include Linux authentication mechanisms (e.g., SSH key-based authentication) and describe how to configure them in the appliance.
- Balance the order of presentation so that Linux and Windows are given equal prominence in tables, lists, and descriptions.
- If certain features are Windows-only, consider adding equivalent Linux discovery features or tools, or link to relevant documentation for Linux environments.
Create Pull Request
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/agent-based-migration-architecture.md
...articles/migrate/agent-based-migration-architecture.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by providing only Windows-specific paths, tools, and registry keys (e.g., Windows registry, MMC snap-in, C:\Program Files paths) when discussing configuration and troubleshooting. There are no Linux equivalents or examples for agent installation, antivirus exclusions, or bandwidth throttling. The documentation assumes the use of Windows environments for process servers and omits Linux-specific instructions or considerations.
Recommendations
- Include Linux-specific paths for antivirus exclusions and agent installation directories.
- Provide instructions for managing bandwidth throttling on Linux-based process servers (e.g., using tc, iptables, or other Linux-native tools).
- Document how to install and manage the Mobility service on Linux servers, including command-line examples.
- Clarify whether the process server and replication appliance can run on Linux, and if so, provide setup and management instructions.
- Add troubleshooting and configuration guidance for Linux environments, such as relevant log locations and service management commands.
- Ensure all examples and configuration steps are presented for both Windows and Linux, or explicitly state platform limitations.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/appcat/dotnet.md
...azure-docs/blob/main/articles/migrate/appcat/dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Visual Studio (a Windows-only tool) in both installation and usage instructions, listing Windows prerequisites first, and providing detailed steps only for Windows environments. There are no Linux-specific instructions or examples, and the CLI section lacks explicit cross-platform usage notes, despite .NET CLI being cross-platform.
Recommendations
- Add explicit instructions and examples for installing and using the CLI tool on Linux and macOS, including any OS-specific considerations (e.g., shell syntax, permissions).
- Clarify that the .NET CLI tool is cross-platform and provide parity in documentation for non-Windows users.
- If Visual Studio Code or other cross-platform editors are supported, mention and provide guidance for those environments.
- Reorder sections or provide parallel instructions so that Linux/macOS users are not implicitly deprioritized.
- Include screenshots or terminal output examples from Linux/macOS environments where relevant.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-migration-webapps.md
...ob/main/articles/migrate/concepts-migration-webapps.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows environments. It exclusively discusses migration of ASP.NET web apps from Windows servers running IIS, requires Windows PowerShell, and explicitly states that Linux servers are not supported. There are no Linux examples, tools, or migration paths mentioned.
Recommendations
- Clearly state in the introduction that only Windows/IIS workloads are currently supported, and provide a roadmap or links for Linux support if planned.
- Add a section addressing Linux users, clarifying current limitations and suggesting alternative migration strategies or tools for Linux-based web apps.
- If Linux support is planned, include anticipated timelines or preview features.
- Where possible, provide parity in documentation structure for Linux (e.g., prerequisites, migration steps) even if only to state 'not yet supported' and link to relevant feedback channels.
- Avoid assuming PowerShell or Windows tools as the only administrative interface; mention alternatives or note the lack thereof.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/best-practices-assessment.md
...lob/main/articles/migrate/best-practices-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-centric workloads (e.g., ASP.NET on IIS), mentioning Windows tools and environments (such as Hyper-V and IIS) before or instead of Linux equivalents, and omitting explicit Linux or open-source workload migration examples. There are no Linux-specific instructions, examples, or references to Linux-native tools or scenarios, and the only web app migration scenario described is for ASP.NET on IIS, with no mention of Linux-based web servers or applications.
Recommendations
- Include explicit examples and guidance for assessing and migrating Linux workloads, such as Apache, Nginx, or Tomcat web servers, and common Linux distributions.
- Provide parity in migration scenarios by describing both Windows (e.g., IIS/ASP.NET) and Linux (e.g., Apache/PHP, Nginx/Node.js) application migrations to Azure App Service.
- Mention Linux-based virtualization environments (such as KVM or Xen) if supported, or clarify support limitations.
- Reference Linux-native tools and patterns where applicable, and provide sample commands or procedures for Linux environments.
- Ensure that instructions, troubleshooting, and best practices address both Windows and Linux server scenarios equally.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/best-practices-least-privileged-account.md
...les/migrate/best-practices-least-privileged-account.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows examples and instructions are often presented before Linux equivalents, and some sections (such as SQL Server discovery) focus exclusively on Windows authentication and tooling. Windows-specific tools and UI steps (e.g., WMI Control, WinRM, Start menu) are described in detail, while Linux instructions are more concise and sometimes lack parity in depth or clarity. There are also more detailed, step-by-step instructions and screenshots for Windows, while Linux guidance is more command-focused and less explanatory.
Recommendations
- Alternate the order of Windows and Linux instructions/examples to avoid always presenting Windows first.
- Provide equally detailed, step-by-step instructions for Linux, including screenshots or references to common Linux desktop environments or CLI tools where appropriate.
- Where Windows-specific tools (e.g., WMI Control, WinRM) are described, include Linux equivalents (e.g., systemd, journalctl, or relevant configuration files) and explain how to achieve the same outcome.
- For database discovery, include examples for Linux-based SQL Server installations and authentication methods, not just Windows authentication.
- Ensure that all tables and permission lists provide Linux and Windows information side by side, rather than in separate sections or with less detail for Linux.
- Where scripts or commands are provided for Windows (e.g., PowerShell, SQL scripts), provide equivalent Bash or shell scripts for Linux where applicable.
- Add troubleshooting and verification steps for Linux environments similar to those given for Windows.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/common-questions-discovery-dependency-analysis.md
...rate/common-questions-discovery-dependency-analysis.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows tools and patterns, such as referencing Microsoft Monitoring Agent (MMA) and deployment tools like Microsoft Configuration Manager and Intigua, without equivalent Linux-focused guidance. Automation and scripting references (e.g., PowerShell Gallery) are Windows-centric, and there are no Linux-specific examples or instructions for agent installation or automation. While Linux support is mentioned, it is not given equal prominence or practical detail.
Recommendations
- Provide explicit Linux agent installation instructions and automation examples (e.g., using shell scripts or Ansible).
- Include Linux-native deployment tool options (e.g., Puppet, Chef, or native package managers) alongside Windows tools.
- Offer Linux command-line examples for agent installation and configuration, not just Windows/PowerShell.
- When listing supported operating systems or tools, present Windows and Linux information in parallel, not with Windows first.
- Reference Linux documentation and resources as prominently as Windows resources.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/common-questions-appliance.md
...ob/main/articles/migrate/common-questions-appliance.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation for the Azure Migrate appliance exhibits a strong Windows bias. Deployment and management instructions are centered around PowerShell scripts, with no mention of Bash, shell, or Linux-native alternatives. Troubleshooting and certificate management steps are exclusively described using Windows tools (e.g., Certificate Manager, Local Group Policy Editor, Windows Update), and all screenshots are from Windows environments. There are no Linux-specific deployment, configuration, or troubleshooting examples, and Linux users are not provided with equivalent guidance for common administrative tasks.
Recommendations
- Provide Linux-native deployment instructions (e.g., using Bash scripts or manual steps for Linux VMs).
- Include troubleshooting steps and screenshots for Linux environments (e.g., managing certificates with openssl or update-ca-certificates, checking group policies or firewall rules on Linux).
- Offer parity in examples by showing both Windows and Linux command-line instructions for common tasks (e.g., verifying MSI signatures, updating the appliance, managing credentials).
- Clarify OS support for the appliance and explicitly state if Linux-based deployments are supported or not. If not, explain the rationale.
- Where PowerShell is required, note if PowerShell Core (cross-platform) is supported and provide installation guidance for Linux if applicable.
- Add a section or FAQ specifically addressing Linux administrators' needs and common scenarios.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-azure-webapps-assessment-calculation.md
...grate/concepts-azure-webapps-assessment-calculation.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing on ASP.NET web apps running on IIS (a Windows technology) and providing no explicit examples or guidance for Linux-based web apps or tools. The assessment process and examples are centered around Windows workloads, with no mention of Linux equivalents (such as Apache, Nginx, or Linux-based Java app servers). The only Java example references Tomcat, but does not clarify OS context or provide parity for Linux-specific scenarios. There are no Linux command-line or tooling examples, and Windows patterns (IIS, ASP.NET) are mentioned first and exclusively.
Recommendations
- Include explicit examples and guidance for assessing Linux-based web apps (e.g., Java apps running on Apache Tomcat on Linux, or Node.js/PHP apps on Linux).
- Mention Linux web server environments (such as Apache, Nginx) and clarify that the assessment tool supports both Windows and Linux workloads.
- Provide parity in documentation by including Linux command-line or configuration examples alongside any Windows/IIS examples.
- List supported platforms and clarify any differences in assessment or migration steps for Linux vs. Windows web apps.
- Ensure that references to tools, patterns, and environments are not Windows-first; present Linux and Windows options together where applicable.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-business-case-calculation.md
...articles/migrate/concepts-business-case-calculation.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing heavily on Windows Server, SQL Server, Hyper-V, and Microsoft management tools (e.g., System Center), with little to no mention of Linux servers or workloads. Cost calculations, licensing, and migration strategies are centered around Windows technologies, and there are no explicit examples or guidance for Linux-based environments. Linux is only briefly mentioned in passing (e.g., in license amortization), with no details or parity in examples or cost breakdowns.
Recommendations
- Include explicit guidance and examples for Linux server discovery, assessment, and migration, such as supported Linux distributions and how the appliance collects data from them.
- Add cost calculation details for Linux OS licensing, support, and management, similar to the breakdowns provided for Windows and SQL Server.
- Reference Linux management and monitoring tools (e.g., Azure Monitor for Linux, open-source alternatives) alongside Windows tools like System Center.
- Ensure migration strategies and assessment insights cover Linux workloads (e.g., Apache, MySQL, PostgreSQL) and not just Windows-centric workloads.
- Provide parity in documentation structure and examples, ensuring Linux scenarios are described with the same depth as Windows scenarios.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-migration-planning.md
...b/main/articles/migrate/concepts-migration-planning.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by specifically highlighting Windows Server scenarios (e.g., end-of-support, OS upgrade), referencing Windows-specific tools and features (such as the Custom Script Extension for Windows), and omitting equivalent Linux migration or upgrade workflows. There are no Linux-specific examples, tools, or migration blockers discussed, and Windows scenarios are given explicit, detailed attention.
Recommendations
- Include explicit Linux migration scenarios, such as handling end-of-support Linux distributions, and provide guidance for Linux OS upgrades during migration.
- Mention and link to the Azure VM Custom Script Extension for Linux, and provide equivalent Linux automation examples.
- Add examples or notes for Linux-specific migration blockers, compatibility issues, and remediation steps.
- Ensure parity in recommendations for both Windows and Linux workloads throughout the documentation, including cost-saving options, assessment reports, and post-migration steps.
- Where Windows-specific features are discussed (e.g., in-place OS upgrade), provide a corresponding section or note for Linux users, even if the feature is not available, to clarify support and alternatives.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-assessment-calculation.md
...in/articles/migrate/concepts-assessment-calculation.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first and Windows-heavy bias. Windows operating systems are listed first and in greater detail in readiness tables, with specific versions and support scenarios exhaustively documented. Linux is treated as a single row with a link to another page, and other non-Windows OSes are grouped together. There are no Linux-specific examples, troubleshooting notes, or parity in detail. Additionally, some technical notes (e.g., UEFI boot support) only mention Windows versions. There are no CLI or PowerShell examples, but the overall pattern prioritizes Windows environments and support scenarios.
Recommendations
- Provide Linux-specific examples and scenarios, such as common Linux distributions, migration caveats, and troubleshooting tips.
- Expand the guest OS readiness table to list major Linux distributions and their support status, similar to the Windows breakdown.
- Include more detailed guidance for Linux VMs, such as kernel version detection, common migration blockers, and links to Linux migration best practices.
- Ensure that technical notes (e.g., UEFI boot support) explicitly mention Linux where applicable, not just Windows.
- Balance the order of presentation so that Linux is not always listed after Windows, and ensure Linux is treated as a first-class platform in all readiness and assessment discussions.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-azure-sql-assessment-calculation.md
...s/migrate/concepts-azure-sql-assessment-calculation.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns (such as Windows Server Failover Clusters, Cloud Witness, and links to Windows-specific best practices) without mentioning or providing parity for Linux environments. There are no Linux-specific examples, instructions, or references to Linux-based SQL Server deployments or high availability patterns. The documentation assumes a Windows-centric SQL Server environment, especially in high availability and migration scenarios.
Recommendations
- Include explicit guidance for assessing and migrating SQL Server instances running on Linux, including any differences in data collection, compatibility checks, and migration steps.
- Provide Linux-specific examples and references, such as links to best practices for SQL Server on Linux VMs in Azure.
- Mention Linux-based high availability options (e.g., Pacemaker clusters) alongside Windows Server Failover Clusters and Cloud Witness.
- Clarify if and how the Azure Migrate appliance supports SQL Server on Linux and what, if any, limitations exist.
- Ensure that documentation for storage, compute, and security settings addresses both Windows and Linux environments equally.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/common-questions-server-migration.md
.../articles/migrate/common-questions-server-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: bandwidth throttling and automation examples are provided exclusively using Windows PowerShell and Windows-specific tools (NetQosPolicy, Scheduled Tasks), with no Linux equivalents or guidance. The OS upgrade feature is available only for Windows, and this is explicitly stated. Throughout the document, Windows terminology and patterns (such as IIS, Windows scheduled tasks, and PowerShell scripting) are presented without Linux alternatives. In some tables and feature explanations, Windows OSes are listed first, and Linux support is mentioned but not detailed with equivalent operational examples.
Recommendations
- Provide Linux-specific examples for bandwidth throttling and automation, such as using tc, wondershaper, or iptables for bandwidth control, and cron jobs or systemd timers for scheduling on Linux-based Azure Migrate appliances.
- When presenting PowerShell or Windows tool-based instructions, include parallel instructions for common Linux distributions, with tested shell scripts or command-line equivalents.
- Where features are Windows-only (such as OS upgrade during migration), clarify if/when Linux support is planned, and suggest best practices or workarounds for Linux users.
- Ensure that documentation tables and lists alternate or balance the order of Windows and Linux information, and provide parity in detail and guidance for both platforms.
- Explicitly mention any limitations or differences in Linux support, and link to relevant Linux documentation or community resources.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/create-web-app-assessment.md
...lob/main/articles/migrate/create-web-app-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific optimization steps (e.g., optimizing Windows Dockerfiles) in the 'Next steps' section, and by linking exclusively to Windows container best practices. There are no equivalent Linux container or general cross-platform examples or references, and the guidance implicitly assumes a Windows-centric workload without mentioning Linux-based web apps or containerization patterns.
Recommendations
- Add parallel Linux-focused guidance and links, such as optimizing Linux Dockerfiles and best practices for Linux containers on AKS.
- Ensure 'Next steps' includes both Windows and Linux optimization resources, or general cross-platform guidance.
- Explicitly mention that the assessment process applies to both Windows and Linux web apps, and provide examples or notes for both.
- Review all linked resources to ensure Linux parity and avoid exclusive focus on Windows tools or patterns.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/concepts-vmware-agentless-migration.md
...rticles/migrate/concepts-vmware-agentless-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias in its operational guidance for managing replication. All command-line examples (e.g., for throttling replication) use PowerShell cmdlets (New-NetQosPolicy), and configuration file paths are given in Windows format (C:\ProgramData\...). There is no mention of Linux equivalents or how to perform these tasks on a Linux-based Azure Migrate appliance. The documentation assumes the appliance and administrative environment are Windows-based, with no Linux parity in examples or instructions.
Recommendations
- Provide equivalent Linux command-line examples (e.g., using tc or other Linux network QoS tools for bandwidth throttling).
- Document the location and format of configuration files on Linux appliances, if supported.
- Clarify whether the Azure Migrate appliance can run on Linux, and if so, provide Linux-specific operational guidance.
- When giving file paths or service names, include both Windows and Linux variants where applicable.
- Add a section or note explicitly addressing Linux support and any differences in management or configuration.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/create-project.md
...zure-docs/blob/main/articles/migrate/create-project.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing command-line instructions specifically for PowerShell, explicitly instructing users to open PowerShell as Administrator after installing the Azure CLI. There are no equivalent instructions or examples for Linux or macOS users, nor is there mention of using a Bash shell or terminal. The documentation assumes a Windows environment for CLI usage, and does not provide parity for Linux users.
Recommendations
- Provide equivalent command-line instructions for Linux/macOS users, including examples using Bash or other common Linux shells.
- Avoid specifying 'PowerShell' as the default terminal unless the instructions are truly Windows-specific; instead, use neutral language such as 'open your terminal'.
- Include notes or callouts indicating that the Azure CLI commands work cross-platform, and provide any OS-specific prerequisites or differences.
- Where screenshots or UI steps are shown, clarify if there are any differences for Linux users, or confirm that the experience is the same.
- Add a section or callout for Linux/macOS users to ensure inclusivity and parity in the documentation.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/discover-and-assess-using-private-endpoints.md
...migrate/discover-and-assess-using-private-endpoints.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use Windows tools (CertUtil), and the only installer script example is shown in PowerShell with Windows-style paths. There are no Linux shell or command examples, nor any mention of how to perform these steps on a Linux-based appliance. Instructions such as 'open an administrator command window' and references to C:\ paths further reinforce the Windows-centric approach. The documentation does not address Linux users or provide parity for Linux-based deployments.
Recommendations
- Provide equivalent Linux shell commands for verifying file hashes (e.g., using sha256sum or openssl).
- Include examples of running the installer script on Linux, using bash and Linux file paths.
- Clarify whether the Azure Migrate appliance can be deployed on Linux, and if so, provide detailed steps.
- When referencing file paths or command prompts, offer both Windows and Linux variants.
- Explicitly mention OS requirements and provide guidance for both Windows and Linux environments.
- Add troubleshooting steps and log file locations for Linux-based appliances, if supported.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/create-manage-projects.md
...s/blob/main/articles/migrate/create-manage-projects.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing command-line examples specifically for PowerShell, referencing running the Azure CLI 'in PowerShell' as Administrator, and omitting equivalent instructions or clarifications for Linux/macOS users. There are no Linux-specific examples or notes, and the instructions assume a Windows environment for CLI usage.
Recommendations
- Provide explicit instructions and command examples for Linux/macOS users, including how to open a terminal and run Azure CLI commands.
- Avoid referencing PowerShell as the default shell for CLI usage; instead, use neutral language such as 'open a terminal or command prompt.'
- Include notes or callouts highlighting any differences in command syntax or prerequisites between Windows and Linux/macOS environments.
- Ensure screenshots and UI references are not Windows-specific, or supplement with Linux/macOS equivalents where relevant.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-automate-migration.md
...lob/main/articles/migrate/how-to-automate-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows environments, specifically PowerShell. All automation examples, scripts, and instructions are provided exclusively in PowerShell (.ps1 scripts), with no mention of Linux-compatible alternatives (such as Bash or cross-platform scripting). The installation instructions and prerequisites focus solely on Azure PowerShell, and there is no guidance for users on Linux or macOS platforms. This approach assumes users are operating in a Windows environment, potentially excluding or inconveniencing those on other operating systems.
Recommendations
- Provide equivalent Bash or cross-platform (e.g., Python) scripts for Linux/macOS users.
- Include instructions for installing and using Azure CLI as an alternative to Azure PowerShell.
- Explicitly state OS compatibility for the provided scripts, and offer guidance for running them on Linux (e.g., using PowerShell Core on Linux).
- Add Linux/macOS-specific examples and troubleshooting tips.
- Consider restructuring the documentation to present both Windows and Linux approaches side by side, or clearly indicate which sections are Windows-specific.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies-agentless.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-group-machine-dependencies-agentless.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: all command-line examples for managing dependency analysis (enabling/disabling, exporting data) are provided exclusively using PowerShell, with no equivalent Bash or Linux CLI examples. The instructions for disabling/enabling dependency analysis and exporting data rely on PowerShell modules and cmdlets, which are native to Windows environments. While Linux is mentioned in credential requirements, there are no practical Linux-based workflows, scripts, or examples. The documentation assumes the use of Windows tools and patterns, and Windows terminology (such as 'domain/Windows credentials') is presented before Linux equivalents.
Recommendations
- Provide equivalent Bash or shell script examples for Linux environments, using Azure CLI or REST API where possible.
- Document how to perform enable/disable and export operations from Linux or cross-platform environments, not just via PowerShell.
- Reference and link to Linux-native tools or methods (e.g., Azure CLI, Python SDK) for managing Azure Migrate dependency analysis.
- Ensure that Linux credential requirements and workflows are presented with equal prominence and detail as Windows.
- Add screenshots or walkthroughs from a Linux admin perspective, including command-line and UI interactions.
- Clarify whether PowerShell Core (cross-platform) is supported, and if so, provide installation and usage instructions for Linux/macOS.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/hyper-v-migration-architecture.md
...ain/articles/migrate/hyper-v-migration-architecture.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows/Hyper-V environments, with all examples, tools, and instructions tailored exclusively to Windows systems. It references Windows-specific tools (MMC snap-ins, registry edits), provides no Linux or cross-platform equivalents, and assumes the user is operating from a Windows context throughout.
Recommendations
- Add equivalent instructions or explicit notes for Linux-based Hyper-V management, if supported, or clarify Windows-only limitations.
- Where Windows tools (e.g., MMC snap-ins, registry edits) are mentioned, provide alternative command-line or cross-platform approaches if available.
- Explicitly state platform requirements and limitations at the beginning of the documentation.
- If Linux-based Hyper-V management is not supported, provide links or references to migration documentation for Linux-based hypervisors (e.g., KVM, Xen) to guide non-Windows users.
- Ensure future documentation includes parity in examples and instructions for both Windows and Linux environments where possible.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/discovered-metadata.md
...docs/blob/main/articles/migrate/discovered-metadata.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias in several ways: Windows/PowerShell tools and patterns are often mentioned first or exclusively, especially for features, storage, and application inventory. Windows-specific tools (WMI, PowerShell cmdlets, Registry, Get-WindowsFeature, etc.) are detailed extensively, while Linux equivalents are less prominent or missing (e.g., storage metadata, feature discovery). Some sections (e.g., ASP.NET, Java, Spring Boot web app data) only describe collection from Windows servers, with no mention of Linux support or parity.
Recommendations
- For every Windows-specific example or tool (e.g., PowerShell cmdlets, WMI classes), provide equivalent Linux commands or tools where possible.
- Ensure that sections describing feature, storage, and application inventory data collection include Linux-specific methods and commands, or explicitly state if Linux is not supported.
- When listing data collection methods, avoid always listing Windows first; alternate or group by platform.
- For web app data (ASP.NET, Java, Spring Boot), clarify if Linux servers are supported for discovery, and if so, document the Linux collection methods.
- Expand the storage metadata section to include Linux storage discovery commands (e.g., lsblk, df, lvs, pvs, etc.) if supported.
- Where Windows registry or PowerShell is referenced, provide Linux equivalents (e.g., config files, systemd, etc.) or note limitations.
- Add explicit notes where a feature is Windows-only, to avoid ambiguity.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/scale-hyper-v-assessment.md
...blob/main/articles/migrate/scale-hyper-v-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Hyper-V, a Windows-based virtualization platform, and only provides instructions and examples relevant to Windows environments. There is no mention of Linux-based hypervisors (such as KVM or Xen), nor are there any Linux command-line or tool examples. The workflow assumes the use of Windows tools and patterns, with no guidance for users operating in Linux-centric environments.
Recommendations
- Include parallel documentation or references for assessing Linux-based virtualization environments (e.g., KVM, Xen, VMware on Linux) for migration to Azure.
- Provide examples and instructions for deploying and managing the Azure Migrate appliance on Linux hosts, if supported.
- Mention Linux-specific requirements, limitations, and best practices for migration assessment.
- If Azure Migrate supports only Hyper-V, clearly state this limitation and provide links to equivalent guidance for Linux-based environments elsewhere in the documentation.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-create-sql-assessment.md
.../main/articles/migrate/how-to-create-sql-assessment.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and optimization guides (e.g., Windows Dockerfiles) in the 'Next steps' section, without providing equivalent Linux examples or guidance. There are no Linux-specific instructions, tools, or examples, and the only optimization and best practices links are for Windows containers. This may lead Linux users to feel unsupported or unclear about Linux container or workload migration.
Recommendations
- Add equivalent Linux container optimization and best practices links, such as optimizing Linux Dockerfiles or managing Linux containers on AKS.
- Include Linux-specific examples or references where Windows-specific tools or workflows are mentioned.
- Ensure parity in guidance for both Windows and Linux workloads, especially in sections like 'Next steps' and optimization.
- Explicitly mention that the guidance applies to both Windows and Linux where applicable, or clarify any differences.