← Back to Dashboard
282
Pages Scanned
94
Pages Flagged
282
Changed Pages
33.3%
% Pages Flagged

Live Progress

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

Scan Information

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

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 282

Files Completed: 282

Problematic Pages

94 issues found
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation for Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples use Windows container images (nanoserver), Windows file paths, and Windows command syntax (cmd.exe). There are no examples or guidance for Linux containers, nor is there mention of Linux-compatible patterns or tools. The ApplicationManifest and ServiceManifest examples exclusively reference Windows-specific paths and images, and the 'getting started' link is for Windows containers.
Recommendations
  • Add parallel examples for Linux containers, using Linux-compatible images (e.g., Ubuntu, Alpine) and shell commands.
  • Clarify whether Initializer CodePackages are supported for Linux containers, and if so, provide guidance and examples.
  • Mention Linux file path conventions and container volume mounts.
  • Link to Linux container documentation where relevant.
  • If Initializer CodePackages are Windows-only, state this explicitly at the top of the page.
GitHub Create Pull Request
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and guidance are implicitly Windows-focused. There are no Linux-specific instructions, examples, or parity guidance for Linux users, and the feature is unavailable on Linux clusters.
Recommendations
  • Clearly state at the top that the reverse proxy feature is Windows-only, and link to any Linux alternatives or roadmap if available.
  • Provide guidance or links for Linux users on how to achieve similar functionality, or clarify limitations and suggest workarounds.
  • If/when Linux support is added, update documentation to include Linux-specific examples, instructions, and troubleshooting.
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
⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
Although the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the documentation page is primarily focused on Windows. All operating system references, security options, and supported OS lists are Windows-only. There are no Linux-specific instructions, examples, or supported OS details. The mention of Linux in the description is misleading, as the 'Supported operating systems' section clarifies that Linux isn't yet supported for standalone clusters.
Recommendations
  • Clarify in the introduction that standalone Service Fabric clusters are currently Windows-only, and Linux support is not available.
  • Remove or revise the misleading statement in the description about Linux support.
  • If/when Linux support becomes available, add Linux-specific instructions, examples, and supported OS details.
  • Consider adding a prominent note at the top of the page to inform users about the Windows-only limitation.
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_first ⚠ī¸ windows_tools
Summary
The documentation provides extensive PowerShell examples and references Windows-specific tools and behaviors (such as Key Vault VM extension for Windows, S-channel, and certificate linking). Windows terminology and patterns are presented first and in detail, while Linux-specific guidance, examples, or parity are largely absent. The Key Vault VM extension is described as Windows-specific, and there are no Bash/CLI/Linux automation examples for certificate management or provisioning. Troubleshooting and scripting sections rely exclusively on PowerShell.
Recommendations
  • Add equivalent Bash/CLI examples for certificate enrollment, provisioning, and automation, especially for Linux-based Service Fabric clusters.
  • Clarify which features and extensions are Windows-only and provide Linux alternatives or note limitations for Linux users.
  • Include documentation or links for Linux certificate management tools (e.g., OpenSSL, Azure CLI) and how to automate certificate provisioning on Linux nodes.
  • Explicitly state any differences in certificate management workflows between Windows and Linux clusters, and provide guidance for Linux users where possible.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows-specific terminology, tools, and patterns (such as certificate store paths like 'LocalMachine\My', references to Win32 CryptoAPI, and event log locations) are mentioned first or exclusively. Troubleshooting sections focus on Windows event logs and CAPI2 logging, with little to no guidance for Linux equivalents. While Linux is referenced (e.g., '/var/lib/sfcerts'), Windows-centric examples and APIs dominate, potentially creating friction for Linux/macOS users.
Recommendations
  • Add Linux-specific examples for certificate storage, retrieval, and troubleshooting (e.g., using OpenSSL, Linux certificate stores, and relevant log locations).
  • When referencing certificate stores, mention both Windows and Linux paths equally and provide guidance for Linux users.
  • Include troubleshooting steps for Linux clusters, such as relevant log files, commands, and error codes.
  • Where Windows APIs (e.g., CertGetCertificateChain) are discussed, clarify the Linux equivalent behavior or implementation.
  • Balance examples and terminology so that Linux and Windows users can follow the documentation without ambiguity.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page primarily discusses deploying custom Windows images on Azure Service Fabric Managed Clusters. Windows terminology and examples are used throughout, and the only command-line example provided is in PowerShell. While there are references to Linux custom image creation and Azure CLI for browsing marketplace images, the main workflow and examples focus on Windows, with no Linux-specific deployment examples or shell commands.
Recommendations
  • Provide equivalent Linux shell (bash/CLI) examples for role assignment and image deployment.
  • Clarify in the introduction whether Linux node types are supported and, if so, include Linux-specific guidance.
  • Add ARM template examples and workflows for deploying Linux custom images, if supported.
  • Ensure that references to Linux documentation are accompanied by actionable steps for Linux users.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides management guidance for Service Fabric Explorer blocking operations, but consistently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) as the primary tooling for resource management. While az CLI is mentioned once for deleting applications, PowerShell examples and terminology are more prominent, and no explicit Linux/macOS command examples or guidance are given. This creates friction for non-Windows users, as PowerShell is less common on Linux/macOS and az CLI is the cross-platform standard.
Recommendations
  • Provide equivalent az CLI commands for all management operations (e.g., deleting, creating, scaling resources) alongside PowerShell examples.
  • Clarify that az CLI is fully supported on Linux/macOS and is the recommended cross-platform tool.
  • Add explicit Linux/macOS instructions or notes where appropriate, ensuring parity in examples and guidance.
  • Consider linking to az CLI documentation for Service Fabric management.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page presents RunToCompletion semantics in Service Fabric with a strong Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, set, ping), and reference Windows container compatibility. Querying deployment status is shown only via PowerShell and C# APIs, with no mention of Linux equivalents or CLI tools. There are no examples or guidance for Linux containers or Linux-based Service Fabric clusters.
Recommendations
  • Add examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
  • Provide guidance or code snippets for querying deployment status using Azure CLI or Linux-native tools.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide parity in documentation.
  • Include notes or links for Linux/macOS users on how to adapt the examples.
  • If RunToCompletion is Windows-only, explicitly state this early in the article to avoid confusion.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides examples and links primarily for Azure PowerShell modules when describing best practices for managing Service Fabric managed clusters. PowerShell is a Windows-centric tool, and its mention precedes Azure CLI and sfctl references. While Azure CLI and ARM/Bicep are also mentioned, the explicit examples and guidance focus on PowerShell, which may create friction for Linux/macOS users.
Recommendations
  • Provide explicit Azure CLI examples alongside PowerShell examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Clarify that Azure CLI and sfctl are cross-platform and suitable alternatives to PowerShell.
  • Reorder tool mentions so that cross-platform tools (Azure CLI, ARM templates, Bicep) are listed before PowerShell.
  • Add sample commands for sfctl where relevant, especially for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides extensive PowerShell-based migration steps and examples, especially in the section for migrating Service Fabric nonmanaged clusters with Basic SKU load balancer and IP resources. All command-line instructions use PowerShell cmdlets (e.g., New-AzureRmResourceGroupDeployment, Connect-ServiceFabricCluster, Disable-ServiceFabricNode), which are Windows-centric and do not offer equivalent Bash/Azure CLI examples. Additionally, the sample template for Linux (Ubuntu) is referenced, but the migration steps and tooling remain Windows/PowerShell-focused. The documentation also uses Windows file paths (e.g., 'D:\\SvcFab') in configuration examples, further reinforcing Windows bias.
Recommendations
  • Provide Azure CLI or Bash equivalents for all PowerShell migration steps, especially for disabling/removing nodes and updating resources.
  • Clarify which steps can be performed on Linux/macOS and which require Windows, and offer guidance for cross-platform users.
  • Include Linux file path examples (e.g., '/var/svcfab') alongside Windows paths in configuration snippets.
  • Reference and link to Linux/macOS tooling or scripts where available.
  • Ensure sample templates and walkthroughs for Linux clusters include migration instructions using cross-platform tools.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation contains evidence of Windows bias. The only tooling example for validating manifest XML schema is Visual Studio on Windows, referencing a Windows file path. There is a mention of using the ServiceFabric PowerShell module to create service instances, but no equivalent Linux CLI example is provided. Windows tools and patterns (Visual Studio, PowerShell) are mentioned exclusively or before any Linux alternatives, and no Linux/macOS-specific guidance or parity is offered.
Recommendations
  • Add instructions for validating manifest XML schema using cross-platform tools (e.g., VS Code, xmllint, or other XML editors available on Linux/macOS).
  • Provide examples for creating service instances using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform, alongside or instead of PowerShell.
  • Reference file paths and tooling in a platform-neutral way, or provide Linux/macOS equivalents where possible.
  • Explicitly note any Windows-only steps and offer Linux/macOS alternatives or workarounds.
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 'Application lifecycle in Service Fabric' repeatedly references PowerShell cmdlets and Windows-centric tooling (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType, Remove-ServiceFabricApplicationPackage) alongside .NET APIs and REST operations. PowerShell examples are given for automation and cleanup, with no equivalent Linux shell or cross-platform CLI (sfctl/Azure CLI) examples. Windows tools and cmdlets are often mentioned first or exclusively, creating friction for Linux/macOS users.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform, for each lifecycle operation (deploy, upgrade, remove, cleanup).
  • Where PowerShell cmdlets are referenced, also provide equivalent sfctl or Azure CLI commands.
  • Ensure REST API references are accompanied by practical usage examples (e.g., curl commands) for Linux/macOS users.
  • Clarify which operations can be performed using cross-platform tools and which are Windows-only.
  • Consider including bash or shell script snippets for automation tasks, especially in sections currently showing only PowerShell.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides a general overview of Service Fabric application security, but several sections show Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned with more detail or appear first, while Linux equivalents are missing or only briefly referenced. Some examples and links are Windows-centric, and Linux guidance is often absent or relegated to TODO comments.
