Scan Details - Linux-first Docs for Azure

274

Pages Scanned

113

Pages Flagged

274

Changed Pages

41.2%

% Pages Flagged

Live Progress

🔴 Connecting...

100%

Phase: discovery

Processing: Initializing...

Activity Feed

00:00:08 Scan started

Scan Information

Started At: 2026-03-10 00:00:08

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 274

Files Completed: 274

Problematic Pages

113 issues found

Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

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 reference Windows container images, Windows paths (e.g., C:\), and Windows-specific commands (cmd, echo, type, ping). There is no mention of Linux containers, Linux paths, or Linux command equivalents. The page explicitly states that the example assumes familiarity with Windows container applications, and all technical details are Windows-centric.

Recommendations

Add examples for Linux containers, including Linux-based container images (e.g., Ubuntu, Alpine) and Linux shell commands (e.g., bash, echo, cat, sleep).
Clarify whether Initializer CodePackages are supported for Linux containers and, if not, state this limitation explicitly at the top of the page.
If Linux containers are supported, provide parallel ApplicationManifest and ServiceManifest examples using Linux paths and volume mounts.
Mention Linux container version compatibility or provide links to relevant documentation, similar to the Windows container compatibility note.

Create Pull Request

Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and guidance are Windows-centric. There are no Linux equivalents, examples, or workarounds provided, and the feature is described as Windows-only. This creates a clear platform bias, but it is primarily due to the feature's current limitations rather than documentation oversight.

Recommendations

Clearly indicate at the top of the documentation that the reverse proxy feature is Windows-only and unavailable for Linux clusters.
Provide links or references to alternative approaches for service discovery and communication in Linux Service Fabric clusters, if any exist.
If possible, document any roadmap or plans for Linux support, or direct Linux users to relevant feature requests or GitHub issues.
Ensure that Linux users are not misled into attempting to use the reverse proxy and are guided to appropriate alternatives.

Create Pull Request

Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ missing_linux_example ⚠️ windows_first

Summary

Although the introduction claims Service Fabric clusters run on both Windows Server and Linux, the documentation later states that Linux isn't yet supported for standalone clusters. All examples, security sections, and supported OS lists are Windows-only, with no Linux instructions or parity. This creates confusion for Linux users and omits Linux-specific guidance.

Recommendations

Clarify early in the overview that standalone clusters are currently Windows-only, and Linux support is not available.
Remove or rephrase statements suggesting Linux parity until it is actually supported.
If Linux support is planned, provide a roadmap or guidance for Linux users.
Ensure that examples and instructions do not imply Linux support where it does not exist.

Create Pull Request

Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation page provides management guidance for Service Fabric Explorer and ARM-managed resources. It consistently recommends Az PowerShell cmdlets for operations (e.g., Remove-AzResource, AzSF PowerShell cmdlets) and references them before or instead of Azure CLI equivalents. While Azure CLI (az resource) is mentioned once for deleting applications, PowerShell is emphasized throughout, and Linux/macOS users may find the instructions less accessible or unclear, especially since PowerShell is not the default shell on those platforms.

Recommendations

Provide Azure CLI equivalents for all PowerShell cmdlet examples, especially for operations like unprovisioning application type versions and creating services/applications.
Clearly indicate when both PowerShell and Azure CLI can be used, and offer examples for each.
Mention that PowerShell Core is cross-platform, but highlight Azure CLI as the default for Linux/macOS users.
Structure examples so that CLI and PowerShell are presented side-by-side, or at least alternate which is shown first.

Create Pull Request

Service Fabric Deploy and upgrade with Azure Resource Manager ...vice-fabric/service-fabric-application-arm-resource.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page provides PowerShell examples for removing Service Fabric application resources and references PowerShell as a primary tool for deployment/removal, with no equivalent CLI or Linux/macOS instructions. PowerShell is mentioned before CLI in the introduction, and the 'Next steps' section lists PowerShell before CLI. There are no explicit Linux/macOS examples or guidance, creating friction for non-Windows users.

Recommendations

Provide Azure CLI examples alongside PowerShell for resource removal and management tasks.
Explicitly mention cross-platform tools (such as Azure CLI and Service Fabric CLI) in relevant sections, not just in 'Next steps'.
Clarify which steps and tools are platform-agnostic and which are Windows-specific.
Add notes or links for Linux/macOS users on how to perform equivalent operations.
Ensure that CLI examples are given equal prominence to PowerShell throughout the documentation.

Create Pull Request

Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation page presents Windows/PowerShell and Visual Studio parameters and workflows first and in greater detail, with Linux/CLI (sfctl) information appearing later and less prominently. Examples and parameter tables are heavily focused on PowerShell and Visual Studio, with minimal direct CLI/Linux guidance or examples. No explicit Linux command examples are provided in the main parameter sections, and Windows tools are mentioned before their Linux equivalents.

Recommendations

Add explicit Linux/CLI (sfctl) command examples alongside PowerShell examples in parameter tables.
Reorganize the documentation so that CLI/sfctl instructions are presented equally and not after Windows tools.
Clarify which tools are cross-platform and which are Windows-only, to help Linux/macOS users navigate options.
Include a summary table mapping parameters between PowerShell, Visual Studio, and sfctl for easy comparison.
Consider providing a Linux/macOS workflow section or highlighting Linux-specific considerations.

Create Pull Request

Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation page primarily discusses deploying custom Windows images on Azure Service Fabric Managed Clusters, with Windows terminology and PowerShell examples presented. While there is a brief mention of Linux custom image creation, the main content and examples focus on Windows, and the PowerShell command for role assignment is given without a Linux CLI equivalent.

Recommendations

Provide equivalent Azure CLI examples for Linux/macOS users, especially for role assignments.
Clarify whether Linux custom images are supported for Service Fabric Managed Clusters and, if so, include relevant examples and guidance.
Balance the order of Windows and Linux references (e.g., mention Linux custom image creation before or alongside Windows).
Explicitly state any platform limitations (e.g., if only Windows images are supported for Service Fabric Managed Clusters, clarify this to avoid confusion).

Create Pull Request

Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first

Summary

The documentation page primarily describes Service Fabric's periodic backup configuration in a platform-neutral way, but the only example for file share backup storage uses Windows-style UNC paths (\\StorageServer\BackupStore) and references 'Integrated Windows Authentication' as the default for file share access. There are no explicit Linux or macOS file share examples, and Windows authentication is discussed before username/password alternatives. No PowerShell or Windows command-line examples are present, but the file share section is Windows-centric.

Recommendations

Add examples for file share backup storage using SMB mounts on Linux (e.g., /mnt/backupstore or guidance for mounting CIFS shares).
Clarify whether Linux clusters can use file share backup storage, and if so, provide instructions for configuring access from Linux nodes.
Mention Linux authentication mechanisms (e.g., username/password, Kerberos, etc.) where relevant.
Consider including a note about cross-platform compatibility for file share backup storage.

Create Pull Request

Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation page provides general guidance for upgrading Azure Service Fabric clusters and references both PowerShell and Azure CLI for management tasks. However, in the section 'Upgrading OS images for cluster nodes', the only linked guidance is for patching Windows operating systems, with no mention or link to Linux node patching. Additionally, the phrase 'Patch the Windows operating system in your Service Fabric cluster' is used without clarifying if Linux clusters are supported or providing equivalent Linux guidance. Examples and tool mentions (PowerShell/Azure CLI) are presented together, but Windows-specific patching is prioritized.

Recommendations

Add explicit guidance or links for patching/upgrading Linux node OS images in Service Fabric clusters, if supported.
Clarify whether the patching guidance is Windows-only, and provide Linux parity or state Linux limitations.
Ensure that examples and instructions for certificate management, port opening, and other cluster operations include both PowerShell and Azure CLI, with explicit Linux/macOS compatibility notes.
Where possible, avoid phrases like 'Patch the Windows operating system' without mentioning Linux, or add a note about Linux support status.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation page provides PowerShell examples for managing node tags and service requirements, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). PowerShell is a Windows-centric tool, and its exclusive use creates friction for non-Windows users. The C# API examples are cross-platform, but scripting and command-line guidance is Windows-biased.

Recommendations

Add Azure CLI or Bash examples for managing node tags and service requirements, highlighting cross-platform usage.
Include REST API example requests for tag management, as REST is platform-neutral.
Clarify which PowerShell commands are available on Linux/macOS (if any), or note their Windows-specific nature.
Consider reordering examples so that cross-platform methods (REST, CLI) are shown before or alongside PowerShell.

Create Pull Request

Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page references Windows-specific upgrade and configuration guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md') and the Patch Orchestration Application for Windows. There are no explicit Linux/macOS examples or links to equivalent Linux documentation, even though Service Fabric standalone clusters can be run on Linux. Windows terminology and guides are mentioned exclusively, creating friction for Linux users.

Recommendations

Add links to Linux-specific upgrade and configuration guides (e.g., 'service-fabric-cluster-upgrade-linux.md', 'service-fabric-cluster-config-upgrade-linux.md') if available.
Mention Linux support explicitly where applicable, and clarify which features/tools are Windows-only.
Provide Linux/macOS examples or instructions alongside Windows ones, especially for cluster upgrades and configuration.
Include information about patch orchestration or OS patching for Linux nodes if supported.

Create Pull Request

Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools ⚠️ windows_first

Summary

The documentation page for 'Networking patterns for Azure Service Fabric' exhibits a notable Windows bias. All deployment and management command-line examples use PowerShell (New-AzResourceGroup, New-AzResourceGroupDeployment, Get-AzPublicIpAddress), with no mention of Azure CLI, Bash, or cross-platform alternatives. File paths and command prompts are Windows-style (e.g., C:\SFSamples\...), and even network troubleshooting examples use Windows commands (ping from C:> prompt). There are no Linux/macOS-specific instructions or parity examples, which may create friction for users on those platforms.

Recommendations

Provide Azure CLI equivalents for all PowerShell deployment commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
Include Bash shell examples and Linux/macOS file path formats where relevant.
When demonstrating network troubleshooting, offer Linux equivalents (e.g., ping 10.0.0.5 from a Bash prompt) alongside Windows commands.
Clarify that PowerShell examples are for Windows users and direct Linux/macOS users to appropriate alternatives.
Consider reordering or balancing examples so that Windows and Linux approaches are presented with equal prominence.

Create Pull Request

Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation page for Azure Service Fabric application resource model exhibits several Windows biases. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI or other cross-platform tools. The packaging step references Visual Studio, a Windows-centric IDE, and does not mention alternatives for Linux/macOS. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented exclusively and first.

Recommendations

Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
Provide instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF SDK for Linux/macOS).
Mention and link to cross-platform IDEs (e.g., VS Code) or command-line alternatives for application packaging.
Clearly indicate which steps are Windows-only and provide Linux/macOS equivalents where possible.
Consider reordering examples so that cross-platform options are presented first or equally.

Create Pull Request

Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation page on Azure Service Fabric Events primarily references Windows-centric logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and tools, with no mention of Linux equivalents or examples. Windows tools and patterns are discussed first and exclusively, creating friction for Linux cluster administrators seeking parity.

Recommendations

Add information about how Service Fabric events are logged and accessed on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration for Linux).
Provide Linux-specific examples or clarify any differences in event collection and diagnostics configuration for Linux-based Service Fabric clusters.
Mention cross-platform monitoring tools and how they can be used to access Service Fabric events regardless of OS.
If certain features are Windows-only, explicitly state this to avoid confusion for Linux users.

Create Pull Request

Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation page provides explicit PowerShell instructions for using the Fault Analysis Service, but does not mention or provide examples for Linux/macOS command-line tools or SDK usage. The focus on PowerShell and lack of Linux-specific guidance creates friction for non-Windows users.

Recommendations

Add examples for using the Fault Analysis Service from Linux/macOS environments, such as Bash scripts, CLI commands, or REST API usage.
Mention cross-platform tools (e.g., Azure CLI, Service Fabric CLI) and how to install/use them on Linux/macOS.
Clarify whether the Fault Analysis Service APIs and features are accessible from Linux-based development environments, and provide relevant guidance.
If PowerShell is required, note that PowerShell Core is cross-platform and provide installation/use instructions for Linux/macOS.

