← Back to Dashboard
283
Pages Scanned
91
Pages Flagged
283
Changed Pages
32.2%
% Pages Flagged

Live Progress

🔴 Connecting...
100%
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:30 Scan started

Scan Information

Started At: 2026-02-14 00:00:30

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 283

Files Completed: 283

Problematic Pages

91 issues found
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
High 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 is heavily focused on Windows-centric tools, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and upgrade instructions reference Visual Studio (a Windows-only IDE) and PowerShell (primarily used on Windows), with no mention of Linux/macOS alternatives, CLI commands, or cross-platform tooling. There are no examples or guidance for Linux users or those using non-Windows environments.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Include guidance for configuring upgrade parameters and health policies using tools available on Linux/macOS, such as sfctl (Service Fabric CLI).
  • Mention and link to documentation for Service Fabric development and deployment workflows on Linux clusters.
  • Clearly indicate if certain steps are Windows-only, and provide parity or alternatives for non-Windows users where possible.
GitHub 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-specific instructions or examples, and the feature is unavailable for Linux users, creating a Windows-first bias.
Recommendations
  • Clearly indicate at the top of the page that the reverse proxy feature is Windows-only, to prevent confusion for Linux users.
  • Provide alternative guidance or links for Linux cluster users, such as recommended patterns for service discovery and communication.
  • If/when Linux support becomes available, add Linux-specific examples and instructions.
GitHub 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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
Although the introduction states Service Fabric clusters run on Windows Server and Linux, the documentation focuses exclusively on Windows Server in critical sections. The 'Supported operating systems' section explicitly states that Linux isn't yet supported for standalone clusters, and all security and scaling examples reference Windows-specific tools and patterns. No Linux-specific instructions, examples, or equivalency are provided.
Recommendations
  • Clarify at the top that standalone clusters are currently Windows-only, despite the general Service Fabric support for Linux.
  • Remove or revise the description to avoid implying Linux parity where it does not exist.
  • Add a section or note explaining Linux support status, and link to relevant Linux documentation if/when available.
  • Ensure that future updates include Linux examples and instructions when Linux support is added.
GitHub 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_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides extensive PowerShell examples and references to PowerShell cmdlets for Service Fabric application upgrades, without offering equivalent CLI or Linux-native examples. Windows/PowerShell tools are mentioned first and exclusively, creating friction for Linux/macOS users who may use Azure CLI or REST APIs. There is no explicit mention of Linux-compatible tooling or guidance for non-Windows environments.
Recommendations
  • Add Azure CLI examples for all upgrade operations alongside PowerShell examples.
  • Explicitly mention that Service Fabric management can be performed from Linux/macOS using Azure CLI or REST API, and provide links to relevant documentation.
  • Include sample ARM template snippets for upgrade operations where possible.
  • Clarify which operations are PowerShell-only (if any), and provide guidance or alternatives for Linux users.
  • Reorder sections or examples to avoid always showing Windows/PowerShell first.
GitHub 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 tooling recommendations. The only explicit tooling advice is to use Visual Studio on Windows and a Windows file path for validating manifest XML schemas. Additionally, the PowerShell module is mentioned for service creation, but no Linux or cross-platform alternatives are referenced. There are no Linux/macOS-specific examples or guidance, and Windows tools are mentioned first and exclusively.
Recommendations
  • Add instructions for validating XML schema on Linux/macOS, such as using xmllint or VS Code with XML plugins.
  • Mention cross-platform alternatives to Visual Studio, like Visual Studio Code or JetBrains Rider.
  • Provide examples for creating services using Azure CLI or other cross-platform tools, not just PowerShell.
  • Include Linux/macOS file path conventions where relevant.
  • Clarify which steps are Windows-only and which are cross-platform.
GitHub 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 ⚠ī¸ windows_first
Summary
The documentation provides numerous manual scaling instructions using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState), but does not mention equivalent Linux CLI commands or tools. PowerShell is referenced as the primary method for manual node management, and Windows-centric tools are presented first or exclusively. While Service Fabric supports Linux clusters, the documentation does not offer Linux-specific guidance or examples for these operations, creating friction for Linux users.
Recommendations
  • Add equivalent Linux CLI instructions for node management (e.g., using sfctl or Service Fabric CLI).
  • Include Linux-specific examples and workflows alongside PowerShell examples.
  • Clarify which commands are cross-platform and which are Windows-only.
  • Provide links to Linux tooling documentation (e.g., sfctl, Azure CLI) where relevant.
  • Ensure parity in example ordering (e.g., show Linux and Windows approaches side by side).
GitHub 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 is generally platform-neutral, focusing on Azure Service Fabric's backup configuration concepts and REST APIs. However, in the 'File share' backup storage section, only Windows-style file share paths (\\StorageServer\BackupStore) and Windows authentication methods are described, with no mention of Linux-compatible SMB mounting or examples. The file share authentication options are Windows-centric, and Windows terminology is used first and exclusively. There are no Linux-specific examples or guidance for configuring file share backups from Linux nodes.
Recommendations
  • Add examples and guidance for configuring file share backup storage from Linux-based Service Fabric clusters, including SMB mount instructions and authentication methods.
  • Mention Linux-compatible file share path formats and clarify any platform limitations.
  • If file share backup is Windows-only, explicitly state this to avoid confusion for Linux users.
  • Consider including parity examples for Linux/macOS where possible, or linking to relevant platform-specific documentation.
GitHub 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 page provides examples and links primarily for Azure PowerShell, with PowerShell-based tools mentioned before Azure CLI and sfctl. While Azure CLI and ARM templates are referenced, the best practices section highlights PowerShell commands first and does not provide equivalent CLI or Linux-native examples for key actions. This creates friction for Linux/macOS users who may prefer CLI or other cross-platform tools.
Recommendations
  • Add Azure CLI examples for deleting NodeTypes, restarting, and reimaging scale sets alongside PowerShell examples.
  • Mention Azure CLI and sfctl before or equally with PowerShell in best practices to avoid Windows-first ordering.
  • Clarify which tools are cross-platform and provide guidance for Linux/macOS users.
  • Include sample commands for ARM/Bicep deployments using CLI.
  • Explicitly state that PowerShell examples are also available via Azure CLI for parity.
GitHub 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 page on the architecture of Azure Service Fabric briefly mentions PowerShell cmdlets as a primary management interface, suggesting a Windows-centric approach to cluster and application lifecycle management. There is no mention of Linux equivalents (such as Bash, CLI, or REST API usage), nor are Linux tools or patterns referenced. The mention of Windows security as an option for securing transport is secondary and does not dominate the content, but the management section's focus on PowerShell creates friction for Linux users.
Recommendations
  • Add examples or references to Azure CLI, Bash scripts, or REST API usage for cluster and application management, alongside PowerShell.
  • Clarify that management operations can be performed from Linux/macOS using Azure CLI or REST APIs, not just PowerShell.
  • Mention Linux-compatible security mechanisms (such as X509 certificates) more prominently when discussing transport security.
  • Ensure that administrative APIs are described in a cross-platform way, not just via Windows tooling.
GitHub 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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and generic/standalone (ClusterConfig.json), but code samples and CLI usage are heavily focused on PowerShell and .NET/C#. There are no Linux-specific CLI examples (e.g., Bash, SFCTL), and the WindowsServer element is shown first in infrastructure configuration. This creates friction for Linux users, especially those running Service Fabric on Linux or using cross-platform tools.
Recommendations
  • Add equivalent Linux/Bash/SFCTL command examples alongside PowerShell for service creation and updates.
  • Clarify that ClusterManifest.xml is for Windows clusters and ClusterConfig.json is for cross-platform/standalone deployments; consider showing Linux infrastructure configuration first or equally.
  • Include explicit guidance or links for Linux users, such as how to configure clusters using Linux node types and relevant tools.
  • Mention cross-platform Service Fabric SDKs and management tools where applicable.
GitHub 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 partition health, using Windows-style paths and commands (e.g., 'PS C:\Users\User > Get-ServiceFabricPartitionHealth'). No equivalent Linux/macOS CLI or REST API example is provided, and the PowerShell example appears early in the page. The rest of the documentation is largely platform-neutral, focusing on concepts and configuration files, but the example section is Windows-centric.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Mention REST API alternatives for querying health, which are cross-platform.
  • When showing command-line examples, provide both Windows (PowerShell) and Linux/macOS (bash/sfctl) versions side-by-side.
  • Clarify that PowerShell is not required and that Linux/macOS users can use sfctl or REST APIs.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.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 presents Windows/PowerShell tooling (New-ServiceFabricApplication cmdlet, Visual Studio, Deploy-FabricApplication.ps1) before mentioning Linux-compatible options (sfctl, install.sh). PowerShell and Visual Studio examples are prioritized, and Linux-specific workflows are only briefly referenced. There are no explicit Linux/macOS examples or screenshots, and the scripting guidance is predominantly Windows-centric.
Recommendations
  • Add explicit Linux/macOS examples for application creation, such as using sfctl and install.sh, with sample commands and parameter formats.
  • Reorder sections to present cross-platform tools (sfctl) before Windows-specific tools (PowerShell, Visual Studio).
  • Include guidance for editing parameter files and deploying from Linux/macOS environments.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right workflow.
