← Back to Dashboard
274
Pages Scanned
114
Pages Flagged
274
Changed Pages
41.6%
% Pages Flagged

Live Progress

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

Scan Information

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

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 274

Files Completed: 274

Problematic Pages

114 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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page focuses exclusively on Windows containers and Windows-specific tooling (e.g., cmd, Windows paths, Windows container images). All examples reference Windows containers, Windows file paths, and Windows commands, with no mention or examples for Linux containers or Linux-compatible initialization patterns. The page assumes familiarity with Windows container development and does not provide Linux alternatives or parity.
Recommendations
  • Add equivalent examples for Linux containers, using Linux-compatible container images (e.g., Ubuntu, Alpine) and shell commands (e.g., bash).
  • Document how Initializer CodePackages can be used in Linux container scenarios, including file paths, volume mounts, and command syntax.
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if not, explicitly state this limitation.
  • If Linux containers are supported, provide a complete ApplicationManifest.xml and ServiceManifest.xml example for Linux containers.
  • Mention Linux container version compatibility considerations if relevant.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on Windows-centric tools, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and instructions reference Windows tools and patterns, with no mention of Linux/macOS equivalents or cross-platform alternatives. Linux users are not provided with guidance or examples for performing these tasks outside of Windows environments.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST APIs.
  • Include guidance for configuring upgrade parameters and health policies on Linux/macOS, or clarify if these tasks are Windows-only.
  • Provide links to Linux/macOS documentation or explicitly state platform limitations if Visual Studio and PowerShell are required.
  • If possible, highlight any available SDKs or tools for Linux/macOS users to manage Service Fabric applications.
GitHub Create Pull Request
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation clearly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and guidance are implicitly Windows-centric. There are no Linux-specific instructions, examples, or parity guidance, and the feature is unavailable on Linux, creating a platform gap.
Recommendations
  • Explicitly highlight the lack of Linux support earlier in the documentation, ideally in the introduction or prerequisites.
  • Provide alternative guidance or links for Linux users, such as how to achieve similar functionality (service discovery, HTTP routing) in Linux Service Fabric clusters, if possible.
  • Add a roadmap or reference to any plans for Linux support, or clarify if this is a permanent limitation.
  • Consider adding a comparison table summarizing feature availability between Windows and Linux clusters for Service Fabric reverse proxy.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
Although the introduction claims Service Fabric clusters run on both Windows Server and Linux, the documentation later states that Linux is not yet supported for standalone clusters. The security and management sections reference Windows-specific features (e.g., Kerberos, group Managed Service Accounts, Windows Active Directory) and do not provide Linux equivalents or guidance. The supported operating systems list is Windows-only, and there are no Linux examples or instructions.
Recommendations
  • Clarify early in the document that standalone clusters are currently Windows-only, to avoid confusion from the initial cross-platform statement.
  • Remove or rephrase statements suggesting Linux support for standalone clusters until it is available.
  • When Linux support becomes available, add Linux-specific instructions, examples, and security guidance.
  • If there are alternative Linux deployment options (e.g., via Azure or containers), link to those resources.
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 focuses on C# and .NET serialization, which is cross-platform, but the 'Next steps' section highlights Windows-centric tools (Visual Studio and PowerShell) for application upgrades, mentioning them before any Linux alternatives. There are no Linux CLI or cross-platform upgrade examples provided, and the recommended serializer is Data Contract, which is historically tied to .NET Framework and Windows, though now supported on .NET Core/.NET 5+.
Recommendations
  • Add examples or links for upgrading applications using Linux/macOS tools, such as Azure CLI or Service Fabric CLI (sfctl).
  • Mention cross-platform editors (e.g., VS Code) alongside Visual Studio.
  • Clarify that PowerShell Core is cross-platform, or provide Bash/CLI equivalents for upgrade steps.
  • Explicitly state that Data Contract serialization is supported on .NET Core/.NET 5+ for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page primarily references Windows custom images and provides PowerShell examples for role assignment, with Windows terminology and patterns appearing before Linux equivalents. While Linux custom images are briefly referenced, Windows is emphasized throughout, and Linux-specific examples or CLI commands are missing.
Recommendations
  • Provide explicit examples and instructions for deploying Linux custom images on Service Fabric Managed Clusters.
  • Include Azure CLI commands alongside PowerShell examples for role assignments and image management.
  • Clarify parity between Windows and Linux image support, including any limitations or differences.
  • Ensure Linux terminology and references are given equal prominence, not just as links.
GitHub Create Pull Request
Service Fabric Deploy and upgrade with Azure Resource Manager ...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell-only examples for removing Service Fabric resources and references PowerShell before cross-platform tools like the Service Fabric CLI. There are no CLI or REST API examples for Linux/macOS users, and PowerShell is presented as the primary automation method, which may create friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI and Service Fabric CLI examples for resource removal and management tasks, especially where PowerShell is currently the only example.
  • When referencing tools, mention cross-platform options (e.g., Service Fabric CLI, Azure CLI) before or alongside PowerShell.
  • Provide REST API examples with curl or HTTPie for tasks like deleting resources, to support users on all platforms.
  • Clarify in each section which tools are cross-platform and which are Windows-only.
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 examples for encrypting secrets, but Windows/PowerShell examples are often presented first and in greater detail. Windows-specific tools (e.g., Windows Defender, PowerShell commands) are mentioned exclusively, and Windows security baselines are discussed without Linux equivalents. Some sections, such as Windows Defender and security baselines, are Windows-only by nature, but overall, Linux parity could be improved in several areas.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which comes first to avoid implicit prioritization.
  • Where Windows-specific tools are discussed (e.g., Windows Defender, security baselines), add equivalent Linux guidance (e.g., recommend Linux security baselines, discuss common Linux antivirus solutions, or clarify if none are required).
  • Expand Linux-specific instructions for certificate management and secret encryption to match the detail provided for Windows.
  • Clarify when a feature or section is Windows-only to reduce confusion for Linux users.
  • Add links or references to Linux documentation for security best practices where possible.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation prioritizes Windows-centric tools (PowerShell, Visual Studio) in both structure and detail. PowerShell and Visual Studio are discussed first and in greater depth, with parameter tables and examples tailored to these tools. Linux/macOS-friendly tools (SFCTL/CLI) are covered later and less prominently. There are no explicit Linux/macOS command-line examples or screenshots, and the CLI section is less detailed in terms of real-world usage patterns.
Recommendations
  • Reorganize the documentation to present SFCTL (Service Fabric CLI) on equal footing with PowerShell and Visual Studio, or consider leading with SFCTL as it is cross-platform.
  • Provide explicit SFCTL command-line examples for common upgrade scenarios, similar to the PowerShell examples.
  • Include Linux/macOS-specific notes or screenshots where appropriate, especially for CLI usage.
  • Clarify in parameter tables which options are available for each tool, and ensure parity in explanation and detail.
  • Consider adding a summary table at the top comparing PowerShell, Visual Studio, and SFCTL approaches, with links to detailed sections.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed guidance on managing certificates in Azure Service Fabric clusters, with a strong focus on Azure-native mechanisms and Windows-centric tooling. PowerShell is the only scripting example provided for certificate enrollment, and references to the Key Vault VM extension are explicitly for Windows. There are no Linux-specific examples, nor is there mention of Linux-compatible provisioning agents or cross-platform scripting alternatives.
Recommendations
  • Provide equivalent CLI or Bash examples for certificate enrollment and management, such as using Azure CLI or REST API calls, in addition to PowerShell.
  • Clarify whether the Key Vault VM extension is available for Linux VMs, and if not, mention Linux-compatible alternatives (e.g., Key Vault secrets extension for Linux, or custom scripts).
  • Explicitly state any platform limitations for provisioning agents and extensions, and provide guidance for Linux-based Service Fabric clusters if supported.
  • Where JSON ARM templates are used, add notes or examples highlighting any OS-specific settings or differences.
  • In troubleshooting and FAQ sections, include Linux/macOS command-line examples where possible.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for Service Fabric application upgrade demonstrates a notable Windows bias. PowerShell is the only CLI example provided, and Windows-specific tools (like PowerShell cmdlets and references to http.sys) are mentioned exclusively. There are no Linux or cross-platform CLI examples (such as Azure CLI, REST API, or Service Fabric CLI), and Windows terminology appears first or exclusively in several sections. This creates friction for Linux/macOS users, who may not be able to follow the instructions directly.
Recommendations
  • Add equivalent Linux/macOS examples using Service Fabric CLI (sfctl), Azure CLI, or REST API for application upgrade operations.
  • Clarify which steps are Windows-only and provide cross-platform alternatives where possible.
  • Mention Linux-specific considerations, such as differences in certificate handling (since http.sys is Windows-specific), and provide guidance for Linux clusters.
  • Reorder or balance examples so that Windows and Linux approaches are presented equally.
  • Link to documentation for Linux clusters and cross-platform tooling.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there are several instances where Windows-specific tools, services, and examples are mentioned first or exclusively, such as references to PowerShell cmdlets, Windows services (FabricHost.exe), and standalone cluster creation only for Windows. Linux equivalents are sometimes mentioned later or not at all, and some sections lack Linux-specific guidance or examples.
Recommendations
  • Ensure Linux examples and tools (such as Bash, Linux CLI usage, and Linux-specific cluster creation) are presented alongside or before Windows examples where applicable.
  • Clarify when features are Windows-only and provide alternative guidance or links for Linux users.
  • Add explicit instructions or links for Linux cluster creation and management, or clearly state limitations.
  • Balance references to PowerShell with Bash/CLI equivalents for Linux users.
  • Highlight Linux support in programming models and deployment scenarios more prominently.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides only PowerShell-based deployment examples and command snippets, with no mention of Azure CLI or Bash equivalents. Windows tools and patterns (such as RDP and PowerShell) are referenced exclusively or before any Linux alternatives. There are no Linux/macOS-specific instructions or examples, which creates friction for non-Windows users deploying Service Fabric clusters with Azure networking features.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps.
  • Include Bash shell snippets for Linux/macOS users where relevant.
  • Mention SSH as a secure jump box alternative to RDP for accessing VMs in the virtual network.
  • Clarify that Service Fabric clusters can be managed and deployed from Linux/macOS as well as Windows, and provide links or references to cross-platform tooling.
  • Where PowerShell is used, note that equivalent steps can be performed with Azure CLI or ARM templates from any OS.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates notable Windows bias. All deployment, upgrade, and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any Azure CLI or Bash equivalents. Application packaging is described via Visual Studio, a Windows-centric tool, with no mention of cross-platform alternatives. No Linux/macOS-specific instructions or examples are provided, and Windows tools are referenced first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion tasks alongside PowerShell.
  • Include instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF tooling) instead of only Visual Studio.
  • Mention how Linux/macOS users can perform equivalent actions, including uploading packages and managing resources.
  • Consider providing Bash scripts or referencing Azure Cloud Shell for cross-platform parity.
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 HTTP.sys (Windows-only) and Kestrel (cross-platform) web servers for ASP.NET Core integration with Azure Service Fabric Reliable Services. However, Windows-specific tools and patterns (such as HTTP.sys, netsh, and Windows HTTP Server API) are described in detail, often before their Linux equivalents or alternatives. There are explicit notes about HTTP.sys being Windows-only, but Linux/macOS users are not given equivalent examples or troubleshooting guidance for non-Windows environments. Kestrel is described as the preferred cross-platform option, but Linux-specific considerations (such as firewall configuration, service manifest setup, or troubleshooting) are not addressed. Additionally, some example code and configuration steps are presented with Windows-centric assumptions (e.g., endpoint registration, port sharing), and Visual Studio debugging is referenced as a next step without mention of Linux/macOS alternatives.
Recommendations
  • Add explicit Linux/macOS guidance for Service Fabric development and deployment, including example commands and troubleshooting steps.
  • Provide parity in example code and configuration instructions for Linux environments (e.g., how to configure firewall rules, manage ports, and debug applications on Linux).
  • Mention cross-platform development tools (such as VS Code or CLI-based debugging) alongside Visual Studio.
  • Clarify any differences in Service Fabric setup, deployment, and runtime behavior between Windows and Linux, especially for Kestrel.
  • Include links or references to Linux/macOS-specific documentation for Service Fabric and ASP.NET Core.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI or scripting examples. Windows tools (PowerShell, Visual Studio) are referenced for service configuration, while Linux-specific guidance is limited. The Linux support section is brief and highlights limitations, but does not provide parity in walkthroughs or examples for Linux users.
