← Back to Dashboard
237
Pages Scanned
85
Pages Flagged
237
Changed Pages
35.9%
% Pages Flagged

Scan Information

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

Finished At: 2026-02-10 18:44:36

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 237

Files Completed: 237

Problematic Pages

84 issues found
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 page for Azure Service Fabric reverse proxy clearly states that reverse proxy is not available for Linux clusters, and all examples, instructions, and references are Windows-centric. There are no Linux equivalents or alternative guidance for Linux users, and the page assumes a Windows environment throughout.
Recommendations
  • Explicitly clarify at the top of the page that reverse proxy is a Windows-only feature, and provide links to Linux alternatives or workarounds if available.
  • Add guidance for Linux users on how to achieve similar functionality, or direct them to supported Service Fabric features for Linux clusters.
  • Consider splitting documentation so that Windows-only features are clearly separated from cross-platform features, reducing confusion for Linux/macOS users.
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: 2 bias types
Detected Bias Types
⚠️ windows_only ⚠️ missing_linux_example
Summary
Although the page introduction claims Service Fabric clusters run on both Windows Server and Linux, the 'Supported operating systems' section explicitly states that Linux isn't yet supported for standalone clusters. All examples, recommendations, and security patterns reference Windows Server and Windows-specific features (Kerberos, Active Directory, group Managed Service Accounts), with no Linux equivalents or guidance. This creates a strong Windows bias, and Linux users cannot deploy standalone clusters following this documentation.
Recommendations
  • Clarify in the introduction that standalone clusters are currently Windows-only, and Linux support is not available yet.
  • Remove or update the misleading statement in the description about Linux support.
  • If Linux support is planned, provide a timeline or link to relevant tracking issues.
  • Once Linux support is available, add Linux-specific instructions, examples, and security guidance.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page primarily references Windows custom images and provides PowerShell commands for role assignment, with no equivalent Linux CLI or Bash examples. While it mentions Azure Marketplace images and links to both Linux and Windows image tutorials, the main workflow and examples are Windows-centric, and Linux-specific instructions are missing for key steps.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for role assignment and other operations currently shown only in PowerShell.
  • Clarify whether Linux custom images are supported for Service Fabric Managed Clusters and, if so, include explicit instructions and examples for Linux images.
  • Ensure that references to image creation and deployment include both Windows and Linux workflows, or clearly state any platform limitations.
  • Where links to external tutorials are provided, summarize the Linux steps inline for parity.
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 examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. However, all CLI/scripted examples use PowerShell cmdlets (e.g., New-AzServiceFabricManagedNodeType, Remove-AzServiceFabricManagedNodeType), with no mention of Azure CLI equivalents or Bash scripting. There are no Linux/macOS-specific instructions or examples, and PowerShell is presented as the only scripting interface, which may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell (e.g., adding, removing, scaling node types).
  • Explicitly state whether PowerShell cmdlets are cross-platform (PowerShell Core) or require Windows.
  • If Azure CLI does not support certain operations, clarify this and provide guidance for Linux/macOS users (e.g., using ARM templates via az deployment).
  • Consider including Bash scripting examples for ARM template deployments.
  • Add a note about cross-platform management options for Service Fabric managed clusters.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation is heavily focused on PowerShell-based workflows, requiring the Microsoft.ServiceFabric.Powershell.Http module and providing all code examples in PowerShell. There are no CLI, Bash, or cross-platform REST examples using tools like curl, nor any mention of Linux/macOS alternatives for connecting to the cluster or invoking REST APIs. This creates friction for Linux/macOS users, who must translate all examples and may not have access to the required PowerShell modules.
Recommendations
  • Provide equivalent examples using Bash and curl for REST API calls, demonstrating how to authenticate and invoke the same Service Fabric APIs from Linux/macOS.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available and supported on PowerShell Core (pwsh) on Linux/macOS. If not, explicitly state this limitation.
  • Include instructions for connecting to Service Fabric clusters and managing certificates on Linux/macOS, or link to relevant documentation.
  • Where possible, use Azure CLI or cross-platform tools for authentication and management, or at least mention them as alternatives.
  • Add a section summarizing cross-platform support and any limitations for non-Windows users.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation is heavily focused on PowerShell cmdlets for Service Fabric application upgrades, with all command-line examples using PowerShell syntax and referencing Windows-specific tools. There are no CLI or Linux-native examples (such as Azure CLI, Bash, or REST API), and the documentation does not mention or link to cross-platform alternatives. This creates friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Add Azure CLI examples (az sf application upgrade, az sf service create, etc.) alongside PowerShell cmdlets.
  • Mention REST API options for application and service upgrades, with example payloads.
  • Clarify which operations are only available via PowerShell (if any), and provide guidance for Linux/macOS users.
  • Link to cross-platform Service Fabric SDK/CLI documentation where appropriate.
  • If PowerShell Core (pwsh) is supported cross-platform, clarify this and provide examples using it on Linux/macOS.
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 ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides some cross-platform information (e.g., mentions both 'ServiceFabricLinuxNode' and 'ServiceFabricNode' in the extension type), but several examples and guidance are Windows-centric. The dataPath example uses a Windows path (D:\\SvcFab), and the 'Next steps' section links to PowerShell scripts for RDP port and user management, which are Windows-specific. There are no explicit Linux/macOS command examples or references to SSH or Linux-native tools for remote access or management.
Recommendations
  • Add Linux/macOS-specific examples for remote connection (e.g., SSH instructions) alongside or in place of RDP/PowerShell examples.
  • Provide Linux file path examples (e.g., /var/lib/servicefabric) in the extension snippet and property descriptions.
  • Include references or links to Linux-native management scripts or Azure CLI usage for Linux clusters.
  • Clarify in the 'Next steps' section which scripts or guides are Windows-only, and provide Linux equivalents where possible.
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 frequently references Windows Server clusters and Windows security options, providing explicit links and instructions for Windows scenarios. While it mentions that concepts apply to both Linux and Windows clusters, there are no direct examples, instructions, or links for Linux standalone clusters. Windows-specific configuration steps and recommendations are given more prominence, and Linux users may find it unclear how to implement equivalent security measures for standalone clusters.
Recommendations
  • Add explicit instructions and links for securing standalone Linux Service Fabric clusters, including certificate setup and configuration.
  • Provide parity in examples and walkthroughs for Linux environments, such as using Linux tools (e.g., OpenSSL) for certificate generation and installation.
  • Clarify which security features and steps apply equally to Linux clusters, and highlight any differences or limitations.
  • Include Linux-specific recommendations and best practices for Service Fabric cluster security.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides code examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all command-line examples are exclusively in PowerShell, with no Linux shell (bash/CLI) equivalents. The PowerShell cmdlets and object types shown are Windows-centric, and there is no mention of how to perform these operations on Linux clusters or using cross-platform tools. This creates friction for Linux users, especially those running containerized workloads on Linux nodes.
Recommendations
  • Add equivalent examples using Azure CLI or REST API, which are cross-platform and usable on Linux/macOS.
  • Explicitly document any differences or limitations for Linux clusters, especially regarding management tools and supported features.
  • If PowerShell is required, clarify whether PowerShell Core (cross-platform) is supported and provide installation guidance for Linux/macOS.
  • Include bash or shell script examples for common operations where possible.
  • Reference Linux-specific documentation or tooling for Service Fabric cluster management.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides PowerShell and ApplicationManifest.xml (Visual Studio) examples for setting DNS names, but does not include Linux-native equivalents (e.g., Azure CLI, Bash, or cross-platform tools). It also references Visual Studio and PowerShell before mentioning ARM templates, and does not provide Linux command-line examples for common tasks. Additionally, enabling DNS service through the Azure portal is not supported for Linux clusters, but this limitation is noted. Overall, the documentation assumes a Windows-centric workflow for several key operations.