GitHub 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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for securing an Azure Service Fabric cluster exhibits moderate Windows bias. Windows Server clusters and Windows security patterns are mentioned repeatedly and often before Linux equivalents. There are explicit references to Windows authentication (Kerberos), Windows certificate services, and Windows-specific tools (MakeCert.exe). While the concept of securing clusters is stated to be the same for Linux and Windows, practical guidance and links for Linux standalone clusters are missing, and Windows-focused instructions and links are provided first or exclusively.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
  • Provide Linux-specific examples and tools for certificate creation and management (e.g., OpenSSL usage, Linux certificate authorities).
  • Ensure parity in documentation structure: mention Linux options alongside Windows options, not only after or as an afterthought.
  • Clarify any Azure Service Fabric features that are Windows-only, and highlight Linux limitations or differences where relevant.
GitHub 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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation provides a detailed conceptual overview of Service Fabric health monitoring, which is cross-platform in nature. However, the only practical example for reporting and evaluating application health is given using PowerShell cmdlets, which are Windows-specific. There are no equivalent Linux/macOS CLI or REST API examples, and PowerShell is presented as the default method for interacting with Service Fabric health reporting. Additionally, the example section does not mention Linux tooling or provide parity for non-Windows users.
Recommendations
  • Add equivalent examples using Azure CLI, REST API, or Service Fabric SDKs for Linux/macOS environments.
  • Explicitly mention that PowerShell is Windows-specific and provide guidance for Linux users on how to accomplish the same tasks.
  • Include sample code snippets for health reporting and querying using cross-platform tools (e.g., curl for REST API, Azure CLI, or Python SDK).
  • Reorder or supplement the example section to show Linux/macOS methods alongside or before Windows/PowerShell examples.
GitHub 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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation consistently provides only PowerShell-based deployment commands and Windows-centric operational examples (e.g., RDP, Windows command prompt usage), with no mention of Azure CLI, Bash, or cross-platform alternatives. This creates friction for Linux/macOS users, who must translate or adapt the instructions themselves.
Recommendations
  • Add Azure CLI equivalents for all PowerShell deployment commands (e.g., resource group and template deployments).
  • Include Bash shell examples where relevant, especially for operations like pinging VMs.
  • Mention cross-platform remote access options (e.g., SSH) alongside or instead of RDP, and clarify when RDP is only applicable to Windows nodes.
  • Explicitly state when a step is Windows-only and provide Linux/macOS alternatives where possible.
  • Consider providing a table or toggle for PowerShell vs. Azure CLI commands, as seen in other Azure documentation.
GitHub 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_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Service Fabric Events primarily describes event access via Windows-centric channels such as ETW/Windows Event logs and the Windows Azure diagnostics agent. Linux equivalents (e.g., Linux diagnostics agents, log access methods, or monitoring tools) are not mentioned, and Windows tools are referenced first and exclusively. This creates friction for Linux-based Service Fabric clusters, as guidance for event access and monitoring is not provided for those environments.
Recommendations
  • Add explicit instructions or examples for accessing Service Fabric events on Linux clusters, including supported logging channels and monitoring tools.
  • Mention Linux diagnostics agents and how to configure them for event collection and forwarding.
  • Clarify which event access methods are cross-platform (e.g., EventStore REST APIs) and which are Windows-only.
  • Provide parity in documentation by listing Linux methods alongside Windows methods, rather than only referencing Windows tools.
GitHub 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 examples and guidance for using the Fault Analysis Service primarily via C# and PowerShell, both of which are Windows-centric tools. There is no mention of Linux/macOS equivalents, such as Bash, CLI commands, or cross-platform scripting approaches. The PowerShell example assumes a Windows environment and does not address how Linux users can interact with the Fault Analysis Service, nor does it reference Azure CLI or REST API usage.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash scripts, or REST API.
  • Clarify whether the Fault Analysis Service APIs can be accessed from non-Windows platforms and provide guidance for cross-platform usage.
  • Include instructions for installing and using Service Fabric SDK and tools on Linux/macOS, if supported.
  • Mention alternative scripting tools (e.g., Bash, Python) for interacting with Service Fabric clusters.
GitHub 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 ⚠ī¸ windows_first
Summary
The documentation page provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits Windows bias in several areas. PowerShell is used exclusively for scripting examples, and the Key Vault VM extension discussed is Windows-specific. The documentation references Windows concepts (such as certificate store locations, ACLing, S-channel, and renewal linking) without Linux equivalents or alternatives. Windows tools and patterns are mentioned first and exclusively, with no Linux-specific guidance or parity for certificate provisioning, automation, or management.
Recommendations
  • Add Linux-specific scripting examples (e.g., Bash, Azure CLI) alongside PowerShell.
  • Explicitly document how certificate provisioning and management can be accomplished on Linux-based Service Fabric clusters, including any limitations or differences.
  • Clarify which VM extensions or provisioning mechanisms are supported on Linux and provide guidance for Linux users.
  • Mention Linux certificate store locations and access control mechanisms where relevant.
  • If certain features are Windows-only (e.g., Key Vault VM extension for Windows), clearly state this and provide Linux alternatives or workarounds.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.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 is generally cross-platform and describes Service Fabric's X.509 certificate authentication in an OS-neutral way. However, there are several subtle Windows biases: Windows certificate store paths and tools are mentioned first or exclusively in some places, troubleshooting instructions and error logs reference Windows event logs and Win32 APIs, and Linux-specific equivalents are only briefly mentioned or omitted. There are no PowerShell-heavy examples, but Windows-centric patterns and terminology are more prominent.
Recommendations
  • Wherever the Windows certificate store (e.g., LocalMachine\My) is referenced, explicitly mention the Linux equivalent (e.g., /var/lib/sfcerts) each time, not just once.
  • In troubleshooting sections, provide Linux log file paths and diagnostic steps alongside Windows Event Log instructions.
  • When referencing Windows-specific APIs (e.g., Win32 CryptoAPI), clarify how equivalent functionality is handled on Linux, or note if not applicable.
  • If there are differences in certificate provisioning or management between Windows and Linux nodes, provide parallel examples or links to Linux-specific guidance.
  • Add explicit Linux/macOS troubleshooting tips for common certificate issues (e.g., permissions, file locations, service restarts).
GitHub 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 given, with no mention of Azure CLI or Bash scripting alternatives. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before any potential cross-platform alternatives, reinforcing a Windows-first approach.
Recommendations
  • Add Azure CLI examples for all tasks currently demonstrated with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users.
  • Consider including Bash scripting or REST API examples where appropriate.
  • Where possible, clarify that ARM templates and portal are platform-agnostic.
GitHub 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, which is primarily a Windows tool. There are no Linux CLI or cross-platform alternatives mentioned for cluster operations, and the PowerShell command is presented as the sole method for manual intervention.
Recommendations
  • Add equivalent Linux/macOS CLI examples (e.g., Azure CLI, Bash) for manual cluster operations.
  • Clarify whether Service Fabric Explorer is accessible or usable from Linux/macOS, or provide alternatives if available.
  • Where possible, provide cross-platform guidance for connecting to and managing Service Fabric clusters.
  • Explicitly note if certain commands or tools are Windows-only, and offer Linux/macOS workarounds or alternatives.
GitHub 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 generally covers both Windows and Linux clusters for Azure Service Fabric monitoring, but there are several areas where Windows tools and patterns are mentioned first or exclusively, and Linux equivalents are referenced later or less prominently. Some examples and tutorials focus on Windows or .NET, and certain features (like EventStore APIs) are Windows-only. Linux-specific guidance is present but less detailed, and Linux configuration steps are sometimes referenced as separate links rather than integrated alongside Windows instructions.
Recommendations
  • Ensure Linux examples and tools are presented alongside Windows ones, not just referenced via links.
  • Where Windows tools (e.g., Event Viewer, ETW) are mentioned, explicitly describe Linux equivalents (e.g., LTTng, Syslog) in the same section.
  • Provide Linux-focused tutorials and sample code, especially for application monitoring and logging.
  • Clarify when features are Windows-only and offer alternative approaches for Linux users.
  • Balance the order of presentation so Linux and Windows are equally visible in lists and explanations.
GitHub 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 ⚠ī¸ windows_tools
Summary
The documentation prioritizes Windows-centric tools (PowerShell and Visual Studio) in both structure and detail. Parameters for PowerShell and Visual Studio are discussed first and in greater depth, with SFCTL (the cross-platform CLI) covered later. Most examples and parameter tables focus on PowerShell, with Linux/macOS users needing to adapt or refer to a separate section. There are no direct Linux shell examples, and the workflow for non-Windows users is less prominent.
Recommendations
  • Reorganize the documentation to present SFCTL (Service Fabric CLI) parameters and workflows alongside or before PowerShell/Visual Studio, highlighting its cross-platform nature.
  • Provide explicit Linux/macOS shell examples (e.g., bash commands) for common upgrade scenarios using SFCTL.
  • Ensure parameter tables and explanations are parallel for all tools, not just PowerShell/Visual Studio.
  • Add a summary table or section at the top that helps users quickly identify which tool/command to use based on their OS.
  • Where PowerShell has a code example, provide an equivalent SFCTL example.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.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 for Initializer CodePackages in Service Fabric provides only Windows container examples, uses Windows-specific images (nanoserver:1809), and references Windows paths and commands (cmd, C:\ paths, ping, type). There is no mention of Linux containers, Linux-compatible images, or equivalent Linux command examples. The ApplicationManifest and ServiceManifest examples are exclusively Windows-focused, and the 'Next steps' section does not link to Linux container guidance.