Create Pull Request

Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

While the documentation states it applies to both Windows and Linux VMs and includes cross-platform Azure CLI and API examples, there are notable signs of Windows bias. PowerShell examples are always present, but there are no equivalent Bash or Linux shell script examples. The ARM template section defaults to Windows images and parameters, with no Linux image guidance. Windows terminology (e.g., password requirements, RDP port 3389) appears by default, and Windows is the only OS shown in ARM template allowed values. Linux is only referenced in the CLI example image parameter.

Recommendations

In ARM template examples, add a Linux image option (e.g., Ubuntu) and show how to parameterize for both Windows and Linux.
In sections referencing administrator credentials, clarify the differences for Linux VMs (e.g., SSH key vs. password).
In ARM template network security rules, include port 22 (SSH) for Linux, not just port 3389 (RDP).
Provide Bash or Linux shell script equivalents for PowerShell examples, or clarify that CLI commands are cross-platform.
When listing OS options or parameters, show both Windows and Linux choices.
Avoid defaulting to Windows terminology or requirements unless the step is truly Windows-specific.

Create Pull Request

Virtual Machines Deploy a Premium SSD v2 managed disk ...n/articles/virtual-machines/disks-deploy-premium-v2.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 disks, but all VM creation examples use a Windows image (Win2016Datacenter) and Windows-style admin credentials. There are no explicit Linux VM examples, and the CLI scripts do not show how to deploy or attach disks to Linux VMs. This may cause confusion or extra work for Linux users.

Recommendations

Add explicit Linux VM deployment examples in the Azure CLI sections (e.g., use Ubuntu or CentOS images, show SSH key authentication).
In CLI variable initialization, provide both Windows and Linux image options, and clarify how to set admin credentials for Linux VMs.
Add a note or section explaining any differences or considerations when deploying Premium SSD v2 disks to Linux VMs.
Ensure that the 'Next steps' links to Linux documentation are clearly visible and referenced earlier in the workflow.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first

Summary

The documentation repeatedly references Windows Server Failover Cluster and links to Windows-specific clustering requirements, without mentioning Linux clustering solutions or their compatibility with Azure shared disks. The proximity placement groups section links to a Windows-specific URL, and no Linux equivalents or examples are provided. The focus on Windows clustering tools and documentation creates a Windows-first impression and omits Linux parity.

Recommendations

Add information about Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
Provide links to Linux documentation for proximity placement groups and disk sharing scenarios.
Clarify whether the listed limitations apply equally to Linux VMs and clustering solutions, or specify any Linux-specific differences.
Include examples or references for Linux users where relevant, especially in sections discussing clustering and disk sharing.

Create Pull Request

Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer without mentioning Linux/macOS alternatives or CLI equivalents. The example and tooling guidance assume Windows environments, creating friction for Linux/macOS users.

Recommendations

Add equivalent Azure CLI or REST API examples for bypassing Infrastructure Service.
Mention cross-platform tools or interfaces (e.g., Service Fabric CLI, REST endpoints) alongside Service Fabric Explorer.
Clarify whether the PowerShell command is required or if alternatives exist for Linux/macOS users.
Provide guidance or links for Linux/macOS users to perform the same operations.

Create Pull Request

Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation provides extensive PowerShell-based examples and references to Windows-specific tools (such as the Key Vault VM extension for Windows and S-channel), with no equivalent Linux/CLI/Bash examples or explicit mention of Linux-based certificate provisioning agents. The focus is on Windows-centric deployment and automation patterns, which may create friction for Linux users managing Service Fabric clusters.

Recommendations

Add equivalent Azure CLI and/or Bash examples for certificate enrollment and management, especially for Key Vault operations.
Document the availability (or lack thereof) of the Key Vault VM extension for Linux, and provide guidance for Linux-based provisioning agents if available.
Clarify any platform-specific limitations or differences in certificate management for Service Fabric clusters running on Linux nodes.
Where PowerShell is used, provide side-by-side Azure CLI or REST API equivalents.
Explicitly state if certain features (like S-channel or certificate linking) are Windows-only, and suggest Linux alternatives or workarounds.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides examples for configuring Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no equivalent Bash, Azure CLI, or Linux/macOS scripting examples. PowerShell is presented as the primary scripting option, which is Windows-centric. There is no explicit mention of Linux/macOS alternatives or cross-platform CLI tools, and PowerShell is referenced before any Linux-friendly tools in all relevant sections.

Recommendations

Add Azure CLI examples alongside PowerShell for all tasks (add, remove, scale, configure placement properties, etc.), as Azure CLI is cross-platform and widely used on Linux/macOS.
Explicitly mention that PowerShell Core is available cross-platform, or clarify if only Windows PowerShell is supported.
Consider including Bash script snippets or references for ARM template deployment using az CLI.
Where possible, note any limitations or differences for Linux/macOS users, especially if certain features are only available via PowerShell.
Review and update section ordering so that cross-platform tools (Azure CLI, ARM templates) are presented before Windows-specific tools (PowerShell).

Create Pull Request

Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides best practice examples and links primarily for Azure PowerShell, with PowerShell-based actions mentioned before Azure CLI or cross-platform alternatives. While Azure CLI and ARM templates are listed in a table, step-by-step examples and direct links in the best practices section focus on PowerShell, which may create friction for Linux/macOS users.

Recommendations

Add parallel Azure CLI examples and links for all PowerShell commands shown, especially for common tasks like deleting or restarting NodeTypes.
In the best practices section, mention Azure CLI and ARM templates alongside PowerShell, not after.
Where possible, provide code snippets or command references for both PowerShell and CLI in each example.
Clarify that Azure CLI and ARM templates are fully supported and cross-platform.

Create Pull Request

Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides only PowerShell-based command-line examples for critical migration steps, with no equivalent CLI, Bash, or Linux-native instructions. This creates friction for Linux/macOS users managing Service Fabric clusters, especially since Service Fabric supports both Windows and Linux node types. The ARM template examples are OS-neutral, but all imperative migration steps are shown using Windows PowerShell cmdlets.

Recommendations

Add equivalent Azure CLI (az) commands for all PowerShell examples, especially for resource deployment, node disabling, and resource cleanup.
Where possible, provide Bash script snippets or clear instructions for Linux/macOS users.
Explicitly note if any steps are only possible via PowerShell, and suggest alternatives or workarounds for non-Windows users.
Reference the Azure CLI documentation alongside PowerShell documentation for resource management tasks.

Create Pull Request

Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation covers Service Fabric application security in a generally platform-agnostic manner, but several sections show Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned without Linux equivalents or with Linux options listed second. Some example links and instructions (e.g., disk encryption, running services under accounts) are Windows-focused, and Linux guidance is sometimes missing or relegated to TODO comments.

Recommendations

Provide explicit Linux examples and instructions alongside Windows ones, especially for disk encryption, service account configuration, and certificate management.
Ensure Linux tools and patterns (e.g., Linux disk encryption, user/group management) are mentioned equally and not only as TODOs.
Where Windows-specific features are discussed (e.g., gMSA, BitLocker), clarify Linux alternatives or limitations.
Add links to Linux-focused documentation and examples where possible.
Review example ordering so Linux and Windows are presented with equal prominence.

Create Pull Request

Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation consistently uses PowerShell cmdlets (e.g., New-ServiceFabricService, Start-ServiceFabricApplicationUpgrade) for all command-line examples and workflows, with no mention of Linux/macOS equivalents such as Azure CLI, REST API, or Service Fabric CLI (sfctl). All concrete examples and guidance are PowerShell-centric, which may create friction for users managing Service Fabric clusters from Linux/macOS environments.

Recommendations

Add equivalent examples using Azure CLI (az sf), Service Fabric CLI (sfctl), or REST API where possible, especially for common operations like service creation, upgrades, and parameter changes.
Explicitly mention cross-platform tools and their usage alongside PowerShell, clarifying when certain operations are only possible via PowerShell.
Where PowerShell is required, note its availability on Linux/macOS and provide installation guidance or alternatives.
Include links to Linux/macOS-specific documentation or guides for Service Fabric management.

Create Pull Request

Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation references PowerShell cmdlets as the primary management interface for Service Fabric, and mentions Windows security as a transport option before X509 certificates. There are no explicit Linux or cross-platform management examples or tools mentioned, and PowerShell is presented as the default for provisioning and lifecycle management.

Recommendations

Explicitly mention cross-platform management tools (such as Azure CLI, REST APIs, or Service Fabric CLI) alongside PowerShell.
Clarify which management operations can be performed on Linux/macOS and provide corresponding examples.
Add references to Linux-compatible authentication mechanisms (e.g., X509 certificates) before or alongside Windows security.
Ensure that administrative APIs are described in a platform-neutral way, or provide links to Linux/macOS documentation.

Create Pull Request

Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation provides monitoring guidance for Azure Service Fabric clusters on both Windows and Linux, but there is a notable Windows bias. Windows-specific tools and patterns (e.g., EventStore APIs, Event Log/Event Viewer, Diagnostics Agent) are mentioned first or exclusively, while Linux equivalents are referenced later or less prominently. Some examples and tutorials focus on Windows/.NET, and Linux-specific guidance is often limited to links or brief notes. Linux users may need to consult additional pages for full parity, and some features (like EventStore APIs) are Windows-only.

Recommendations

Provide Linux-specific examples and step-by-step instructions alongside Windows examples, especially for cluster and infrastructure monitoring.
Ensure Linux configuration guidance (e.g., Syslog integration, LTTng event channels) is as detailed and prominent as Windows guidance.
Clarify which features are Windows-only and offer alternative approaches for Linux where possible.
Add sample queries and alert rules relevant to Linux clusters and containers.
Balance tutorial links and references so Linux users can easily find equivalent walkthroughs.

Create Pull Request

Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation page on RunToCompletion semantics for Service Fabric presents examples and guidance exclusively for Windows containers, referencing Windows-specific container images and command syntax. PowerShell is the only CLI tool mentioned for querying deployment status, and Windows tools/patterns (e.g., cmd, Windows container images) are used throughout. There are no Linux container examples or equivalent Linux tooling references, despite Service Fabric supporting Linux containers.

Recommendations

Add examples using Linux container images (e.g., Ubuntu or Alpine) and Linux shell commands.
Include instructions for querying deployment status using Linux CLI tools (such as sfctl or REST API).
Clarify in the introduction whether RunToCompletion semantics are supported on Linux, and provide parity guidance if so.
Present Windows and Linux examples side-by-side, or at least mention Linux equivalents where applicable.

Create Pull Request

Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first

Summary

The documentation contains a notable Windows bias in its guidance for validating manifest XML schemas. It exclusively recommends opening the schema file in Visual Studio at a Windows-specific path (C:\Program Files\...), with no mention of Linux/macOS equivalents or cross-platform tools. Additionally, the PowerShell module is referenced before any mention of cross-platform alternatives for service creation, though this is minor.

Recommendations

Provide instructions or examples for validating manifest XML schemas using cross-platform editors (e.g., VS Code with XML extensions) or command-line tools available on Linux/macOS.
Mention the location of the ServiceFabricServiceModel.xsd schema file on Linux clusters, or clarify if it is not available.
When referencing the Service Fabric PowerShell module, also mention cross-platform alternatives (such as Azure CLI or REST API) for service management, if available.
Consider reordering examples or providing parallel instructions for Linux/macOS users where applicable.

Create Pull Request

Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., PowerShell commands, .NET APIs) throughout critical lifecycle operations (deploy, upgrade, remove, cleanup). While REST API and .NET method alternatives are sometimes mentioned, Linux-friendly tools (such as Azure CLI or sfctl) are not referenced in the main procedural steps, and no Linux/macOS-specific examples or guidance are provided. PowerShell commands are often listed before REST API options, reinforcing a Windows-first bias.

Recommendations

Add examples and procedural steps using Azure CLI and sfctl for all major lifecycle operations (deploy, upgrade, remove, cleanup).
Explicitly mention Linux/macOS compatibility for REST API and CLI tools.
Where PowerShell is referenced, provide equivalent Linux/macOS command-line instructions (e.g., bash, sfctl, Azure CLI).
Reorder examples so that cross-platform tools (REST API, CLI) are listed before or alongside PowerShell.
Include a section or note clarifying which tools are available on Linux/macOS and how to perform common tasks without PowerShell.