Recommendations
  • Add Linux CLI (e.g., Azure CLI, Bash) examples for configuring DNS service and setting DNS names.
  • Include instructions for editing service manifests and deploying on Linux clusters using common Linux tools.
  • Clarify how Linux users can accomplish tasks that are shown with PowerShell or Visual Studio, possibly referencing cross-platform tools or alternatives.
  • Expand the Linux section to provide step-by-step guidance for containerized services, including how to enable DNS service without the portal.
  • Where possible, present Linux and Windows examples side-by-side, or indicate which steps are platform-specific.
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 and retrieving the cluster manifest. It also mentions Visual Studio (a Windows-centric tool) for publishing to Azure. While Service Fabric is cross-platform, the documentation leans towards Windows tools and patterns, with PowerShell and Visual Studio mentioned before alternatives. There are no explicit Linux/macOS command examples or references to cross-platform CLI tools.
Recommendations
  • Add examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and can be used on Linux/macOS.
  • Mention and provide sample commands for retrieving cluster manifests using REST API or .NET Core (not just .NET Framework), highlighting their cross-platform compatibility.
  • Include guidance for Linux/macOS users, such as how to configure and verify ImageStoreConnectionString using non-Windows tools.
  • Balance references to Visual Studio with alternatives like VS Code or command-line deployment methods.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation is focused on Linux VMs and provides comprehensive Azure CLI examples, but PowerShell examples are given equal or greater prominence and detail. Several PowerShell commands reference Windows-specific tools and patterns (e.g., ipconfig, .ps1 scripts, Windows-specific parameter passing, and 'Secondary Logon' service), sometimes without clear Linux alternatives. REST and ARM template examples occasionally use Windows script syntax (.ps1) or Windows-centric command IDs. Some notes and explanations are written from a Windows perspective, and PowerShell is presented as a primary tool for Linux VM management, which may not align with typical Linux administrator workflows.
Recommendations
  • Ensure all PowerShell examples referencing Windows-specific tools (e.g., ipconfig, .ps1 scripts) are clearly marked as Windows-only or provide Linux equivalents (e.g., ifconfig, .sh scripts).
  • Where parameter passing differs between Windows and Linux, clarify the Linux-specific behavior and provide explicit Linux shell script examples.
  • In REST and ARM template examples, use Linux shell script syntax (.sh) and Linux command IDs where appropriate.
  • Present Azure CLI examples before PowerShell, as CLI is more commonly used by Linux administrators.
  • Remove or minimize references to Windows-only services (e.g., 'Secondary Logon') in Linux-focused documentation, or clearly state their relevance.
  • Add more Linux-native troubleshooting and scripting examples, such as bash scripts, and highlight Linux-specific best practices.
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 command-line examples exclusively using Azure PowerShell cmdlets, with no mention of Azure CLI or Bash scripting alternatives. This creates friction for Linux and macOS users who may prefer or require cross-platform tools. Additionally, the documentation refers to Windows-centric concepts such as drive letters (e.g., 'S', 'C', 'D'), which are not applicable to Linux environments, without clarifying their relevance or providing Linux equivalents.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (adding, removing, scaling node types, etc.), as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Where drive letters are discussed, clarify that this is a Windows-specific concept and explain how disk mounting works for Linux-based node types, or note if only Windows OS images are supported.
  • Explicitly state OS support (Windows/Linux) for node types and features where relevant, and provide examples for both if supported.
  • Consider adding Bash script examples for ARM template deployments, or reference the Azure CLI documentation for template deployment.
  • If certain operations are only possible with PowerShell or on Windows, clearly call this out to set expectations for non-Windows users.
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 other cross-platform tools. While Azure CLI and ARM/Bicep are referenced in the utility table, actionable examples and guidance are PowerShell-heavy, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit Azure CLI examples alongside PowerShell examples for key actions (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Mention Azure CLI before or alongside PowerShell in best practices sections to reinforce cross-platform parity.
  • Clarify that Azure CLI and ARM/Bicep are fully supported and provide links to relevant CLI documentation for Service Fabric managed clusters.
  • Consider including sample commands for both PowerShell and CLI where possible.
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_first ⚠ī¸ windows_tools
Summary
The documentation provides extensive PowerShell-based migration steps and examples, especially for the Basic SKU migration scenario. PowerShell commands and Windows-centric paths (e.g., 'D:\\SvcFab') are used exclusively, with no equivalent Bash, Azure CLI, or Linux/macOS-friendly instructions. Sample templates and migration walkthroughs are often Windows-focused, and Windows tooling (PowerShell, Windows paths) is presented first or exclusively, even though Service Fabric supports Linux node types.
Recommendations
  • Provide Azure CLI or Bash equivalents for all PowerShell commands, especially for resource deployment, node disabling, and DNS updates.
  • Include Linux/macOS-friendly instructions and examples, such as using Azure CLI or REST API for cluster management.
  • Ensure sample templates and walkthroughs reference both Windows and Linux node types (e.g., include Ubuntu examples alongside Windows).
  • Clarify which steps are OS-agnostic and which are Windows-specific, and offer 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 terminology and tools (e.g., certificate store paths like 'LocalMachine\My', references to Win32 CryptoAPI, and event log channels) are mentioned first or exclusively, with Linux equivalents only briefly referenced (e.g., 'var/lib/sfcerts'). Troubleshooting guidance and error codes are Windows-centric, and there are no Linux-specific examples or troubleshooting steps. This creates friction for Linux users, though most concepts are cross-platform.
Recommendations
  • Provide Linux-specific certificate store paths, commands, and troubleshooting steps alongside Windows examples.
  • Include Linux error codes and log locations relevant to Service Fabric clusters.
  • Clarify when instructions or examples are Windows-only, and offer Linux alternatives where possible.
  • Expand troubleshooting guidance to address Linux scenarios, such as certificate permissions and storage.
  • Ensure parity in example ordering (e.g., mention Linux paths/tools before or alongside Windows ones).
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) exclusively in the 'ContainerImagesToSkip' setting, and provides examples that focus on Windows images. There are no Linux container image examples or explicit mention of Linux container management, despite Service Fabric supporting both Windows and Linux containers. The documentation does not provide parity for Linux users in terms of examples or guidance.
Recommendations
  • Add examples of Linux container images (e.g., 'docker.io/library/alpine', 'mcr.microsoft.com/dotnet/runtime') in the 'ContainerImagesToSkip' setting and elsewhere.
  • Clarify that the cleanup and management settings apply to both Windows and Linux containers, if applicable.
  • Provide guidance or notes for Linux-specific scenarios, such as differences in image management or cleanup behavior.
  • Ensure that descriptions and examples are inclusive of both Windows and Linux container images.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a GUI tool typically used on Windows). No Linux or cross-platform CLI examples are given, and Windows tools/patterns are mentioned first or exclusively.
Recommendations
  • Add equivalent Linux/macOS command-line examples using Azure CLI or REST API if available.
  • Clarify whether Service Fabric Explorer is accessible cross-platform or provide alternatives for Linux users.
  • Mention any prerequisites or limitations for Linux/macOS users when performing cluster operations.
  • If PowerShell is required, note how Linux/macOS users can install and use PowerShell Core.
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) for resource management tasks. While the 'az resource' CLI is mentioned once, PowerShell examples and terminology are prioritized, which may create friction for Linux/macOS users who typically use the Azure CLI or ARM templates. No Linux-specific examples or explicit cross-platform guidance is provided.
Recommendations
  • Include Azure CLI equivalents for all PowerShell cmdlet examples, especially for resource deletion and creation.
  • Explicitly mention that ARM templates and Azure CLI are cross-platform and suitable for Linux/macOS users.
  • Provide links to Azure CLI documentation alongside PowerShell links.
  • Clarify that Az PowerShell cmdlets are Windows-centric and suggest alternatives for non-Windows environments.
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 instances where Windows tools and patterns (such as EventStore APIs, Event Log/Event Viewer, Diagnostics Agent) are mentioned first or exclusively, with Linux equivalents referenced later or less prominently. Some examples and tutorials focus on .NET/Windows, and Linux-specific guidance is often relegated to links or brief notes. There are missing Linux-specific examples for some monitoring scenarios, and Windows-centric terminology (ETW, Event Log) is used without always providing Linux alternatives (LTTng, Syslog) in equal detail.
Recommendations
  • Provide Linux-specific examples and walkthroughs for key monitoring scenarios, especially where Windows tools (EventStore APIs, Event Log, Diagnostics Agent) are highlighted.
  • Ensure Linux equivalents (LTTng, Syslog, Azure Monitor agent configuration) are described with equal prominence and detail, not just referenced via links.
  • Add sample code or configuration snippets for Linux clusters where Windows/PowerShell examples are given.
  • Where possible, present cross-platform instructions or note differences clearly, rather than defaulting to Windows-first explanations.
  • Include more explicit guidance for monitoring .NET Core applications on Linux, not just .NET Framework/.NET on Windows.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation contains a notable Windows bias in its guidance for authoring Service Fabric manifest files. It explicitly recommends opening the ServiceFabricServiceModel.xsd schema in Visual Studio at a Windows file path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\...), which is only valid on Windows. No equivalent instructions or file paths are provided for Linux/macOS users, nor are cross-platform XML editors or schema validation tools mentioned. Additionally, PowerShell is referenced as a way to create service instances, with no mention of cross-platform alternatives.