Recommendations
  • Add a parallel example using Linux containers (e.g., mcr.microsoft.com/linux/base images) with Linux shell commands.
  • Include guidance on using Initializer CodePackages with Linux containers, specifying differences in paths, commands, and volume mounts.
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide Linux-specific documentation.
  • If Initializer CodePackages are Windows-only, explicitly state this limitation at the top of the article.
GitHub 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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page primarily references PowerShell cmdlets (Az PowerShell, AzSF PowerShell) for management operations, with no explicit mention of Linux/macOS alternatives or CLI equivalents. While the Azure CLI (az resource) is mentioned once, the overall guidance and examples are PowerShell-centric, which may create friction for Linux/macOS users who typically use Azure CLI or bash scripts.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell cmdlet examples, especially for common operations like creating or deleting applications and services.
  • Explicitly mention that the Azure CLI can be used on Linux/macOS for ARM resource management, and provide links to relevant documentation.
  • Where possible, include bash script examples or cross-platform instructions alongside PowerShell examples.
  • Clarify in each section whether the instructions are cross-platform or Windows-specific.
GitHub 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 ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page for RunToCompletion semantics in Service Fabric presents code examples and guidance exclusively for Windows containers and Windows-specific tools. All container examples use Windows images and Windows command syntax, and querying deployment status is described only via PowerShell and C# APIs, with no mention of Linux equivalents. There is no guidance or example for Linux containers or cross-platform usage, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent Linux container examples using popular Linux base images (e.g., Ubuntu, Alpine) and shell commands.
  • Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, provide Linux-specific guidance.
  • Include instructions for querying deployment status using Linux tools (e.g., Azure CLI, Bash scripts) or cross-platform approaches.
  • Present examples for both Windows and Linux containers, or explicitly state if the feature is Windows-only.
  • Avoid using Windows-specific terminology (e.g., cmd, PowerShell) without mentioning Linux alternatives.
GitHub 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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ 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 alternatives are mentioned, Linux-native CLI tools (such as sfctl or Azure CLI) are not referenced in the main procedural steps, and PowerShell examples are shown first or exclusively. This creates friction for Linux/macOS users, who must infer or search for equivalent commands.
Recommendations
  • Add explicit examples and procedural steps using sfctl (Service Fabric CLI) and Azure CLI for all major lifecycle operations (deploy, upgrade, remove, cleanup).
  • Where PowerShell cmdlets are referenced, provide Linux/macOS equivalents alongside, not just REST API links.
  • Ensure that CLI and REST API options are presented before or alongside PowerShell examples, not after.
  • Include sample command blocks for sfctl and Azure CLI in relevant sections.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right approach.
GitHub 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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides links to application upgrade tutorials using Visual Studio and PowerShell, both of which are primarily Windows-centric tools. There are no explicit Linux/macOS examples or equivalent upgrade instructions for those platforms. The serialization guidance is .NET-focused, but does not reference Linux-specific workflows or tools.
Recommendations
  • Add links or sections for upgrading Service Fabric applications using Linux/macOS tools, such as Azure CLI or REST APIs.
  • Provide examples or tutorials for application upgrades on Linux-based Service Fabric clusters.
  • Clarify which upgrade methods are cross-platform and which are Windows-only.
  • Mention alternative development environments (e.g., VS Code, CLI) for non-Windows users.
GitHub 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 Azure Service Fabric application security in a generally platform-neutral manner, but several sections show Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned before or instead of Linux equivalents. Disk encryption is only referenced via a PowerShell/Windows link, and Linux disk encryption is listed as a TODO. Some examples and guidance (e.g., running services under user accounts) focus on Windows scenarios, with less detail for Linux. Linux-specific tools and patterns are rarely mentioned, and Linux parity is incomplete in some critical areas.
Recommendations
  • Add Linux-specific examples and guidance for disk encryption, referencing Azure documentation for encrypting disks on Linux VMSS clusters.
  • Ensure parity in sections about running services under user accounts: clarify how this works on Linux clusters, including any limitations or differences.
  • Where Windows tools (e.g., PowerShell, BitLocker, gMSA) are mentioned, provide equivalent Linux tools or note if no equivalent exists.
  • Review all examples and ensure both Windows and Linux scenarios are covered, especially for certificate management, user accounts, and startup scripts.
  • Remove or resolve TODOs regarding Linux disk encryption, providing actionable guidance.
GitHub 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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation for Service Fabric application upgrades demonstrates a notable Windows bias. It provides only PowerShell-based examples and references to Windows-specific tools (e.g., http.sys), with no equivalent examples or guidance for Linux users. The upgrade process is described using Windows-centric commands, and Linux/CLI alternatives are not mentioned or linked. This creates friction for Linux/macOS users who may be managing Service Fabric clusters on those platforms.
Recommendations
  • Add equivalent examples using Azure CLI or REST API for application upgrades, especially for parameter preservation.
  • Explicitly mention Linux support for Service Fabric and link to relevant Linux documentation where available.
  • Clarify when features or commands are Windows-only (e.g., http.sys, PowerShell cmdlets) and provide Linux alternatives or workarounds.
  • Reorder sections or examples to present cross-platform or platform-neutral approaches first, followed by platform-specific guidance.
GitHub 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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation exclusively uses PowerShell and Windows-centric tools (Microsoft.ServiceFabric.Powershell.Http module) for all command-line and API examples. There are no Linux/macOS CLI equivalents (such as Bash, curl, or Azure CLI) provided, and PowerShell is presented as the primary and only scripting environment. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls, so Linux/macOS users can follow along without PowerShell.
  • Mention and provide Azure CLI commands where possible, as Azure CLI is cross-platform.
  • Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS, and provide installation instructions if so.
  • Reorganize examples to show cross-platform approaches first, or at least in parallel with PowerShell.
  • Explicitly state if any steps are Windows-only, and provide alternatives or workarounds for other platforms.
GitHub 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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily biased toward Windows/PowerShell usage. All code examples use PowerShell, and the prerequisite is to install a Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, curl, or other cross-platform tools. The REST API is only shown via PowerShell scripts, and Windows authentication patterns (certificate thumbprints, PowerShellGet) are referenced. Service Fabric Explorer is mentioned, but no information is given about its availability or usage on Linux/macOS.
Recommendations
  • Add examples using Azure CLI or curl for REST API calls, which are cross-platform.
  • Document how to authenticate and connect to Service Fabric clusters from Linux/macOS (e.g., using certificates, REST calls).
  • Mention or link to any available Service Fabric tools or modules for Linux/macOS, or clarify if PowerShell Core is supported cross-platform.
  • Provide guidance for Linux/macOS users on installing and using PowerShell Core if that's required.
  • Clarify Service Fabric Explorer's platform support and usage for non-Windows users.
GitHub 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_tools ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell is featured prominently and used for upgrade operations without Linux/macOS alternatives. Windows-specific tools and registry settings are discussed in detail, while Linux equivalents (such as shell commands or Linux VM configuration) are missing or referenced only via external links. Windows configuration details (e.g., registry keys, Windows Update settings) are described before or instead of Linux approaches.
Recommendations
  • Include Linux/macOS shell (bash) examples for cluster upgrade operations, especially where only PowerShell is shown.
  • Add Linux-specific configuration guidance for disabling automatic updates on Linux VMSS nodes, analogous to the Windows registry and Windows Update settings.
  • Where PowerShell is used for cluster management, provide equivalent bash/CLI commands for Linux users, or clarify if such operations are Windows-only.
  • Balance the order of presentation so that Linux and Windows instructions/examples are given equal prominence, or clearly separate them by OS.
  • Explicitly note when a step or tool is Windows-only to avoid confusion for Linux/macOS users.
GitHub 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 most security best practices, including certificate creation and secret encryption. However, Windows examples (PowerShell commands, Windows Defender, Windows security baselines) are often presented first or in greater detail, and Windows-specific tools (PowerShell, Windows Defender, Azure Desired State Configuration) are referenced without Linux equivalents or with less emphasis. Some sections, such as Windows Defender and security baselines, are inherently Windows-focused, but overall, Linux guidance is present but less prominent.
Recommendations
  • Ensure Linux examples are given equal prominence and detail as Windows examples, especially in sections on certificate creation, secret encryption, and endpoint configuration.
  • Where Windows-specific tools (e.g., PowerShell, Windows Defender, DSC) are mentioned, provide clear Linux alternatives or explicitly state when no equivalent exists.
  • Consider alternating the order of Windows and Linux examples, or grouping them together for parity.
  • Add references to Linux security baselines and antivirus solutions where relevant, or clarify their absence.
  • Expand Linux-specific guidance for Azure Firewall rules, endpoint certificates, and managed identities if applicable.