Recommendations
  • Add Azure CLI examples for enabling DNS service and setting DNS names, especially for Linux users.
  • Provide Bash or cross-platform scripting examples where PowerShell is used.
  • Explicitly mention and link to Linux-native tools or workflows for managing Service Fabric clusters and services.
  • Clarify which steps are Windows-only and provide alternative instructions for Linux where possible.
  • Reorder sections to present ARM template and CLI-based approaches before PowerShell and Visual Studio examples, to avoid Windows-first bias.
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 ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for the Fault Analysis Service overview provides usage instructions for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell (via the Service Fabric SDK and PowerShell module). There are no examples or guidance for Linux/macOS users, such as using Bash, CLI, or REST API equivalents. The focus on PowerShell and lack of Linux tooling or examples creates friction for non-Windows users.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI, Bash, or REST API to support Linux/macOS users.
  • Clarify whether the PowerShell instructions are Windows-only, and provide alternative instructions for Linux/macOS environments if available.
  • Indicate platform requirements for the Service Fabric SDK and Fault Analysis Service usage, so users know what is supported on their OS.
  • If certain features are Windows-only, explicitly state this to avoid confusion.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation is heavily focused on Windows tooling, specifically Visual Studio and PowerShell, for upgrading Service Fabric applications. All examples and instructions reference Windows-centric tools and workflows, with no mention of Linux/macOS alternatives or cross-platform CLI options. This creates friction for users on non-Windows platforms, as they are not provided with guidance or examples relevant to their environments.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), where possible.
  • Clarify which steps are Windows-only and provide alternative workflows for Linux/macOS users, especially for manual upgrades.
  • Include Linux/macOS shell examples (e.g., Bash) alongside PowerShell examples for hash table input formats and manifest editing.
  • Explicitly state platform requirements and limitations at the beginning of the document, so non-Windows users can quickly assess applicability.
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 and Visual Studio workflows. All examples and instructions reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish), and PowerShell is mentioned as the only CLI example for service creation. There is no mention of Linux/macOS tooling, nor are cross-platform alternatives (such as Azure CLI, SFCTL, or VS Code) discussed. This creates friction for Linux/macOS users who may use Service Fabric in non-Windows environments.
Recommendations
  • Add explicit notes clarifying that StartupServices.xml is only supported for Visual Studio deployments on Windows.
  • Provide alternative instructions or links for Linux/macOS users, such as using ARM templates, Azure CLI, or SFCTL for service deployment and configuration.
  • Mention that the Visual Studio workflow is Windows-only and suggest cross-platform development environments (e.g., VS Code) for non-Windows users, with guidance on how to manage service configuration in those contexts.
  • Include examples of deploying Service Fabric applications using non-Windows tools where possible.
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 consistently provides only PowerShell-based deployment examples and command-line instructions, with no mention of Azure CLI, Bash, or Linux/macOS workflows. Windows tools and patterns (e.g., RDP, Windows-style paths, PowerShell prompts) are used exclusively and presented first, making it less accessible for Linux/macOS users.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps.
  • Include instructions for accessing VMs using SSH (for Linux/macOS) in addition to RDP.
  • Use platform-neutral file paths and prompts in examples, or provide both Windows and Linux/macOS variants.
  • Explicitly state that the templates and procedures are cross-platform, and clarify any platform-specific requirements.
  • Reference Bash or shell scripting alternatives where applicable.
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 a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits a moderate Windows bias. PowerShell is the only scripting example shown for programmatic certificate enrollment, and references to Windows-specific mechanisms (such as S-channel, ACLing, and Key Vault VM extension for Windows) are prominent. The Key Vault VM extension is described primarily in its Windows context, and the linking feature is explicitly stated as 'Only Windows.' Linux equivalents (such as Linux VM extensions, CLI, or bash scripting) are not mentioned, and Windows-centric terminology and examples appear first or exclusively.
Recommendations
  • Provide Linux/macOS equivalents for scripting and automation, such as Azure CLI or bash examples for certificate enrollment and management.
  • Reference and link to the Key Vault VM extension for Linux documentation, and clarify differences in behavior or configuration.
  • Discuss certificate provisioning and ACLing in the context of Linux nodes (e.g., file permissions, certificate stores), especially for clusters that may run on Linux VMSS.
  • Where Windows-specific features (like S-channel or CERT_RENEWAL_PROP_ID) are discussed, explicitly note their absence or alternatives on Linux.
  • Balance example order so that Linux/macOS approaches are presented alongside or before Windows-specific ones where applicable.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias by prioritizing Azure PowerShell examples and references in the 'Best practices' section, listing PowerShell before Azure CLI, and omitting explicit Linux/macOS command examples for cluster management tasks. While ARM templates, Bicep, and Azure CLI are mentioned, actionable examples and links are PowerShell-centric, which may create friction for Linux/macOS users.
Recommendations
  • Provide explicit Azure CLI examples and links for all management tasks currently shown with PowerShell (e.g., deleting NodeType, restarting/reimaging scale sets).
  • Ensure that CLI commands are shown alongside PowerShell commands in all relevant sections.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS users.
  • Consider reordering examples so that CLI and PowerShell are presented equally, or CLI is shown first for cross-platform parity.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page for RunToCompletion semantics in Azure Service Fabric demonstrates a notable Windows bias. All code examples use Windows containers (nanoserver:1809) and Windows command syntax (cmd, set, exit, etc.), with explicit references to Windows container compatibility. Querying deployment status is shown only via PowerShell and C# APIs, both Windows-centric tools. There are no Linux container examples, nor any mention of Linux shell commands or querying tools. The documentation does not clarify whether RunToCompletion semantics are supported for Linux containers, nor does it provide guidance for Linux users.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu, Alpine) and Linux shell commands (bash, echo, exit, etc.) to demonstrate RunToCompletion semantics for non-Windows environments.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and guest executables, and note any platform limitations.
  • Provide instructions for querying deployment status using cross-platform tools (e.g., Azure CLI, REST API) or Linux-native equivalents.
  • Reorder examples or provide parallel Windows and Linux sections to avoid Windows-first presentation.
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: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation on X.509 Certificate-based Authentication in Service Fabric clusters exhibits moderate Windows bias. Windows terminology and tools (e.g., certificate stores like LocalMachine\My, Win32 CryptoAPI, Windows event logs, CAPI2 logging) are referenced first and in detail, while Linux equivalents are mentioned briefly or parenthetically. Troubleshooting and configuration examples focus on Windows paths and APIs, with limited guidance for Linux users. There are no explicit Linux/macOS command-line examples or troubleshooting steps.
Recommendations
  • Provide Linux/macOS-specific examples for certificate management (e.g., using OpenSSL, Linux file paths, and certificate stores).
  • Expand troubleshooting guidance to include Linux/macOS log locations and diagnostic tools.
  • Clarify how Service Fabric certificate presentation and validation works on Linux, including differences in certificate storage and access.
  • When referencing Windows-specific APIs or tools, offer Linux/macOS alternatives or note platform differences.
  • Include explicit Linux/macOS configuration snippets and step-by-step instructions where relevant.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service throttling, with no equivalent CLI or Linux/macOS instructions. It references Service Fabric Explorer, which is cross-platform, but omits Linux-native command-line options. The overall guidance assumes familiarity with Windows tooling.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for managing Infrastructure Service operations, especially for bypassing throttling.
  • Clarify whether the PowerShell command is required or if alternatives exist for Linux/macOS users.
  • Explicitly mention cross-platform management options and tools where available.
  • Add a note about platform requirements for the PowerShell command, and link to Linux/macOS-compatible instructions if possible.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, using Windows-specific images, file paths, and commands (cmd, C:\ paths, type, ping). There is no mention of Linux container equivalents, nor are Linux file paths, shell commands, or images referenced. The example and guidance are exclusively Windows-focused, which creates friction for Linux users seeking parity.
Recommendations
  • Add a parallel example using Linux containers (e.g., mcr.microsoft.com/ubuntu or other Linux images), with Linux shell commands (bash/sh), file paths (/workspace/log.txt), and appropriate volume mounts.
  • Clarify whether Initializer CodePackages are supported for Linux containers in Service Fabric, and if so, provide guidance and examples.
  • If there are limitations or differences for Linux containers, explicitly document them to help users understand platform-specific behavior.
  • Present examples for both Windows and Linux containers, or clearly indicate platform scope at the beginning of the article.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page predominantly references PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for managing Service Fabric resources, with no mention of equivalent Bash/CLI commands or Linux/macOS workflows. While az resource is referenced, PowerShell examples and terminology are given first and most frequently, which may create friction for Linux/macOS users who typically use Bash and the Azure CLI.