Create Pull Request

Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides several critical operational examples (such as scaling in/out nodes) exclusively using PowerShell commands, with no equivalent Linux/bash/CLI examples. This creates friction for Linux users, who must translate PowerShell steps to their platform without guidance.

Recommendations

For every PowerShell command (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState), provide equivalent Azure CLI or Service Fabric CLI (sfctl) commands, or at least mention them.
Add explicit Linux/bash examples for common scaling workflows, or link to relevant Linux/CLI documentation.
Clarify in each section whether the steps are OS-agnostic or if there are differences for Linux clusters.
Where C# SDK examples are given, note if they are cross-platform, and if not, provide a Linux-compatible alternative or guidance.

Create Pull Request

Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation page for Service Fabric application upgrade presents PowerShell examples exclusively and references Windows-specific tools (e.g., http.sys, Windows HTTP Server API). There are no Linux or cross-platform CLI examples, and the upgrade process is described primarily in terms of Windows tooling and APIs. This creates friction for Linux/macOS users, as Service Fabric supports Linux clusters and the Azure CLI and REST APIs are available for cross-platform management.

Recommendations

Add equivalent examples using Azure CLI, REST API, or Service Fabric CLI (sfctl) for application upgrades, especially for retrieving and passing application parameters.
Clarify which features or steps are Windows-only (e.g., http.sys, Windows HTTP Server API) and provide Linux-specific guidance or alternatives where applicable.
Include notes or sections for Linux/macOS users, highlighting any differences in upgrade procedures or tooling.
Ensure that references to PowerShell or Windows tools are balanced with cross-platform options, or at least mention their existence.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first

Summary

The documentation page primarily references Windows-centric tools and patterns, such as Visual Studio and PowerShell, in the 'Next steps' section. Linux equivalents (e.g., CLI, Bash, cross-platform editors) are not mentioned, and PowerShell is presented as the only scripting example. The serialization guidance is focused on C# and .NET, which is cross-platform, but the upgrade workflow references Windows tools first and exclusively.

Recommendations

Add instructions or links for upgrading applications using Azure CLI or Bash scripts, which are cross-platform.
Mention cross-platform editors (e.g., VS Code) alongside Visual Studio for application upgrades.
Clarify if PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide Bash/CLI alternatives.
Ensure that Linux/macOS users are guided to equivalent workflows and tools for Service Fabric application upgrades.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation page for on-demand backup in Azure Service Fabric demonstrates notable Windows bias. All code examples use PowerShell, and the prerequisite is to install a PowerShell module. There are no examples or guidance for Linux/macOS users (e.g., Bash, curl, or cross-platform tools). The REST API is only shown via PowerShell, and Windows-centric tools are mentioned exclusively and first.

Recommendations

Add equivalent Bash/curl examples for REST API calls to support Linux/macOS users.
Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available or supported on PowerShell Core (pwsh) for Linux/macOS, or provide alternatives.
Mention cross-platform tools (such as Azure CLI or direct REST calls) where possible.
Include a note about Linux/macOS support and any limitations, if applicable.
Reorder sections or provide parallel examples so Linux/macOS users are not forced to adapt Windows-centric instructions.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation page for restoring backup in Azure Service Fabric exclusively uses PowerShell for all command-line examples and references the Microsoft.ServiceFabric.Powershell.Http module, which is a Windows-centric tool. No Linux/macOS CLI or REST API examples using cross-platform tools (such as curl or Azure CLI) are provided. All scripting and automation guidance assumes a Windows environment, creating friction for Linux/macOS users.

Recommendations

Add equivalent examples using cross-platform tools such as curl for REST API calls.
Provide Azure CLI examples where possible, as Azure CLI is supported on Windows, Linux, and macOS.
Clarify whether the PowerShell module is supported on PowerShell Core (pwsh) for Linux/macOS, and if so, provide installation and usage instructions for those platforms.
Include explicit guidance for Linux/macOS users, such as how to authenticate and make REST calls without PowerShell.
Mention any limitations or requirements for Linux/macOS environments if certain features are Windows-only.

Create Pull Request

Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

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 and examples (e.g., PowerShell, Windows Defender, Windows security baselines) are often presented first or exclusively. Windows-centric terminology and recommendations (such as Windows Defender and DSC) are included without Linux equivalents or alternatives. However, Linux-specific instructions are present for certificate creation and secret encryption, and links to Linux cluster creation are provided.

Recommendations

Where Windows-specific tools (e.g., PowerShell, Windows Defender, DSC) are mentioned, add equivalent Linux guidance or clarify if no Linux equivalent exists.
Present Windows and Linux examples side-by-side or in parallel sections, rather than Windows-first.
For sections like 'Windows security baselines' and 'Windows Defender', explicitly state if there are Linux alternatives (e.g., CIS Linux benchmarks, common Linux antimalware solutions) or clarify that these are Windows-only.
Ensure Linux-specific terminology and tools are referenced where appropriate (e.g., SELinux, AppArmor, Linux firewall tools).
Add links to Linux security best practices for Azure workloads where relevant.

Create Pull Request

Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation covers Service Fabric cluster settings for both Azure-hosted and standalone clusters. While the content is largely platform-neutral, there are several areas where Windows terminology and tools are referenced first or exclusively. For example, certificate store names default to "My" and store locations like "LocalMachine", which are Windows-centric. Some parameters reference Windows-specific concepts (e.g., NTLM authentication, Windows Defender Firewall, and Windows-only log file settings). Additionally, links and guidance for standalone clusters point to Windows Server documentation, with no explicit mention of Linux standalone clusters or parity for Linux tools and patterns.

Recommendations

Where certificate store names or locations are referenced, clarify Linux equivalents (e.g., file system paths, openssl usage, etc.).
Add explicit examples or guidance for Linux standalone clusters, including how to update ClusterConfig.json and perform configuration upgrades on Linux.
When referencing NTLM, Windows Defender Firewall, or other Windows-specific features, note their applicability and provide Linux alternatives or state if not supported.
Ensure that links and guidance for standalone clusters include Linux documentation or clarify if only Windows is supported.
Review default values and terminology (e.g., 'My', 'LocalMachine') and provide Linux equivalents where appropriate.

Create Pull Request

Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

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 REST API) are provided. The PowerShell examples are given alongside C# code, but there is no mention of how Linux users can perform these tasks, nor are Linux-friendly tools referenced. The documentation implicitly assumes Windows environments for operational tasks.

Recommendations

Add Azure CLI examples for configuring placement policies, as Azure CLI is cross-platform.
Mention REST API options for placement policy configuration, if available.
Clarify whether these PowerShell commands can be run on PowerShell Core (cross-platform) or only Windows PowerShell.
Provide guidance for Linux/macOS users on how to configure these policies without relying on Windows tools.
Consider including YAML or ARM template snippets if relevant for cross-platform deployment scenarios.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell examples are given equal prominence despite PowerShell being primarily a Windows tool. In the cluster upgrade section, only PowerShell commands are provided for manual upgrades, with no Linux/bash equivalents. Windows registry keys and Windows Update configuration are discussed without mentioning Linux alternatives or clarifying Linux applicability. Windows-specific configuration is described before Linux, and Windows tools are referenced more frequently.

Recommendations

Add bash or Linux shell equivalents for manual cluster upgrade commands (currently only PowerShell is shown).
Clarify which steps are Windows-only and provide Linux-specific guidance where applicable (e.g., for OS upgrades and update management).
When referencing Windows registry keys or Windows Update settings, explicitly state if these are not relevant for Linux clusters and provide Linux alternatives if available.
Ensure Linux examples are given equal prominence, not just linked in 'Next steps', but integrated throughout the documentation.
Consider adding a table or section summarizing differences between Windows and Linux cluster management for clarity.

Create Pull Request

Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page discusses Azure Service Fabric node types and their relationship to virtual machine scale sets. While it mentions both Windows and Linux node types in the extension configuration, there is a subtle bias toward Windows: the JSON snippet uses a Windows-style path ('D:\\SvcFab') for the 'dataPath' property, and the 'Next steps' section links to PowerShell scripts for changing RDP port ranges and admin credentials, which are Windows-specific tasks. No Linux-specific examples or guidance are provided for equivalent operations, and Windows terminology (RDP, PowerShell) appears without Linux alternatives.

Recommendations

Provide Linux-specific examples for 'dataPath' (e.g., '/var/svcfab') and clarify OS-specific configuration differences.
Add guidance or links for connecting to Linux nodes (e.g., SSH instructions) alongside RDP/PowerShell content.
Include Linux-focused scripts or documentation for changing admin credentials and port ranges.
Ensure that both 'ServiceFabricNode' (Windows) and 'ServiceFabricLinuxNode' (Linux) are equally represented in examples and explanations.

Create Pull Request

Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation page provides all command-line examples using PowerShell cmdlets (e.g., New-ServiceFabricApplication, Update-ServiceFabricApplication), which are Windows-specific tools. There are no equivalent examples for Linux/macOS environments (such as Azure CLI, REST API, or cross-platform Service Fabric tools). This creates friction for Linux users, as they cannot directly follow the examples unless they use Windows or adapt the instructions themselves.

Recommendations

Add Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform.
Include REST API sample requests for application creation, update, and querying load information.
Mention and link to any cross-platform Service Fabric management tools or SDKs.
Clarify which features are available on Linux clusters and note any Windows-only limitations.
Consider showing cross-platform examples before or alongside PowerShell examples.

Create Pull Request

Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

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 often presented first or exclusively, and the XML configuration is shown only for WindowsServer clusters, with no explicit Linux configuration example. PowerShell is the only CLI example given, with no Bash or Linux-native CLI equivalents. The documentation does not mention Linux node configuration or Linux-specific tools, even though Service Fabric supports Linux clusters.

Recommendations

Add explicit Linux cluster configuration examples, such as ClusterManifest.xml for Linux or relevant Linux-specific settings.
Provide Bash or Linux-native CLI examples alongside PowerShell, such as using sfctl (Service Fabric CLI) for service creation and updates.
Clarify that ClusterConfig.json and Template.json are cross-platform, and note any differences for Linux deployments.
Include guidance or links for Linux users on how to set up and manage Service Fabric clusters, node properties, and placement constraints.
Ensure that examples and explanations are not Windows-first; alternate or parallel Linux examples should be provided.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using Application Manifest, C# APIs, and PowerShell. However, all scripting examples are PowerShell-based, which is primarily a Windows tool. There are no equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API). Additionally, PowerShell examples are given equal prominence to C# and manifest examples, and there is no mention of cross-platform command-line alternatives. This creates friction for Linux users, especially since Service Fabric supports Linux containers and clusters.

Recommendations

Add Azure CLI or Bash script examples for configuring scaling policies, especially for Linux-based clusters.
Explicitly mention whether PowerShell examples are usable on Linux (e.g., via PowerShell Core), or provide guidance for Linux users.
Include REST API examples for scaling operations, which are platform-agnostic.
Clarify any platform-specific limitations in scripting or tooling, and provide links to Linux-specific documentation where relevant.

Create Pull Request

Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides both C# and PowerShell examples for managing Service Fabric metrics, but only PowerShell is shown for CLI-based operations. There are no Linux/macOS equivalents (such as Azure CLI or Bash examples), and PowerShell is presented as the primary scripting method, which may create friction for Linux/macOS users. The documentation does not mention cross-platform tools or alternatives, and PowerShell examples are given before any Linux-friendly options.

Recommendations

Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform and widely used on Linux/macOS.
Include Bash scripting examples where applicable, or reference REST API calls for metric management.
Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users.
Document any limitations or differences for Linux/macOS users in Service Fabric management.
Consider referencing Service Fabric SDK tools that are available for Linux/macOS, if relevant.

Create Pull Request

Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides a PowerShell example for querying Service Fabric partition health, using Windows-specific command syntax (PS C:\Users\User > Get-ServiceFabricPartitionHealth). No equivalent Linux/macOS CLI or REST API example is provided. The example is presented early in the page, potentially creating friction for non-Windows users. However, the rest of the documentation is platform-neutral, focusing on concepts and configuration files.