Recommendations
  • Provide instructions or file paths for accessing the ServiceFabricServiceModel.xsd schema on Linux/macOS, or clarify if it is not available.
  • Mention cross-platform XML editors (such as VS Code with XML extensions) and how to load the schema for IntelliSense and validation.
  • When referencing PowerShell for service creation, also mention cross-platform tools (such as Azure CLI or Service Fabric CLI) and provide example commands.
  • Review the documentation for other implicit Windows-first assumptions and add Linux/macOS guidance where applicable.
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 frequently references PowerShell cmdlets and Windows-centric tools for Service Fabric application lifecycle management, often listing them before or alongside REST and .NET API methods. There is minimal mention of Linux-specific CLI tools (e.g., sfctl), and no explicit Linux command examples are provided. The bias is most evident in deployment, upgrade, and cleanup sections, where PowerShell is the primary scripting interface discussed.
Recommendations
  • Add explicit examples using sfctl (Service Fabric CLI) for Linux/macOS users in each lifecycle phase, especially for deployment, upgrade, and removal.
  • Where PowerShell cmdlets are mentioned, also provide equivalent sfctl or Azure CLI commands.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right interface.
  • Consider restructuring lists so REST, sfctl, and PowerShell are presented in parallel, not always with PowerShell first.
  • Add notes or links to Linux/macOS-specific guidance for Service Fabric operations.
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 the primary example for management operations, and references Windows security as a transport option before X509 certificates. No Linux-specific tools or examples (such as Bash, CLI, or Linux security mechanisms) are provided, and PowerShell is presented as the default management interface.
Recommendations
  • Add examples or references to Azure CLI or Bash scripts for management operations alongside PowerShell.
  • Mention Linux-compatible security mechanisms (such as OpenSSL or SSH) in the transport subsystem discussion.
  • Clarify that Service Fabric management can be performed from Linux/macOS using REST APIs or Azure CLI, not just PowerShell.
  • Ensure parity in documentation by listing cross-platform tools and interfaces before or alongside Windows-specific ones.
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 ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no Linux/macOS CLI or scripting equivalents. All command-line instructions use PowerShell cmdlets, which are native to Windows. There is no mention of cross-platform tools (such as Azure CLI, REST API, or Bash scripts) that Linux/macOS users could use to perform equivalent operations.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlet operations, if supported.
  • Mention and provide REST API examples for managing Application Groups, especially for users on Linux/macOS.
  • Clarify whether PowerShell cmdlets can be used via PowerShell Core on Linux/macOS, or if they are Windows-only.
  • Include Bash or shell script examples where possible.
  • Explicitly state platform requirements for the PowerShell examples, and link to cross-platform alternatives if available.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a notable Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set, exit), and reference Windows container compatibility. Query instructions are given only for PowerShell and C#, with no mention of Linux/macOS equivalents or CLI tools. There are no examples for Linux containers or Linux shell commands, and Windows terminology is used throughout.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu images) and Linux shell commands (bash, echo, ping, exit).
  • Clarify whether RunToCompletion semantics are supported for Linux containers and guest executables, and provide guidance if so.
  • Include instructions for querying deployment status using Azure CLI or Linux shell tools, if available.
  • Balance the documentation by showing both Windows and Linux scenarios, or explicitly state if the feature is Windows-only.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation covers Azure Service Fabric application security in a generally cross-platform manner, but several sections show Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned before or more prominently than Linux equivalents. Some examples and links focus on Windows tools or configurations, and Linux-specific guidance is sometimes missing or relegated to TODO comments.
Recommendations
  • Add Linux-specific examples and guidance where only Windows instructions are given (e.g., disk encryption, user accounts).
  • Ensure parity in mentioning both Windows and Linux options for securing hosting environments, containers, and application data at rest.
  • Where Windows tools (e.g., BitLocker, gMSA) are referenced, provide equivalent Linux solutions (e.g., dm-crypt/LUKS, Linux user/group management) or clarify if no equivalent exists.
  • Remove or resolve TODO comments about Linux features, providing concrete instructions or links.
  • When listing options, alternate or balance Windows and Linux mentions to avoid 'Windows-first' ordering.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides extensive PowerShell examples and references, with no equivalent Linux CLI or cross-platform examples. Windows/PowerShell tools are mentioned exclusively, and there is no guidance for Linux/macOS users on how to perform Service Fabric application upgrades using CLI or REST APIs. The bias is notable, as Linux users may struggle to follow the instructions or complete the tasks without additional research.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlets shown, especially for service creation, upgrades, and parameter updates.
  • Mention and link to REST API documentation for Service Fabric management tasks, which are cross-platform.
  • Clarify which PowerShell cmdlets are available on Linux/macOS (via PowerShell Core), and provide guidance for users on those platforms.
  • Provide sample scripts or commands for Linux users, or explicitly state if certain tasks are Windows-only.
  • Reorganize sections to present cross-platform options first, or in parallel, rather than Windows/PowerShell exclusively.
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 is heavily focused on PowerShell for all CLI examples, including REST API calls, and exclusively references the Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI, curl), nor is there mention of cross-platform tools. This creates friction for non-Windows users, as Service Fabric clusters can be managed from Linux/macOS but the documentation does not provide parity.
Recommendations
  • Add Bash/curl examples for REST API calls alongside PowerShell examples.
  • Mention Azure CLI equivalents if available, or clarify if only PowerShell is supported.
  • Document any prerequisites or limitations for Linux/macOS users (e.g., certificate handling, authentication).
  • Reference cross-platform tools or SDKs where possible.
  • Explicitly state if certain modules (e.g., Microsoft.ServiceFabric.Powershell.Http) are Windows-only, and provide alternatives or workarounds.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page is generally platform-neutral, but the 'File share' backup storage section exclusively references Windows file share paths (\\StorageServer\BackupStore) and Integrated Windows Authentication, without mentioning Linux-compatible alternatives or SMB mounting instructions for Linux. Windows authentication patterns are described first and in detail, while Linux or cross-platform approaches are missing.
Recommendations
  • Add examples or guidance for configuring file share backup storage using SMB mounts on Linux clusters, including sample paths and authentication methods.
  • Clarify whether Linux-based Service Fabric clusters can use file share backup storage, and if so, provide parity instructions for Linux authentication and mounting.
  • Mention cross-platform alternatives (such as NFS or Azure Files with Linux) if supported.
  • Explicitly state any limitations or requirements for Windows-only file share backup storage, so Linux/macOS users are aware.
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 instructions using PowerShell modules and cmdlets. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools to interact with the REST API. The PowerShell module installation and usage instructions are presented first and exclusively, creating friction for non-Windows users.
Recommendations
  • Add Bash/curl examples for REST API calls, showing how Linux/macOS users can trigger backups and track progress.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all operations, or if REST API calls can be made directly from any platform.
  • Provide guidance on authenticating and connecting to Service Fabric clusters from Linux/macOS, including certificate handling.
  • Explicitly state platform requirements or limitations if any features are Windows-only.
  • Consider including cross-platform CLI tools (e.g., Azure CLI) if available for Service Fabric backup operations.
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 manual scaling instructions that rely exclusively on PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning or providing equivalent Linux/bash/CLI commands. There are no bash, Azure CLI, or cross-platform alternatives shown for these critical operations, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for all PowerShell commands used in scaling operations.
  • Explicitly mention if certain operations can only be performed via PowerShell, and suggest alternatives or workarounds for Linux/macOS users.
  • Add bash or cross-platform scripting examples where possible, especially for cluster management tasks.
  • Clarify in each section whether the instructions are valid for both Windows and Linux clusters, or if there are differences.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides some evidence of Windows bias. The 'dataPath' example in the extension snippet uses a Windows-style path (D:\\SvcFab) without a Linux equivalent. The 'Next steps' section links to PowerShell scripts for changing RDP port ranges and admin credentials, which are Windows-centric tasks and tools, and does not mention Linux/SSH equivalents or guidance. While the extension snippet does mention both 'ServiceFabricLinuxNode' and 'ServiceFabricNode', the practical examples and follow-up tasks are Windows-focused.
Recommendations
  • Provide Linux-style path examples (e.g., /var/lib/sf) alongside Windows paths in the extension snippet.
  • Include or link to Linux/SSH-based instructions for remote connection, port management, and credential changes in the 'Next steps' section.
  • Clarify when instructions or scripts are Windows-only, and offer Linux alternatives where possible.
  • Balance PowerShell/Windows tool references with Bash/SSH/Linux tool equivalents.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides code samples for placement policies in C# and PowerShell, but does not include equivalent examples for Linux/macOS environments (e.g., Bash, CLI, or REST API). PowerShell is a Windows-centric tool and is presented as the primary scripting method for service configuration, 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 or REST API examples for configuring placement policies, as these are cross-platform and accessible from Linux/macOS.
  • Explicitly mention whether PowerShell examples are usable on Linux (via PowerShell Core), or provide Bash scripts if possible.
  • Clarify any platform-specific requirements for Service Fabric management tools, and link to documentation for Linux/macOS users.
  • Consider including a table or section comparing Windows and Linux management approaches 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 example code for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. PowerShell is shown as the only scripting interface, and there is no mention of Linux-native tools or commands. While Service Fabric supports Linux containers, the documentation does not demonstrate how Linux users can configure auto scaling from the command line, creating friction for non-Windows users.
Recommendations
  • Add Bash or Azure CLI examples for configuring scaling policies, especially for Linux-based clusters.
  • Mention cross-platform tools (e.g., Azure CLI, REST API) where applicable, and provide links or examples.
  • Clarify which PowerShell commands are available via Azure CLI or REST API for Linux users.
  • Explicitly note any limitations or differences for Linux clusters in relevant sections.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and detailed usage, while Linux-native alternatives (like Bash scripting or Linux-specific deployment steps) are not shown. For cluster upgrades, only PowerShell commands are provided, with no Linux equivalent (e.g., Bash or sfctl). Windows-specific configuration (such as registry keys and Windows Update settings) is discussed in detail, while Linux equivalents are not mentioned or are missing. In several sections, Windows tools and patterns are discussed before or instead of Linux options.
Recommendations
  • Provide Linux-native command examples (e.g., Bash scripts, sfctl usage) alongside PowerShell for cluster management and upgrades.
  • Include Linux-specific configuration guidance for patch management and OS upgrades, such as disabling unattended-upgrades or equivalent settings.
  • When referencing registry keys or Windows Update settings, add parallel instructions for Linux (if applicable), or clarify when a step is Windows-only.
  • Balance the order of presentation so that Linux and Windows examples are given equal prominence.
  • Where only Windows instructions are possible, explicitly state that the step is Windows-only and provide links to Linux documentation if available.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux guidance for Azure Service Fabric networking, but there are several areas where Windows bias is evident. PowerShell and Windows tools are referenced more frequently and often appear first. Some examples and links (e.g., ARM templates, network configuration, DevOps tasks) are Windows-centric or reference Windows-specific tooling before Linux equivalents. The Client API port is described as 'used by PowerShell', and Azure DevOps classic tasks are discussed primarily in a Windows context. However, Linux support is acknowledged and included in key sections.
Recommendations
  • Provide Linux CLI examples alongside PowerShell examples wherever possible, especially for cluster management and networking tasks.
  • When referencing ARM templates or sample clusters, include links to Linux-focused templates in addition to Windows ones.
  • Clarify when guidance applies equally to both Windows and Linux, and avoid phrasing that implies Windows is the default (e.g., 'Client API used by PowerShell' should mention Linux CLI usage as well).
  • Ensure DevOps and operational guidance includes Linux agent/task scenarios, not just classic PowerShell tasks.
  • When listing tools (e.g., reverse proxy), mention Linux-native options and usage patterns explicitly.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page lists Service Fabric cluster settings in a platform-neutral way, but there are several signs of Windows bias. Windows terminology (e.g., 'certificate store', 'MY', 'LocalMachine'), Windows-specific defaults, and references to Windows tools (such as NTLM authentication, Windows Defender Firewall, and Windows log paths) appear throughout. Where Linux equivalents exist, they are sometimes mentioned second or not at all. Some settings are described as 'Windows only' without Linux alternatives or guidance. There are no explicit Linux/macOS configuration examples or clarifications for cross-platform differences, which may create friction for non-Windows users.
Recommendations
  • For each setting that references Windows-specific concepts (e.g., certificate stores, NTLM, log paths), add Linux/macOS equivalents or clarify if the setting is not applicable.
  • Where settings are 'Windows only', explicitly state Linux/macOS alternatives or limitations.
  • Provide Linux/macOS configuration examples, especially for certificate management, log locations, and firewall settings.
  • Review default values and descriptions to ensure Linux defaults are documented equally.
  • Add a summary table or section highlighting platform-specific differences for key settings.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Windows-specific (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json) configuration examples. However, Windows-centric formats and tools (ClusterManifest.xml, PowerShell) are presented first and more frequently, with PowerShell examples given for service creation and updates, while Linux/macOS equivalents (such as CLI or REST API) are missing. The documentation does not mention Linux-specific tools or patterns, nor does it provide parity for Linux/macOS users in command-line examples.
