← Back to Dashboard
290
Pages Scanned
92
Pages Flagged
290
Changed Pages
31.7%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-02-13 00:00:08

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 290

Files Completed: 290

Problematic Pages

92 issues found
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation for Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples use Windows-specific images (nanoserver), Windows file paths, and Windows commands (cmd, echo, type, ping). There are no examples or guidance for Linux containers or Linux-based workloads, and the ApplicationManifest and ServiceManifest snippets exclusively reference Windows paths and conventions. The introductory note explicitly states the example assumes familiarity with Windows container applications, but does not mention Linux equivalents or alternatives.
Recommendations
  • Add examples using Linux containers (e.g., Ubuntu or Alpine images) with Linux shell commands.
  • Provide guidance for specifying Initializer CodePackages in Linux-based Service Fabric clusters.
  • Include ApplicationManifest and ServiceManifest snippets using Linux file paths and mount points.
  • Clarify whether Initializer CodePackages are supported for Linux containers, and if so, provide parity in documentation.
  • If Initializer CodePackages are Windows-only, state this clearly at the top to avoid confusion.
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 clearly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and guidance are implicitly Windows-centric. There are no Linux instructions or parity, and the feature is Windows-only at this time.
Recommendations
  • Explicitly state at the top of the page that the reverse proxy is a Windows-only feature and is not supported on Linux clusters.
  • If/when Linux support is added, provide equivalent Linux examples and configuration steps.
  • Link to alternative solutions or workarounds for Linux clusters, if any exist.
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
The documentation page initially claims Service Fabric clusters run on both Windows Server and Linux, but all subsequent details, examples, and supported OS lists focus exclusively on Windows. Windows authentication, Windows security, and Windows Server versions are discussed, with no Linux-specific instructions, examples, or supported OS versions. The page mentions Linux in the introduction but omits Linux details throughout, creating confusion and friction for Linux users.
Recommendations
  • Clarify in the introduction and supported OS section whether Linux is actually supported for standalone clusters, or if Linux support is planned but not yet available.
  • If Linux is supported, add Linux-specific instructions, examples, and supported OS versions throughout the page.
  • If Linux is not supported, update the introduction to avoid misleading statements and clearly state that standalone clusters are Windows-only.
  • Ensure parity in security, scaling, and upgrade sections by describing Linux-specific tools, authentication methods, and procedures where applicable.
GitHub Create Pull Request
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on Windows-centric tools, specifically Visual Studio and PowerShell. All upgrade instructions and examples reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS alternatives or cross-platform CLI tools. There are no examples or guidance for performing upgrades using Linux-compatible tools or environments, and Windows tools are presented first and exclusively.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST API.
  • Mention and provide guidance for Linux/macOS users, including any available Service Fabric SDKs or command-line utilities.
  • Clarify whether the Visual Studio tooling is Windows-only and, if so, direct Linux/macOS users to alternative workflows.
  • Include PowerShell Core (pwsh) compatibility notes if relevant, or specify if only Windows PowerShell is supported.
  • Provide sample upgrade parameter configurations using JSON or YAML if supported, for broader platform compatibility.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides several manual scaling instructions using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning equivalent Linux/macOS commands or Service Fabric CLI usage. Windows/PowerShell-based workflows are described first and exclusively in step-by-step guides, while Linux alternatives are not presented, creating friction for non-Windows users.
Recommendations
  • Add equivalent instructions for Linux/macOS environments, using Service Fabric CLI (sfctl) or REST API where applicable.
  • Explicitly mention cross-platform tooling and provide examples for both PowerShell (Windows) and CLI/REST (Linux/macOS) in all procedural steps.
  • Clarify which commands are Windows-only and offer alternatives for Linux clusters.
  • Reorder examples so that platform-neutral or Linux instructions are presented alongside or before Windows-specific ones where possible.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and examples before Linux equivalents (SFCTL/CLI), with more detailed coverage and example formats for PowerShell and Visual Studio. The SFCTL section is present and covers Linux CLI usage, but is positioned after Windows tools and is less prominent. There are no Linux-specific examples or parity in example formatting (e.g., PowerShell has hashtable examples, SFCTL has JSON, but no direct comparison).
Recommendations
  • Reorder sections so that cross-platform tools (SFCTL/CLI) are presented before or alongside Windows tools.
  • Provide example command invocations for SFCTL in the same detail as PowerShell, including parameter formats and sample JSON.
  • Explicitly note which tools are cross-platform and which are Windows-only, to help users choose the right tool.
  • Add a comparison table showing parameter mapping between PowerShell and SFCTL for clarity.
  • Include Linux/macOS-specific notes or examples where relevant, especially for CLI usage.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page references Windows-centric tools and patterns, such as Visual Studio and PowerShell, in the 'Next steps' section. These are presented as primary upgrade methods, with no mention of Linux/macOS equivalents (e.g., CLI, Bash, cross-platform editors). The serialization discussion is tied to C# and .NET, which are cross-platform, but the upgrade guidance leans toward Windows workflows.
Recommendations
  • Add instructions or links for upgrading Service Fabric applications using Azure CLI or Bash scripts, which are cross-platform.
  • Mention cross-platform editors (such as VS Code) alongside Visual Studio.
  • Clarify whether PowerShell instructions are compatible with PowerShell Core on Linux/macOS, or provide Bash/CLI alternatives.
  • Explicitly note that Service Fabric development and upgrades can be performed on Linux/macOS, if applicable, and provide relevant guidance.
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 recommendations that prominently feature Azure PowerShell, including links to PowerShell modules for cluster management tasks. While Azure CLI and ARM/Bicep are mentioned, PowerShell is given as the primary example for key operations (delete, restart, reimage), and no explicit Linux/macOS command-line examples (such as Azure CLI usage) are provided for these tasks. The 'Best practices' section lists PowerShell before CLI, and PowerShell-specific links are used for critical actions.
Recommendations
  • Add explicit Azure CLI examples for deleting NodeTypes, restarting, and reimaging scale sets, alongside PowerShell examples.
  • Ensure that CLI and PowerShell are presented equally, or that CLI examples are shown first, as CLI is cross-platform.
  • Clarify that all recommended tools (Azure CLI, ARM templates, Bicep) are fully supported on Linux/macOS.
  • Where possible, provide links to CLI documentation for the same actions currently linked to PowerShell modules.
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 describes the architecture of Azure Service Fabric in a platform-neutral way, but in the Management subsystem section, it specifically mentions 'PowerShell cmdlets' as a primary management interface, without mentioning Linux or cross-platform equivalents (such as Azure CLI or REST APIs). This creates a Windows-first impression and suggests Windows tooling is the default for management tasks, even though Service Fabric supports Linux clusters and cross-platform management.
Recommendations
  • Mention Azure CLI and REST API as cross-platform management options alongside PowerShell.
  • Clarify that management tasks can be performed from Linux/macOS using CLI or API, not just PowerShell.
  • Provide links or references to documentation for Linux management tools and examples.
  • Ensure examples and tooling references are balanced between Windows and Linux/macOS environments.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides general information about Azure Service Fabric node types and VM scale sets, but exhibits subtle Windows bias. The JSON snippet for the Service Fabric VM extension uses a Windows-style file path (D:\\SvcFab) as the default for 'dataPath', and certificate store references (x509StoreName) are Windows-centric. The 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-specific tasks and tools, without mentioning Linux equivalents or SSH guidance. Linux node type is referenced in the extension ('ServiceFabricLinuxNode'), but Linux-specific examples or guidance are missing.
Recommendations
  • Provide Linux-specific examples for connecting to cluster nodes (e.g., SSH instructions alongside RDP/PowerShell).
  • Clarify that 'dataPath' should use Linux-style paths when deploying Linux node types (e.g., /var/svcfab).
  • Add guidance for managing admin credentials and port ranges on Linux VMs (e.g., using Azure CLI or SSH).
  • Mention Linux certificate storage locations or alternatives to x509StoreName for Linux deployments.
  • Balance 'Next steps' links by including Linux-focused documentation or scripts.
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 provides general guidance for upgrading Azure Service Fabric clusters, but exhibits mild Windows bias. Windows-specific tools (PowerShell) are mentioned alongside Azure CLI, but Linux equivalents (e.g., Bash, Linux-specific guidance) are not explicitly referenced. The section on OS image upgrades links only to Windows patching guidance, omitting Linux node patching. Windows terminology and tools are mentioned first or exclusively in some areas, and Linux/macOS users may need to infer their workflow.
Recommendations
  • Explicitly mention Linux/macOS support where applicable, especially for Service Fabric clusters running on Linux nodes.
  • Provide Linux-specific examples (e.g., Bash commands) alongside PowerShell and Azure CLI, or clarify that Azure CLI commands work cross-platform.
  • Add links or sections for patching/upgrading Linux node OS images in Service Fabric clusters, not just Windows.
  • Ensure that references to tools (PowerShell/Azure CLI) clarify their cross-platform availability, or provide parity in examples.
  • Review all guidance for assumptions that clusters are Windows-only, and clarify when guidance applies to both Windows and Linux clusters.
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 ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides only PowerShell-based deployment instructions and command-line examples, with no mention of Linux/macOS equivalents (such as Azure CLI or Bash). Windows tools and patterns (e.g., RDP, Windows directory paths, PowerShell syntax) are referenced exclusively and shown first. There are no Linux-specific examples or guidance, which creates friction for non-Windows users.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps, as Azure CLI is cross-platform.
  • Include Bash shell examples for template deployments where relevant.
  • Mention SSH as a method for accessing VMs/jump boxes, not just RDP.
  • Use generic directory paths or note differences for Linux/macOS users.
  • Clearly indicate that PowerShell is just one option, and provide links to Azure CLI documentation.
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'), without offering equivalent Linux/macOS CLI or REST API examples. This suggests a bias toward Windows environments and tools, potentially creating friction for Linux/macOS users who may use Service Fabric CLI (sfctl) or REST APIs instead.
Recommendations
  • Add equivalent Linux/macOS examples using Service Fabric CLI (sfctl) or REST API calls for health queries.
  • Mention cross-platform management tools and clarify which commands are available on each OS.
  • Where possible, provide both Windows (PowerShell) and Linux/macOS (bash/sfctl/REST) examples side-by-side.
  • Explicitly note any limitations or differences in tooling between platforms.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell example for deploying Service Fabric applications, which is Windows-centric. The schema file path references a Windows directory first. Linux-specific information is limited to a single note about certificate storage, and Linux deployment examples or CLI equivalents are missing.