Recommendations
  • Provide Azure CLI (az) command examples alongside PowerShell cmdlets for all operations, especially for resource deletion, creation, and scaling.
  • Clarify that az CLI commands work cross-platform and are recommended for Linux/macOS users.
  • Reorder examples to present CLI and PowerShell options equally, or group them by platform.
  • Add notes or links for Linux/macOS users on how to perform these operations without PowerShell.
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 both Windows and Linux Service Fabric clusters, but there is a tendency to mention Windows tools and patterns first, such as Event Log/Event Viewer, ETW, and Diagnostics Agent. Some examples and tutorials are Windows/.NET-focused, and Linux equivalents are referenced but not always given equal detail or example coverage. Linux-specific configuration is sometimes only linked, not described inline. PowerShell is mentioned as an automation option, but Linux CLI or scripting alternatives are not highlighted.
Recommendations
  • Provide Linux-specific examples and walkthroughs alongside Windows ones, especially for cluster monitoring and diagnostics setup.
  • When referencing tools (e.g., Event Viewer, ETW), also mention and briefly describe Linux equivalents (e.g., LTTng, Syslog) in the same section.
  • Include sample commands or scripts for Linux environments (e.g., Bash, CLI) where PowerShell is referenced.
  • Ensure that tutorials and code samples for application monitoring include Linux/.NET Core scenarios, not just .NET Framework/Windows.
  • Clarify in each section whether the guidance applies to both Windows and Linux, and link to Linux-specific documentation where appropriate.
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 page is generally platform-neutral in its description of Service Fabric application and service manifests, focusing on XML configuration and concepts. However, there is a notable Windows bias in the tooling recommendations: the warning section suggests using Visual Studio on Windows and references the ServiceFabricServiceModel.xsd file path in 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas', which is a Windows-specific location. Additionally, PowerShell is mentioned as a way to create service instances before any Linux alternatives, and there are no explicit Linux/macOS tooling or workflow examples provided.
Recommendations
  • Add equivalent instructions for Linux/macOS users, such as how to validate manifest XML schemas using cross-platform editors (e.g., VS Code, JetBrains Rider) and where to find the ServiceFabricServiceModel.xsd file on non-Windows systems.
  • Mention cross-platform Service Fabric CLI (sfctl) or Azure CLI commands for creating service instances, alongside or before PowerShell.
  • Where file paths are referenced, provide both Windows and Linux/macOS examples.
  • Explicitly state that the manifest authoring and deployment process is supported on Linux/macOS, and link to relevant cross-platform tooling documentation.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page for the Service Fabric application lifecycle demonstrates a notable Windows bias. PowerShell cmdlets are referenced extensively and often listed before or alongside REST and .NET API methods, with no mention of Linux-native CLI equivalents (such as sfctl or Azure CLI) in the main lifecycle sections. The workflow examples and automation guidance rely heavily on PowerShell, which is primarily a Windows tool, and there is little to no explicit guidance for Linux/macOS users, despite Service Fabric supporting cross-platform clusters and management.
Recommendations
  • Include Linux/macOS-friendly command-line examples using sfctl and Azure CLI in all lifecycle phases (deploy, upgrade, remove, etc.), not just in the introductory links.
  • Where PowerShell cmdlets are mentioned, provide equivalent sfctl or Azure CLI commands side-by-side.
  • Add explicit notes or sections for Linux/macOS users, clarifying any differences or limitations in tooling or workflow.
  • Ensure automation examples (such as cleanup policies) are shown using cross-platform tools/scripts, not just PowerShell.
  • Review and update links to point to cross-platform documentation where available.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page is generally platform-neutral in its discussion of data serialization and rolling upgrades in Azure Service Fabric. However, in the 'Next steps' section, upgrade tutorials are presented for Visual Studio and PowerShell, both of which are primarily Windows-centric tools. No Linux/macOS equivalents (such as CLI or cross-platform IDEs) are mentioned or linked, and PowerShell is highlighted before any Linux-friendly options.
Recommendations
  • Add links or references to upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are available on Linux/macOS.
  • Include examples or tutorials for application upgrades using non-Windows environments, or clarify if certain upgrade paths are Windows-only.
  • Mention cross-platform IDEs (such as VS Code) if relevant for application upgrade workflows.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page on Azure Service Fabric architecture references PowerShell cmdlets as the primary example of management tooling, and mentions Windows security as a transport option before X509 certificates. No Linux-specific management tools or examples are provided, and PowerShell is referenced without mention of cross-platform alternatives, creating a subtle Windows-first bias.