GitHub 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 or scripting examples (such as Bash, Azure CLI, or REST API) are provided. All PowerShell examples are shown immediately after the C# code, with no mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for each placement policy, as Azure CLI is cross-platform and widely used.
  • Mention REST API options for configuring placement policies, with example requests.
  • Explicitly note PowerShell's platform limitations and link to Linux/macOS-compatible tools.
  • Consider including Bash or Python SDK examples where relevant.
  • Clarify if certain configuration steps are only possible via PowerShell, and provide guidance for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.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 Windows and Linux guidance for Azure Service Fabric networking, but there are several areas where Windows-specific tools (e.g., PowerShell, netsh) and examples are mentioned first or exclusively. Some explanations reference Windows patterns or tools before Linux equivalents, and PowerShell is highlighted as the primary API client. ARM template samples and links are also Windows-focused. However, Linux support is acknowledged and included in key sections.
Recommendations
  • Add Linux CLI examples alongside PowerShell examples, especially for cluster management and networking tasks.
  • Where Windows tools (e.g., netsh) are referenced, provide equivalent Linux commands (e.g., 'ss', 'lsof', or 'netstat') for port range checks.
  • Balance the order of presentation so Linux and Windows are treated equally (e.g., mention Linux and Windows in parallel, not Windows first).
  • Include ARM template samples for Linux clusters with NSG configuration, not just Windows.
  • Clarify when guidance applies to both platforms, and explicitly note any platform-specific differences.
GitHub 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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page covers Service Fabric cluster settings for both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows-specific terms (e.g., certificate store names like 'My', store locations like 'LocalMachine', NTLM authentication, and references to Windows Defender Firewall) are prevalent. Windows terminology and tools are often mentioned first or exclusively, with Linux equivalents rarely explained or referenced. Some parameters default to Windows values or behaviors, and Linux-specific guidance is minimal or absent. There are settings that reference Windows-only features (e.g., Windows Update, NTLM, Windows log directories) without clear Linux alternatives or parity explanations.
Recommendations
  • For parameters referencing Windows certificate stores (e.g., 'My', 'LocalMachine'), add explanations or examples for Linux equivalents (such as file paths or openssl usage).
  • Where NTLM authentication or Windows Defender Firewall is referenced, clarify Linux alternatives or note if the feature is Windows-only.
  • For settings with Windows-centric defaults, provide Linux-specific default values and guidance where applicable.
  • Add explicit Linux examples and explanations for customizing cluster settings, especially for standalone clusters.
  • Ensure that Linux-specific configuration paths, tools, and terminology are documented alongside Windows equivalents.
GitHub 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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets, but several sections and examples show Windows bias. The JSON snippet uses a Windows-style file path (D:\SvcFab) as the default for dataPath, and the 'Next steps' section links to PowerShell scripts for changing RDP port ranges and admin credentials, which are Windows-specific tasks. There are no explicit Linux/macOS examples or guidance, and Windows tools/patterns (RDP, PowerShell) are mentioned exclusively.
Recommendations
  • Provide equivalent Linux/macOS examples, such as using SSH for remote connection instead of RDP.
  • Show Linux file path conventions (e.g., /var/svcfab) alongside Windows paths in configuration examples.
  • Include links to Bash or CLI scripts for cluster management tasks, not just PowerShell.
  • Clarify which tasks are Windows-only and which are cross-platform, and offer Linux guidance where possible.
GitHub 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 only PowerShell and C# examples for managing Service Fabric Application Groups. PowerShell is a Windows-centric tool, and no Linux/macOS CLI (such as Bash, Azure CLI, or REST API) examples are given. There is no mention of Linux-compatible tooling or commands, which creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add Azure CLI examples for all operations shown (application creation, updating, querying load, removing capacity).
  • Include REST API examples for cross-platform management.
  • Explicitly mention whether PowerShell commands are supported on PowerShell Core (cross-platform) or only Windows PowerShell.
  • Provide guidance for Linux/macOS users on how to perform equivalent tasks.
  • Clarify any platform limitations if certain features are Windows-only.
GitHub 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 manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented alongside C# and manifest examples without mention of Linux alternatives, and there is no guidance for Linux users on how to perform these tasks via Bash, Azure CLI, or REST APIs.
Recommendations
  • Add equivalent Bash or Azure CLI examples for configuring scaling policies, especially for Linux clusters.
  • Clarify which PowerShell commands (if any) are supported on Linux/macOS, or provide alternatives.
  • Explicitly mention REST API options for auto scaling configuration, if available.
  • Add notes or sections indicating how Linux users can perform these tasks, including links to relevant tools or documentation.
GitHub 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_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent Linux/macOS CLI examples (e.g., Bash, Azure CLI). PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users. Additionally, the PowerShell section precedes any mention of cross-platform tools, and there is no guidance for Linux users on how to perform these tasks.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for Linux/macOS users.
  • Clarify whether PowerShell Core (pwsh) can be used cross-platform, and provide instructions if so.
  • Mention any REST API or SDK alternatives that are platform-agnostic.
  • Reorder examples so that cross-platform options are presented alongside or before Windows-specific tools.
  • Explicitly state if certain operations are only possible via PowerShell on Windows, and suggest workarounds for Linux/macOS users.
GitHub 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, without mentioning Linux equivalents or providing Linux-specific guidance. This creates friction for Linux users seeking parity in upgrade and maintenance procedures.
Recommendations
  • Add links and references to Linux-specific Service Fabric upgrade and configuration documentation, if available.
  • Clarify whether the procedures described apply to both Windows and Linux standalone clusters, or specify any differences.
  • Include examples or guidance for Linux environments where relevant (e.g., patch orchestration, cluster configuration).
  • If Linux standalone clusters are not supported, explicitly state this to avoid confusion.
GitHub 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 using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or bash examples, nor are Linux-native tools or commands mentioned. Windows/PowerShell examples are consistently presented first and exclusively, creating friction for Linux users who may not have access to PowerShell or prefer bash/CLI tools. The section 'Choosing a platform' does acknowledge platform differences, but the practical guidance and examples remain Windows-focused.
Recommendations
  • Add equivalent Linux CLI/bash examples for administrative tasks (e.g., scaling services, creating/removing instances).
  • Mention and link to Linux-native Service Fabric tools or commands where available.
  • Present examples for both Windows and Linux platforms, or clarify when a command is Windows-only.
  • Consider providing platform-neutral guidance or highlighting cross-platform APIs where possible.
GitHub 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 code examples for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell examples are given for service creation and metric configuration, but there are no equivalent CLI or Linux-native examples (such as Azure CLI or Bash). PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before any mention of cross-platform alternatives, and no Linux-specific guidance or parity is provided.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention whether PowerShell commands can be run on PowerShell Core (pwsh) on Linux/macOS, or provide Bash scripting alternatives.
  • Include guidance for Linux users, such as using REST APIs or SDKs in Python/Java, where applicable.
  • Clarify any limitations or differences for Linux clusters versus Windows clusters in Service Fabric, if relevant.
GitHub 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 and C# examples for configuring movement cost in Service Fabric, but does not include equivalent Linux/macOS command-line examples (such as Bash or CLI). PowerShell is presented first in each example section, which may create friction for Linux users. There is no mention of Linux-native tools or cross-platform CLI usage, and the documentation assumes familiarity with Windows-centric tooling.
Recommendations
  • Add Azure CLI or Bash examples for creating and updating Service Fabric services and move costs, if supported.
  • Explicitly mention whether PowerShell commands are cross-platform or Windows-only, and provide alternatives for Linux/macOS users.
  • Consider including references to Service Fabric REST APIs or SDKs usable from Linux environments.
  • Reorder examples so that cross-platform or Linux-native methods are presented alongside or before Windows-specific ones.
GitHub 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 provides extensive PowerShell examples for managing node tags and service requirements, but does not offer equivalent CLI or scripting examples for Linux/macOS users (such as Bash, Azure CLI, or REST API usage). PowerShell is primarily a Windows tool, and its prominence here creates friction for non-Windows users. The documentation mentions REST APIs but does not provide concrete examples or guidance for their use.
Recommendations
  • Add examples using Azure CLI or Bash scripts for managing node tags and service requirements.
  • Provide REST API sample requests and responses for relevant operations.
  • Clarify which PowerShell commands are cross-platform (if any), or explicitly note Windows-only limitations.
  • Consider including a table or section comparing available tooling for Windows, Linux, and macOS environments.
GitHub 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 exhibits Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. There are no Linux-specific examples, tools, or instructions provided, nor is it clarified whether Linux-based standalone clusters are supported or how to scale them.
Recommendations
  • Add examples and instructions for scaling standalone clusters running on Linux, including relevant command-line tools (e.g., bash scripts, sfctl, or REST API usage).
  • Clarify whether standalone Service Fabric clusters can be deployed and scaled on Linux, and if not, explicitly state this limitation.
  • Provide parity in documentation by including Linux-specific guidance or links alongside Windows/PowerShell instructions.
  • Mention cross-platform tools (such as sfctl) where applicable, and show how to use them for cluster scaling operations.
GitHub 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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for upgrading Azure Service Fabric clusters shows mild Windows bias. While most upgrade instructions are platform-neutral, sections such as 'Upgrading OS images for cluster nodes' and references to Patch Orchestration Application (POA) link only to Windows-specific guidance. Additionally, PowerShell is mentioned alongside Azure CLI for cluster management tasks, but Linux-specific tools or examples are not provided. The documentation does not explicitly state whether Linux-based Service Fabric clusters are supported or provide parity guidance for Linux users.
Recommendations
  • Add explicit guidance and links for upgrading OS images on Linux-based Service Fabric clusters, if supported.
  • Provide Linux/macOS-specific examples for certificate management, port opening, and node property configuration using Azure CLI or relevant tools.
  • Clarify whether Patch Orchestration Application (POA) or similar solutions exist for Linux clusters, and link to relevant documentation.
  • Where PowerShell is mentioned, ensure Azure CLI examples are equally prominent and platform-neutral.
  • State cluster OS support matrix early in the article to clarify applicability.