Recommendations
  • Add Azure CLI or REST API examples for service creation and updates, alongside PowerShell.
  • Clarify which configuration files and formats are used for Linux/macOS standalone deployments (e.g., ClusterConfig.json vs ClusterManifest.xml).
  • Explicitly mention Linux/macOS support and any differences in cluster setup or management.
  • Provide links or references to Linux/macOS-specific documentation or tooling where applicable.
  • Ensure that example order alternates or is balanced between Windows and Linux/macOS formats.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides PowerShell and C# examples for configuring Service Fabric MoveCost, but does not include equivalent Linux/Unix shell (e.g., Bash/CLI) examples or mention cross-platform tools. PowerShell is Windows-centric, and the lack of Azure CLI or REST API examples creates friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for creating and updating Service Fabric services with MoveCost, if supported.
  • Mention REST API options for MoveCost configuration, if available, and provide example requests.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., with PowerShell Core on Linux/macOS), or provide Bash equivalents if possible.
  • Explicitly state if certain operations are only possible via PowerShell or C# SDK, and suggest alternatives for non-Windows 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 ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for managing node tags and service requirements, but does not offer equivalent Linux/bash/CLI examples. PowerShell is primarily a Windows tool, and its prominence, along with the lack of Linux-specific instructions, creates friction for Linux users managing Service Fabric clusters. The C# API examples are platform-neutral, but operational/command-line guidance is Windows-centric.
Recommendations
  • Add Azure CLI or bash examples for node tag management and service configuration, if supported.
  • Explicitly mention whether PowerShell commands can be run cross-platform (e.g., PowerShell Core on Linux/macOS), or provide alternatives for Linux users.
  • Clarify any limitations or differences for Linux-hosted Service Fabric clusters regarding node tag management.
  • Consider including REST API examples, which are platform-agnostic, for operational tasks.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters shows Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. There are no Linux-specific examples, tools, or instructions provided, and the guidance assumes the use of Windows tooling for cluster management.
Recommendations
  • Add equivalent Linux/Unix instructions for querying and updating cluster manifests, such as using Service Fabric CLI (sfctl) or REST APIs.
  • Include examples for scaling clusters managed on Linux hosts, if supported.
  • Clarify whether standalone Service Fabric clusters can be managed from Linux, and if not, explicitly state Windows-only limitations.
  • Provide links to Linux-specific documentation or note the absence of Linux support if applicable.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for securing an Azure Service Fabric cluster exhibits moderate Windows bias. While it acknowledges that Service Fabric clusters can run on both Windows and Linux, the majority of security configuration examples, links, and recommendations are focused on Windows Server clusters. Windows security (Kerberos) and Windows certificate services are discussed in detail, with explicit links to Windows-specific guides. There is a lack of equivalent guidance, examples, or references for Linux-based standalone clusters, and Linux-specific certificate creation or security patterns are not mentioned. The concept section briefly states that secure clusters are the same for Linux and Windows, but practical Linux guidance is missing.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate management and client authentication.
  • Provide Linux-specific examples for certificate creation (e.g., using OpenSSL), installation, and cluster configuration.
  • Mention Linux tools and patterns (such as using systemd, OpenSSL, or Linux account management) where relevant, alongside Windows tools.
  • Ensure parity in recommendations and best practices for Linux environments, not just Windows.
  • Clarify which security features are cross-platform and which are Windows-only, to avoid confusion.
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 (Get-ServiceFabricPartitionHealth) for querying health reports, with no equivalent Linux/CLI example. The example is presented without mention of cross-platform alternatives, and the PowerShell syntax is shown first and exclusively. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform management via CLI and REST APIs, but these are not referenced or exemplified.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Mention REST API options for querying health reports, with example requests.
  • Clarify that PowerShell is one option and provide links or references to cross-platform tools.
  • Where possible, show both Windows and Linux/macOS command examples side by side.
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 primarily in C# and PowerShell, with PowerShell being the only CLI example shown for creating and managing Service Fabric services and metrics. There are no equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI, or REST API), and PowerShell is presented before any alternative tooling. This creates friction for users on non-Windows platforms, as Service Fabric can be run and managed from Linux nodes and cross-platform tools.
Recommendations
  • Add Azure CLI or REST API examples for creating and managing Service Fabric services and metrics, as these are cross-platform and accessible from Linux/macOS.
  • Explicitly mention which PowerShell commands are available via Azure CLI or REST API, and provide links or references.
  • If certain operations are only possible via PowerShell, clarify this limitation and suggest alternatives or workarounds for Linux/macOS users.
  • Consider adding Bash script examples or guidance for Linux environments where applicable.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent Linux/macOS CLI examples (such as Bash or Azure CLI). PowerShell is presented as the primary scripting interface, and no mention is made of cross-platform alternatives or Linux-native tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other interfaces.
Recommendations
  • Add Azure CLI or Bash examples for all PowerShell commands, highlighting cross-platform usage.
  • Explicitly mention whether PowerShell Core (pwsh) is supported on Linux/macOS, and provide guidance if so.
  • Document any REST API or SDK alternatives for configuring service sensitivity, with sample requests.
  • Clarify if Service Fabric management can be performed from Linux/macOS, and link to relevant docs if available.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page primarily references Windows-specific upgrade paths and tools for Azure Service Fabric standalone clusters. Key upgrade and configuration links point to Windows Server-specific guides, and the Patch Orchestration Application is described only for Windows. There are no explicit Linux examples or equivalent Linux upgrade/configuration documentation referenced, despite Service Fabric standalone clusters being supported on both Windows and Linux.
Recommendations
  • Add links and guidance for upgrading Service Fabric standalone clusters on Linux, including relevant configuration and upgrade steps.
  • Mention and describe the Patch Orchestration Application (POA) for Linux, if available, or clarify its absence.
  • Ensure that references to configuration files and upgrade procedures are platform-neutral or provide separate sections/examples for Windows and Linux.
  • Update 'Next steps' and other sections to include Linux-specific documentation where applicable.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides code examples and administrative instructions primarily using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or scripting examples (such as Bash or Azure CLI), nor are Linux-native tools or patterns mentioned. Windows tools (PowerShell cmdlets) are referenced first and exclusively, creating friction for Linux/macOS users who may not have access to PowerShell or prefer other tooling.
Recommendations
  • Add equivalent Linux examples using Bash, Azure CLI, or REST API calls for administrative tasks such as creating/updating services.
  • Mention Linux-native tools and patterns alongside PowerShell, ensuring parity in instructions.
  • Clarify when a PowerShell example is Windows-specific and provide alternative approaches for Linux users.
  • Consider referencing cross-platform tools (e.g., Azure CLI) before or alongside PowerShell.
  • Include notes or links to Linux-specific Service Fabric documentation where relevant.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters and generally avoids platform-specific bias. However, in sections about managing certificates and opening application ports, PowerShell is mentioned alongside Azure CLI, but no explicit Linux/macOS shell examples are shown. Additionally, the 'Patch Orchestration Application' section links only to Windows OS patching documentation, suggesting a Windows-first approach for OS upgrades.
Recommendations
  • Where PowerShell is mentioned, ensure equivalent Bash/Azure CLI examples are provided or clarify cross-platform support.
  • If Patch Orchestration Application supports Linux clusters, add links and guidance for Linux OS patching; otherwise, clarify Windows-only applicability.
  • Explicitly state when a feature or example is Windows-specific to reduce ambiguity for Linux/macOS users.
  • Where possible, provide Azure CLI commands in Bash syntax for Linux/macOS users, especially in certificate and port management sections.
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 primarily references Windows-specific event logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and tools, with no mention of Linux equivalents or examples. Access methods and default configurations are described in a Windows-centric manner, creating friction for Linux cluster administrators.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including supported logging mechanisms and tools.
  • Provide examples or references for monitoring and diagnostics setup on Linux (e.g., using syslog, journald, or other Linux-native logging solutions).
  • Clarify which features or access methods are Windows-only and provide Linux alternatives where available.
  • Ensure parity in documentation by including Linux-specific instructions alongside Windows instructions.
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 detailed conceptual overview of Service Fabric health monitoring, but the only practical example for reporting and evaluating health is given using PowerShell cmdlets. There are no equivalent examples for Linux/macOS users (e.g., REST API, CLI, or SDK usage), and PowerShell is a Windows-centric tool. The documentation mentions REST and FabricClient APIs but does not show how to use them, nor does it provide Linux-friendly command-line or code samples.
Recommendations
  • Add equivalent examples using REST API calls for health reporting and querying, suitable for Linux/macOS users.
  • Include sample code snippets using the Service Fabric SDK in languages/platforms that are cross-platform (e.g., Python, .NET Core).
  • Provide Azure CLI or Bash shell examples where possible.
  • Explicitly mention Linux/macOS support and tools for health reporting and querying.
  • Reorder examples so that Windows and Linux approaches are presented equally, or at least clarify which tools are platform-specific.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page is based on Windows Server 2016 container samples and frequently references Windows-specific patterns (e.g., 'c:\VolumeTest\Data', 'winver' command, Windows build numbers, and Windows certificate stores). Linux equivalents are not provided or are only mentioned in passing. The manifest examples and explanations focus on Windows containers and settings, with no explicit Linux container examples or guidance.
Recommendations
  • Provide equivalent Linux container manifest examples, including Linux file paths and volume mounts.
  • Add instructions for obtaining OS build/version information on Linux (e.g., 'cat /etc/os-release' or 'uname -r') alongside the Windows 'winver' command.
  • Clarify which settings and patterns are Windows-only and which are cross-platform.
  • Include Linux-specific guidance for certificate handling, volume drivers, and image overrides.
  • Reference Linux container samples in addition to the Windows sample repository.
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 references PowerShell for deployment/removal tasks and links to PowerShell-specific modules for downloading service packages. There are no explicit Linux or cross-platform CLI examples, and the 'Next steps' section points users to PowerShell for application deployment/removal, implying Windows as the default environment.
Recommendations
  • Add equivalent examples and links for Linux/macOS users, such as Azure CLI or Service Fabric CLI (sfctl) commands for deploying/removing applications.
  • Clarify in the 'Next steps' section that PowerShell is one option, and provide guidance for Linux/macOS environments.
  • Where PowerShell modules are referenced (e.g., Copy-ServiceFabricServicePackageToNode), mention or link to cross-platform alternatives if available.
  • Review the documentation for any implicit assumptions about Windows environments and update language to be more platform-neutral where possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides conceptual information about Service Fabric hosting models, but operational examples and tooling references are heavily Windows/PowerShell-centric. PowerShell is the only CLI example shown for creating services, and all links to command references are for PowerShell modules. There are no Linux CLI (e.g., Azure CLI, Bash) or cross-platform examples, nor is it clarified how Linux users should perform equivalent tasks.
Recommendations
  • Add Azure CLI examples for service creation and management, highlighting cross-platform usage.
  • Mention or link to Linux-compatible tools and workflows for Service Fabric operations.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide guidance for Linux/macOS users.
  • Include Bash or REST API command examples where possible, especially for critical operations.
  • Reorder examples so that cross-platform options are presented alongside or before Windows-specific ones.
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 Windows/PowerShell tools. PowerShell is mentioned first for application creation, and Visual Studio (a Windows-centric IDE) is referenced for parameter file management. While sfctl (a cross-platform CLI) and Jenkins (cross-platform CI tool) are mentioned, Linux/macOS-specific workflows or examples are not explicitly provided.
Recommendations
  • Add explicit Linux/macOS examples for application creation and parameter passing, such as using sfctl from a Bash shell.
  • Provide sample shell scripts (e.g., install.sh) for Linux/macOS environments alongside PowerShell scripts.
  • Clarify cross-platform support for tools and highlight any differences in workflows between Windows and Linux/macOS.
  • Include references to Linux/macOS-friendly editors or IDEs (such as VS Code) for managing parameter files.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page for Service Fabric reliable services app manifest examples shows mild Windows bias. Windows-specific tools (e.g., 'Setup.bat', '.exe' files, references to 'Administrators' system group, and PowerShell module) are used in examples and explanations. Windows terminology and patterns (such as NETWORKSERVICE, local admin accounts, and console redirection warnings) are prominent, and Windows-centric examples (batch scripts, EXE hosts) are given without Linux equivalents. However, the manifest XML itself is cross-platform, and the page does not explicitly exclude Linux, but Linux-specific guidance is missing.