Recommendations
  • Add explicit Linux examples and guidance for securing Service Fabric applications, including container certificate access and disk encryption.
  • Ensure parity in documentation for running services under Linux user accounts, including relevant manifest examples.
  • Provide links to Linux-specific tools and patterns (e.g., disk encryption with dm-crypt/LUKS, Linux container security best practices).
  • Where Windows tools are mentioned (e.g., BitLocker, gMSA), add or reference Linux alternatives or clarify platform limitations.
  • Remove or resolve TODO comments regarding Linux disk encryption and provide actionable guidance.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides extensive PowerShell-based examples and references, with no mention of Linux/macOS equivalents (such as Azure CLI or REST API usage). All command-line upgrade instructions and parameter modifications are shown using Windows PowerShell cmdlets, and the PowerShell approach is presented as the default throughout. There are no Linux/macOS-specific instructions or examples, and the use of PowerShell is assumed for all users.
Recommendations
  • Add Azure CLI examples for all upgrade operations (e.g., creating/updating services, starting upgrades, rolling back upgrades, updating parameters).
  • Include REST API sample calls for relevant operations, especially for users on Linux/macOS or those automating upgrades.
  • Clearly indicate which operations are possible via CLI or REST, and provide links to relevant cross-platform documentation.
  • Where PowerShell is referenced, add a note about cross-platform alternatives and their usage.
  • Ensure that ARM template examples are accompanied by CLI/REST deployment instructions for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and examples before Linux equivalents (SFCTL). The PowerShell and Visual Studio sections are detailed and appear first, while Linux tooling (SFCTL) is covered later and with less example depth. There are no explicit Linux CLI examples or parameter tables shown first, and the PowerShell-centric approach may create friction for Linux/macOS users.
Recommendations
  • Reorganize the documentation to present SFCTL (Service Fabric CLI) parameters and examples alongside or before PowerShell/Visual Studio, especially since SFCTL is cross-platform.
  • Add explicit Linux/macOS command examples using SFCTL for common upgrade scenarios, similar to the PowerShell examples.
  • Clarify that SFCTL is the recommended cross-platform CLI for Service Fabric upgrades, and highlight its parity with PowerShell.
  • Ensure that parameter tables and descriptions for SFCTL are as detailed as those for PowerShell/Visual Studio.
  • Consider a summary table comparing PowerShell, Visual Studio, and SFCTL usage for upgrade parameters, making Linux/macOS parity clear.
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 mentions PowerShell cmdlets as primary management tools and refers to Windows security as a transport option, suggesting a Windows-centric approach. PowerShell is listed first and exclusively in the management subsystem section, with no mention of Linux-native equivalents (such as Azure CLI or REST APIs). Windows security is mentioned alongside X509 certificates, but Linux security mechanisms are not referenced. No Linux/macOS-specific examples or tools are provided.
Recommendations
  • Add examples or references to Linux/macOS management tools, such as Azure CLI or REST API usage, alongside PowerShell.
  • Clarify that Service Fabric management can be performed from Linux/macOS using cross-platform tools.
  • Mention Linux security mechanisms (e.g., SSH, certificate-based auth) where relevant, not just Windows security.
  • Ensure that tooling and API references are platform-neutral or include both Windows and Linux/macOS options.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page references Windows-centric tools and patterns, such as Visual Studio and PowerShell, in the 'Next steps' section. These are presented as primary upgrade methods, with no mention of Linux/macOS alternatives (e.g., CLI or cross-platform editors). The serialization discussion is focused on C# and .NET, which are cross-platform, but the upgrade guidance leans toward Windows workflows.
Recommendations
  • Add examples or links for upgrading applications using Azure CLI or Service Fabric CLI, which are cross-platform.
  • Mention cross-platform editors (such as VS Code) alongside Visual Studio.
  • Clarify that PowerShell examples are available for Linux/macOS, or provide Bash/CLI equivalents.
  • Explicitly note if the upgrade process is identical across platforms, or highlight any differences.
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 Windows bias through exclusive use of PowerShell examples, references to Windows-specific tools (e.g., http.sys, Windows HTTP Server API), and lack of Linux or cross-platform CLI examples. The upgrade process is illustrated only with Windows-centric commands and concepts, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Where PowerShell is used, provide alternative Bash or CLI commands for Linux users.
  • Clarify which steps or concepts are Windows-only (e.g., http.sys, Windows HTTP Server API) and provide Linux-specific guidance where possible.
  • Update 'Next steps' to include tutorials for Linux/macOS users, such as upgrading applications using sfctl or REST APIs.
  • Mention platform differences explicitly and link to Linux/macOS documentation where relevant.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for on-demand backup in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all code examples and command-line instructions using PowerShell and the Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools. The REST API is referenced, but only in the context of PowerShell usage. This creates friction for users on non-Windows platforms.
Recommendations
  • Add Bash/curl examples for REST API calls, showing how to trigger backups and track progress from Linux/macOS.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available cross-platform (via PowerShell Core), and if so, provide installation instructions for Linux/macOS.
  • Provide guidance for connecting to Service Fabric clusters and managing certificates from Linux/macOS environments.
  • Explicitly mention any limitations or differences for Linux/macOS users, if applicable.
  • Consider including sample scripts or links to Service Fabric CLI tools (if available) for non-Windows platforms.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily biased towards Windows and PowerShell usage. All CLI examples use PowerShell syntax and require the Microsoft.ServiceFabric.Powershell.Http module, which is Windows-centric. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools. The REST API is only demonstrated via PowerShell, and there is no mention of Linux-compatible Service Fabric CLI or Azure CLI alternatives.
Recommendations
  • Add equivalent examples using Bash/curl for REST API calls, making it clear how Linux/macOS users can perform the same operations.
  • Document any cross-platform Service Fabric CLI commands (sfctl) for backup and restore, if available.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST API calls can be made directly from any platform.
  • Explicitly state platform requirements and provide links to Linux/macOS-compatible tooling where possible.
  • If PowerShell Core (pwsh) is supported on Linux/macOS, mention this and provide examples for those environments.
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 Resource Manager templates, but PowerShell is featured prominently and exclusively for cluster upgrade operations. Windows-specific tools (registry keys, Windows Update configuration) are discussed in detail, while Linux equivalents are not mentioned. Windows-related configuration appears before Linux options in some sections, and Linux-specific guidance is minimal or absent for certain tasks.
Recommendations
  • Add Linux/bash examples for cluster upgrade operations (e.g., using shell scripts or relevant Linux tools instead of PowerShell).
  • Include guidance on disabling automatic updates for Linux VM scale sets (e.g., using cloud-init or OS-specific package management).
  • Provide parity for registry/configuration instructions, such as mentioning how to manage updates on Linux nodes.
  • Ensure Linux-specific links and instructions are given equal prominence and detail as Windows.
  • Where PowerShell is used, offer a bash or CLI alternative if possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux guidance for Azure Service Fabric networking, but there are several signs of Windows bias. PowerShell is referenced as the primary client API example, and Windows-specific tools and patterns (such as PowerShell tasks in Azure DevOps, Windows container networking, and Windows Update patching) are discussed in detail, often before or instead of Linux equivalents. Some examples and ARM templates are Windows-centric. Linux is mentioned, but often as a secondary consideration.
Recommendations
  • Include Linux CLI (az CLI, bash) examples alongside PowerShell for client API and cluster management tasks.
  • Provide equal coverage of Linux container networking scenarios, including best practices for Linux container workloads.
  • Add ARM template examples for Linux clusters and reference Linux-specific templates where possible.
  • Clarify when guidance is Windows-only and provide Linux alternatives or links to Linux documentation.
  • Expand DevOps and automation examples to include Linux agents and cross-platform tools, not just PowerShell.
  • Ensure application networking guidance covers Linux containers and reverse proxy usage on Linux clusters.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, covering both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: references to Windows-specific concepts (e.g., certificate store names like 'MY', 'LocalMachine', NTLM authentication, and Windows Defender Firewall) appear throughout, and Windows terminology (e.g., 'Windows Fabric', 'fabric.exe', 'ServiceFabricAdministrators') is used as the default or primary context. Some settings and descriptions reference Windows tools or patterns (such as certificate store locations and NTLM), and Windows is often mentioned first or exclusively, with Linux equivalents sometimes missing or only briefly referenced.
Recommendations
  • Where Windows-specific terms or tools are referenced (e.g., certificate store names, NTLM authentication, firewall configuration), provide equivalent Linux/macOS instructions or clarify if the feature is Windows-only.
  • Ensure Linux-specific settings (such as certificate folder paths, LinuxExternalExecutablePath) are equally documented and highlighted.
  • When describing configuration parameters, avoid defaulting to Windows terminology; instead, present both Windows and Linux options side-by-side.
  • Add explicit notes or tables indicating which settings are platform-specific, and provide links to Linux/macOS guidance where available.
  • Review sections for settings that reference Windows-only features (e.g., 'Windows Defender Firewall', 'NTLM') and clarify their applicability.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides several step-by-step instructions for scaling Service Fabric clusters that rely exclusively on PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent CLI, Bash, or REST API examples for Linux/macOS users. There are no explicit Linux command examples or guidance for users who do not have access to PowerShell, creating friction for those managing Linux-based clusters.