Recommendations
  • Explicitly mention cross-platform management options, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
  • Clarify that PowerShell is available on Linux/macOS, or provide equivalent Linux/macOS command examples where appropriate.
  • When discussing security, list X509 certificates before or alongside Windows security, and note Linux compatibility.
  • Add a brief note or section highlighting how Linux users can interact with Service Fabric clusters, including supported tools and workflows.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides several PowerShell-based examples and instructions (e.g., using Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning or providing Linux/macOS equivalents. There is an implicit assumption that users are operating in a Windows environment, and no CLI or bash alternatives are given. This creates friction for Linux/macOS users, especially when performing manual scaling operations.
Recommendations
  • For every PowerShell command (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState), provide equivalent instructions using the Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Explicitly mention that the PowerShell commands are for Windows and link to Linux/macOS alternatives where available.
  • Add bash or CLI examples for common scaling operations, or reference official documentation for Linux/macOS users.
  • Clarify in the relevant sections that both Windows and Linux clusters are supported, and provide parity in operational guidance.
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 generally covers Service Fabric security concepts in a cross-platform manner, but several sections show a Windows-first bias. Examples and references to Windows-specific features (Active Directory, gMSA, BitLocker) are given before or in more detail than Linux equivalents. Some features (like disk encryption) only link to Windows/PowerShell guides, with Linux instructions missing or marked as TODO. There are few explicit Linux examples or parity notes for key scenarios.
Recommendations
  • Add explicit Linux examples for disk encryption and securing application data at rest, including links to relevant Azure documentation for Linux VMSS disk encryption.
  • Where Windows-specific features (e.g., gMSA, AD accounts) are mentioned, clarify their platform scope and provide Linux alternatives or state if not applicable.
  • Ensure that API gateway and container security sections include Linux-specific guidance and examples, especially for certificate management.
  • Review all example code and configuration snippets to ensure they are platform-neutral or provide both Windows and Linux variants where appropriate.
  • Update TODOs (e.g., 'Encrypt disks on Linux clusters?') with actual guidance or links to Linux documentation.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page presents PowerShell and Visual Studio (Windows-centric tools) parameters and workflows first, with more detailed tables and examples, before covering the cross-platform Service Fabric CLI (sfctl) approach. PowerShell-specific parameters and patterns are described in detail, while Linux/macOS users (who would use sfctl) receive less prominent placement and fewer usage examples. There are no explicit Linux/macOS command-line examples in the main body, and the CLI section is less detailed. The 'Next steps' section does link to Linux/sfctl and Eclipse plugin guides, but the primary focus remains on Windows tools.
Recommendations
  • Reorder sections so that cross-platform tools (sfctl) are presented before or alongside Windows-specific tools (PowerShell, Visual Studio).
  • Provide equally detailed parameter tables and usage examples for sfctl, including example commands for common upgrade scenarios.
  • Explicitly mention that sfctl is the recommended approach for Linux/macOS users, and clarify tool parity.
  • Where PowerShell-specific syntax is shown (e.g., hashtable examples), provide equivalent JSON or CLI examples for sfctl.
  • Add a short summary table at the top comparing the three main upgrade methods (PowerShell, Visual Studio, sfctl) and their platform compatibility.
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 upgrade demonstrates a notable Windows bias. The only code example provided uses PowerShell cmdlets, which are traditionally Windows-centric and may not work natively on Linux/macOS clusters. References to Windows-specific tools (e.g., http.sys, PowerShell, Visual Studio) are present throughout the page, with no equivalent Linux or cross-platform instructions. The 'Next steps' section prioritizes Windows tooling (Visual Studio, PowerShell) and omits guidance for Linux users or Service Fabric CLI usage.
Recommendations
  • Provide equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include notes or sections clarifying how Linux/macOS users can perform application upgrades, including any differences in workflow or tooling.
  • Add references to Linux-compatible tools and patterns (e.g., bash scripts, sfctl commands) alongside or before Windows/PowerShell examples.
  • Ensure that upgrade scenarios involving http.sys or other Windows-only APIs are clearly marked as Windows-specific, and offer Linux alternatives or caveats where appropriate.
  • Expand 'Next steps' to include tutorials for upgrading applications using cross-platform tools.
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 ⚠️ missing_linux_example
Summary
The documentation page for configuring periodic backups in Azure Service Fabric is generally platform-neutral, but the only on-premises backup storage example provided is for Windows file shares (with Integrated Windows Authentication and UNC paths). There are no examples or mentions of Linux-compatible storage options (such as NFS or SMB with Linux authentication), nor guidance for Linux clusters. This may create friction for Linux users deploying standalone Service Fabric clusters.
Recommendations
  • Add examples for configuring backup storage using Linux-compatible file shares, such as NFS mounts or SMB shares accessed from Linux nodes.
  • Clarify whether the FileShare storage option supports Linux clusters and, if so, provide authentication and path examples relevant to Linux environments.
  • Explicitly state any platform limitations for backup storage types (e.g., if FileShare is Windows-only, mention alternatives for Linux).
  • Consider including a note or section on best practices for backup storage configuration on Linux-based Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation for restoring backups in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all CLI/API examples provided exclusively in PowerShell syntax. The prerequisite section requires installation of a PowerShell module, and all command-line instructions use PowerShell cmdlets or scripts. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools. The documentation implicitly assumes a Windows environment and does not mention alternatives for non-Windows platforms.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls, demonstrating how Linux/macOS users can perform the same operations.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all platforms, and if not, provide platform-specific instructions.
  • Explicitly mention cross-platform support and provide guidance for Linux/macOS users, including any required authentication steps (e.g., certificate handling) in Bash.
  • If Service Fabric supports REST API calls directly, provide generic HTTP request examples that do not depend on PowerShell.
  • Reorder examples so that REST API usage is shown first, followed by platform-specific tooling.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell is featured prominently and exclusively for several critical operations (e.g., cluster upgrade). Windows-specific configuration details, such as registry keys and Windows Update settings, are described without Linux equivalents or guidance. The upgrade instructions rely solely on PowerShell, with no Linux shell or cross-platform alternatives provided. Windows-related tools and patterns (registry, PowerShell, WindowsUpdate) are mentioned before or instead of Linux approaches.
Recommendations
  • Provide equivalent Linux shell (bash) commands for cluster upgrade operations currently shown only in PowerShell.
  • Include Linux-specific configuration guidance for disabling automatic updates or managing patching, analogous to the Windows registry and WindowsUpdate settings.
  • Where Windows-specific instructions are given (e.g., registry keys), clarify if/how Linux users should perform similar steps or state that no action is needed.
  • Balance example order: present Azure CLI and Linux shell examples before or alongside PowerShell/Windows examples.
  • Explicitly call out differences or limitations between Windows and Linux clusters in relevant sections.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation generally covers both Windows and Linux scenarios for Service Fabric security, but there is a tendency to present Windows-specific tools and examples first, such as PowerShell commands for certificate management and encryption. Windows Defender and Windows security baselines are discussed in detail, while Linux equivalents are either omitted or referenced only briefly. Some sections (e.g., Windows Defender) are Windows-only by nature, but others could provide more Linux parity.
Recommendations
  • Present Windows and Linux examples side-by-side or alternate which is shown first to avoid implicit prioritization.
  • For sections like security baselines and antivirus, mention recommended Linux equivalents (e.g., CIS benchmarks, ClamAV, or other Linux security tools) and link to relevant documentation.
  • Where PowerShell is used for Windows, provide equivalent Bash/openssl commands for Linux where possible, or link to Linux-specific guides.
  • Clarify when a feature or recommendation is Windows-only, and provide Linux alternatives or explicitly state when no equivalent exists.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides code samples in C# and PowerShell only, with no mention of Linux command-line equivalents or cross-platform CLI tools. PowerShell is a Windows-centric tool, and its use throughout the examples suggests a Windows-first approach. There is no guidance for Linux/macOS users on how to perform these tasks, nor are alternatives like Azure CLI or REST API referenced.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include REST API or ARM template snippets for placement policy configuration, as these are OS-agnostic.
  • Explicitly mention how Linux/macOS users can perform these operations, or link to relevant cross-platform tooling.
  • Clarify if PowerShell Core (pwsh) is supported for these commands, and provide examples if so.
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 references for Service Fabric networking, but there is a notable Windows-first bias in several sections. PowerShell is mentioned as the primary API client, and Windows-specific tools and examples (such as netsh and RDP) are referenced without equivalent Linux commands or alternatives. Some examples and ARM templates are Windows-focused, and Linux-specific guidance is less detailed or omitted.
Recommendations
  • Include Linux CLI (az, bash) examples alongside or before PowerShell examples, especially for common operations.
  • Provide Linux equivalents for Windows-specific tools (e.g., show how to check dynamic port ranges on Linux).
  • Reference Linux-focused ARM templates and sample clusters where appropriate.
  • Clarify when instructions or examples apply only to Windows, and provide parallel Linux guidance where possible.
  • Ensure that application networking and security sections mention Linux container scenarios and tools (e.g., iptables, SSH, Linux firewall configuration).
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 provides command-line examples exclusively using PowerShell cmdlets for Service Fabric application management tasks, with no mention of Linux shell equivalents or cross-platform CLI tools. This creates friction for Linux/macOS users, as PowerShell is a Windows-centric tool and the Service Fabric CLI (sfctl), which is cross-platform, is not referenced. All automation and scripting examples are either PowerShell or C#, with no Bash or sfctl usage.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is supported on Linux and macOS.
  • Include Bash shell examples for common tasks where appropriate.
  • Clarify which commands are Windows-only and provide cross-platform alternatives where possible.
  • Add a note about platform support for PowerShell cmdlets and recommend sfctl for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides code examples for C# and PowerShell, with PowerShell being the only CLI example shown for service creation and metric configuration. There are no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API), and PowerShell is presented as the default scripting interface. This creates friction for users managing Service Fabric clusters from non-Windows platforms.
Recommendations
  • Add Azure CLI or REST API examples for service creation and metric configuration, alongside PowerShell.
  • Explicitly mention cross-platform management options for Service Fabric (e.g., Azure CLI, REST API, or Service Fabric CLI).
  • Clarify when PowerShell is required and provide guidance for Linux/macOS users on alternative workflows.
  • Reorder examples so that platform-neutral options (e.g., REST API, Azure CLI) are presented before or alongside PowerShell.
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 provides PowerShell examples for creating and updating Service Fabric services with move cost, but does not offer equivalent CLI or bash examples for Linux/macOS users. PowerShell is a Windows-centric tool, and its use as the sole shell example creates friction for users managing Service Fabric clusters from Linux or macOS. The C# API examples are cross-platform, but operational/management examples are Windows-first and lack Linux parity.
Recommendations
  • Add Azure CLI or REST API examples for creating and updating Service Fabric services with move cost, as these are cross-platform and commonly used on Linux/macOS.
  • If PowerShell is required, clarify whether PowerShell Core is supported on Linux/macOS and provide usage notes.
  • Explicitly mention management options for Linux/macOS users, such as Service Fabric CLI (sfctl) or REST API, and provide equivalent examples.
  • Reorder examples so that cross-platform options appear before or alongside Windows-specific tools.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides configuration and code examples for describing and managing Service Fabric clusters using Cluster Resource Manager. While the concepts are platform-neutral, the examples and tooling references show a notable Windows bias: PowerShell and WindowsServer XML configuration are presented first and more prominently, with no equivalent Linux CLI or Bash examples. The documentation does not mention Linux-specific configuration patterns or Service Fabric management tools, nor does it clarify how Linux users should adapt the PowerShell or WindowsServer examples.
Recommendations
  • Add Linux/Bash CLI examples alongside PowerShell for service creation and updates (e.g., using sfctl or REST API).
  • Include configuration snippets for Linux-based Service Fabric clusters (e.g., referencing 'Linux' infrastructure in ClusterManifest.xml or clarifying differences).
  • Explicitly state which examples are Windows-only and provide guidance or links for Linux users.
  • Where PowerShell is shown, add equivalent Linux command-line or API usage to ensure parity.
  • Clarify any platform-specific limitations or differences in resource manager behavior.
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 ⚠️ missing_linux_example
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying health information, but does not include equivalent examples for Linux/macOS environments or Service Fabric CLI (sfctl). The only command-line example is Windows/PowerShell-specific, and there is no mention of cross-platform tools or commands.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS as well as Windows.
  • When showing command-line examples, provide both PowerShell and sfctl (or REST API) usage, or at least mention the cross-platform alternatives.
  • Explicitly state which tools/commands are Windows-only and which are available cross-platform.
  • Consider showing Linux/macOS commands first or side-by-side with Windows examples to promote parity.
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 ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides detailed PowerShell examples for managing node tags and service requirements, but does not offer equivalent CLI or script examples for Linux/macOS users. PowerShell is featured first and exclusively as the command-line interface, with no mention of Service Fabric CLI (sfctl) or REST API usage from non-Windows platforms. This creates friction for Linux/macOS administrators who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and commonly used on Linux/macOS.
  • Include REST API example commands (e.g., using curl) for adding/removing node tags and updating service requirements.
  • Clarify which tools are available on which platforms, and provide guidance for Linux/macOS users on how to perform these tasks.
  • Consider reordering examples so that cross-platform tools (sfctl, REST API) are presented before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific instructions. There are no examples or guidance for Linux-based standalone clusters, nor are Linux tools or commands mentioned. This creates friction for users deploying Service Fabric on non-Windows environments.
Recommendations
  • Add equivalent Linux instructions and examples for scaling standalone clusters, including relevant shell commands and configuration steps.
  • Reference cross-platform tools or clarify if only Windows is supported for standalone clusters.
  • Explicitly state platform limitations if standalone clusters are Windows-only, or provide parity where Linux is supported.
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
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters in a generally platform-neutral manner, but several sections and references show a mild Windows bias. PowerShell and Azure CLI are mentioned as command-line options, but PowerShell is listed first. The only OS patching guidance linked is for Windows clusters, and the Patch Orchestration Application (POA) is described as a Windows patching solution, with no mention of Linux equivalents or guidance. References to NTLM settings and FileStoreService are Windows-centric, and there is no explicit Linux example or mention of Linux-specific upgrade considerations.
Recommendations
  • Include explicit Linux upgrade guidance or links for Service Fabric clusters running on Linux nodes, especially for OS patching and cluster management.
  • When mentioning PowerShell/Azure CLI, clarify which commands are cross-platform and provide bash examples where relevant.
  • Add references or links to Linux-specific Service Fabric documentation, such as patching, certificate management, and node configuration.
  • If certain features (like POA) are Windows-only, clarify this and provide Linux alternatives or state the limitations.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides configuration examples using XML, JSON, PowerShell, and C# APIs. PowerShell is featured prominently as the only CLI example for dynamic configuration, with no equivalent Linux/macOS CLI (e.g., Azure CLI, REST API, or cross-platform Service Fabric CLI) examples. PowerShell examples are shown before C# API examples, and there is no mention of Linux tools or workflows for managing service sensitivity, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Add equivalent examples using cross-platform tools such as Azure CLI, Service Fabric CLI (sfctl), or REST API for setting service sensitivity and maximum load.
  • Clarify whether PowerShell examples are required for all environments, or if Linux/macOS users should use alternative tools.
  • Reorder examples so that cross-platform methods (e.g., CLI, REST) are presented before or alongside PowerShell.
  • Explicitly mention Linux/macOS management options if available, or provide guidance for non-Windows users.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for upgrading an Azure Service Fabric standalone cluster exhibits a moderate Windows bias. References and links to upgrade instructions and configuration changes point specifically to Windows Server documentation (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md'). The patch orchestration application is described only for Windows, with no mention of Linux equivalents or instructions. There are no explicit Linux examples or guidance, and Windows terminology/tools are referenced exclusively.
Recommendations
  • Add equivalent documentation and examples for Linux-based Service Fabric standalone clusters, if supported.
  • Clarify in the introduction whether Linux standalone clusters are supported and, if not, explicitly state this to avoid confusion.
  • Where possible, provide links to Linux-specific upgrade/configuration instructions or note any feature gaps.
  • Include examples of configuration files, upgrade steps, and patch orchestration for Linux clusters if applicable.
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 several Windows-centric biases. All command-line deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI equivalents. The application packaging workflow is described using Visual Studio, a Windows-focused IDE, and screenshots show Windows file paths and UI. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion steps alongside PowerShell examples.
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK on Linux/macOS) and mention alternatives to Visual Studio.
  • Provide screenshots or descriptions for Linux/macOS workflows (e.g., file system paths, terminal commands).
  • Clearly indicate which steps are platform-agnostic and which require Windows-specific tooling, and suggest alternatives where possible.
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_tools ⚠️ missing_linux_example
Summary
The documentation provides code examples for scaling Service Fabric services using C# and PowerShell, but omits equivalent Linux CLI (sfctl) or bash examples. PowerShell is a Windows-centric tool, and its exclusive use in examples and references creates friction for Linux users. The documentation also references administrative actions using PowerShell cmdlets before mentioning programmatic APIs, and does not provide Linux-specific guidance or parity in operational instructions.
Recommendations
  • Add equivalent Linux CLI (sfctl) or bash examples alongside PowerShell examples for all administrative tasks.
  • Explicitly mention Linux tooling (sfctl, REST API) in sections discussing service creation, updates, and management.
  • Clarify which tools are cross-platform and which are Windows-only, and provide links or guidance for Linux users.
  • Consider reordering examples so that platform-neutral or Linux examples are presented alongside or before Windows/PowerShell examples.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files on Azure Service Fabric. However, PowerShell examples are presented first, with more detailed command breakdowns, and PowerShell is a Windows-centric tool. There are no explicit Linux shell (e.g., Bash) or macOS Terminal examples, nor is there mention of Linux-specific patterns or tools. The CLI (sfctl) is cross-platform, but its usage is described after PowerShell and with less detail.
Recommendations
  • Present CLI (sfctl) examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Explicitly mention that sfctl works on Linux/macOS and provide example commands in a Linux shell context (e.g., Bash).
  • Clarify any platform requirements for PowerShell commands and recommend CLI usage for non-Windows users.
  • Add a brief section or note for Linux/macOS users, highlighting installation and usage of sfctl.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page provides a broad overview of Azure Service Fabric, covering both Windows and Linux support. However, there is a noticeable Windows bias in several areas: Windows terminology and executables (e.g., FabricHost.exe) are described first and in detail, with Linux equivalents only mentioned later or not at all. PowerShell is frequently referenced as a primary management tool, with CLI and REST APIs listed after. Standalone cluster creation is described only for Windows, with Linux standalone clusters explicitly noted as unsupported. Examples and instructions tend to use Windows-centric tools and patterns, and Linux-specific workflows or examples are generally missing or referenced second.
Recommendations
  • Provide equal prominence to Linux workflows and tools, especially in sections describing cluster nodes, management, and health monitoring.
  • Include Linux-specific examples and instructions where possible, such as using Linux CLI tools, shell commands, and Linux service management patterns.
  • Clarify when features or instructions are Windows-only, and offer Linux alternatives or workarounds if available.
  • In lists of management tools (PowerShell, CLI, REST), present CLI and REST APIs before or alongside PowerShell to avoid implying PowerShell is the primary or preferred method.
  • Add links or references to Linux-focused documentation or quickstarts where available.
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 ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric Events demonstrates a Windows bias by primarily referencing Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent. There are no explicit examples or instructions for accessing Service Fabric events on Linux clusters, nor are Linux-native tools or patterns mentioned. The documentation assumes the use of Windows-based monitoring and diagnostics tools, which may create friction for Linux users.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms and monitoring tools.
  • Mention Linux equivalents to ETW/Windows Event logs, such as syslog, journald, or other Linux-native logging solutions.
  • Clarify whether the Azure diagnostics agent and event logging features are available and supported on Linux clusters, and provide configuration instructions if so.
  • Include Linux-specific examples or note any limitations for Linux users.
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 only PowerShell examples for reporting and evaluating Service Fabric health, with no equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST). The use of PowerShell is presented as the default, and Windows-centric tooling appears first and exclusively in the example section, creating friction for users on non-Windows platforms.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or REST API for health reporting and querying, which are cross-platform.
  • Explicitly mention and link to Linux/macOS-compatible tools and workflows for Service Fabric health operations.
  • Reorder or balance example sections so that Windows and Linux approaches are presented with equal prominence.
  • Clarify in the example section that PowerShell is one option, and provide guidance for users on other platforms.
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 demonstrates a moderate Windows bias. PowerShell and Visual Studio (Windows-centric tools) are mentioned first and in greater detail, with explicit references to PowerShell cmdlets and scripts. While sfctl (cross-platform CLI) is mentioned, there are no concrete Linux/macOS shell examples, and the workflow descriptions focus on Windows tools and patterns. There is no clear parity in examples or guidance for Linux/macOS users, especially regarding parameter file usage and deployment scripts.
Recommendations
  • Add explicit Linux/macOS shell examples for application creation and parameter passing using sfctl and bash scripts.
  • Clarify how parameter files are used in non-Visual Studio workflows, such as with CLI or CI/CD pipelines on Linux.
  • Reorder examples so that cross-platform tools (sfctl) are presented before or alongside Windows-specific tools (PowerShell, Visual Studio).
  • Provide links or references to Linux/macOS-specific guidance for Service Fabric deployments.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page on the Azure Service Fabric hosting model demonstrates a moderate Windows bias. PowerShell is the only CLI example shown for service creation, and PowerShell-based management links are referenced throughout. There are no Linux CLI (e.g., Bash, Azure CLI) or cross-platform examples, nor is there mention of Linux-specific tooling or patterns. This creates friction for Linux/macOS users, who must infer or research equivalent commands and workflows.