Recommendations
  • Add Linux-specific examples for service startup scripts (e.g., using shell scripts like 'Setup.sh' instead of 'Setup.bat').
  • Mention Linux equivalents for user/group management (e.g., mapping to Linux system users/groups).
  • Clarify that EXE hosts can be replaced with ELF binaries on Linux, and provide example manifest snippets for Linux deployments.
  • Include instructions or references for deploying and managing Service Fabric applications on Linux clusters, including relevant CLI commands.
  • When referencing PowerShell, also mention Azure CLI or Bash alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides detailed PowerShell examples for reporting health in Service Fabric, including connection and health report commands, but does not offer equivalent Linux/macOS CLI examples (such as Azure CLI or Bash). PowerShell is presented as the primary scripting interface, and Windows-style paths and prompts are used. REST and API methods are mentioned, but scripting and command-line guidance is Windows-centric.
Recommendations
  • Add equivalent examples for Linux/macOS environments using Azure CLI, Bash, or cross-platform tools where possible.
  • Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS and provide examples if so.
  • Mention any limitations or differences for Linux users in Service Fabric health reporting.
  • Reorder sections or add notes to ensure REST and API methods are highlighted as cross-platform options, not secondary to PowerShell.
  • Use neutral prompts and paths in examples (e.g., $ instead of PS C:\>) when possible.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for Replica soft delete in Service Fabric consistently references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links only for PowerShell usage. There is no mention of Linux/macOS equivalents, CLI commands, or cross-platform SDK usage. The documentation assumes familiarity with Windows tooling and does not clarify how Linux users can perform these operations, creating friction for non-Windows users.
Recommendations
  • Add examples for performing replica soft delete and restore operations using cross-platform tools such as Azure CLI, REST API, or .NET Core SDK.
  • Clarify whether the PowerShell APIs are available on Linux/macOS (via PowerShell Core), and provide installation or usage guidance if so.
  • Include explicit instructions or code samples for Linux users, such as using FabricClient APIs in .NET Core or Java.
  • Mention any limitations or differences for Linux clusters, if applicable.
  • Ensure screenshots and command outputs are not exclusively from Windows environments.
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 specific to Windows. Windows file paths and store names (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd', 'MY' certificate store) are mentioned first or exclusively, with Linux equivalents only briefly referenced. Linux deployment methods and CLI examples are missing, and Windows-centric terminology appears throughout.
Recommendations
  • Add equivalent Linux deployment examples using Azure CLI or Service Fabric CLI (sfctl), especially for application parameter overrides.
  • Mention Linux file paths and certificate store locations alongside Windows paths, not only in passing.
  • Clarify when PowerShell commands are Windows-only and provide alternative commands for Linux/macOS users.
  • Ensure that Linux-specific configuration nuances (such as certificate handling and endpoint ACLing) are covered in parity with Windows.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page is generally cross-platform and describes Service Fabric concepts applicable to both Windows and Linux. However, there is a notable Windows bias in the 'Node' section, which describes nodes as having an auto-start Windows service (FabricHost.exe) and references EXE/DLL files as typical code packages. Windows terminology and tools are mentioned first and more prominently, while Linux equivalents are not explicitly described. The Linux support is acknowledged in container and guest executable sections, but lacks parity in technical detail.
Recommendations
  • In the 'Node' section, clarify how node processes are managed on Linux (e.g., systemd, FabricHost process, etc.), not just Windows services.
  • When describing code packages, mention typical Linux executable formats (e.g., ELF binaries) alongside EXE/DLL.
  • Provide explicit examples or descriptions for Linux clusters where relevant, such as how Service Fabric services are started and managed.
  • Ensure that references to Windows-specific tools or terminology are matched with Linux equivalents, or note differences.
  • Consider alternating the order in which Windows and Linux are mentioned to avoid 'windows_first' bias.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented toward Windows development workflows, specifically Visual Studio. All deployment and configuration examples reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish) and Windows-centric tools. PowerShell is mentioned as the CLI for service creation, with no mention of Linux/macOS alternatives or cross-platform CLI tools. There are no examples or guidance for Linux/macOS users, nor is there any indication of how to use StartupServices.xml outside of Visual Studio or on non-Windows platforms.
Recommendations
  • Add explicit guidance for Linux/macOS users, including whether StartupServices.xml is supported outside Visual Studio and how to manage service configurations using cross-platform tools.
  • Provide examples using Azure CLI or Service Fabric CLI (sfctl) for service deployment and configuration, if supported.
  • Clarify any platform limitations for StartupServices.xml, and if it is Windows-only, state this clearly at the top of the documentation.
  • If possible, include instructions for editing and deploying Service Fabric applications from Linux/macOS environments, or link to relevant documentation.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides explicit PowerShell instructions for using the Fault Analysis Service but does not mention or provide examples for Linux/macOS users (e.g., Bash/CLI equivalents). It references the Service Fabric PowerShell module and SDK, which are Windows-centric tools, without discussing cross-platform alternatives or CLI usage.
Recommendations
  • Add examples or instructions for using the Fault Analysis Service from Linux/macOS environments, such as with Azure CLI, Bash scripts, or REST APIs.
  • Clarify whether the Fault Analysis Service APIs are accessible and supported from non-Windows platforms.
  • If PowerShell Core (cross-platform) is supported, specify this and provide relevant examples.
  • Mention any limitations or requirements for Linux/macOS users explicitly, so expectations are clear.
GitHub Create Pull Request
Virtual Machines Deploy a Premium SSD v2 managed disk ...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 disks, but the CLI examples default to Windows VM images (e.g., 'Win2016Datacenter') and use Windows-centric parameters (admin password, username, etc.). PowerShell is featured equally alongside CLI, and all scripts use Windows images by default. There are no explicit Linux VM deployment examples, and the documentation does not mention or show how to deploy or attach Premium SSD v2 disks to Linux VMs, nor does it show Linux-specific parameters or considerations. This creates a subtle but notable Windows bias, especially in the example scripts.
Recommendations
  • Add explicit Linux VM deployment examples using popular Linux images (e.g., Ubuntu, CentOS) in the Azure CLI sections.
  • In CLI scripts, show how to set up SSH authentication for Linux VMs (e.g., using --authentication-type ssh and --ssh-key-values).
  • Clarify in each example that the disk can be attached to both Windows and Linux VMs, and provide at least one Linux-focused walkthrough.
  • When initializing variables in CLI scripts, use a Linux image (e.g., 'UbuntuLTS') as the default or show both Windows and Linux alternatives.
  • Mention any Linux-specific considerations for Premium SSD v2 disks, 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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
While the documentation claims to apply to both Windows and Linux VMs, there are several areas where a Windows bias is evident. PowerShell examples are consistently provided alongside Azure CLI, but there are no Bash or Linux shell script equivalents. In the ARM template section, only Windows images are referenced, and the default parameters and allowed values are exclusively for Windows Server SKUs. The PowerShell tab is always present, but there is no mention of Linux-native scripting tools. In some cases, Windows-centric terminology (e.g., password complexity for 'Administrator account') is used without clarifying Linux differences.
Recommendations
  • In the ARM template section, provide an example or parameter set for deploying a Linux VM (e.g., using Ubuntu or CentOS images) alongside the Windows example.
  • Where PowerShell examples are given, consider adding Bash or shell script equivalents for Linux users, or clarify that Azure CLI commands are cross-platform and can be run in Bash.
  • In sections referencing 'Administrator account' and password requirements, clarify the differences for Linux VMs (e.g., SSH key usage, username restrictions).
  • In the allowed values for OSVersion in ARM templates, include popular Linux distributions or provide a note/link to Linux image references.
  • Review the ordering of examples/tabs to ensure CLI (cross-platform) is presented before PowerShell where possible.
GitHub Create Pull Request
Virtual Machines Deploy a ZRS managed disk ...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying ZRS managed disks, but PowerShell (and Windows-centric tooling) is heavily emphasized. PowerShell examples are extensive and detailed, and Resource Manager template sections use PowerShell for feature registration and deployment. Windows VM images are used in PowerShell examples, while CLI examples use Ubuntu. The order of tabs puts Azure portal first, then CLI, then PowerShell, but PowerShell is given parity and more detail. Feature registration steps are only shown in PowerShell, with no Linux/bash equivalent. Resource Manager template deployment commands are PowerShell-only.
Recommendations
  • Add bash/Linux shell equivalents for feature registration and Resource Manager template deployment (e.g., using Azure CLI or 'az deployment group create').
  • Provide examples for deploying Windows VMs using Azure CLI, and Linux VMs using PowerShell, to show cross-platform parity.
  • Clarify that PowerShell commands can be run on Linux/macOS (with PowerShell Core), or provide explicit bash alternatives.
  • For Resource Manager template sections, show both PowerShell and Azure CLI deployment commands.
  • Where possible, avoid using Windows-specific VM images in PowerShell examples unless demonstrating a Windows-only scenario.
GitHub Create Pull Request
Virtual Machines Ultra Disks for VMs - Azure Managed Disks ...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is intended for both Linux and Windows VMs, but consistently uses Windows-centric examples (e.g., Win2016Datacenter image, password authentication, Windows admin username conventions) in all CLI and PowerShell code blocks. There are no Linux-specific VM image examples, nor guidance for Linux authentication or disk formatting. The Quickstart link in the Portal section points only to Windows VM creation. While the Azure CLI and PowerShell tools are cross-platform, the actual examples are Windows-only, creating friction for Linux users.
Recommendations
  • Provide Linux VM image examples (e.g., Ubuntu, CentOS) alongside Windows examples in CLI and PowerShell sections.
  • Include Linux authentication options (e.g., SSH key authentication) in CLI/PowerShell examples.
  • Add links to Linux VM Quickstart documentation in the Portal section.
  • Mention Linux disk initialization/formatting steps after disk attachment.
  • Alternate Windows and Linux examples, or show both in parallel where possible.
GitHub Create Pull Request
Virtual Machines Azure Write Accelerator ...es/virtual-machines/how-to-enable-write-accelerator.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides extensive Azure PowerShell examples and scripts, with detailed step-by-step instructions for enabling Write Accelerator using PowerShell. Windows-specific tools (Chocolatey, cmd.exe, PowerShell) are referenced for installing armclient, with no mention of Linux/macOS alternatives. The PowerShell section is much more detailed than the Azure CLI section, which is brief and lacks full scripting examples. Windows tools and patterns are mentioned first and more prominently, even though the feature is available for both Linux and Windows VMs.
Recommendations
  • Provide parity in scripting examples for Azure CLI, including full scripts for adding/enabling Write Accelerator on disks, similar to the PowerShell section.
  • Mention and provide installation instructions for armclient on Linux/macOS (e.g., via npm or direct download), not just Chocolatey/Windows.
  • When referencing disk/volume managers, ensure Linux tools (LVM, MDADM) are mentioned equally and provide links to relevant Linux documentation.
  • Consider presenting Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
  • Clarify that all steps and tools are available for both Linux and Windows users, and highlight any OS-specific differences.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment. .../includes/virtual-machines-disks-shared-limitations.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation repeatedly references Windows Server Failover Cluster and links exclusively to Windows-specific clustering requirements. There is no mention of Linux clustering solutions (such as Pacemaker or Corosync), nor any guidance for Linux users. Windows clustering is presented as the only relevant scenario for shared disks, creating a Windows-first bias.