Recommendations
  • Add equivalent Azure CLI or REST API examples for all PowerShell-based instructions, especially for disabling/removing nodes and cleaning up node state.
  • Clearly indicate whether the PowerShell commands are required for both Windows and Linux clusters, or if there are alternative methods for Linux users.
  • Provide Bash or cross-platform script examples where possible, or reference Service Fabric CLI (sfctl) commands for Linux/macOS.
  • Add a short section or callout for Linux users, summarizing the recommended tools and commands for common scaling operations.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides code samples in C# and PowerShell only. PowerShell is a Windows-centric tool, and there are no examples for Linux/macOS users (e.g., Azure CLI, REST API, or cross-platform Service Fabric CLI). This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent Azure CLI or Service Fabric CLI (sfctl) examples for all PowerShell commands, as these are cross-platform and commonly used on Linux/macOS.
  • Clearly indicate if certain management operations are only possible via PowerShell, and provide alternative guidance or workarounds for Linux users if available.
  • Where possible, mention REST API options for configuring placement policies, as these are platform-agnostic.
  • Reorder code samples to present cross-platform options first or side-by-side with PowerShell.
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 consistently provides PowerShell examples for managing Service Fabric Application Groups, but does not offer equivalent CLI or bash examples for Linux/macOS users. All command-line instructions use PowerShell cmdlets, which are native to Windows. There is no mention of cross-platform tools (such as Azure CLI or REST API) that Linux/macOS users could use, nor are Linux-specific workflows or commands referenced.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlet instructions, as Azure CLI is cross-platform and widely used.
  • Mention REST API endpoints or provide sample REST calls for managing Application Groups, which are platform-agnostic.
  • Clarify whether PowerShell cmdlets can be used via PowerShell Core on Linux/macOS, or explicitly state if they are Windows-only.
  • Consider including bash scripts or instructions for Linux users where relevant.
  • Add a short section or note on cross-platform management options for Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI examples are PowerShell-based, with no mention of Linux/macOS equivalents such as Bash, Azure CLI, or REST API. The PowerShell examples are presented prominently, and there is no guidance for Linux users on how to perform these operations. While Service Fabric supports Linux containers, the documentation does not offer parity for Linux administration workflows.
Recommendations
  • Add Azure CLI or Bash examples for configuring scaling policies, especially for Linux-based clusters.
  • Mention REST API options for auto scaling configuration, which are cross-platform.
  • Clarify which PowerShell commands are available via Azure CLI or REST for Linux users.
  • Explicitly state any limitations or differences for Linux clusters, and provide links to Linux-specific documentation if available.
  • Consider including a table or section comparing Windows and Linux management options for Service Fabric auto scaling.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell example for querying partition health, with no equivalent Linux/macOS CLI example (e.g., Service Fabric CLI or REST API). The example uses Windows-style paths and PowerShell syntax, suggesting Windows as the default environment. There is no mention of Linux tools or cross-platform alternatives for cluster management or health queries.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Mention REST API endpoints for health queries, which are platform-agnostic.
  • Clarify that Service Fabric management can be performed from Linux/macOS and provide links or examples for those environments.
  • Avoid using Windows paths (e.g., C:\Users\User) unless necessary, or provide cross-platform alternatives.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides PowerShell examples for configuring move cost in Service Fabric, but does not include equivalent Linux CLI (e.g., Bash, Azure CLI) or cross-platform scripting examples. PowerShell is presented first, and no Linux/macOS-specific tools or commands are mentioned, which may create friction for users deploying Service Fabric clusters on Linux or managing them from non-Windows environments.
Recommendations
  • Add Azure CLI or Bash examples for creating and updating Service Fabric services with move cost settings.
  • Clarify whether PowerShell commands are supported on Linux (via PowerShell Core), or provide guidance for Linux users.
  • Consider including REST API or SDK examples that are platform-neutral.
  • Explicitly state any limitations or differences for Linux-based Service Fabric clusters regarding move cost configuration.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not mention or provide equivalent Linux/macOS CLI examples (such as Azure CLI or REST API). PowerShell is presented as the primary scripting interface, which may create friction for Linux users. The C# API examples are cross-platform, but operational/administrative examples are Windows-centric.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, if supported.
  • Explicitly mention whether PowerShell commands are available on Linux/macOS (via PowerShell Core), or provide guidance for Linux users.
  • Reorder sections or add notes to clarify cross-platform options for cluster administration.
  • If PowerShell is the only supported method, state this clearly and provide installation guidance for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page references Windows-specific upgrade instructions and tools, such as linking to 'service-fabric-cluster-upgrade-windows-server.md' and 'service-fabric-cluster-config-upgrade-windows-server.md'. The Patch Orchestration Application is described as 'for Windows' only, and there are no explicit Linux or cross-platform examples or links. The page does not clarify if Linux standalone clusters are supported or provide equivalent Linux guidance, creating friction for Linux users.
Recommendations
  • Add explicit guidance or links for upgrading Linux-based Service Fabric standalone clusters, if supported.
  • Clarify in the introduction whether the instructions apply only to Windows clusters or to both Windows and Linux.
  • Provide Linux-specific examples, tools, or references where relevant.
  • If Linux standalone clusters are not supported, state this clearly to avoid confusion.
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, but does not include equivalent CLI or scripting examples for Linux/macOS users (e.g., Azure CLI, Bash). PowerShell is presented as the primary command-line interface for service creation and management, with no mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention Bash scripting or REST API usage for managing Service Fabric metrics, where applicable.
  • Clarify which PowerShell commands are available cross-platform (PowerShell Core) and which are Windows-only.
  • Present code examples for both Windows and Linux/macOS users, ideally side-by-side.
  • Explicitly state if certain management tasks require Windows or PowerShell, and provide alternatives or workarounds for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides detailed PowerShell examples for managing node tags and service tag requirements in Azure Service Fabric, but does not offer equivalent CLI or scripting examples for Linux/macOS environments. The exclusive use of PowerShell and lack of Linux-native tools or cross-platform command-line examples creates friction for non-Windows users, even though Service Fabric itself is cross-platform.
Recommendations
  • Add Azure CLI or REST API examples for managing node tags and service tag requirements, as these are cross-platform and usable from Linux/macOS.
  • Include sample Bash scripts or instructions for Linux users, especially for standalone Service Fabric deployments.
  • Clarify which PowerShell commands are available via PowerShell Core (pwsh) on Linux/macOS, if applicable.
  • Mention any limitations or differences in node tag management between Windows and Linux Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters contains notable Windows bias. All command-line examples reference PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade), and there is no mention of Linux equivalents or cross-platform tools. The linked 'scale a standalone cluster' guide is titled 'service-fabric-cluster-windows-server-add-remove-nodes.md', implying a Windows Server focus. No Linux-specific guidance or examples are provided, which may create friction for Linux users managing standalone clusters.
Recommendations
  • Add Linux-specific examples and instructions for scaling standalone clusters, including relevant commands and tools (e.g., using sfctl or REST APIs).
  • Clarify whether standalone clusters can be managed on Linux, and if so, provide parity in documentation for Linux environments.
  • If PowerShell is required, explicitly state its platform limitations and suggest alternatives for Linux/macOS users.
  • Update links and referenced guides to include Linux-focused content or indicate Windows-only applicability.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for securing an Azure Service Fabric cluster presents Windows-specific security options and links before Linux equivalents, and lacks explicit examples or guidance for standalone Linux clusters. Windows tools and patterns (such as Windows security, Windows Server certificate service, and group Managed Service Accounts) are mentioned, while Linux-specific instructions, tools, or terminology are absent. The concept of Linux clusters is acknowledged, but practical guidance is missing.
Recommendations
  • Add explicit sections or links for securing standalone Linux Service Fabric clusters, including certificate management and client authentication.
  • Provide Linux-specific examples for certificate creation and installation (e.g., using OpenSSL, Linux file paths, and certificate stores).
  • Clarify which instructions apply equally to Linux and Windows, and highlight any differences.
  • Mention Linux alternatives to Windows tools (e.g., OpenSSL instead of Windows Server certificate service, Linux user accounts instead of Windows accounts).
  • Ensure parity in recommendations and guidance for both Linux and Windows environments.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides code examples for scaling Service Fabric services primarily in C# and PowerShell, with PowerShell being a Windows-centric tool. There are no equivalent Linux CLI or scripting examples (e.g., Bash, Azure CLI), and PowerShell commands are referenced before any Linux alternatives. The page does mention platform differences in logging, but otherwise does not provide Linux-specific guidance or parity in examples.
Recommendations
  • Add equivalent Linux-friendly examples using Azure CLI or Bash scripts for scaling operations.
  • Explicitly mention cross-platform tools and workflows where possible, and clarify which commands are Windows-only.
  • Provide guidance or links for Linux users on how to perform similar tasks without PowerShell.
  • Consider including a table or section summarizing platform-specific differences in scaling operations.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there are several instances where Windows-specific concepts, tools, and examples are presented first or exclusively. Windows services and executables (e.g., FabricHost.exe) are described in detail, with Linux equivalents not mentioned. PowerShell is referenced heavily for management tasks, and standalone cluster creation is only documented for Windows, with Linux support explicitly noted as unavailable. CLI tools and REST APIs are mentioned, but Windows-centric tools and patterns are often listed first or in more detail.