Recommendations
  • Add Azure CLI examples for service creation and management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention Linux support for Service Fabric and provide guidance or links for Linux users.
  • Reference REST API usage with curl or similar tools for Linux users, not just .NET and PowerShell.
  • Clarify any platform-specific limitations or differences in hosting model configuration and management.
  • Ensure that management operations (e.g., querying, health reporting, restarting code packages) are documented with both PowerShell and Azure CLI/REST API examples.
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 frequently references PowerShell and Visual Studio for deployment and configuration tasks, both of which are traditionally Windows-centric tools. Examples and next steps focus on PowerShell usage, with no mention of Linux/macOS equivalents (such as Azure CLI, Bash, or cross-platform SDKs). There is no guidance for Linux/macOS users on how to retrieve or set the ImageStoreConnectionString, nor are alternative workflows or tools suggested.
Recommendations
  • Add examples using Azure CLI, Bash, or cross-platform SDKs for retrieving and setting the ImageStoreConnectionString.
  • Include instructions for deploying and managing Service Fabric clusters from Linux/macOS environments.
  • Reference cross-platform tools and workflows alongside PowerShell and Visual Studio, ensuring parity in documentation.
  • Clarify which steps or tools are Windows-only and provide alternatives for non-Windows users where possible.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page for Service Fabric Reliable Services app manifest examples shows moderate Windows bias. It references Windows concepts (NetworkService, Administrators group, .bat scripts), uses Windows-style executable names (VotingWeb.exe, Setup.bat), and mentions ServiceFabric PowerShell module for service creation. There are no explicit Linux/macOS equivalents or examples, and Windows terminology appears first and exclusively in several places.