GitHub 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 demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any Azure CLI or Bash equivalents. The application packaging step is described using Visual Studio, a Windows-centric tool, with no mention of cross-platform alternatives. No Linux/macOS-specific instructions or examples are provided, and Windows tools are referenced first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell cmdlets.
  • Provide instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF tooling) instead of only Visual Studio.
  • Mention and show Bash or shell commands for uploading files to Azure Blob Storage (e.g., using az storage blob upload).
  • Clearly indicate which steps are cross-platform and which are Windows-specific, and provide alternatives where possible.
GitHub 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: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation references the Service Fabric SDK schema file using a Windows file path and does not mention Linux or cross-platform equivalents. The overall structure and examples (such as .exe files) are Windows-centric, and there is no explicit mention of Linux tooling, file paths, or packaging non-Windows executables. However, the content does not explicitly exclude Linux, and Service Fabric does support Linux clusters.
Recommendations
  • Add references to Linux file paths for the Service Fabric SDK schema, or clarify if/where it is available on Linux.
  • Include examples using Linux-compatible executables (e.g., ELF binaries, .sh scripts) alongside .exe examples.
  • Mention cross-platform or Linux-specific tooling for packaging and deploying guest executables, if available.
  • Clarify any platform-specific limitations or requirements for guest executables on Linux clusters.
GitHub 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 CLI or Linux-native examples. It assumes the use of PowerShell and Windows tooling for service creation and management, which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for service creation and management, especially for specifying ServicePackageActivationMode.
  • Explicitly mention cross-platform tools (e.g., Azure CLI, REST API) and provide usage examples.
  • Clarify whether PowerShell Core (cross-platform) is supported, or if examples are Windows PowerShell-specific.
  • Where possible, provide bash or shell script equivalents for common operations.
  • Link to Linux/macOS-specific guidance if available.
GitHub 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 notable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned first or exclusively in several sections, and some examples reference Windows services and executables (e.g., FabricHost.exe) without clarifying Linux equivalents. Standalone cluster creation and upgrade instructions are Windows-only, and Linux standalone clusters are not yet supported, but this is clearly stated. CLI tools are mentioned, but PowerShell is often listed first. There are few explicit Linux examples or parity notes, and Linux-specific workflows are not illustrated.
Recommendations
  • Where possible, provide Linux-specific examples and workflows alongside Windows ones, especially for cluster management, health monitoring, and application lifecycle.
  • Mention Linux CLI tools (sfctl) and Bash usage equally with PowerShell, and avoid listing Windows tools first unless contextually appropriate.
  • Clarify differences in service management between Windows and Linux nodes, including which executables/services are used on Linux.
  • Add links to Linux-focused tutorials and documentation where Windows-only instructions are given.
  • Explicitly note feature parity or limitations for Linux throughout, not just in the standalone cluster section.
GitHub 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 or scripting examples. Windows tools (PowerShell, Visual Studio) are mentioned for service configuration, while Linux-specific workflows are not covered. The limitations section notes Linux support is restricted, but the overall guidance and examples favor Windows users.
Recommendations
  • Add Linux CLI (e.g., Bash, Azure CLI) examples for configuring DNS names and services.
  • Include instructions for editing ApplicationManifest.xml and deploying from Linux environments (e.g., using VS Code or command-line tools).
  • Clarify any differences in workflow for Linux users, especially where portal or PowerShell methods are unavailable.
  • Provide guidance for enabling DNS service on Linux clusters via ARM templates, including any required steps or caveats.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium 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 Service Fabric CLI (sfctl) examples for deploying Docker Compose files, but PowerShell commands are presented first and in greater detail. This may create friction for Linux/macOS users, as PowerShell is primarily a Windows tool, and the CLI is cross-platform. There is no explicit mention of Linux/macOS-specific workflows or considerations, though the CLI examples are suitable for those platforms.
Recommendations
  • Present Service Fabric CLI (sfctl) examples before PowerShell, as CLI is cross-platform and more relevant to Linux/macOS users.
  • Explicitly state that sfctl is supported on Linux/macOS and provide installation instructions or a link for those platforms.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, while sfctl is recommended for Linux/macOS.
  • Consider including a short section on Linux/macOS prerequisites or environment setup for Service Fabric Compose deployments.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page on Azure Service Fabric hosting activation and deactivation life cycle is largely platform-neutral in its conceptual explanations. However, the 'Next steps' section directs users to deployment instructions specifically in PowerShell, and an example link for downloading a ServicePackage refers to a PowerShell cmdlet. This creates a subtle Windows bias by implying PowerShell as the primary or only supported tooling for deployment and management, without mentioning Linux or cross-platform alternatives (such as Azure CLI or REST APIs).
Recommendations
  • Add links or references to Linux/macOS-compatible deployment instructions, such as using Azure CLI or REST APIs for deploying and removing applications.
  • Clarify in the 'Next steps' section that PowerShell is one option, and provide parity guidance for Linux users.
  • Where PowerShell cmdlets are referenced, include equivalent commands or workflows for Linux environments, or explicitly state if PowerShell Core is supported cross-platform.
  • Consider mentioning any platform-specific limitations or supported tools for Service Fabric management.
GitHub 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 is heavily focused on Visual Studio workflows (Build/Rebuild/F5/Ctrl+F5/Publish) and references PowerShell modules 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 page assumes Visual Studio usage, which is not available on Linux/macOS, and does not provide alternative approaches for those platforms.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to configure and deploy Service Fabric applications without Visual Studio.
  • Provide examples using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), where applicable.
  • Clarify which aspects of StartupServices.xml are Visual Studio-specific and offer alternatives for non-Windows environments.
  • Mention any limitations or supported workflows for Linux/macOS users up front, so expectations are clear.
GitHub 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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows/PowerShell bias. It references PowerShell as the primary method for retrieving the cluster manifest and links to a PowerShell-based deployment guide as the next step. There are no explicit Linux/bash/CLI examples or references, and Windows/PowerShell tools are mentioned before other options. While .NET and REST are briefly mentioned, Linux users are left to infer their workflow, and no Linux-specific guidance or parity is provided.
Recommendations
  • Add Azure CLI or bash examples for retrieving the cluster manifest and managing the ImageStoreConnectionString.
  • Include links to Linux/macOS-compatible tools or documentation for Service Fabric management.
  • Balance the 'Next steps' section by referencing non-PowerShell deployment guides (e.g., Azure CLI, REST, or SDK-based workflows).
  • Clarify that PowerShell is not required and provide equivalent Linux-friendly instructions where possible.
GitHub 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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides Service Fabric application and service manifest examples, referencing Windows-specific tools and patterns (e.g., .bat files, Windows user accounts, PowerShell module usage) without offering equivalent Linux examples or clarifying cross-platform applicability. The examples and descriptions assume Windows conventions, such as running scripts via Setup.bat and referencing Windows system groups and accounts, but do not mention or demonstrate Linux-compatible alternatives (e.g., shell scripts, Linux user/group management, Linux deployment commands).
Recommendations
  • Add Linux-specific examples alongside Windows ones, such as using .sh scripts instead of .bat for SetupEntryPoint, and clarify how user/group principals map to Linux environments.
  • Explicitly state which manifest features are supported on Linux clusters and provide guidance for Linux deployments (e.g., using Bash scripts, Linux user/group management).
  • When referencing PowerShell modules, also mention or link to CLI or Bash alternatives for Linux/macOS users.
  • Clarify any Windows-only limitations in the manifest features, and highlight cross-platform compatibility where applicable.
GitHub 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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page heavily references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links exclusively to PowerShell cmdlets. There is no mention of Linux or cross-platform equivalents, nor are FabricClient API usage examples shown for non-Windows environments. The focus on PowerShell and Windows tooling creates friction for Linux/macOS users, as Service Fabric supports cross-platform development but the documentation does not reflect this.
Recommendations
  • Add examples using FabricClient APIs in C# or other languages to demonstrate how to perform replica soft delete and restore operations programmatically, which is platform-agnostic.
  • Explicitly mention whether these operations can be performed from Linux/macOS environments, and if so, provide CLI or SDK-based instructions.
  • If there are Azure CLI or REST API equivalents for managing replicas, include those examples.
  • Clarify any limitations or differences for Linux clusters, if applicable.