Recommendations
  • Add equivalent Linux deployment instructions using Azure CLI or Service Fabric CLI (sfctl).
  • Provide Linux file path examples for schema files alongside Windows paths.
  • Include notes or examples for managing endpoints and certificates on Linux clusters, such as using Kestrel or configuring certificates in /var/lib/sfcerts.
  • Ensure that PowerShell examples are accompanied by cross-platform alternatives.
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 Template as migration tools, but does not provide explicit Linux/bash examples or parity for PowerShell commands. Windows-specific scenarios (activation, updates) are mentioned before Linux equivalents, and PowerShell is listed before CLI in some places. There are no explicit Linux/macOS-focused migration steps or examples, and the CLI example is minimal and not clearly cross-platform.
Recommendations
  • Provide explicit bash/Linux/macOS examples alongside PowerShell, especially for migration steps.
  • Ensure Azure CLI examples are clearly cross-platform and not just shown as an alternative to PowerShell.
  • Mention Linux package manager connectivity needs before or alongside Windows activation/update scenarios.
  • Clarify that all steps can be performed from Linux/macOS using Azure CLI or ARM templates.
  • Add links or references to Linux/macOS-specific documentation where relevant.
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 provides extensive PowerShell examples and references Windows-specific tools (such as the Key Vault VM extension for Windows and S-channel APIs). Windows terminology and mechanisms are frequently mentioned first or exclusively, and Linux-specific guidance or parity is not provided for certificate provisioning, management, or automation. The Key Vault VM extension is described only for Windows, and there are no Bash/CLI or Linux-native examples for certificate enrollment, provisioning, or rotation.
Recommendations
  • Add equivalent Bash/CLI examples for certificate enrollment and management, especially for Key Vault operations.
  • Document the Key Vault VM extension for Linux, or clarify its availability and usage for Linux VM/VMSS nodes.
  • Provide guidance for certificate provisioning and autorollover in Service Fabric clusters hosted on Linux (if supported), including relevant tools and automation patterns.
  • Explicitly note any Windows-only limitations and offer alternative approaches for Linux/macOS users where possible.
  • Ensure troubleshooting and FAQ sections include Linux scenarios and commands.
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 provides detailed conceptual and configuration guidance for X.509 certificate-based authentication in Service Fabric clusters, but exhibits a moderate Windows bias. Windows-specific terminology and tools (e.g., 'LocalMachine\My' certificate store, Win32 CryptoAPI, CAPI2 logging, error codes, and troubleshooting steps) are mentioned first or exclusively in several places. Linux equivalents are referenced only briefly or parenthetically, and there are no concrete Linux-specific examples or troubleshooting steps. This may create friction for Linux users, especially when interpreting certificate store paths, error diagnostics, or when following troubleshooting advice.
Recommendations
  • Provide Linux-specific examples alongside Windows ones, especially for certificate store paths (e.g., expand on the mention of '/var/lib/sfcerts').
  • Include Linux troubleshooting steps and log locations, not just Windows Event Log and CAPI2 logging.
  • When referencing Windows APIs (e.g., Win32 CryptoAPI), clarify the equivalent behavior or configuration on Linux.
  • List Linux and Windows paths/tools in parallel, not just as parentheticals after Windows-first explanations.
  • Add a section or callouts for common Linux-specific certificate issues and how to resolve them.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in the cleanup process, and mentions Windows images before Linux equivalents. There are no explicit Linux container image examples or references, and the documentation does not clarify Linux-specific behaviors or provide parity examples for Linux container images.
Recommendations
  • Add examples referencing common Linux container images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the 'ContainerImagesToSkip' setting.
  • Clarify whether the cleanup process applies equally to Linux containers and Windows containers, and note any differences.
  • Provide guidance or examples for Linux-based Service Fabric clusters, if applicable.
  • Mention Linux container image management patterns or considerations alongside Windows examples.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page primarily discusses deploying custom Windows images in Service Fabric Managed Clusters, with Windows terminology and PowerShell examples presented. While Linux is referenced in links and some concepts, Windows is mentioned first and PowerShell is used for role assignment, with no equivalent Linux CLI example provided. The ARM template examples are generic, but the focus and examples are Windows-centric.
Recommendations
  • Add explicit Linux-focused examples and clarify Linux support for custom images in Service Fabric Managed Clusters.
  • Provide Azure CLI commands for role assignment alongside PowerShell examples.
  • Mention Linux image types and marketplace images equally with Windows, and clarify any limitations or parity.
  • Ensure that links to Linux documentation are as prominent as Windows links.
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 (a Windows-centric tool) without mentioning Linux/macOS alternatives. There are no Linux CLI or cross-platform examples for cluster operations, and Windows tools/patterns are mentioned first or exclusively.
Recommendations
  • Add equivalent Linux/macOS command-line examples (e.g., using sfctl or Azure CLI) for cluster operations.
  • Clarify whether Service Fabric Explorer is available cross-platform or suggest alternatives for Linux/macOS users.
  • Where PowerShell is used, provide Bash or cross-platform CLI equivalents if possible.
  • Explicitly note any limitations or differences for Linux clusters, if relevant.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides step-by-step instructions for configuring and modifying Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. However, all CLI/scripted examples are exclusively in PowerShell, with no mention of Azure CLI (az) or Bash scripting. This creates friction for Linux/macOS users, as PowerShell is not the default or preferred tool on those platforms. Additionally, the documentation refers to PowerShell cmdlets without clarifying cross-platform support or offering alternatives.