Recommendations
  • Add explicit Linux examples and workflows alongside Windows ones, especially for cluster management, health monitoring, and application lifecycle.
  • Clarify when a feature or tool is Windows-only, and provide Linux alternatives or workarounds where possible.
  • Balance the order of presentation so that Linux and Windows are treated equally (e.g., mention CLI and REST APIs before PowerShell when both are supported).
  • Document Linux cluster creation and management steps as soon as they become available.
  • Where Windows executables are discussed, note Linux equivalents or differences, linking to the 'Differences between Service Fabric on Linux and Windows' page.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is generally platform-neutral in its technical explanations, but the 'Next steps' section and the only explicit command-line reference (for downloading a ServicePackage in advance) point to PowerShell-based workflows and documentation. This subtly prioritizes Windows/PowerShell usage and may create friction for Linux users, as there are no equivalent Linux/CLI examples or links.
Recommendations
  • Add equivalent Azure CLI or REST API links and examples for deploying and managing Service Fabric applications, especially in the 'Next steps' section.
  • Where PowerShell cmdlets are referenced (such as for downloading ServicePackages), provide Linux-compatible alternatives or clarify if the operation is only possible via PowerShell.
  • Explicitly state platform compatibility for all referenced tools and commands.
  • If certain operations are only available via PowerShell, note this clearly and suggest workarounds or alternatives for Linux users if available.
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 for Azure Service Fabric container application manifest examples is notably Windows-centric. The manifest examples are explicitly based on a Windows Server 2016 container sample, and several explanations reference Windows-specific tools (e.g., 'winver' command) and Windows file paths (e.g., 'c:\VolumeTest\Data'). There is minimal mention of Linux, and no Linux-specific manifest examples or guidance are provided. Some sections briefly acknowledge Linux (e.g., certificate handling), but the overall focus and examples are tailored to Windows environments.
Recommendations
  • Provide equivalent manifest examples based on Linux containers and/or clusters, or clarify if Linux is not supported for these scenarios.
  • Include Linux-specific instructions or notes where Windows tools (like 'winver') or paths are referenced (e.g., how to get the OS build/version on Linux, use of '/mnt/volume' paths).
  • Explicitly state any feature or manifest element that is Windows-only, and offer Linux alternatives or limitations where applicable.
  • Add links or references to Linux container documentation or samples if available.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric is cross-platform, the exclusive use of Windows/PowerShell in the example creates friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS environments.
  • Include REST API examples for health reporting and querying, which are platform-agnostic.
  • Mention cross-platform tooling and clarify which commands are available on each OS.
  • Consider showing Linux/macOS examples first or alongside Windows/PowerShell examples.
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 for Azure Service Fabric hosting model presents PowerShell as the primary CLI example for service creation and management, with no mention of Linux-native CLI tools or examples. PowerShell is referenced first and exclusively for command-line operations, and all linked command references are for PowerShell modules. There are no Bash, Azure CLI, or Linux-specific workflow examples, creating friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add Azure CLI examples for service creation and management, especially for operations like New-ServiceFabricService.
  • Mention cross-platform tools and workflows (e.g., Azure CLI, REST API usage from Bash/curl) alongside PowerShell.
  • Clarify which operations can be performed from Linux/macOS and provide guidance for those environments.
  • Reorder examples to present cross-platform options first, or at least equally with PowerShell.
  • Link to documentation for Linux/macOS Service Fabric clusters and management tools.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for managing application parameters in Azure Service Fabric, with a notable emphasis on PowerShell and Visual Studio workflows. PowerShell is mentioned first for application creation, and Visual Studio parameter files are discussed in detail, both of which are Windows-centric tools. While sfctl and Jenkins are mentioned, Linux-specific examples or workflows are less prominent and not explained in depth.
Recommendations
  • Provide explicit Linux/macOS examples for application creation, such as using sfctl with install.sh, including sample commands.
  • Expand on Jenkins usage for parameter substitution, with sample shell scripts or workflows for Linux environments.
  • Balance the order of examples so that Linux tools (sfctl, shell scripts) are presented alongside or before Windows tools.
  • Clarify which tools are cross-platform and which are Windows-only, to guide users appropriately.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides deployment instructions and command-line examples exclusively using PowerShell, with no mention of Azure CLI or Bash equivalents. The examples for connecting to VMs (RDP and ping) use Windows-centric tools and syntax. There are no Linux/macOS-specific instructions or examples, and Windows tools are referenced first and exclusively throughout the article.
Recommendations
  • Add Azure CLI and Bash equivalents for all PowerShell deployment commands.
  • Include examples for connecting to VMs using SSH, and for network testing using Linux/macOS tools (e.g., ssh, ping from Bash).
  • Mention cross-platform tools and clarify that Service Fabric clusters can be managed from Linux/macOS as well as Windows.
  • Where possible, provide guidance for Linux/macOS users on template editing, deployment, and troubleshooting.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides thorough coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Azure Service Fabric. However, Windows-specific tools and APIs (e.g., HTTP.sys, netsh, Windows HTTP Server API) are discussed in detail, often before or alongside Kestrel. HTTP.sys usage is described with explicit notes about Windows-only support, but Linux/macOS equivalents or considerations are not mentioned. Examples and endpoint configuration instructions reference Windows tools (netsh) and concepts, and there are no explicit Linux/macOS setup or troubleshooting examples. Kestrel is correctly positioned as the preferred cross-platform option, but Windows-specific patterns and tools are given significant space and are sometimes discussed first.
Recommendations
  • Add explicit Linux/macOS instructions or troubleshooting notes for Service Fabric and ASP.NET Core hosting, especially for endpoint configuration and port management.
  • Include example workflows or code snippets for Linux/macOS environments, such as how to configure firewall rules or manage ports without Windows tools like netsh.
  • Clarify that Kestrel is the only supported web server for Linux/macOS, and provide guidance for Linux users on avoiding Windows-only features.
  • Reorder sections to present cross-platform (Kestrel) options before Windows-only (HTTP.sys) options, emphasizing Linux/macOS parity.
  • Add a summary table or section highlighting platform support for each web server and feature.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides code examples and references that are platform-neutral (C#), but in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned for application upgrades, with PowerShell specifically called out. There are no Linux/macOS equivalents (such as CLI or Bash) referenced alongside these tools, which may create friction for non-Windows users.
Recommendations
  • Add links or references to Linux/macOS-compatible upgrade methods, such as using Azure CLI or Bash scripts, if available.
  • Clarify whether the PowerShell and Visual Studio tutorials are Windows-only, and provide alternative instructions for Linux/macOS users if possible.
  • Consider mentioning cross-platform tools earlier or alongside Windows tools to ensure parity.
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 examples for PowerShell commands and usage, which are Windows-centric, and presents these before mentioning REST or API alternatives. There are no equivalent Linux/bash CLI examples or references to cross-platform tools. The PowerShell examples are extensive and shown first, while REST is only briefly mentioned and lacks concrete examples. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer bash/CLI workflows.
Recommendations
  • Add equivalent bash or Azure CLI examples for sending health reports and querying health status.
  • Explicitly mention cross-platform alternatives to PowerShell, such as Azure CLI or REST, and provide concrete examples.
  • Clarify which tools are available on Linux/macOS and how to perform the same tasks without PowerShell.
  • Consider reorganizing the examples so REST or cross-platform approaches are presented before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell example for deploying Service Fabric applications, which is Windows-centric. The Service Fabric schema path is given only for Windows. Linux-specific deployment instructions and CLI examples are missing or less prominent, though there is a brief mention of the Linux certificate store location.
Recommendations
  • Add equivalent Linux/macOS deployment examples using Azure CLI or Service Fabric CLI (sfctl), especially for application deployment and parameter overrides.
  • Mention the schema location for Linux installations, or clarify if it is not applicable.
  • Ensure that Linux-specific instructions (such as certificate handling, endpoint configuration, and port ACLing) are as detailed as Windows instructions.
  • Where PowerShell is used, provide alternative commands for Linux/macOS users.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily focused on Visual Studio workflows and Windows-centric tooling. All deployment and configuration examples reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish), which are Windows-only. There are no Linux/macOS equivalents or guidance for cross-platform development, and the only alternative deployment methods mentioned are ARM templates and PowerShell cmdlets, both referenced after Visual Studio. No CLI or Linux-native tools are discussed, and all screenshots and instructions assume Windows environments.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage StartupServices.xml outside Visual Studio.
  • Provide examples using Azure CLI, Service Fabric CLI (sfctl), or other cross-platform tools for deployment and configuration.
  • Clarify which features are Visual Studio/Windows-only and offer alternative workflows for Linux/macOS users.
  • Include sample workflows for editing and deploying StartupServices.xml from non-Windows environments.
  • Mention any limitations or unsupported scenarios for Linux/macOS users up front.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides usage instructions for the Fault Analysis Service in Service Fabric, with explicit PowerShell guidance and references to the Service Fabric SDK and PowerShell module. There are no Linux/macOS CLI or scripting examples (such as Bash or Azure CLI), nor is there mention of Linux-specific tools or workflows. The focus on PowerShell and Windows SDK tools creates friction for Linux/macOS users, who may need to find alternative methods or tools.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or Bash scripts, if supported.
  • Clarify whether the Fault Analysis Service APIs can be accessed from Linux/macOS environments, and provide guidance for those platforms.
  • Mention any cross-platform SDKs or tools (such as .NET Core, REST APIs) that can be used from Linux/macOS.
  • If PowerShell is required, note the availability of PowerShell Core on Linux/macOS and provide installation instructions.
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-centric tools, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and upgrade instructions reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS alternatives or cross-platform CLI tools. The page does not provide guidance for users on Linux or macOS, nor does it reference Azure CLI or REST API options for application upgrades.
Recommendations
  • Add instructions or links for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Include examples for configuring upgrade parameters and health policies using Linux/macOS-compatible tools.
  • Clarify whether Visual Studio and PowerShell are required, or if alternative workflows exist for non-Windows environments.
  • Mention any limitations or required workarounds for Linux/macOS users, if applicable.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is intended for both Windows and Linux virtual machines, as stated at the top. Most command-line examples (Azure CLI, API, PowerShell) are generic and applicable to both OS types. However, the ARM template example is Windows-specific: it only provides parameters and configuration for Windows Server images, with no Linux image options or guidance. Additionally, the ARM template section presents Windows as the default, which may create friction for Linux users seeking parity.