GitHub 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 extensive PowerShell examples and references, with no equivalent Linux shell or cross-platform CLI examples. Windows/PowerShell tools are mentioned first and exclusively in example sections, creating friction for Linux/macOS users who may not have access to PowerShell or Windows-specific Service Fabric tooling. REST API usage is briefly mentioned but not demonstrated with concrete examples, and there are no references to Linux-native tools or commands.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for health reporting, especially for sending health reports and querying health status.
  • Explicitly mention and demonstrate REST API usage with curl or other cross-platform tools, including sample requests and responses.
  • Clarify which PowerShell commands are available cross-platform (via PowerShell Core) and which are Windows-only, and provide alternatives where needed.
  • Consider referencing or linking to any Linux/macOS Service Fabric tooling or SDKs, if available.
  • Structure example sections so that REST or cross-platform methods are presented before or alongside Windows/PowerShell methods.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.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 a moderate Windows bias. The manifest examples are explicitly based on a Windows Server 2016 container sample, and several instructions and comments reference Windows-specific tools and patterns (e.g., 'winver' for OS build detection, Windows file paths, and certificate handling in the Windows LocalMachine store). There is limited mention of Linux equivalents, and no Linux-specific manifest samples or guidance are provided, despite Service Fabric supporting Linux containers. The documentation does mention that certificates are exposed as PEM files on Linux, but overall, Linux users are left to infer how to adapt the examples.
Recommendations
  • Provide parallel manifest examples based on a Linux container sample, or clarify which elements differ for Linux deployments.
  • Include Linux-specific instructions for tasks such as OS build detection (e.g., using 'cat /etc/os-release' or 'uname -r'), volume mounting paths, and certificate installation.
  • Explicitly state which manifest elements or features are Windows-only and which are cross-platform.
  • Add links to Linux-focused Service Fabric container documentation where appropriate.
GitHub 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 ⚠ī¸ missing_linux_example
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, Windows-specific tools and APIs (e.g., HTTP.sys, netsh, Windows HTTP Server API) are discussed in detail, often before or alongside Kestrel. HTTP.sys is clearly marked as Windows-only, but there are no explicit Linux/macOS usage examples or guidance. Kestrel is recommended for cross-platform scenarios, but Linux-specific instructions, troubleshooting, or parity notes are missing. Windows-centric configuration (e.g., ServiceManifest.xml endpoint registration for HTTP.sys) is explained, but Linux users may lack clarity on equivalent steps or limitations.
Recommendations
  • Add explicit Linux/macOS examples for Kestrel usage, including any OS-specific configuration steps, troubleshooting, or differences in Service Fabric integration.
  • Clarify which sections are Windows-only and which are cross-platform, especially when discussing endpoint configuration and port management.
  • Provide guidance or links for Linux/macOS users on how to debug, deploy, and configure ASP.NET Core services in Service Fabric clusters running on Linux.
  • Mention any limitations or differences for Linux Service Fabric clusters, such as the absence of HTTP.sys and how to handle scenarios where port sharing is needed.
GitHub 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 provides several examples and deployment instructions using PowerShell commands (e.g., New-ServiceFabricApplication) with Windows-style paths, and references to the Service Fabric SDK schema location in 'C:\Program Files\...'. While there is a brief mention of the Linux certificate store location, the majority of operational/deployment examples and tooling references are Windows-centric, with no Linux CLI or cross-platform equivalents provided.
Recommendations
  • Include equivalent Azure CLI or Service Fabric CLI (sfctl) commands for application deployment and parameter overrides, especially for Linux/macOS users.
  • Mention the location of the ServiceFabricServiceModel.xsd schema on Linux, or clarify if it is not applicable.
  • When referencing file paths or tools, provide both Windows and Linux/macOS equivalents where possible.
  • Add explicit notes or links to Linux/macOS deployment guidance, especially in sections that currently only show PowerShell/Windows examples.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.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 references Azure CLI, Azure PowerShell, and ARM templates for deployment, but does not provide explicit Linux/bash examples or mention Linux tools. Azure PowerShell is listed alongside Azure CLI, but there are no bash or shell script examples. Windows-specific scenarios (activation, updates) are mentioned before Linux equivalents, and Windows examples (such as activation and updates) are listed first in outbound connectivity requirements. The only command example is Azure CLI, which is cross-platform, but there are no explicit Linux/macOS shell examples or guidance.
Recommendations
  • Add explicit Linux/bash shell script examples for key migration steps, especially where Azure CLI is used.
  • Ensure Linux-specific scenarios (such as package manager access) are given equal prominence to Windows scenarios in outbound connectivity requirements.
  • Mention Azure CLI as the primary cross-platform tool, and clarify that PowerShell is Windows-centric, with alternatives for Linux/macOS users.
  • Provide links or references to Linux/macOS documentation for relevant Azure VM operations.
  • Where PowerShell is referenced, add equivalent bash/CLI examples for Linux/macOS users.
GitHub 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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for enabling Automatic Zone Balance on Virtual Machine Scale Sets. However, PowerShell (a Windows-centric tool) is given equal prominence to CLI, and there are several examples using PowerShell. The Application Health extension example in PowerShell uses 'ApplicationHealthWindows' as the extension type, while the CLI example uses 'ApplicationHealthLinux', which may cause confusion or friction for Linux users. Additionally, PowerShell examples are presented in all major sections, and the tab order sometimes places PowerShell before CLI, indicating a mild Windows-first bias.
Recommendations
  • Ensure that Linux-focused examples (Azure CLI) are always presented before PowerShell in tab order and narrative.
  • Clarify when to use 'ApplicationHealthLinux' vs 'ApplicationHealthWindows' extension types, and provide both examples in PowerShell and CLI sections.
  • Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add a note or section for macOS users if any steps differ.
  • Review tab ordering to ensure CLI is first, followed by PowerShell, to reduce Windows-first bias.
GitHub 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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is intended for both Windows and Linux virtual machines, as stated at the top. Most command-line examples (Azure CLI, API, PowerShell) are generic and applicable to both OS types. However, the ARM template section only provides a Windows VM example, with no Linux equivalent. Additionally, the ARM template parameters and image references are exclusively for Windows Server, and the Windows image options are listed without mention of Linux images. This creates a subtle Windows bias, especially for users seeking ARM template guidance for Linux VMs.
Recommendations
  • Add an ARM template example for a Linux VM (e.g., Ubuntu or CentOS), including relevant parameters and image references.
  • In the ARM template section, clarify how to modify the template for Linux VMs, such as changing the publisher, offer, and SKU.
  • Consider listing both Windows and Linux image options in the ARM template parameters.
  • Ensure that instructions and examples consistently mention both Windows and Linux where applicable.
GitHub 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, repeatedly references Windows-specific tools and workflows (notably Hyper-V and Convert-VHD PowerShell cmdlet) for creating and converting VHDs. Windows/Hyper-V is mentioned first and most prominently as the example virtualization solution, and Linux-native alternatives (such as qemu-img, VirtualBox, or KVM) are not provided. The instructions for extracting the VHD tarball on Windows recommend using WSL, but do not provide guidance for Linux/macOS users. Critical steps like VHD conversion are only described with Windows/PowerShell tooling, leaving gaps for Linux users.
Recommendations
  • Add Linux-native instructions for creating and converting VHDs (e.g., using qemu-img or VBoxManage).
  • Mention Linux/macOS virtualization solutions (such as KVM, VirtualBox, or QEMU) alongside Hyper-V.
  • Provide explicit examples for extracting the VHD tarball on Linux/macOS (e.g., using tar in a terminal).
  • Include guidance for converting VHDX to fixed VHD on Linux (e.g., qemu-img convert -O vpc).
  • Reorder examples so Linux-native tools are presented first or in parallel with Windows tools.
GitHub 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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ minor_windows_example_priority
Summary
The documentation covers both Windows and Linux VM image creation with Azure Image Builder, and provides parity for most features. However, there is a notable Windows bias in several areas: PowerShell is frequently used for examples (e.g., generating SHA256 checksums, Sysprep commands, image build/cancel operations), Windows customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in more detail and often before Linux equivalents, and Windows-specific tools (Get-FileHash, shutdown, Sysprep) are referenced. Linux examples are present and explained, but Windows tools and patterns are sometimes mentioned first or exclusively (e.g., no Linux restart customizer, PowerShell validator details shown before Shell validator details).
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell commands (e.g., show sha256sum before or alongside Get-FileHash).
  • Ensure Linux examples are given equal prominence and detail, especially in sections where Windows tools are described.
  • Where Windows customizers (e.g., WindowsRestart, WindowsUpdate) are described, clarify Linux alternatives or explicitly state their absence.
  • In validation and customization sections, alternate the order of Windows and Linux examples, or present them side-by-side.
  • Add explicit notes or links for Linux/macOS users where only Windows tools are referenced (e.g., Sysprep, PowerShell).
GitHub 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: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
While the documentation is focused on Linux VMs and provides extensive Azure CLI examples (which are cross-platform), there is a notable bias toward Windows tooling and PowerShell. PowerShell examples are provided in great detail, often with Windows-centric terminology and tools (e.g., 'New-AzStorageBlobSASToken', 'ipconfig' as a commandId, 'myscript.ps1' in examples). REST API and ARM template examples frequently use Windows-style scripts (PowerShell, .ps1) rather than Linux shell scripts (.sh). Some explanations and notes reference Windows-specific behaviors or tools before Linux equivalents, and certain advanced scenarios (e.g., streaming output to blobs) are only illustrated with PowerShell. There are also missing Linux-specific examples for some advanced features.
Recommendations
  • Provide Linux shell script (.sh) examples alongside PowerShell (.ps1) in REST API and ARM template sections.
  • Clarify when PowerShell tools (e.g., New-AzStorageBlobSASToken) are Windows-only and offer Linux alternatives (e.g., Azure CLI or Python SDK for SAS token generation).
  • Ensure commandId examples use Linux-relevant commands (e.g., 'ifconfig', 'ls', 'bash') instead of Windows commands like 'ipconfig'.
  • Add advanced Azure CLI examples for features currently only shown in PowerShell (e.g., streaming output to blobs, parameter passing).
  • Review notes and explanations to avoid referencing Windows behaviors before Linux, or to clearly distinguish OS-specific instructions.