Recommendations
  • Add Azure CLI (az) command examples for all operations currently shown only with PowerShell, such as adding, removing, and scaling node types.
  • Explicitly state whether the PowerShell cmdlets used are supported on PowerShell Core (cross-platform) or only on Windows PowerShell.
  • Where possible, provide Bash scripting examples or clarify that ARM template deployment can be performed with az CLI on any platform.
  • Reorder sections or provide parallel examples so that Linux/macOS users see relevant options without needing to adapt Windows-centric instructions.
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 predominantly references PowerShell cmdlets (Az PowerShell, AzSF PowerShell) for managing Service Fabric resources, with no mention of Linux/macOS equivalents or usage of Azure CLI except for a single az resource example. This creates friction for users on Linux or macOS, as PowerShell is traditionally Windows-centric and not the default shell on those platforms.
Recommendations
  • Provide equivalent Azure CLI commands for all management operations, as Azure CLI is cross-platform and preferred on Linux/macOS.
  • Explicitly state that PowerShell cmdlets can be run on Linux/macOS if supported, or provide installation guidance.
  • Reorder examples to show Azure CLI usage first or alongside PowerShell, ensuring parity.
  • Clarify any platform-specific limitations or requirements for the AzSF PowerShell module.
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, primarily in the 'WARNING' section recommending Visual Studio and referencing a Windows file path for schema validation. It also mentions the ServiceFabric PowerShell module as a way to create service instances, without referencing Linux equivalents or cross-platform tools. However, the core content (manifest XML, concepts) is platform-neutral.
Recommendations
  • Provide instructions for validating XML schema on Linux/macOS, such as using VS Code, xmllint, or other cross-platform editors/tools.
  • Mention cross-platform deployment tools (e.g., Azure CLI, sfctl) alongside PowerShell.
  • Clarify that Service Fabric development and deployment can be performed on Linux clusters and provide links or examples for Linux users.
  • Avoid referencing Windows file paths exclusively; if schema files are available on Linux, specify their location.
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 frequently references PowerShell cmdlets and Windows-specific tools (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType, Remove-ServiceFabricApplicationPackage) alongside .NET APIs and REST operations. PowerShell examples are consistently provided, but Linux equivalents (such as Azure CLI or sfctl) are not mentioned in the main lifecycle steps, despite a brief link to CLI documentation at the top. Windows tools and patterns are often listed first, and there is no explicit guidance or examples for Linux/macOS users, which creates friction for those not on Windows.
Recommendations
  • Add explicit Azure CLI and sfctl command examples for each lifecycle operation (deploy, upgrade, remove, etc.), not just REST or PowerShell.
  • Where PowerShell cmdlets are referenced, include corresponding Linux/macOS-friendly commands and clarify cross-platform support.
  • Reorder tool mentions so that cross-platform options (REST, CLI) are listed before or alongside Windows-specific tools.
  • Add a section or note clarifying which tools are supported on Linux/macOS and how to accomplish the same tasks.
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 page for Service Fabric application upgrades exhibits notable Windows bias. PowerShell is the only CLI example provided, and references to Windows-specific tools (e.g., http.sys, PowerShell cmdlets) are prominent. There are no Linux or cross-platform CLI examples (such as Azure CLI, REST API, or Service Fabric CLI), nor are Linux-specific upgrade workflows discussed. References to upgrade tutorials and troubleshooting are also Windows-centric, with Visual Studio and PowerShell mentioned exclusively.
Recommendations
  • Add equivalent Linux/macOS examples using Service Fabric CLI (sfctl), Azure CLI, or REST API for application upgrades.
  • Mention cross-platform tools and workflows alongside Windows tools, not just after or instead of them.
  • Clarify which features or steps are Windows-only and provide Linux alternatives where possible.
  • Include links to Linux/macOS-specific tutorials and troubleshooting guides.
  • Ensure that upgrade scenarios and health checks are described in a platform-neutral way unless they are inherently Windows-specific.
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 covers monitoring for Azure Service Fabric clusters on both Windows and Linux, but there is a notable Windows bias in several areas. Windows-specific tools (such as EventStore APIs and Diagnostics Agent) are mentioned first or exclusively, with Linux equivalents referenced later or in less detail. Some examples and tutorials focus on Windows clusters or .NET applications, with Linux-specific guidance often relegated to links or brief notes. The EventStore APIs are Windows-only, and Windows event channels (ETW/Event Viewer) are described in detail, while Linux channels (LTTng/Syslog) are mentioned but not explained as thoroughly. Linux configuration steps and examples are less prominent.
Recommendations
  • Provide Linux-specific examples and tutorials with equal prominence to Windows ones, especially for cluster and infrastructure monitoring.
  • Expand explanations of Linux event channels (LTTng/Syslog) and their configuration, matching the detail given to Windows (ETW/Event Viewer).
  • Include Linux-focused sample queries and alert rules, and clarify any differences in setup or available metrics.
  • Ensure that references to tools and agents (e.g., Diagnostics Agent, Azure Monitor agent) include clear Linux instructions and links.
  • Add more examples for application monitoring using non-.NET stacks (e.g., Java, Node.js) on Linux clusters.
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 ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates notable Windows bias by exclusively providing Windows container examples (using Windows NanoServer images and Windows-specific commands), referencing Windows container compatibility, and only mentioning PowerShell and C# tools for querying deployment status. No Linux container examples, Linux commands, or cross-platform querying methods are provided, despite Service Fabric supporting containers in general.
Recommendations
  • Add equivalent Linux container examples (e.g., using Ubuntu or Alpine images) to demonstrate RunToCompletion semantics for Linux workloads.
  • Include Linux shell commands (such as Bash or CLI tools) for querying deployment status, or reference cross-platform Service Fabric CLI tools.
  • Clarify in the introduction whether RunToCompletion semantics are supported for Linux containers and, if so, provide guidance for Linux users.
  • Ensure examples and terminology are inclusive of both Windows and Linux environments where applicable.
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 provides a general overview of Service Fabric application security, but several sections show a Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned with more detail or first, while Linux equivalents are missing or only briefly referenced. Examples and guidance for Linux clusters are limited, and some features (like disk encryption) reference Windows tools (PowerShell, BitLocker) without Linux parity or links.
Recommendations
  • Add explicit Linux examples and guidance for securing Service Fabric clusters, including disk encryption and certificate management.
  • Mention Linux tools and patterns (e.g., dm-crypt, LUKS, Linux user accounts) alongside Windows features, or clarify feature parity.
  • Provide links to Linux-specific documentation or third-party resources where Azure-native solutions are not available.
  • Ensure that sections referencing Windows tools (e.g., PowerShell, BitLocker) also reference Linux equivalents or note limitations.
  • Where features are Windows-only, clearly state this to avoid confusion.
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, with no equivalent CLI or Linux/macOS instructions. All command-line guidance is given in PowerShell syntax, and Windows tooling (Visual Studio, PowerShell cmdlets) is mentioned first or exclusively. There is no mention of cross-platform alternatives such as Azure CLI, Bash, or Linux/macOS-compatible tools, despite Service Fabric supporting Linux clusters and cross-platform management.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlet usages, especially for service creation, updates, and upgrades.
  • Explicitly note which PowerShell commands can be run on Linux/macOS (using PowerShell Core), and provide Bash or shell script alternatives where possible.
  • Include guidance for managing Service Fabric applications on Linux clusters, referencing relevant tools and patterns.
  • Mention Visual Studio Code as a cross-platform IDE alongside Visual Studio.
  • Clarify any Windows-only limitations for features or commands, and provide Linux/macOS parity notes where applicable.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for on-demand backup in Azure Service Fabric is heavily biased toward Windows/PowerShell usage. All code examples use PowerShell, including REST API calls, and there is no mention of Linux/macOS-compatible tools or shell commands (such as Bash, curl, or Azure CLI). The prerequisite section requires installation of a PowerShell module, and there are no instructions for Linux users or alternative approaches. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to trigger backups and track progress using standard Linux tools.
  • Mention and provide guidance for using Azure CLI (az) where possible, as it is cross-platform.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all platforms, or if there are alternatives for Linux/macOS.
  • Reorganize examples so that cross-platform methods (REST API, Azure CLI) are presented before or alongside PowerShell examples.
  • Explicitly state platform requirements and provide links to PowerShell installation instructions for Linux/macOS if PowerShell is required.
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, but the 'File share' backup storage section exclusively references Windows-style file shares (\\server\share) and Integrated Windows Authentication, without mentioning Linux-compatible alternatives or SMB mounting instructions for Linux/macOS. Windows authentication patterns are described first and in detail, while no Linux-specific guidance or examples are provided for on-premises backup storage.
Recommendations
  • Add instructions or examples for configuring file share backup storage using SMB mounts on Linux/macOS clusters.
  • Mention Linux-compatible authentication options (e.g., username/password, Kerberos, or mounting via CIFS) for file shares.
  • Clarify whether Linux Service Fabric clusters can use file share backup storage, and if so, provide parity guidance.
  • Consider including a note about limitations or supported platforms for file share backup storage, especially if Windows-only.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides both Windows and Linux guidance for Azure Service Fabric networking, but there are several areas where Windows examples, tools, or terminology are prioritized or exclusively mentioned. PowerShell and Windows-specific tasks are referenced before Linux equivalents, and some example links and templates are Windows-focused. Linux-specific instructions and examples are less prominent or missing in some sections.
Recommendations
  • Ensure Linux examples and CLI commands are provided alongside PowerShell/Windows examples, especially for cluster management and networking tasks.
  • Where PowerShell is referenced (e.g., Client API, Azure DevOps), add equivalent Azure CLI or bash examples for Linux users.
  • Balance the order of presentation so Linux and Windows are treated equally (e.g., mention Linux and Windows together, not always Windows first).
  • Provide ARM template samples for Linux clusters with NSG, not just Windows clusters.
  • Clarify when a feature or example is Windows-only, and offer Linux alternatives or note Linux limitations.
  • Expand references to Linux-specific networking considerations, such as firewall configuration or port management.
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_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for restoring backup in Azure Service Fabric is heavily biased towards Windows and PowerShell usage. All code examples and instructions rely exclusively on PowerShell commands and modules (Microsoft.ServiceFabric.Powershell.Http), with no mention of Linux/macOS-compatible alternatives or CLI tools. The REST API is only demonstrated via PowerShell scripts, and there is no guidance for Bash, curl, or cross-platform approaches. The prerequisites and workflow assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent examples using Azure CLI, Bash scripts, or curl for REST API calls.
  • Document how to authenticate and connect to Service Fabric clusters from Linux/macOS, including certificate handling.
  • Mention any cross-platform tools or SDKs available for Service Fabric backup/restore operations.
  • Clarify whether the PowerShell module is required or if REST API calls can be made directly from any OS.
  • Add a section explicitly addressing Linux/macOS users, outlining supported workflows and limitations.
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 (a Windows-centric tool) is given its own section and is used for cluster upgrade operations without Linux alternatives. Windows-specific registry keys and VM template properties are discussed in detail, while Linux equivalents are not mentioned. The upgrade instructions for Service Fabric clusters rely solely on PowerShell commands, which are not natively available on Linux/macOS. Windows VM configuration is described before Linux, and disabling Windows Update is covered, but not Linux patching.
Recommendations
  • Provide Bash or Azure CLI equivalents for all PowerShell commands, especially for cluster upgrade operations.
  • Include Linux-specific instructions for VM patch management and configuration, such as disabling automatic updates on Linux VMs.
  • Mention Linux registry/file system equivalents or clarify when a step is Windows-only.
  • Ensure that Linux examples are presented alongside Windows examples, not only in the 'Next steps' section.
  • Add notes or links to Linux/macOS compatible tools for tasks currently described with Windows-only utilities.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation generally covers both Windows and Linux scenarios for Service Fabric security, but there is a noticeable pattern of Windows-first presentation, especially in sections about certificate management and encryption. Windows-specific tools (e.g., PowerShell, Windows Defender, Azure DSC) are discussed in detail, sometimes with limited or no Linux equivalents or guidance. Some sections, such as Windows Defender and security baselines, are Windows-only, but this is appropriate. However, in other areas, Windows examples and tools are presented before Linux equivalents, and some advanced configuration (e.g., antimalware exclusions) lacks Linux guidance.