Recommendations
  • Add ARM template examples or parameters for Linux VM images (e.g., Ubuntu, CentOS) alongside Windows examples.
  • Clarify in the ARM template section that Linux images are supported and provide guidance or links for Linux VM ARM template configuration.
  • Consider alternating the order of examples or explicitly stating that CLI and API methods are OS-agnostic.
  • If possible, provide PowerShell and CLI examples for both Windows and Linux VM creation (e.g., using --image Ubuntu2204 and Windows image).
GitHub Create Pull Request
Virtual Machines Deprovision or generalize a VM before creating an image ...docs/blob/main/articles/virtual-machines/generalize.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides clear, separate instructions for both Linux and Windows VMs. However, the Windows section includes more detailed prerequisites and uses PowerShell-specific commands (Set-AzVm) without mentioning Azure CLI equivalents. The Windows example for marking a VM as generalized uses PowerShell, while the Linux section uses Azure CLI. The Windows section also appears after the Linux section, but the PowerShell example is not accompanied by a CLI equivalent, which could create friction for users on Linux/macOS who manage Windows VMs.
Recommendations
  • Add Azure CLI equivalents for Windows VM steps, especially for marking a VM as generalized (e.g., 'az vm generalize').
  • Mention that Azure CLI can be used cross-platform for Windows VM management, not just PowerShell.
  • Consider providing both PowerShell and CLI examples side-by-side for Windows VM steps.
  • Ensure parity in detail between Linux and Windows sections, especially regarding prerequisites and commands.
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
While the documentation is focused on Linux VMs, there is notable Windows bias in several areas: PowerShell examples and tooling are heavily featured alongside Azure CLI, with PowerShell-specific commands and SAS token generation instructions dominating. Windows tools (e.g., PowerShell, 'New-AzStorageBlobSASToken') are referenced without Linux equivalents or alternatives. In some sections, Windows patterns (such as script parameter passing) are explained first or exclusively. REST API and ARM template examples use Windows-style scripts (e.g., 'Write-Host', '.ps1' files), and there is a lack of explicit Linux/bash script examples in these areas.
Recommendations
  • Add Linux/bash script examples in REST API and ARM template sections (e.g., use 'echo Hello World!' or '.sh' files instead of 'Write-Host' and '.ps1').
  • Provide Linux-native alternatives for SAS token generation (e.g., Azure CLI commands instead of 'New-AzStorageBlobSASToken').
  • Clarify when PowerShell commands are Windows-specific and offer equivalent Azure CLI or bash commands for Linux users.
  • Ensure script parameter passing examples are shown for both Windows (.ps1) and Linux (.sh) scripts, with clear distinctions.
  • Review and update documentation to avoid referencing Windows tools or patterns before Linux equivalents, especially in Linux-focused content.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux VHD creation, frequently references Windows-centric tools and workflows (Hyper-V, PowerShell's Convert-VHD) and presents Windows/Hyper-V steps before mentioning or omitting Linux-native alternatives. Linux users are left without clear guidance for VHD creation, conversion, or VM management, creating friction for non-Windows environments.
Recommendations
  • Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, KVM).
  • Provide examples for extracting and manipulating VHDs on Linux without referencing Hyper-V or Windows PowerShell.
  • Reorganize prerequisite and manual steps to prioritize Linux workflows, or at least present Linux and Windows options equally.
  • Clarify which steps are Windows-only and offer Linux alternatives wherever possible (e.g., disk conversion, VM management).
  • Link to Linux-specific guides for virtualization and VHD management.
GitHub Create Pull Request
Virtual Machines Upload a VHD to Azure or copy a disk across regions - Azure CLI ...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a Windows-centric example for uploading a VHD using AzCopy, specifically referencing 'AzCopy.exe' and a Windows file path ('c:\somewhere\mydisk.vhd'), without offering a Linux/macOS equivalent. The AzCopy command is shown only in Windows syntax, and there is no explicit example for Linux/macOS users, even though the page is intended for both Linux and Windows VMs. Additionally, the Windows example appears before any mention of Linux usage patterns.
Recommendations
  • Add a Linux/macOS AzCopy example, e.g., 'azcopy copy /home/user/mydisk.vhd "sas-URI" --blob-type PageBlob'.
  • Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
  • Use generic file paths or show both Windows and Linux/macOS paths in examples.
  • Ensure that CLI examples and scripts are platform-neutral or provide variants for each OS.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, and references Service Fabric Explorer (a GUI tool typically used on Windows). There are no Linux CLI or cross-platform alternatives mentioned for these operations, and Windows tools/patterns are presented first and exclusively.
Recommendations
  • Add equivalent Linux/macOS command-line examples, such as using Azure CLI or REST API if available.
  • Clarify whether the PowerShell command can be run from PowerShell Core on Linux/macOS, or provide Bash alternatives.
  • Mention cross-platform access to Service Fabric Explorer or alternatives for Linux users.
  • Explicitly state platform requirements for any commands or tools, and provide guidance for Linux/macOS users where possible.
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 exhibits notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any equivalent Azure CLI or Bash examples. The application packaging step references Visual Studio, a Windows-centric tool, and does not mention cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and Windows tools are presented as the default approach.
Recommendations
  • Add Azure CLI examples for deployment and deletion tasks alongside PowerShell examples.
  • Include instructions for packaging applications using cross-platform tools (such as dotnet CLI or sfpkg command-line utility) instead of only Visual Studio.
  • Provide guidance for Linux/macOS users on uploading application packages to Azure Blob Storage (e.g., using az storage blob upload).
  • Ensure screenshots and walkthroughs are not exclusively tied to Windows tools or interfaces.
  • Mention that all steps can be completed on Linux/macOS and provide links to relevant cross-platform documentation.
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 are exclusively in PowerShell, with no mention of Azure CLI (az), Bash, or cross-platform scripting alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer using the Azure CLI.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all relevant operations (add, remove, scale, configure node types).
  • Explicitly mention that PowerShell examples require Azure PowerShell module and may not be available on all platforms.
  • Where possible, provide Bash or cross-platform scripting guidance, or link to Azure CLI documentation.
  • Clarify if any operations are only possible with PowerShell and explain why, or provide workarounds for non-Windows users.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation covers monitoring Azure Service Fabric clusters on both Windows and Linux, but there are several areas where Windows tools and examples are mentioned first or exclusively. Windows-specific tools (e.g., Event Log, Event Viewer, Diagnostics Agent) are referenced before or more prominently than Linux equivalents. Some sections lack Linux-specific examples or guidance, and Windows terminology (ETW, EventSource) is used without always providing Linux alternatives (LTTng, Syslog). However, Linux support is acknowledged and most monitoring approaches are described as cross-platform.
Recommendations
  • Ensure Linux-specific tools and workflows (e.g., LTTng, Syslog, Linux agent configuration) are described with equal prominence and detail as Windows tools.
  • Provide Linux-focused examples and tutorials alongside Windows ones, especially for cluster monitoring, event access, and agent setup.
  • When referencing Windows tools (Event Viewer, Diagnostics Agent), immediately mention the Linux equivalents and link to relevant Linux documentation.
  • Clarify which features are Windows-only (e.g., EventStore APIs) and provide alternative solutions or workarounds for Linux users.
  • Add sample code or configuration snippets for Linux environments where only Windows examples are currently given.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page is generally platform-neutral regarding Azure Service Fabric periodic backup configuration, but there is a notable bias in the 'File share' backup storage section. Only Windows-style UNC paths (\\StorageServer\BackupStore) and Windows authentication methods are described, with no mention of Linux-compatible file share paths (e.g., SMB mounts on Linux) or authentication options. Additionally, Windows authentication is discussed first and in more detail, while Linux alternatives are absent.
Recommendations
  • Add examples and guidance for configuring file share backup storage using Linux-compatible paths and authentication methods (e.g., mounting SMB shares on Linux, using CIFS, specifying credentials).
  • Clarify whether Linux clusters can use file share backup storage and provide any relevant limitations or instructions.
  • Where authentication options are discussed, mention Linux equivalents or note if only Windows authentication is supported.
  • Consider including a note about cross-platform compatibility for backup storage options, especially for standalone clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux guidance for key security tasks, but Windows examples and tools (such as PowerShell and Windows Defender) are often presented first or exclusively. Windows-specific recommendations (e.g., security baselines, Defender, DSC) are highlighted, while Linux equivalents are not mentioned or are less detailed. Some sections (like Windows Defender) are Windows-only, but this is acknowledged. Overall, Linux users can complete the tasks, but may experience friction due to Windows-first presentation and lack of Linux-specific tooling recommendations.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them.
  • Provide Linux-specific security baseline recommendations (e.g., CIS benchmarks, OS hardening guides) where Windows baselines are mentioned.
  • Mention Linux antimalware solutions or clarify best practices for Linux security in relevant sections.
  • Where PowerShell is used for Windows, provide equivalent Bash or CLI commands for Linux.
  • Explicitly note when a feature or tool is Windows-only, and offer Linux alternatives or guidance where possible.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides general guidance on Azure Service Fabric node types and VM scale sets, referencing both Windows and Linux node types in the extension snippet. However, there is a subtle Windows bias: the JSON example uses a Windows-style file path ('D:\\SvcFab') for the 'dataPath' property, and the 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-specific tasks. No equivalent Linux examples or guidance are provided, and Windows patterns (such as RDP and file paths) are mentioned first or exclusively.