Recommendations
  • Add information about Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility with Azure shared disks.
  • Include links to Linux clustering documentation and requirements.
  • Clarify whether shared disks are supported for Linux clusters, and if so, provide examples or limitations.
  • If Windows Failover Cluster is the only supported scenario, explicitly state this to avoid confusion.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux VHD creation, frequently references Windows-centric tools and workflows (notably Hyper-V and PowerShell's Convert-VHD), presents Windows/Hyper-V as the primary or only detailed method for VHD creation/conversion, and does not provide equivalent Linux-native tooling or workflows for these critical steps. This can create friction for Linux/macOS users attempting to follow the guide.
Recommendations
  • Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, or dd) alongside or before Hyper-V/PowerShell steps.
  • Explicitly mention and provide example commands for extracting and working with VHDs on Linux/macOS, not just in the context of WSL on Windows.
  • Where Hyper-V or Windows tools are referenced, clarify that they are optional and provide parity for users on Linux/macOS.
  • Link to or include references for open-source or cross-platform alternatives for each Windows-specific tool or step.
  • Consider reordering sections so that Linux-native workflows are presented first, or at least in parallel with Windows/Hyper-V approaches.
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-style AzCopy command example ('AzCopy.exe copy "c:\somewhere\mydisk.vhd" "sas-URI" --blob-type PageBlob') and does not offer a Linux/macOS equivalent. The AzCopy CLI example uses Windows path syntax and executable naming, and the Linux/macOS usage (e.g., './azcopy' or '/home/user/mydisk.vhd') is not shown. The documentation otherwise uses Azure CLI commands, which are cross-platform, but the critical upload step is presented only in Windows format.
Recommendations
  • Add a Linux/macOS AzCopy example, such as './azcopy copy "/home/user/mydisk.vhd" "sas-URI" --blob-type PageBlob'.
  • Mention that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
  • Clarify that file paths and executable names differ between Windows and Linux/macOS.
  • Consider showing both Windows and Linux/macOS AzCopy commands side-by-side for parity.
GitHub Create Pull Request
Virtual Machines Verify encryption status for Linux - Azure Disk Encryption ...tual-machines/linux/how-to-verify-encryption-status.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs. However, PowerShell examples are presented before Azure CLI examples, and the PowerShell section is more extensive, with detailed scripts and screenshots. This ordering and emphasis may create friction for Linux users, as PowerShell is not a native tool on most Linux distributions, whereas Azure CLI and Bash are more common. The OS-level section does use Bash commands, but platform-level validation is PowerShell-first.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is more widely used and available on Linux.
  • Expand Azure CLI sections to match the detail and coverage of PowerShell examples, including screenshots and explanations.
  • Clearly indicate that PowerShell is optional and primarily for users who have it installed, while Azure CLI is recommended for Linux environments.
  • Consider adding Bash-only or Python examples for querying Azure APIs, if relevant.
  • Review and ensure parity in explanations and troubleshooting guidance for both CLI and PowerShell sections.
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 frequent and often shown first, especially for checksum generation and image build operations. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents (Shell) are less emphasized. Windows tools and patterns (e.g., Get-FileHash, Sysprep, PowerShell commands) are referenced more often than Linux tools, and Windows terminology appears before Linux in some sections.
Recommendations
  • Where PowerShell examples are given for checksum generation, always provide the Linux/Mac equivalent (e.g., sha256sum) alongside or before the Windows example.
  • Ensure that Linux shell customizer examples are as detailed and prominent as PowerShell customizer examples.
  • When describing image build operations (start/cancel), show Azure CLI examples first or equally with PowerShell, since Azure CLI is cross-platform.
  • For sections describing Windows-specific customizers (WindowsRestart, WindowsUpdate), explicitly note Linux alternatives or clarify their absence.
  • Balance references to Windows tools (e.g., Get-FileHash, Sysprep) with Linux equivalents (e.g., waagent, sha256sum), and avoid assuming PowerShell as the default for cross-platform tasks.
  • Consider alternating the order of Windows and Linux examples to avoid 'windows_first' bias.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and cross-platform CLI (sfctl) examples for deploying Docker Compose applications to Azure Service Fabric. However, the PowerShell section is presented first and in greater detail, with the CLI section labeled as 'alternative.' This ordering and emphasis may suggest a preference for Windows/PowerShell usage, even though the CLI is cross-platform. No Linux/macOS-specific tools or patterns are missing, and the CLI examples are sufficient for non-Windows users.
Recommendations
  • Present the Service Fabric CLI (sfctl) examples before or alongside the PowerShell examples to emphasize cross-platform support.
  • Explicitly mention that sfctl is cross-platform and suitable for Linux/macOS users.
  • Consider adding a short introductory note clarifying that both PowerShell and sfctl are supported, and users should choose based on their OS.
  • Ensure that any advanced usage or troubleshooting sections include CLI examples, not just PowerShell.
GitHub Create Pull Request
Virtual Machine Scale Sets Spot Placement Score ...les/virtual-machine-scale-sets/spot-placement-score.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides four methods for accessing Spot Placement Score: Azure portal, REST API, Azure CLI, and Azure PowerShell. The PowerShell example is presented last, after CLI and REST API, and all examples are generic and cross-platform. There is no evidence of Windows-specific tools or patterns being prioritized, nor are Linux equivalents missing. However, the inclusion of Azure PowerShell as a method may be considered a minor Windows-first bias, as PowerShell is most commonly used on Windows, though it is available cross-platform.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform (Windows, Linux, macOS) to avoid perception of Windows-only bias.
  • Ensure that CLI and REST API examples are equally detailed and highlighted, as they are the most platform-neutral.
  • Consider adding explicit notes or links for Linux/macOS users, such as installation instructions for Azure CLI and PowerShell on those platforms.
GitHub Create Pull Request
Virtual Machines Best practices for virtual machine cost optimization ...s/virtual-machines/cost-optimization-best-practices.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is generally neutral, but there is a minor bias where Windows-specific guidance appears before Linux equivalents. For example, in the VM selector section, 'Use at least B2 for Windows machines' is mentioned without a corresponding Linux recommendation, and Windows pricing links are listed before Linux. However, Linux is referenced in pricing and VM creation links, and most recommendations are platform-agnostic.
Recommendations
  • Ensure Linux-specific guidance is provided alongside Windows guidance, such as recommended B-Series sizes for Linux VMs.
  • Present Windows and Linux links in parallel or alphabetical order to avoid perceived prioritization.
  • Where possible, clarify when recommendations are platform-specific (e.g., disk types, automation tools) and provide Linux alternatives if applicable.
GitHub Create Pull Request
Virtual Machines Migrate Standard HDD OS disks by September 08, 2028 ...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation covers both Linux and Windows VMs and provides Azure CLI and PowerShell examples for listing affected disks. However, the PowerShell example is mentioned first, which may indicate a minor 'windows_first' bias. Both Linux (Azure CLI) and Windows (PowerShell) tools are referenced, and no critical steps are Windows-only.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side or list Azure CLI first, as it is cross-platform.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Ensure parity in example depth and clarity for both CLI and PowerShell instructions.
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 links and examples for both Azure CLI (Linux-friendly) and Azure PowerShell (Windows-centric), but PowerShell is mentioned first in several sections and the custom RBAC role creation link points only to a PowerShell-based guide. This creates a mild Windows bias, as Linux users may need to search for CLI or ARM template equivalents.
Recommendations
  • Add links or examples for creating custom RBAC roles using Azure CLI or ARM templates, not just PowerShell.
  • Ensure that CLI and PowerShell examples are presented together, or alternate which is shown first.
  • Clarify that all steps can be performed on Linux/macOS using Azure CLI, and provide explicit guidance or links.
  • Where possible, provide parity in documentation for both PowerShell and CLI approaches.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, there is a slight bias toward Windows in some sections: Windows container runtimes are listed in more detail than Linux, IIS lift-and-shift scenarios are highlighted first in the container use cases, and Windows-specific links are sometimes shown before Linux equivalents. Windows tools (IIS, Mirantis Container Runtime, DockerEE) are mentioned with more specificity than Linux tools (only Docker is referenced). Linux examples and tutorials are present and linked, but Windows scenarios are often described first or in greater detail.
Recommendations
  • Ensure Linux container runtimes and tools are described with equal specificity as Windows (e.g., mention containerd or other alternatives if relevant).
  • Present Linux and Windows examples/tutorials in parallel, rather than listing Windows scenarios first.
  • Balance use case examples by including a Linux-specific scenario (e.g., Apache/Nginx lift-and-shift) alongside IIS.
  • Where possible, provide links to Linux container documentation with the same prominence as Windows container links.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. It references Windows file paths (e.g., Service Fabric SDK schema location in C:\Program Files\...), and mentions Visual Studio as a packaging tool, which is primarily Windows-centric. No explicit Linux/macOS examples or equivalent tooling are provided, and the directory structure example uses a Windows executable (.exe). However, the content does not appear to be strictly Windows-only, as Service Fabric supports guest executables of various types (Node.js, Java, C++), and the samples include Node.js. The bias is mostly in the examples and tooling references.
Recommendations
  • Include Linux/macOS equivalents for SDK schema locations and clarify cross-platform support.
  • Provide command-line packaging and deployment examples using cross-platform tools (e.g., Azure CLI, PowerShell Core, Bash).
  • Mention and link to Linux/macOS-compatible editors and tools for manifest editing and packaging.
  • Show example directory structures with non-.exe binaries (e.g., .sh, .out, or generic binaries) to reinforce cross-platform applicability.
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. However, in the 'Any OS, any cloud' section, Windows development (Visual Studio and PowerShell) is mentioned first, followed by Linux development (Eclipse and Yeoman). The quickstart link also points to a .NET-based guide, which may be more Windows-centric, though .NET Core is cross-platform. No exclusive Windows tools or missing Linux examples are present, but Windows is presented before Linux in several places.
Recommendations
  • Alternate the order of Windows and Linux mentions, or present them together to avoid implicit prioritization.
  • Provide quickstart links for both Windows (.NET) and Linux (Java/.NET Core) users, or clarify that .NET Core is cross-platform.
  • Ensure that examples and tooling references for Linux (e.g., command-line, Eclipse, Yeoman) are as prominent as those for Windows (Visual Studio, PowerShell).
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides code examples exclusively in C#, which is common for Azure Service Fabric but does not explicitly show Windows-specific tools or patterns. However, in the 'Next steps' section, Windows-centric upgrade tutorials (Visual Studio and PowerShell) are listed before any Linux/macOS alternatives, and no Linux-specific upgrade guidance is referenced. There are no explicit Linux or cross-platform examples or tooling mentioned.
Recommendations
  • Add references or links to Linux/macOS upgrade tutorials, such as using the Service Fabric CLI (sfctl) or REST APIs.
  • Include examples or notes about running Service Fabric on Linux, if applicable, and clarify any platform-specific differences in serialization.
  • Ensure parity in 'Next steps' by listing Linux/macOS options alongside Windows tools, not after or instead of them.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ minor_windows_tools
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) give PowerShell examples before CLI or in greater detail. There are no Linux-specific shell examples (e.g., Bash), and Windows tools/patterns (PowerShell) are sometimes emphasized. However, Azure CLI is cross-platform and is included throughout, mitigating most bias. No critical networking features are Windows-only, and Linux users can complete all tasks.
Recommendations
  • Present Azure CLI examples before PowerShell to prioritize cross-platform guidance.
  • Ensure all PowerShell examples are matched with equivalent Azure CLI examples.
  • Where possible, include Bash shell scripting examples for Linux users.
  • Explicitly note that Azure CLI works on Linux/macOS/Windows to reassure non-Windows users.
  • Review for any PowerShell-only workflows and add CLI alternatives if missing.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, but PowerShell (a Windows-centric tool) is always presented after CLI and before ARM template examples. There are no Linux-specific examples or mentions of Linux tools (e.g., Bash scripting, cloud-init), and PowerShell is given equal prominence to CLI, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Clearly indicate that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are preferred for Linux/macOS users.
  • Add a note at the start of each section clarifying which tools are cross-platform and which are Windows-only.
  • Consider providing Bash shell scripting examples for common tasks, or referencing how to use Azure CLI in Bash for Linux users.
  • Move PowerShell examples to a separate tab labeled 'Windows PowerShell' to clarify its platform specificity.
  • Add explicit guidance for Linux/macOS users, such as 'For Linux/macOS, use Azure CLI or ARM templates.'