Recommendations
  • Add Linux/macOS-specific examples, such as using shell scripts (.sh) in SetupEntryPoint and EntryPoint, and clarify how to specify these in manifests.
  • Document Linux/macOS equivalents for user/group principals (e.g., mapping to Unix users/groups), and clarify differences in account types.
  • Mention cross-platform deployment patterns and tools (e.g., Service Fabric CLI, sfctl) alongside PowerShell.
  • Note any platform-specific constraints or behaviors for manifest elements (e.g., RunAsPolicy, resource governance) on Linux clusters.
  • Where Windows concepts are referenced (e.g., NetworkService, Administrators), provide Linux analogs or clarify platform applicability.
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 notable 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 exclusively or before Linux equivalents. There is no mention of Linux container samples, Linux path conventions, or Linux-specific instructions, and the manifest examples do not show Linux container scenarios or cross-platform considerations.
Recommendations
  • Include Linux-based container sample manifests and link to a Linux sample repository if available.
  • Provide Linux path examples (e.g., '/mnt/VolumeTest/Data') alongside Windows paths in volume binding sections.
  • Mention Linux commands for OS build/version detection (e.g., 'cat /etc/os-release' or 'uname -r') where 'winver' is referenced.
  • Clarify which manifest features or settings are cross-platform and which are Windows-only.
  • Add notes or examples for certificate handling on Linux (e.g., PEM file usage) and highlight differences in environment variable exposure.
  • Ensure parity in instructions for deploying and managing Service Fabric containers on Linux clusters.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation covers both Windows-only (HTTP.sys) and cross-platform (Kestrel) hosting options for ASP.NET Core in Azure Service Fabric. However, it provides more detailed examples and configuration steps for HTTP.sys (Windows-only) before Kestrel, and does not explicitly show Linux/macOS-specific configuration, troubleshooting, or deployment steps. Windows tools and APIs (e.g., netsh, Windows HTTP Server API) are referenced without Linux equivalents, and there is no mention of Linux/macOS-specific considerations for Service Fabric clusters or ASP.NET Core hosting.
Recommendations
  • Add explicit Linux/macOS deployment and configuration examples for Service Fabric clusters running ASP.NET Core services with Kestrel.
  • Include troubleshooting tips or notes for common Linux/macOS issues (e.g., firewall configuration, permissions, directory paths).
  • Clarify in relevant sections that HTTP.sys is Windows-only and provide alternative guidance for Linux/macOS users (e.g., always use Kestrel).
  • Where Windows tools (like netsh) are mentioned, note that these steps are not required or applicable on Linux/macOS.
  • Consider reordering sections so that cross-platform (Kestrel) guidance appears before Windows-only (HTTP.sys) guidance.
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 for Replica soft delete in Service Fabric presents all command-line/API examples using PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica), which are Windows-centric tools. There is no mention of Linux equivalents, cross-platform CLI usage, or REST API alternatives. The documentation assumes use of Windows tooling and does not provide guidance for Linux/macOS users, even though Service Fabric supports Linux clusters.
Recommendations
  • Include examples using Service Fabric CLI (sfctl), which is cross-platform and commonly used on Linux/macOS.
  • Mention REST API endpoints or FabricClient SDK usage for replica management, clarifying how Linux users can perform equivalent operations.
  • Add a section or note specifying how Linux cluster administrators can query, remove, and restore replicas using non-Windows tools.
  • Clarify whether the PowerShell cmdlets are available or supported on Linux, or provide alternatives if not.
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 provides detailed PowerShell examples for health reporting and cluster connection, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or cross-platform scripts). PowerShell is featured prominently and exclusively in example commands, and Windows-style paths (e.g., PS C:\>) are used. REST and API methods are mentioned, but practical command-line usage for Linux environments is not demonstrated.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for health reporting and cluster connection, suitable for Linux/macOS users.
  • Clarify whether PowerShell examples are usable on Linux (via PowerShell Core), and provide guidance for Linux users if so.
  • Include cross-platform instructions for installing and using Service Fabric command-line tools on Linux/macOS.
  • Show REST API usage with curl or similar tools, including sample requests and authentication guidance for Linux environments.
  • Avoid using Windows-style paths and prompts exclusively; use generic or platform-neutral prompts where possible.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page primarily uses Windows/PowerShell tooling for deployment examples (e.g., New-ServiceFabricApplication), references Windows file paths for schema locations, and generally presents Windows-specific details before Linux equivalents. Linux-specific instructions are minimal and only briefly mentioned (e.g., certificate store path).
Recommendations
  • Provide equivalent Linux CLI examples (e.g., using sfctl or Azure CLI) alongside PowerShell commands for deploying applications and passing parameters.
  • Mention Linux file paths and configuration locations wherever Windows paths are referenced (e.g., for schema files).
  • Explicitly state any differences or additional steps required for Linux clusters, especially regarding endpoint/certificate management and deployment.
  • Ensure Linux examples are presented with equal prominence, not only as afterthoughts or notes.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page generally presents Service Fabric concepts in a cross-platform manner, noting support for both Windows and Linux. However, there are subtle signs of Windows bias: Windows-specific tools and processes (such as auto-start Windows services and EXE/DLL terminology) are described first and in detail, while Linux equivalents are not explicitly mentioned or explained. For example, the node description focuses on Windows services and executables, and the code package section refers to EXE/DLL files, which are Windows-centric. Linux-specific process/service management is not discussed, and Linux file types or patterns are not illustrated.
Recommendations
  • Explicitly mention Linux equivalents when describing node startup and service management (e.g., systemd services, ELF binaries).
  • Provide examples or notes for Linux file types and process management alongside Windows EXE/DLL references.
  • Clarify that Service Fabric supports both Windows and Linux nodes, and highlight any differences in terminology or tooling where relevant.
  • Where Windows-specific terms are used, add Linux-specific terminology or examples for parity.
GitHub Create Pull Request
Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.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 intended for both Linux and Windows VM images, but there is a notable Windows bias in several areas. PowerShell examples are given equal or greater prominence than Azure CLI, and in some cases, only PowerShell is referenced for certain tasks (e.g., sharing images across tenants). Windows/PowerShell links and terminology often appear first or exclusively, while Linux/Bash equivalents are less emphasized or missing. Some references and examples (such as uploading VHDs) do link to both Windows and Linux guides, but overall, Windows tooling and patterns are more visible.
Recommendations
  • Ensure that every PowerShell example is paired with an Azure CLI (Bash) example, especially for sharing and management tasks.
  • When referencing external guides or examples, always provide both Windows and Linux links side-by-side.
  • In lists or tables, alternate or randomize the order of Windows and Linux references to avoid always listing Windows first.
  • Expand troubleshooting and FAQ sections to explicitly mention Linux/Bash commands and common issues.
  • Review all cross-references to ensure Linux parity in linked documentation.
GitHub Create Pull Request
Virtual Machines Create a VM from a generalized image in a gallery ...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from generalized images in an Azure Compute Gallery. However, the PowerShell examples are exclusively for Windows, with all VM creation commands using Set-AzVMOperatingSystem -Windows and prompting for Windows credentials. There are no PowerShell examples for Linux VM creation, nor is there guidance for using PowerShell to deploy Linux VMs. In contrast, the CLI examples default to Linux VM creation with SSH keys, but do mention how to adapt for Windows. The PowerShell sections are Windows-centric and do not offer Linux parity.
Recommendations
  • Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and appropriate credential handling.
  • Include a note in PowerShell sections explaining how to adapt the examples for Linux VMs.
  • Ensure both CLI and PowerShell sections provide parity in Linux and Windows VM creation instructions.
  • Consider showing Linux examples first or side-by-side with Windows examples in PowerShell sections.