Recommendations
  • Provide Linux-specific examples for the 'dataPath' property (e.g., '/var/svcfab') alongside the Windows path.
  • Add guidance or links for SSH access and Linux admin credential changes, mirroring the Windows RDP/PowerShell examples.
  • Clarify which steps or scripts are Windows-only and offer Linux alternatives where possible.
  • Ensure that examples and property descriptions are OS-neutral or include both Windows and Linux variants.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json) deployments. However, Windows-specific configuration (ClusterManifest.xml with <WindowsServer>) is presented first and more prominently, and PowerShell examples are included for service creation and updates, with no equivalent Linux shell or CLI examples. The documentation refers to WindowsServer as the infrastructure type in the XML example, which may imply Windows bias, but also includes JSON examples suitable for Linux/standalone clusters. No explicit Linux/macOS examples or tools (such as Bash, Azure CLI, or Linux-specific guidance) are provided.
Recommendations
  • Add explicit Linux/Unix/macOS configuration examples, such as referencing <Linux> infrastructure in ClusterManifest.xml or providing guidance for Linux node setup.
  • Include Azure CLI or Bash examples for service creation and updates alongside PowerShell and C#.
  • Clarify that ClusterConfig.json is suitable for Linux/standalone deployments and provide links or references to Linux-specific Service Fabric documentation.
  • Balance the order of examples so that Linux/cross-platform options are presented equally or before Windows-specific ones.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation generally avoids OS-specific instructions, but in the 'Upgrading OS images for cluster nodes' section, it explicitly links only to Windows patching guidance and references Patch Orchestration Application (POA) as a Windows solution. There are no equivalent Linux instructions or links, and the section title does not clarify that it is Windows-only. Additionally, PowerShell and Azure CLI are mentioned together for some tasks, but no Linux-specific tools or examples are provided, and Windows patching is discussed before any mention of Linux.
Recommendations
  • Add a parallel section or link for upgrading OS images on Linux-based Service Fabric clusters, if supported.
  • Clarify in the 'Upgrading OS images for cluster nodes' section title or body that the linked guidance is Windows-specific, and provide Linux guidance or a statement if Linux is not supported.
  • Where PowerShell/Azure CLI are mentioned, ensure Linux users are explicitly addressed (e.g., provide Bash/Azure CLI examples or clarify cross-platform support).
  • Review for any other OS-specific tools or patterns and ensure Linux parity or clear labeling.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page on Azure Service Fabric Events primarily references Windows-centric logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and monitoring tools. There are no explicit Linux/macOS equivalents or examples provided, nor is there guidance for accessing Service Fabric events from Linux-based clusters. The Windows tools and patterns are mentioned first and exclusively, creating friction for Linux users.
Recommendations
  • Add documentation and examples for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration for Linux).
  • Mention Linux-compatible diagnostics agents or tools, if available, and provide configuration guidance.
  • Clarify which event access methods are cross-platform (such as EventStore REST APIs) and highlight their use for Linux/macOS users.
  • Where possible, provide parity in examples and tool references for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI or bash examples. Windows-centric tools (PowerShell, Visual Studio) are mentioned for service configuration, while Linux alternatives are not. The limitations section notes Linux support is restricted, but the overall guidance and examples are Windows-first, creating friction for Linux users.
Recommendations
  • Add Linux CLI/bash examples for configuring DNS names, such as using Azure CLI or REST API.
  • Mention cross-platform editors (e.g., VS Code) alongside Visual Studio for editing ApplicationManifest.xml.
  • Clarify how Linux users can enable DNS service (e.g., via ARM templates or CLI) and highlight any differences.
  • Provide explicit guidance or links for Linux users to complete tasks that are shown with PowerShell for Windows.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and links to a PowerShell-based deployment article as the next step. While .NET and REST are mentioned, PowerShell is presented first and most prominently. There are no explicit Linux/macOS CLI or tooling examples (such as Azure CLI, Bash, or cross-platform scripts), and the workflow assumes Visual Studio for publishing, which is Windows-centric.
Recommendations
  • Add examples using Azure CLI or Bash scripts for retrieving cluster manifests and deploying applications, highlighting cross-platform approaches.
  • Include references to cross-platform tools (e.g., Service Fabric CLI, sfctl) and document their usage for Linux/macOS users.
  • Balance the order of examples so that PowerShell is not always presented first; alternate with cross-platform or Linux-native tools.
  • Clarify that Visual Studio is Windows-centric and suggest alternatives for Linux/macOS users (e.g., VS Code, command-line tools).
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation references both Azure CLI and Azure PowerShell for creating Virtual Machine Scale Sets, but PowerShell is mentioned alongside CLI and before ARM Template. There are no explicit Linux shell (bash) examples, and PowerShell is referenced without equivalent Linux-specific guidance. Windows-specific scenarios (activation, updates) are listed before Linux package manager access in the networking section. No Linux-specific migration examples or tools are provided.
Recommendations
  • Provide explicit bash/Linux shell examples alongside PowerShell and Azure CLI, especially for VM creation and migration steps.
  • Mention Azure CLI (which is cross-platform) before PowerShell, and clarify that CLI commands work on Linux/macOS.
  • Add Linux-specific migration considerations, such as handling SSH keys, package managers, and OS disk migration.
  • Ensure Linux package manager connectivity is discussed with equal prominence as Windows activation and updates.
  • Where PowerShell is referenced, add notes or links for Linux/macOS users to use Azure CLI or bash equivalents.
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_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page provides Service Fabric application and service manifest examples. There are several indications of Windows bias: (1) Windows terminology and tools are referenced first or exclusively, such as 'ServiceFabric PowerShell module' for service creation, (2) examples use Windows-style batch scripts (Setup.bat) and executables (.exe), (3) security principals reference Windows system groups (Administrators, NetworkService), and (4) domain account support is noted as Windows-only. There are no explicit Linux or cross-platform examples, and Linux-specific guidance is missing.
Recommendations
  • Add examples using Linux shell scripts (e.g., Setup.sh) and non-.exe binaries to demonstrate cross-platform deployment.
  • Mention and provide examples for using Service Fabric CLI (sfctl) or REST API for service management, which are cross-platform, instead of only referencing PowerShell.
  • Clarify which security principal concepts (users, groups) are supported on Linux clusters and provide Linux-specific guidance.
  • Explicitly note any manifest settings or patterns that differ between Windows and Linux clusters, and link to relevant Linux documentation.
  • Where possible, show both Windows and Linux approaches side-by-side in manifest and operational examples.
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 heavily references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links exclusively to PowerShell cmdlets. There are no examples or explicit instructions for Linux/macOS users, such as using the Service Fabric CLI (sfctl) or REST APIs, even though Service Fabric supports cross-platform management. The documentation assumes Windows tooling and does not mention Linux equivalents or alternative workflows.
Recommendations
  • Add examples using sfctl (Service Fabric CLI) for Linux/macOS users, showing how to remove, restore, and query replicas.
  • Mention REST API endpoints or FabricClient SDK usage for cross-platform scenarios.
  • Clarify whether the PowerShell APIs are available only on Windows, and provide guidance for Linux users if not.
  • Include a section or note explicitly addressing Linux/macOS management options for replica soft delete operations.
GitHub Create Pull Request
Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation covers both Linux and Windows VM image creation with Azure Image Builder, but there is a notable Windows bias in several areas. PowerShell examples and references are frequently given, sometimes before or instead of Linux equivalents. Windows-specific tools (e.g., Get-FileHash, Sysprep) are mentioned with detailed instructions, while Linux tools (e.g., sha256sum, waagent) are referenced but less emphasized. Some customizers (WindowsRestart, WindowsUpdate, PowerShell) are Windows-only, and this is clearly documented. However, in sections like checksum generation, Windows/PowerShell instructions are often more prominent or detailed than Linux equivalents.
Recommendations
  • Ensure Linux (bash/terminal) examples are provided alongside PowerShell examples, especially for checksum generation and image build operations.
  • Present Linux and Windows examples in parallel or alternate order, rather than defaulting to Windows/PowerShell first.
  • Expand Linux tool instructions (e.g., explain how to use sha256sum, wget, curl) with the same detail as Windows tools.
  • Where possible, clarify when a feature or customizer is Windows-only, and offer Linux alternatives or workarounds if available.
  • Add explicit bash/terminal commands for common operations (e.g., starting/cancelling builds, querying resources) alongside Azure CLI/PowerShell.
  • Review the order and prominence of Windows vs. Linux content to ensure parity.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page for Azure Service Fabric container image management shows minor Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned explicitly in the configuration examples and descriptions, and the default behavior is to skip deleting these Windows images. Linux container images are referenced only in a generic example, and there are no Linux-specific examples or guidance. However, the documentation does not restrict the feature to Windows and does mention generic container image patterns.