Recommendations

Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
Mention REST API alternatives for health queries, with example requests.
Clarify that PowerShell is one option, and provide links or references to cross-platform tools.
Where possible, show both Windows and Linux/macOS command examples side-by-side.

Create Pull Request

Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page on scaling Azure Service Fabric standalone clusters predominantly references Windows tools and PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without mentioning Linux equivalents or providing cross-platform guidance. There are no examples or instructions for Linux users, and the linked 'scale a standalone cluster' page appears to be Windows Server-focused, implying that Linux users may lack clear guidance for cluster scaling operations.

Recommendations

Include instructions and examples for scaling Service Fabric standalone clusters on Linux, if supported.
Mention and link to any Linux-specific tools or commands for cluster management.
Clarify whether standalone clusters can be managed on Linux, and if not, explicitly state Windows-only support.
Provide parity in documentation structure, ensuring Linux/macOS users can follow equivalent steps.
If PowerShell is required, note any cross-platform alternatives or limitations.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation provides PowerShell API examples for configuring service sensitivity and maximum load, but does not offer equivalent CLI or scripting examples for Linux/macOS users. It assumes the use of Windows-native tools (PowerShell, C# APIs) without mentioning cross-platform alternatives or clarifying platform requirements. This creates friction for Linux administrators managing Service Fabric clusters.

Recommendations

Clarify whether the PowerShell commands are supported on Linux/macOS (e.g., via PowerShell Core), or provide equivalent examples using Azure CLI, REST API, or other cross-platform tools.
Explicitly state any platform requirements for the Service Fabric management APIs.
Add guidance for Linux/macOS users on how to perform these tasks, including references to supported tools and workflows.
If only Windows tools are supported, clearly indicate this limitation to set user expectations.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page provides PowerShell examples for configuring move cost, but does not include equivalent Linux/bash/CLI examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. The C# examples are cross-platform, but the lack of Linux-native command-line instructions (such as Azure CLI or bash) means Linux users may struggle to perform basic operations without additional research.

Recommendations

Add Azure CLI or bash examples for creating and updating Service Fabric services with move cost settings.
Explicitly mention whether PowerShell Core (cross-platform) is supported, or provide guidance for Linux users.
Clarify if certain operations are only possible via PowerShell or C#, or provide links to Linux/macOS-compatible tools.
Consider adding a table or section comparing Windows and Linux approaches for service management.

Create Pull Request

Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page primarily discusses security scenarios for Azure Service Fabric clusters, but consistently references Windows Server for standalone clusters and omits explicit guidance or examples for standalone Linux clusters. Windows security (Kerberos) is described in detail, while Linux equivalents (such as certificate-based authentication or Linux user/group management) are not mentioned. Links and instructions for standalone clusters are exclusively for Windows, and certificate creation advice is Windows-centric (e.g., Windows Server certificate service, MakeCert.exe).

Recommendations

Add explicit guidance and examples for securing standalone Service Fabric clusters running on Linux, including certificate setup and client authentication.
Provide links to Linux-specific documentation or tools for certificate creation and management (e.g., OpenSSL).
Clarify whether standalone Linux clusters are supported and, if so, how their security setup differs from Windows clusters.
Balance references to Windows tools (like MakeCert.exe) with Linux alternatives (such as OpenSSL or certbot).
Include Linux user/group-based authentication options if available, or explicitly state if only certificate-based authentication is supported for Linux.

Create Pull Request

Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

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 (e.g., Bash, Azure CLI) examples. Windows tools and patterns (PowerShell, ApplicationManifest.xml in Visual Studio) are mentioned before Linux alternatives, and Linux-specific limitations are highlighted without guidance or parity. There are no Linux-specific walkthroughs for enabling DNS service or managing DNS names, and portal-based instructions are Windows-centric.

Recommendations

Add Azure CLI or Bash examples for managing Service Fabric services and setting DNS names, especially for Linux clusters.
Clarify how Linux users can set DNS names (e.g., via ARM templates, Azure CLI, or other supported methods).
Provide explicit instructions and examples for enabling DNS service on Linux clusters, including workarounds for portal limitations.
Mention Linux-compatible editors and workflows when referencing ApplicationManifest.xml (e.g., VS Code, nano, vim).
Ensure that Linux limitations are accompanied by actionable alternatives or links to relevant Linux documentation.

Create Pull Request

Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page exhibits mild Windows bias. It references Windows directory paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd'), and mentions Visual Studio as a packaging tool without listing Linux alternatives or command-line options. There are no explicit Linux/macOS examples or instructions, and the directory structure and file naming conventions are Windows-centric. However, the content does not restrict the guidance to Windows-only features, and Service Fabric itself supports Linux clusters.

Recommendations

Add explicit Linux/macOS instructions and examples for packaging and deploying guest executables.
Mention cross-platform tools (such as Azure CLI or Service Fabric CLI) and provide sample commands for Linux/macOS.
Reference Linux file paths and installation locations for the Service Fabric SDK and schema files.
Clarify that guest executables can be packaged and deployed from Linux/macOS environments, not just Windows/Visual Studio.

Create Pull Request

Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page provides code examples and administrative instructions primarily in PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or scripting examples (e.g., Bash, Azure CLI) for scaling Service Fabric services. Windows tools (PowerShell cmdlets) are mentioned first and exclusively, creating friction for Linux users who may need to perform similar tasks. The only explicit mention of Linux is in the platform comparison section, but it does not provide Linux-specific operational guidance.

Recommendations

Add Linux-friendly examples using Bash scripts or Azure CLI commands for scaling operations.
Mention and link to Linux-specific Service Fabric management tools and documentation.
Where PowerShell cmdlets are referenced, provide equivalent Azure CLI or REST API examples for cross-platform parity.
Clarify which operations are supported on Linux clusters and provide guidance for Linux users.
Consider restructuring examples so that Windows and Linux approaches are presented side-by-side.

Create Pull Request

Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

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 is a notable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) and processes are often mentioned first or exclusively, and several examples reference Windows executables and services. Linux equivalents are sometimes referenced, but often after Windows or in less detail. Some sections (e.g., standalone clusters) are Windows-only, with Linux support explicitly noted as unavailable. CLI tools and REST APIs are mentioned, but PowerShell is frequently highlighted. There are few explicit Linux command examples or Linux-centric workflows.

Recommendations

Ensure Linux and cross-platform examples are provided alongside Windows/PowerShell examples, especially for cluster management and health monitoring.
Mention Linux CLI tools (e.g., sfctl) and workflows before or alongside Windows tools.
Add explicit Linux instructions or links for tasks where Linux is supported (e.g., cluster creation, application lifecycle).
Clarify when a feature or example is Windows-only, and provide Linux alternatives or workarounds where possible.
Balance references to Visual Studio with Linux-friendly IDEs or command-line approaches.

Create Pull Request

Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric supports cross-platform management, the exclusive use of PowerShell creates friction for non-Windows users.

Recommendations

Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS.
Include REST API sample requests for health reporting and querying.
Mention cross-platform tools and clarify which methods are available on all OSes.
Ensure examples for health reporting and querying are shown for both Windows (PowerShell) and Linux/macOS (CLI/REST).

Create Pull Request

Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation provides PowerShell-based examples and references for managing Service Fabric services, with no equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). All command-line instructions and links are PowerShell-centric, which may create friction for users on non-Windows platforms.

Recommendations

Add Azure CLI or REST API command examples for creating and managing services, especially for operations currently shown only with PowerShell.
Clarify in each example whether the command is Windows-only, and provide platform-agnostic alternatives where possible.
Reference cross-platform tools (e.g., Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
Add a note or section summarizing cross-platform management options for Service Fabric clusters.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates notable Windows bias. All command-line/API examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica), with no mention of Linux equivalents or cross-platform CLI usage. The administrative workflow is described primarily in terms of PowerShell and Windows tooling, and Windows-specific terminology is used throughout. There are no examples or guidance for Linux/macOS users, nor are FabricClient API usage patterns shown in a cross-platform context.

Recommendations

Add examples for managing replica soft delete using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
Document how to use FabricClient APIs in .NET Core or other cross-platform languages, including sample code for Linux/macOS environments.
Clarify whether the PowerShell cmdlets are available or supported on Linux (via PowerShell Core), or provide alternative instructions if not.
Include explicit notes or sections for Linux/macOS users, highlighting any differences or limitations.
Where possible, show Linux commands and configuration file edits alongside Windows/PowerShell examples.

Create Pull Request

Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation references PowerShell as the primary example for interacting with Service Fabric clusters and retrieving the cluster manifest. It mentions Visual Studio (a Windows-centric tool) for publishing to Azure, and links to PowerShell-based deployment guidance as the main 'Next steps'. While REST and .NET are briefly mentioned, Linux-native tools and workflows (such as Azure CLI or Bash) are absent. The examples and guidance are Windows-first, creating friction for Linux/macOS users.

Recommendations

Add Azure CLI examples for retrieving the cluster manifest and deploying applications.
Include Bash or cross-platform scripting examples alongside PowerShell.
Mention Linux/macOS-compatible tools for Service Fabric management.
Provide guidance for deploying from non-Windows environments (e.g., VS Code, CLI).
Ensure 'Next steps' links include Linux-friendly options, not just PowerShell.

Create Pull Request

Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

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 in Azure Service Fabric. However, there is a notable Windows bias in several sections: HTTP.sys (a Windows-only technology) is discussed in depth, with explicit mention of Windows tools (netsh), Windows kernel drivers, and Windows-specific endpoint configuration. HTTP.sys examples and explanations are presented before Kestrel in some sections, and Windows-specific configuration steps (such as URL reservation and endpoint setup) are detailed. While Kestrel is recommended for Linux and cross-platform scenarios, the prominence and depth of Windows-specific HTTP.sys content may create friction for Linux/macOS users. PowerShell or Windows command-line tools are referenced for endpoint management, but Linux equivalents are not provided.

Recommendations

Clearly mark HTTP.sys sections as Windows-only and direct Linux/macOS users to Kestrel sections.
Move Kestrel (cross-platform) examples and explanations before HTTP.sys (Windows-only) in each relevant section.
Provide explicit guidance for Linux/macOS users, including any necessary Service Fabric configuration steps for Kestrel on those platforms.
Avoid referencing Windows tools (such as netsh) without mentioning that they are not applicable to Linux/macOS.
Add a summary table or section early in the document clarifying which features are Windows-only and which are cross-platform.
Ensure all code samples for service communication are available for both Kestrel and HTTP.sys, with clear platform applicability.

Create Pull Request

Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page provides detailed examples for reporting Service Fabric health using C# APIs and PowerShell, with all command-line examples shown in PowerShell and Windows-style prompts. There are no equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI, or cross-platform PowerShell Core), and the PowerShell examples use Windows-specific syntax and paths. REST is mentioned but not exemplified. This creates friction for Linux/macOS users, who may not have access to Windows PowerShell or may use different tools.

Recommendations