GitHub 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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in image cleanup, but does not mention Linux container base images or provide Linux-specific examples. The configuration examples and descriptions are generic, but the only concrete image examples are Windows-centric. There are no PowerShell or Windows tool references, but the bias is present in the image examples and omission of Linux parity.
Recommendations
  • Add examples of Linux container base images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the 'ContainerImagesToSkip' setting.
  • Clarify whether the cleanup features and settings apply equally to Linux containers and Windows containers.
  • Include a note or section about Linux container image management, especially if there are any differences or considerations.
  • Provide sample configurations or scenarios for clusters running Linux containers.
GitHub 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 support for Azure Service Fabric, including development and deployment. However, Windows development (with .NET SDK, Visual Studio, PowerShell) is described first, while Linux development (Java SDK, Eclipse, Yeoman) is mentioned second. There are no explicit Linux/PowerShell-only examples or tools, but the ordering and emphasis slightly favor Windows.
Recommendations
  • Present Windows and Linux development options in parallel, rather than listing Windows first.
  • Add links to Linux quickstart guides and documentation alongside Windows equivalents.
  • Ensure example workflows and tool references are balanced for both platforms.
  • Consider including a brief comparison table of Windows and Linux development environments.
GitHub Create Pull Request
Virtual Machines Enable InfiniBand on HPC VMs - Azure Virtual Machines | Microsoft Docs ...icles/virtual-machines/extensions/enable-infiniband.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation covers both Linux and Windows, but there is mild Windows bias in the VM extension section, where Azure PowerShell is mentioned as the primary tool for adding extensions, with no mention of Azure CLI or ARM templates. Windows VM extension details are given before Linux in that section. However, Linux examples are provided for manual driver installation and IPoIB configuration, and Linux VM images are highlighted first.
Recommendations
  • Add Azure CLI and ARM template examples for adding VM extensions, alongside PowerShell.
  • Mention Linux tools and workflows equally when discussing VM extension management.
  • Consider presenting Linux and Windows instructions in parallel or with equal prominence.
  • Provide a Windows example for manual driver installation, similar to the Linux example, or clarify if manual install is not recommended on Windows.
GitHub 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
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell (a Windows-centric tool) is often presented before CLI, and some sections (such as querying public IPs) show PowerShell examples before CLI. There are no Linux-specific shell examples (e.g., Bash), but CLI commands are cross-platform. The documentation does not reference Windows-only tools or patterns outside PowerShell, and Linux parity is generally maintained, though minor Windows bias is evident in example ordering and tool emphasis.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell to reduce perceived Windows bias.
  • Explicitly note that Azure CLI commands work on Linux/macOS as well as Windows.
  • Where possible, provide Bash shell script examples for Linux users, especially for tasks involving REST API calls.
  • Clarify in introductory sections that both PowerShell and CLI are supported, and highlight CLI as the default for cross-platform usage.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page exhibits mild Windows bias. The introductory section and terminology focus primarily on 'custom windows images', and the only CLI example provided is in PowerShell. While there are references to Linux custom image creation and Azure CLI for browsing images, the main workflow and examples are Windows-centric, and Linux-specific command-line examples are missing.
Recommendations
  • Clarify that both Windows and Linux custom images are supported, and update language to refer to 'custom images' rather than 'custom windows images' where appropriate.
  • Provide equivalent Linux command-line examples (e.g., Azure CLI or Bash) for role assignment and other operations, alongside PowerShell.
  • Include explicit guidance or links for deploying Linux custom images to Service Fabric Managed Clusters.
  • Ensure ARM template examples and explanations are generic and applicable to both Windows and Linux node types.
GitHub 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. However, Windows-specific tools (IIS, Mirantis Container Runtime, DockerEE) and scenarios (IIS lift and shift) are mentioned before or more prominently than Linux equivalents. Windows container examples and links are sometimes listed before Linux ones, and Windows-specific terminology is used in some sections. Linux examples and tutorials are present, but Windows scenarios are slightly prioritized.
Recommendations
  • Ensure Linux and Windows examples/tutorials are presented in parallel or with Linux examples listed first where appropriate.
  • Add Linux-specific scenarios (e.g., Apache/Nginx lift-and-shift, systemd-based applications) to balance the IIS lift-and-shift Windows scenario.
  • Mention Linux container runtimes and tools (e.g., containerd, Podman) alongside Docker, where relevant.
  • Clarify that Service Fabric supports both Linux and Windows containers equally, and highlight cross-platform parity in capabilities.
  • Where Windows-specific tools are discussed, provide Linux equivalents or note their absence if not applicable.
GitHub 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 is generally platform-neutral, focusing on .NET and Azure Service Fabric concepts. However, in the 'Next steps' section, Windows-centric upgrade tutorials (Visual Studio and PowerShell) are listed before any mention of Linux or cross-platform alternatives. No Linux/macOS-specific examples or tools are referenced, and there are no explicit Linux instructions or parity notes.
Recommendations
  • Add links or references to Linux/macOS-compatible upgrade workflows, such as using Azure CLI or REST APIs.
  • Include examples or notes for developers using .NET Core/.NET 5+ on Linux/macOS, clarifying any platform-specific considerations.
  • If PowerShell is mentioned, also mention Bash or other scripting alternatives for Linux/macOS users.
  • Consider reordering 'Next steps' to avoid Windows-first ordering, or explicitly state cross-platform options.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page is generally platform-neutral, describing Service Fabric concepts applicable to both Windows and Linux. However, there are subtle signs of Windows bias: Windows-specific tools and executables (e.g., FabricHost.exe, Fabric.exe, FabricGateway.exe) are mentioned first and in detail, with less explicit coverage of Linux equivalents. The description of node startup references an 'auto-start Windows service' without clarifying Linux behavior. Executable file types are described as EXE/DLL, which are Windows-centric, and Windows containers are mentioned before Linux containers in some sections.
Recommendations
  • Clarify Linux node startup behavior alongside Windows (e.g., what processes/services are used on Linux nodes).
  • When describing executable file types, mention Linux equivalents (e.g., ELF binaries, .so files) in addition to EXE/DLL.
  • Where Windows-specific tools or services are referenced, add notes or links about Linux equivalents or differences.
  • Ensure container support is described with Linux and Windows parity, mentioning Docker containers on Linux before or alongside Windows containers.
  • Review ordering of examples and terminology to avoid always listing Windows first.
GitHub 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 command-line examples, but consistently presents PowerShell examples directly after CLI and before ARM templates. PowerShell is a Windows-centric tool, and its inclusion alongside CLI (which is cross-platform) is appropriate, but the ordering may subtly prioritize Windows users. No Windows-only tools or patterns are mentioned, and Linux/macOS users can complete all tasks using the CLI. There are no missing Linux examples, but PowerShell is given equal prominence to CLI, which may not reflect the cross-platform usage patterns.
Recommendations
  • Consider presenting Azure CLI examples before PowerShell in each section, as CLI is cross-platform and more widely used among Linux/macOS users.
  • Explicitly note that Azure CLI commands work on Windows, Linux, and macOS, while PowerShell is primarily for Windows users (unless using PowerShell Core).
  • If possible, add brief guidance for macOS/Linux users about installing and using Azure CLI.
  • Maintain parity by ensuring all features shown in PowerShell are also available and demonstrated in CLI.
GitHub 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
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 Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension and custom metrics. However, there are several instances where Windows/PowerShell examples are presented before Linux/Bash equivalents, and Windows-specific extension types (ApplicationHealthWindows) are used in sample code. PowerShell examples are detailed and prominent, and Windows tools/patterns (e.g., PowerShell HTTP server) are included alongside Linux examples. The REST API examples also default to Windows extension types. Overall, Linux parity is present but not always prioritized.
Recommendations
  • Present Linux/Bash examples before Windows/PowerShell examples in each section to avoid 'windows_first' bias.
  • Ensure REST API and JSON configuration samples alternate or default to ApplicationHealthLinux when not OS-specific.
  • Clarify in sample code and tables that both ApplicationHealthLinux and ApplicationHealthWindows are supported, and provide explicit Linux-focused samples.
  • Expand troubleshooting and verification examples to include Linux-specific commands (e.g., systemctl, netstat) where appropriate.
  • Review sample output snippets to ensure they reference both Linux and Windows extension types equally.
GitHub 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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations (attach, detach, move VMs), but consistently includes PowerShell examples alongside CLI, and in some cases, PowerShell examples are shown after CLI but before portal instructions. PowerShell is a Windows-centric tool, and its inclusion may signal a Windows bias, especially since Bash or Linux shell scripting alternatives are not mentioned. However, Azure CLI is cross-platform and the CLI examples use Linux VM images (e.g., Ubuntu2204), indicating some Linux parity. There are no Windows-only tools or patterns, and the documentation does not exclusively mention Windows tools. The bias is minor and does not prevent Linux/macOS users from completing the tasks.
Recommendations
  • Consider explicitly mentioning that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add brief notes or links for Linux/macOS users clarifying that Azure PowerShell is available on Linux, but Bash scripting is also possible with Azure CLI.
  • Ensure that CLI examples use both Linux and Windows VM images to show parity.
  • If possible, provide Bash shell scripting examples for common tasks, or clarify that Azure CLI commands can be run in Bash.
  • In troubleshooting sections, ensure links to migration guides (e.g., unmanaged to managed disks) include both Windows and Linux documentation.
