13764
Pages Scanned
50
Pages Flagged
13764
Changed Pages
0.4%
% Pages Flagged
Scan Information
Started At: 2025-12-14 05:05:33
Finished At: 2025-12-14 19:41:44
Status: completed
Target Repo: Azure
Current Phase: discovery
Files Queued: 13764
Files Completed: 13764
Problematic Pages
50 issues found
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-ldap-extended-groups.md
...s/azure-netapp-files/configure-ldap-extended-groups.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows/Active Directory bias by exclusively supporting and referencing Microsoft Active Directory Domain Services (AD DS) and Microsoft Entra Domain Services for LDAP integration, with explicit statements that OpenLDAP and other third-party LDAP services are not supported. Configuration steps and attribute management examples are provided only for Windows tools (e.g., Active Directory Users and Computers MMC snap-in, Multi-valued String Editor), and troubleshooting guidance references Windows-centric tools (e.g., ntdsutil.exe) without Linux equivalents. Linux/NFS client configuration is only briefly mentioned and not illustrated with equivalent attribute management or troubleshooting steps.
Recommendations
- Provide equivalent examples and screenshots for managing POSIX attributes using common Linux LDAP tools (e.g., ldapmodify, phpldapadmin) where possible.
- Clarify the lack of OpenLDAP or third-party LDAP support earlier in the document and, if possible, provide a roadmap or alternatives for Linux environments.
- Include troubleshooting steps and attribute verification commands for Linux environments (e.g., using ldapsearch).
- When referencing Windows tools (e.g., ntdsutil.exe), provide Linux alternatives or explicitly state that these steps are only applicable to Windows environments.
- Consider including a section that addresses common Linux administrator scenarios, even if only to clarify limitations and suggest workarounds.
Create Pull Request
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/test-toolkit.md
...icles/azure-resource-manager/templates/test-toolkit.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily PowerShell-centric, reflecting the fact that the ARM template test toolkit is implemented as a set of PowerShell scripts. All usage examples, including those for Linux and macOS, require PowerShell (pwsh) and do not provide native Bash, sh, or other shell alternatives. The documentation consistently presents Windows instructions first, with Linux and macOS following, and does not mention or provide examples using common Linux-native tools or scripting languages. There are no examples for running the toolkit in a non-PowerShell environment, and the integration examples for CI/CD pipelines are also PowerShell-based.
Recommendations
- Explicitly state that the toolkit is PowerShell-only, and clarify that native Bash or shell usage is not supported if that is the case.
- If possible, provide or link to a cross-platform wrapper or alternative (e.g., a Docker image or a Bash script) for users who do not wish to install PowerShell.
- Consider developing and documenting a native Linux/Unix CLI or containerized version of the toolkit.
- In the documentation, mention up front that PowerShell is required on all platforms, and provide guidance for users unfamiliar with PowerShell on Linux/macOS.
- If PowerShell is the only supported method, consider reordering the instructions to present cross-platform steps first, or group steps by 'Prerequisites' (install PowerShell) and then 'Run the toolkit' (same for all OSes), to reduce the Windows-first impression.
- For CI/CD integration, mention or provide examples for running the toolkit in containerized environments (e.g., GitHub Actions, Docker), which are common in Linux-based workflows.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/configure-external-identity-source-nsx-t.md
...ure-vmware/configure-external-identity-source-nsx-t.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing Windows Server Active Directory as the LDAP provider, requiring Windows-specific infrastructure (domain controllers, AD Certificate Services), and omitting any examples or guidance for integrating with Linux-based LDAP servers (such as OpenLDAP). All prerequisites, examples, and screenshots focus on Windows environments, with no mention of Linux alternatives or parity.
Recommendations
- Add explicit instructions and examples for configuring NSX with Linux-based LDAP servers (e.g., OpenLDAP), including certificate management and user/group mapping.
- Update prerequisites to mention that any LDAP-compliant directory (not just Windows Server AD) can be used, and provide guidance for Linux setups.
- Include screenshots and walkthroughs for Linux LDAP server integration, not just Windows Server AD.
- Reference Linux certificate authorities and tools (e.g., OpenSSL, Let's Encrypt) alongside Windows Certificate Services.
- Clarify that the process is not limited to Windows environments and provide troubleshooting tips for common Linux LDAP issues.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-sql.md
...s/blob/main/articles/backup/backup-azure-backup-sql.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation is heavily biased towards Windows environments. It exclusively references Data Protection Manager (DPM), a Windows-only backup tool, and all examples, screenshots, and instructions are based on Windows Server and SQL Server running on Windows. There is no mention of Linux-based SQL Server deployments, nor are there any examples or guidance for backing up SQL Server on Linux. The only automation reference is to PowerShell, which is primarily a Windows tool.
Recommendations
- Add guidance and examples for backing up SQL Server running on Linux, including supported scenarios and limitations.
- Include alternative backup tools or workflows for Linux environments, such as Azure Backup integration with Linux agents or native SQL Server backup commands.
- Provide parity in automation examples, such as Bash scripts or CLI commands, alongside PowerShell.
- Clearly indicate in the prerequisites and introduction that the documented workflow is specific to Windows/DPM, and link to Linux-specific documentation if available.
- Mention Azure Backup support for SQL Server on Linux, if applicable, or clarify limitations.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/relocation-hdinsight.md
...-manager/management/relocation/relocation-hdinsight.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by consistently listing Azure PowerShell and Azure Cloud Shell deployment methods alongside or before Azure CLI, with no mention of Linux-native tools or shell scripting. There are no explicit Linux/bash examples, and the guidance does not reference Linux-specific patterns or tools, despite the cross-platform nature of Azure CLI and ARM/Bicep templates.
Recommendations
- Ensure that Azure CLI examples (which are cross-platform and commonly used on Linux) are listed before or at least equally with PowerShell examples.
- Add explicit bash/Linux shell command examples for exporting and deploying ARM/Bicep templates.
- Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide examples for both.
- Avoid using 'Azure PowerShell' as the default or primary automation method; present it as one of several options.
- Include references to Linux-native scripting and automation patterns where relevant.
- Review and balance the order of tool mentions so that Linux users do not feel secondary.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicom-configure-azure-rbac.md
...es/healthcare-apis/dicom/dicom-configure-azure-rbac.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell for creating custom RBAC roles, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI, REST API, or ARM templates. There are no Linux-specific instructions or cross-platform command-line examples, and the only automation tool referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Add equivalent instructions and examples for creating custom roles using Azure CLI, which is cross-platform and widely used on Linux.
- Mention and link to REST API or ARM template approaches for custom role creation, which are platform-agnostic.
- Explicitly state that PowerShell is available on Linux and macOS, or clarify when instructions are Windows-specific.
- Ensure that screenshots and UI instructions are not Windows-centric, or provide notes for any platform-specific differences.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/concepts.md
...zure-docs/blob/main/articles/load-balancer/concepts.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where the quickstart example focuses on creating VMs with a custom IIS extension installed (IIS is a Windows-only web server). There are no equivalent Linux-based examples (e.g., using Apache or Nginx), nor are Linux tools or patterns mentioned. The documentation implicitly assumes Windows as the default platform for web workloads, omitting guidance for Linux users.
Recommendations
- Add quickstart examples for Linux-based VMs using popular web servers such as Apache or Nginx.
- Mention Linux equivalents alongside Windows tools (e.g., IIS) to provide parity.
- Include instructions or links for deploying and load balancing Linux workloads.
- Ensure that examples and walkthroughs are platform-neutral or provide both Windows and Linux variants.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/connect-virtual-machine-mac-remote-desktop.md
...services/connect-virtual-machine-mac-remote-desktop.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates bias towards Windows by exclusively recommending the 'Windows App' for RDP connections from Mac, without mentioning or providing examples of alternative RDP clients commonly used on Linux or Mac (e.g., FreeRDP, Remmina, Microsoft Remote Desktop). The instructions and screenshots focus on the Windows App, and there is no parity in showing how to connect using Linux-native tools or providing equivalent Linux examples. The related content mentions X2Go for Linux, but only as a link, not as a direct alternative or example within the main workflow.
Recommendations
- Include instructions and examples for connecting to Azure Lab Services VMs using popular Linux/Mac RDP clients such as Remmina, FreeRDP, or Microsoft Remote Desktop for Mac.
- Present connection options for both Windows and Linux/Mac tools side-by-side, rather than focusing solely on Windows App.
- Add screenshots and step-by-step guidance for alternative clients to ensure users on Linux or Mac have clear, supported workflows.
- Clarify that 'Windows App' is not the only option and mention other cross-platform RDP clients in the main content, not just in related links.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/load-balancer-distribution-mode.md
...icles/load-balancer/load-balancer-distribution-mode.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides step-by-step instructions for configuring Azure Load Balancer distribution mode using the Azure portal, PowerShell, and Azure CLI. PowerShell (a Windows-centric tool) is given a dedicated section and example before Azure CLI, which is cross-platform. There are no explicit Linux-specific examples, nor is there mention of Linux-native tools or shell environments (e.g., Bash). The CLI example is generic but does not clarify usage in Linux environments or provide Linux-specific context.
Recommendations
- Add explicit Bash/Linux shell examples for Azure CLI usage, including environment setup and command execution in a Linux terminal.
- Clarify that Azure CLI commands work cross-platform and provide any necessary notes for Linux users (e.g., installation, authentication).
- Consider reordering sections to present cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) to avoid Windows-first bias.
- Include links or references to Linux-specific quickstart or configuration guides where relevant.
- If PowerShell is mentioned, note that PowerShell Core is available on Linux, or provide equivalent Bash commands where possible.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/quickstart-load-balancer-standard-internal-portal.md
...r/quickstart-load-balancer-standard-internal-portal.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation demonstrates a clear Windows bias. All VM creation examples use Windows Server images, and all configuration and testing steps (such as IIS installation and web server setup) are performed exclusively with Windows tools (PowerShell, IIS, Microsoft Edge). There are no Linux equivalents or examples provided for creating Linux VMs, installing a web server (e.g., Apache or Nginx), or using Linux command-line tools. The documentation does not mention or show how to perform the same tasks on Linux VMs, nor does it offer Linux shell commands.
Recommendations
- Provide parallel instructions for creating Linux-based VMs (e.g., Ubuntu or CentOS) alongside Windows examples.
- Include Linux-specific steps for installing a web server (such as Apache or Nginx) using shell commands (e.g., apt, yum).
- Show how to create a custom index.html on Linux VMs to mirror the IIS customization on Windows.
- Demonstrate how to test the load balancer using a browser or curl/wget on Linux VMs.
- When presenting code or command-line examples, offer both PowerShell (for Windows) and Bash (for Linux) equivalents.
- Explicitly mention that the process works for both Windows and Linux VMs, and link to relevant Linux documentation if available.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/assign-policy-template.md
...n/articles/governance/policy/assign-policy-template.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a Windows bias by consistently listing PowerShell (a Windows-centric tool) examples and instructions before Azure CLI, and by recommending Visual Studio Code (a Microsoft product) as the editor. The use of PowerShell-specific concepts (such as splatting) and output examples is prominent. There is no mention of Linux-native editors or shell environments, and no explicit guidance for Linux or macOS users, even though Azure CLI is cross-platform.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first, as it is cross-platform and more familiar to Linux/macOS users.
- Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and provide installation links for all platforms.
- Include instructions or examples using native Linux/macOS editors (e.g., nano, vim) alongside Visual Studio Code, or clarify that any text editor can be used.
- Avoid PowerShell-specific terminology (like 'splatting') without providing equivalent explanations for Bash or shell scripting.
- Add a brief section or note addressing Linux/macOS users, confirming that all steps are supported on their platforms and highlighting any differences if they exist.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/azure-integration-services-choose-capabilities.md
...apps/azure-integration-services-choose-capabilities.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 BizTalk Server and SQL Server Integration Services (SSIS) as primary migration sources, both of which are traditionally Windows-centric enterprise tools. The migration scenarios and examples focus on these Windows technologies without mentioning Linux-based integration platforms or providing equivalent Linux migration examples. There are no examples or references to Linux-native tools, patterns, or migration paths, and the documentation does not address Linux users' needs or scenarios.
Recommendations
- Include references to Linux-based integration platforms (e.g., Apache Camel, Talend, Mule ESB) and provide guidance for migrating from these platforms to Azure Integration Services.
- Add examples and scenarios relevant to Linux users, such as integrating with Linux file systems, cron jobs, or open-source workflow tools.
- Mention cross-platform compatibility and highlight any Azure Integration Services features that support Linux environments.
- Balance the migration guidance by providing parity for both Windows and Linux users, ensuring that Linux-first organizations see their scenarios reflected.
- If possible, provide sample code or configuration snippets for both Windows (PowerShell, SSIS) and Linux (Bash, open-source ETL tools) environments.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/security/fundamentals/ransomware-detect-respond.md
...les/security/fundamentals/ransomware-detect-respond.md
High Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (e.g., Defender for Endpoint, Security Event log, PowerShell Operational logs) and patterns (e.g., RDP, Windows event logs) without mentioning Linux equivalents. Examples and guidance are focused on Windows environments, with no parallel instructions or references for Linux-based Azure VMs or their security event sources. The documentation assumes familiarity with Windows-centric incident response workflows and omits Linux-specific detection and response strategies.
Recommendations
- Include examples and guidance for Linux-based Azure VMs, such as monitoring syslog, auditd, and Linux-specific ransomware indicators.
- Mention Linux remote access protocols (e.g., SSH) alongside RDP when discussing common entry points.
- Provide instructions for isolating Linux VMs and responding to incidents using Linux-native tools (e.g., iptables, systemctl, fail2ban).
- Reference Linux anti-malware solutions and how to integrate them with Defender for Cloud.
- Add parity in event log monitoring by describing how to detect log tampering or clearing in Linux environments.
- Ensure that incident response steps are platform-agnostic or include both Windows and Linux procedures.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/rules-engine/create-rules.md
.../main/articles/logic-apps/rules-engine/create-rules.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily centered around the Microsoft Rules Composer, which is a GUI tool that appears to be Windows-only. There are no instructions, examples, or mentions of how to perform equivalent tasks on Linux or using cross-platform tools. The documentation assumes the use of a local GUI application, with no mention of CLI, PowerShell, or Linux alternatives. .NET assemblies are referenced as data sources, reinforcing a Windows/.NET-centric workflow. There are no Linux-specific instructions, nor any guidance for users on non-Windows platforms.
Recommendations
- Explicitly state platform requirements for Microsoft Rules Composer, including whether it is Windows-only.
- If available, provide Linux or cross-platform alternatives for rule authoring and management (e.g., CLI tools, VS Code extensions, or web-based interfaces).
- Include instructions or examples for Linux users, such as how to author rulesets in XML manually or using other tools.
- If only Windows is supported, clearly call this out at the top of the documentation and suggest workarounds for Linux users (such as using a Windows VM or container).
- Consider providing REST API or SDK-based workflows that are platform-agnostic, and document these alongside the GUI tool.
- Ensure parity in documentation by including Linux and macOS where possible, or by providing explicit guidance for non-Windows environments.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/monitor-health-standard-workflows.md
...ticles/logic-apps/monitor-health-standard-workflows.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-centric tools and workflows (such as KuduPlus and CMD in the Azure portal), without mentioning or providing parity for Linux-based alternatives. There are no examples or instructions for accessing or editing files using Linux tools or command lines, and the documentation assumes a Windows environment for advanced operations. Linux users may find it unclear how to perform equivalent tasks.
Recommendations
- Include instructions or notes for accessing and editing files (such as host.json) using Linux-compatible tools (e.g., SSH, SFTP, Azure CLI, or the Bash console in Kudu).
- When referencing the Debug console, mention both CMD (Windows) and Bash (Linux) options, and provide examples for both.
- Clarify that the Azure portal and KuduPlus are available for both Windows and Linux App Service plans, and note any differences in navigation or functionality.
- Add explicit Linux command-line examples for file editing and navigation where relevant.
- Review troubleshooting and setup steps to ensure they are platform-agnostic or provide Linux-specific guidance where necessary.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/business-one-azure.md
...blob/main/articles/sap/workloads/business-one-azure.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation exhibits a Windows bias by frequently mentioning Windows and Windows Server before Linux, referencing Windows-specific tools (e.g., PowerShell, RDS), and providing more detailed guidance for Windows scenarios. Linux equivalents are mentioned but often after Windows, with less detail and no explicit Linux command examples. There is a lack of parity in practical examples and operational guidance for Linux environments.
Recommendations
- Ensure Linux and Windows are mentioned together, or alternate which is listed first, to avoid 'windows_first' bias.
- Provide equivalent Linux command-line examples (e.g., Bash/CLI) wherever PowerShell or Windows tools are referenced.
- Expand operational guidance for Linux, including details on RDP alternatives (e.g., xRDP, SSH with X11 forwarding) for client access.
- Include links to Linux-specific Azure documentation (e.g., managing VMs, networking, and storage with Bash/CLI) alongside or before Windows links.
- Add explicit examples and best practices for deploying and managing SAP Business One on Linux-based Azure VMs, matching the detail given for Windows.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/apache-kafka-confluent-cloud/troubleshoot.md
...solutions/apache-kafka-confluent-cloud/troubleshoot.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily focused on the Azure portal and Microsoft Entra, which are Windows-centric tools and services. All troubleshooting steps reference the Azure portal UI and related Microsoft tools, with no mention of command-line alternatives, cross-platform tools, or Linux-specific workflows. There are no examples or guidance for users who may be working from Linux environments or prefer CLI-based troubleshooting.
Recommendations
- Include Azure CLI and Azure PowerShell command examples alongside portal instructions, and ensure parity between Windows and Linux command-line workflows.
- Mention and link to cross-platform tools (such as Azure CLI) for resource management, troubleshooting, and role assignment.
- Add troubleshooting steps that can be performed from Linux or macOS environments, not just through the Azure portal.
- Explicitly state that the instructions apply to all platforms, and provide alternative steps for users who do not use the Azure portal UI.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sentinel/create-analytics-rule-from-template.md
...ticles/sentinel/create-analytics-rule-from-template.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page references PowerShell as a method for pushing rules to Microsoft Sentinel, without mentioning Linux-native alternatives (such as Bash, CLI, or automation via shell scripts). There are no examples or guidance for Linux users, and the only automation tool referenced is PowerShell, which is traditionally associated with Windows environments. This creates a bias towards Windows tooling and omits Linux parity.
Recommendations
- Include examples for Linux users, such as using Azure CLI or REST API via curl/bash scripts for rule management.
- Explicitly mention cross-platform options for automation, clarifying that PowerShell Core is available on Linux but also providing native Linux shell examples.
- Add guidance or links for Linux users on installing and using PowerShell Core if it is required, or provide alternative instructions using common Linux tools.
- Ensure that references to automation tools do not default to Windows-centric solutions, and present Linux options alongside or before Windows ones.
Unknown
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 page is heavily focused on Windows environments, specifically Hyper-V, and exclusively references Windows tools and workflows. All examples and instructions are tailored to Windows, such as using MMC snap-ins, registry edits, and Windows-specific paths. There is no mention of Linux equivalents, nor guidance for administrators working in non-Windows environments. The documentation assumes the reader is operating on Windows and does not provide parity for Linux users.
Recommendations
- Include information about migrating workloads from Linux-based hypervisors (e.g., KVM, Xen) if supported, or clarify platform limitations.
- Provide equivalent instructions or notes for controlling upload throughput and efficiency on Linux hosts, if applicable.
- Mention Linux-compatible migration tools or workflows, or explicitly state if the process is Windows-only.
- Add a section comparing Hyper-V migration with Linux VM migration in Azure Migrate, highlighting differences and similarities.
- Ensure future documentation includes cross-platform examples and avoids assuming a Windows-only audience.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-set-up-appliance-vmware.md
...ain/articles/migrate/how-to-set-up-appliance-vmware.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell-based installation methods, referencing Windows paths and tools (e.g., C:\Program Files), and providing detailed instructions for Windows authentication and integration (Active Directory, IIS, SQL Server) without equivalent detail for Linux systems. Linux credentials are mentioned but lack example workflows, troubleshooting, or parity in guidance. Windows-centric patterns (PowerShell, Windows authentication, IIS) are described before or instead of Linux alternatives.
Recommendations
- Provide step-by-step Linux installation examples, including shell script usage and Linux file paths.
- Include troubleshooting steps and validation instructions for Linux credentials, similar to those given for Windows/Active Directory.
- Offer guidance for agentless dependency analysis and software inventory on Linux servers, including supported authentication methods and limitations.
- Add examples for discovering and assessing Linux-specific workloads (e.g., Apache, MySQL) alongside Windows workloads (IIS, SQL Server).
- Clarify prerequisites and supported scenarios for Linux appliances, including proxy configuration and VDDK installation paths on Linux.
- Ensure screenshots and UI instructions reflect both Windows and Linux server environments where applicable.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/tutorial-assess-sql-vmware.md
...ob/main/articles/migrate/tutorial-assess-sql-vmware.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates Windows bias primarily through exclusive references to Windows-based tools and patterns, such as Windows Server Failover Clusters and Cloud Witness, and by linking only to Windows-specific best practices for SQL Server on Azure VMs. There are no examples or guidance for Linux-based SQL Server deployments, nor are Linux migration scenarios or high availability options mentioned. All technical links and recommendations are Windows-centric, and Linux is only briefly referenced in the context of Azure Hybrid Benefit licensing, not in migration or assessment procedures.
Recommendations
- Include examples and guidance for assessing and migrating SQL Server instances running on Linux (e.g., SQL Server on Ubuntu, RHEL, or SLES VMs).
- Add references and links to Linux-specific best practices for SQL Server on Azure VMs (e.g., /azure/azure-sql/virtual-machines/linux/).
- Describe high availability and disaster recovery options for Linux-based SQL Server deployments, such as Pacemaker clusters or Linux-based witness options.
- Ensure that when discussing features like Azure Hybrid Benefit, the documentation equally explains the process for Enterprise Linux subscriptions and not just Windows Server/SQL Server.
- Wherever Windows-specific tools or procedures are mentioned (e.g., Cloud Witness, Windows Server Failover Clusters), provide equivalent Linux alternatives or explicitly state their applicability or limitations for Linux.
- Consider adding a section or callout for users migrating SQL Server on Linux, outlining any differences or additional steps required.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/delete-appliance.md
...s/blob/main/articles/site-recovery/delete-appliance.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (e.g., Services.msc, World Wide Web Publishing Service, Microsoft Edge) and omitting equivalent instructions for Linux-based appliances. No Linux commands or desktop environments are mentioned, and all post-reset steps assume a Windows environment. The documentation also refers to the Azure portal and Windows-centric management patterns without acknowledging Linux alternatives.
Recommendations
- Provide equivalent instructions for Linux-based appliances, such as commands to restart the web server (e.g., systemctl restart apache2 or nginx) and clearing browser cache on popular Linux browsers.
- Mention Linux services (e.g., Apache, Nginx) if the appliance can run on Linux, or clarify if only Windows is supported.
- Include Linux command-line examples (e.g., systemctl, service) alongside Windows GUI steps.
- Avoid assuming the use of Microsoft Edge; suggest clearing cache in a cross-platform way or mention Firefox/Chrome.
- Explicitly state OS support for the appliance and tailor instructions accordingly.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-link/create-private-link-service-template.md
...s/private-link/create-private-link-service-template.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by providing only Windows-based connection instructions (RDP), using Windows tools (Remote Desktop, IIS), and offering only a PowerShell command for resource cleanup. No Linux or cross-platform alternatives are mentioned for connecting to the VM, accessing the service, or deleting resources.
Recommendations
- Add instructions for connecting to the VM using SSH for Linux-based VMs, including how to use the Azure CLI or standard SSH clients.
- Provide examples for accessing the deployed web service from a Linux VM (e.g., using curl or a browser in a Linux desktop environment).
- Include Azure CLI and/or REST API examples for resource group deletion, not just PowerShell.
- Mention Linux as a supported platform for the deployed VMs, or clarify if only Windows VMs are supported by the template.
- If IIS is used only as an example, suggest an equivalent Linux web server (e.g., Apache or Nginx) and provide instructions for that scenario.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/delete-vault.md
...-docs/blob/main/articles/site-recovery/delete-vault.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page provides only PowerShell examples for deleting an Azure Site Recovery vault, with no mention of equivalent Linux or cross-platform CLI commands. The use of PowerShell and references to Windows-centric tools (Hyper-V, VMM) dominate the instructions, and there is no guidance for users who may be operating from Linux or macOS environments. Windows tools and patterns are presented exclusively and before any Linux alternatives (which are absent).
Recommendations
- Add Azure CLI examples for deleting the Recovery Services vault, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Include notes or sections for Linux/macOS users, specifying how to perform the same actions from Bash or other shells.
- Where possible, provide parity in instructions for both PowerShell and Azure CLI, and clarify which tools are available on which platforms.
- Reference documentation for installing and using Azure CLI on Linux/macOS.
- Review other steps (such as unregistering servers or deleting policies) for any Windows-specific bias and add cross-platform alternatives.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-failback.md
.../main/articles/site-recovery/hyper-v-azure-failback.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V and System Center VMM, with all examples and instructions tailored to Windows hosts. There is no mention of Linux-based hypervisors, Linux tooling, or Linux failback scenarios, and prerequisites explicitly require Windows and Hyper-V. This creates a clear Windows bias, excluding Linux administrators and environments from the guidance.
Recommendations
- Add equivalent instructions and examples for Linux-based hypervisors (e.g., KVM, VMware on Linux) if supported by Azure Site Recovery.
- Include prerequisites and setup steps for Linux hosts, such as supported Linux distributions and required packages.
- Provide parity in failback workflows for Linux VMs, including any differences in agent installation, data synchronization, and recovery steps.
- Explicitly state platform limitations if Azure Site Recovery does not support Linux failback, and link to alternative solutions for Linux environments.
- Ensure terminology and UI references are inclusive of both Windows and Linux management tools where applicable.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/transport-layer-security.md
...ain/articles/site-recovery/transport-layer-security.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation exclusively covers enabling and verifying TLS 1.2 on Windows systems, with all examples, registry edits, and references tailored to Windows environments. There are no instructions or examples for enabling or verifying TLS 1.2 on Linux systems, nor are any Linux-specific tools or configuration files mentioned. All troubleshooting and configuration guidance assumes a Windows context.
Recommendations
- Add a section describing how to verify and enable TLS 1.2 on Linux-based Azure Site Recovery components, including relevant configuration file changes (e.g., OpenSSL, GnuTLS, or system-wide crypto policies).
- Provide Linux command-line examples (e.g., using openssl s_client or update-crypto-policies) for verifying TLS 1.2 support.
- Mention Linux equivalents for .NET Framework configuration, such as Mono or .NET Core on Linux, if applicable.
- Include troubleshooting steps and error messages relevant to Linux environments.
- Ensure that references and external links include Linux-focused resources where available.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-architecture.md
...in/articles/site-recovery/vmware-azure-architecture.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific technologies (such as VSS for app-consistent snapshots and Configuration Manager for deployment), using Windows terminology (e.g., 'office hours'), and omitting Linux-specific instructions or alternatives. There are no examples or explicit guidance for Linux VMs, their snapshotting mechanisms, or deployment tools, and Windows tools and patterns are mentioned exclusively or before any Linux equivalents.
Recommendations
- Include explicit guidance and examples for protecting Linux VMs, such as how app-consistent snapshots are handled on Linux (e.g., pre/post scripts, fsfreeze, or other mechanisms).
- Mention Linux deployment tools (e.g., Ansible, SSH scripts) alongside Configuration Manager for Mobility Service installation.
- Clarify whether features like app-consistent snapshots and VSS are Windows-only, and provide Linux alternatives or limitations.
- Use more platform-neutral language (e.g., replace 'office hours' with 'maintenance window' or specify time zones).
- Add a section or table comparing Windows and Linux support and any differences in process, requirements, or limitations.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/authorization-resource-provider.md
...cles/storage/common/authorization-resource-provider.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates Windows bias by listing Windows-centric tools (PowerShell, Azure classic CLI) before mentioning platform-neutral options like REST API. There are no explicit Linux or bash examples, and no mention of Linux-specific tools or patterns. The code samples section does not clarify platform compatibility or provide Linux command-line examples.
Recommendations
- Include explicit Linux/bash command-line examples for common management tasks.
- Mention cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools like PowerShell.
- Clarify platform compatibility for each code sample and provide instructions for running them on Linux.
- Add references or links to Linux-specific documentation or tutorials for Azure Storage management.
- Ensure REST API usage is highlighted as a cross-platform method, not secondary to Windows tools.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-autoscale.md
.../blob/main/articles/stream-analytics/cicd-autoscale.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell commands for all CI/CD and deployment steps, referencing Windows-specific tools (e.g., Connect-AzAccount, New-AzResourceGroupDeployment), and omitting any Bash, Linux, or cross-platform CLI equivalents. There are no examples or instructions for Linux or macOS users, despite the use of Visual Studio Code (which is cross-platform) and Node.js-based tools. The documentation also refers to 'PowerShell' explicitly in several sections, reinforcing the Windows-centric approach.
Recommendations
- Provide equivalent Bash or Azure CLI command examples for all steps, especially for deployment and Azure authentication.
- Explicitly mention that the CI/CD tool and Visual Studio Code are cross-platform, and provide instructions for Linux/macOS users.
- Use neutral language (e.g., 'terminal' instead of 'PowerShell') and clarify that commands can be run in any shell where Node.js and npm are available.
- Include screenshots or notes relevant to Linux/macOS environments where file paths or UI elements may differ.
- List both Windows and Linux/macOS instructions side by side or in tabs to ensure parity and inclusivity.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/debug-locally-using-job-diagram.md
...es/stream-analytics/debug-locally-using-job-diagram.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exclusively references Visual Studio, a Windows-centric tool, for local debugging of Azure Stream Analytics queries. There are no mentions of Linux-compatible alternatives, nor are there examples or instructions for performing similar tasks on Linux or macOS. The workflow, screenshots, and next steps all assume the use of Visual Studio, reinforcing a Windows-first approach and omitting Linux parity.
Recommendations
- Include instructions or references for performing local debugging of Stream Analytics queries using cross-platform tools such as Visual Studio Code, Azure CLI, or other supported environments.
- Provide explicit examples for Linux and macOS users, including setup steps and screenshots where applicable.
- Mention any limitations or differences in functionality between Windows (Visual Studio) and Linux/macOS environments.
- If Visual Studio is required, clarify whether it can be used on Linux (e.g., via Visual Studio Code or remote development) and provide guidance for those platforms.
- Add parity in troubleshooting steps and job diagram visualization for non-Windows users.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/kafka-output.md
...cs/blob/main/articles/stream-analytics/kafka-output.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in its instructions for uploading certificates to Azure Key Vault. All CLI examples are given using PowerShell syntax, and file path examples use Windows-style paths (e.g., C:\Users\Downloads\certificatefile.pem). There is no mention of Linux or macOS equivalents, nor are there examples using Bash or Linux file paths. The guidance for setting up Azure CLI locally refers to PowerShell, implicitly prioritizing Windows users.
Recommendations
- Provide equivalent Bash/Linux/macOS examples for Azure CLI commands, including file path formats (e.g., /home/user/certificatefile.pem).
- Explicitly mention that Azure CLI works across platforms and link to platform-specific installation guides.
- Include notes or examples for common Linux/macOS certificate locations and path conventions.
- Avoid language that assumes PowerShell or Windows as the default environment; use neutral phrasing such as 'your terminal' or 'command line'.
- Where screenshots or instructions reference file dialogs or path copying, clarify the steps for both Windows and Linux/macOS users.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/custom-providers/tutorial-custom-providers-function-setup.md
...-providers/tutorial-custom-providers-function-setup.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation assumes use of the Azure portal and .NET/C# for function app development, which are cross-platform but have historically been more Windows-centric. There are no explicit examples or instructions for Linux users (e.g., using Azure CLI, VS Code on Linux, or command-line tools), and the workflow described aligns more closely with Windows/portal-first development patterns.
Recommendations
- Add instructions for setting up Azure Functions using the Azure CLI or Azure Functions Core Tools, which are cross-platform and commonly used on Linux.
- Include examples for editing project files and managing dependencies from the command line, not just through the Azure portal.
- Mention and link to Linux-specific or cross-platform development guides (e.g., using VS Code on Linux, or developing with Python/Node.js).
- Clarify that all steps can be performed on Linux and macOS, and provide any platform-specific notes if needed.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-signalr/signalr-concept-disaster-recovery.md
...les/azure-signalr/signalr-concept-disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides configuration examples and command-line instructions primarily in Windows-centric formats (e.g., references to web.config, environment variable naming conventions, and use of dotnet user-secrets commands). There are no explicit Linux or cross-platform configuration examples, nor are Linux-specific tools or patterns (such as bash scripts, systemd, or Linux environment variable conventions) mentioned. The documentation assumes familiarity with Windows conventions and does not offer parity for Linux users.
Recommendations
- Include Linux-specific configuration examples, such as using environment variables in bash, editing appsettings.json, or using systemd service files.
- Provide equivalent Linux command-line instructions for setting secrets (e.g., using export, .env files, or Azure CLI on Linux).
- Clarify environment variable naming conventions for both Windows (double underscore) and Linux (colon or underscore).
- Mention cross-platform configuration file locations and patterns (e.g., ~/.aspnet/ for user secrets on Linux).
- Add notes or examples for deploying and managing SignalR service in Linux environments, including Azure Functions on Linux.
- Ensure diagrams and terminology do not assume a Windows-only deployment model.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/exchange-and-refund-azure-reservations.md
...reservations/exchange-and-refund-azure-reservations.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and screenshots for the Azure Portal UI, which is most commonly accessed via Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux or cross-platform tools for managing reservations. Additionally, the only specific OS reference in the content is to 'Windows software costs not included with reservations' in the related links, with no Linux equivalent. This may leave Linux users or those preferring automation via CLI without clear guidance.
Recommendations
- Add Azure CLI examples for exchanging and refunding reservations, as Azure CLI is cross-platform and widely used on Linux.
- If PowerShell examples are provided, ensure Azure CLI or Bash equivalents are also present and given equal prominence.
- Include references to Linux-specific documentation or considerations where relevant, such as managing reservations from Linux environments.
- Clarify that the Azure Portal is accessible from any OS, and provide instructions for both GUI and command-line workflows.
- Review related links to ensure parity between Windows and Linux topics (e.g., include a link to Linux reservation cost considerations if available).
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/lab-services/manage-labs.md
...re-docs/blob/main/articles/lab-services/manage-labs.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively describes managing labs using the Azure portal, a graphical tool that is most familiar to Windows users. There are no examples or instructions for managing labs via command-line tools such as Azure CLI, PowerShell, or Bash, nor are there any references to Linux-specific workflows. This can disadvantage Linux users or those who prefer automation and scripting.
Recommendations
- Add examples for managing labs using Azure CLI commands, which are cross-platform and work on Linux, macOS, and Windows.
- Include sample scripts or command-line instructions for viewing and deleting labs, in addition to the portal-based steps.
- Explicitly mention that the Azure portal is cross-platform but provide parity for users who prefer or require command-line access.
- Reference relevant documentation for both Azure CLI and PowerShell, making clear that both are supported.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/add-agent-tools-connector-actions.md
...ticles/logic-apps/add-agent-tools-connector-actions.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively references the Azure portal and Foundry portal web interfaces, which are Microsoft-centric tools. There are no examples or instructions for Linux-native tools, CLI usage, or cross-platform alternatives. All workflows assume use of the Azure web UI, which is most familiar to Windows users, and there is no mention of Linux command-line tools, automation via shell scripts, or guidance for non-Windows environments.
Recommendations
- Provide equivalent instructions using the Azure CLI and/or Azure PowerShell, making clear which commands work cross-platform.
- Include examples or notes for Linux users, such as how to perform tasks via the CLI or automation scripts.
- Mention and link to documentation for cross-platform tools where available, such as Azure CLI installation and usage on Linux and macOS.
- Clarify that the Azure portal and Foundry portal are accessible from any modern browser on any OS, and explicitly state any OS-specific requirements if they exist.
- If possible, add screenshots or terminal examples from Linux environments to demonstrate parity.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-connector/tutorial-python-aks-openai-workload-identity.md
...nector/tutorial-python-aks-openai-workload-identity.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation relies exclusively on Azure CLI and Bash commands, which are cross-platform, but does not provide any explicit Linux-specific instructions or examples. However, there is a subtle Windows bias in the way prerequisites and instructions are presented: there are no explicit Linux shell or package manager installation steps, and the Azure CLI is often associated with Windows-first onboarding. There are no PowerShell or Windows-only tools, but the lack of Linux-specific troubleshooting or environment setup may disadvantage Linux users.
Recommendations
- Add explicit Linux installation instructions for Azure CLI, Docker, and kubectl, including common package manager commands (e.g., apt, yum, zypper).
- Include notes or troubleshooting tips for common Linux-specific issues (e.g., permissions, Docker group membership, firewall).
- Clarify that all CLI commands are cross-platform and provide any necessary adaptations for Linux/macOS environments.
- Where GUI (Portal) instructions are given, mention that they are OS-agnostic.
- Consider adding a section or callout for Linux users to ensure parity and inclusivity.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/managed-grafana/how-to-authentication-permissions.md
...s/managed-grafana/how-to-authentication-permissions.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively describes configuration steps using the Azure Portal GUI, which is most commonly accessed via Windows environments. There are no examples or instructions for performing these tasks using cross-platform tools such as the Azure CLI or Azure PowerShell, nor are there any Linux-specific instructions or terminal-based workflows. This may disadvantage Linux users or those who prefer command-line interfaces.
Recommendations
- Add equivalent instructions for configuring managed identities and role assignments using the Azure CLI (az) with example commands.
- Include PowerShell examples, but ensure Azure CLI examples are presented first or alongside them, as Azure CLI is cross-platform.
- Explicitly mention that all steps can be performed from any OS using the Azure CLI or Azure Cloud Shell.
- Provide links to relevant Azure CLI and PowerShell documentation for identity and role assignment management.
- Consider including a section or callout for Linux/macOS users, highlighting cross-platform workflows.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sentinel/connect-services-diagnostic-setting-based.md
.../sentinel/connect-services-diagnostic-setting-based.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation focuses exclusively on Azure Portal UI workflows and does not provide any command-line examples. While it avoids explicit Windows tools or PowerShell, it also does not mention or provide parity for Linux-based automation (such as Azure CLI or Bash scripting). The only command-line reference is a link to Azure Monitor documentation with a '?tabs=CMD' parameter, but no CLI or Linux-specific instructions are surfaced in this article. This results in an implicit bias towards users who rely on graphical interfaces, which are more common in Windows environments, and leaves out Linux-first or automation-focused users.
Recommendations
- Add Azure CLI examples for configuring diagnostic settings and connecting resources to Microsoft Sentinel, alongside the portal instructions.
- Explicitly mention and link to Linux-compatible automation methods (e.g., Bash scripts, az CLI) for each major workflow.
- Ensure that any referenced documentation includes both Windows (PowerShell) and Linux (Bash/CLI) tabs or examples.
- Consider including a section or appendix summarizing cross-platform automation options for these tasks.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/peering-service/connection.md
...-docs/blob/main/articles/peering-service/connection.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation references analysis of 'Windows and Microsoft 365 telemetry' for latency measurements, implying a focus on Windows-based environments. There are no examples or mentions of Linux or cross-platform telemetry sources, nor are there any Linux-specific instructions or considerations.
Recommendations
- Clarify whether telemetry analysis supports Linux endpoints or only Windows/Microsoft 365 clients.
- If Linux is supported, provide examples or documentation references for collecting and analyzing telemetry from Linux systems.
- Avoid language that implies exclusivity to Windows unless technically required, and explain any platform limitations.
- Include cross-platform guidance or explicitly state platform requirements for Peering Service telemetry and connection setup.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/peering-service/customer-walkthrough.md
.../main/articles/peering-service/customer-walkthrough.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes the Azure portal (GUI) workflow without referencing any command-line tools or scripts. While it does not explicitly mention Windows-specific tools like PowerShell, the absence of CLI (such as Azure CLI or Bash) examples or Linux-specific guidance can be considered a form of implicit Windows bias, as many cross-platform users expect parity in automation and scripting options.
Recommendations
- Add Azure CLI command-line examples for prefix activation and configuration steps, suitable for both Windows and Linux environments.
- Include Bash shell script snippets where applicable, to demonstrate automation for Linux users.
- Explicitly mention that all steps can be performed via the Azure CLI or REST API, and provide links to relevant documentation.
- Ensure that screenshots and instructions do not assume a Windows-only environment (e.g., avoid showing only Windows-style file paths or UI elements if possible).
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/nat-gateway-design.md
...s/blob/main/articles/nat-gateway/nat-gateway-design.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits subtle Windows bias by mentioning Windows-specific services (Windows Activation and Windows Updates) as examples of workloads requiring outbound connectivity, without referencing Linux equivalents. There are no command-line examples, but when discussing services impacted by outbound connectivity, only Windows is named. No Linux-specific services or update mechanisms are mentioned, and no Linux-centric scenarios are provided.
Recommendations
- Include examples of Linux workloads that require outbound connectivity, such as package updates (apt, yum, etc.), security patching, or connecting to Linux repositories.
- Mention that Linux virtual machines also require outbound connectivity for OS updates and activation of certain enterprise features.
- Provide parity by listing both Windows and Linux services that may be impacted by lack of outbound connectivity.
- If discussing activation or update scenarios, clarify that the need for outbound connectivity applies to all operating systems, not just Windows.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-migrate-outbound-nat.md
.../articles/nat-gateway/tutorial-migrate-outbound-nat.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The tutorial exclusively uses the Azure portal UI for all instructions, which is a cross-platform interface. However, there are no command-line examples provided (such as Azure CLI, PowerShell, or Bash). When command-line instructions are omitted, Windows users are implicitly prioritized, as Azure documentation often defaults to PowerShell in such cases. There is no mention of Linux-specific tools, nor any parity between PowerShell and Bash/CLI examples. The documentation does not acknowledge Linux workflows or provide guidance for users who prefer command-line automation, which is common in Linux environments.
Recommendations
- Add Azure CLI examples for each major step, as Azure CLI is cross-platform and widely used on Linux.
- If PowerShell examples are provided, ensure Bash equivalents are included and presented with equal prominence.
- Explicitly mention that all steps can be performed using Azure CLI or ARM templates, and link to relevant documentation.
- Include a section on automating the migration using scripts, with both Bash (Linux) and PowerShell (Windows) samples.
- Review terminology and instructions to ensure they do not assume a Windows-centric workflow (e.g., avoid references to Windows-only tools or patterns).
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/encryption-feature-deprecation.md
...ticles/site-recovery/encryption-feature-deprecation.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation focuses exclusively on Hyper-V virtual machines, a Windows-centric technology, and does not mention or provide guidance for Linux-based VMs or other platforms. All examples and remediation steps are tailored to Windows environments, with no Linux equivalents or cross-platform considerations discussed.
Recommendations
- Include information about how the deprecation affects Linux VMs or other non-Hyper-V platforms supported by Azure Site Recovery.
- Provide remediation steps and examples for Linux-based disaster recovery scenarios, including references to relevant tools and commands.
- Add a section comparing the impact and process for both Windows (Hyper-V) and Linux VMs to ensure parity and clarity for all users.
- Mention any differences in encryption at rest implementation or requirements for Linux VMs.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/spring-apps/enterprise/quickstart-automate-deployments-github-actions-enterprise.md
...ckstart-automate-deployments-github-actions-enterprise.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation uses Azure CLI commands throughout, which are cross-platform, but all shell examples are presented in Bash syntax (using backslashes for line continuation and 'read' commands), with no explicit mention of Windows (CMD or PowerShell) equivalents. There are no PowerShell or Windows CMD examples, but the instructions implicitly assume a Unix-like shell environment, which may not be familiar to Windows users who do not use WSL or Git Bash. No guidance is provided for running these commands on native Windows shells.
Recommendations
- Add a note clarifying that the Azure CLI commands are shown in Bash syntax and provide guidance for Windows users (e.g., using PowerShell or CMD).
- Provide equivalent PowerShell or CMD command examples, or link to Azure CLI documentation on running commands in different shells.
- Explicitly mention that tools like 'jq' may need to be installed separately on Windows and provide installation instructions or alternatives.
- Consider including a short section or callout for Windows users who may not have Bash available, recommending WSL, Git Bash, or showing how to adapt commands for PowerShell.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-network-security-manage-exceptions.md
...e/common/storage-network-security-manage-exceptions.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both PowerShell and Azure CLI examples for managing network security exceptions, but PowerShell (a Windows-centric tool) is presented before Azure CLI (cross-platform). There is no explicit Linux example or mention of Linux-specific tools or shell environments. The ordering and emphasis may subtly favor Windows users.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding Bash or shell script examples for Linux users, or at least clarify that Azure CLI commands can be run in Bash.
- If possible, include links or notes about using Azure CLI in native Linux environments or via WSL on Windows.
- Review other documentation pages to ensure Linux parity and avoid implicit prioritization of Windows tools.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/copy-job.md
...e-docs/blob/main/articles/stream-analytics/copy-job.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation exclusively references Visual Studio Code and its Azure Stream Analytics extension as the tool for exporting and importing jobs, without mentioning or providing examples for Linux-native tools, CLI commands, or alternative editors. There are no instructions or screenshots for Linux environments, and no mention of cross-platform considerations.
Recommendations
- Explicitly state that Visual Studio Code is available on Windows, Linux, and macOS, and clarify that the extension works across these platforms.
- Provide command-line examples using Azure CLI or Azure PowerShell for exporting and importing Stream Analytics jobs, ensuring parity for users who prefer terminal-based workflows.
- Include screenshots or instructions that reflect Linux desktop environments (e.g., Ubuntu, GNOME, KDE) to demonstrate cross-platform support.
- Mention any platform-specific prerequisites or differences, such as file paths or permissions, when exporting jobs.
- If Visual Studio Code is the only supported method, clearly state this and provide guidance for Linux users on installing and using VS Code.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-queues-introduction.md
...articles/storage/queues/storage-queues-introduction.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits a subtle Windows bias, primarily in the 'Next steps' section. The quickstart links for .NET, Java, Python, and Node.js all include 'environment-variable-windows' in their tab parameters, indicating that Windows environment variable setup is prioritized or exclusively shown. There is no explicit mention of Linux or cross-platform command-line examples, and no Linux-specific instructions or parity is visible.
Recommendations
- Add Linux and macOS environment variable setup instructions and tabs to all quickstart guides.
- Ensure that all code and CLI examples are available for Bash (Linux/macOS) as well as PowerShell/Windows.
- Where possible, present cross-platform examples first, or provide a clear choice between Windows and Linux/macOS instructions.
- Review linked quickstart guides to ensure Linux parity and update tab parameters to include 'environment-variable-linux' or similar.
- Explicitly mention that Azure Queue Storage is accessible from all major platforms, and provide links or notes for non-Windows users.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/job-config-json.md
...blob/main/articles/stream-analytics/job-config-json.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses exclusively on Visual Studio Code for creating and managing Azure Stream Analytics jobs, without mentioning Linux-specific workflows, tools, or examples. All references to development and testing are tied to Visual Studio Code, which, while cross-platform, is often associated with Windows environments. There are no examples or instructions for using Linux-native editors, command-line tools, or shell environments.
Recommendations
- Include explicit instructions or examples for Linux users, such as using VS Code on Linux, or alternative editors and command-line workflows.
- Mention cross-platform compatibility of Visual Studio Code and clarify any OS-specific requirements or limitations.
- Provide examples of managing JobConfig.json files using Linux shell commands (e.g., cat, nano, vim) and Azure CLI.
- Add a section on deploying and testing Stream Analytics jobs from Linux environments, including any relevant tools or scripts.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-operations/discover-manage-assets/howto-use-mqtt-connector.md
...ons/discover-manage-assets/howto-use-mqtt-connector.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation page provides instructions primarily through the Azure web UI and does not present any command-line examples for either Windows (PowerShell/Command Prompt) or Linux (Bash). However, there is a notable absence of Linux-specific guidance, such as Bash CLI commands, YAML manifests, or references to Linux-native tools, especially given the context of Kubernetes and MQTT, which are commonly managed on Linux systems. The only CLI mentioned is the Azure CLI, which is cross-platform, but no explicit Linux examples or considerations are provided.
Recommendations
- Add explicit Bash or shell command examples for Linux users, especially for tasks like creating Kubernetes secrets (e.g., using kubectl).
- Include YAML manifest examples for Kubernetes resource creation, which are platform-agnostic and familiar to Linux users.
- Clarify that the Azure CLI commands work on both Windows and Linux, and provide sample commands for both platforms where relevant.
- Mention any Linux-specific considerations (such as file paths, permissions, or environment variables) where applicable.
- If screenshots are used, consider including examples from both Windows and Linux environments to ensure parity.