Add equivalent examples using Bash or Azure CLI for Linux/macOS users where possible.
Clarify whether PowerShell Core (pwsh) is supported cross-platform, and if so, provide examples using it with non-Windows prompts.
Provide explicit REST API request examples (e.g., using curl) to demonstrate a fully cross-platform approach.
Note any platform-specific requirements or limitations for Service Fabric management tools.
Where possible, use neutral prompts (e.g., $ or #) or clarify that commands are not Windows-specific.

Create Pull Request

Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation focuses exclusively on Visual Studio workflows (Build/Rebuild/F5/Ctrl+F5/Publish) and references PowerShell cmdlets for service creation, both of which are Windows-centric. There are no examples or guidance for Linux/macOS users, nor any mention of cross-platform tooling or workflows for Service Fabric application configuration. The documentation assumes the use of Visual Studio, which is primarily available on Windows, and does not provide alternative instructions for Linux/macOS environments.

Recommendations

Add explicit guidance for Linux/macOS users, including how to configure and deploy Service Fabric applications without Visual Studio.
Provide CLI-based examples (using Azure CLI or cross-platform PowerShell Core) for managing StartupServices.xml and ApplicationManifest.xml.
Clarify whether StartupServices.xml workflows are supported or possible on Linux/macOS, and if not, provide alternatives.
Mention any cross-platform tools or editors that can be used for editing manifest files and deploying Service Fabric applications.
If the feature is Windows-only, state this clearly at the top of the documentation.

Create Pull Request

Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

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 is a subtle Windows bias in the 'Node' section, where Windows-specific tools and executables (FabricHost.exe, Fabric.exe, FabricGateway.exe) are described as auto-start Windows services, with no mention of Linux equivalents or how nodes operate on Linux. Windows terminology and patterns are presented first or exclusively in some places, such as referencing EXE/DLL files and Windows services, while Linux-specific details are missing or less prominent.

Recommendations

Add explicit descriptions of how Service Fabric nodes operate on Linux, including any differences in service management, process startup, and relevant Linux tools or patterns.
When referencing executable files, clarify that Linux deployments use ELF binaries and describe any differences in packaging or execution.
Ensure that examples and terminology are presented in a platform-neutral way, or provide parallel Linux-specific examples and explanations where Windows-specific terms are used.
Mention Linux service management (e.g., systemd) where Windows services are discussed, to help Linux users understand equivalent concepts.

Create Pull Request

Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

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 upgrade instructions reference Windows tools, with no mention of Linux/macOS equivalents or cross-platform CLI options. Linux users are not provided with guidance or examples for performing upgrades, creating friction for non-Windows environments.

Recommendations

Add instructions and examples for upgrading Service Fabric applications using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
Include guidance for configuring upgrade parameters and health policies without Visual Studio, such as editing manifest files and deploying via CLI.
Mention any limitations or differences for Linux/macOS users, and provide links to relevant documentation for non-Windows environments.
Present PowerShell and Visual Studio instructions alongside (not before) cross-platform alternatives to ensure parity.

Create Pull Request

Virtual Machine Scale Sets Automatic OS image upgrades with Azure Virtual Machine Scale Sets ...e-sets/virtual-machine-scale-sets-automatic-upgrade.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation covers both Windows and Linux VM Scale Sets, but there is a notable Windows bias in example ordering, tool references, and template defaults. PowerShell examples are prominent and shown before Azure CLI, and ARM/Bicep template snippets default to Windows images. Linux-specific examples, troubleshooting, and considerations are less visible or missing.

Recommendations

Alternate the order of PowerShell and Azure CLI examples, or show CLI first for parity.
Provide ARM/Bicep template snippets with Linux image defaults (e.g., Ubuntu) alongside Windows examples.
Add explicit Linux troubleshooting notes where Windows-specific guidance is given (e.g., drive letter reassignment).
Ensure all example commands (PowerShell, CLI, REST) are shown for both Windows and Linux scenarios.
Clarify that all features and steps apply equally to Linux, and highlight any Linux-specific requirements or caveats.
Add links to Linux-specific documentation or best practices where relevant.

Create Pull Request

Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first

Summary

The documentation page provides Service Fabric manifest XML examples that are platform-agnostic, but when it comes to deployment and parameterization, it only shows PowerShell (Windows) commands (e.g., New-ServiceFabricApplication) and references Windows file paths for the schema. Linux equivalents (such as Azure CLI or sfctl) are not mentioned, and the PowerShell example is given without Linux parity. The documentation also references the Service Fabric SDK schema path using a Windows directory, with only a brief note about the Linux certificate store location.

Recommendations

Add equivalent Linux/macOS deployment examples using Azure CLI (az sf application create) or sfctl.
When referencing file paths (such as the Service Fabric SDK schema), provide both Windows and Linux paths.
If showing PowerShell examples, always follow with Linux/macOS equivalents or a note linking to cross-platform instructions.
Clarify any platform-specific behaviors, such as certificate store handling, in all relevant sections.

Create Pull Request

Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation provides both Linux and Windows examples for configuring custom metrics and the application health extension on Azure Virtual Machine Scale Sets. However, there is evidence of Windows bias: PowerShell examples are often given equal or greater prominence than Bash/Linux examples, and Windows-specific extension types (e.g., ApplicationHealthWindows) are shown first or exclusively in some code snippets. PowerShell and Windows tools are referenced throughout, sometimes before their Linux equivalents. The REST API and Azure CLI examples are platform-neutral, but the PowerShell sections are detailed and prominent.

Recommendations

Ensure Linux and Bash examples are presented before or alongside Windows/PowerShell examples in each section.
Where extension types are shown (e.g., ApplicationHealthWindows vs ApplicationHealthLinux), clarify both options and show Linux as the default or first example when possible.
Expand Bash/Linux scripting examples to match the detail and completeness of PowerShell examples.
Add explicit notes or tables clarifying parity between Windows and Linux extension types and commands.
Review sample outputs and code snippets to ensure Linux is equally represented and not overshadowed by Windows-specific content.

Create Pull Request

Virtual Machines Benchmark your application on Azure Disk Storage ...lob/main/articles/virtual-machines/disks-benchmarks.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation mentions both Windows and Linux VMs are supported and introduces DiskSpd (Windows) and FIO (Linux) as benchmarking tools. However, DiskSpd (Windows) is mentioned first, and the overall tone and example setup (e.g., host caching terminology) may be more familiar to Windows users. There is no explicit Linux example or command shown, and the inclusion of PowerShell/Windows terminology is slightly more prominent.

Recommendations

Provide explicit Linux command examples using FIO, alongside Windows DiskSpd examples.
Ensure Linux terminology and disk configuration steps are equally described (e.g., how to stripe disks and set caching on Linux).
Alternate the order of tool presentation or clarify parity between Windows and Linux throughout.
Add links or references to Linux-specific documentation for disk management and benchmarking.

Create Pull Request

Virtual Machines Deploy a ZRS managed disk ...lob/main/articles/virtual-machines/disks-deploy-zrs.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides both Azure CLI and Azure PowerShell examples for deploying ZRS managed disks, but PowerShell (a Windows-centric tool) is heavily featured, especially in the Resource Manager Template section and for feature registration. PowerShell examples are more verbose and detailed, and some critical steps (like feature registration) are only shown in PowerShell. Additionally, the Resource Manager Template examples use PowerShell for deployment, with no equivalent Bash or cross-platform scripting shown. The PowerShell examples use Windows VM images and Windows-specific parameters, while CLI examples use Ubuntu images, but the PowerShell sections are more prominent and detailed.

Recommendations

Add Bash or cross-platform shell examples for feature registration and Resource Manager Template deployment (e.g., using Azure CLI or ARM template deployment via CLI).
Provide parity in example detail for Azure CLI and PowerShell, ensuring that Linux/macOS users can follow all steps without switching to PowerShell.
Clearly indicate that PowerShell examples are for Windows users and provide alternative instructions for Linux/macOS users where possible.
Include examples for deploying Windows and Linux VMs in both CLI and PowerShell sections to avoid implicit OS bias.

Create Pull Request

Virtual Machines Ultra Disks for VMs - Azure Managed Disks ...in/articles/virtual-machines/disks-enable-ultra-ssd.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and PowerShell examples for deploying and managing Ultra Disks, but all VM creation examples use Windows VM images (e.g., Win2016Datacenter) and do not show Linux equivalents. PowerShell examples are prominent, and there are no Linux-specific instructions or examples for attaching, formatting, or using Ultra Disks. This creates friction for Linux users, who must adapt Windows-centric examples to their needs.

Recommendations

Add Linux VM image examples (e.g., --image UbuntuLTS) alongside or in place of Windows images in Azure CLI and PowerShell commands.
Include Linux-specific instructions for partitioning, formatting, and mounting Ultra Disks after attachment.
Where PowerShell is used, provide equivalent Bash or shell scripting examples for Linux users.
Explicitly state that the examples apply to both Linux and Windows, and clarify any OS-specific differences.
In the portal instructions, link to both Linux and Windows VM creation quickstarts, not just the Windows one.

Create Pull Request

Virtual Machines Azure Write Accelerator ...es/virtual-machines/how-to-enable-write-accelerator.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first

Summary

The documentation is generally cross-platform and explicitly states applicability to both Linux and Windows VMs. Most command-line instructions are provided for both Azure PowerShell (which is cross-platform but Windows-centric in usage and syntax) and Azure CLI (which is cross-platform). However, the REST API section instructs users to install 'armclient' via Chocolatey, a Windows-only package manager, and provides installation steps only for Windows (cmd.exe and PowerShell), with no mention of Linux/macOS alternatives. Additionally, PowerShell-based instructions and examples are presented before CLI examples, which may create a slight 'Windows-first' impression.

Recommendations

For the REST API/armclient section, provide installation instructions for Linux/macOS users, such as using .NET Core global tools, manual download, or alternative package managers (e.g., Homebrew for macOS, apt/yum for Linux), or clarify if armclient is Windows-only.
Where possible, present Azure CLI examples before or alongside PowerShell examples, as CLI is more universally cross-platform and familiar to Linux/macOS users.
Explicitly state that PowerShell Core (pwsh) is available on Linux/macOS if those examples are intended to be cross-platform.
Consider mentioning or linking to alternative REST API tooling (e.g., curl, Postman, or az rest) that works natively on all platforms.
Add a note clarifying that Chocolatey is Windows-only and provide equivalent Linux/macOS installation steps or alternatives.

Create Pull Request

Virtual Machines Create an encrypted image version with customer-managed keys .../articles/virtual-machines/image-version-encryption.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides both PowerShell and Azure CLI examples, but PowerShell (a Windows-centric tool) is presented first and in greater detail, with more verbose and step-by-step scripting. References to enabling customer-managed keys and double encryption in the prerequisites link to PowerShell guides before CLI or Linux-native alternatives. There is also a reference to the Windows-specific Cryptography API: Next Generation for cryptographic modules. However, Azure CLI (cross-platform) examples are present and complete, and the feature itself is not Windows-only.

Recommendations

Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
Ensure all prerequisite links include Azure CLI or REST API options, not just PowerShell and portal.
Reference cross-platform cryptography documentation (such as Azure Key Vault or Managed Disks general docs) rather than Windows-specific APIs.
Clarify that PowerShell examples can be run on Linux/macOS using Azure PowerShell Core, if applicable.
Add explicit notes or links for Linux/macOS users where workflows or commands may differ.

Create Pull Request

Virtual Machines Customer intent: As a cloud administrator, I want to expand virtual machine disks efficiently, so that I can manage storage capacity without downtime and ensure optimal performance in my infrastructure. ...al-machines-disks-expand-without-downtime-restrictions.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation mentions Azure PowerShell and Windows rescan functions prominently, and provides links to Windows-specific tools and procedures. While Linux is referenced, Linux-specific examples or commands are not provided directly in the text, and Windows tools are mentioned before Linux equivalents. The Azure CLI is listed, but PowerShell is emphasized, and Linux disk expansion steps are only linked, not described.

Recommendations

Provide explicit Linux command-line examples (e.g., using Azure CLI and Linux disk rescan commands) alongside Windows/PowerShell examples.
Mention Linux tools and procedures with equal prominence to Windows tools.
Ensure Linux disk expansion steps are described in the documentation, not just linked.
List Azure CLI and Linux options before or alongside PowerShell and Windows options to avoid 'windows_first' bias.

Create Pull Request

Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation, while focused on Ubuntu Linux VHD creation for Azure, frequently references Windows-specific tools (Hyper-V, Convert-VHD PowerShell cmdlet) and provides Windows-centric instructions (e.g., Hyper-V Manager steps) without offering Linux-native alternatives or mentioning Linux tools first. Linux users may struggle to find equivalent guidance for creating or converting VHDs, as the documentation assumes Windows as the primary platform for virtualization and disk conversion.

Recommendations

Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VirtualBox, KVM).
Mention Linux alternatives to Hyper-V and PowerShell (such as qemu-img for disk conversion, virt-manager for VM creation).
Provide step-by-step examples for extracting, preparing, and converting VHDs on Linux systems, not just referencing Windows/Hyper-V.
Reorder sections to present Linux-native workflows first, or at least in parallel with Windows options.
Clarify that Hyper-V and Convert-VHD are Windows-specific, and link to Linux-focused guides where possible.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides a Windows-centric AzCopy example (using AzCopy.exe and Windows file paths) for uploading a VHD, but does not offer a Linux/macOS equivalent. The AzCopy command is shown only in Windows syntax, and the file path example uses Windows conventions. There is no explicit Linux/macOS AzCopy command or mention of how to run AzCopy on those platforms, despite the page targeting both Linux and Windows VMs. The rest of the CLI commands are cross-platform, but the critical upload step is Windows-biased.