Recommendations
  • When presenting cross-platform procedures (such as certificate creation and secret encryption), alternate the order of Windows and Linux examples or present them side-by-side.
  • Where Windows-specific tools (e.g., PowerShell, Windows Defender, Azure DSC) are discussed, add clear notes or equivalent Linux guidance (e.g., using ClamAV or other Linux antimalware solutions, or how to configure Linux security baselines).
  • For sections that only provide Windows examples (such as antimalware exclusions), explicitly state if there is no Linux equivalent or provide links to Linux security best practices.
  • Ensure that all critical security workflows (certificate management, secret encryption, managed identity usage) have complete Linux examples and not just links to separate articles.
  • Consider adding a summary table at the start of the document indicating which features or practices are Windows-only, Linux-only, or cross-platform.
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 provides a comprehensive reference for Service Fabric cluster settings, but exhibits some Windows bias. Windows terminology (e.g., 'Windows Fabric', 'Windows only' flags, 'MY' certificate store, NTLM authentication, Windows Defender Firewall) is used throughout, and Windows-specific settings are often mentioned before Linux equivalents. Some parameters (e.g., NTLM, Windows Update, log file settings) are marked 'Windows only' or default to Windows values, with Linux alternatives not always explained. Linux-specific settings (e.g., certificate folders, LinuxExternalExecutablePath) are present but less prominent. There are no explicit Linux configuration examples or guidance for Linux users, and some settings reference Windows APIs or documentation (e.g., CertGetCertificateChain) without Linux equivalents.
Recommendations
  • Add explicit Linux/macOS configuration examples or guidance for key settings, especially where Windows defaults or terminology are used.
  • Where parameters are Windows-only, clarify Linux equivalents or note if not applicable.
  • Ensure Linux-specific settings (e.g., certificate storage, log file paths, firewall configuration) are described with equal prominence.
  • Reference Linux documentation or APIs where Windows APIs are mentioned.
  • Review default values and descriptions to ensure Linux parity and avoid Windows-centric language where possible.
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 consistently provides PowerShell examples for configuring Service Fabric placement policies, but does not include equivalent Linux/macOS CLI or scripting examples (such as Azure CLI or Bash). PowerShell is primarily a Windows tool, and its exclusive use here creates friction for Linux/macOS users. Additionally, PowerShell examples are presented immediately after C# code samples, with no mention of cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for each placement policy configuration, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Mention and link to any relevant REST API documentation for configuring placement policies, which can be used from any OS.
  • Clarify whether PowerShell examples are usable on Linux/macOS (via PowerShell Core), or provide Bash scripting alternatives.
  • Explicitly state if certain configuration steps are only possible via PowerShell, and provide guidance for Linux/macOS users.
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 equivalent Linux/macOS CLI or scripting examples (such as Azure CLI, Bash, or REST API) are provided. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools.
Recommendations
  • Add Azure CLI examples for all operations shown (creating, updating, querying, and removing Application Groups and capacities).
  • Include REST API examples where applicable, as these are platform-agnostic.
  • Mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users on alternative tools.
  • Consider referencing or linking to documentation about Service Fabric CLI (sfctl), if relevant, and provide examples using it.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Windows and cross-platform (JSON) configuration examples for Service Fabric clusters, but Windows-specific XML (ClusterManifest.xml) and PowerShell examples are presented first or exclusively in several sections. PowerShell is the only CLI example shown for service creation and updates, with no Linux/macOS CLI (e.g., Bash, Azure CLI) equivalents. The XML configuration is specifically labeled as 'WindowsServer', and there is no mention of Linux-based Service Fabric clusters or their configuration patterns.
Recommendations
  • Add explicit examples and guidance for Linux-based Service Fabric clusters, including configuration files and supported OS types.
  • Provide equivalent Bash or Azure CLI examples for service creation and updates, alongside PowerShell.
  • Clarify whether the XML configuration applies only to Windows clusters and provide Linux configuration alternatives if supported.
  • Ensure that cross-platform JSON examples are given equal prominence and context as Windows XML examples.
  • Mention any limitations or differences for Linux/macOS users, if applicable.
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 examples for configuring move cost, but does not include equivalent Linux/macOS CLI (e.g., Bash, Azure CLI) examples. PowerShell is presented before C# in all cases, and there is no mention of Linux-native tools or cross-platform command-line options for Service Fabric management. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tooling.
Recommendations
  • Add Bash or Azure CLI examples for creating and updating Service Fabric services and move cost settings.
  • Mention cross-platform management options (such as Azure CLI, REST API, or Service Fabric CLI) where available.
  • Clarify whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), and provide guidance for users on those platforms.
  • Consider presenting cross-platform or neutral examples (e.g., Azure CLI, REST API) 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 detailed PowerShell examples for managing node tags and service requirements, but does not include equivalent CLI or scripting examples for Linux/macOS users. PowerShell is a Windows-centric tool, and its exclusive use here creates friction for users managing Service Fabric clusters on Linux. No Linux-native commands (such as Bash, Azure CLI, or REST API examples) are provided, despite REST APIs being mentioned.