GitHub Create Pull Request
Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for enabling Automatic Zone Balance on Virtual Machine Scale Sets. However, PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and in some sections (such as feature registration), PowerShell is listed after CLI but receives equal prominence. Portal instructions are also included, which are platform-agnostic. There is a minor bias in the PowerShell examples: the Application Health extension is shown as 'ApplicationHealthWindows', while the CLI example uses 'ApplicationHealthLinux', potentially causing confusion for Linux users. The documentation does not omit Linux-compatible instructions, but Windows tools and patterns are given equal or slightly more prominence than Linux equivalents.
Recommendations
  • Clarify when to use 'ApplicationHealthWindows' vs 'ApplicationHealthLinux' in extension examples, and ensure both are shown for cross-platform parity.
  • Explicitly note that Azure PowerShell is available on Linux/macOS (via PowerShell Core), or link to cross-platform installation instructions.
  • Consider listing Azure CLI examples before PowerShell, as CLI is natively cross-platform.
  • Where possible, provide both Linux and Windows extension examples in PowerShell and CLI sections.
  • Add a brief note about the cross-platform nature of Azure CLI and PowerShell to reduce perceived Windows bias.
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all tasks, with the Azure CLI (cross-platform) example always shown before the PowerShell (Windows-centric) example. However, the inclusion of PowerShell examples throughout, and the use of Azure PowerShell cmdlets, may be seen as a mild Windows bias. There are no Linux-specific shell examples (e.g., Bash scripts), but the CLI commands are cross-platform and use a Linux image in the example. No Windows-only tools or patterns are mentioned, and the documentation is not exclusive to Windows.
Recommendations
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • Optionally, add a short Bash script example for common attach/detach operations to further demonstrate Linux parity.
  • Explicitly state that PowerShell examples are for users who prefer PowerShell, and that Azure CLI is recommended for cross-platform use.
  • Ensure that all troubleshooting links and referenced docs have Linux equivalents where relevant.
GitHub Create Pull Request
Virtual Machine Scale Sets Automatic OS image upgrades with Azure Virtual Machine Scale Sets ...e-sets/virtual-machine-scale-sets-automatic-upgrade.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ minor_arm_template_bias
Summary
The documentation provides both Windows and Linux parity in terms of supported OS images and Azure CLI/PowerShell examples. However, there are some minor biases: Windows terminology and properties are often mentioned first (e.g., ARM template defaults, property names), PowerShell examples are prominent and sometimes appear before CLI, and Windows-specific configuration details (like drive letters, enableAutomaticUpdates) are discussed in detail. ARM template and Bicep examples default to Windows images, and some explanations use Windows-centric language. Overall, Linux users can complete all tasks, but Windows is subtly prioritized.
Recommendations
  • Ensure ARM template and Bicep examples use both Windows and Linux image defaults, or alternate examples.
  • Where possible, present Azure CLI and PowerShell examples together, or alternate which appears first.
  • Explicitly mention Linux-specific considerations where Windows-specific details are discussed (e.g., drive letter reassignment vs. Linux mount points).
  • Clarify that all features and steps apply equally to Linux and Windows unless otherwise noted.
  • Add a note in sections with Windows-specific properties (like enableAutomaticUpdates) to indicate Linux users can ignore these.
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 and Windows examples for configuring custom metrics for rolling upgrades on Virtual Machine Scale Sets. However, there are several instances of Windows bias: PowerShell examples are consistently present and often shown before or alongside CLI/Bash examples; Windows-specific extension types (ApplicationHealthWindows) are used in some sample code and REST payloads, sometimes without clear Linux equivalents; and Windows tools (PowerShell) are given equal or greater prominence compared to Linux tools (Bash/Python). REST examples default to Windows extension types. Overall, Linux users can complete the task, but Windows patterns and tools are frequently prioritized or shown first.
Recommendations
  • Ensure Linux and Windows extension types are both shown in REST and JSON examples, or clarify when to use each.
  • Alternate the order of CLI/Bash and PowerShell examples so Linux tools are not always second.
  • Explicitly state that both ApplicationHealthLinux and ApplicationHealthWindows are supported, and provide clear guidance for Linux users.
  • Provide more Linux-native sample scripts (e.g., Python, Bash) for configuring the health endpoint, and link to Linux-specific troubleshooting resources.
  • In REST and JSON examples, show both Linux and Windows extension types, or use a placeholder to indicate either can be used.
GitHub Create Pull Request
Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is generally cross-platform and neutral, describing orchestration modes for Azure Virtual Machine Scale Sets without favoring Windows-specific features. However, there is minor evidence of Windows bias: in the 'Backup and recovery' section, Azure Site Recovery is noted as supported for Flexible orchestration mode 'via PowerShell' only, without mentioning Linux CLI or Bash alternatives. Additionally, the only explicit CLI example uses Azure CLI, which is cross-platform, but the documentation sometimes references PowerShell in the context of Azure Site Recovery, potentially implying Windows-first tooling.
Recommendations
  • Clarify whether Azure Site Recovery for Flexible orchestration mode can be managed via Azure CLI or Bash on Linux/macOS, not just PowerShell.
  • Where PowerShell is mentioned, add equivalent Azure CLI or Bash examples if available.
  • Ensure that all examples and tooling references are explicitly cross-platform unless a feature is truly Windows-only.
GitHub Create Pull Request
Virtual Machines Benchmark your application on Azure Disk Storage ...lob/main/articles/virtual-machines/disks-benchmarks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation mentions both Windows and Linux VMs are supported and provides examples using DiskSpd (Windows) and FIO (Linux). However, DiskSpd (Windows) is mentioned first, and the overall narrative and tool descriptions are slightly Windows-first. There is a mild bias toward Windows tools and patterns, but Linux parity is generally maintained.
Recommendations
  • Alternate the order of tool mentions (e.g., mention FIO first in some sections).
  • Ensure example commands and tool descriptions for Linux (FIO) are as detailed as those for Windows (DiskSpd).
  • Add explicit Linux setup instructions and troubleshooting tips where relevant.
  • Consider including a comparison table of DiskSpd and FIO features for both platforms.
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 Azure CLI and PowerShell examples for key operations, but PowerShell examples are often presented before CLI, and references to PowerShell are slightly more prominent. There is no explicit Linux shell example (e.g., Bash), but Azure CLI is cross-platform and suitable for Linux/macOS users. The 'Next steps' section lists both Linux and Windows guides, but Windows PowerShell is mentioned before Linux CLI in some places.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell examples, especially since CLI is cross-platform.
  • Add explicit Bash or Linux shell examples where relevant, or clarify that Azure CLI commands are suitable for Linux/macOS.
  • In 'Next steps', alternate the order of Linux and Windows links, or group them by platform for clarity.
  • Where PowerShell is referenced, also mention that Azure CLI is available for Linux/macOS users.
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 (a Windows-centric tool) is given equal prominence to Azure CLI, and is sometimes presented before or alongside CLI examples. The CLI examples are cross-platform, but there are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is referenced throughout, which may create friction for Linux/macOS users. The Azure Resource Manager template section does mention both Linux and Windows, but the overall pattern is to treat PowerShell as a primary method.
Recommendations
  • Ensure Azure CLI examples are presented before PowerShell examples, as CLI is cross-platform.
  • Add explicit Bash shell examples where relevant, especially for scripting tasks.
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide guidance for Linux/macOS users.
  • Consider reducing PowerShell prominence or adding notes for Linux/macOS users about alternative tools.
GitHub Create Pull Request
Virtual Machines Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents." ...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides backup and disaster recovery guidance for Azure Managed Disks on both Linux and Windows VMs. While most sections are platform-neutral, there are a few instances where Windows tools (e.g., Volume Shadow Service) are mentioned before Linux equivalents (e.g., fsfreeze), and Windows-specific examples (SQL Server) are highlighted first. However, Linux options are also described, and the overall guidance is inclusive.
Recommendations
  • When mentioning coordinated backup mechanisms, present Linux tools (e.g., fsfreeze) alongside Windows tools (e.g., Volume Shadow Service) with equal prominence.
  • Include examples of Linux-based database backup and disaster recovery (e.g., PostgreSQL, MySQL) in the 'Major database solutions' scenario, not just SQL Server and Oracle.
  • Ensure that file system consistency and application consistency for Linux VMs are explained in detail, similar to Windows.
  • Add links to Linux-specific documentation for backup and disaster recovery where relevant.
GitHub Create Pull Request
Virtual Machines Support matrix for VM restore points ...n/articles/virtual-machines/concepts-restore-points.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides a support matrix for VM restore points and covers both Windows and Linux operating systems. However, in the 'Operating system support for application consistency' section, Windows is discussed first and in greater detail (listing specific supported versions), while Linux is described more generally and with less granularity. No Windows-specific tools or examples are present, and Linux support is clearly mentioned. The 'Next steps' section references CLI, Azure portal, and PowerShell, but does not show a preference for Windows tools.
Recommendations
  • Present Windows and Linux operating system support in parallel, either in a single table or by listing Linux first in some cases.
  • Provide a more detailed list of supported Linux distributions (or a summary of key distros) rather than only linking to another page.
  • Ensure parity in detail between Windows and Linux sections, such as listing minimum requirements or notable limitations for both.
  • If possible, clarify that CLI and PowerShell are cross-platform, and provide links to Linux-specific guidance where relevant.
GitHub Create Pull Request
Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides examples for creating Azure Compute Galleries using Portal, Azure CLI, PowerShell, and REST API. While all major cross-platform tools are covered, PowerShell examples are presented alongside CLI and REST, and the PowerShell section is not prioritized over Linux-friendly tools. However, in the 'Create a private gallery' section, the PowerShell example is given its own tab, and is listed after CLI, which is cross-platform. There are no Windows-specific tools or patterns mentioned, and Linux parity is maintained throughout. The only minor bias is that PowerShell is included, but not prioritized, and Windows is not referenced first.
Recommendations
  • Ensure that CLI examples are always shown before PowerShell examples, as CLI is cross-platform.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider adding Bash shell script examples where relevant, to reinforce Linux parity.
  • If possible, clarify that PowerShell examples are for Windows and PowerShell Core users.
GitHub Create Pull Request
Virtual Machines Server-side encryption of Azure Managed Disks ...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation covers server-side encryption for Azure Managed Disks and is intended for both Linux and Windows VMs. While the content is generally cross-platform, there is a consistent pattern of mentioning Windows/PowerShell tools and articles before Linux/CLI equivalents, especially in 'Next steps' and throughout the article. References to PowerShell are often listed first, and some links (e.g., for automatic key rotation) point to Windows/PowerShell-specific guides before Linux alternatives. However, Linux parity is maintained with CLI links and explanations.
Recommendations
  • Present Azure CLI (Linux/macOS) and PowerShell (Windows) options together or alternate their order to avoid Windows-first bias.
  • Ensure that links to Linux/CLI guides are as prominent as Windows/PowerShell guides, especially in critical sections and 'Next steps'.
  • Where possible, provide code snippets or examples for both platforms side-by-side.
  • Review references to PowerShell and ensure CLI equivalents are always mentioned and linked in the same context.