Recommendations

Add a Linux/macOS AzCopy example, e.g., 'azcopy copy "/home/user/mydisk.vhd" "sas-URI" --blob-type PageBlob'
Mention that AzCopy is available for Linux/macOS and provide installation instructions or a link for those platforms.
Clarify file path conventions for both Windows and Linux/macOS users.
Consider showing both Windows and Linux/macOS AzCopy commands side-by-side for parity.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation is focused on running scripts in Linux VMs using Azure managed Run Commands. While the primary examples are for Linux (shell scripts), there is notable bias in the tooling and example ordering: PowerShell cmdlets (Set-AzVMRunCommand, Get-AzVMRunCommand, etc.) are heavily featured, and Windows-specific tools (PowerShell, New-AzStorageBlobSASToken) are referenced throughout. In several sections, PowerShell examples are given equal or greater prominence than Azure CLI, despite CLI being more native to Linux. REST API and ARM template examples sometimes use Windows-style scripts (e.g., Write-Host, .ps1 files) or reference Windows-specific command IDs (ipconfig), and Windows-specific notes are interspersed in Linux-focused sections. The documentation assumes familiarity with PowerShell tooling for tasks like generating SAS tokens, which may create friction for Linux users.

Recommendations

Provide Azure CLI examples for all tasks where PowerShell examples are given, especially for SAS token generation and blob operations.
Ensure that shell script examples (.sh) are used in REST API and ARM template sections, not PowerShell (.ps1), unless explicitly discussing Windows.
Clarify when a command or tool is Windows-only, and provide Linux alternatives or note Linux limitations.
Reorder examples so that Azure CLI (or Bash) is presented before PowerShell in Linux-focused documentation.
Add guidance for Linux-native tools (e.g., azcopy, Azure CLI) for blob SAS token generation and management.

Create Pull Request

Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation mentions both Windows and Linux environments for Azure Service Fabric, and provides parity in describing development tools for each. However, Windows development is mentioned first, with references to Visual Studio and PowerShell, while Linux development is described second, with Eclipse and Yeoman. No explicit Linux bias or missing Linux examples are present, but the ordering may subtly prioritize Windows.

Recommendations

Alternate the order in which Windows and Linux development environments are presented, or present them together in a neutral way.
Ensure quickstart and linked guides provide Linux examples and are equally accessible from the overview.
Explicitly mention cross-platform support in introductory sections to reinforce parity.

Create Pull Request

Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell examples are often presented before CLI examples, and some sections (such as querying public IPs) give more detailed PowerShell usage. There is a slight preference for Windows/PowerShell tools and patterns, but Linux parity is generally maintained via CLI and ARM template examples.

Recommendations

Ensure CLI examples are always provided alongside PowerShell, especially for querying and managing resources.
Present CLI and PowerShell examples in parallel (side-by-side tabs) or alternate their order to avoid implicit Windows-first bias.
Expand CLI examples where PowerShell examples are more detailed, such as querying public IPs.
Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
Consider adding bash scripting examples for common Linux workflows where appropriate.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, in several sections, Windows/Hyper-V tools and workflows are mentioned first or given prominence (e.g., Hyper-V Manager, convert-vhd cmdlet), before Linux-native alternatives. Linux workflows are fully documented, but Windows/Hyper-V is often presented as the primary or default option.

Recommendations

Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before Hyper-V/Windows tools, or at least equally.
When mentioning disk conversion tools, list Linux-native options (qemu-img, VirtualBox) before Windows tools (Hyper-V Manager, convert-vhd).
Clarify that Hyper-V steps are only required if using Windows as the host, and highlight Linux-native workflows for users on Linux/macOS.
Ensure that references to PowerShell or Windows tools are always accompanied by Linux equivalents, and that Linux instructions are not dependent on Windows tooling.

Create Pull Request

Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy

Summary

The documentation provides a thorough overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits mild Windows bias. Windows-specific terminology, tools, and patterns (e.g., certificate store paths like 'LocalMachine\My', references to Win32 CryptoAPI, and event log locations) are mentioned first or exclusively, with Linux equivalents sometimes referenced parenthetically or not at all. Troubleshooting and configuration examples focus on Windows paths and APIs, and PowerShell/C++ error codes are used without Linux-specific guidance.

Recommendations

Ensure Linux certificate store paths (e.g., /var/lib/sfcerts) are mentioned equally and clearly alongside Windows paths in all relevant sections.
Add troubleshooting guidance for Linux clusters, including log locations and commands for certificate validation (e.g., using openssl, journalctl, or systemd logs).
Where Windows APIs (e.g., CertGetCertificateChain) are referenced, provide Linux equivalents or clarify how Service Fabric handles certificate validation on Linux.
Include Linux-specific error codes, symptoms, and remediation steps in troubleshooting sections.
Present examples and configuration snippets for both Windows and Linux environments, not just Windows-first.

Create Pull Request

Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page for Azure Service Fabric container image management shows mild Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned as default exclusions, and no Linux container image examples or references are provided. The examples and descriptions focus on Windows images and do not mention Linux container management or provide Linux-specific guidance.

Recommendations

Add examples referencing common Linux container images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the 'ContainerImagesToSkip' setting.
Clarify whether the cleanup and management features apply equally to Linux containers, and if there are any differences in behavior or configuration.
Include notes or examples for Linux-based Service Fabric clusters, if supported.
Explicitly state if the feature set is Windows-only, or provide parity guidance for Linux users.

Create Pull Request

Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools ⚠️ minor_missing_linux_example

Summary

The documentation provides networking best practices for Azure Service Fabric clusters and covers both Windows and Linux scenarios. However, there is a mild bias toward Windows: PowerShell is referenced as the primary API client, Windows-specific tools and examples (like netsh) are mentioned, and Windows container scenarios are described in more detail. Linux equivalents (such as CLI commands or Linux container networking) are less prominent or missing. Windows examples and terminology often appear first or exclusively, especially in sections about API access and application networking.

Recommendations

Add Linux CLI (az CLI) examples alongside PowerShell references, especially for client API access.
Include Linux-specific commands for checking dynamic port ranges (e.g., 'ss', 'lsof', or '/proc/net/tcp') instead of only referencing 'netsh'.
Expand application networking guidance to cover Linux container workloads and networking modes, not just Windows containers.
Balance references to Windows and Linux in tables and explanations, ensuring Linux scenarios are equally described.
Where possible, provide links to Linux-focused ARM templates and sample deployments.

Create Pull Request

Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows, but there are minor signs of Windows bias. Windows container runtimes and tools (Mirantis, DockerEE) are listed in more detail than Linux, and Windows scenarios (IIS lift and shift) are described first in the 'Scenarios for using containers' section. However, Linux examples and tutorials are present and referenced throughout.

Recommendations

Ensure Linux and Windows examples are presented in parallel, rather than Windows scenarios being listed first.
Expand Linux-specific scenarios (e.g., Apache, NGINX, Python workloads) to match the detail given to Windows/IIS examples.
Provide more detail on Linux container runtimes and tools, similar to the Windows section.
Where possible, alternate the order of Linux and Windows links/examples to avoid 'windows_first' bias.

Create Pull Request

Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

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 (a Windows-centric tool) is presented first and in greater detail, with more explanation and command coverage. The CLI section is present and functional for Linux/macOS users, but appears secondary.

Recommendations

Present the Azure Service Fabric CLI (sfctl) examples before PowerShell, or clarify that sfctl is cross-platform and recommended for Linux/macOS users.
Explicitly state which tools are available on which platforms at the start of the 'Deploy a Docker Compose file' section.
Ensure that all PowerShell commands have direct sfctl equivalents shown, and vice versa, to reinforce parity.
Add a note highlighting that sfctl is the preferred method for non-Windows environments.

Create Pull Request

Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides examples for managing Service Fabric application parameters across environments. It mentions PowerShell and Visual Studio (both Windows-centric tools) first and in detail, while Linux/macOS equivalents (sfctl, install.sh) are mentioned but with less prominence and detail. There is a slight bias toward Windows tools and workflows, though Linux options are referenced.

Recommendations

Provide equally detailed examples for Linux/macOS workflows, such as using sfctl and install.sh.
List Linux/macOS tools and commands before or alongside Windows tools to avoid 'windows_first' bias.
Expand on how Jenkins (a cross-platform tool) can be used for parameter substitution, including sample scripts.
Clarify which tools are cross-platform and which are Windows-only, so users can easily identify their options.

Create Pull Request

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

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation page provides Service Fabric application and service manifest examples, but exhibits mild Windows bias. Windows-specific terminology (e.g., 'NetworkService', 'Administrators', 'Setup.bat', 'VotingWeb.exe') is used throughout, and references to running scripts (e.g., 'Setup.bat') and executables (.exe) are Windows-centric. The only mention of tooling is the 'ServiceFabric PowerShell module', with no Linux CLI or cross-platform alternatives referenced. There are no explicit Linux/macOS examples or notes about cross-platform support.

Recommendations

Add examples or notes for Linux deployments, such as using shell scripts (.sh) instead of batch files (.bat) and referencing Linux user/group equivalents.
Mention cross-platform tools (e.g., Azure CLI, sfctl) alongside PowerShell, and provide example commands for Linux/macOS.
Clarify which features are Windows-only and which are supported on Linux clusters, especially around user accounts and security principals.
Include guidance for running .NET Core apps on Linux Service Fabric clusters, if supported.
Where possible, use neutral terminology (e.g., 'service executable') and provide both Windows and Linux file formats in examples.

Create Pull Request

Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation page demonstrates a mild Windows bias. The manifest examples and explanations are based on the 'Windows Server 2016 Container Sample', and Windows-specific tools and patterns (such as referencing 'winver' to get the OS build version) are mentioned before or instead of their Linux equivalents. However, the documentation does acknowledge Linux in places (e.g., certificate handling), and the manifest XML itself is largely cross-platform. There are no PowerShell-heavy sections or critical omissions of Linux examples, but the overall framing and some instructions assume a Windows-first context.

Recommendations

Include or reference parallel Linux-based manifest samples, or clarify which elements are cross-platform and which are Windows-specific.
When mentioning Windows tools (e.g., 'winver'), also mention the Linux equivalent (e.g., 'cat /etc/os-release' or 'uname -r') for determining OS version.
Explicitly state which manifest features or XML elements are supported on Linux clusters, and highlight any differences.
If possible, provide links to Linux container samples or documentation alongside the Windows sample reference.

Create Pull Request

Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation provides code examples and references that are primarily .NET/C#-centric, which is common for Service Fabric, but does not show Linux-specific patterns or alternatives. In the 'Next steps' section, Windows tools (Visual Studio, PowerShell) are mentioned before any Linux-friendly options, and there are no explicit Linux/macOS examples or CLI alternatives provided.

Recommendations

Add examples or notes for Linux/macOS users, such as using the Azure CLI or Service Fabric CLI (sfctl) for application upgrades.
Mention cross-platform development environments (e.g., Visual Studio Code) alongside Visual Studio.
Clarify if the serialization APIs and patterns are equally supported on Linux Service Fabric clusters, and provide any relevant differences.
Reorder 'Next steps' to avoid always listing Windows tools first, or group by platform.

Create Pull Request

Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

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 CLI examples, and in some sections (such as feature registration), the PowerShell tab appears after CLI but before REST API. The PowerShell examples reference Windows-specific extension types (e.g., ApplicationHealthWindows), while the CLI examples use ApplicationHealthLinux. Portal instructions are platform-neutral, but PowerShell is a Windows-centric tool, and its presence may suggest Windows bias. REST API instructions are included, but Linux-specific guidance (e.g., Bash scripting, Linux-native tools) is not provided. The CLI examples use Ubuntu images, which is positive for Linux parity.

Recommendations