Recommendations
  • Include explicit examples for Linux container images (e.g., Ubuntu, Alpine) in the 'ContainerImagesToSkip' setting.
  • Clarify that the cleanup and deletion features apply equally to Linux containers, and provide guidance for common Linux container scenarios.
  • Mention any differences in behavior between Windows and Linux containers, if applicable.
  • Add sample configuration for skipping Linux base images (e.g., 'docker.io/library/ubuntu:latest').
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 are minor signs of Windows bias. Windows container runtimes and scenarios (such as IIS lift-and-shift) are described in greater detail, and Windows tools (Mirantis Container Runtime, DockerEE) are listed explicitly. Windows examples and links are sometimes presented before Linux equivalents, and Windows-specific scenarios (IIS, ASP.NET MVC) are highlighted. However, Linux support is clearly mentioned, and Linux tutorials are linked.
Recommendations
  • Ensure Linux and Windows examples/tutorials are presented with equal prominence and in parallel (e.g., always list Linux and Windows quickstarts together).
  • Expand Linux-specific scenarios and examples to match the detail given for Windows (e.g., highlight common Linux workloads or migration scenarios).
  • Mention Linux container runtimes/tools with the same specificity as Windows (e.g., reference containerd or other alternatives if relevant).
  • Avoid listing Windows tools or scenarios first unless there is a technical reason.
  • Add more Linux-focused use cases alongside Windows-specific ones (such as IIS).
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation presents PowerShell commands first for deploying Docker Compose files on Azure Service Fabric, followed by cross-platform Service Fabric CLI (sfctl) examples. The PowerShell section is more detailed, with multiple commands for deployment, status, upgrade, and rollback. While the CLI section covers equivalent functionality, the ordering and depth of PowerShell examples suggest a Windows-first bias. However, Linux/macOS users can complete all tasks using sfctl, and no critical functionality is missing for non-Windows users.
Recommendations
  • Present Service Fabric CLI (sfctl) examples before PowerShell, or in parallel, to emphasize cross-platform support.
  • Ensure that CLI examples are as detailed as PowerShell examples, covering all operations (deployment, status, upgrade, rollback, etc.).
  • Explicitly state that sfctl is supported on Linux/macOS and provide installation instructions or links for those platforms.
  • Add a note clarifying that all tasks can be performed on Linux/macOS using sfctl, to reassure non-Windows users.
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_tools ⚠ī¸ windows_first
Summary
The documentation page exhibits a mild Windows bias. The only explicit file path for the Service Fabric schema is given as a Windows path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\...), and there is no mention of Linux or cross-platform equivalents. The structure and terminology (e.g., .exe files) also implicitly assume a Windows environment, and Visual Studio is mentioned as a primary tool, which is most commonly used on Windows. However, the content does not explicitly exclude Linux, and some examples reference Node.js and Java, which are cross-platform.
Recommendations
  • Provide Linux-equivalent file paths or clarify where schema files are located on Linux installations.
  • Include explicit mention or examples of packaging non-Windows executables (e.g., ELF binaries) to reinforce cross-platform support.
  • Mention cross-platform tools (such as Visual Studio Code or CLI alternatives) alongside Visual Studio.
  • Clarify any platform-specific limitations or requirements for Service Fabric guest executables.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions both Windows and Linux support for Azure Service Fabric, and provides parity in describing development environments for each OS. However, in the 'Any OS, any cloud' section, Windows development is described first, with Visual Studio and PowerShell highlighted before Linux development tools (Eclipse, Yeoman). The quickstart link also points to a .NET (likely Windows-oriented) guide, rather than a Linux or cross-platform example.
Recommendations
  • Alternate the order of Windows and Linux mentions to avoid implicit prioritization.
  • Provide quickstart links for both Windows (.NET) and Linux (Java/.NET Core) users.
  • Ensure that examples and tooling references for Linux are as prominent and detailed as those for Windows.
  • Consider linking to cross-platform guides or explicitly noting parity where it exists.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page primarily describes Service Fabric concepts and terminology, but there are several instances where Windows-specific tools and patterns are mentioned before their Linux equivalents. For example, the description of nodes references an 'auto-start Windows service, FabricHost.exe' and Windows executables (EXE/DLL) without mentioning Linux equivalents or patterns. Windows Server containers are mentioned before Docker containers on Linux. However, the page does acknowledge Linux support and provides some parity in container and guest executable descriptions.
Recommendations
  • When describing node startup, clarify how Service Fabric operates on Linux nodes (e.g., which processes/services are used, if any).
  • When referencing executable formats, mention Linux equivalents (e.g., ELF binaries) alongside EXE/DLL.
  • Present Windows and Linux container support together, or mention Linux first where appropriate.
  • Add explicit examples or clarifications for Linux environments where Windows-specific terminology is used.
  • Ensure that descriptions of tools and processes are platform-neutral unless the feature is Windows-only.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell (a Windows-centric tool) is often presented before CLI, and some sections (such as querying public IPs) show PowerShell examples before CLI. Portal instructions are platform-neutral, but PowerShell is emphasized in several places. No critical features are Windows-only, and Linux parity is generally maintained, but the ordering and emphasis subtly favor Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by Linux/macOS users.
  • Ensure all PowerShell examples have equivalent Azure CLI examples, especially for querying and updating resources.
  • Add explicit notes clarifying that Azure CLI commands work on Linux, macOS, and Windows.
  • Where possible, highlight cross-platform tools and workflows first.
  • Consider adding Bash script examples for advanced scenarios, if relevant.
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 custom metrics and the application health extension. However, there are several instances where Windows/PowerShell tools and patterns are mentioned first or in more detail. For example, in the 'Install the application health extension' section, PowerShell is presented immediately after CLI, and the PowerShell example is more verbose and detailed. REST examples use 'ApplicationHealthWindows' as the extension type, even though Linux is also supported. In querying and troubleshooting, PowerShell is consistently given as a primary option alongside CLI and REST, sometimes with more explanation. The documentation does not omit Linux examples, but Windows/PowerShell tools and terminology are often prioritized or presented first.
Recommendations
  • Ensure Linux and macOS examples (Bash, Python, CLI) are presented before or alongside Windows/PowerShell examples, especially in critical sections.
  • Use 'ApplicationHealthLinux' as the default extension type in generic examples, or show both Linux and Windows variants equally.
  • Balance the detail and explanation between Bash/Python and PowerShell examples, so Linux users receive equally comprehensive guidance.
  • Where possible, clarify cross-platform support and highlight any OS-specific requirements or differences.
  • Consider adding macOS-specific notes or examples if relevant, especially for CLI usage.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring rolling upgrades on Virtual Machine Scale Sets. However, PowerShell examples are present throughout and in every major section, and in some cases, PowerShell is listed before ARM template examples. There is a slight Windows bias due to the heavy inclusion of PowerShell, which is primarily used on Windows, but Azure CLI examples (cross-platform) are also provided. No critical Linux/macOS parity issues are found, as all tasks can be completed using Azure CLI.
Recommendations
  • Ensure Azure CLI examples are always listed before PowerShell examples, as CLI is cross-platform.
  • Clarify that PowerShell is primarily for Windows users and Azure CLI is recommended for Linux/macOS.
  • Consider adding Bash shell scripting examples for advanced automation scenarios.
  • Explicitly mention that all Azure CLI commands work on Linux/macOS and Windows.
  • If possible, add a note about using Azure Cloud Shell, which is platform-agnostic.
GitHub Create Pull Request
Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides configuration examples for rolling upgrades with MaxSurge using Azure Portal, Azure CLI, PowerShell, and ARM templates. While the CLI and ARM template sections are cross-platform, the PowerShell example is Windows-specific and is given equal prominence. The ordering of examples places PowerShell immediately after CLI, which may subtly prioritize Windows tools. However, no critical steps are Windows-only, and Linux/macOS users can complete all tasks using CLI or ARM templates.
Recommendations
  • Explicitly note that Azure CLI and ARM templates are fully cross-platform and suitable for Linux/macOS users.
  • Consider listing CLI examples before PowerShell, or grouping CLI and ARM Template as 'cross-platform' options.
  • Add a brief note in the PowerShell section indicating it is Windows-only, for clarity.
  • If possible, add Bash shell scripting examples for Azure CLI to further reinforce Linux parity.
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI links for configuring the NetworkAccessPolicy, but the PowerShell link is listed first and the custom RBAC role creation is linked only to a PowerShell-based guide. There are no explicit Linux/macOS examples or references, and the CLI link for private links is specifically labeled 'linux', but the main guidance and examples tend to favor Windows/PowerShell tools.
Recommendations
  • Provide links to both Azure CLI and PowerShell guides for custom RBAC role creation, not just PowerShell.
  • List Azure CLI and PowerShell options together or alternate their order to avoid Windows-first bias.
  • Clarify that Azure CLI is cross-platform and provide explicit Linux/macOS usage examples where relevant.
  • Ensure that all referenced guides (such as for private links) have parity between Windows and Linux instructions.
GitHub Create Pull Request
Virtual Machines Secure Azure Managed Disk Downloads and Uploads ...icles/virtual-machines/disks-secure-upload-download.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell examples are presented before CLI examples in several sections. Portal instructions are also included. While CLI is cross-platform, PowerShell is more commonly associated with Windows, and its precedence in examples may create a subtle Windows bias. However, Linux-specific guidance is present in the 'Next steps' section, and CLI instructions are available throughout.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly note that Azure CLI works on Linux/macOS, and provide links to installation instructions for those platforms.
  • Where possible, add Bash shell script examples alongside PowerShell, especially for disk operations.
  • Ensure that any screenshots or UI references are not Windows-specific unless necessary.
  • Review included files (prereqs, restrictions) to confirm Linux parity in prerequisites and restrictions.
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is focused on Linux VM extensions, but consistently presents both Azure CLI and Azure PowerShell examples for all tasks. PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every section may create friction for Linux users. Additionally, in several sections, PowerShell examples are given immediately after CLI, sometimes with more detailed output, which may subtly reinforce Windows tooling. However, all examples and explanations are applicable to Linux VMs, and Linux-specific tools (bash, waagent) are referenced where relevant.
Recommendations
  • Consider prioritizing Azure CLI examples, as CLI is cross-platform and native to Linux/macOS.
  • Move PowerShell examples to a secondary position or into expandable sections, so Linux users see CLI first.
  • Clarify that PowerShell is optional and primarily for users on Windows or those who prefer it.
  • Add explicit notes or links for Linux-native scripting and automation (bash, shell scripts) where relevant.
  • Ensure that troubleshooting and log file references use Linux paths and conventions, as is mostly done.