Recommendations
  • Add examples using Azure CLI or Bash scripts for managing node tags and service requirements.
  • Provide REST API sample requests for adding/removing node tags and configuring service tag requirements, as REST APIs are mentioned as an interface.
  • Clarify whether PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide alternative instructions if not.
  • Ensure that Linux/macOS users can complete all documented tasks without relying on Windows tools.
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_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed PowerShell examples for configuring auto scaling policies, but does not include equivalent Linux CLI or cross-platform examples (such as Azure CLI, REST API, or bash scripting). The PowerShell cmdlets and .NET/C# APIs shown are primarily Windows-centric, and there is no guidance for Linux-native Service Fabric management tools or workflows. This creates friction for Linux users, especially as Service Fabric supports Linux clusters and container workloads.
Recommendations
  • Add equivalent examples using Azure CLI, REST API, or Service Fabric CLI (sfctl), which are cross-platform and work on Linux/macOS.
  • Clearly indicate which management approaches are Windows-only (e.g., PowerShell cmdlets) and provide Linux alternatives where possible.
  • Include bash or shell script snippets for common operations, or reference official Linux management documentation.
  • Explicitly state any limitations or differences in auto scaling support between Windows and Linux clusters, especially where features or tooling diverge.
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 both C# and PowerShell examples for managing Service Fabric metrics, but only PowerShell is used for CLI examples. There are no Linux/macOS CLI equivalents (such as Azure CLI or REST API), and PowerShell is presented before any mention of alternative tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools.
Recommendations
  • Add Azure CLI examples for all PowerShell commands shown, as Azure CLI is cross-platform and widely used.
  • Mention REST API options where applicable, especially for service creation and metric management.
  • Clearly indicate which commands are Windows-only and provide guidance for Linux/macOS users.
  • Consider showing Azure CLI or REST API examples before PowerShell, or at least in parallel, to avoid Windows-first bias.
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_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides extensive PowerShell examples for configuring service sensitivity and maximum load in Azure Service Fabric, but does not offer equivalent CLI or scripting examples for Linux/macOS users. The use of PowerShell and references to Windows tooling may create friction for users managing Service Fabric clusters on non-Windows platforms.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, where possible.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., with PowerShell Core) or if they are Windows-only.
  • Provide guidance for Linux/macOS users on how to achieve the same configuration tasks, including any limitations.
  • Explicitly mention if certain operations are only supported via PowerShell or Windows tools, and suggest alternatives if available.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for securing an Azure Service Fabric cluster presents security scenarios and technologies applicable to both Azure-hosted clusters and standalone Windows clusters. However, it repeatedly references Windows Server clusters and provides links and guidance specifically for Windows environments, with no equivalent examples or links for standalone Linux clusters. Windows security (Kerberos) is discussed, but Linux authentication options are not mentioned. Certificate creation recommendations focus on Windows tools and services, with no Linux tooling or process described. The concept of Linux clusters is acknowledged, but practical guidance is missing.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and authentication options.
  • Provide Linux-specific examples for certificate creation and management (e.g., using OpenSSL, Linux certificate stores).
  • Mention Linux authentication patterns (e.g., local user accounts, integration with Linux-based identity providers) where relevant.
  • Ensure parity in references and links for both Windows and Linux standalone cluster scenarios.
  • Clarify which features or recommendations apply to both OS types, and which are Windows-specific.
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 for scaling Azure Service Fabric standalone clusters demonstrates a Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without providing equivalent Linux or cross-platform CLI examples. The linked 'scale a standalone cluster' documentation is specifically for Windows Server, and there is no mention of Linux-based Service Fabric standalone clusters or instructions for scaling them. This creates friction for Linux users who may wish to deploy or manage Service Fabric clusters outside of Windows environments.
Recommendations
  • Clarify whether Service Fabric standalone clusters are supported on Linux. If so, provide Linux-specific instructions and examples for scaling operations.
  • Include cross-platform CLI examples (such as Service Fabric CLI or REST API usage) alongside PowerShell commands.
  • If standalone clusters are Windows-only, explicitly state this in the documentation to avoid confusion for Linux users.
  • Reference or link to any Linux-specific documentation if available.
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, references ApplicationManifest.xml (a Windows-centric deployment artifact), and describes enabling DNS service via the Azure portal (Windows clusters only), but does not offer equivalent Linux CLI or deployment examples. Linux support is mentioned as limited, but no Linux-specific guidance or parity in examples is provided.
Recommendations
  • Add Linux-specific examples for setting DNS names, such as using Azure CLI or ARM templates for containerized services.
  • Clarify Linux deployment workflows, including how to enable DNS service for Linux clusters (since portal is not supported).
  • Provide sample commands or scripts for Linux users (e.g., Bash, Azure CLI) alongside PowerShell examples.
  • Explicitly note differences in ApplicationManifest.xml usage for Linux clusters, or provide Docker Compose examples where relevant.
  • Highlight limitations for Linux clusters more prominently and link to Linux-specific guidance.
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, but the only practical example for reporting and evaluating application health uses PowerShell cmdlets, which are Windows-specific. No equivalent Linux or cross-platform CLI (such as Azure CLI or REST API) example is given, and PowerShell is presented as the default method for interacting with Service Fabric health reporting. This creates friction for Linux/macOS users, as they must seek out alternative methods not documented here.
Recommendations
  • Add examples using Azure CLI or REST API for reporting and querying health, which are cross-platform and supported on Linux/macOS.
  • Explicitly mention that PowerShell is Windows-specific and provide links or guidance for Linux/macOS users.
  • Consider including sample code using the Service Fabric SDK in languages like Python or .NET Core, which are cross-platform.
  • Reorder or supplement the 'Example: Report and evaluate application health' section to show Linux-compatible methods first or alongside PowerShell.
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 on Azure Service Fabric image store connection strings shows a moderate Windows/PowerShell bias. It references PowerShell as the primary way to retrieve the cluster manifest and links to a PowerShell-based deployment guide as the next step. There is no mention of Linux/macOS CLI equivalents (such as Azure CLI or Bash scripts), and Windows/PowerShell tools are presented first and most prominently.
Recommendations
  • Add examples or references for retrieving the cluster manifest using Azure CLI or Bash scripts, especially for Linux/macOS users.
  • Include links to cross-platform tools or documentation (e.g., Azure CLI, REST API usage with curl) alongside or before PowerShell references.
  • Clarify whether the described procedures and tools are available and supported on Linux/macOS, and provide parity where possible.
  • Consider adding a 'Platform support' note to indicate that Service Fabric management can be performed from non-Windows environments, if applicable.
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 provides examples and tooling references that prioritize Windows/PowerShell workflows (e.g., PowerShell cmdlets, Visual Studio, Deploy-FabricApplication.ps1) and mentions them before Linux equivalents. While sfctl and Jenkins are referenced, there are no concrete Linux/macOS command examples, and the overall guidance is oriented toward Windows-centric tools and patterns.
Recommendations
  • Add explicit Linux/macOS examples for application creation and parameter passing, such as full sfctl command lines and shell script snippets.
  • Include step-by-step instructions for using Jenkins or other cross-platform CI/CD tools, not just mentioning them.
  • Balance the order of examples so Linux/macOS and Windows workflows are presented equally.
  • Reference cross-platform editors and deployment tools alongside Visual Studio.
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 guides and tools (e.g., Patch Orchestration Application for Windows) and links primarily to Windows Server-focused upgrade/configuration articles. There is no mention of Linux-specific upgrade procedures, tools, or configuration guides, nor are Linux examples provided. This creates friction for Linux cluster administrators seeking parity.
Recommendations
  • Add links and references to Linux-specific Service Fabric standalone cluster upgrade guides, if available.
  • Provide examples and instructions for upgrading and configuring Service Fabric clusters running on Linux, including patch orchestration and configuration management.
  • Clarify in the documentation when a feature or tool is Windows-only, and offer Linux alternatives or workarounds where possible.
  • Ensure that both Windows and Linux procedures are covered in parallel, or explicitly state platform limitations.
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 for the Azure Service Fabric application resource model demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI or other cross-platform tools. Application packaging instructions reference Visual Studio, a Windows-centric IDE, and do not provide alternatives for Linux/macOS users. There are no Linux/macOS-specific examples or guidance, and Windows tools and patterns are presented exclusively and first.
Recommendations
  • Add Azure CLI examples for deployment and deletion tasks alongside PowerShell examples.
  • Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK for Linux/macOS).
  • Mention and link to cross-platform IDEs or command-line alternatives for application packaging.
  • Clearly indicate which steps are Windows-only and offer Linux/macOS equivalents where possible.
  • Ensure screenshots and walkthroughs are not exclusively tied to Windows/Visual Studio.
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 provides code examples and administrative instructions primarily using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or script examples (e.g., Bash, Azure CLI) for scaling Service Fabric services. Windows/PowerShell commands are presented first and exclusively, which may create friction for Linux users. The only explicit Linux mention is in the 'Choosing a platform' section, which discusses implementation differences but does not provide Linux-specific operational guidance.
Recommendations
  • Add equivalent Linux/Bash/Azure CLI examples for scaling operations (e.g., creating/removing services, updating instance counts).
  • Reference Linux tooling (such as Azure CLI or REST API) alongside PowerShell, not just in the 'Choosing a platform' section.
  • Ensure administrative instructions are platform-neutral or provide parallel guidance for both Windows and Linux users.
  • Consider linking to Linux-specific Service Fabric documentation or guides where appropriate.
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 ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation covers both Windows and Linux usage of Azure Service Fabric, but exhibits several Windows biases. Windows-specific tools (PowerShell, Visual Studio) and terminology (Windows service, FabricHost.exe) are mentioned first or exclusively in key sections. Examples and instructions often default to Windows, with Linux equivalents referenced later or omitted. Standalone cluster creation and upgrades are described only for Windows, with Linux support explicitly stated as unavailable. Some CLI and REST API options are mentioned, but PowerShell is emphasized. Visual Studio is referenced for cluster creation, but no Linux-native tooling is suggested.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, upgrades, and management.
  • Mention Linux CLI tools (e.g., sfctl) and Bash scripts before or alongside PowerShell, and clarify their parity.
  • Include references to Linux-native development environments (e.g., VS Code, JetBrains Rider) where Visual Studio is mentioned.
  • Clearly indicate which features are Windows-only and which are cross-platform, linking to the Linux/Windows differences page.
  • Add guidance for Linux users on monitoring, diagnostics, and health reporting using Linux tools.
  • Update 'Next steps' to include Linux cluster creation and management, or clarify Linux limitations.
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_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page describes Service Fabric event logging primarily in terms of Windows-centric tools and patterns, such as ETW/Windows Event logs and the Windows Azure diagnostics agent. There is no mention of Linux equivalents or guidance for accessing events on Linux-based Service Fabric clusters, nor are Linux-specific monitoring tools or log channels referenced. Windows tools and terminology are presented first and exclusively.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported log channels (e.g., stdout, syslog, Azure Monitor integration for Linux).
  • Mention Linux-compatible diagnostics agents or methods, such as Azure Monitor agent or Log Analytics agent for Linux.
  • Provide examples or links for querying and visualizing events from Linux clusters, including any differences in configuration or event formats.
  • Clarify which features or event channels are Windows-only and which are cross-platform.
  • Ensure parity in documentation structure by presenting Linux and Windows approaches side-by-side where applicable.
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 location using a Windows file path and does not mention Linux or cross-platform equivalents. The only explicit tooling path given is Windows-specific, and there is no mention of Linux/Mac installation or usage patterns. However, the overall guidance is mostly platform-agnostic, and the examples reference general concepts and cross-platform languages (e.g., Node.js, Java, C++).
Recommendations
  • Add information about the location of Service Fabric SDK files on Linux/macOS, if available.
  • Clarify whether the packaging and deployment process is supported and documented for Linux/macOS, and provide equivalent instructions or links.
  • When referencing file paths or tools, include both Windows and Linux/macOS examples, or note platform differences.
  • Explicitly state if certain steps or tools are Windows-only, and provide alternatives or workarounds for Linux/macOS users where possible.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides PowerShell examples for creating services with the Exclusive Process model and references PowerShell cmdlets for querying and managing Service Fabric services. PowerShell is a Windows-centric tool, and no equivalent Linux CLI (such as sfctl) or bash examples are provided. Additionally, PowerShell is mentioned before REST and FabricClient options, reinforcing Windows-first patterns.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform and commonly used on Linux/macOS, for service creation and management.
  • Include bash or shell script examples where applicable, especially for querying and managing deployed service packages.
  • Mention Linux/macOS-compatible tools and workflows alongside PowerShell, and clarify any platform limitations.
  • Reorder sections to avoid always listing Windows tools first, or explicitly state tool parity.
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 demonstrates a moderate Windows bias. The examples and explanations are based on the Windows Server 2016 Container Sample, and Windows-specific tools and patterns (such as 'winver' for OS build detection and Windows-style paths like 'c:\VolumeTest\Data') are referenced first or exclusively. There is limited mention of Linux equivalents, and no Linux-specific manifest examples or guidance are provided, even though Service Fabric supports Linux containers. The certificate handling section does mention both PFX (Windows) and PEM (Linux) formats, but overall, Linux users may find it difficult to adapt these examples without additional guidance.
Recommendations
  • Provide equivalent Linux-based manifest examples, including Linux-style paths and container images.
  • Include instructions for determining OS build/version on Linux (e.g., using 'uname -a' or '/etc/os-release'), alongside the Windows 'winver' command.
  • Clarify which manifest settings or features are cross-platform and which are Windows-only.
  • Reference both Windows and Linux sample repositories, if available.
  • Add notes or callouts where behavior differs between Windows and Linux containers (e.g., volume mounting, certificate formats, isolation modes).
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 cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) and administrative APIs, but does not provide equivalent examples or instructions for Linux/macOS users. There is no mention of Linux CLI tools, REST APIs, or cross-platform SDK usage for replica management. The focus on PowerShell and Windows-centric tooling creates friction for non-Windows users.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), which is cross-platform and available on Linux/macOS.
  • Document how to use REST APIs or FabricClient SDKs in cross-platform languages (e.g., Python, Java) to perform replica soft delete and restore operations.
  • Clarify whether the PowerShell cmdlets are available on Linux (via PowerShell Core), and if not, provide alternative instructions.
  • Include sample commands and screenshots for Linux/macOS environments where 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 demonstrates a notable Windows bias by providing extensive PowerShell examples and referencing Windows command-line patterns. There are no equivalent Linux/bash examples, nor is there guidance for Linux users on how to perform health reporting tasks using cross-platform tools. PowerShell is presented as the primary CLI method, with no mention of Linux-native alternatives or Azure CLI. This creates friction for Linux/macOS users, especially those running Service Fabric clusters on Linux or developing cross-platform applications.