GitHub Create Pull Request
Virtual Machines Share an Azure Managed Disk across VMs ...cs/blob/main/articles/virtual-machines/disks-shared.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides parity between Windows and Linux in terms of supported workloads, cluster managers, and technical concepts. However, in the 'Sample workloads' section, Windows examples and explanations are presented before Linux, and the performance throttling examples also begin with Windows scenarios. All major Linux equivalents are covered, but Windows is consistently shown first.
Recommendations
  • Consider alternating the order of Windows and Linux sections, or presenting them in parallel, to avoid implicit prioritization.
  • Add explicit Linux sample workload templates or links, similar to the Windows SoFS and SAP templates.
  • Ensure performance throttling examples include Linux scenarios with equal detail and prominence.
  • Where possible, provide Linux-specific guidance or walkthroughs alongside Windows examples.
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation is mostly neutral and focused on Azure Disk Storage features, but there are a few instances where Windows-specific links or tools are mentioned before Linux equivalents, or Windows documentation is referenced without equal Linux coverage. For example, in the 'Live Resize' section, the link is to a Windows-specific article, and in the 'Expand Ultra Disks and Premium SSD v2 without downtime' section, the Windows article is listed before the Linux one. Additionally, the 'LastOwnershipUpdateTime' property section references a Windows-specific documentation link. However, most features are cross-platform and the overall impact is minor.
Recommendations
  • Ensure that Linux documentation links are provided alongside Windows links wherever relevant, and consider listing Linux and Windows links together or in a neutral order.
  • Where referencing OS-specific guides, clarify that both Windows and Linux are supported and provide links to both.
  • Review documentation for any sections where only Windows tools (e.g., PowerShell) are mentioned, and add equivalent Linux (e.g., Bash/Azure CLI) examples if missing.
GitHub Create Pull Request
Virtual Machines Enable shared disks for Azure Managed Disks .../main/articles/virtual-machines/disks-shared-enable.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all disk types, but PowerShell examples are consistently present and often shown immediately after Azure CLI. The PowerShell module is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. However, Azure CLI examples are always present and are cross-platform. No Windows-only tools or patterns are mentioned, and Linux support is explicitly stated. There are no missing Linux examples, but PowerShell is given equal or greater prominence than CLI, which is more universal.
Recommendations
  • Consider listing Azure CLI examples before PowerShell in all sections, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly mention that Azure CLI is recommended for Linux/macOS users, and PowerShell is primarily for Windows users.
  • Add brief notes clarifying that PowerShell examples are for Windows (or for PowerShell Core on Linux/macOS if supported), to avoid confusion.
  • Ensure that all critical steps can be completed with Azure CLI, and highlight CLI as the preferred method for Linux/macOS parity.
GitHub Create Pull Request
Virtual Machines Ephemeral OS disks ...b/main/articles/virtual-machines/ephemeral-os-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation covers both Linux and Windows VMs, and provides parity in most explanations and examples. However, there are minor signs of Windows bias: Windows-specific details (such as page file placement and Windows Server image sizing) are often mentioned first or in more detail, and PowerShell is listed before CLI in the section about enabling customer managed keys. Linux equivalents are present but sometimes secondary.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence, alternating order where possible.
  • Provide explicit Linux image size examples alongside Windows ones in all relevant sections.
  • When referencing tools, list Azure CLI and PowerShell together, or alternate their order.
  • Expand Linux-specific operational details (e.g., swap file placement, common Linux distributions) to match Windows-specific coverage.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is focused on Linux, but in several sections (especially deployment and troubleshooting), Windows/PowerShell examples are presented first or with more detail. Azure PowerShell is discussed before Azure CLI, and PowerShell deployment examples are more prominent. However, Linux-specific instructions, paths, and CLI examples are present and generally sufficient for Linux users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred for Linux users.
  • Clarify that PowerShell is optional and not required for Linux deployments.
  • Add explicit notes or guidance for Linux users where PowerShell is mentioned, indicating that Azure CLI is the recommended tool.
  • Ensure troubleshooting instructions include CLI commands before PowerShell.
  • Review the order of sections to ensure Linux-centric tools and patterns are prioritized.
GitHub Create Pull Request
Virtual Machines NVIDIA GPU Driver Extension - Azure Linux VMs ...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM GPU driver installation, but includes PowerShell examples alongside Azure CLI and ARM template examples. In the deployment section, PowerShell is presented before Azure CLI, which is more native to Linux environments. However, Linux-specific commands and troubleshooting steps are well represented, and the overall guidance is Linux-centric.
Recommendations
  • Move Azure CLI examples before PowerShell in all sections, as Azure CLI is more commonly used on Linux.
  • Clearly indicate that PowerShell is optional and primarily for users on Windows or cross-platform environments.
  • Add Bash shell script examples for extension deployment and troubleshooting, as Bash is the default shell on most Linux distributions.
  • Ensure that all troubleshooting and manual steps are available in CLI or Bash, not just PowerShell.
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Linux and Windows guidance, but there are subtle signs of Windows bias. PowerShell examples are given equal prominence to CLI, but the PowerShell example defaults to Windows, while the CLI defaults to Linux. In some sections, Windows-specific terminology (e.g., Sysprep) is mentioned before Linux equivalents. However, Linux is well-represented, and the CLI examples are Linux-first.
Recommendations
  • In PowerShell examples, default to Linux OS type or provide both Linux and Windows variants equally.
  • Ensure that introductory guidance and examples alternate or equally represent Linux and Windows, rather than defaulting to Windows in PowerShell and Linux in CLI.
  • Where Windows-specific terminology is mentioned (e.g., Sysprep), ensure Linux equivalents (e.g., waagent -deprovision) are mentioned with equal prominence.
  • Consider adding explicit macOS guidance where relevant, or clarifying that CLI instructions are cross-platform.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines. ...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation presents benchmarking instructions for both Windows and Linux, but the Windows section (DISKSPD) appears first and is more prominent. Windows-specific tooling (DISKSPD) is introduced before Linux tooling (FIO), and the Windows section provides detailed command-line examples and parameter explanations. The Linux section follows, with equally detailed examples using FIO. There is a slight bias in ordering and tool prominence, but Linux parity is generally maintained.
Recommendations
  • Consider presenting Windows and Linux sections in parallel or with equal prominence, possibly with a table or side-by-side comparison.
  • Explicitly state that DISKSPD is Windows-focused and FIO is Linux-focused at the start of each section.
  • Add a brief summary at the top clarifying that both Windows and Linux are covered, and users should select the relevant section for their OS.
  • Ensure that parameter explanations and example detail are equally thorough for both tools.
  • If possible, provide links to additional Linux benchmarking tools (e.g., ioping, dd) for broader coverage.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption scenarios on Linux VMs ...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is often mentioned first or in more detail, and some backup/encryption instructions reference PowerShell cmdlets before their CLI equivalents. There is a slight preference for PowerShell in explanations and script detail, which may create friction for Linux users, though all tasks are achievable via CLI and the documentation is clearly Linux-focused.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell examples, especially in sections targeting Linux users.
  • Where possible, provide parity in detail and explanation for Azure CLI commands as is given for PowerShell scripts.
  • Clarify that Azure PowerShell can be run cross-platform, but highlight Azure CLI as the primary tool for Linux environments.
  • Add explicit notes or guidance for Linux/macOS users on tool selection and usage.
  • Review backup and snapshot instructions to ensure CLI options are equally emphasized.
GitHub Create Pull Request
Virtual Machines Enable Azure Disk Encryption for Linux VMs ...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is focused on enabling Azure Disk Encryption for Linux VMs and provides Linux-specific guidance throughout. However, in several places, Azure PowerShell is mentioned alongside Azure CLI as a management option for Linux VMs, and PowerShell examples/scripts are referenced equally with CLI examples/scripts. In the 'Next steps' and introductory sections, PowerShell is listed after CLI, but both are presented as options for Linux VM management, which may create minor confusion since PowerShell is traditionally associated with Windows. No critical Linux parity issues are present, and all technical guidance is Linux-centric.
Recommendations
  • Clarify that Azure PowerShell can be used cross-platform (Linux, macOS, Windows) and is not Windows-only.
  • Consider emphasizing Azure CLI as the primary tool for Linux users, with PowerShell as an alternative for those who prefer it.
  • Add a short note explaining that both Azure CLI and PowerShell are supported on Linux, to avoid confusion for users who may associate PowerShell with Windows.
  • Ensure that all example scripts and links are clearly labeled as cross-platform where applicable.
GitHub Create Pull Request
Virtual Machines Expand Virtual Hard Disks on a Linux VM ...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_tools
Summary
The documentation is overwhelmingly Linux-focused, with detailed instructions for Ubuntu, SUSE, Red Hat (with and without LVM), and generic Linux disk expansion. However, there is a minor bias in the section 'Expand without downtime classic VM SKU support', which provides only a PowerShell script for checking SKU support, without a Linux/Azure CLI equivalent.
Recommendations
  • Provide an Azure CLI or Bash equivalent for the PowerShell script used to check classic VM SKU support for disk expansion without downtime.
  • Add a note clarifying if the PowerShell script is only relevant for users managing classic VMs from Windows, and suggest alternatives for Linux/macOS users if available.
  • Ensure parity by mentioning cross-platform tools where possible, especially in sections referencing Azure management operations.
GitHub Create Pull Request
Virtual Machines Create and upload a Red Hat Enterprise Linux VHD for use in Azure ...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, in several sections, Windows/Hyper-V instructions are presented first, and some steps reference Hyper-V Manager as the primary workflow, even when Linux-native hypervisors (KVM, VMware) are equally supported. There are no missing Linux examples, and Linux tools and patterns are well represented throughout.
Recommendations
  • Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, rather than always after.
  • Clarify that Hyper-V Manager steps are only required for users on Windows, and highlight Linux-native workflows for users on Linux/macOS.
  • Add a short summary or table at the top outlining which hypervisors are supported on which platforms, to help Linux/macOS users quickly identify relevant instructions.
  • Ensure that conversion steps (e.g., VHD creation) reference Linux-native tools (qemu-img, guestfish) equally or before Windows tools.
  • Where possible, avoid language that implies Hyper-V is the default or preferred workflow for Linux VHD creation.
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 thorough Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details, which may create a perception of Windows bias. All technical guidance, examples, and tools are Linux-centric and appropriate for the topic.
Recommendations
  • Move Windows Server 2016 discussion and references to a background or infrastructure section, clarifying that it is relevant only as the Azure host OS and not for Linux VM configuration.
  • Consider starting the page with Linux-specific context and requirements, only mentioning Windows infrastructure as necessary.
  • Ensure that Linux guidance is always presented first and Windows references are clearly marked as background information.
GitHub Create Pull Request
Virtual Machines Overview of Azure Disk Storage ...in/articles/virtual-machines/managed-disks-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ minor_windows_reference
Summary
The documentation provides a balanced overview of Azure Managed Disks for both Linux and Windows VMs. However, there are minor instances where Windows-specific tools, terminology, or references are mentioned first or exclusively, such as links to Windows/PowerShell upload guides, Windows partitioning (MBR/GPT) documentation, and Windows drive letter conventions. Linux equivalents are present but sometimes mentioned after Windows, or referenced less directly.
Recommendations
  • Ensure Linux and Windows examples/tools are presented together or Linux is not consistently secondary.
  • Where Windows-specific links are given (e.g., PowerShell upload), ensure Linux/CLI links are equally prominent and described.
  • When discussing disk partitioning (MBR/GPT), include links to Linux partitioning documentation or clarify that guidance applies to both OS types.
  • When referencing drive letters (e.g., C: or D:), also mention Linux device paths (e.g., /dev/sda, /dev/disk/azure/resource) with equal clarity.
  • Review all sections for balanced terminology and tool references, ensuring Linux users are not left to infer their equivalents.
GitHub Create Pull Request