GitHub Create Pull Request
Virtual Machines NVIDIA GPU Driver Extension - Azure Linux VMs ...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM GPU driver installation, but includes PowerShell examples alongside Azure CLI and ARM template examples. The PowerShell example is presented before the Azure CLI example, which is more relevant for Linux users. There is also mention of a Windows extension, but only as a cross-reference, not as a primary topic. All screenshots and manual steps are Linux-specific, and troubleshooting/logging paths are Linux-centric.
Recommendations
  • Move the Azure CLI example before the PowerShell example, as Azure CLI is more commonly used for Linux VM management.
  • Clearly indicate that PowerShell is optional and primarily for users managing Azure from Windows environments.
  • Consider adding Bash shell script examples for common tasks, as Bash is the default shell for most Linux users.
  • If PowerShell is included, add a note explaining its cross-platform nature, but clarify its typical usage scenarios.
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 the Azure Key Vault VM Extension for Linux and provides extensive Linux-specific details. However, in several sections, Windows-oriented tools (Azure PowerShell) are presented before their Linux equivalents (Azure CLI), and PowerShell deployment examples are more detailed and appear first. Troubleshooting instructions also mention PowerShell before CLI. There are no missing Linux examples or Windows-only tools, but the ordering and emphasis could create friction for Linux users.
Recommendations
  • Present Azure CLI examples before Azure PowerShell examples, as CLI is cross-platform and preferred for Linux users.
  • Expand CLI troubleshooting instructions to match the detail provided for PowerShell.
  • Clarify that PowerShell examples are optional and primarily for Windows users, while CLI is recommended for Linux.
  • Consider adding Bash script examples for common deployment scenarios.
  • Ensure all deployment and troubleshooting instructions are equally detailed for CLI and PowerShell.
GitHub Create Pull Request
Virtual Machines What's New in Azure VM Image Builder ...ual-machines/image-builder-api-update-release-notes.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation covers Azure VM Image Builder updates for both Linux and Windows VMs. However, in sections providing API usage examples, Windows/PowerShell commands are presented alongside Azure CLI and HTTP, with PowerShell shown last but present. In customization and validation feature lists, Windows-specific tools (PowerShell, Windows Update, Windows restart) are mentioned, but Linux equivalents (Shell, File) are also included. The documentation does not prioritize Windows tools or patterns over Linux, but Windows examples and tools are consistently present, sometimes with more detail (e.g., PowerShell options like 'run elevated, run as system').
Recommendations
  • Ensure Linux and Windows examples are given equal prominence and detail.
  • Where PowerShell examples are provided, also include Bash or Shell script examples for Linux users.
  • If Windows-specific features are described in detail (e.g., PowerShell options), provide comparable detail for Linux features (e.g., shell script execution modes).
  • Consider alternating the order of examples so Linux and Windows are not always in the same sequence.
  • Explicitly note when a feature or example is cross-platform or platform-specific.
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides parity between Windows and Linux throughout most sections, including CLI, REST, and portal instructions. However, in the PowerShell example, Windows is shown first and Linux is only mentioned as a note. Additionally, PowerShell is presented as a primary scripting option, which is more common for Windows users. The CLI examples are Linux-centric, but PowerShell sections could be more balanced. Overall, the bias is minor and does not prevent Linux/macOS users from completing the task.
Recommendations
  • In PowerShell sections, provide Linux examples first or equally, rather than defaulting to Windows.
  • Explicitly show both Linux and Windows values in example code blocks, rather than referencing Linux as a note.
  • Consider adding Bash or shell scripting examples for Linux/macOS users, especially for automation scenarios.
  • Clarify that PowerShell can be used cross-platform, but highlight CLI as the preferred option for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Create and upload a Red Hat Enterprise Linux VHD for use in Azure ...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation covers multiple hypervisors (Hyper-V, KVM, VMware, Kickstart) for preparing a Red Hat Enterprise Linux VHD for Azure. However, Windows/Hyper-V tools and workflows are consistently presented first in each major section, and Windows-centric terminology (e.g., 'Hyper-V Manager', 'convert-vhd cmdlet') is referenced before Linux alternatives. Linux/KVM/VMware instructions are present and detailed, but Windows/Hyper-V is prioritized in ordering and tool mentions.
Recommendations
  • Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, rather than always after.
  • In introductory notes, mention Linux-native tools (e.g., qemu-img, guestfish) equally or before Windows tools (e.g., Hyper-V Manager, convert-vhd).
  • Where conversion tools are discussed, provide Linux command-line alternatives (e.g., qemu-img) in the same breath as Windows/PowerShell tools.
  • Consider a summary table or flowchart at the top showing parity between Windows and Linux workflows for each hypervisor.
  • Avoid language that implies Hyper-V is the default or preferred method for Linux VHD preparation.
GitHub Create Pull Request
Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, the PowerShell section is given equal prominence to the CLI section, and PowerShell is a Windows-centric tool. The CLI example is cross-platform, but the documentation does not explicitly mention Linux/macOS compatibility or alternative tools. The PowerShell example may create friction for Linux/macOS users, as it is not natively available on those platforms without additional installation steps.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Consider mentioning that PowerShell Core is available for Linux/macOS, or clarify that the PowerShell example is primarily for Windows users.
  • Provide links or brief instructions for installing Azure CLI and PowerShell Core on Linux/macOS.
  • If possible, add a note about using Bash or other shell environments for Linux/macOS users.
  • Ensure that CLI examples are shown first, as CLI is more universal across platforms.
GitHub Create Pull Request
Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation covers both Linux and Windows VM images and is generally platform-neutral. However, there are subtle signs of Windows bias: PowerShell examples are often presented alongside or before CLI examples, and references to Windows-specific tools (like Sysprep) appear before Linux equivalents (waagent). Some links and examples reference Windows paths or documentation first. Linux parity is mostly maintained, but Windows tools and patterns are sometimes mentioned first or more prominently.
Recommendations
  • Ensure CLI and PowerShell examples are presented in parallel, with equal prominence.
  • Where possible, alternate the order of Windows and Linux references (e.g., mention waagent before Sysprep in some sections).
  • Add explicit Linux-focused examples or links where only Windows examples are given.
  • Review FAQ and troubleshooting sections to ensure Linux scenarios are equally covered.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (e.g., 'Create zone spanning or zonal scale sets'), PowerShell is listed before Resource Manager templates. There is a slight 'windows_first' bias in the ordering of example methods and in the inclusion of PowerShell examples, which are primarily relevant to Windows users. All CLI examples are cross-platform and there are links to both Linux and Windows ARM template guides, but no explicit Linux/macOS shell examples (e.g., Bash) are provided.
Recommendations
  • Ensure that Azure CLI examples are always listed before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
  • Consider adding explicit Bash shell examples or clarifying that Azure CLI commands work identically on Linux/macOS.
  • Where PowerShell is used, note that it is primarily for Windows users and suggest CLI for Linux/macOS.
  • Review the ordering of sections to avoid subtle 'windows_first' bias (e.g., PowerShell before ARM templates).
GitHub Create Pull Request
Virtual Machines HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs ...main/articles/virtual-machines/hbv3-series-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation generally presents both Linux and Windows as supported platforms for HBv3-series VMs. However, in the 'Software specifications' table, the 'Recommended OS for Performance' is listed as 'Windows Server 2019+' without mentioning any recommended Linux distributions, despite Linux being widely used for HPC workloads. Additionally, the order of OS support in the SRIOV RDMA row lists Linux distributions first, but the explicit recommendation for Windows may create a perception of Windows preference.
Recommendations
  • Add recommended Linux distributions for performance (e.g., RHEL, Ubuntu, SLES) alongside Windows in the 'Recommended OS for Performance' row.
  • Clarify that both Linux and Windows are supported and that the best OS may depend on workload requirements.
  • If Windows is recommended for specific scenarios, specify those scenarios and provide equivalent Linux recommendations where applicable.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance and examples. However, the introduction and overview sections discuss Windows Server 2016 time sync improvements and reference Windows documentation before Linux-specific details, which may create a perception of Windows-first bias. All configuration examples, tools, and commands are Linux-centric, with only a single PowerShell snippet used for base64 encoding cloud-init (which is relevant for Azure users on Windows workstations). No Linux examples are missing, and Linux tools are prioritized throughout.
Recommendations
  • Move Windows Server 2016 discussion and references to a background or context section, clarifying that Azure infrastructure uses Windows but the focus is Linux VM configuration.
  • Add a brief summary at the start emphasizing that the page is Linux-focused and all examples are for Linux VMs.
  • For the PowerShell base64 example, provide a Linux equivalent (e.g., 'base64 cloud-config.txt') for users preparing cloud-init data on Linux/macOS workstations.
  • Ensure that Linux documentation links are as prominent as Windows links in the 'Next steps' section.
GitHub Create Pull Request