Recommendations
  • Add bash or Azure CLI examples for health reporting, especially for REST calls and cluster interactions.
  • Explicitly mention that PowerShell commands are for Windows, and provide guidance for Linux users (e.g., using curl for REST, or Azure CLI where possible).
  • Include notes or sections on how to perform equivalent tasks on Linux/macOS clusters, including any limitations or differences.
  • Consider referencing cross-platform scripting options, such as PowerShell Core (pwsh), if applicable, and clarify compatibility.
  • Ensure REST examples include sample curl commands for Linux/macOS users.
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 provides explicit instructions for using the Fault Analysis Service via PowerShell and C#, but does not mention or provide examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). The PowerShell module is highlighted as the primary scripting interface, and there is no guidance for equivalent Linux tooling or cross-platform approaches.
Recommendations
  • Add examples or references for using the Fault Analysis Service via Azure CLI, Bash, or REST API, if available.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide instructions for Linux/macOS users if so.
  • Mention any limitations or alternative approaches for non-Windows users.
  • Ensure that code and scripting examples are provided for both Windows and Linux environments, or explicitly state if only Windows is supported.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented toward Windows environments, specifically Visual Studio workflows. All deployment and configuration examples reference Visual Studio actions (Build/Rebuild/F5/Ctrl+F5/Publish), which are Windows-only. The only alternative deployment methods mentioned are ARM templates and PowerShell cmdlets, with no Linux/macOS equivalents or CLI examples. There are no instructions or examples for Linux/macOS users, nor any mention of cross-platform tooling or workflows.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide Azure CLI or cross-platform PowerShell Core examples for deploying Service Fabric applications and configuring StartupServices.xml.
  • Clarify which features are Visual Studio/Windows-only and offer alternative workflows for other platforms.
  • Mention any limitations or supported scenarios for Linux/macOS users up front, so they can determine applicability.
  • Include references to Service Fabric SDK usage on Linux/macOS, if supported, and how StartupServices.xml fits into those workflows.
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 is primarily focused on Ubuntu Linux, but it exhibits Windows bias in several areas. Hyper-V (a Windows-only virtualization tool) is mentioned as the main example for creating VHDs, and instructions reference Hyper-V Manager and PowerShell's Convert-VHD cmdlet without providing equivalent Linux tooling or workflows. Windows extraction instructions are given (via WSL), but native Linux extraction is not explicitly described. Linux-native tools for VHD creation and conversion (such as qemu-img or VBoxManage) are missing, and the workflow assumes Windows/Hyper-V as the default environment.
Recommendations
  • Add instructions and examples for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, dd).
  • Provide steps for extracting the .tar.gz image natively on Linux (not just via WSL on Windows).
  • Mention Linux virtualization solutions (e.g., KVM, VirtualBox) alongside Hyper-V, and link to relevant guides.
  • Include PowerShell/Hyper-V steps as an alternative, not the default, and ensure Linux-first parity in examples.
  • Clarify that Hyper-V is just one option, and highlight Linux-native workflows for users on Linux/macOS.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Windows and Linux coverage, but there are several areas where Windows/PowerShell tools and patterns are emphasized or presented first. PowerShell is frequently used for checksum generation and command examples, sometimes without Linux equivalents. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents are less prominent or missing (e.g., no Linux restart customizer). In some sections, Windows tools (PowerShell cmdlets) are referenced before Linux tools, and Windows examples are shown first.
Recommendations
  • Where PowerShell is used for tasks like checksum generation, always provide the equivalent Linux/macOS command (e.g., sha256sum) alongside.
  • For customizer types, clarify Linux limitations (e.g., no restart customizer) and suggest workarounds for Linux users.
  • Ensure that Linux examples (e.g., shell scripts, CLI commands) are presented with equal prominence and, where possible, shown before or alongside Windows examples.
  • For validation and customization, explicitly state Linux support and provide Linux-specific examples where only Windows examples are given.
  • Where Windows tools or patterns are mentioned (such as Get-FileHash), add Linux/macOS alternatives (such as sha256sum) in the same context.
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
Although the documentation is focused on Linux VMs, there is notable Windows bias in several areas. PowerShell examples and tooling (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand) are heavily featured, sometimes before or in greater detail than Azure CLI examples. Windows-specific tools and patterns (such as PowerShell cmdlets and SAS token generation via New-AzStorageBlobSASToken) are referenced throughout. REST API and ARM template examples use Windows-centric script examples (e.g., Write-Host, .ps1 files) instead of Linux shell scripts (.sh). Some explanations and notes reference Windows behaviors or requirements, and Linux-specific guidance is less prominent or missing in places.
Recommendations
  • Ensure all examples and explanations are Linux-centric, using bash/shell scripts (.sh) instead of PowerShell (.ps1) where appropriate.
  • Provide Azure CLI examples before PowerShell, as CLI is more cross-platform and native for Linux users.
  • Where PowerShell cmdlets are referenced, add equivalent Azure CLI commands and highlight their use for Linux environments.
  • In REST API and ARM template samples, use Linux shell script examples (e.g., 'echo Hello World!' or .sh files) rather than Windows PowerShell scripts.
  • Clarify SAS token generation for Linux users, referencing Azure CLI commands instead of only PowerShell.
  • Remove or minimize Windows-specific notes unless they are relevant to Linux VM scenarios.
GitHub Create Pull Request
Virtual Machines Upgrade Gen1 VMs to Trusted launch ...s/virtual-machines/trusted-launch-existing-vm-gen-1.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 upgrading Gen1 VMs to Trusted launch, but Windows-specific instructions, tools (MBR2GPT.exe, Defrag, PowerShell), and troubleshooting are more detailed and appear first. Linux instructions are present but less extensive, and CLI/ARM template examples are cross-platform. Windows tools and patterns are mentioned before Linux equivalents, and troubleshooting sections are heavily Windows-focused.
Recommendations
  • Expand Linux troubleshooting guidance to match Windows detail, including common errors and recovery steps.
  • Provide Linux-specific disk conversion instructions for cases where GPT/EFI is not already present, including recommended tools and commands.
  • Add Linux examples for ARM template deployment and validation where relevant.
  • Ensure parity in best practices, such as disk preparation and backup, for Linux VMs.
  • Consider listing Linux instructions/examples before or alongside Windows to avoid 'windows_first' bias.
GitHub Create Pull Request
Virtual Machines Deploy a Trusted Launch VM ...ain/articles/virtual-machines/trusted-launch-portal.md
Medium 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 deployment with Trusted Launch, and provides parity in Azure CLI and ARM template examples. However, PowerShell examples are Windows-centric and shown in detail, with Windows-specific parameters and image references. In several PowerShell sections, only Windows examples are provided, while CLI examples use Linux images. The order of examples sometimes puts Windows/PowerShell before Linux/CLI, and PowerShell sections do not offer Linux-specific guidance or parameters.
Recommendations
  • Add Linux-specific PowerShell examples, including Linux image references and parameters (e.g., Set-AzVMOperatingSystem -Linux).
  • Ensure PowerShell snippets for Linux are included wherever Windows PowerShell examples are shown.
  • Where possible, alternate the order of Windows and Linux examples, or group them clearly to avoid implicit Windows-first bias.
  • Clarify in PowerShell sections whether the example is Windows-only, and provide Linux alternatives if supported.
  • Review screenshots and UI instructions to ensure Linux options are visible or explained.
GitHub Create Pull Request
Virtual Machines Resize a virtual machine ...blob/main/articles/virtual-machines/sizes/resize-vm.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 PowerShell examples for resizing Azure VMs, including scripts for both single VMs and VMs in availability sets. PowerShell is a Windows-centric tool, and these examples are more numerous and detailed than the Azure CLI examples, which are cross-platform. The Terraform section references both Linux and Windows resources but links only to a Windows quickstart. There are no explicit Linux-specific examples or guidance, and the PowerShell examples are presented before CLI and Terraform, reinforcing a Windows-first pattern.
Recommendations
  • Add Bash shell examples for resizing VMs using Azure CLI, highlighting Linux/macOS usage.
  • Provide parity in example detail between PowerShell and Azure CLI, including scripts for availability sets and error handling.
  • Include links to both Linux and Windows Terraform quickstarts, or provide a Linux-focused Terraform snippet.
  • Consider mentioning cross-platform tools (e.g., Bash, Python SDK) alongside PowerShell for scripting.
  • Ensure that Linux VM scenarios are explicitly referenced in code samples and explanations.
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, there is a slight tendency to mention Windows-specific tools (like Mirantis Container Runtime and DockerEE) and Windows scenarios (such as IIS lift-and-shift) before or more prominently than Linux equivalents. Windows examples and tutorials are listed alongside Linux ones, but Windows scenarios (like IIS) are described in more detail.
Recommendations
  • Ensure Linux scenarios (such as Apache/Nginx lift-and-shift or Linux-specific app migrations) are described with equal detail as Windows scenarios.
  • Mention Linux container runtimes and tools (such as containerd or Podman) if relevant, not just Docker.
  • Provide Linux-first examples in some sections, or alternate the order between Linux and Windows.
  • Expand on Linux-specific use cases and container orchestration patterns within Service Fabric.
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, and provides parity in describing development environments and cluster deployment options. However, in the 'Any OS, any cloud' section, Windows development (with .NET SDK, Visual Studio, PowerShell) is described before Linux development (with Java SDK, Eclipse, Yeoman), and the quickstart link points to a .NET (Windows-centric) guide. No Linux-specific quickstart or example is linked, and Windows tools are mentioned first.
Recommendations
  • Add a quickstart link for Linux development (e.g., a Java or .NET Core example on Linux).
  • Present Windows and Linux development options in parallel, rather than Windows first.
  • Ensure that both Windows and Linux tooling (e.g., PowerShell vs. Bash, Visual Studio vs. Eclipse) are described with equal prominence.
  • Link to Linux-specific documentation (such as service-fabric-quickstart-java.md or service-fabric-quickstart-linux.md) alongside Windows quickstarts.
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 both Linux and Windows guidance, but there are subtle signs of Windows bias. In the PowerShell section, Windows examples are shown first and in more detail, with Linux mentioned as an alternative. PowerShell is presented as a primary scripting option, which is more relevant to Windows users. However, CLI and REST examples are neutral or Linux-first, and the overall guidance covers both OS types.
Recommendations
  • In PowerShell examples, show Linux usage first or provide parity in example detail for both OS types.
  • Explicitly mention cross-platform PowerShell (pwsh) usage for Linux/macOS users, or clarify that PowerShell examples work on all platforms.
  • Ensure all CLI and REST examples include both Linux and Windows variants where relevant.
  • Review ordering of OS-specific guidance to avoid always listing Windows first.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_reference