Ensure that PowerShell examples are clearly marked as Windows-only and that Linux/macOS users are directed to Azure CLI or REST API.
Provide Bash or shell script examples for Linux/macOS users where relevant.
Clarify in the PowerShell section that it is primarily for Windows users, and recommend Azure CLI for cross-platform scenarios.
Expand documentation to include troubleshooting or extension configuration for both Windows and Linux VMSS instances (e.g., ApplicationHealthWindows vs ApplicationHealthLinux).
Consider listing Azure CLI examples before PowerShell to reinforce cross-platform parity.

Create Pull Request

Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and Azure PowerShell examples for all operations (attach, detach, move), but consistently presents Azure PowerShell examples immediately after Azure CLI, giving PowerShell equal prominence. Azure PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every section may subtly favor Windows users. However, Azure CLI examples are present and use Linux-friendly syntax (e.g., Ubuntu image), and there are no Windows-only tools or patterns. The order of examples (CLI first, PowerShell second) is appropriate, but the parity between CLI and PowerShell may suggest a slight bias toward Windows environments.

Recommendations

Consider clarifying that Azure PowerShell can be used cross-platform (Windows, Linux, macOS) via PowerShell Core, to reduce perceived Windows bias.
Explicitly mention that Azure CLI is available on all platforms and is often preferred for Linux/macOS users.
If possible, add brief notes about using PowerShell Core on Linux/macOS for Azure PowerShell examples.
Ensure that CLI examples remain prominent and up-to-date, and that any platform-specific caveats are noted.
If scripting is discussed, mention Bash as well as PowerShell for automation scenarios.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides parity between Azure CLI and PowerShell for all major tasks, but consistently presents PowerShell examples immediately after CLI, and includes detailed PowerShell usage. There are no Linux-specific examples or references to Linux tools, but the Azure CLI is cross-platform and is presented first. Minor bias is present due to the prominence and detail of PowerShell examples, but Linux/macOS users can fully complete all tasks using the CLI.

Recommendations

Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
Add a note clarifying that PowerShell examples are for Windows users, while CLI examples are for cross-platform users.
Consider including Bash scripting examples for advanced automation scenarios.
Ensure screenshots and instructions in portal sections are not Windows-centric (e.g., avoid showing Windows UI elements unless necessary).

Create Pull Request

Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides configuration examples for rolling upgrades with MaxSurge using Azure Portal, Azure CLI, PowerShell, and ARM Template. While the Azure CLI and ARM Template are cross-platform, PowerShell is Windows-centric and receives its own dedicated example. Additionally, the PowerShell example is presented immediately after the CLI example, which is common but may reinforce Windows-first patterns. No Linux-specific tools or shell examples (e.g., Bash, Cloud Shell) are provided, but the CLI example is sufficient for Linux/macOS users.

Recommendations

Clarify that Azure CLI commands work on Linux, macOS, and Windows, and recommend Cloud Shell for cross-platform usage.
Consider adding Bash shell script examples or referencing Azure Cloud Shell for Linux/macOS users.
Explicitly state that PowerShell is optional and primarily for Windows users, to avoid confusion for Linux/macOS readers.
Ensure parity in example ordering by listing CLI (cross-platform) before PowerShell, and possibly labeling PowerShell as Windows-specific.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 2 bias types

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, and in some sections (such as updating scale sets), PowerShell is presented before REST API and ARM template examples. There is a slight 'windows_first' bias in listing PowerShell as a primary method alongside CLI, despite CLI being more cross-platform. No Linux-specific shell examples (e.g., Bash) are provided, but the CLI examples are inherently cross-platform. References to ARM templates include links for both Linux and Windows, maintaining parity. No Windows-only tools or patterns are mentioned, and the feature itself is not Windows-specific.

Recommendations

List Azure CLI examples before PowerShell in all sections, as CLI is more cross-platform and preferred for Linux/macOS users.
Explicitly note that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is Windows-centric.
Consider adding Bash shell script examples for Linux users, or clarifying that Azure CLI examples are suitable for Bash/zsh environments.
Where possible, avoid presenting PowerShell as equally cross-platform as CLI.

Create Pull Request

Virtual Machines Best practices for virtual machine cost optimization ...s/virtual-machines/cost-optimization-best-practices.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation is generally cross-platform and references both Windows and Linux VM options, but there is a minor bias in the ordering and phrasing: Windows VM considerations (e.g., 'Use at least B2 for Windows machines') are mentioned before Linux equivalents, and Windows pricing links are listed before Linux pricing links. No Windows-only tools or examples are given, and Linux is referenced throughout. No critical sections are Windows-only.

Recommendations

When mentioning VM sizing or pricing, present Windows and Linux options together or alternate the order to avoid Windows-first bias.
Where specific recommendations are made for Windows (e.g., 'Use at least B2 for Windows machines'), consider adding equivalent guidance for Linux VMs if applicable.
Ensure parity in links and examples, such as listing Linux pricing alongside Windows pricing, and referencing automation tools that work for both platforms.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 1 bias type

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, there is a minor bias in the 'Backup and recovery' section, where Azure Site Recovery is noted as supported for Flexible orchestration 'via PowerShell' without mentioning equivalent Linux CLI or Azure CLI support. Additionally, the only explicit command example given uses Azure CLI, which is cross-platform, but the documentation does not provide explicit Linux/macOS shell examples or clarify parity for PowerShell versus Bash/CLI usage.

Recommendations

Clarify that Azure Site Recovery can be managed via Azure CLI or REST API, not just PowerShell, and provide Linux/macOS-compatible command examples.
Where command examples are given, explicitly show both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) versions, or note that Azure CLI is cross-platform.
Add notes or links to documentation for Linux users where features are managed primarily via PowerShell, indicating alternative methods if available.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides backup and disaster recovery guidance for Azure Managed Disks on both Linux and Windows VMs. However, there are minor signs of Windows bias: Windows tools (such as Volume Shadow Service for application-consistent backups) are mentioned first and in more detail, while Linux equivalents (like fsfreeze) are referenced briefly and described as less capable. SQL Server (a Windows-centric workload) is highlighted with links to Windows-specific backup articles, and Windows is mentioned before Linux in some consistency descriptions.

Recommendations

Expand Linux backup tooling guidance: Provide more detail on Linux tools (e.g., fsfreeze, LVM snapshots, application-specific backup solutions) for achieving file and application consistency.
Balance example order: When describing backup consistency, mention Linux and Windows approaches equally, and avoid always listing Windows first.
Include links to Linux-specific documentation: Add references to Linux backup strategies (such as PostgreSQL, MySQL, MongoDB, Cassandra) and their Azure integration.
Clarify parity: Explicitly state where Azure backup features offer equivalent support for Linux and Windows, or note any limitations.
Add Linux-focused scenarios: Include examples of Linux workloads (e.g., web servers, open-source databases) and their backup strategies.

Create Pull Request

Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. While PowerShell is included, it is not the only example, and it is presented after CLI examples. The CLI examples use Azure CLI, which is cross-platform and works on Windows, Linux, and macOS. PowerShell is shown as an additional option, but not exclusively or first. There are no Windows-only tools or patterns, and Linux users are not excluded from any critical workflow. However, PowerShell is included as a distinct example, which may be seen as a minor bias toward Windows users, but the CLI is always shown first.

Recommendations

Continue to provide Azure CLI examples first, as it is cross-platform.
Clarify that Azure CLI commands work on Linux, macOS, and Windows.
Optionally, add a note that PowerShell examples are for users who prefer PowerShell, typically on Windows, but PowerShell Core is also available cross-platform.
Ensure screenshots and portal instructions do not reference Windows-specific UI elements.
Consider adding a short section highlighting cross-platform support for all tools used.

Create Pull Request

Virtual Machines Server-side encryption of Azure Managed Disks ...blob/main/articles/virtual-machines/disk-encryption.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation generally maintains parity between Windows and Linux, providing links to both PowerShell (Windows) and CLI (Linux) guides for enabling encryption features. However, there is a mild 'windows_first' bias, as PowerShell/Windows links and references are consistently listed before their Linux/CLI counterparts. Additionally, in some places, PowerShell is mentioned as the primary tool for certain operations (e.g., revoking access to customer-managed keys), with CLI mentioned second.

Recommendations

Alternate the order of Windows/PowerShell and Linux/CLI references throughout the documentation to avoid consistently prioritizing Windows.
Where both PowerShell and CLI are mentioned, explicitly state that both are equally supported and provide parallel examples or links.
In sections where only PowerShell is referenced first (e.g., revoking access), ensure CLI is given equal prominence, or consider combining into a single sentence referencing both tools.
Consider adding brief inline CLI and PowerShell command examples for common tasks, rather than only linking out, to improve parity and user experience.

Create Pull Request

Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and Azure PowerShell examples for creating instant access snapshots, but the PowerShell example is given equal prominence to the CLI example, and is not clearly marked as Windows-specific. The CLI example is cross-platform, but there are no explicit Linux/macOS shell examples (e.g., Bash) or clarifications about platform compatibility. The PowerShell example may create friction for Linux/macOS users, as Azure PowerShell is primarily used on Windows. The documentation does not mention Linux tools or patterns, nor does it clarify that Azure CLI is the recommended cross-platform approach.

Recommendations

Clearly indicate that Azure PowerShell examples are Windows-centric and recommend Azure CLI for Linux/macOS users.
Add explicit Bash shell examples or clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS terminals.
Consider showing Azure CLI examples first, or labeling them as the default for cross-platform usage.
Add a note explaining that Azure PowerShell can be used on Linux/macOS via PowerShell Core, but Azure CLI is generally preferred for cross-platform scenarios.

Create Pull Request

Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides both Azure CLI and Azure PowerShell options for configuring disk restrictions, but references to PowerShell and Windows-centric links (e.g., custom RBAC roles via PowerShell) are presented first or exclusively in some sections. The custom RBAC role section links only to a PowerShell-based guide, and PowerShell is mentioned before CLI in the NetworkAccessPolicy section. Linux-specific guidance is present but not always prioritized.

Recommendations

Add or link to Linux/CLI-based guides for creating custom RBAC roles, not just PowerShell.
Present Azure CLI examples and links before or alongside PowerShell examples, especially in sections relevant to all platforms.
Ensure that all referenced articles (e.g., for private links) have clear Linux/CLI equivalents and are equally visible.
Where possible, clarify that both Azure CLI and PowerShell can be used, and provide examples for each.

Create Pull Request

Virtual Machines Enable shared disks for Azure Managed Disks .../main/articles/virtual-machines/disks-shared-enable.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides parity between Azure CLI and Azure PowerShell for all disk operations, but PowerShell examples are given equal prominence and sometimes shown before CLI. Azure PowerShell is a Windows-centric tool, and its heavy usage may create friction for Linux/macOS users. However, Azure CLI examples are present for every operation, and the documentation explicitly states applicability to both Linux and Windows VMs. No Windows-only tools or patterns are used, and Linux is not missing from any critical example.

Recommendations

Consider listing Azure CLI examples before PowerShell in each section, as Azure CLI is cross-platform and more accessible for Linux/macOS users.
Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows (with limited cross-platform support).
Add brief notes or links for Linux/macOS users on how to install and use Azure CLI.
Where possible, clarify that all steps are OS-agnostic unless a specific OS is required.

Create Pull Request

Virtual Machines Share an Azure Managed Disk across VMs ...cs/blob/main/articles/virtual-machines/disks-shared.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation covers both Windows and Linux platforms for Azure shared disks, but Windows examples and explanations are consistently presented before Linux equivalents. The 'Sample workloads' section starts with Windows, and performance throttling examples also begin with Windows scenarios. However, Linux information is present and detailed, including supported distributions, cluster managers, and relevant utilities.

Recommendations

Alternate the order of Windows and Linux sections, or present Linux examples first in some cases.
Ensure parity in example detail: provide equally detailed Linux workload examples, including step-by-step guides or links to Linux-specific templates (similar to the Windows SoFS and SAP templates).
Add explicit Linux sample configurations or walkthroughs for clustered file servers and database workloads, matching the depth of Windows examples.
Where possible, include links to Linux-focused documentation or templates for common workloads.