GitHub Create Pull Request
Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-specialized-image-version.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 Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell examples are significantly more detailed and complex, including full network setup and VM configuration, while CLI examples are much simpler. PowerShell is a Windows-centric tool, and the lack of parity in example depth may disadvantage Linux/macOS users. Additionally, PowerShell examples are presented before CLI in some sections, and there are no Bash or Linux-native scripting examples for advanced scenarios.
Recommendations
  • Provide equally detailed Bash/Azure CLI examples for advanced VM creation steps, including network setup and configuration, matching the PowerShell depth.
  • Clarify that PowerShell examples are primarily for Windows users, and recommend CLI/Bash for Linux/macOS users.
  • Ensure that CLI examples are presented before PowerShell, or at least in parallel, to avoid Windows-first perception.
  • Consider adding a section or tab for Bash scripts or Linux-native automation for users who do not use PowerShell.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric container image management shows a mild Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned as defaults in cleanup exclusions, and Windows images are referenced before Linux equivalents. There are no explicit Linux container image examples (e.g., Ubuntu, Alpine) or notes about Linux-specific considerations, despite Service Fabric supporting both Windows and Linux containers.
Recommendations
  • Include Linux container image examples (e.g., docker.io/library/ubuntu, docker.io/library/alpine) alongside Windows examples in the 'ContainerImagesToSkip' setting.
  • Clarify that Service Fabric supports both Windows and Linux containers, and note any differences in image management between platforms if applicable.
  • Add a section or note about Linux container base images and typical cleanup scenarios for Linux clusters.
  • Ensure examples and defaults do not imply Windows is the primary or only supported platform unless the feature is Windows-only.
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, but there is a slight Windows-first bias in some sections. Windows container runtimes and scenarios (such as IIS lift-and-shift) are described in more detail and mentioned before Linux equivalents. Windows-specific tools (Mirantis Container Runtime, DockerEE) are listed, while Linux only mentions Docker. Some examples and links prioritize Windows scenarios, though Linux quickstarts and tutorials are also present.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail.
  • List Linux container runtimes and tools with the same specificity as Windows (e.g., mention containerd, Podman if supported).
  • Provide Linux-specific scenarios (e.g., Apache/Nginx lift-and-shift, common Linux workloads) alongside Windows/IIS examples.
  • Alternate the order of Linux and Windows examples/links to avoid implicit prioritization.
  • Expand on Linux container orchestration and integration details, matching the depth given to Windows scenarios.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation is generally cross-platform and does not exhibit strong Windows bias in its main content. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned before any Linux/macOS equivalents, which may subtly prioritize Windows workflows.