Summary
The documentation is focused on Linux VM time sync in Azure and provides extensive Linux-specific guidance and examples. However, the opening sections reference Windows Server 2016 and its time sync improvements, and link to Windows documentation before Linux-specific details. There are no PowerShell or Windows command examples except for a single PowerShell snippet used for base64 encoding cloud-init, which is contextually relevant for Azure users but could be supplemented with a Linux equivalent. All configuration, troubleshooting, and tool instructions are Linux-centric.
Recommendations
  • Move or minimize Windows Server 2016 references to a background section or sidebar, emphasizing Linux-specific mechanisms first.
  • Provide a Linux shell command equivalent for base64 encoding cloud-init (e.g., 'base64 cloud-config.txt') alongside the PowerShell example.
  • Ensure that Linux documentation links are as prominent as Windows links in the 'Next steps' and introductory sections.
  • Clarify that Windows references are for host infrastructure context, not for VM configuration.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and cross-platform CLI (sfctl) instructions for deploying Docker Compose files to Azure Service Fabric. However, the PowerShell (Windows-centric) instructions are presented first and in greater detail, with more explanation and command breakdowns. The CLI (sfctl) section is present and functional for Linux/macOS users, but is introduced as an 'alternative' rather than a co-equal path. There are no Linux/macOS-specific caveats or examples, but the ordering and emphasis slightly favor Windows users.
Recommendations
  • Present PowerShell and sfctl (CLI) instructions in parallel or with equal prominence, possibly using tabs or side-by-side sections labeled 'Windows (PowerShell)' and 'Cross-platform (sfctl)'.
  • Explicitly state that sfctl works on Linux/macOS and provide installation links or prerequisites for non-Windows users.
  • Ensure that all command examples and explanations are equally detailed for both PowerShell and sfctl.
  • Consider including a short section or note confirming that Service Fabric Compose deployment is supported on both Windows and Linux clusters (if true), or clarify any platform limitations.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page is generally platform-neutral in its explanations of Service Fabric activation and deactivation lifecycle. However, the 'Next steps' section and one example reference PowerShell and a PowerShell module for downloading ServicePackages, suggesting Windows-centric tooling and workflows. There are no explicit Linux/bash examples or references to Linux-native tools, and PowerShell is mentioned as the deployment/removal method without alternatives.
Recommendations
  • Add Linux/bash examples or references alongside PowerShell for deployment/removal tasks.
  • Mention cross-platform tools (such as Azure CLI or REST API) where applicable, and provide links or examples.
  • Clarify if PowerShell examples are cross-platform (PowerShell Core) or Windows-only, and provide Linux/macOS equivalents if available.
  • Reference Linux-specific documentation or workflows for Service Fabric where possible.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides comprehensive guidance for integrating ASP.NET Core with Azure Service Fabric Reliable Services, covering both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers. While Kestrel is recommended and well-documented for cross-platform (Windows and Linux) scenarios, HTTP.sys is discussed in detail with explicit notes about its Windows-only nature. In some sections, Windows-specific tools and patterns (e.g., HTTP.sys, netsh, Windows HTTP Server API) are mentioned before or in more detail than their Linux equivalents, but Linux parity is generally maintained through Kestrel guidance.
Recommendations
  • Continue to clearly indicate when features are Windows-only (as is done with HTTP.sys).
  • Where Windows-specific tools like netsh are referenced, briefly note that they are not applicable on Linux and that Kestrel is the cross-platform alternative.
  • Consider adding a short section or callout early in the article explicitly stating that Kestrel is the recommended and supported option for Linux deployments, and that HTTP.sys is only for Windows.
  • In code and configuration examples, ensure that Kestrel (cross-platform) examples are shown first or given equal prominence to avoid the perception of Windows-first bias.
  • If possible, add a troubleshooting or FAQ section addressing common Linux deployment questions.
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 is generally cross-platform and describes Service Fabric concepts in an OS-agnostic way. However, there are minor instances of Windows bias: Windows terminology and tools (such as 'Windows service', 'FabricHost.exe', and references to EXE/DLL files) are mentioned first or exclusively in some definitions, even though Linux is supported. The description of nodes focuses on Windows services and executables, and the code package section refers to EXE/DLL files, which are Windows-centric. Linux is mentioned in the context of containers and guest executables, but not always with equal prominence.
Recommendations
  • When describing node startup, clarify the equivalent Linux processes or daemons, or note that on Linux, Service Fabric uses systemd or other init systems.
  • In the 'Code package' section, mention that on Linux, code packages may include ELF binaries or scripts, not just EXE/DLL files.
  • Where Windows executables or services are referenced, add a note or parallel description for Linux (e.g., 'On Linux, Service Fabric runs as systemd services and uses equivalent binaries').
  • Ensure that examples and terminology are balanced, mentioning both Windows and Linux where relevant, especially in introductory or conceptual sections.
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
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page for Service Fabric Reliable Services app manifest examples demonstrates a mild Windows bias. Windows-specific concepts (such as running scripts via .bat files, references to NETWORKSERVICE, and mentions of ServiceFabric PowerShell module) are present. Examples and explanations often use Windows terminology and tools (e.g., Setup.bat, VotingWeb.exe), and the PowerShell module is referenced as the default for service creation. There is no explicit mention of Linux equivalents (such as shell scripts or Linux user accounts), nor are Linux-specific patterns or examples provided.
Recommendations
  • Add examples using Linux-compatible scripts (e.g., .sh files) alongside .bat examples.
  • Clarify that Service Fabric supports Linux and provide guidance for Linux user account configuration and script execution.
  • Mention Linux tools or CLI alternatives to the ServiceFabric PowerShell module for service creation.
  • Where user accounts or system groups are referenced, note Linux equivalents (e.g., systemd users, sudo group).
  • Ensure terminology is cross-platform or clarify Windows-specific terms when used.
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 provides .NET/C# code examples and references Visual Studio and PowerShell in the 'Next steps' section. While the main content is platform-neutral (focused on .NET Core/Service Fabric Reliable Collections), the order of 'Next steps' links places Windows-centric tools (Visual Studio, PowerShell) before any mention of cross-platform or Linux alternatives. No Linux/macOS-specific examples or guidance are provided.
Recommendations
  • Add explicit mention of cross-platform development with .NET Core/.NET 5+ and Service Fabric, clarifying Linux/macOS support.
  • Include examples or links for upgrading applications using CLI tools (e.g., Azure CLI, Service Fabric CLI) that work on Linux/macOS.
  • Balance the order of 'Next steps' so Linux/macOS-friendly options (CLI, VS Code) are not always listed after Windows tools.
  • If relevant, provide sample code or instructions for serialization in environments other than Windows (e.g., running Service Fabric on Linux).
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 first or in greater detail, and Windows-specific extension types (ApplicationHealthWindows) are used in sample code. PowerShell usage is prominent, and Windows tools/patterns are referenced alongside their Linux equivalents, but sometimes Windows terminology or examples appear before Linux ones. The REST API examples also default to ApplicationHealthWindows, though ApplicationHealthLinux is mentioned.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail.
  • Alternate the order of examples so Linux/Bash is not always after Windows/PowerShell.
  • In REST and JSON samples, use ApplicationHealthLinux as the default or provide both Linux and Windows variants.
  • Clarify that both ApplicationHealthLinux and ApplicationHealthWindows are supported, and provide guidance for Linux users where Windows-specific terminology is used.
  • Where possible, avoid Windows-centric language (e.g., referencing Windows extension types first) unless the feature is Windows-only.
GitHub Create Pull Request
Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. PowerShell is presented as a distinct example, but it is not prioritized over cross-platform tools. However, in the 'Create a private gallery' section, the PowerShell example is shown after CLI and Portal, which is a minor 'windows_first' bias, as PowerShell is a Windows-centric tool. All critical tasks are covered with cross-platform CLI and REST examples, ensuring Linux/macOS users can complete the tasks without friction.
Recommendations
  • Consider clarifying that Azure CLI commands work on Windows, Linux, and macOS.
  • Explicitly mention that PowerShell examples are primarily for Windows users, and that Azure CLI is recommended for cross-platform use.
  • If possible, provide Bash shell scripting examples for Linux/macOS users, or note that Azure CLI commands can be used in Bash.
  • Ensure that CLI examples are always shown before PowerShell, and that PowerShell is clearly labeled as Windows-specific.