GitHub 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 instructions for rolling upgrades with MaxSurge on Azure Virtual Machine Scale Sets. It includes examples for the Azure Portal, Azure CLI, PowerShell, and ARM templates. While the CLI and ARM template examples are cross-platform, the PowerShell example is Windows-centric, and PowerShell is presented as a primary method alongside CLI. Additionally, PowerShell is listed before ARM templates, which may subtly prioritize Windows tooling.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and suitable for Linux/macOS users, while PowerShell is Windows-centric.
  • Consider listing CLI examples before PowerShell to emphasize cross-platform accessibility.
  • Add explicit notes or guidance for Linux/macOS users, such as recommending Azure CLI or ARM templates.
  • If possible, provide Bash shell scripting examples for common tasks.
  • Ensure parity in documentation structure and visibility for Linux/macOS-friendly tools.
GitHub 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 is generally neutral and cross-platform, describing orchestration modes for Azure Virtual Machine Scale Sets without explicit Windows bias. However, in the 'Managed Identity' row of the comparison table, the link for configuring User Assigned Identity points to a Windows VMSS-specific guide, and the order of mention for Linux and Windows in 'Mix operating systems' puts Windows first. There are no PowerShell-only examples, Windows tools, or missing Linux examples. The Azure CLI is used for command-line examples, which is cross-platform.
Recommendations
  • Update the 'Managed Identity' link to reference both Linux and Windows VMSS configuration guides, or use a neutral landing page.
  • In 'Mix operating systems', mention Linux first or clarify parity.
  • Review linked guides and ensure Linux parity in referenced documentation.
  • Explicitly state that all features and examples apply equally to Linux and Windows unless otherwise noted.
GitHub 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 'Use Azure PowerShell'), Windows-specific tooling is highlighted separately. The ordering of examples sometimes places PowerShell before Linux-focused tools, and there is no explicit Bash or Linux shell example (though Azure CLI is cross-platform). The Resource Manager template section does link to both Linux and Windows quick-starts, but overall, Windows tools and patterns are mentioned as much as Linux equivalents.
Recommendations
  • Ensure that Azure CLI examples are shown first, as CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit Bash shell examples where relevant, especially for update operations.
  • Clarify that Azure PowerShell is Windows-centric and recommend Azure CLI for Linux/macOS users.
  • Where possible, provide parity in example scripts for Linux and Windows environments.
  • Consider adding a note about cross-platform support for Azure CLI and ARM templates.
GitHub 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 provides both Azure CLI and Azure PowerShell examples for all major extension management tasks. However, Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) may create friction for Linux/macOS users. Additionally, in some sections, PowerShell examples are presented before or equally with CLI, rather than prioritizing CLI for a Linux-focused audience. No critical Linux information is missing, and all examples are relevant to Linux VMs, but the parity could be improved by emphasizing CLI and de-emphasizing PowerShell.
Recommendations
  • Prioritize Azure CLI examples before PowerShell in all code tabs and narrative, as CLI is cross-platform and native for Linux users.
  • Clearly indicate that Azure PowerShell is optional and primarily for users who prefer it, rather than presenting it as an equal or default choice.
  • Where possible, provide Bash-native or shell script examples for common extension operations, especially for troubleshooting or log analysis.
  • Consider omitting PowerShell examples from the main flow, or placing them in expandable sections, to reduce cognitive load for Linux-focused readers.
GitHub 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 VM GPU driver installation, but includes PowerShell examples for deploying the extension and troubleshooting, and presents PowerShell before Azure CLI in some sections. While Azure CLI and ARM template examples are provided, the inclusion and ordering of PowerShell (a Windows-centric tool) may create friction for Linux users. No Windows-specific tools or patterns are exclusively mentioned, and Linux-specific commands and troubleshooting are well covered.
Recommendations
  • Move Azure CLI examples before PowerShell in all sections to prioritize Linux-native tooling.
  • Clearly indicate that PowerShell is optional and primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
  • Consider adding Bash script examples for common operations, especially for troubleshooting.
  • Where PowerShell is used, provide equivalent Bash or shell commands for Linux users.
  • Review screenshots and UI instructions to ensure they are Linux-appropriate (though current ones appear to be).
GitHub 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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is focused on Linux, but there are some minor Windows biases. Azure PowerShell deployment instructions and troubleshooting are presented before Azure CLI equivalents, and PowerShell examples are given with more detail. The note about Key Vault access policy links to a Windows VM-specific article, even though the extension is Linux-focused. However, all critical tasks are fully documented for Linux users, and Linux-specific paths, tools, and behaviors are clearly described.
Recommendations
  • Present Azure CLI instructions before PowerShell, as CLI is cross-platform and preferred by many Linux users.
  • Add links to Linux-specific managed identity and Key Vault access policy configuration guides, rather than referencing Windows VM portal articles.
  • Ensure troubleshooting sections highlight CLI commands equally or before PowerShell.
  • Where possible, clarify that PowerShell is optional and not required for Linux users.
GitHub 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 parity between Linux and Windows in most sections, including CLI and REST examples. However, in the PowerShell section, Windows is presented first and as the default, with Linux mentioned only as an alternative. Additionally, PowerShell examples are shown alongside CLI, but CLI is not shown first or exclusively. Overall, the bias is minor and does not prevent Linux/macOS users from completing the task.
Recommendations
  • In PowerShell examples, show Linux as the default or provide a Linux-specific example first, or clarify that PowerShell can be used for both OS types.
  • Ensure that CLI examples (which are cross-platform) are presented before PowerShell, or at least equally, to avoid implying Windows is the default.
  • Explicitly state that all steps and tools (CLI, REST) are fully supported on Linux/macOS, and provide links to Linux-specific guidance where relevant.
  • Where possible, provide sample commands for both Linux and Windows in PowerShell and CLI sections.
GitHub Create Pull Request
Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.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 checking vCPU quotas. However, PowerShell is featured as a primary method alongside CLI, and its inclusion may be seen as Windows-centric since PowerShell is most commonly used on Windows. The CLI example is cross-platform, but PowerShell is presented as an equal alternative, which may create friction for Linux/macOS users who rarely use PowerShell. Additionally, the PowerShell section follows the CLI section, so Windows tools are not shown first, but their presence is notable.
Recommendations
  • Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
  • Explicitly mention that PowerShell is primarily for Windows users, or note its availability on Linux/macOS if relevant.
  • Consider adding Bash or shell script examples if applicable, or reinforce CLI as the main method.
  • Add a short note about CLI's cross-platform compatibility to guide non-Windows users.
GitHub 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 covers preparing Red Hat Enterprise Linux VHDs for Azure using multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, in most sections, the instructions for Hyper-V (a Windows-only hypervisor) are presented first, and references to Windows tools (Hyper-V Manager, convert-vhd cmdlet) appear before Linux alternatives. Linux hypervisors (KVM, VMware) are covered thoroughly and with parity, but Windows-centric tools and ordering are prioritized.
Recommendations
  • Reorder sections so that Linux-native hypervisors (KVM, VMware) are presented before Hyper-V, or at least in parallel.
  • When mentioning disk conversion tools, list Linux tools (qemu-img) before or alongside Windows tools (Hyper-V Manager, convert-vhd).
  • Clarify that Hyper-V steps are only required for users on Windows, and highlight Linux-native workflows for Linux/macOS users.
  • Consider a summary table at the top showing all supported hypervisors and their OS requirements, so Linux users can quickly find relevant instructions.
GitHub 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 is focused on Linux VM time synchronization in Azure and provides comprehensive 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. This could create a perception of Windows-first bias, but all technical guidance is Linux-centric.
Recommendations
  • Move or minimize Windows Server 2016 discussion to a background or context section, emphasizing that it is relevant only as the Azure host OS.
  • Begin the page with Linux-specific time sync concepts and configuration options, referencing Windows only as necessary for host context.
  • Ensure that Linux documentation links and examples are presented before any Windows references.
  • Clarify that all configuration steps and examples are for Linux, and that Windows references are for infrastructure context only.
GitHub Create Pull Request
Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation covers both Linux and Windows VM images, but there are several subtle signs of Windows bias. PowerShell examples are provided alongside Azure CLI, but PowerShell is often shown second and referenced frequently. Some links and references (such as image finding and uploading) point to Windows-specific pages first or separately, and PowerShell is mentioned in feature examples and sharing scenarios. However, Linux equivalents are generally present, and the overall guidance is cross-platform.
Recommendations
  • Ensure that Linux and Windows examples are presented with equal prominence, alternating their order or grouping them together.
  • Where PowerShell is referenced, ensure Bash/CLI examples are equally detailed and linked.
  • Review linked pages to ensure Linux-specific guidance is as accessible as Windows guidance.
  • Explicitly state that all features and procedures apply equally to Linux and Windows, unless otherwise noted.
  • Consider adding sample Bash scripts or Linux command-line workflows where PowerShell scripts are shown.
GitHub Create Pull Request