Create Pull Request

Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation is generally neutral and focused on Azure Disk Storage features, which are cross-platform. However, there are minor instances where Windows-specific links or references are given before Linux equivalents, such as linking to Windows documentation first for disk expansion, and referencing Windows tools (Azure PowerShell) alongside Azure CLI. No critical features are described in a Windows-only manner, and Linux parity is mostly maintained.

Recommendations

When referencing how to expand disks, ensure both Windows and Linux documentation links are presented together, or Linux is not consistently listed second.
Where Azure PowerShell is mentioned, explicitly note Azure CLI and Bash alternatives for Linux/macOS users.
Review linked articles (e.g., expand-disks, find-unattached-disks) to ensure Linux/macOS examples are present and not secondary.
Consider adding a short statement clarifying that all features are available for both Windows and Linux unless otherwise noted.

Create Pull Request

Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ minor_windows_reference

Summary

The documentation is primarily focused on Linux, as expected given the page title and scope. However, there are minor instances of Windows bias: (1) PowerShell deployment instructions are presented before Azure CLI instructions, which may be less relevant to Linux users; (2) Some notes reference Windows documentation or PowerShell tools first; (3) Troubleshooting and deployment sections sometimes mention PowerShell before CLI, even though CLI is more commonly used on Linux. No critical Linux gaps are present, and all examples, paths, and instructions are Linux-centric.

Recommendations

Present Azure CLI deployment instructions before PowerShell, as CLI is more relevant for Linux users.
Where possible, avoid referencing Windows-specific documentation or tools unless necessary for context.
Ensure troubleshooting steps prioritize Azure CLI and Linux-native tools.
Clarify that PowerShell instructions are optional for users who prefer it, but Azure CLI is the default for Linux.

Create Pull Request

Virtual Machines Ephemeral OS disks ...b/main/articles/virtual-machines/ephemeral-os-disks.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ minor_powershell_reference

Summary

The documentation covers ephemeral OS disks for both Linux and Windows VMs, with clear parity in feature descriptions and examples. However, there are minor instances where Windows-specific information is presented first or in more detail (e.g., page file placement, cache size example), and PowerShell is mentioned before CLI in the customer-managed key section. Linux examples are present and not omitted, but Windows details sometimes precede Linux equivalents.

Recommendations

Ensure Linux and Windows examples are presented with equal prominence and in parallel where possible.
When referencing tools (e.g., PowerShell, CLI), alternate their order or present them together to avoid Windows-first bias.
Provide explicit Linux command examples alongside Windows/PowerShell ones in deployment and configuration sections.
Clarify when information is Windows-specific and provide Linux-specific details in the same section.

Create Pull Request

Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation is generally Linux-focused, as expected from its title and content. However, throughout the page, Azure CLI and Azure PowerShell examples are consistently paired, with PowerShell examples always present and sometimes shown immediately after CLI. PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every section may create friction for Linux/macOS users, especially since PowerShell is not a default shell on Linux. Additionally, references to Azure PowerShell are frequent and sometimes precede CLI or are given equal prominence, despite the Linux audience.

Recommendations

Consider prioritizing Azure CLI examples, as CLI is cross-platform and native to Linux/macOS users.
Where PowerShell is included, clarify its availability on Linux and provide installation guidance or links.
In sections where both CLI and PowerShell are shown, ensure CLI is presented first, or mark PowerShell as optional for users who prefer it.
Add Bash or shell script examples where relevant, especially for troubleshooting or agent operations.
Review the use of PowerShell in ARM template sections and ensure Linux-native tools (like CLI or Bash) are emphasized.

Create Pull Request

Virtual Machines NVIDIA GPU Driver Extension - Azure Linux VMs ...es/virtual-machines/extensions/hpccompute-gpu-linux.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation is focused on Linux Azure VMs, but includes PowerShell examples alongside Azure CLI and ARM template examples. In the deployment section, PowerShell is presented before Azure CLI, which is more commonly used on Linux. There is also a brief mention of a Windows extension, but this is appropriate for cross-referencing. The troubleshooting section provides both PowerShell and Azure CLI commands, but PowerShell is listed first. All technical instructions, screenshots, and manual steps are Linux-specific, and there are no Windows-only tools or patterns used for critical tasks.

Recommendations

Present Azure CLI examples before PowerShell, as CLI is the primary cross-platform tool and preferred on Linux.
Explicitly note that PowerShell examples are optional and primarily for users on Windows or those who prefer PowerShell.
Consider removing or de-emphasizing PowerShell examples unless there is a clear use case for Linux users.
Ensure troubleshooting commands prioritize Azure CLI and Bash, with PowerShell as an alternative.
Add a short note clarifying that all instructions are for Linux VMs, and PowerShell is included for completeness.

Create Pull Request

Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

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 is used as the default example, with Linux mentioned as an alternative. In the CLI section, Linux is the default, but Windows is referenced. The PowerShell examples are prominent and detailed, which may favor Windows users. However, the documentation overall covers both platforms and gives parity in CLI and REST examples.

Recommendations

In PowerShell examples, provide a Linux example as the primary or in parallel with the Windows example.
Ensure that both Linux and Windows are equally represented in example blocks, alternating which is shown first.
Add explicit notes or links for Linux users in PowerShell sections, clarifying usage or alternatives.
Consider including Bash or shell script examples for Linux users, especially for tasks commonly performed outside Azure CLI.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation presents Windows benchmarking (DISKSPD) before Linux benchmarking (FIO), with detailed parameter explanations and sample commands for DISKSPD. Windows tools and patterns are mentioned first, and the Windows section is more prominent. Linux parity is achieved with FIO examples, but Windows bias is evident in ordering and tool emphasis.

Recommendations

Present Linux (FIO) and Windows (DISKSPD) sections in parallel, or alternate their ordering to avoid Windows-first bias.
Provide equally detailed explanations and parameter breakdowns for FIO as for DISKSPD.
Explicitly mention cross-platform alternatives for DISKSPD (e.g., FIO for Windows, if applicable) or clarify tool selection rationale.
Add a summary table comparing Windows and Linux tools, parameters, and expected results.
Ensure images and sample outputs are balanced between Windows and Linux examples.

Create Pull Request

Virtual Machines Enable Azure Disk Encryption for Linux VMs ...les/virtual-machines/linux/disk-encryption-overview.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation is focused on Linux VMs and provides Linux-specific guidance throughout. However, there is mild evidence of Windows bias in the form of PowerShell examples and scripts being mentioned alongside Azure CLI, and PowerShell is referenced before CLI in some places. The 'Next steps' section lists both CLI and PowerShell quickstarts, but PowerShell is not strictly a Linux-native tool, and its inclusion may create friction for Linux users who prefer Bash or native Linux tools. The terminology table also references PowerShell cmdlets, which are not typically used in Linux environments, though Azure PowerShell is cross-platform.

Recommendations

Ensure Azure CLI examples and scripts are listed before PowerShell in all sections, as CLI is more native to Linux environments.
Clarify that PowerShell is optional and that Azure CLI is the recommended tool for Linux users.
Consider removing or de-emphasizing PowerShell references in terminology for Linux-focused documentation.
Provide Bash script examples where possible, or highlight native Linux tools for disk encryption management.
Explicitly state that Azure PowerShell is cross-platform, but CLI is preferred for Linux users.

Create Pull Request

Virtual Machines Expand Virtual Hard Disks on a Linux VM ...b/main/articles/virtual-machines/linux/expand-disks.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_tools

Summary

The documentation is focused on expanding disks for Linux VMs and provides comprehensive Linux-specific guidance. However, in the section about 'Expand without downtime classic VM SKU support', only a PowerShell script is provided to check SKU support, with no equivalent Bash/Azure CLI example for Linux users. This is a minor bias, as the rest of the document is highly Linux-centric.

Recommendations

Add a Bash or Azure CLI example for checking classic VM SKU support for disk expansion, so Linux users can perform the same check without needing PowerShell.
Consider linking to cross-platform tools or scripts where possible, or clarify that the PowerShell example is only required for classic VM SKU checks and provide alternatives if available.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first ⚠️ minor_windows_notes

Summary

The documentation covers both Linux and Windows VM image creation with Azure Image Builder, providing parity in most areas. However, there is a notable tendency to use PowerShell for checksum generation and example commands, and Windows-specific tools (e.g., Get-FileHash, shutdown, Sysprep) are referenced more frequently and sometimes before their Linux equivalents. Some notes and examples are Windows-centric, and PowerShell is often presented alongside Azure CLI, but not always with equal prominence for Linux/macOS users.

Recommendations

Where PowerShell is referenced for tasks like checksum generation, always provide the equivalent Linux/macOS command (e.g., sha256sum) with equal prominence.
Ensure that Azure CLI examples are shown first or equally with PowerShell, as CLI is cross-platform.
When referencing Windows-specific tools or commands, clarify Linux/macOS equivalents or alternatives where applicable.
Review the order of examples and notes to avoid Windows-first bias; alternate or group by OS where possible.
Add explicit Linux/macOS troubleshooting guidance where only Windows troubleshooting is mentioned.
For customizer types, clarify Linux limitations (e.g., no restart customizer) and suggest workarounds if possible.

Create Pull Request

Virtual Machines Verify encryption status for Linux - Azure Disk Encryption ...tual-machines/linux/how-to-verify-encryption-status.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both PowerShell and Azure CLI examples for verifying disk encryption status, but consistently presents PowerShell (a Windows-centric tool) before Azure CLI (cross-platform and native to Linux/macOS). The PowerShell section is more detailed and prominent, potentially signaling a Windows-first bias. However, the CLI and OS-level Linux commands are present and sufficient for Linux users.

Recommendations

Present Azure CLI examples before PowerShell, as CLI is cross-platform and more natural for Linux users.
Ensure that all PowerShell examples have equivalent, clearly documented Azure CLI commands.
Consider marking PowerShell sections as 'for Windows users' and CLI as 'for Linux/macOS users' to clarify intent.
Expand the OS-level verification section with more Linux-native tools or troubleshooting tips if possible.

Create Pull Request

Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation page is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance, commands, and examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details, which may create a perception of Windows-first bias. All configuration examples, tools, and troubleshooting steps are Linux-centric, and there are no PowerShell or Windows-only tools used for Linux configuration. The only PowerShell example is for base64 encoding a cloud-init file, which is relevant for Azure users on Windows but is not critical to the Linux time sync topic.

Recommendations

Move the Windows Server 2016 discussion and references to a background or context section, clarifying its relevance to Azure infrastructure rather than Linux VM configuration.
Add a brief note explaining why Windows Server 2016 time sync improvements matter for Linux VMs (e.g., Azure hosts use Windows Server 2016, so host time accuracy benefits Linux guests).
Provide a Linux shell command alternative for base64 encoding the cloud-init file, such as `base64 cloud-config.txt`, to ensure parity for Linux/macOS users.
Ensure Linux-specific links and guidance appear before or alongside any Windows references.

Create Pull Request

Virtual Machines Overview of Azure Disk Storage ...in/articles/virtual-machines/managed-disks-overview.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ minor_windows_reference

Summary

The documentation is largely cross-platform and neutral, but there are a few sections where Windows-specific tools, terminology, or links are mentioned before Linux equivalents, or Windows terminology is used without equal Linux context. For example, in the 'Images' section, the link provided is Windows-specific, and in the OS disk section, Windows partitioning is discussed in detail with only brief Linux mention. The 'Upload your VHD or VHDX' section does provide both Azure CLI (Linux) and PowerShell (Windows) links, but the Windows link is listed second. The temporary disk section gives both Linux and Windows paths, but Windows terminology (drive letters) is used more frequently.

Recommendations

Ensure that all example links and deep-dive articles are provided for both Linux and Windows users, especially in sections like 'Images' where only a Windows-specific link is given.
When discussing disk partitioning and OS disk details, provide equivalent Linux information (e.g., reference Linux partitioning schemes, default partitioning behavior, and relevant documentation).
Balance terminology and examples so that Linux and Windows are equally represented, for instance, by mentioning Linux device paths alongside Windows drive letters in all relevant sections.
Where possible, alternate the order of Linux and Windows examples or links to avoid implicit prioritization.

Create Pull Request