GitHub Create Pull Request
Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI (bash/Linux/macOS) and Azure PowerShell (Windows) examples for creating instant access snapshots, but the PowerShell example is given equal prominence and detail. However, there is no explicit Linux/macOS bias or omission; all critical tasks can be performed using Azure CLI, which is cross-platform. The ordering of examples sometimes puts PowerShell before CLI, and PowerShell is referenced as a primary tool, which may create minor friction for Linux/macOS users.
Recommendations
  • Ensure Azure CLI examples are always presented first, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, while PowerShell is primarily for Windows (though it can run cross-platform).
  • Add a short note clarifying that all tasks can be completed on Linux/macOS using Azure CLI.
  • Consider including sample bash scripts for automation, or referencing Linux/macOS shell usage where appropriate.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for Azure CLI, PowerShell, Portal, and ARM templates. PowerShell examples are present throughout, and in some sections (such as 'Restart a rolling upgrade'), PowerShell is shown before ARM templates or other options. However, Azure CLI is always present and is cross-platform, so Linux/macOS users can complete all tasks. There are no Windows-only tools or commands, but PowerShell is emphasized, which may create friction for non-Windows users.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider adding Bash shell script examples where relevant, especially for automation.
  • Where PowerShell is shown, clarify its availability on Linux/macOS (via PowerShell Core), or link to guidance for installing PowerShell on those platforms.
  • Ensure CLI examples are always shown first, as they are most universally accessible.
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 examples are often shown before CLI, and some sections (such as querying public IPs) provide more detailed PowerShell usage. Portal instructions are generic and not OS-specific, but PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. However, CLI and ARM template examples are present throughout, ensuring Linux parity for most tasks.
Recommendations
  • Present Azure CLI examples before PowerShell examples to prioritize cross-platform tools.
  • Ensure all PowerShell examples are matched with equivalent Azure CLI examples, especially for querying and managing resources.
  • Explicitly mention that Azure CLI is available on Windows, Linux, and macOS, and encourage its use for cross-platform scenarios.
  • Where possible, add Bash shell script examples for advanced scenarios.
  • Review sections where PowerShell is used for querying (e.g., public IPs) and ensure CLI examples are equally detailed.
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 and sometimes appear before Linux-oriented CLI examples. The PowerShell examples are Windows-centric, and there is no explicit mention of Linux/macOS alternatives for PowerShell commands. The CLI examples are cross-platform, but the documentation does not clarify this. There is minor bias in the ordering and prominence of Windows tools.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and are recommended for cross-platform use.
  • Consider listing Azure CLI examples before PowerShell examples to prioritize cross-platform guidance.
  • Add a note clarifying that PowerShell examples are for Windows users, and suggest CLI for Linux/macOS users.
  • Ensure parity in example detail and completeness between CLI and PowerShell sections.
  • Where possible, provide bash shell script snippets for Linux users alongside CLI examples.
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 page is focused on Linux VM extensions, but consistently presents both Azure CLI and Azure PowerShell examples side-by-side throughout. In several sections, PowerShell examples are given equal prominence to CLI, despite PowerShell being a Windows-centric tool (even though it is cross-platform, its usage is far more common on Windows). Additionally, in the 'Discover VM extensions' section, the PowerShell example is shown after the CLI example, but both are given full code blocks and explanations. There is no evidence of missing Linux examples or exclusive mention of Windows tools, but the parity between CLI and PowerShell may create a subtle Windows-first impression.
Recommendations
  • Consider emphasizing Azure CLI as the primary example for Linux-focused documentation, since CLI is natively available on Linux and macOS, while PowerShell is less commonly used in those environments.
  • Where PowerShell is included, clarify its cross-platform availability and typical use cases for Linux users.
  • If space or clarity is a concern, offer PowerShell examples in expandable sections or as supplementary material, rather than giving them equal prominence.
  • Review the ordering of examples to ensure CLI is presented first in all cases for Linux documentation.
  • Add explicit notes or links for Linux users on how to install and use PowerShell if they choose to use it.
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 alongside Azure CLI and ARM template examples. In several sections, PowerShell is presented before Azure CLI, which is more native to Linux environments. There is also a mention of a Windows extension, but it is clearly separated and not the main topic. All troubleshooting and manual steps are Linux-centric, and Linux tools and commands are used throughout.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is the primary cross-platform tool and more relevant for Linux users.
  • Clearly indicate that PowerShell is optional and primarily for users on Windows or those who prefer it, while Azure CLI is recommended for Linux/macOS.
  • Consider adding Bash script examples for common deployment scenarios, since Bash is native to Linux.
  • Review the order of example sections to ensure Linux-native tools are prioritized.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides thorough Linux-specific guidance. However, there is evidence of Windows bias in the deployment sections: PowerShell examples are given before Azure CLI examples, and troubleshooting commands are shown first in PowerShell. The PowerShell deployment section is more detailed and prominent, despite the extension being Linux-only. There are no missing Linux examples, and all configuration paths, logs, and certificate handling are Linux-centric.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more relevant for Linux users.
  • Reduce the prominence of PowerShell deployment instructions or clarify that PowerShell is primarily for Windows users.
  • Add explicit notes that Azure CLI is recommended for Linux environments.
  • Ensure troubleshooting instructions highlight CLI commands first.
  • Consider removing PowerShell deployment instructions unless there is a clear use case for Linux administrators using PowerShell.
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 provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, in several sections, Windows/Hyper-V tools and workflows are presented first or with more detail, such as disk conversion instructions referencing Hyper-V Manager and PowerShell cmdlets before Linux alternatives. Linux/KVM/VMware instructions are present and thorough, but Windows/Hyper-V is often prioritized in ordering and introductory notes.
Recommendations
  • Reorder sections so that Linux-native hypervisors (KVM, VMware) are presented before Hyper-V/Windows tools, or group them equally.
  • When mentioning disk conversion tools, list Linux-native tools (qemu-img, guestfish) alongside or before Windows/Hyper-V tools.
  • Where possible, provide parity in detail and step-by-step instructions for Linux/KVM/VMware workflows, matching the clarity and completeness of Hyper-V sections.
  • Add a summary table at the top outlining the supported hypervisors and tools for both Windows and Linux, making it clear that Linux workflows are fully supported.
  • Avoid referencing Windows/PowerShell tools (e.g., convert-vhd cmdlet) before Linux equivalents unless contextually necessary.
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 signs of Windows bias. PowerShell examples and references are given alongside CLI, but PowerShell is mentioned first in several places. Windows-specific tools (Sysprep) are referenced before Linux equivalents (waagent). Some links and examples are Windows-focused or presented before Linux alternatives. However, Linux support is acknowledged, and CLI examples are provided, so Linux users can complete the tasks.
Recommendations
  • Ensure Linux and Windows examples are presented in parallel, alternating order or grouped by OS.
  • Provide explicit Linux-focused examples and links wherever Windows examples are given (e.g., for uploading VHDs, generalizing images).
  • Avoid mentioning PowerShell first; alternate with CLI or Bash examples.
  • Where possible, use cross-platform tools (Azure CLI) as the primary example, and supplement with PowerShell only as needed.
  • Review linked pages to ensure Linux parity in referenced content.
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
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell example is given equal prominence, and the CLI example is not explicitly labeled as Linux/macOS-friendly. The tab order presents CLI first, but the PowerShell section is detailed and assumes familiarity with Windows tools. There is no explicit mention of Linux-specific considerations or alternative Linux-native tools.
Recommendations
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
  • Explicitly mention that PowerShell examples are primarily for Windows users, while CLI is recommended for Linux/macOS.
  • Consider adding a note or section for Linux users, confirming that all quota management tasks can be performed using Azure CLI.
  • If relevant, provide example commands for Bash or other common Linux shells, or mention that Azure CLI can be installed natively on Linux.
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Gen2 VMs ...rticles/virtual-machines/trusted-launch-existing-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 parity for both Linux and Windows VMs, including explicit statements that the feature applies to both. However, there is a mild Windows bias in the ordering and tooling: PowerShell examples are provided alongside CLI and ARM template, but PowerShell is a Windows-centric tool and its installation instructions link to Windows-specific pages. Additionally, in some sections, PowerShell is listed before CLI, and screenshots reference RDP (Windows) before SSH (Linux). The documentation does mention Linux-specific validation (SBInfo tool), but overall, Windows tools and patterns are slightly prioritized.
Recommendations
  • Add explicit instructions or links for installing Azure PowerShell on Linux/macOS, not just Windows.
  • Where possible, clarify that PowerShell can be used cross-platform, or highlight CLI as the preferred cross-platform tool.
  • Alternate the order of CLI and PowerShell sections, or list CLI first to emphasize cross-platform accessibility.
  • Ensure screenshots and example text reference SSH (Linux) and RDP (Windows) equally, or alternate their order.
  • Consider adding Bash shell script examples for Linux users, if relevant.
GitHub Create Pull Request
Virtual Machines FAQ for Trusted Launch ...b/main/articles/virtual-machines/trusted-launch-faq.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The FAQ for Trusted Launch covers both Windows and Linux VM scenarios. However, there is a mild Windows bias: PowerShell examples are consistently provided alongside CLI, and Windows-specific terminology and links (e.g., Secure Boot, Hyper-V) often appear first or are referenced before Linux equivalents. While Linux examples and troubleshooting are present (especially for Secure Boot validation and SBInfo tool usage), Windows examples and tools are sometimes prioritized or more detailed. The documentation does not omit Linux information, but Windows examples are often shown first and PowerShell is always included.
Recommendations
  • Alternate the order of CLI and PowerShell examples so Linux CLI is not always second.
  • Where possible, provide Bash shell examples for Linux users alongside PowerShell.
  • Ensure Linux-specific troubleshooting and validation steps are as prominent and detailed as Windows equivalents.
  • Add explicit notes clarifying parity between Windows and Linux for each feature or command.
  • Consider including macOS-specific notes or examples where relevant (e.g., Azure CLI usage on macOS).
GitHub Create Pull Request