Recommendations
  • In the 'Next steps' section, add or highlight Linux/macOS-compatible upgrade workflows, such as using Azure CLI, Service Fabric CLI (sfctl), or other cross-platform tools.
  • Ensure that upgrade tutorials for Linux/macOS are linked alongside or before Windows-specific ones.
  • Consider explicitly stating that Service Fabric Reliable Collections and serialization features are available and supported on both Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows file paths (e.g., installation of schema files in 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd') and mentioning Visual Studio as a primary packaging tool. There are no explicit Linux/macOS command-line examples or references to Linux tooling, and the directory structure examples use Windows-style naming conventions. However, the content does not appear to be exclusively Windows-focused, and Service Fabric itself supports guest executables of various types (Node.js, Java, C++), which are cross-platform.
Recommendations
  • Include Linux/macOS equivalents for SDK installation paths and clarify where schema files are located on non-Windows systems.
  • Provide examples or references for packaging and deploying guest executables using Linux/macOS command-line tools.
  • Mention cross-platform editors or IDEs (such as VS Code) alongside Visual Studio.
  • Show directory structures using platform-neutral notation or include both Windows and Linux/macOS examples.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ minor_windows_tools
Summary
The documentation generally presents Service Fabric as a cross-platform solution, mentioning both Windows and Linux support. However, there is a subtle Windows bias: Windows development is described first, with emphasis on Visual Studio and PowerShell integration, while Linux development is mentioned second, with Eclipse and Yeoman. The quickstart link points to a .NET/Windows-centric guide. There are no Linux-specific examples or walkthroughs on this overview page, and Windows tools (Visual Studio, PowerShell) are referenced before Linux equivalents.
Recommendations
  • Present Windows and Linux development options in parallel, rather than listing Windows first.
  • Include links to both Windows and Linux quickstart guides in the 'Next steps' section.
  • Add explicit mention of Linux CLI tools (e.g., Bash, CLI commands) alongside PowerShell.
  • Reference Linux SDKs and development environments with equal prominence as Windows tools.
  • Where possible, provide cross-platform examples or clarify when instructions differ by OS.
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides Azure portal, Azure CLI, and Azure PowerShell instructions for attaching and detaching VMs to/from scale sets. In each case, Azure PowerShell examples are given equal prominence to Azure CLI, and PowerShell is a Windows-centric tool. The CLI examples use Ubuntu images, showing Linux is supported, but PowerShell is always listed as a primary method, and examples are not explicitly labeled as Windows-only. The troubleshooting section links to some Windows-specific docs (e.g., converting unmanaged disks, proximity placement groups) without Linux equivalents or clarifying applicability.
Recommendations
  • Clearly label Azure PowerShell examples as Windows-only, and note that PowerShell is primarily for Windows users.
  • Provide Bash or shell script equivalents for Linux/macOS users where PowerShell is shown.
  • Ensure troubleshooting links and migration steps reference both Windows and Linux documentation where applicable (e.g., disk migration, proximity placement group removal).
  • Consider listing Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Add a brief note at the top clarifying that Azure CLI is recommended for Linux/macOS users, while PowerShell is for Windows.
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 PowerShell examples for creating and updating scale sets with Availability Zones, but PowerShell examples are given equal prominence to CLI, and are shown before REST/ARM template examples. While CLI is cross-platform, PowerShell is primarily a Windows tool (though available on Linux/macOS, it's less commonly used there). The documentation does not provide any Linux/macOS-specific shell examples (e.g., Bash), nor does it clarify CLI usage on Linux/macOS. The ARM template section does link to both Linux and Windows quickstart articles, but in the main walkthrough, Windows-centric tooling (PowerShell) is featured as a primary method.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS as well as Windows.
  • Consider providing Bash shell examples for Linux/macOS users, especially for common operations like az vmss create.
  • If PowerShell is shown, clarify its cross-platform availability, but note that CLI is the recommended tool for Linux/macOS.
  • Ensure that Linux/macOS users are not left to infer that PowerShell is required.
  • In the 'Use Azure Resource Manager templates' section, clarify parity between Linux and Windows deployments, and ensure links to both quickstart guides are equally visible.
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
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides examples and references for both Windows and Linux scenarios, but Windows-specific tasks (such as VM activation and Windows updates) are mentioned before Linux equivalents, and there are no explicit Linux/PowerShell/Bash command examples or Linux migration patterns shown. The CLI example is generic, but the narrative and troubleshooting links prioritize Windows use cases.
Recommendations
  • Include explicit Linux migration considerations and examples, such as package manager connectivity requirements (apt/yum) and troubleshooting steps for Linux VMs.
  • Provide CLI or script examples for Linux environments (e.g., Bash, cloud-init) alongside PowerShell or generic Azure CLI examples.
  • Balance the order of mention between Windows and Linux scenarios (e.g., discuss Linux package manager connectivity before or alongside Windows activation and updates).
  • Reference Linux-specific documentation for troubleshooting and best practices where relevant.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides example commands for Azure CLI, PowerShell, Portal, and ARM templates. While Azure CLI is cross-platform, PowerShell examples are given equal prominence and detail, and are presented immediately after CLI in each section. There is a slight Windows-first bias in the ordering and inclusion of PowerShell examples, which are primarily relevant to Windows users. However, all critical tasks (configuring, monitoring, canceling, and restarting rolling upgrades) can be completed using the cross-platform Azure CLI, and no functionality is locked to Windows/PowerShell tools.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider listing CLI examples before PowerShell in each section to reinforce Linux parity.
  • Add a short note in each PowerShell section clarifying that PowerShell Core is available on Linux/macOS, or link to installation instructions for PowerShell on non-Windows platforms.
  • Where possible, clarify that all operations can be performed via CLI, and PowerShell is an alternative for those who prefer it.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for most networking tasks with Azure Virtual Machine Scale Sets, but PowerShell (Windows-centric) examples are often presented before CLI (cross-platform) equivalents. In some sections, only PowerShell is shown for querying resources, with CLI examples provided separately or later. There is a slight tendency to mention Windows tools or patterns first, and some examples (such as querying public IPs) are more detailed for PowerShell than CLI. No Linux-specific shell examples (e.g., bash scripts) are given, and the documentation does not reference Linux-native tools or patterns outside of Azure CLI.
Recommendations
  • Present Azure CLI (cross-platform) examples before or alongside PowerShell examples to avoid Windows-first bias.
  • Ensure all PowerShell examples have equivalent Azure CLI examples, especially for querying and managing resources.
  • Add explicit notes or examples for Linux/macOS users where CLI usage may differ (e.g., environment variables, shell syntax).
  • Consider including bash script snippets or references to Linux-native tools where relevant.
  • Clarify that Azure CLI is the recommended tool for cross-platform scenarios.
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 response, and covers Azure CLI, PowerShell, and REST API for extension installation and querying. However, in several places, Windows/PowerShell examples are presented before Linux/Bash equivalents, and PowerShell scripts are detailed and prominent. The extension installation section lists PowerShell after CLI, but the PowerShell example is more verbose and detailed. The extension type examples use both ApplicationHealthLinux and ApplicationHealthWindows, but the REST API and PowerShell samples default to Windows extension types. There is a slight preference for Windows tools and ordering, but Linux parity is generally maintained.
Recommendations
  • Ensure that Linux examples (Bash, Python) are presented before or alongside Windows/PowerShell examples, especially in sections where ordering implies priority.
  • In REST API examples, alternate between ApplicationHealthLinux and ApplicationHealthWindows for extension type, or explicitly show both.
  • Clarify in introductory sections that all examples are available for both Linux and Windows VMSS instances.
  • Where possible, balance the detail level between Bash and PowerShell scripts, so Linux users have equally comprehensive guidance.
  • Consider adding a table or note summarizing OS-specific extension types and usage patterns for clarity.
GitHub Create Pull Request
Virtual Machines Deprovision or generalize a VM before creating an image ...docs/blob/main/articles/virtual-machines/generalize.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 clear, detailed instructions for both Linux and Windows VM generalization, but the Windows section includes more prerequisites, registry edits, and PowerShell-specific commands. The Windows example for marking the VM as generalized uses Azure PowerShell, while the Linux example uses Azure CLI. The Windows section appears after the Linux section, but the Windows-specific tooling (Sysprep, registry, PowerShell) is emphasized without mentioning Linux equivalents or cross-platform alternatives for some steps.
Recommendations
  • Ensure parity in tooling: For marking a VM as generalized, provide both Azure CLI and Azure PowerShell examples for both Linux and Windows VMs.
  • Clarify cross-platform options: Where Windows uses PowerShell, note that Azure CLI can be used on Windows as well, and show CLI syntax.
  • Balance prerequisites: If possible, add more detail to Linux prerequisites, such as common pitfalls or distro-specific notes, to match the depth of the Windows section.
  • Order examples consistently: Consider alternating the order of Linux and Windows examples or grouping cross-platform steps together.
  • Reference cross-platform documentation: Link to Azure CLI and PowerShell docs for both OSes in the 'Related content' section.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation page is focused on Linux VM time sync in Azure and provides Linux-specific guidance and examples. However, the introduction and overview sections discuss Windows Server 2016 time sync improvements and Windows infrastructure before describing Linux mechanisms. All technical instructions, examples, and tools are Linux-centric, with no PowerShell or Windows-only commands given for time sync configuration. The only Windows-related content is background context and links to Windows documentation, which may be unnecessary for Linux users.
Recommendations
  • Move Windows Server 2016 time sync background to a separate 'Azure infrastructure' or 'Background' section, or condense it to a brief note if relevant.
  • Begin the page with Linux-specific time sync context and configuration options, reserving Windows infrastructure details for later or as a sidebar.
  • Clarify that Windows documentation links are for background only and not required for Linux VM configuration.
  • Ensure all examples and instructions remain Linux-focused, as currently provided.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation is focused on Linux, as indicated by the title and content. However, in several sections, Windows-oriented tools and patterns (notably Azure PowerShell) are presented before Linux-native equivalents (Azure CLI). PowerShell deployment instructions and troubleshooting commands are shown first, even though Linux users are more likely to use Azure CLI. There are also warnings about PowerShell-specific issues, which may not be relevant for most Linux users. All configuration and operational details are Linux-centric, and no critical functionality is missing for Linux users.
Recommendations
  • Present Azure CLI examples before PowerShell examples in all deployment and troubleshooting sections.
  • Clearly mark PowerShell instructions as primarily for Windows users, and Azure CLI for Linux/macOS users.
  • Add a short note at the start of deployment sections indicating that Azure CLI is recommended for Linux users.
  • Move PowerShell-specific warnings to a dedicated troubleshooting subsection for Windows users.
  • Review all example ordering to ensure Linux-first presentation.
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 in several sections, Windows/PowerShell examples and terminology are presented before Linux equivalents. The PowerShell tab examples default to Windows, while the CLI tab defaults to Linux. There is a slight tendency to mention Windows/PowerShell first or more prominently, but Linux parity is generally maintained through CLI and REST examples.
Recommendations
  • Ensure that Linux and Windows examples are presented with equal prominence and order in all code sample tabs (e.g., alternate which OS is shown first, or provide both in parallel).
  • In PowerShell sections, explicitly show both Linux and Windows examples, or clarify that PowerShell can be used for Linux images as well.
  • Where OS-specific preparation steps are referenced, ensure links and instructions for both Linux and Windows are equally visible and accessible.
  • Review all examples to confirm that Linux users are not required to infer steps from Windows-centric instructions.
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 presents both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell example is given equal prominence despite PowerShell being primarily a Windows tool. The CLI example is shown first, which is positive, but the inclusion of PowerShell may imply a Windows-centric workflow. No Linux-specific shell examples (e.g., Bash scripting) are provided, though the CLI is cross-platform.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows equally.
  • Explicitly mention that PowerShell is primarily for Windows users, while CLI is recommended for Linux/macOS.
  • Consider adding a short Bash script example for Linux users, or a note about using CLI in Bash/zsh.
  • Reiterate cross-platform compatibility in the introduction to reduce perceived Windows bias.
GitHub Create Pull Request
Virtual Machines Deploy a Trusted Launch VM ...ain/articles/virtual-machines/trusted-launch-portal.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides examples and instructions for both Linux and Windows VMs throughout, including CLI, portal, template, and PowerShell methods. However, in several sections, Windows/PowerShell examples are presented first or in more detail, and PowerShell examples are exclusively for Windows VMs, with no Linux PowerShell equivalents. Some PowerShell snippets default to Windows images and configurations, while Linux examples are primarily shown in CLI and template sections.
Recommendations
  • Ensure parity in PowerShell examples by including Linux VM deployment snippets where possible, or clearly state PowerShell is Windows-only if that's the case.
  • Alternate the order of Windows and Linux examples so Linux is sometimes shown first, or group examples by OS for clarity.
  • In PowerShell sections, explicitly mention that Linux VMs should be deployed using CLI or ARM templates if PowerShell support is limited.
  • Add clarifying notes where a method (e.g., PowerShell) is Windows-specific, to avoid confusion for Linux users.
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
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides parity for both Linux and Windows VMs, explicitly stating applicability to both. However, there is a mild Windows bias in the ordering and tooling: PowerShell examples are included and shown before Linux-native alternatives, and some steps (such as VM deallocation in the ARM template section) use PowerShell syntax exclusively, even though Linux users would use Bash or Azure CLI. The verification step mentions RDP (Windows) before SSH (Linux) throughout. All CLI examples use Azure CLI, which is cross-platform, but PowerShell is given equal prominence, which may be less relevant for Linux/macOS users.
Recommendations
  • Where PowerShell is used for generic Azure operations (e.g., deallocating VMs), provide equivalent Azure CLI or Bash examples, especially in sections like ARM template deployment.
  • When listing verification steps, alternate or parallelize RDP/SSH references, or mention SSH first in Linux-focused contexts.
  • Consider clarifying that PowerShell examples are primarily for Windows users, and recommend Azure CLI/Bash for Linux/macOS users.
  • Ensure screenshots and UI references are not Windows-centric if possible.
GitHub Create Pull Request
Virtual Machines VM vCore Customization ...lob/main/articles/virtual-machines/vm-customization.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ minor_windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization, but PowerShell (a Windows-centric tool) is given its own section and detailed example. The CLI example uses Ubuntu as the image, showing Linux applicability, but the PowerShell section appears before ARM template automation and is presented as a primary method. There is a slight Windows-first ordering in the examples and tool references, but Linux users can fully complete the tasks using CLI, ARM templates, and the portal.
Recommendations
  • Add explicit Bash or shell scripting examples for Linux users, especially for automation scenarios.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and highlight this in the CLI section.
  • Consider reordering sections so that cross-platform tools (CLI, ARM templates) appear before Windows-specific tools (PowerShell).
  • Add a note in the PowerShell section indicating its Windows-centric nature and suggest CLI for Linux/macOS users.
GitHub Create Pull Request