274
Pages Scanned
116
Pages Flagged
274
Changed Pages
42.3%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-03-07 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure Compute
Current Phase: discovery
Files Queued: 274
Files Completed: 274
Problematic Pages
116 issues found
Service Fabric
Initializer CodePackages in Service Fabric
...in/articles/service-fabric/initializer-codepackages.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page for Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples use Windows container images (nanoserver), Windows paths (C:\), and Windows shell commands (cmd, echo, type, ping). There are no Linux container examples, nor any mention of Linux-compatible paths, commands, or images. The ApplicationManifest and ServiceManifest examples exclusively reference Windows-specific configurations. The page also explicitly states that the example assumes familiarity with creating Windows container applications.
Recommendations
- Add examples using Linux container images (e.g., Ubuntu, Alpine) and Linux shell commands (bash, echo, cat, etc.).
- Show how to specify Linux-compatible paths and volume mounts (e.g., /workspace/log.txt).
- Clarify whether Initializer CodePackages are supported for Linux containers in Service Fabric, and if so, provide parity in documentation.
- If Initializer CodePackages are Windows-only, state this explicitly at the top of the page to avoid confusion.
Create Pull Request
Service Fabric
Azure Service Fabric reverse proxy
...articles/service-fabric/service-fabric-reverseproxy.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation clearly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and instructions are implicitly Windows-centric. There are no Linux-specific examples or guidance, and the feature is unavailable for Linux users, which is acknowledged but not elaborated upon.
Recommendations
- Explicitly highlight the lack of Linux support earlier and more prominently, including in the introduction and summary.
- Provide alternative guidance or links for Linux users, such as recommended patterns for service discovery and communication in Linux Service Fabric clusters.
- Document any roadmap or workarounds for Linux users, or clarify if/when Linux support may be expected.
- Consider adding a section summarizing limitations and alternatives for Linux clusters.
Service Fabric
Standalone Service Fabric clusters overview
...-fabric/service-fabric-standalone-clusters-overview.md
High Priority
View Details â
Detected Bias Types
missing_linux_example
windows_first
Summary
Although the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the documentation later states that Linux isn't yet supported for standalone clusters. All examples and supported OS lists are Windows-only, and Windows security options are described in detail, with no Linux equivalents or instructions provided.
Recommendations
- Clarify early in the documentation that standalone clusters are currently Windows-only, to avoid misleading Linux users.
- Remove or rephrase statements suggesting Linux support for standalone clusters unless/when it becomes available.
- If Linux support is planned, provide a roadmap or guidance for Linux users.
- Ensure that all security and operational examples either include Linux equivalents or explicitly state their absence.
Service Fabric
Service Fabric Explorer blocking operations
...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page primarily references Az PowerShell cmdlets for managing Service Fabric resources, with explicit links to PowerShell modules. While the az CLI is mentioned for deleting applications, PowerShell is presented first and more frequently, potentially creating friction for Linux/macOS users who typically use the az CLI. There are no explicit Linux/macOS examples or references to Bash or shell scripting.
Recommendations
- Add az CLI examples for all operations (unprovision, create, delete) alongside PowerShell examples.
- Clarify that az CLI is cross-platform and provide links to relevant az CLI documentation.
- Consider presenting az CLI examples before PowerShell, or at least in parallel, to improve parity.
- Explicitly mention that PowerShell is available cross-platform, but az CLI is often preferred on Linux/macOS.
Service Fabric
Deploy and upgrade with Azure Resource Manager
...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides PowerShell-only examples for removing Service Fabric application resources and references Remove-AzResource as the main tool, with no equivalent Azure CLI, Bash, or cross-platform REST examples. This creates friction for Linux/macOS users, who may not have access to PowerShell or prefer other tools. The rest of the documentation is largely platform-neutral, focusing on ARM templates, but operational examples are Windows-centric.
Recommendations
- Add Azure CLI examples for resource removal (e.g., using az resource delete) alongside PowerShell.
- Explicitly mention and provide REST API examples with curl for cross-platform users.
- Clarify that PowerShell is not required and that all operations can be performed via Azure CLI or REST.
- Where PowerShell is shown, provide equivalent Bash/CLI commands or reference them in 'See also'.
Service Fabric
Deny assignment policy for Service Fabric managed clusters
...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides best practice examples using Azure PowerShell modules and references PowerShell-based tools before mentioning cross-platform alternatives like Azure CLI and sfctl. The PowerShell examples are prominent, and the guidance links primarily to PowerShell documentation, which may create friction for Linux/macOS users who prefer CLI or ARM/Bicep templates.
Recommendations
- Add explicit Azure CLI examples alongside PowerShell examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets).
- Ensure CLI and Bicep/ARM template usage is given equal prominence in guidance and links.
- Clarify which tools are cross-platform and which are Windows-only, especially in the best practices section.
- Consider providing sample commands for sfctl where relevant, as it is cross-platform.
Service Fabric
Service Fabric Cluster Resource Manager - Application Groups
...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides PowerShell examples exclusively for command-line operations related to Service Fabric Application Groups, with no mention of Linux-compatible tools or CLI equivalents. All command-line instructions use PowerShell cmdlets, which are native to Windows. There is no guidance for Linux/macOS users on how to perform these tasks, nor are cross-platform alternatives (such as Azure CLI or REST API) referenced.
Recommendations
- Add Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and supported on Linux/macOS.
- Mention REST API endpoints or SDK usage for application management where applicable.
- Clearly state if PowerShell is required and provide guidance for Linux/macOS users (e.g., using PowerShell Core or alternative tools).
- If certain operations are only possible via PowerShell, explicitly note this limitation and link to relevant cross-platform solutions or workarounds.
Service Fabric
Upgrade an Azure Service Fabric standalone cluster
...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page references Windows-specific upgrade paths and tools, such as linking to 'service-fabric-cluster-upgrade-windows-server.md' and 'service-fabric-cluster-config-upgrade-windows-server.md'. The Patch Orchestration Application is described as 'for Windows', with no mention of Linux equivalents or guidance. There are no explicit Linux examples or references, and Windows terminology appears first or exclusively in upgrade instructions.
Recommendations
- Add links and instructions for upgrading Service Fabric standalone clusters on Linux, if supported.
- Include Linux-specific configuration and upgrade guidance alongside Windows instructions.
- Clarify whether Patch Orchestration Application or similar solutions exist for Linux clusters.
- Ensure parity in examples and references for both Windows and Linux environments.
Service Fabric
Azure Service Fabric hosting model
...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell examples and references PowerShell cmdlets for managing Service Fabric services, but does not include equivalent Linux CLI or cross-platform examples. Windows tooling (PowerShell) is mentioned first and exclusively in command-line sections, creating friction for Linux/macOS users who may use Service Fabric CLI or REST APIs instead.
Recommendations
- Add Service Fabric CLI (sfctl) examples for Linux/macOS users alongside PowerShell examples.
- Mention REST API usage more prominently and provide concrete REST examples, not just links.
- Clarify which management tools are cross-platform and which are Windows-only.
- Consider including bash or shell script examples where applicable.
- Explicitly state PowerShell cmdlets are Windows-only and suggest alternatives for Linux/macOS.
Service Fabric
Scalability of Service Fabric services
.../service-fabric/service-fabric-concepts-scalability.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides code examples and administrative instructions primarily using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or bash examples, nor are Linux-native tools or patterns mentioned. PowerShell commands are referenced before any mention of Linux alternatives, and the administrative actions section exclusively uses Windows tooling. This creates friction for Linux users, who must translate these examples or find their own equivalents.
Recommendations
- Add equivalent Linux CLI examples (e.g., using sfctl or bash scripts) alongside PowerShell examples.
- Mention Linux-native tools (such as sfctl) and provide links to their documentation.
- Where administrative actions are described, explicitly note how to perform them on Linux clusters.
- Ensure code samples are platform-neutral or provide both Windows and Linux versions.
- Clarify any platform-specific limitations or differences in the examples.
Service Fabric
Change Azure Service Fabric cluster settings
...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides a comprehensive reference of Service Fabric cluster settings, but exhibits some Windows bias. Windows-specific terminology (e.g., certificate store names like 'MY', 'LocalMachine', NTLM authentication, Windows account types) is used throughout, often without Linux equivalents or clarification. Windows tools and patterns (such as certificate store access, NTLM, and account types) are mentioned exclusively or before Linux alternatives. Some settings (like log file paths, account types, and container network setup) default to Windows values or only reference Windows behaviors. Linux-specific options are present in some places (e.g., 'LinuxExternalExecutablePath', 'X509Folder'), but are not consistently explained or prioritized. There are missing Linux examples or guidance for several settings, especially those referencing Windows stores, accounts, or authentication.
Recommendations
- For each parameter referencing Windows-specific concepts (e.g., certificate stores, NTLM, account types), add Linux equivalents or clarify Linux behaviors.
- Where settings differ between Windows and Linux (e.g., default values, paths, authentication), explicitly document both platforms.
- Provide Linux-specific examples or guidance, especially for certificate management, account configuration, and file paths.
- Review and update descriptions to avoid Windows terminology as the default; use cross-platform language where possible.
- Add a summary table or section highlighting platform-specific settings and differences.
Service Fabric
Azure Service Fabric DNS service
...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI or scripting examples. Windows tools (PowerShell, ApplicationManifest.xml via Visual Studio) are mentioned before Linux alternatives, and Linux-specific limitations are listed but not accompanied by guidance or parity examples. There is no mention of how Linux users can set DNS names via CLI (e.g., Bash, Azure CLI), nor are Linux-friendly workflows or code samples provided.
Recommendations
- Add Linux CLI examples (e.g., Azure CLI, Bash scripts) for setting DNS names and managing Service Fabric services.
- Explicitly document how Linux users can perform equivalent tasks, such as configuring DNS names, without relying on PowerShell or Visual Studio.
- Provide guidance for Linux users on editing ARM templates and deploying services, including any required tools or commands.
- Clarify Linux limitations with actionable alternatives or workarounds, such as using ARM templates or REST APIs.
- Ensure code samples and instructions are platform-neutral or provide both Windows and Linux variants.
Service Fabric
Azure Service Fabric Auto Scaling Services and Containers
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides examples for configuring auto scaling policies in Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no equivalent Bash, Linux CLI, or cross-platform scripting examples. PowerShell is presented as the only scripting option, which creates friction for Linux/macOS users. Additionally, there is no mention of Linux-specific tools or commands, and PowerShell examples are given after C# but before any Linux alternatives (which are missing).
Recommendations
- Add Bash or Azure CLI examples for configuring scaling policies, especially for Linux clusters.
- Clarify which PowerShell commands are cross-platform (if any), or provide alternatives for Linux/macOS users.
- Explicitly mention any limitations or differences for Linux clusters, and link to relevant Linux documentation.
- Consider including sample scripts or instructions for Linux users, such as using REST APIs or Azure CLI.
- Indicate whether PowerShell examples are usable on Linux (PowerShell Core), or if they're Windows-only.
Service Fabric
Specifying Service Fabric service endpoints
...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell example for deploying Service Fabric applications, which is Windows-centric. References to the Service Fabric SDK schema location use a Windows file path first, and PowerShell is mentioned as the primary deployment tool. Linux-specific deployment tools or examples (such as Azure CLI or Bash) are not provided, though there is a brief mention of Linux certificate store location. The overall guidance and XML manifest examples are platform-neutral, but deployment instructions and tooling are Windows-biased.
Recommendations
- Add Linux/macOS deployment examples using Azure CLI or Bash scripts alongside PowerShell examples.
- Mention cross-platform tools (e.g., Azure CLI, REST API) for application deployment.
- Provide Linux file path equivalents for SDK/schema locations if relevant.
- Clarify which steps are platform-specific and offer alternatives for Linux/macOS users.
Virtual Machines
Ultra Disks for VMs - Azure Managed Disks
...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides examples for deploying Ultra Disks using Azure Portal, CLI, and PowerShell. However, throughout the CLI and PowerShell sections, the VM image used in all code samples is 'Win2016Datacenter', and there are no equivalent examples for Linux VM images (e.g., Ubuntu, CentOS). The Quickstart link in the Portal section also points to Windows VM creation. This creates friction for Linux users, as they must adapt the examples themselves. The documentation does state Ultra Disks apply to both Linux and Windows VMs, but practical Linux guidance is missing.
Recommendations
- Add Linux VM image examples (e.g., UbuntuLTS) alongside Windows examples in CLI and PowerShell sections.
- Provide a Quickstart link for creating a Linux VM in the Azure portal.
- Explicitly mention how to adapt the CLI/PowerShell commands for Linux VMs (e.g., changing the --image parameter).
- Ensure screenshots and portal instructions are not Windows-centric, or clarify that the steps are identical for Linux VMs.
Virtual Machines
Upload a VHD to Azure or copy a disk across regions - Azure CLI
...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides a Windows-centric example for uploading a VHD using AzCopy (with 'AzCopy.exe' and Windows file paths), but does not offer a Linux/macOS equivalent. The AzCopy upload command is only shown for Windows, and Linux/macOS users are not given a corresponding example or guidance. Additionally, the Windows example appears before any mention of Linux usage, despite the page targeting both Linux and Windows VMs.
Recommendations
- Add an AzCopy upload example for Linux/macOS, using the 'azcopy' binary and typical Linux file paths (e.g., '/home/user/mydisk.vhd').
- Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
- Present both Windows and Linux/macOS examples side by side, or note any OS-specific syntax differences.
- Ensure that file size commands (e.g., 'wc -c', 'ls -al') are explained for both platforms, or provide Windows equivalents (e.g., 'dir').
Service Fabric
Manage certificates in a Service Fabric cluster
...vice-fabric/cluster-security-certificate-management.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits a moderate Windows bias. PowerShell is the only scripting example given for certificate enrollment, and the Key Vault VM extension is discussed primarily in its Windows variant. The documentation references Windows-specific certificate store locations and ACLing patterns, and the Key Vault VM extension is described using its Windows-specific schema and behaviors. There is no mention of Linux equivalents (e.g., Key Vault VM extension for Linux), nor are Bash/CLI examples provided. Windows tools and patterns are presented first and sometimes exclusively, which may create friction for Linux users.
Recommendations
- Add parallel examples using Azure CLI and/or Bash for certificate enrollment and management, alongside or instead of PowerShell.
- Explicitly mention and link to the Key Vault VM extension for Linux, and clarify any differences in behavior or configuration.
- Discuss certificate store locations and ACLing for Linux nodes (e.g., /etc/ssl/certs, permissions, etc.), not just Windows certificate stores.
- Where Windows-specific behaviors are described (such as S-channel or CERT_RENEWAL_PROP_ID), add notes about Linux equivalents or clarify if not applicable.
- Provide at least one end-to-end example for a Service Fabric cluster running on Linux nodes, or clarify if certain features are Windows-only.
Service Fabric
X.509 Certificate-based Authentication in a Service Fabric Cluster
...ticles/service-fabric/cluster-security-certificates.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters. However, there is evidence of Windows bias: Windows certificate store paths and terminology are mentioned first and more frequently, Windows-specific tools and APIs (e.g., Win32 CryptoAPI, CertGetCertificateChain, CAPI2 logging) are referenced without Linux equivalents, and troubleshooting sections focus on Windows event logs and error codes. Linux paths (e.g., /var/lib/sfcerts) are mentioned only in passing, and there are no Linux/macOS-specific troubleshooting steps or tool recommendations.
Recommendations
- Add Linux/macOS certificate store paths and management instructions alongside Windows examples.
- Include troubleshooting steps for Linux/macOS nodes, such as relevant log locations and commands (e.g., journalctl, openssl, systemd logs).
- Reference Linux certificate validation APIs/tools (e.g., OpenSSL, NSS, GnuTLS) where Windows CryptoAPI is discussed.
- Provide Linux/macOS error codes and remediation steps for common certificate issues.
- Ensure examples and configuration snippets are platform-neutral or include both Windows and Linux variants.
Service Fabric
Introduction to the Service Fabric Infrastructure Service
.../articles/service-fabric/infrastructure-service-faq.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a tool with Windows-centric usage). No Linux CLI or cross-platform alternatives are mentioned for cluster operations or command execution. While Service Fabric clusters can run on both Windows and Linux, the guidance here assumes Windows tooling and patterns.
Recommendations
- Add equivalent Linux CLI (e.g., sfctl) or REST API examples for cluster operations, especially for bypassing Infrastructure Service.
- Clarify whether Service Fabric Explorer is available/cross-platform, or provide alternatives for Linux users.
- Where PowerShell is used, note if the command can be run from Azure Cloud Shell (which supports Linux), or provide Bash equivalents if possible.
- Explicitly state if certain operations are Windows-only, or provide guidance for Linux clusters.
Service Fabric
Migrate an Azure Service Fabric cluster to availability zone support
...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides migration guidance for Azure Service Fabric clusters to availability zone support. While most of the content is platform-neutral (focused on Azure Resource Manager templates and JSON), the critical migration steps for clusters with Basic SKU load balancer and IP resources rely exclusively on PowerShell commands and Windows-centric tooling (e.g., Remove-AzureRmVmss, Connect-ServiceFabricCluster). These commands are presented without Linux/bash equivalents, and the PowerShell examples are shown first and only. Additionally, some sample templates referenced are Windows-specific, though at least one Ubuntu sample is linked.
Recommendations
- Provide equivalent bash/CLI examples for all PowerShell commands, especially for cluster node management and resource cleanup.
- Explicitly mention whether the PowerShell steps can be performed using Azure CLI or REST API, and link to relevant documentation.
- Add guidance for Linux/macOS users, including any prerequisites or limitations for Service Fabric cluster management on non-Windows platforms.
- Ensure sample templates include both Windows and Linux VM options, and clarify which steps are OS-agnostic.
Service Fabric
RunToCompletion semantics and specifications
...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates notable Windows bias. All code examples use Windows containers (nanoserver:1809) and Windows-specific commands (cmd, echo, ping, set, exit). The 'Query deployment status' section only references PowerShell and C# APIs, with no mention of Linux or cross-platform CLI tools. There are no examples or guidance for Linux containers, Linux shell commands, or querying deployment status from Linux/macOS environments.
Recommendations
- Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine) and Linux shell commands (bash, echo, ping, exit).
- Provide guidance for querying deployment status using Azure CLI or REST APIs, which are cross-platform.
- Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, include relevant examples.
- Mention Linux/macOS compatibility and any limitations explicitly.
- If PowerShell is referenced, also mention Bash or other Linux-native tools where possible.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page is not strictly Windows-only, but it demonstrates Windows bias by repeatedly referencing 'custom windows images' and providing a PowerShell example for role assignment without a Linux CLI equivalent. Windows terminology and examples are presented first and more prominently, even though Service Fabric Managed Clusters can use Linux images. Linux-specific guidance is minimal and secondary.
Recommendations
- Clarify that custom images can be Windows or Linux, and provide equal coverage for both.
- Add Azure CLI examples for role assignment (e.g., az role assignment create) alongside PowerShell.
- Include explicit Linux image ARM template examples and reference Linux image documentation directly.
- Avoid using 'custom windows images' as the default term; use 'custom images' and specify OS where relevant.
- Ensure links to Linux image creation and marketplace browsing are as prominent as Windows equivalents.
Service Fabric
Configure or modify a Service Fabric managed cluster node type
...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides command-line examples exclusively using PowerShell cmdlets (e.g., New-AzServiceFabricManagedNodeType, Remove-AzServiceFabricManagedNodeType, Set-AzServiceFabricManagedNodeType), which are Windows-centric tools. There are no equivalent examples using Azure CLI, Bash, or cross-platform scripting tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer using Azure CLI. The documentation also refers to drive letters (e.g., S, C, D), which are a Windows disk convention, without clarifying Linux implications.
Recommendations
- Add Azure CLI examples for all operations currently shown with PowerShell (add, remove, scale, configure placement properties, etc.), as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly state if certain operations are only possible with PowerShell, and provide guidance or workarounds for Linux/macOS users (e.g., using Azure Cloud Shell, which supports PowerShell and Bash).
- Clarify the meaning of drive letters in the context of Linux-based node types, or note if this is only relevant for Windows-based nodes.
- Consider listing Azure CLI examples before or alongside PowerShell to promote parity.
Service Fabric
Monitor Azure Service Fabric
...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation generally covers both Windows and Linux Service Fabric clusters, but there are several areas where Windows tools and patterns are mentioned first or exclusively. Windows-specific tools (e.g., Event Log/Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some examples/tutorials focus on .NET/Windows. Linux-specific guidance is present but often secondary or less detailed. Some features (like EventStore APIs) are Windows-only, but this is clearly stated. Overall, Linux users can complete monitoring tasks, but may encounter friction due to Windows-centric examples and tool references.
Recommendations
- Ensure Linux monitoring tools and patterns are described with equal prominence and detail as Windows equivalents.
- Provide Linux-specific examples and tutorials (e.g., instrumenting applications, configuring diagnostics, querying logs) alongside Windows/.NET examples.
- When referencing Windows tools (e.g., Event Viewer, Diagnostics Agent), immediately mention Linux alternatives (e.g., Syslog, LTTng) and link to relevant Linux documentation.
- Clarify which features are Windows-only and offer Linux workarounds or alternatives where possible.
- Add sample code and walkthroughs for Linux clusters using popular languages and frameworks (e.g., Python, Java, Node.js) in addition to .NET.
Service Fabric
Describing Azure Service Fabric apps and services
...ic/service-fabric-application-and-service-manifests.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation contains a notable Windows bias in its guidance for authoring Service Fabric manifests. It explicitly recommends opening the Service Fabric XSD schema file in Visual Studio using a hardcoded Windows path (C:\Program Files\...), without mentioning Linux or cross-platform alternatives. Additionally, PowerShell is referenced as a way to create services, with no mention of Bash/CLI equivalents. However, the core manifest content and examples are platform-agnostic.
Recommendations
- Provide equivalent instructions for Linux/macOS users, such as how to access the XSD schema file on non-Windows installations and which editors (e.g., VS Code, JetBrains Rider) can provide XML schema validation.
- Mention cross-platform tools (e.g., Azure CLI, Bash scripts) for creating and managing services, not just PowerShell.
- When referencing file paths, include Linux/macOS paths or clarify if the feature is only available on Windows.
- Consider including a note about cross-platform development environments and how to work with Service Fabric manifests outside of Visual Studio on Windows.
Service Fabric
Learn about Azure Service Fabric application security
...ric/service-fabric-application-and-service-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides a general overview of Service Fabric application security, but there are several instances where Windows-specific features, tools, and examples are mentioned before or instead of Linux equivalents. For example, running services under Active Directory domain accounts and group managed service accounts (gMSA) are highlighted for Windows standalone clusters, while Linux alternatives are not discussed. Disk encryption references PowerShell and BitLocker (Windows tools), with Linux disk encryption marked as a 'TO DO'. Some examples and terminology (e.g., NetworkService) are Windows-centric, and Linux-specific guidance is limited or absent.
Recommendations
- Add Linux-specific examples and instructions where Windows features are discussed, such as running services under Linux user accounts or groups.
- Provide guidance for disk encryption on Linux clusters, including supported tools and procedures.
- Ensure parity in examples (e.g., manifest snippets) by including both Windows and Linux configurations.
- Mention Linux alternatives to Windows-specific tools (e.g., BitLocker, PowerShell) and clarify which features are cross-platform.
- Review terminology to ensure it is not unnecessarily Windows-centric (e.g., NetworkService) and provide Linux equivalents.
Service Fabric
Application upgrade: data serialization
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page focuses on data serialization during application upgrades in Azure Service Fabric. While the main content is platform-neutral, the 'Next steps' section lists Windows-centric tools (Visual Studio and PowerShell) for upgrade walkthroughs, with no mention of Linux/macOS equivalents or CLI options. PowerShell is highlighted as a primary upgrade method, which may create friction for Linux users.
Recommendations
- Add links or references to cross-platform upgrade methods, such as Azure CLI or Service Fabric CLI (sfctl), especially for Linux/macOS users.
- Include examples or tutorials for upgrading applications using CLI tools available on Linux/macOS.
- Clarify which upgrade methods are Windows-only and provide alternatives for other platforms.
- Ensure parity in documentation by listing Linux/macOS-compatible tools alongside Windows tools in the 'Next steps' section.
Service Fabric
Service Fabric application upgrade
...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page for Service Fabric application upgrade demonstrates a notable Windows bias. All code examples are provided exclusively in PowerShell, with no equivalent CLI or Linux/macOS instructions. Windows-specific tools (PowerShell, http.sys) are referenced without mention of cross-platform alternatives. The 'Next steps' section prioritizes Windows-centric workflows (Visual Studio, PowerShell) and omits Linux-native options, creating friction for non-Windows users.
Recommendations
- Add Azure CLI or Service Fabric CLI (sfctl) examples alongside PowerShell scripts for application upgrades.
- Explicitly mention cross-platform tools and workflows where possible, such as using sfctl for Linux/macOS.
- Clarify which features or steps are Windows-only, and provide Linux/macOS alternatives or workarounds where available.
- Include links or references to Linux/macOS documentation for Service Fabric application upgrades.
- Reorder or balance 'Next steps' to include Linux/macOS upgrade tutorials and tools.
Service Fabric
Restoring backup in Azure Service Fabric
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page for restoring backup in Azure Service Fabric is heavily biased toward Windows/PowerShell usage. All command-line examples use PowerShell, including REST API calls, and require installation of a Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, curl, or other cross-platform tools. The documentation assumes the reader is using Windows and PowerShell, creating friction for Linux/macOS users.
Recommendations
- Add equivalent examples using cross-platform tools such as curl or Azure CLI for REST API calls.
- Document how to authenticate and interact with Service Fabric clusters from Linux/macOS environments.
- Mention any prerequisites or limitations for Linux/macOS users explicitly, including alternative modules or tools if available.
- Where possible, provide sample scripts in Bash or generic HTTP request formats alongside PowerShell.
- Clarify if the Microsoft.ServiceFabric.Powershell.Http module is required only for Windows, and suggest alternatives for other platforms.
Service Fabric
Application lifecycle in Service Fabric
...service-fabric/service-fabric-application-lifecycle.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-specific tooling throughout critical lifecycle operations (deploy, upgrade, remove, cleanup). While REST API and .NET methods are also mentioned, there is a notable absence of Linux-oriented command-line examples (such as Azure CLI or sfctl) and no explicit guidance for Linux/macOS users. The PowerShell cmdlets are presented alongside .NET and REST, but Linux equivalents are not discussed, creating friction for non-Windows users.
Recommendations
- Add explicit examples and instructions using sfctl (Service Fabric CLI) and Azure CLI for all major lifecycle operations (deploy, upgrade, remove, cleanup).
- Clarify which tools are cross-platform and which are Windows-only, and provide guidance for Linux/macOS users.
- Where PowerShell is referenced, include parallel sfctl or Azure CLI commands, or link to relevant Linux/macOS documentation.
- Consider reordering examples so that cross-platform tools are presented before or alongside Windows-specific tools.
- Add a section or note summarizing tool parity and platform support for Service Fabric management.
Service Fabric
Advanced Application Upgrade Topics
...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page for 'Advanced Application Upgrade Topics' in Azure Service Fabric heavily features PowerShell cmdlets for all operational examples (e.g., creating, updating, upgrading, rolling back applications), with no mention of Linux/macOS equivalents or CLI commands. Windows/PowerShell tools are referenced exclusively, and Windows-centric patterns (such as Visual Studio integration) are mentioned first or solely. There is no guidance for Linux users on how to perform these tasks using cross-platform tools like Azure CLI or REST APIs.
Recommendations
- Add equivalent examples using Azure CLI (az servicefabric) or REST API for all PowerShell cmdlet operations.
- Explicitly mention cross-platform tooling and workflows for Linux/macOS users, including how to perform upgrades and configuration changes.
- Provide links to Linux/macOS-specific documentation or note any limitations for non-Windows environments.
- Clarify which features or steps are Windows-only, and which are available cross-platform, to reduce confusion.
- Include sample scripts or commands for Linux shells (bash/zsh) where appropriate.
Service Fabric
Application upgrade: upgrade parameters
...abric/service-fabric-application-upgrade-parameters.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page presents PowerShell and Visual Studio (Windows tools) parameters and workflows before those for the cross-platform Service Fabric CLI (sfctl). Most parameter tables and examples are focused on PowerShell and Visual Studio, with Linux/macOS (sfctl) details grouped later. There are no explicit Linux/macOS command-line examples in the main body, and PowerShell/Windows-centric tools are described in more detail and with more context. This ordering and emphasis may create friction for Linux/macOS users.
Recommendations
- Reorganize the documentation to present cross-platform (sfctl/REST) options before or alongside Windows-specific tools (PowerShell, Visual Studio).
- Add explicit Linux/macOS command-line examples using sfctl in the main parameter sections, not just in a separate section.
- Clarify in the introduction that sfctl is the recommended cross-platform tool for Linux/macOS users.
- Balance the depth of explanation and examples between PowerShell/Visual Studio and sfctl/REST.
- Where possible, provide parameter tables that show mappings for all tools (PowerShell, Visual Studio, sfctl, REST) side-by-side.
Service Fabric
On-demand backup in Azure Service Fabric
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page for on-demand backup in Azure Service Fabric exclusively uses PowerShell for all CLI examples and module instructions, with no mention of Linux/macOS-compatible tools or commands. All REST API examples are shown using PowerShell, and the prerequisite is to install a PowerShell module. There are no Bash, curl, or cross-platform CLI examples, nor is there guidance for Linux/macOS users on how to perform equivalent actions.
Recommendations
- Add Bash/curl examples for REST API calls, demonstrating how Linux/macOS users can trigger backups and track progress.
- Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST API calls can be made directly from any platform.
- Provide instructions for connecting to Service Fabric clusters from Linux/macOS, including authentication and certificate handling.
- Mention cross-platform tools (such as Azure CLI or Service Fabric CLI) if available, and provide equivalent examples.
- Explicitly state platform requirements for PowerShell-based steps, and offer alternatives where possible.
Service Fabric
Capacity planning and scaling for Azure Service Fabric
...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides several manual scaling instructions using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning or providing equivalent CLI commands for Linux/macOS users. There are no Bash, Azure CLI, or cross-platform alternatives shown for these critical operations, which may create friction for non-Windows users.
Recommendations
- For every PowerShell example, provide equivalent Azure CLI or REST API commands that can be run on Linux/macOS.
- Explicitly mention cross-platform tools and workflows where possible, or link to documentation for Linux/macOS users.
- Clarify whether the PowerShell commands are required (i.e., if no cross-platform alternative exists), and if so, provide guidance for Linux users (e.g., using Azure Cloud Shell, which supports PowerShell).
- Add Bash or Azure CLI examples for common operations like disabling nodes, scaling in/out, and cleaning up node state.
Service Fabric
Azure Service Fabric infrastructure as Code Best Practices
...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and is the only scripting language shown for cluster upgrades. Windows-specific registry and VM configuration details are included without Linux equivalents. The upgrade process shows only PowerShell commands, with no Linux shell or cross-platform alternatives. Some configuration snippets and guidance are Windows-focused, and Linux parity is not always maintained.
Recommendations
- Provide equivalent Bash or Linux shell commands for all PowerShell examples, especially for cluster upgrades.
- Include Linux-specific guidance for disabling automatic updates and managing upgrades, or clarify if not required on Linux.
- When mentioning Windows registry or VM configuration, add a note or section for Linux users, or explicitly state if the step is Windows-only.
- Present cross-platform tools (like Azure CLI) first, or in parallel with PowerShell, to avoid a Windows-first impression.
- Ensure all critical workflows (deployment, upgrade, configuration) have Linux examples or clear statements about platform differences.
Service Fabric
Node types and virtual machine scale sets
...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides some Windows-centric examples and references, such as using Windows-style file paths (e.g., 'D:\\SvcFab') in the Service Fabric extension snippet and referencing RDP and PowerShell scripts in the 'Next steps' section. There is no explicit Linux example for the dataPath or for connecting to Linux nodes, and Linux tools or SSH are not mentioned, which may cause friction for Linux users.
Recommendations
- Provide Linux-specific examples, such as using a Linux-style dataPath (e.g., '/var/lib/servicefabric') in the extension snippet.
- Include guidance or links for connecting to Linux nodes (e.g., SSH instructions) alongside RDP/PowerShell references.
- Add parity in the 'Next steps' section by including Linux/SSH-related scripts or documentation for common management tasks.
- Clarify when instructions or examples are Windows-specific, and offer Linux alternatives where possible.
Service Fabric
Understanding periodic backup configuration
...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is generally platform-neutral, focusing on Azure Service Fabric backup configuration. However, the 'File share' backup storage section exclusively describes Windows-style file shares (UNC paths, Integrated Windows Authentication), with no mention of Linux-compatible alternatives (e.g., SMB/CIFS mounts on Linux, NFS, or Azure Files usage from Linux). Additionally, Windows authentication patterns are described first and in detail, while Linux scenarios are not addressed.
Recommendations
- Add guidance for configuring file share backup storage from Linux nodes, including supported protocols (e.g., SMB/CIFS, NFS, Azure Files) and authentication methods.
- Clarify whether Linux Service Fabric clusters can use file share backup storage, and if so, provide Linux-specific examples (e.g., mounting Azure Files via SMB from Linux, using Linux credentials).
- If file share backup is Windows-only, explicitly state this limitation to avoid confusion for Linux users.
- Consider including parity examples for Azure Blob storage usage from Linux clusters, if there are any platform-specific considerations.
Service Fabric
Azure Service Fabric networking best practices
...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides both Windows and Linux guidance for Service Fabric networking, but there are several areas where Windows tools (e.g., PowerShell, Windows-specific port ranges, Windows container guidance) are mentioned first or exclusively. PowerShell is referenced as the primary client API example, and some sample ARM templates and links are Windows-centric. Linux equivalents are sometimes mentioned, but not always with equal detail or prominence.
Recommendations
- Provide Linux CLI examples alongside PowerShell, especially for client API access and cluster management.
- Include Linux-focused ARM template samples and links, not just Windows ones.
- Clarify when port ranges or networking rules are Windows-only and provide Linux-specific guidance where applicable.
- Ensure reverse proxy and container networking guidance is equally detailed for Linux workloads.
- Where Windows tools are mentioned (e.g., netsh), offer Linux equivalents (e.g., ss, iptables, etc.).
- Balance the order of presentation so Linux and Windows are treated equally (e.g., do not always mention Windows first).
Service Fabric
Azure Service Fabric security best practices
...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance for key security tasks, but Windows-specific tools (PowerShell, Windows Defender, DSC) are often mentioned first or exclusively. Windows examples (especially PowerShell commands) precede Linux equivalents in some sections, and Windows Defender configuration is covered in detail while Linux antimalware is only referenced generically. Some sections (e.g., Windows security baselines, Windows Defender) are Windows-only, but this is appropriate given their nature.
Recommendations
- Where possible, present Windows and Linux examples side-by-side or alternate which comes first.
- Expand Linux-specific guidance for antimalware and baseline configuration, referencing common Linux tools (e.g., ClamAV, auditd, CIS benchmarks) and how to apply them to Service Fabric clusters.
- Clarify when sections are Windows-only and provide links or notes for Linux alternatives if available.
- Ensure parity in detail and clarity for Linux commands and workflows, matching the depth of Windows instructions.
- Add explicit notes when a feature or tool is Windows-only, to avoid confusion for Linux users.
Service Fabric
Service Fabric Cluster Resource Manager - Placement Policies
...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides code examples in C# and PowerShell for configuring Service Fabric placement policies. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash scripts) are provided. PowerShell examples are consistently shown alongside C# code, with no mention of cross-platform alternatives or Linux-native tooling. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer platform-agnostic approaches.
Recommendations
- Add Azure CLI examples for each placement policy, as Azure CLI is cross-platform and widely used.
- Mention whether PowerShell examples are supported on Linux/macOS (via PowerShell Core), and clarify any limitations.
- Provide Bash or shell script equivalents where possible, or reference relevant REST API calls.
- Explicitly state if certain configuration steps require Windows, or if they can be performed from any OS.
- Consider reordering examples so that platform-neutral options (e.g., Azure CLI, REST API) are presented before PowerShell.
Service Fabric
Describe a cluster by using Cluster Resource Manager
...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows-specific (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json) configuration examples. However, Windows/PowerShell examples are consistently presented first and are more detailed, with Windows terminology (e.g., <WindowsServer> element) appearing before Linux equivalents. PowerShell is the only CLI example shown, with no Linux shell or CLI parity. There is no explicit mention of Linux-specific node configuration or Linux command-line usage, though Service Fabric does support Linux clusters.
Recommendations
- Provide Linux-specific configuration examples, such as referencing <Linux> infrastructure elements in ClusterManifest.xml.
- Add Linux CLI examples (e.g., Bash, Azure CLI) alongside PowerShell for service creation and updates.
- Clarify that both Windows and Linux clusters are supported and highlight any differences in configuration or terminology.
- Ensure that JSON-based configuration examples are clearly marked as cross-platform.
- Consider alternating the order of Windows and Linux examples, or grouping them together for parity.
Service Fabric
Cluster Resource Manager - Management Integration
...fabric-cluster-resource-manager-management-integration.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell example for querying Service Fabric partition health, using Windows-style paths and commands (e.g., 'PS C:\Users\User > Get-ServiceFabricPartitionHealth'). There are no equivalent Linux/macOS CLI examples or references to cross-platform tools. The PowerShell example is presented as the only way to interact with the cluster, which may create friction for Linux/macOS users.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
- Mention that PowerShell is one option, but that sfctl or REST APIs can be used from any OS.
- Provide Linux/macOS command-line examples alongside Windows/PowerShell examples.
- Clarify any OS-specific limitations if certain commands/tools are Windows-only.
Service Fabric
Azure Service Fabric dynamic node tags
...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page for Azure Service Fabric dynamic node tags provides command-line examples exclusively using PowerShell, which is a Windows-centric tool. There are no Linux shell (bash/CLI) examples or references to Linux-native tools for managing node tags, despite Service Fabric supporting Linux nodes and clusters. The documentation also does not mention cross-platform alternatives or clarify whether the PowerShell commands are available on Linux (via PowerShell Core), nor does it provide REST API or CLI examples for Linux/macOS users.
Recommendations
- Add equivalent bash/CLI examples for managing node tags on Linux clusters.
- Include Azure CLI or REST API examples for cross-platform usage.
- Clarify whether PowerShell commands are supported on Linux (via PowerShell Core), and if so, provide guidance.
- Mention any limitations or differences for Linux users, if applicable.
- Ensure examples are balanced and not Windows-first unless the feature is Windows-only.
Service Fabric
Azure Service Fabric standalone cluster scaling
...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters shows notable Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without mentioning Linux equivalents or cross-platform tools. The linked 'scale a standalone cluster' guide is Windows Server-specific, and there are no examples or guidance for Linux-based standalone clusters, even though Service Fabric can be deployed on Linux. This creates friction for Linux users seeking parity.
Recommendations
- Add examples and instructions for scaling standalone clusters deployed on Linux, including relevant CLI commands or scripts.
- Mention cross-platform tools (such as sfctl or REST APIs) alongside PowerShell cmdlets.
- Clarify which steps are Windows-specific and provide Linux alternatives where possible.
- Update links and references to include Linux documentation if available.
Service Fabric
Secure an Azure Service Fabric cluster
...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page primarily discusses security scenarios for Azure Service Fabric clusters, but consistently presents Windows-specific guidance and links before Linux equivalents. Standalone cluster security is only described for Windows Server, with no mention of Linux standalone clusters or their security setup. Certificate creation recommendations and tooling are Windows-centric, and there are no Linux-specific examples or instructions for standalone clusters.
Recommendations
- Add explicit guidance and links for securing standalone Service Fabric clusters running on Linux, including certificate and authentication setup.
- Provide Linux-specific examples and instructions alongside Windows examples, especially for certificate management, cluster configuration, and client authentication.
- Clarify which security scenarios and features are supported on Linux clusters, and note any differences or limitations.
- Mention Linux-compatible certificate creation tools (e.g., OpenSSL) and provide sample commands.
- Ensure parity in recommendations and best practices for both Windows and Linux environments.
Service Fabric
Manage Azure Service Fabric app load using metrics
...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides code examples for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API) are provided. Additionally, PowerShell examples are presented before any mention of cross-platform alternatives, and there is no guidance for Linux users on how to perform these tasks. This creates friction for Linux/macOS users deploying or managing Service Fabric clusters.
Recommendations
- Add Azure CLI examples for service creation and metric management, which are cross-platform.
- Include REST API sample calls for metric configuration and load reporting.
- Explicitly mention cross-platform tools and workflows, and clarify which features are available on Linux Service Fabric clusters.
- If PowerShell is required for certain tasks, note any Linux alternatives or limitations.
- Consider providing Bash scripts or instructions for Linux environments where applicable.
Service Fabric
Service Fabric Cluster Resource Manager: Movement cost
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides PowerShell and C# examples for configuring Service Fabric MoveCost, but does not include equivalent Linux/CLI (e.g., Azure CLI, Bash) examples. PowerShell is Windows-centric, and the absence of Linux-native command-line examples may hinder Linux/macOS users.
Recommendations
- Add Azure CLI or Bash examples for creating and updating Service Fabric services with MoveCost, if supported.
- Clarify if PowerShell commands are cross-platform (e.g., Azure PowerShell Core) or Windows-only.
- Mention any Linux/macOS limitations or provide guidance for users on those platforms.
- Consider including REST API examples, which are platform-agnostic.
Service Fabric
Service sensitivity
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not mention or provide equivalent Linux/macOS CLI examples (such as Azure CLI or REST API). PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users. The C# API is also shown, but this is platform-neutral. No explicit Windows-only features are discussed, so Linux parity is expected.
Recommendations
- Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, if supported.
- Clarify whether PowerShell commands can be run cross-platform (e.g., via PowerShell Core), or if they are Windows-only.
- Mention any Linux/macOS tools or workflows for Service Fabric administration, or link to relevant guides.
- If PowerShell is the only supported scripting interface, explicitly state this limitation.
Service Fabric
Azure Service Fabric application resource model
...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation page demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI or Bash equivalents. Application packaging is described via Visual Studio, a Windows-centric tool, and directory paths use Windows-style notation. There are no Linux/macOS-specific instructions or examples, and Windows tools are referenced before any cross-platform alternatives.
Recommendations
- Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
- Include instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, zip utilities) instead of only Visual Studio.
- Use platform-neutral directory paths or provide both Windows and Linux/macOS path examples.
- Mention that PowerShell examples are for Windows and provide Bash/Azure CLI alternatives for Linux/macOS users.
- Clarify that Visual Studio is optional and suggest cross-platform editors or build tools.
Service Fabric
Learn more about Azure Service Fabric
...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there are several instances where Windows concepts, tools, and examples are presented first or exclusively. Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned before their Linux equivalents, and some sections (such as standalone clusters) only reference Windows, with Linux support noted as unavailable. There is frequent mention of Windows executables and services (e.g., FabricHost.exe), and PowerShell is often highlighted as a management tool, with less emphasis on Linux CLI or scripting alternatives. Linux examples and tools are sometimes missing or relegated to secondary status.
Recommendations
- Ensure that Linux equivalents (e.g., CLI commands, Bash scripts) are presented alongside PowerShell examples, not just referenced.
- When describing cluster management, highlight Linux tools and workflows equally, and provide links to Linux-specific documentation.
- In sections where Windows executables are discussed, clarify the Linux equivalents or note differences more prominently.
- For standalone clusters, provide a roadmap or guidance for Linux users, even if full support is not yet available.
- Avoid presenting Windows tools (e.g., Visual Studio, PowerShell) before Linux alternatives unless the feature is Windows-only.
- Add explicit Linux examples and screenshots where possible, especially in 'Next steps' and quick start guides.
Service Fabric
Upgrading Azure Service Fabric clusters
...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page provides general guidance on upgrading Azure Service Fabric clusters, which are not inherently Windows-only. However, in the 'Upgrading OS images for cluster nodes' section, the only linked guidance is for patching Windows operating systems, with no mention or link to Linux equivalents. Additionally, throughout the page, PowerShell is mentioned as a tool for managing certificates and ports, but Azure CLI is also referenced, mitigating some bias. Windows-specific patching tools (Patch Orchestration Application) are discussed without Linux alternatives.
Recommendations
- Add explicit guidance and links for upgrading Linux-based Service Fabric cluster node OS images, if supported.
- When mentioning PowerShell, always pair with Azure CLI or Bash examples, or clarify cross-platform support.
- If Patch Orchestration Application (POA) is Windows-only, clarify this and provide Linux alternatives or state limitations.
- Ensure that all management actions (certificates, ports, node properties) include Linux-compatible tooling and examples.
Service Fabric
Azure Service Fabric Events
...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page for Azure Service Fabric Events shows a notable Windows bias. It references Windows Event logs, ETW, and the Windows Azure diagnostics agent as primary mechanisms for accessing Service Fabric events, without mentioning Linux equivalents or providing Linux-specific guidance. Windows tools and patterns are discussed first and exclusively, and there are no examples or instructions for accessing events on Linux-based Service Fabric clusters.
Recommendations
- Add information about how Service Fabric events are accessed and logged on Linux clusters, including any differences in event channels, logging mechanisms, or monitoring tools.
- Include Linux-specific examples or references (such as using syslog, journald, or other Linux logging agents) for event collection and integration with Azure Monitor.
- Clarify which features or instructions are Windows-only, and provide parallel guidance for Linux where possible.
- If certain event access methods are not available on Linux, explicitly state this and suggest alternative approaches.
Service Fabric
Health monitoring in Service Fabric
...s/service-fabric/service-fabric-health-introduction.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without mentioning or demonstrating equivalent Linux/macOS methods (such as REST API, CLI, or SDK usage). The PowerShell cmdlet is presented as the primary approach, and no Linux-native tooling or cross-platform instructions are given. This creates friction for Linux/macOS users, who may not have access to PowerShell or Windows-specific cmdlets.
Recommendations
- Add equivalent examples using REST API, Service Fabric CLI (sfctl), or SDK methods for health reporting and querying, suitable for Linux/macOS environments.
- Explicitly mention cross-platform options (REST, sfctl, SDKs) alongside PowerShell, and clarify which tools are available on which platforms.
- Consider presenting cross-platform examples first, or at least in parallel with Windows/PowerShell examples.
- Link to documentation for Linux/macOS-compatible tools and APIs for Service Fabric health reporting and querying.
Service Fabric
Azure Service Fabric image store connection string
...fabric/service-fabric-image-store-connection-string.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and links to PowerShell-based deployment instructions as the next step. While .NET and REST are mentioned as alternatives, PowerShell is presented first and most prominently. There are no explicit Linux/bash examples or references to Linux-native tools for these tasks.
Recommendations
- Add examples or links for performing cluster manifest retrieval and application deployment using Linux/macOS tools (e.g., Azure CLI, bash, or REST via curl).
- Ensure parity in documentation by providing step-by-step instructions for Linux users alongside PowerShell instructions.
- Clarify which tools are cross-platform and which are Windows-specific, especially for deployment workflows.
- Consider linking to Linux/macOS-specific guides or including a section for non-Windows environments.
Service Fabric
Azure Service Fabric hosting activation and deactivation life cycle
...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page on Azure Service Fabric hosting activation and deactivation life cycle is largely platform-neutral in its conceptual explanations. However, the 'Next steps' section directs users to deploy and remove applications specifically 'in PowerShell', and the only linked example for downloading a ServicePackage in advance references a PowerShell module. There are no equivalent Linux/bash examples or references to cross-platform tools, which may create friction for Linux/macOS users.
Recommendations
- Add Linux/bash CLI examples alongside PowerShell examples for deployment and management tasks.
- Update 'Next steps' to include links to cross-platform deployment instructions (e.g., Azure CLI, REST API, or Service Fabric CLI).
- Where PowerShell modules are referenced, note if there are equivalent commands for Linux/macOS or clarify if the operation is Windows-only.
- Ensure that conceptual sections remain platform-neutral, and provide parity in operational guidance.
Service Fabric
Manage apps for multiple environments
...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for managing application parameters in Azure Service Fabric, with a notable emphasis on PowerShell and Visual Studio workflows. PowerShell is mentioned first for application creation, and Visual Studio parameter files are discussed in detail. Linux-oriented tools (sfctl, install.sh) are referenced but receive less prominence and explanation.
Recommendations
- Present Linux-native tools (sfctl, install.sh) before or alongside PowerShell examples to ensure equal visibility.
- Expand explanations and examples for sfctl and install.sh usage, including sample commands and workflows for Linux/macOS users.
- Clarify which tools are cross-platform and which are Windows-only, to help users choose appropriate options.
- Add explicit Linux/macOS parameter file handling guidance, especially for users not using Visual Studio.
Service Fabric
Azure Service Fabric container application manifest examples
...abric/service-fabric-manifest-example-container-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page provides container application manifest examples for Azure Service Fabric, but it exhibits a Windows bias. The examples are based on the 'Windows Server 2016 Container Sample', and Windows-specific tools (e.g., 'winver' command) and paths (e.g., 'c:\VolumeTest\Data') are referenced. Linux equivalents are not mentioned, and there are no explicit Linux-focused examples or guidance. While some notes acknowledge Linux (e.g., certificate handling), the overall presentation and examples are Windows-centric.
Recommendations
- Add Linux-based manifest examples or clarify which elements differ for Linux clusters.
- Include Linux-specific instructions for obtaining OS build/version (e.g., 'cat /etc/os-release' or 'uname -r') instead of only referencing 'winver'.
- Provide sample container volume paths using Linux conventions (e.g., '/mnt/VolumeTest/Data') alongside Windows paths.
- Explicitly state which features and settings are cross-platform and which are Windows-only.
- Reference or link to Linux container samples if available.
Service Fabric
Reliable services app manifest examples
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page provides Service Fabric manifest examples and references Windows-specific concepts and tools, such as running scripts via .bat files and mentioning the ServiceFabric PowerShell module for service creation. The examples and explanations assume Windows conventions (e.g., .exe, .bat, NETWORKSERVICE account), and do not provide Linux equivalents or guidance for Linux clusters. Windows terminology and tools are mentioned first or exclusively, creating friction for Linux users.
Recommendations
- Add Linux-specific examples, such as using shell scripts (.sh) instead of .bat files for SetupEntryPoint and EntryPoint.
- Mention and provide guidance for Linux Service Fabric clusters, including differences in user accounts, file permissions, and service management.
- Include instructions for creating services using Linux CLI tools (e.g., sfctl) alongside or instead of PowerShell.
- Clarify which manifest features and settings are cross-platform and which are Windows-only, and link to Linux-specific documentation where relevant.
- Ensure terminology is inclusive (e.g., 'NETWORKSERVICE' vs. Linux equivalents) and explain any platform-specific concepts.
Service Fabric
Networking patterns for Azure Service Fabric
...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides only PowerShell-based deployment examples and references Windows-centric tools and patterns (e.g., RDP, Windows directory paths, PowerShell commands). There are no equivalent Bash/CLI examples or explicit guidance for Linux/macOS users, and Windows tools (like RDP) are mentioned before alternatives. This creates friction for non-Windows users, though the underlying Azure features are cross-platform.
Recommendations
- Add Azure CLI (az) and Bash shell examples alongside PowerShell for all deployment steps.
- Mention SSH as a remote access method for Linux VMs instead of only referencing RDP.
- Use platform-neutral directory paths and command prompts (e.g., ~/ instead of C:\).
- Explicitly note that templates and networking features are usable from any OS, and link to Linux/macOS-specific guidance where relevant.
- Provide sample commands for Linux/macOS users to deploy ARM templates and manage networking resources.
Service Fabric
Service communication with the ASP.NET Core
...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric. However, there is a notable Windows bias in several areas: HTTP.sys (Windows-only) is described in detail and appears before Kestrel in the structure; Windows-specific tools and APIs (such as netsh and Windows HTTP Server API) are referenced without Linux equivalents; endpoint configuration examples and explanations are often tied to Windows concepts. While Kestrel is recommended for Linux and cross-platform scenarios, Windows-specific patterns and terminology are presented first and more extensively.
Recommendations
- Reorder sections so that cross-platform Kestrel guidance appears before Windows-only HTTP.sys.
- Explicitly call out Linux/macOS support and limitations at the start of relevant sections.
- Provide Linux/macOS-specific troubleshooting tips or configuration advice where appropriate.
- Clarify that HTTP.sys and related endpoint configuration steps are Windows-only, and offer alternative guidance for Linux users.
- Add links or references to Linux/macOS development environment setup and debugging tools (e.g., VS Code, CLI).
Service Fabric
Replica soft delete for enhanced data protection in Service Fabric
...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page for Replica soft delete in Service Fabric heavily references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and API links exclusively for PowerShell usage. There is no mention of Linux/macOS equivalents, CLI usage, or cross-platform SDK approaches. This creates friction for Linux/macOS users, as Service Fabric supports Linux clusters and the APIs can be accessed via .NET SDK or REST, but only Windows/PowerShell tooling is documented.
Recommendations
- Add examples for using the relevant APIs (Remove, Restore, Get Replica) via the Service Fabric .NET SDK, REST API, or CLI, which are cross-platform.
- Explicitly mention how Linux/macOS users can perform replica soft delete and recovery operations, including any limitations or differences.
- Provide sample commands or code snippets for Linux environments, such as using sfctl (Service Fabric CLI) or direct SDK calls.
- Clarify whether the PowerShell APIs are available only on Windows, and if so, what alternatives exist for Linux clusters.
Service Fabric
Add custom Service Fabric health reports
...rticles/service-fabric/service-fabric-report-health.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides extensive PowerShell examples for health reporting in Service Fabric, with no equivalent Linux/macOS CLI or scripting examples. Windows/PowerShell tools are mentioned first and exclusively in example sections, while REST and API options are described but not demonstrated with Linux-friendly tools. This creates friction for Linux/macOS users, who must infer or research their own methods for interacting with Service Fabric health reporting.
Recommendations
- Add equivalent examples using Azure CLI, Bash, or curl for REST operations, demonstrating health report submission from Linux/macOS environments.
- Clarify which PowerShell commands are cross-platform (if any) and provide guidance for Linux users if PowerShell Core is supported.
- Explicitly mention Linux/macOS support for Service Fabric health reporting and link to relevant tools or documentation.
- Reorder sections to present REST and API methods before or alongside PowerShell, emphasizing platform-neutral approaches.
Service Fabric
Configure the upgrade of a Service Fabric application
...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on Windows tooling, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and workflows reference Windows tools, with no mention of Linux/macOS alternatives or cross-platform CLI options. Linux users are not provided with equivalent instructions or examples, creating friction for non-Windows environments.
Recommendations
- Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
- Mention and link to any available Linux/macOS tooling for Service Fabric application management.
- Provide parity in examples, such as showing how to configure upgrade parameters and health policies using non-Windows tools.
- Clarify which steps are Windows-only and offer alternatives for Linux/macOS users where possible.
Service Fabric
Define Service Configuration in StartupServices.xml for a Service Fabric Application
...service-fabric/service-fabric-startupservices-model.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is strongly oriented toward Windows development workflows, specifically Visual Studio, with repeated references to Windows-centric tools and patterns (e.g., F5/Ctrl+F5/Publish, Visual Studio UI, PowerShell module). There are no examples or guidance for Linux/macOS users, nor any mention of cross-platform alternatives for developing or deploying Service Fabric applications. The page assumes the use of Visual Studio and Windows, omitting CLI or non-Windows tooling.
Recommendations
- Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
- Provide examples using Azure CLI, Service Fabric CLI (sfctl), or other cross-platform tools for creating and deploying Service Fabric applications.
- Clarify which features are Visual Studio/Windows-only and suggest alternative workflows for non-Windows environments.
- Include sample workflows for editing and deploying ApplicationManifest.xml and StartupServices.xml using command-line tools or editors available on Linux/macOS.
Service Fabric
Fault Analysis Service overview
.../service-fabric/service-fabric-testability-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides explicit instructions for using the Fault Analysis Service with PowerShell and C#, but does not mention or provide examples for Linux/macOS users (e.g., Bash/CLI, REST API, or cross-platform SDK usage). The PowerShell instructions assume a Windows environment, and there is no guidance for equivalent operations on Linux or macOS.
Recommendations
- Add examples or instructions for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash scripts, or REST API.
- Clarify whether the PowerShell module or SDK is available and supported on non-Windows platforms, or provide alternatives if not.
- Include cross-platform C#/.NET Core examples if applicable, and note any platform-specific limitations.
- Explicitly state if certain features are Windows-only, to set expectations for Linux/macOS users.
Virtual Machine Scale Sets
Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview)
...virtual-machine-scale-sets/auto-zone-balance-enable.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for enabling Automatic Zone Balance on Virtual Machine Scale Sets. However, PowerShell examples are consistently presented alongside or immediately after CLI examples, and Windows-specific PowerShell tooling is referenced throughout. The Application Health extension example in PowerShell uses 'ApplicationHealthWindows', while the CLI uses 'ApplicationHealthLinux', but there is no explicit guidance for Linux users in PowerShell. Portal instructions are platform-neutral, but the PowerShell sections are inherently Windows-centric, and PowerShell is presented as a primary automation option, which may create friction for Linux/macOS users.
Recommendations
- Clarify that Azure PowerShell is cross-platform and can be used on Linux/macOS, or provide Bash scripting examples where appropriate.
- Ensure that Application Health extension examples in PowerShell include both Windows and Linux variants, or explain how to use 'ApplicationHealthLinux' in PowerShell.
- Consider presenting CLI (Bash) examples before PowerShell, or explicitly state that CLI is recommended for Linux/macOS users.
- Add a note about PowerShell Core support on non-Windows platforms if PowerShell is required.
- Where possible, provide Bash shell scripting examples for automation tasks.
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for associating VMs to capacity reservation groups, but there is a notable Windows bias in several areas. PowerShell (a Windows-centric tool) is given equal prominence to the cross-platform Azure CLI, and in some cases, the ARM template and parameter defaults focus exclusively on Windows images. The ARM template example only covers Windows Server SKUs, and there are no explicit Linux ARM template examples. Additionally, some sections (like the ARM template) do not mention how to use a Linux image, and PowerShell is always presented as the only scripting alternative to CLI, with no mention of Bash or other Linux-native scripting approaches.
Recommendations
- Add ARM template examples for Linux VMs, or at least document how to modify the template to deploy a Linux image (e.g., Ubuntu).
- When showing parameter lists (such as OSVersion), include popular Linux distributions as allowed values, or provide a parallel Linux example.
- Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Where PowerShell is shown, mention that it is available cross-platform, but also suggest Bash or other Linux-native scripting approaches if relevant.
- Review the documentation for any assumptions that the user is on Windows (e.g., references to password complexity for Windows, or RDP ports), and clarify when steps are OS-agnostic or OS-specific.
Virtual Machines
Deploy a ZRS managed disk
...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI (Linux/macOS-friendly) and Azure PowerShell (Windows-centric) examples for deploying ZRS managed disks. However, PowerShell examples are extensive, and some Resource Manager Template instructions rely on PowerShell commands for feature registration and deployment, with no Bash or cross-platform alternatives. Windows/PowerShell tools are mentioned first or exclusively in some sections, and the PowerShell examples use Windows VM images, while CLI examples use Ubuntu. The Azure portal instructions are platform-neutral.
Recommendations
- Add Bash or cross-platform alternatives for feature registration and ARM template deployment, especially for Linux/macOS users.
- Ensure that Resource Manager Template instructions include az CLI equivalents for feature registration and deployment.
- Balance the order of examples so that CLI (Linux/macOS) and PowerShell (Windows) are presented equally, or clarify platform applicability.
- Where possible, provide both Windows and Linux VM image examples in PowerShell sections, or clarify that PowerShell can be used for Linux VM deployments as well.
Virtual Machines
Deploy a Premium SSD v2 managed disk
...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all programmatic steps, and also covers the Azure portal. However, in all CLI/PowerShell examples, the default VM image used is 'Win2016Datacenter', a Windows Server image. There are no explicit Linux VM image examples, and the variable names and instructions do not mention Linux. This creates a subtle Windows-first bias, as Linux users must know to substitute an appropriate Linux image. The use of PowerShell is not inherently biased, as Azure PowerShell is cross-platform, but the examples and context lean toward Windows usage patterns.
Recommendations
- In CLI and PowerShell examples, provide both Windows and Linux VM image examples (e.g., show 'UbuntuLTS' as an alternative to 'Win2016Datacenter').
- Explicitly mention that the VM image variable can be set to a Linux image and provide a sample value.
- Add a note or section clarifying how Linux users should adapt the examples, especially regarding authentication (e.g., SSH keys for Linux VMs instead of passwords).
- Where possible, show Linux-friendly authentication options (e.g., --authentication-type ssh for az vm create).
- Ensure that the documentation does not imply that only Windows VMs are supported or recommended.
Virtual Machines
Share an Azure Managed Disk across VMs
...cs/blob/main/articles/virtual-machines/disks-shared.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation covers both Windows and Linux usage of Azure shared disks, but Windows examples and tools (WSFC, CSV, Windows clustering, Windows-specific templates) are presented first and in greater detail. Windows clustering patterns (WSFC, CSV) are described before Linux equivalents (Pacemaker, Corosync), and Windows sample workloads are more numerous and detailed. Linux examples are present but less extensive, and Linux-specific tools/utilities are mentioned later and with less explanation.
Recommendations
- Present Linux and Windows examples in parallel, or alternate which platform is shown first in each section.
- Expand Linux sample workloads to match the detail and breadth of Windows examples (e.g., provide more Linux application templates or walkthroughs).
- Add more explicit Linux command-line examples for disk reservation and clustering (e.g., sg_persist, fence_scsi usage).
- Include links to Linux-specific documentation and templates as prominently as Windows equivalents.
- Clarify parity between Windows and Linux features and limitations, especially for clustering and disk sharing scenarios.
Virtual Machines
Enable shared disks for Azure Managed Disks
.../main/articles/virtual-machines/disks-shared-enable.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all disk types and operations, but PowerShell (a Windows-centric tool) is given equal prominence and sometimes appears before CLI examples. There are no Linux-specific shell or tooling examples (e.g., Bash, cloud-init), and the 'Using Azure shared disks with your VMs' section only shows PowerShell for attaching disks, omitting Linux VM attachment methods. The documentation is not Windows-only, but the example tooling leans toward Windows/PowerShell, creating friction for Linux/macOS users.
Recommendations
- Add Bash or Linux-specific examples for attaching shared disks to VMs, such as using Azure CLI or cloud-init.
- Ensure Azure CLI examples are shown first or equally with PowerShell, as CLI is cross-platform.
- Include guidance or links for Linux VM disk attachment and SCSI PR command usage, referencing relevant Linux tools (e.g., sg_persist, udev).
- Clarify that PowerShell examples are for Windows users, and provide alternative steps for Linux users where applicable.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides extensive Azure PowerShell examples and scripts, with detailed step-by-step instructions for enabling Write Accelerator. Azure CLI coverage is present but less detailed, and REST API instructions rely on Chocolatey and Windows-centric installation methods (cmd.exe, PowerShell), with no mention of Linux alternatives. Windows tools and patterns (e.g., Chocolatey, PowerShell) are referenced before Linux equivalents, and Linux-specific guidance is minimal or missing in scripting sections.
Recommendations
- Provide equivalent Azure CLI scripts and examples for all PowerShell scenarios, including step-by-step instructions for adding/enabling Write Accelerator disks.
- Include Linux-friendly installation instructions for armclient (e.g., via pip, npm, or manual download), and clarify how to use it on Linux/macOS.
- Ensure REST API usage examples include Linux shell commands (e.g., curl, wget) and instructions for updating VM configurations.
- Where disk/volume managers are referenced, ensure parity in guidance for Linux tools (e.g., LVM, MDADM) alongside Windows tools.
- Consider presenting Azure CLI examples before PowerShell, or side-by-side, to avoid Windows-first bias.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux, repeatedly references and prioritizes Windows-centric tools and workflows (notably Hyper-V and PowerShell's Convert-VHD) for VHD creation and conversion. Linux-native alternatives (such as qemu-img or VBoxManage) are not mentioned, and the only detailed VHD creation path is via Hyper-V, which is Windows-only. This may create friction for Linux/macOS users who do not have access to Hyper-V or PowerShell.
Recommendations
- Add instructions for creating and converting VHD files using Linux-native tools such as qemu-img or VBoxManage.
- Provide example workflows for preparing and converting VHDs entirely on Linux (and/or macOS) systems, including extraction, conversion, and validation steps.
- Mention Linux virtualization solutions (e.g., KVM, VirtualBox) alongside Hyper-V, and provide links to relevant documentation.
- Reorder or parallelize instructions so that Linux-native tools are presented before or alongside Windows tools, not only after.
- Clarify which steps are OS-agnostic and which are Windows-specific, to help users on non-Windows platforms navigate the process.
Virtual Machines
Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment.
.../includes/virtual-machines-disks-shared-limitations.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation repeatedly references Windows Server Failover Cluster as the primary clustering solution when discussing shared disk limitations. All links and examples related to clustering are Windows-centric, with no mention of Linux clustering solutions (such as Pacemaker or Corosync) or their compatibility with shared disks. The proximity placement group link is also Windows-specific, and Windows terminology is used throughout.
Recommendations
- Add information about Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
- Include links to Linux clustering documentation where relevant.
- Clarify whether limitations (such as 'only basic disks can be used') apply to Linux clusters, or if they are Windows-specific.
- Provide parity in terminology and examples for Linux users, avoiding Windows-centric language unless the feature is Windows-only.
Virtual Machines
Run scripts in a Linux VM in Azure using managed Run Commands
...articles/virtual-machines/linux/run-command-managed.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
While the documentation is focused on Linux VMs, there is notable Windows bias in several areas: PowerShell examples and tools (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand) are heavily featured alongside Azure CLI, and Windows-specific terminology and tools (such as PowerShell cmdlets and references to Windows VM behaviors) are present. REST API and ARM template examples sometimes use PowerShell script syntax (Write-Host, .ps1) even in Linux contexts. In some sections, Windows tools and patterns are mentioned before their Linux equivalents, and there are references to Windows-specific behaviors (e.g., 'Secondary Logon' service). However, Linux parity is generally maintained, and Linux-specific details are provided.
Recommendations
- Ensure REST API and ARM template examples use Linux shell script syntax (e.g., 'echo Hello World!' or '.sh' files) when the context is Linux VMs.
- Clarify in PowerShell sections which cmdlets are cross-platform and which are Windows-only; add notes for Linux users where relevant.
- Where Windows-specific tools or services are mentioned (e.g., 'Secondary Logon'), clearly indicate their irrelevance for Linux users.
- Consider showing Azure CLI examples before PowerShell examples, as CLI is more platform-neutral and widely used for Linux.
- Review all example scripts and ensure Linux shell script (.sh) syntax is used for Linux VM scenarios.
- Add explicit Linux-focused troubleshooting steps and examples where possible.
Service Fabric
Azure Service Fabric Docker Compose Deployment Preview
...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both PowerShell and cross-platform CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell commands are presented first and in more detail, which may suggest a Windows-first approach. The CLI examples are present and sufficient for Linux/macOS users, but the initial emphasis and ordering may create minor friction.
Recommendations
- Present CLI (sfctl) examples before or alongside PowerShell examples to emphasize cross-platform support.
- Explicitly mention that sfctl is cross-platform and suitable for Linux/macOS users.
- Ensure that all features described are equally accessible via sfctl, and clarify any limitations if present.
- Consider adding a table summarizing command equivalence between PowerShell and CLI for clarity.
Virtual Machines
Best practices for virtual machine cost optimization
...s/virtual-machines/cost-optimization-best-practices.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation generally maintains parity between Windows and Linux, but there is a minor bias in listing Windows-specific recommendations before Linux equivalents (e.g., 'Use at least B2 for Windows machines' without a similar Linux note). Windows and Linux pricing links are both provided, and Linux VM creation is referenced alongside Windows. No critical sections are Windows-only, and Linux users can complete all tasks.
Recommendations
- Where VM recommendations are given (e.g., 'Use at least B2 for Windows machines'), consider also specifying guidance for Linux machines, or clarify if the recommendation applies to both.
- Ensure that automation examples (e.g., Logic Apps, Azure Automation) mention cross-platform applicability or provide links to Linux-specific automation guidance if relevant.
- When listing pricing or VM size links, consistently mention both Windows and Linux together, rather than referencing Windows first.
- If disk or storage recommendations differ for Linux, explicitly state them.
Virtual Machine Scale Sets
Networking for Azure Virtual Machine Scale Sets
...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell (a Windows-centric tool) is often presented before CLI, and some sections (e.g., adding a VMSS to Application Gateway) feature more detailed PowerShell scripts. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is referenced as a primary scripting method, which may create friction for Linux/macOS users. However, Azure CLI examples are present throughout, and ARM templates are used for platform-neutral configuration.
Recommendations
- Present Azure CLI examples before PowerShell to prioritize cross-platform tools.
- Ensure all PowerShell examples have equivalent Azure CLI examples with equal detail.
- Explicitly mention that Azure CLI works on Linux/macOS and Windows, and link to installation guides for non-Windows platforms.
- Consider adding Bash shell scripting examples for common tasks where appropriate.
- Clarify that PowerShell Core is available cross-platform, but Azure CLI is generally preferred for Linux/macOS users.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation covers both Linux and Windows VM scenarios for ephemeral OS disks, including examples and sizing for Ubuntu and Windows Server images. However, there are minor signs of Windows bias: Windows-specific details (such as page file placement) are mentioned before Linux equivalents, and PowerShell is listed before CLI in the section on customer managed keys. Overall, Linux parity is good, but Windows examples and tools are sometimes prioritized.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence and in parallel, rather than Windows first.
- When referencing tools for configuration (e.g., PowerShell and CLI), list CLI (cross-platform) before PowerShell, or present both together.
- Add explicit Linux-specific details where relevant (e.g., swap file placement, disk partitioning) to match Windows-specific notes.
- Review the order of examples and tool mentions to avoid implicit prioritization of Windows.
Service Fabric
Azure Service Fabric container image management
.../articles/service-fabric/container-image-management.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page on Azure Service Fabric container image management presents configuration settings and cleanup logic that reference Windows container base images (e.g., microsoft/windowsservercore, microsoft/nanoserver) as defaults to skip deletion. Windows images are mentioned explicitly and before Linux examples. While the configuration examples themselves are platform-neutral, the documentation does not provide Linux-specific guidance or examples, and Windows images are prioritized in explanations.
Recommendations
- Add explicit examples and guidance for Linux container images (e.g., Ubuntu, Alpine, etc.) in the 'ContainerImagesToSkip' setting.
- Clarify whether the cleanup logic and settings apply equally to Linux-based Service Fabric clusters and containers.
- Include a note or section describing any platform-specific differences in container image management between Windows and Linux Service Fabric clusters.
- Provide sample regular expressions for skipping common Linux container images, similar to the Windows examples.
Service Fabric
Architecture of Azure Service Fabric
...articles/service-fabric/service-fabric-architecture.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page describes the architecture of Azure Service Fabric in a platform-neutral way, but in the Management subsystem section, it specifically mentions 'PowerShell cmdlets' as a primary management tool, without referencing Linux/macOS equivalents (such as Azure CLI or REST APIs). This creates a mild Windows bias by implying PowerShell is the main or only management interface, and mentioning Windows security as an option in the Transport subsystem before X509 certificates.
Recommendations
- Explicitly mention cross-platform management tools such as Azure CLI and REST APIs alongside PowerShell cmdlets.
- Clarify that management operations can be performed on Linux/macOS using Azure CLI or other APIs, not just PowerShell.
- When discussing security, list X509 certificates before Windows security, or clarify that X509 certificates are cross-platform.
- Add links or references to Linux/macOS management documentation where relevant.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides both Linux and Windows perspectives, but Windows-specific tools and scenarios (such as IIS lift-and-shift and Windows container runtimes) are mentioned before or more prominently than Linux equivalents. Windows examples and links are often listed before Linux ones, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are detailed while Linux only mentions Docker. The IIS scenario is Windows-centric, with no Linux equivalent provided.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, alternating their order or grouping them together.
- Expand Linux-specific scenarios (e.g., Apache/Nginx lift-and-shift) to match the Windows IIS example.
- Provide more detail about Linux container runtimes and tools, not just Docker.
- Where Windows-specific tools are mentioned, clarify Linux equivalents or alternatives.
- Add links to Linux container documentation where Windows container docs are referenced.
Service Fabric
Package an existing executable to Azure Service Fabric
...abric/service-fabric-guest-executables-introduction.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates mild Windows bias. It references Windows file paths (e.g., Service Fabric SDK schema location in C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd), and mentions Visual Studio as a packaging tool without referencing cross-platform alternatives. There are no explicit Linux/macOS examples or instructions, and the directory structure example uses a Windows-style executable (.exe). However, the content does not explicitly exclude Linux/macOS users, and Service Fabric itself supports Linux clusters.
Recommendations
- Add explicit instructions or examples for packaging and deploying guest executables on Linux/macOS clusters.
- Mention cross-platform tools (such as Azure CLI, Service Fabric CLI (sfctl), or Visual Studio Code) alongside Visual Studio.
- Provide Linux/macOS file path equivalents for schema files and clarify if the SDK is available on those platforms.
- Include sample directory structures and executable file extensions relevant to Linux/macOS (e.g., .sh, .out).
Service Fabric
Overview of Azure Service Fabric
...ain/articles/service-fabric/service-fabric-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents Windows development tools (Visual Studio, PowerShell) before Linux equivalents and references the .NET SDK as integrated with Visual Studio and PowerShell, while Linux development is described with Java SDK, Eclipse, and Yeoman. Windows tools and patterns are mentioned first, and the quickstart link points to a .NET/Windows-focused guide, suggesting a Windows-first bias. However, Linux development is acknowledged and supported.
Recommendations
- Present Linux and Windows development options in parallel, rather than listing Windows tools first.
- Add links to Linux quickstart guides alongside Windows quickstart guides.
- Ensure examples and references to SDKs, IDEs, and CI/CD tools are balanced for both platforms.
- Clarify parity between .NET Core/.NET 5+ and Java workloads on Linux and Windows.
- Consider linking to container-focused quickstarts that are platform-agnostic.
Service Fabric
Reliable Collection object serialization
...c-reliable-services-reliable-collections-serialization.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides conceptual and code examples for Reliable Collection object serialization in Azure Service Fabric, which is a cross-platform technology. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned before any Linux/macOS alternatives, and there are no references to Linux-native tools or CLI equivalents for application upgrades.
Recommendations
- Add references to cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl) for application upgrades.
- Include links or examples for upgrading applications on Linux/macOS environments.
- Ensure parity by mentioning Linux/macOS-compatible development environments (e.g., VS Code, CLI) alongside Visual Studio and PowerShell.
- If PowerShell is referenced, also mention Bash or other shell scripting options where applicable.
Service Fabric
Learn Azure Service Fabric terminology
...es/service-fabric/service-fabric-technical-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page is generally cross-platform and describes Service Fabric concepts applicable to both Windows and Linux. However, there are subtle indications of Windows bias: Windows-specific tools and executables (such as FabricHost.exe, Fabric.exe, and FabricGateway.exe) are mentioned without Linux equivalents or clarification, and Windows terminology (e.g., EXE/DLL files) is used first or exclusively in some sections. The description of node startup references an 'auto-start Windows service' without mentioning the Linux equivalent. Overall, Linux support is acknowledged, but Windows examples and terminology are presented first or more prominently.
Recommendations
- Clarify when concepts or tools are Windows-specific and provide Linux equivalents or explanations where applicable (e.g., how nodes are started on Linux, what executables are used).
- Use neutral terminology (e.g., 'executable files' instead of 'EXE/DLL files') and mention Linux file types or patterns.
- Add explicit notes or examples for Linux users where Windows-specific processes or tools are described.
- Ensure parity in describing both Windows and Linux container support, including mentioning Docker containers on Linux alongside Windows Server containers.
Virtual Machine Scale Sets
Azure Virtual Machine Scale Sets Attached Data Disks
...cale-sets/virtual-machine-scale-sets-attached-disks.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Windows and Linux examples for preparing data disks in Service Fabric clusters, but the Windows example is presented first. There is no evidence of missing Linux examples, PowerShell-heavy bias, or exclusive mention of Windows tools. Both Azure CLI and PowerShell tutorials are referenced equally, and Linux parity is maintained throughout the article.
Recommendations
- Present Windows and Linux examples side-by-side or alternate their order to avoid implicit prioritization.
- Explicitly state that both Windows and Linux are supported for all relevant operations.
- Ensure future updates maintain parity in examples and tool references.
Virtual Machine Scale Sets
Configure rolling upgrades on Virtual Machine Scale Sets
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides parity between Azure CLI and PowerShell for all programmatic examples, but consistently lists PowerShell examples immediately after CLI and before ARM templates. Portal instructions are also included. There is no explicit bias toward Windows tools, but PowerShell is presented as a primary scripting option alongside CLI, which may subtly prioritize Windows users. No Linux-specific tools or shell examples (e.g., Bash) are provided, but Azure CLI is cross-platform and sufficient for Linux/macOS users.
Recommendations
- Clarify that Azure CLI commands are fully supported on Linux/macOS and are the recommended cross-platform option.
- Consider explicitly mentioning Bash or shell scripting as an alternative for Linux/macOS users, if relevant.
- If possible, provide brief notes or links for Linux/macOS users about installing and using Azure CLI.
- Ensure that PowerShell is not presented as the default or primary scripting method for cross-platform scenarios.
Virtual Machine Scale Sets
Automatic OS image upgrades with Azure Virtual Machine Scale Sets
...e-sets/virtual-machine-scale-sets-automatic-upgrade.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation covers both Windows and Linux VM images for Azure Virtual Machine Scale Sets and provides parity in supported OS SKUs and configuration methods. However, there are minor signs of Windows bias: Windows terminology and properties (e.g., drive letters, enableAutomaticUpdates) are mentioned first or exclusively in some requirements, and PowerShell examples are presented before Azure CLI examples. ARM template snippets default to Windows image values. No critical Linux gaps are present, but Windows-centric patterns are slightly prioritized.
Recommendations
- Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- In ARM template and Bicep examples, provide both Windows and Linux image values, or use a neutral example.
- Where Windows-specific properties (e.g., drive letters, enableAutomaticUpdates) are discussed, clarify Linux equivalents or explicitly state if not applicable.
- Ensure Linux terminology (e.g., mount points, file systems) is referenced where relevant, not just Windows drive letters.
- Review for any subtle language that assumes Windows as the default and adjust for neutrality.
Virtual Machine Scale Sets
Custom metrics for rolling upgrades on Virtual Machine Scale Sets
...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Linux and Windows examples for configuring custom metrics for rolling upgrades on Virtual Machine Scale Sets, including CLI, Bash, PowerShell, and REST API. However, there are several areas where Windows/PowerShell examples are presented first or in greater detail, and Windows-specific extension types (ApplicationHealthWindows) are used in sample code. PowerShell examples are prominent, and Windows tools/patterns (such as PowerShell scripts and extension names) are mentioned alongside or before Linux equivalents. Linux parity is generally good, but minor ordering and naming biases exist.
Recommendations
- Ensure Linux examples (CLI, Bash, ApplicationHealthLinux) are presented before or alongside Windows/PowerShell examples, especially in critical sections.
- Clarify in sample code and tables that both ApplicationHealthLinux and ApplicationHealthWindows are supported, and provide explicit Linux-focused examples where possible.
- Review ordering of tabs and examples to avoid Windows-first bias; alternate or group by OS where appropriate.
- Expand Bash/Linux sample scripts to match the detail and completeness of PowerShell examples.
- Explicitly mention macOS compatibility where relevant (e.g., Bash, Python examples).
Virtual Machines
Deploy Azure dedicated hosts
...in/articles/virtual-machines/dedicated-hosts-how-to.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides parity for both Linux and Windows users, with Azure CLI and PowerShell examples for all major operations. However, PowerShell examples are always present and CLI examples sometimes reference Windows-specific instructions (e.g., removing --generate-ssh-keys for Windows VMs). Portal instructions use generic steps, but the ordering of examples consistently places PowerShell after CLI, and CLI after Portal, which may subtly prioritize Windows users. There are no missing Linux examples, and Azure CLI is cross-platform, but PowerShell is Windows-centric (though now available on Linux/macOS).
Recommendations
- Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Where CLI examples reference Windows-specific steps (such as password prompts), clarify Linux/macOS differences.
- Consider alternating the order of CLI and PowerShell examples, or grouping them as 'Command-line' to avoid implicit prioritization.
- Add a brief note that PowerShell is available on Linux/macOS, but Azure CLI is generally preferred for Linux users.
- Ensure that all CLI examples are tested and work on Linux/macOS shells (bash/zsh), and clarify any OS-specific nuances.
Virtual Machine Scale Sets
Orchestration modes for Virtual Machine Scale Sets in Azure
...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides a comprehensive overview of orchestration modes for Azure Virtual Machine Scale Sets and is largely platform-neutral. However, in the 'Backup and recovery' section, Azure Site Recovery is noted as supported 'via PowerShell' for Flexible orchestration mode, without mentioning Linux CLI or portal alternatives. Additionally, the only explicit CLI example uses Azure CLI, which is cross-platform, but the PowerShell mention appears before any Linux equivalent. Overall, the documentation does not heavily favor Windows, but there is a minor tendency to mention Windows/PowerShell tools first.
Recommendations
- Clarify that Azure Site Recovery can be managed via Azure CLI and Portal, not just PowerShell, for Linux/macOS users.
- Where PowerShell is mentioned, also provide Azure CLI or portal instructions/examples if available.
- Ensure examples and tool references are presented in a platform-neutral order or explicitly state cross-platform support.
Virtual Machine Scale Sets
Create an Azure scale set that uses Availability Zones
...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI examples, and in some sections (such as updating scale sets), PowerShell is listed before REST API and after CLI. There is no explicit Linux shell example (e.g., Bash), and PowerShell is a Windows-centric tool, though it is now cross-platform. The CLI example uses az CLI, which is cross-platform, but there are no explicit Linux/macOS shell commands or notes about Linux-specific considerations. The Resource Manager template section references both Linux and Windows getting started articles, which is positive for parity. Overall, the bias is minor and mostly in the ordering and prominence of PowerShell.
Recommendations
- Ensure that CLI (az CLI) examples are always listed first, as they are cross-platform and preferred for Linux/macOS users.
- Add explicit Bash shell examples or notes clarifying that Azure CLI commands work on Linux/macOS terminals.
- Where PowerShell is used, clarify that it is available cross-platform, or provide Bash equivalents if there are any subtle differences.
- Consider adding a brief section or note for Linux/macOS users to highlight any OS-specific considerations or prerequisites.
Virtual Machines
Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents."
...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides a generally balanced overview of backup and disaster recovery for Azure Managed Disks, explicitly stating applicability to both Linux and Windows VMs. However, there are subtle signs of Windows bias: Windows tools and patterns (such as Volume Shadow Service and SQL Server Always On) are mentioned before Linux equivalents, and Windows-specific examples (SQL Server) are more detailed. Linux tools (like fsfreeze) are referenced, but with less explanation and prominence. No Linux/Unix command-line examples or scripts are provided, and PowerShell or Windows-centric terminology appears more frequently.
Recommendations
- Provide Linux-specific examples and tools with equal detail and prominence as Windows tools (e.g., explain fsfreeze usage and limitations, mention other Linux backup coordination tools).
- Include sample Linux shell commands/scripts for snapshot coordination and backup automation, similar to PowerShell examples often found in Windows documentation.
- When referencing application-consistent backup, clarify how Linux workloads (such as PostgreSQL, MySQL, etc.) can achieve similar results, and link to relevant documentation.
- Ensure parity in database examples by including Linux-first workloads (e.g., PostgreSQL, MySQL) alongside SQL Server.
- Review the order of tool mentions to avoid always listing Windows solutions first.
Virtual Machines
Server-side encryption of Azure Managed Disks
...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation covers server-side encryption for Azure Managed Disks and is explicitly applicable to both Linux and Windows VMs. However, throughout the page, Windows/PowerShell examples and links are consistently presented before Linux/CLI equivalents. References to Azure PowerShell are often given first, and in some cases, only PowerShell is mentioned in the context of revoking access, with CLI as a secondary mention. There is also a slight emphasis on Windows tools (e.g., BitLocker) in comparison sections, but Linux equivalents (DM-Crypt) are also referenced.
Recommendations
- Present Linux/CLI examples and links alongside or before Windows/PowerShell examples to avoid implicit prioritization.
- Ensure that all procedural references (such as revoking access) include both PowerShell and CLI options equally and clearly.
- Where possible, use neutral language and ordering when listing cross-platform tools or features.
- Consider adding explicit Linux/macOS command examples or clarifying parity in any ambiguous sections.
Virtual Machines
Benchmark your application on Azure Disk Storage
...lob/main/articles/virtual-machines/disks-benchmarks.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation mentions both Windows (DiskSpd) and Linux (FIO) benchmarking tools, but DiskSpd (Windows) is listed first and the overall tone slightly favors Windows by mentioning Windows tools and patterns before Linux equivalents. However, both platforms are acknowledged and tools for each are referenced. The actual benchmarking example details are not shown, so it's unclear if Linux examples are missing or less detailed.
Recommendations
- Ensure Linux (FIO) examples are as detailed and prominent as Windows (DiskSpd) examples.
- Consider alternating the order in which Windows and Linux tools are mentioned, or presenting them side-by-side.
- Explicitly state that both tools are equally supported and provide links to comprehensive usage guides for both.
- If possible, include sample command lines or scripts for both DiskSpd and FIO in the documentation.
Virtual Machines
Migrate Standard HDD OS disks by September 08, 2028
...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides migration guidance for both Linux and Windows VMs, and explicitly states applicability to both. However, in the section describing how to list affected disks using Azure PowerShell and Azure CLI, the PowerShell example is mentioned first, which is a minor Windows-first bias. Both Linux-friendly (Azure CLI) and Windows-friendly (PowerShell) tools are referenced, and the examples are equivalent. No critical Windows-only tools or patterns are present, and Linux users can complete all tasks described.
Recommendations
- Present Azure CLI and PowerShell examples in parallel or alternate which is shown first.
- Explicitly note that Azure CLI is cross-platform and may be preferred for Linux/macOS users.
- Consider adding Bash or shell script snippets for bulk operations, if relevant.
Virtual Machines
Enable on-demand disk bursting
...ain/articles/virtual-machines/disks-enable-bursting.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for enabling on-demand disk bursting using the Azure portal, PowerShell, Azure CLI, and ARM templates. The PowerShell section is prominent and detailed, and PowerShell is a Windows-centric tool. The ordering of examples places PowerShell before Azure CLI, which is more cross-platform. There are no explicit Linux/macOS-specific instructions or examples, but Azure CLI and ARM templates are inherently cross-platform. No Windows-only tools or patterns are exclusively mentioned, and Linux users can complete all tasks using Azure CLI or ARM templates.
Recommendations
- Consider placing Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI and ARM templates can be used on Linux/macOS, and provide links to installation guides for those platforms.
- Add a note clarifying that PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
- Ensure parity in example detail between PowerShell and Azure CLI sections.
Virtual Machines
Enable end-to-end encryption using encryption at host - Azure portal - managed disks
...-machines/disks-enable-host-based-encryption-portal.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for enabling encryption at host, but PowerShell examples are consistently presented first. The 'Next steps' section links to a PowerShell-focused sample repository. There is a slight preference for Windows/PowerShell tools and ordering, though Linux parity is generally maintained via Azure CLI examples.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first in some sections.
- Include links to Azure CLI sample repositories in the 'Next steps' section, not just PowerShell.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and clarify any OS-specific nuances.
- Where possible, add screenshots or references for Linux/macOS users in portal walkthroughs.
Virtual Machines
Restrict managed disks from being imported or exported
...tual-machines/disks-restrict-import-export-overview.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides links and references to both Azure PowerShell and Azure CLI for configuring disk restrictions, but the custom RBAC role section links only to a PowerShell-based guide. Additionally, PowerShell is mentioned before CLI in the section about configuring the NetworkAccessPolicy parameter, suggesting a Windows-first approach. Linux-specific examples or parity are not missing, but Windows tools are given prominence.
Recommendations
- Add a link to a custom RBAC role creation guide using Azure CLI or ARM templates, not just PowerShell.
- When mentioning configuration tools, list Azure CLI before PowerShell or equally, to avoid Windows-first bias.
- Where possible, provide explicit Linux/macOS command examples alongside PowerShell examples.
Virtual Machines
Secure Azure Managed Disk Downloads and Uploads
...icles/virtual-machines/disks-secure-upload-download.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for securing managed disk downloads and uploads, but PowerShell examples are often presented before CLI examples. There is a slight preference for PowerShell (a Windows-centric tool) in ordering and prominence. However, Linux parity is generally maintained, with CLI examples and Linux-specific next steps included.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side or alternate their ordering to avoid Windows-first bias.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Where possible, add Bash shell script examples for Linux users.
- Ensure screenshots and portal instructions are not Windows-centric.
- Review included files (prereqs/restrictions) to confirm Linux parity.
Virtual Machines
Enable InfiniBand on HPC VMs - Azure Virtual Machines | Microsoft Docs
...icles/virtual-machines/extensions/enable-infiniband.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation covers both Linux and Windows for enabling InfiniBand on Azure HPC VMs. However, there is mild bias in the 'InfiniBand Driver VM Extensions' section, where Windows extension details and PowerShell usage are mentioned before Linux equivalents, and PowerShell is presented as the primary tool for extension management. Linux examples are present and detailed, but Windows tools and patterns are referenced first in some sections.
Recommendations
- Present Linux and Windows instructions in parallel or clearly separated sections, avoiding Windows-first ordering.
- Include Azure CLI or ARM template examples for managing VM extensions, as these are cross-platform and commonly used on Linux/macOS.
- Explicitly mention Linux tools (e.g., az CLI) alongside PowerShell when discussing VM extension management.
- Ensure that Linux examples are as prominent and detailed as Windows examples throughout the documentation.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides both Azure CLI and Azure PowerShell deployment instructions. However, PowerShell examples and troubleshooting commands are presented first in several sections, and PowerShell-specific warnings are highlighted. While Azure CLI instructions are included and the extension is Linux-specific, the ordering and emphasis on PowerShell may create friction for Linux users, as PowerShell is not a native tool on most Linux distributions.
Recommendations
- Present Azure CLI examples before PowerShell in all sections, as CLI is more commonly used on Linux.
- Add explicit notes clarifying that PowerShell is optional and not required for Linux deployments.
- Highlight Azure CLI as the recommended method for Linux users.
- Where troubleshooting commands are shown, show Azure CLI first and PowerShell second.
- Consider removing PowerShell-specific warnings from the main flow or move them to a dedicated section for cross-platform users.
Virtual Machines
What's new in Azure Disk Storage
...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation is largely neutral and focused on Azure Disk Storage features, but there are a few minor signs of Windows bias. Some links and references point to Windows-specific documentation first or exclusively (e.g., 'expand with Ultra Disks and Premium SSD v2' links to a Windows page, and 'find-unattached-disks' documentation is Windows-focused). In one section, the Windows article is mentioned before the Linux equivalent for expanding disks without downtime. There is also a reference to Azure PowerShell in describing disk properties, which may be perceived as a Windows-centric tool, though Azure CLI is also mentioned.
Recommendations
- Ensure that all feature links referencing operational tasks (e.g., expanding disks, finding unattached disks) include both Windows and Linux documentation, or use a neutral landing page that covers both.
- When mentioning tools like Azure PowerShell, always mention Azure CLI alongside it, and clarify cross-platform support.
- When listing example articles for tasks, alternate the order or use a neutral phrasing (e.g., 'See the Windows and Linux articles' instead of 'See the Windows or Linux articles').
- Review linked documentation to ensure Linux parity and add missing Linux examples where only Windows is referenced.
Virtual Machines
NVIDIA GPU Driver Extension - Azure Linux VMs
...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation is focused on Linux VM GPU driver installation, but includes PowerShell examples for deploying the extension before Azure CLI examples. PowerShell is primarily a Windows tool, and its inclusion and placement before Linux-native tools (Azure CLI, Bash) may create friction for Linux users. However, Linux-specific instructions, examples, and troubleshooting steps are present throughout, and the extension itself is Linux-focused.
Recommendations
- Move Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more commonly used by Linux/macOS users.
- Clarify that PowerShell is optional and primarily for Windows users; recommend Azure CLI for Linux/macOS users.
- Consider adding Bash script examples for common tasks (e.g., checking extension status, troubleshooting).
- Ensure screenshots and instructions are Linux-centric, as currently done.
Virtual Machines
Create an encrypted image version with customer-managed keys
.../articles/virtual-machines/image-version-encryption.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both PowerShell and Azure CLI examples for creating encrypted image versions with customer-managed keys. However, PowerShell examples are presented first and in greater detail, with more explanation and step-by-step variable setup, while the Azure CLI section is less detailed. There are no explicit Linux shell (bash) or macOS-specific examples, but the CLI commands are cross-platform. References to Windows-specific tools or patterns are minimal, and the feature itself applies to both Linux and Windows VMs.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Ensure that CLI and PowerShell examples are equally detailed, with similar variable setup and explanation.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide a short note or link on how to install Azure CLI on non-Windows platforms.
- Where possible, add bash script examples for common tasks, or clarify that the CLI commands can be run in any shell.
- Avoid referencing Windows-specific cryptographic documentation (e.g., CNG) unless there is no cross-platform equivalent.
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Linux and Windows guidance, but there are subtle signs of Windows bias. In the PowerShell section, Windows examples are shown first and in more detail, while Linux is mentioned as an alternative. The CLI section is more neutral, but the PowerShell section is Windows-centric. The portal instructions are OS-agnostic. There are no missing Linux examples, and Linux-specific guidance is linked. Overall, the bias is minor and does not prevent Linux/macOS users from completing the task.
Recommendations
- In PowerShell examples, show Linux usage first or equally alongside Windows.
- Add explicit PowerShell examples for Linux image creation, not just mention '-OsType Linux'.
- Ensure parity in detail and explanation for both OS types in all example sections.
- Consider adding Bash scripting examples for Linux users, especially for automation.
- Review ordering of OS-specific guidance to avoid 'Windows first' impression.
Virtual Machines
Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines.
...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents benchmarking instructions for both Windows (using DISKSPD) and Linux (using FIO). However, the Windows section appears first and is more detailed in its explanation of command parameters, while the Linux section is presented second. Both platforms are covered with practical examples, but the ordering and slightly greater detail for Windows may create a minor perception of Windows bias.
Recommendations
- Present Linux and Windows benchmarking instructions in parallel or with equal prominence.
- Provide equally detailed explanations for Linux (FIO) command parameters as given for Windows (DISKSPD).
- Consider starting with a platform-neutral overview, then clearly separate Windows and Linux sections.
- Add a summary table comparing DISKSPD and FIO usage for quick reference.
Virtual Machines
Enable Azure Disk Encryption for Linux VMs
...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is focused on Linux VMs, with all technical guidance, examples, and requirements tailored to Linux distributions and tools. However, there is minor evidence of Windows bias: PowerShell is mentioned alongside Azure CLI as a management tool, and PowerShell quickstart links are presented equally with CLI links. The 'Terminology' section includes 'PowerShell cmdlets' as a defined term, even though the primary audience is Linux users. Azure PowerShell is a cross-platform tool, but its inclusion may create confusion for Linux users unfamiliar with PowerShell.
Recommendations
- Clarify that Azure PowerShell is available and supported on Linux/macOS, not just Windows.
- Consider prioritizing Azure CLI examples and quickstarts, as CLI is more native to Linux environments.
- In the 'Terminology' section, explain the cross-platform nature of Azure PowerShell or consider removing 'PowerShell cmdlets' if not essential for Linux users.
- If PowerShell scripts are referenced, ensure they are tested and documented for Linux/macOS shells (e.g., bash, zsh) and PowerShell Core.
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation is overwhelmingly Linux-focused, with detailed, distribution-specific instructions for expanding disks on Linux VMs. However, there is a single section at the end that provides a PowerShell script for checking classic VM SKU support for expanding disks without downtime, without offering a Linux CLI or Bash equivalent. This section assumes Windows tooling and does not provide parity for Linux users.
Recommendations
- Provide an Azure CLI or Bash equivalent for checking classic VM SKU support for expanding disks without downtime.
- If PowerShell is required for certain Azure operations, clarify that this is a Windows-only step and offer guidance for Linux users (e.g., using Azure CLI or REST API).
- Consider adding a note or link to relevant Linux/CLI documentation for classic VM SKU checks.
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is often mentioned first in critical backup/encryption steps and is referenced heavily throughout. Some instructions and warnings refer to PowerShell cmdlets before CLI equivalents, and PowerShell scripts are detailed with variable initialization, while CLI examples are more concise. However, Linux parity is generally maintained, as Azure CLI is cross-platform and all tasks can be completed using CLI. No Windows-only tools or patterns are used, and Linux-specific context is clear.
Recommendations
- Ensure that Azure CLI examples are shown before PowerShell examples, especially in critical steps, to reinforce Linux-first workflows.
- Expand CLI examples to include more detailed scripting where appropriate, matching the depth of PowerShell scripts.
- Clarify that PowerShell can be used cross-platform (via PowerShell Core), but highlight Azure CLI as the primary tool for Linux users.
- Review warnings and important notes to ensure CLI commands are referenced equally or before PowerShell cmdlets.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for verifying disk encryption status on Linux VMs. However, the PowerShell section is presented before the Azure CLI section, and PowerShell examples are more detailed and numerous. This creates a minor Windows bias, as PowerShell is primarily a Windows-centric tool, even though it is available cross-platform. The CLI examples are present and functional, but PowerShell receives more prominence and depth.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is the default cross-platform tool for Linux users.
- Ensure CLI and PowerShell sections have parity in detail and coverage.
- Explicitly note that PowerShell examples are for users who prefer PowerShell (including on Linux/macOS), but Azure CLI is recommended for Linux environments.
- Consider adding Bash script examples for purely OS-level checks, where relevant.
Virtual Machines
Create and upload a Red Hat Enterprise Linux VHD for use in Azure
...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation covers preparation of Red Hat Enterprise Linux VHDs for Azure using multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). While all major Linux hypervisors are included, Windows-centric tools and workflows (Hyper-V Manager, PowerShell convert-vhd cmdlet) are often mentioned first or in more detail, and some conversion instructions reference Windows tools before Linux equivalents. However, Linux-native workflows are well-documented and parity is strong overall.
Recommendations
- Where disk conversion is discussed, mention Linux-native tools (e.g., qemu-img) before or alongside Windows tools (e.g., Hyper-V Manager, convert-vhd).
- Ensure that instructions for VMware and KVM are as detailed and prominent as those for Hyper-V.
- Consider adding a summary table or section at the top that lists all supported hypervisors and their respective workflows equally, rather than starting with Hyper-V.
- Where possible, avoid language that implies Hyper-V is the default or preferred option for Linux VHD creation.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides comprehensive Linux-specific guidance. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details. All configuration examples, tools, and commands are Linux-centric, with only a single PowerShell example for base64 encoding cloud-init data (which is relevant for Azure ARM template usage, not VM configuration). There are no missing Linux examples or Windows-only tools for the core topic.
Recommendations
- Move or minimize Windows Server 2016 discussion in the introduction, focusing first on Linux time sync context.
- Add a brief explanation for the PowerShell example, noting its relevance for Azure template preparation and suggesting a Linux equivalent (e.g., using 'base64' command).
- Ensure Linux-specific guidance is always presented before any Windows references unless Windows context is strictly necessary.
Virtual Machines
Overview of Azure Disk Storage
...in/articles/virtual-machines/managed-disks-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
minor_windows_reference
Summary
The documentation provides a balanced overview of Azure Managed Disks for both Linux and Windows VMs. However, there are minor instances where Windows-specific tools, references, or examples are mentioned first or exclusively, such as links to Windows/PowerShell guides, references to Windows drive letters, and Windows partitioning documentation. Linux equivalents are present but sometimes appear after Windows examples or are less detailed.
Recommendations
- Ensure Linux and Windows examples/tools are presented together or in parallel, rather than Windows-first.
- Where Windows-specific documentation is linked (e.g., PowerShell), provide equivalent Linux (e.g., Bash/CLI) links alongside.
- When referencing disk partitioning or file systems, include Linux documentation and examples (e.g., GPT/MBR on Linux, /dev paths, fdisk/gdisk usage).
- Clarify Linux-specific behaviors (e.g., temporary disk location, partitioning) with equal detail as Windows.
- Review all linked guides to ensure Linux parity in depth and clarity.
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation covers both Linux and Windows VM image creation with Azure Image Builder, and provides parity in most areas. However, there are several instances of Windows bias: PowerShell examples and references are often shown before Linux equivalents, Windows-specific tools (e.g., Get-FileHash, PowerShell customizer, WindowsRestart/WindowsUpdate customizers) are discussed in detail, and instructions for generating checksums or running commands frequently reference Windows/PowerShell first. Some customizers (WindowsRestart, WindowsUpdate) are Windows-only, but this is clearly documented. Linux examples are present, but sometimes appear after Windows ones or are less detailed.
Recommendations
- Ensure Linux (Shell/bash) examples are presented alongside or before Windows/PowerShell examples, especially in sections where both are supported.
- When referencing tools for tasks like generating SHA256 checksums, mention Linux/macOS commands (e.g., sha256sum) before or alongside Windows tools (e.g., Get-FileHash).
- Where possible, provide Linux-focused troubleshooting and validator examples with equal detail to Windows.
- Explicitly note when a feature or customizer is Windows-only to avoid confusion.
- Review ordering of sections and examples to avoid implicit prioritization of Windows tools and patterns.