← Back to Dashboard
277
Pages Scanned
112
Pages Flagged
277
Changed Pages
40.4%
% Pages Flagged

Live Progress

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

Scan Information

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

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 277

Files Completed: 277

Problematic Pages

113 issues found
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation clearly states that the Service Fabric reverse proxy is not available for Linux clusters. All examples, guidance, and configuration instructions are implicitly Windows-centric, as Linux users cannot use the reverse proxy feature. There are no Linux-specific examples or alternative approaches provided for Linux clusters.
Recommendations
  • Add a prominent note at the top clarifying that the reverse proxy feature is Windows-only and not supported on Linux clusters.
  • Provide links or references to alternative communication patterns or tools for Linux Service Fabric clusters, if available.
  • If possible, mention any roadmap or plans for Linux support, or direct Linux users to relevant documentation for service discovery and communication.
  • Ensure that related documentation (e.g., setup, diagnostics) also clearly states platform limitations.
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-specific tools, particularly Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and workflows reference Windows tools, and there are no Linux/macOS equivalents or cross-platform guidance. The use of PowerShell and Visual Studio is presented as the default or only method, with no mention of CLI, REST API, or other cross-platform alternatives.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST API.
  • Include guidance for Linux/macOS users, such as how to configure upgrades without Visual Studio or PowerShell.
  • Mention and link to any available SDKs or tools for Service Fabric that work on Linux/macOS.
  • Clearly indicate if certain steps are Windows-only and provide alternative workflows for other platforms where possible.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is notably Windows-focused: it refers to 'custom windows images' throughout, provides only PowerShell (Windows-centric) examples for role assignment, and references Windows/PowerShell CLI documentation before Linux equivalents. There are no explicit Linux-specific examples or instructions, and the ARM template examples do not clarify Linux support. The page title and content do not indicate this is a Windows-only feature, and Service Fabric Managed Clusters support both Windows and Linux node types.
Recommendations
  • Clarify in the introduction whether custom images for Linux node types are supported and, if so, provide explicit instructions and examples for Linux.
  • Include Linux-specific CLI examples (e.g., using Azure CLI or Bash) for role assignment and other operations, not just PowerShell.
  • When referencing documentation, link to both Linux and Windows guides equally, or provide a neutral, cross-platform reference.
  • Update terminology to refer to 'custom images' (not just 'custom windows images') where appropriate, and specify differences if any exist.
  • Add ARM template examples for deploying Linux-based custom images if supported.
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 exclusively provides PowerShell-based examples and instructions, including module installation and REST API usage via PowerShell. There are no examples or guidance for Linux/macOS users (e.g., Bash, curl, Azure CLI), and PowerShell is presented as the primary and only scripting method, which creates friction for non-Windows users.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to trigger backups and track progress from Linux/macOS.
  • Mention Azure CLI commands if available for backup operations, or clarify their absence.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all platforms, or provide alternatives for Linux/macOS users.
  • Include a note about cross-platform support and any limitations for Linux/macOS users.
  • Consider showing Bash/curl examples before or alongside PowerShell to improve parity.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates 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 provided only for PowerShell and C#, with no mention of Linux/macOS equivalents or cross-platform CLI tools. There are no examples or guidance for Linux containers or non-Windows environments, despite Service Fabric supporting containers in general.
Recommendations
  • Add examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
  • Provide instructions for querying deployment status using Azure CLI or cross-platform tools, not just PowerShell.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide equivalent code and manifest examples.
  • Mention any platform-specific limitations or differences explicitly.
  • Ensure that introductory and code sections do not assume Windows familiarity unless the feature is Windows-only.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page primarily discusses data serialization in the context of Azure Service Fabric, which is cross-platform. However, in the 'Next steps' section, it references upgrading applications using Visual Studio and PowerShell—both of which are traditionally Windows-centric tools—before mentioning any CLI or Linux-native alternatives. There are no explicit Linux/macOS examples or references to cross-platform tools like Azure CLI or Service Fabric CLI.
Recommendations
  • Include examples or references for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), especially for Linux/macOS users.
  • When listing upgrade tutorials, either provide parity (e.g., 'Upgrading your Application Using Azure CLI') or clarify which tools are cross-platform.
  • Consider mentioning Visual Studio Code as a cross-platform alternative to Visual Studio, if applicable.
  • Explicitly state when a tool or method is Windows-only to help set expectations for non-Windows users.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page presents upgrade parameters for Service Fabric applications, but gives primary focus to Windows-centric tools (PowerShell and Visual Studio) in both structure and examples. PowerShell and Visual Studio are discussed first and in greater detail, with parameter tables and example formats, while Linux-compatible tools (SFCTL CLI) are covered later and less thoroughly. There are no explicit Linux command examples or walkthroughs in the main content, and the SFCTL section lacks parity in example depth compared to PowerShell. This creates friction for Linux/macOS users, though workarounds exist via SFCTL and REST.
Recommendations
  • Reorganize the page to present SFCTL (cross-platform CLI) examples and parameters before or alongside PowerShell/Visual Studio.
  • Provide explicit Linux/macOS command examples using SFCTL, including sample upgrade commands and parameter usage.
  • Clarify which tools are cross-platform and which are Windows-only, to guide users appropriately.
  • Ensure parameter tables for SFCTL match the detail and clarity of PowerShell/Visual Studio sections.
  • Add a note at the top indicating that PowerShell and Visual Studio are Windows-only, and SFCTL is recommended for Linux/macOS users.
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 examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented alongside C# and manifest examples, but no Linux-native tooling or cross-platform CLI (such as sfctl) is mentioned or demonstrated. The documentation does note that resource monitoring is supported for containerized applications on Linux, but the practical guidance and examples are Windows-oriented.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS.
  • Provide Bash shell script examples for relevant operations, especially for updating scaling policies.
  • Clarify which steps or commands are Windows-only and which are cross-platform.
  • Mention Linux/macOS tooling and workflows explicitly where applicable.
  • Consider reordering examples so that cross-platform options are presented before or alongside Windows-specific ones.
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 references PowerShell cmdlets as a primary management interface for Service Fabric, and mentions Windows security as a transport option, with no equivalent Linux tooling or examples provided. While the architectural concepts are platform-neutral, the management subsystem section gives Windows-oriented tools first and omits Linux alternatives, creating friction for Linux users.
Recommendations
  • Add references to Linux-compatible management tools, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
  • Explicitly mention cross-platform options for cluster management and lifecycle operations.
  • Clarify that X509 certificates are supported for secure transport on Linux, and provide links or examples for Linux security configuration.
  • Ensure examples and tooling references are balanced between Windows and Linux, or note platform-specific 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 ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides general information about Azure Service Fabric node types and virtual machine scale sets, but there are subtle signs of Windows bias. Examples and guidance reference Windows-style paths (e.g., 'D:\\SvcFab'), and the 'Next steps' section links primarily to PowerShell scripts and RDP-related tasks, which are Windows-centric. There is no explicit Linux/macOS guidance or examples for connecting to nodes or managing clusters, despite the mention of 'ServiceFabricLinuxNode' in the extension snippet.
Recommendations
  • Provide equivalent Linux/macOS examples for remote connection (e.g., SSH instructions alongside RDP/PowerShell).
  • Include Linux file path examples (e.g., '/var/svcfab') when referencing 'dataPath'.
  • Add links to Bash/CLI scripts or documentation for Linux cluster management tasks.
  • Clarify which instructions are OS-specific and offer parity for both Windows and Linux users.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric supports cross-platform management, the exclusive use of PowerShell creates friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS.
  • Include REST API examples for health reporting and querying, which are platform-agnostic.
  • Mention cross-platform tools and clarify which commands are available on each OS.
  • Where PowerShell is used, provide links or references to Linux/macOS alternatives.
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 for Azure Service Fabric Events primarily references Windows-specific event logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent, with no mention of Linux equivalents or guidance for Linux-based Service Fabric clusters. The examples and instructions focus on Windows tools and patterns, and Linux event access methods are not discussed.
Recommendations
  • Add information about how Service Fabric events are accessed and logged on Linux-based clusters, including supported logging mechanisms (e.g., stdout, syslog, journald).
  • Provide examples or references for configuring diagnostics and monitoring on Linux clusters, such as using the Azure Monitor agent for Linux.
  • Clarify which event access methods are cross-platform (e.g., EventStore REST APIs) and which are Windows-only.
  • Consider including a comparison table or section outlining differences in event access between Windows and Linux clusters.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation references PowerShell for deployment/removal tasks and for downloading ServicePackages in advance, without mentioning Linux equivalents (such as Azure CLI or REST API). There are no explicit Linux/macOS command examples or tool references, and the linked guidance for deployment/removal is PowerShell-centric. This may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for deployment, removal, and ServicePackage download tasks.
  • Include references or links to Linux/macOS-compatible tools and documentation where available.
  • Clarify in the 'Next steps' section if PowerShell is required, or offer alternative instructions for non-Windows users.
  • Where possible, add notes about cross-platform support for Service Fabric management tasks.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is the only command-line example shown for deploying applications with parameter overrides, and Windows file paths and certificate store names (e.g., 'C:\Program Files\...', 'MY' store) are mentioned first or exclusively in several places. While there is a brief note about Linux certificate storage, Linux/macOS command-line equivalents and deployment instructions are missing.
Recommendations
  • Provide equivalent Linux/macOS command-line examples (e.g., using Azure CLI or sfctl) alongside PowerShell for deploying Service Fabric applications with parameter overrides.
  • Mention Linux file paths and certificate store locations in parallel with Windows paths, not only as a note after the Windows example.
  • Clarify any differences in endpoint/certificate configuration between Windows and Linux clusters, and link to relevant Linux-specific documentation where appropriate.
  • If certain features or commands are Windows-only, explicitly state this and provide Linux alternatives or workarounds if available.
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 VM images (e.g., Win2016Datacenter) in all CLI and PowerShell examples, and does not provide equivalent Linux image examples or instructions. This creates friction for Linux users, who must infer the correct Linux image and adapt the commands themselves. Additionally, references to Windows quickstart documentation are given first, and Linux-specific guidance is missing.
Recommendations
  • Provide Linux VM image examples (e.g., UbuntuLTS, CentOS) alongside Windows examples in all CLI and PowerShell code snippets.
  • Add links to Linux VM quickstart documentation where Windows quickstart links are provided.
  • Explicitly state that the instructions apply to both Linux and Windows, and clarify any OS-specific steps if needed.
  • Where variables are set for VM image, recommend both Windows and Linux values.
  • Ensure screenshots and portal instructions mention Linux VM deployment as well.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed explanations and examples for X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows certificate store paths and tools are mentioned first or exclusively, such as 'LocalMachine\My', with Linux equivalents only briefly referenced. Troubleshooting sections focus on Windows event logs and tools (e.g., CAPI2 logging), with no Linux log or troubleshooting guidance. Code snippets and configuration examples use Windows-centric terminology and paths, and there are no explicit Linux/macOS command examples or troubleshooting steps.
Recommendations
  • Provide Linux/macOS equivalents for certificate store paths and management (e.g., clarify how certificates are stored and loaded on Linux nodes, with explicit paths and commands).
  • Include troubleshooting guidance for Linux clusters, such as relevant log locations, commands (e.g., journalctl, syslog), and certificate validation tools (e.g., openssl, certtool).
  • Add Linux/macOS-focused examples for certificate provisioning, validation, and rotation, including sample commands for certificate installation and verification.
  • When referencing Windows tools (e.g., CAPI2 logging, Win32 CryptoAPI), also mention or link to Linux/macOS alternatives or explain how similar diagnostics can be performed on those platforms.
  • Ensure parity in example ordering: present Linux/macOS examples alongside or before Windows examples where possible.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits a moderate Windows bias. PowerShell is the only CLI scripting language shown for programmatic certificate enrollment, and the Key Vault VM extension is described primarily in its Windows variant. The 'linkOnRenewal' feature and S-channel behavior are discussed as Windows-specific, with no mention of Linux equivalents or alternatives. JSON ARM templates are cross-platform, but operational scripting and troubleshooting focus on Windows tools and patterns. Linux scenarios, tools, or command-line examples (e.g., Azure CLI, bash scripting, or Linux VM extensions) are not covered, and Windows-specific mechanisms are often described first or exclusively.
Recommendations
  • Add Azure CLI (az) and/or bash scripting examples for certificate enrollment and management, alongside or in place of PowerShell.
  • Document the use of the Key Vault VM extension for Linux (if supported), or clarify any platform limitations.
  • Explicitly mention Linux/macOS support for Service Fabric clusters, and provide guidance or links for certificate provisioning and management on those platforms.
  • When discussing Windows-specific features (e.g., S-channel, linkOnRenewal), clearly state their platform scope and, if possible, provide Linux/macOS alternatives or note their absence.
  • Balance the ordering of examples and explanations so that Linux and cross-platform approaches are presented alongside Windows ones, not only after or not at all.
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 example for bypassing Infrastructure Service, and references Service Fabric Explorer (a GUI tool typically used on Windows). No equivalent Linux/macOS CLI or tooling examples are given, and PowerShell is presented as the default method for manual operations.
Recommendations
  • Add equivalent CLI examples for Linux/macOS users, such as using Azure CLI or REST API calls where possible.
  • Clarify whether the PowerShell command can be run from PowerShell Core on Linux/macOS, or provide alternative commands.
  • Mention cross-platform tools or interfaces (e.g., Azure CLI, REST API) for managing Service Fabric clusters.
  • If Service Fabric Explorer is Windows-only, note alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Initializer CodePackages in Service Fabric provides only Windows container examples, uses Windows-specific images (nanoserver), Windows paths, and Windows command syntax (cmd, C:\ paths). It explicitly references Windows container compatibility and does not provide any Linux container or cross-platform examples. All sample manifests, commands, and volume mounts are Windows-centric, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) with Linux command syntax and paths.
  • Document any platform limitations or differences in Initializer CodePackages for Linux containers, if applicable.
  • Provide guidance or links for creating Service Fabric applications with Linux containers.
  • Clarify whether Initializer CodePackages are supported for Linux container workloads, and if not, state this explicitly.
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 and ARM-managed clusters. It consistently recommends Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for operations such as deleting or creating applications/services, with only a brief mention of the Azure CLI (az resource) for application deletion. There are no explicit Linux/macOS examples or references to cross-platform tools, and PowerShell cmdlets are presented first and most frequently.
Recommendations
  • Include Azure CLI equivalents for all PowerShell cmdlet examples (e.g., az resource delete, az servicefabric managed-cluster application create).
  • Present both PowerShell and Azure CLI options side-by-side, clarifying which are cross-platform.
  • Explicitly note that Azure CLI is supported on Linux/macOS and provide links to relevant CLI documentation.
  • Where possible, add ARM template examples and clarify their cross-platform nature.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in cleanup, and these are mentioned before Linux equivalents. The examples and explanations focus on Windows images, with Linux images only referenced in an example regex. No Linux-specific guidance or parity is provided.
Recommendations
  • Include Linux container base images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the explanation of default exclusions and examples.
  • Clarify whether the cleanup and management features apply equally to Linux containers and Windows containers, and provide explicit guidance for Linux scenarios.
  • Add examples showing how to skip Linux base images, and discuss any differences in image management between Windows and Linux nodes.
  • Ensure documentation is clear about cross-platform applicability, especially for clusters running Linux VMs.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. However, all CLI-based examples use PowerShell cmdlets (e.g., New-AzServiceFabricManagedNodeType), with no mention of Azure CLI (az) equivalents or Bash scripting. This creates a bias towards Windows/PowerShell users and omits guidance for Linux/macOS users who may prefer or require Azure CLI or Bash.
Recommendations
  • Add Azure CLI (az) command examples for all tasks currently shown with PowerShell, such as adding, removing, and scaling node types.
  • Explicitly mention that PowerShell examples can be run on macOS/Linux using PowerShell Core, or clarify if they require Windows.
  • Where possible, provide Bash scripting examples or note cross-platform alternatives.
  • Consider listing Azure CLI examples before or alongside PowerShell to promote parity.
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 templates are referenced in a table, actionable examples and guidance are PowerShell-heavy, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit Azure CLI command examples alongside PowerShell examples for key tasks (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Mention Azure CLI and cross-platform tools in the narrative text, not just in the table.
  • Clarify that PowerShell modules are available cross-platform (if true), or provide equivalent CLI/Bicep instructions.
  • Ensure all guidance and examples are platform-neutral or provide parity for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides migration guidance for Azure Service Fabric clusters to availability zone support. While much of the guidance is platform-neutral (focused on ARM templates and Azure resources), the only CLI/script examples given are in PowerShell, and the sample templates referenced are primarily for Windows clusters. PowerShell is a Windows-centric tool, and no Bash, Azure CLI, or Linux-native scripting examples are provided. Additionally, the first sample template referenced is for Windows, and only later is an Ubuntu template mentioned, but no Linux-specific migration commands are shown.
Recommendations
  • Add Azure CLI or Bash script examples for resource deployment, node disabling, and removal, alongside PowerShell.
  • Reference and provide Linux/Ubuntu sample templates equally and early in the document.
  • Clarify which steps are platform-agnostic and which require Windows tools, and provide alternatives where possible.
  • Explicitly note any platform-specific requirements and offer guidance for Linux/macOS users.
  • Include links to Linux/macOS Service Fabric tooling documentation.
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 warning that recommends opening the Service Fabric XSD schema file in Visual Studio using a Windows file path, suggesting a Windows-centric workflow and toolset. There is no mention of Linux or cross-platform alternatives for schema validation or authoring manifests. Additionally, the only tool-specific guidance is Windows-first.
Recommendations
  • Provide instructions or suggestions for validating the Service Fabric manifest XML schema on Linux/macOS, such as using cross-platform editors (e.g., VS Code with XML extensions) or command-line tools (e.g., xmllint, xmlstarlet).
  • Mention the location of the schema file on Linux clusters, if applicable, or clarify if the schema is only available on Windows.
  • When referencing tools like Visual Studio, note cross-platform alternatives or explicitly state if a feature is Windows-only.
  • Include example workflows for authoring and validating manifests on Linux/macOS, or link to relevant guidance.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation covers monitoring for Azure Service Fabric clusters on both Windows and Linux, but there is a noticeable Windows bias in several areas. Windows-specific tools (e.g., EventStore APIs, Diagnostics Agent) are mentioned first or exclusively, and some example/tutorial links focus on Windows or .NET applications. Linux equivalents are referenced, but often with less detail or as secondary mentions. Some sections lack explicit Linux examples or guidance, especially for cluster-level monitoring and event access.
Recommendations
  • Provide parallel Linux examples and tutorials for cluster monitoring, application monitoring, and event access, matching the detail given for Windows.
  • Ensure Linux-specific tools and patterns (e.g., LTTng, Syslog, Linux agent configuration) are described with equal prominence and clarity.
  • Add links to Linux-focused tutorials and documentation where Windows tutorials are referenced.
  • Clarify which features are Windows-only and provide alternative approaches for Linux users where possible.
  • Balance the order of presentation so Linux and Windows are treated equally, rather than Windows-first.
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 Service Fabric application security in a mostly platform-neutral way, but there are several subtle Windows biases. Windows-specific tools and features (e.g., Active Directory, gMSA, BitLocker) are mentioned with more detail or before Linux equivalents. Some sections (e.g., disk encryption) reference Windows solutions (BitLocker, PowerShell) and leave Linux solutions as TODOs, without examples or guidance. Windows user account types and AD integration are described, but Linux equivalents (e.g., Linux user/group management, disk encryption) are not provided or are missing.
Recommendations
  • Add Linux-specific examples and guidance, especially for disk encryption and user/group management in Service Fabric clusters.
  • Ensure parity in describing how to secure applications and resources on Linux clusters, including how to run services under Linux user accounts and manage secrets/certificates.
  • Provide links or references to Linux documentation where appropriate (e.g., encrypting disks on Linux clusters, using Linux containers).
  • Avoid listing Windows tools/features first unless they are more broadly applicable; present both Windows and Linux options together.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page for 'Application lifecycle in Service Fabric' demonstrates notable Windows bias. PowerShell cmdlets are consistently referenced alongside .NET APIs and REST operations, but Linux-native tools or CLI examples (such as sfctl or Azure CLI) are missing or relegated to a generic link. Windows tools and PowerShell patterns are mentioned throughout, often before REST or .NET alternatives, and no Linux/macOS-specific guidance or examples are provided. This creates friction for non-Windows users, especially since Service Fabric supports cross-platform development and management.
Recommendations
  • Add explicit sfctl (Service Fabric CLI) and Azure CLI command examples for each lifecycle operation (deploy, upgrade, remove, etc.), not just links.
  • Where PowerShell cmdlets are mentioned, provide equivalent CLI commands and highlight their parity.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right approach.
  • Consider including bash or shell script snippets for common workflows.
  • Review and update links to ensure Linux/macOS users can easily find relevant instructions.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for Service Fabric application upgrades demonstrates a notable Windows bias. All code examples are provided exclusively in PowerShell, a Windows-centric tool, with no equivalent examples for Linux/macOS users. The documentation references Windows-specific technologies (e.g., http.sys, Windows HTTP Server API) without clarifying cross-platform alternatives or limitations. Additionally, the 'Next steps' section prioritizes Visual Studio and PowerShell workflows, both of which are primarily Windows-based, and does not mention Linux-native tools or workflows.
Recommendations
  • Provide equivalent CLI (Azure CLI or Service Fabric CLI) commands for application upgrade tasks, especially for Linux/macOS users.
  • Explicitly state any platform limitations or differences, such as http.sys and certificate handling, and offer Linux-specific guidance where possible.
  • Include Linux/macOS examples alongside PowerShell, or at least reference cross-platform tools in all relevant sections.
  • In the 'Next steps' section, add links or references to Linux/macOS-compatible upgrade workflows and tooling.
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 page provides PowerShell-only examples for application removal and references PowerShell as a primary tool for managing Service Fabric resources. There are no CLI or Linux/macOS equivalent examples for critical operations, and PowerShell is mentioned before CLI in the 'Next steps' section. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools.
Recommendations
  • Add Azure CLI examples for application removal and other management tasks alongside PowerShell examples.
  • Explicitly mention cross-platform tools (such as Azure CLI and Service Fabric CLI) in all relevant sections, not just in 'Next steps'.
  • Provide guidance or links for Linux/macOS users on how to perform equivalent operations.
  • Ensure that REST API examples are shown where possible, as these are platform-agnostic.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for advanced Service Fabric application upgrade topics demonstrates a notable Windows/PowerShell bias. All command-line examples use PowerShell cmdlets (e.g., New-ServiceFabricService, Start-ServiceFabricApplicationUpgrade), with no mention of Linux/macOS equivalents such as the Service Fabric CLI (sfctl). References to ARM templates and XML manifest editing are platform-neutral, but all interactive/command-line instructions assume a Windows/PowerShell environment. There are no examples or guidance for Linux users, and PowerShell is presented as the default tool for upgrades and service management.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Where PowerShell cmdlets are referenced, include a note or table mapping them to their sfctl equivalents.
  • Clarify in the introduction that both PowerShell and sfctl can be used for Service Fabric management, and link to relevant cross-platform documentation.
  • Ensure that at least one example in each section demonstrates the Linux/macOS workflow.
  • Where possible, use platform-neutral language (e.g., 'use a command-line tool such as PowerShell or sfctl') instead of only referencing PowerShell.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily biased toward Windows and PowerShell usage. All code examples use PowerShell, including REST API calls, and require installation of Microsoft.ServiceFabric.Powershell.Http Module. There are no examples or guidance for Linux/macOS users (e.g., using Bash, curl, or Azure CLI), nor is there mention of cross-platform alternatives. The reliance on PowerShell and Windows-specific tooling creates friction for non-Windows users.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls, suitable for Linux/macOS users.
  • Document how to authenticate and interact with Service Fabric REST APIs from Linux/macOS (e.g., using OpenSSL for certificate handling).
  • Mention Azure CLI or other cross-platform tools if available.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http Module is required only for Windows, and provide alternatives for other platforms.
  • Reorder examples so that REST API usage is shown in a generic, cross-platform way first, followed by PowerShell-specific examples.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides several manual scaling instructions using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux CLI or cross-platform alternatives. Additionally, PowerShell is mentioned first and exclusively in step-by-step guides, which may create friction for Linux/macOS users. However, the page does reference Linux clusters in the 'Next steps' section, and the overall guidance is not Windows-only.
Recommendations
  • Add equivalent Linux CLI instructions (e.g., using sfctl or REST API) alongside PowerShell examples for manual scaling operations.
  • Clearly indicate which commands are Windows-only and provide cross-platform alternatives where possible.
  • Consider showing cross-platform examples first or in parallel, rather than defaulting to PowerShell.
  • Link to documentation for Linux/macOS management tools (e.g., sfctl, Azure CLI) when referencing PowerShell commands.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides several Windows/PowerShell-centric examples and references, such as mentioning PowerShell APIs and classic PowerShell tasks in Azure DevOps, referencing Windows-specific tools (e.g., netsh), and linking to Windows ARM templates before Linux equivalents. Linux is mentioned, but examples and explanations are often Windows-first or Windows-only, with Linux alternatives sometimes missing or less detailed.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside PowerShell examples, especially for cluster management and networking tasks.
  • Reference Linux ARM template samples equally with Windows samples.
  • Clarify which networking rules and port ranges apply to Linux clusters, and provide Linux-specific guidance where Windows-only tools (e.g., netsh) are referenced.
  • Expand explanations for Linux scenarios, such as application networking, DevOps integration, and reverse proxy usage.
  • Ensure Linux documentation links are as prominent as Windows links throughout the page.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page is generally platform-neutral, focusing on Azure Service Fabric's backup configuration. However, the only on-premises backup storage example provided is for a Windows file share, using Windows authentication and UNC paths (\\StorageServer\BackupStore). No Linux or cross-platform file share example (e.g., SMB with Linux, NFS, or guidance for Linux clusters) is given. This may create friction for Linux users deploying standalone Service Fabric clusters who wish to use local backup storage.
Recommendations
  • Add examples or guidance for configuring file share backup storage on Linux clusters, such as using SMB/CIFS mounts or NFS.
  • Clarify whether file share backup storage is supported on Linux Service Fabric clusters, and if so, provide sample configurations.
  • Mention any platform-specific limitations for backup storage options (e.g., if file share is Windows-only, state this explicitly).
  • Provide parity in documentation by including Linux authentication mechanisms or mount instructions where relevant.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but only PowerShell is used for advanced cluster upgrade operations. Windows-specific tools and registry settings are mentioned without Linux equivalents or guidance. There are missing Linux-specific examples for tasks like manual cluster upgrades, and disabling Windows Update is discussed without mentioning Linux patch management.
Recommendations
  • Provide Linux-native command examples (e.g., Bash scripts or Linux CLI equivalents) for cluster upgrade operations currently shown only in PowerShell.
  • Include guidance or references for managing OS updates and patching on Linux-based Service Fabric clusters, similar to the Windows Update/registry section.
  • When mentioning Windows-specific tools or settings, add parallel Linux guidance or explicitly state if the step is not required/applicable for Linux.
  • Where possible, balance PowerShell and Bash/CLI examples throughout the documentation, not just for initial deployment.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation generally provides both Windows and Linux guidance for key security tasks, but there is a recurring pattern of presenting Windows/PowerShell examples and tools first, and in some sections, Windows-specific tooling (e.g., Windows Defender, PowerShell cmdlets) is discussed in detail while Linux equivalents are only briefly mentioned or omitted. Some sections (like Windows Defender) are Windows-only by nature, but others (such as encryption and certificate management) could benefit from more balanced Linux coverage.
Recommendations
  • When presenting example commands or workflows, alternate the order or present Linux and Windows examples side by side to avoid the perception of Windows-first bias.
  • Where Windows-specific tools (e.g., PowerShell, Windows Defender) are discussed, provide equivalent Linux guidance or explicitly state when no equivalent exists.
  • In sections like 'Encrypting Service Fabric package secret values', ensure Linux and Windows instructions are equally detailed and parallel in structure.
  • For security baseline recommendations, mention or link to industry-standard Linux security baselines (e.g., CIS Benchmarks) alongside Windows baselines.
  • In sections where only Windows tooling is described (e.g., Windows Defender exclusions), add a note or section about recommended Linux antimalware practices or clarify that Linux users should refer to their distribution's documentation.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation covers Service Fabric cluster settings for both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows terminology and tools (e.g., certificate store names like 'MY', 'LocalMachine', NTLM authentication, Windows Defender Firewall) are referenced throughout, often without explicit Linux equivalents or with Windows defaults shown first. Some parameters (e.g., ContainerNetworkSetup) have Windows defaults prioritized. Certificate store references and NTLM authentication are Windows-centric, and explanations often reference Windows APIs (e.g., CertGetCertificateChain). While Linux is mentioned in some places, parity is not always clear.
Recommendations
  • Explicitly document Linux equivalents for certificate store names, authentication mechanisms, and file paths.
  • Where Windows tools or terminology are used (e.g., NTLM, Windows Defender Firewall), add Linux alternatives or clarify if the feature is Windows-only.
  • Ensure that Linux-specific configuration options and defaults are shown alongside Windows, not only as afterthoughts.
  • Add links or references to Linux-specific documentation where relevant.
  • Clarify which settings are cross-platform and which are platform-specific, ideally with a table or annotation.
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 for Service Fabric Cluster Resource Manager - Placement Policies consistently provides PowerShell examples for configuring placement policies, but does not offer equivalent Linux/macOS CLI (e.g., sfctl) or REST API examples. The PowerShell examples are shown alongside C# code, with no mention of cross-platform tools or commands, creating friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and supported on Linux/macOS.
  • Include REST API examples for placement policy configuration, as these are platform-agnostic.
  • Clearly indicate which tools are Windows-only and provide guidance for Linux/macOS users on how to achieve the same tasks.
  • Consider reordering examples so that cross-platform tools (sfctl, REST) are shown before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no mention of Linux-compatible CLI tools or Bash equivalents. PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users, who may use Azure CLI or REST APIs instead. There is no guidance or parity for non-Windows environments.
Recommendations
  • Add Azure CLI examples for all PowerShell commands shown, as Azure CLI is cross-platform and supported on Linux/macOS.
  • Mention REST API options for managing Application Groups, with example requests.
  • Clarify which management tools are available on Linux/macOS and provide links or instructions for their use.
  • If PowerShell Core (pwsh) is supported for these commands, specify this and provide Linux/macOS installation guidance.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides code examples for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash scripts) are provided. The PowerShell examples are given alongside C# code, but there is no mention of cross-platform alternatives or guidance for Linux users. This creates friction for users running Service Fabric clusters on Linux or managing them from non-Windows environments.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, as Azure CLI is cross-platform.
  • Mention Bash scripting or REST API usage for metric management tasks, with sample commands.
  • Clarify whether the PowerShell commands are supported on PowerShell Core (cross-platform) or only Windows PowerShell.
  • Provide guidance or links for Linux/macOS users on how to perform equivalent tasks.
  • Explicitly state any limitations or differences for Linux clusters in Service Fabric regarding metrics management.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides configuration examples using XML, JSON, PowerShell, and C#. However, all CLI/API examples are given exclusively in PowerShell, with no equivalent Bash, Linux CLI, or cross-platform REST API examples. PowerShell is presented as the primary scripting interface for dynamic operations, creating friction for Linux/macOS users who cannot use PowerShell natively. The C# examples are platform-neutral, but the lack of Linux-friendly CLI guidance is notable.
Recommendations
  • Add Bash or Azure CLI examples for service sensitivity and maximum load configuration, where possible.
  • Clarify whether PowerShell commands can be run on Linux/macOS (e.g., via PowerShell Core), or provide REST API equivalents.
  • Mention cross-platform tools or interfaces (such as Azure CLI or REST API) before or alongside PowerShell.
  • Explicitly state if certain operations are only possible via PowerShell, and suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying health reports, but does not include equivalent examples for Linux/macOS users (e.g., using sfctl or REST API). The only command-line interaction shown is Windows/PowerShell-specific, which may create friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent Linux/macOS examples using sfctl (the cross-platform Service Fabric CLI) for querying partition health and other management tasks.
  • Where possible, provide REST API examples for cluster management operations, as these are platform-agnostic.
  • When showing command-line examples, present both Windows (PowerShell) and Linux/macOS (bash/sfctl) options, or note the cross-platform alternatives.
  • Explicitly mention that the PowerShell example is for Windows and direct Linux/macOS users to the appropriate tools.
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 featured as the only command-line interface, which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for creating and updating Service Fabric services with MoveCost, if supported.
  • If PowerShell is required, clarify whether Azure PowerShell Core (cross-platform) is supported, and provide Bash/CLI alternatives where possible.
  • Explicitly mention any platform limitations (e.g., if MoveCost configuration is only possible via PowerShell or C#).
  • Include notes or links to Linux/macOS setup guides for Service Fabric management.
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 include equivalent Linux/macOS CLI examples (such as Bash or Azure CLI). PowerShell is presented first and exclusively as the shell-based method, which may create friction for Linux/macOS users who typically use Bash or other shells. There is no mention of cross-platform tools or commands for these operations.
Recommendations
  • Add Azure CLI or Bash script examples for managing node tags and service requirements, if supported.
  • Clarify whether PowerShell commands are available cross-platform (PowerShell Core), or if they are Windows-only.
  • Mention REST API usage with example curl commands for Linux/macOS users.
  • Explicitly state if certain operations are only possible via PowerShell, and provide guidance for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters exhibits Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. There are no Linux-specific examples, commands, or guidance, and the tooling mentioned is Windows-centric.
Recommendations
  • Add equivalent Linux instructions and examples, such as using Service Fabric CLI (sfctl) or REST APIs for cluster management.
  • Explicitly state if standalone clusters are Windows-only, or clarify Linux support status.
  • Provide links to Linux-specific documentation or note limitations if Linux is not supported.
  • Mention cross-platform tools or approaches where possible, and avoid referencing only Windows tools.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page focuses heavily on Windows Server clusters when discussing standalone cluster security, providing links and instructions only for Windows. There are no equivalent examples, links, or instructions for securing standalone Linux Service Fabric clusters, even though the text mentions that the concepts are similar for Linux and Windows. Windows security mechanisms (Kerberos, group Managed Service Accounts) are discussed without Linux alternatives, and certificate creation is described with a Windows-centric approach. Azure-hosted clusters are covered in a platform-neutral way, but standalone scenarios are Windows-only.
Recommendations
  • Add explicit guidance, links, and examples for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
  • Clarify which security features are available or unsupported on Linux standalone clusters.
  • Provide Linux-specific instructions or references for certificate creation, installation, and management (e.g., using OpenSSL, Linux certificate stores).
  • Mention Linux authentication mechanisms or note their absence if not supported.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation consistently references Windows-specific upgrade and configuration guides (e.g., links ending with '-windows-server.md'), and the only patch orchestration application mentioned is for Windows. There are no Linux-specific instructions, examples, or references, and the documentation does not clarify whether Linux clusters are supported or provide parity guidance.
Recommendations
  • Clarify early in the article whether Service Fabric standalone clusters are Windows-only or if Linux is supported.
  • If Linux standalone clusters are supported, provide equivalent Linux upgrade/configuration guides and link to them alongside or before Windows guides.
  • Mention and link to any Linux-compatible patch orchestration solutions, or explicitly state if such functionality is unavailable.
  • Ensure that examples, references, and tool mentions are either cross-platform or clearly indicate platform specificity.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for the Azure Service Fabric application resource model exhibits several Windows biases. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mentioning or providing Azure CLI equivalents. The application packaging step references Visual Studio, a Windows-centric tool, and does not offer alternatives for Linux/macOS users. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
  • Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands).
  • Mention and link to Linux/macOS-compatible tooling for application packaging and deployment.
  • Clarify which steps are Windows-only and offer Linux/macOS alternatives where possible.
  • Consider reordering examples so that cross-platform solutions are presented before or alongside Windows-specific ones.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a noticeable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are often mentioned first or exclusively, and several examples reference Windows services and executables (e.g., FabricHost.exe). Standalone cluster creation and upgrades are only described for Windows, with Linux standalone clusters explicitly noted as unsupported. Linux equivalents (e.g., Bash, Linux CLI usage) are rarely mentioned, and Linux-specific guidance is minimal or missing in several sections.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster management, health monitoring, and application lifecycle tasks.
  • Mention Linux tools (e.g., Bash, Linux CLI) and workflows where PowerShell or Visual Studio are referenced.
  • Clarify which features are Windows-only and which are cross-platform, linking to Linux documentation where available.
  • Add parity for standalone cluster creation and upgrades when Linux support becomes available, or provide alternative guidance for Linux users.
  • Ensure CLI examples are platform-neutral or include both Windows and Linux variants.
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 cross-platform alternatives. Windows-centric tools (PowerShell, ApplicationManifest.xml in Visual Studio) are mentioned before Linux options, and Linux limitations are noted without guidance for Linux users. There are no Linux-specific examples or instructions, creating friction for Linux users.
Recommendations
  • Add CLI examples for Linux, such as Azure CLI or bash scripts, for setting DNS names and managing Service Fabric services.
  • Include instructions or examples for editing service manifests and deploying services on Linux clusters using cross-platform tools.
  • Clarify how Linux users can accomplish tasks that are currently only documented with PowerShell or Windows tooling.
  • Provide guidance for enabling DNS service on Linux clusters, including steps for containerized services and alternatives to the Azure portal.
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
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters, which can run on both Windows and Linux. However, there are several areas where Windows bias is evident: references to 'Patch the Windows operating system in your Service Fabric cluster' are given as the only OS patching example, and PowerShell is mentioned before Azure CLI in several places. There are no explicit Linux-specific examples or guidance, and the OS upgrade section only links to Windows patching documentation.
Recommendations
  • Add explicit guidance and links for patching/upgrading Linux-based Service Fabric clusters, including relevant documentation for Linux OS image upgrades.
  • When mentioning PowerShell and Azure CLI, ensure both are presented equally, and provide Bash/Linux CLI examples where appropriate.
  • Clarify which features or upgrade steps are Windows-only and which are cross-platform, to help Linux users identify relevant instructions.
  • Include examples or references for managing certificates, ports, and node properties using Linux tools or Azure CLI from a Linux/macOS environment.
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 patterns primarily using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or bash examples, and PowerShell is mentioned before any Linux alternatives. While the page does acknowledge platform differences in the 'Choosing a platform' section, the practical guidance and examples are heavily skewed toward Windows users, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Linux CLI/bash examples for administrative tasks (e.g., scaling services, creating/removing services/applications).
  • Mention and link to Linux-specific Service Fabric management tools (such as sfctl) alongside PowerShell.
  • Present Windows and Linux examples side by side, or alternate which platform is shown first.
  • Clarify when a command is Windows-only and provide Linux alternatives 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 for Azure Service Fabric hosting model presents PowerShell as the primary CLI example for service creation and management, with no mention of Linux-compatible CLI tools (such as sfctl) or Bash equivalents. Windows/PowerShell examples are given first and exclusively, creating friction for Linux/macOS users who may not have access to PowerShell or prefer native tools. REST API and .NET code examples are included, but CLI guidance is Windows-centric.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI) for Linux/macOS users alongside PowerShell examples.
  • Explicitly mention that sfctl can be used on Linux/macOS and provide links to its documentation.
  • Clarify which tools are cross-platform and which are Windows-only, to help users select the right approach.
  • Consider providing Bash script examples where relevant, or note any limitations for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page presents Windows/PowerShell (New-ServiceFabricApplication) as the first and most prominent example for specifying parameters during application creation. Linux tooling (sfctl) is mentioned second, but with less detail. There are no explicit Linux/macOS shell examples (e.g., Bash), and Visual Studio (a Windows-centric tool) is referenced without alternatives for Linux/macOS users. The page assumes familiarity with Windows tools and workflows, creating friction for Linux/macOS users.
Recommendations
  • Provide explicit Bash or shell examples for Linux/macOS users alongside PowerShell examples.
  • Mention and detail cross-platform tools (e.g., sfctl) before Windows-specific tools.
  • Include instructions for using parameter files and deployment scripts in Linux/macOS environments.
  • Reference alternative editors or IDEs (e.g., VS Code) for Linux/macOS users instead of only Visual Studio.
  • Clarify which tools are cross-platform and which are Windows-only.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Replica Soft Delete in Service Fabric heavily references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links exclusively for PowerShell usage. There is no mention of Linux CLI equivalents, nor are examples provided for Linux/macOS users. The documentation assumes familiarity with Windows tooling and patterns, creating friction for users operating Service Fabric clusters on Linux.
Recommendations
  • Add examples and references for managing replicas using Service Fabric CLI (sfctl) or REST APIs, which are cross-platform.
  • Clarify whether the PowerShell APIs are available or have equivalents on Linux/macOS, and provide guidance for those platforms.
  • Include sample commands for Linux environments, such as using sfctl or FabricClient APIs in .NET Core.
  • Explicitly state platform limitations if certain APIs are Windows-only, so Linux/macOS users are not misled.
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 links to PowerShell-based deployment/removal guides. While Service Fabric is cross-platform, the documentation does not provide Linux/macOS CLI or scripting alternatives, nor does it mention tools like Azure CLI or Bash. Windows-centric tools and workflows (PowerShell, Visual Studio) are mentioned first and exclusively, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples and links for Linux/macOS users, such as using Azure CLI, Bash scripts, or cross-platform .NET Core tools.
  • Explicitly mention cross-platform options for retrieving cluster manifests and deploying applications.
  • Provide guidance for configuring and managing Service Fabric clusters from non-Windows environments.
  • Include references to relevant Linux/macOS documentation or tools alongside PowerShell and Visual Studio.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides Service Fabric container application manifest examples based on a Windows Server 2016 Container sample. Windows-specific tools and patterns are referenced first and sometimes exclusively (e.g., 'winver' for OS version, Windows file paths, and the use of 'process' isolation). There is minimal mention of Linux equivalents, and no Linux-specific manifest examples or guidance are provided, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent Linux-based manifest examples, or clearly indicate which features are Windows-only.
  • When referencing Windows tools (e.g., 'winver'), also mention Linux equivalents (e.g., 'uname -r' or '/etc/os-release').
  • Use platform-neutral file paths in examples, or provide both Windows and Linux variants where applicable.
  • Clarify in the introduction which features or manifest elements are cross-platform and which are Windows-specific.
  • If features are not supported on Linux, explicitly state this to avoid confusion.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides only PowerShell-based deployment commands and examples, with no mention of Azure CLI, Bash, or Linux/macOS workflows. It also references Windows tools (e.g., RDP, Windows command prompt for ping) and uses Windows-centric file paths and command syntax. There are no Linux/macOS equivalents or guidance for users on those platforms.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps, as Azure CLI is cross-platform.
  • Include Bash/Linux/macOS command-line examples for common tasks (e.g., using ssh instead of RDP, using ping from a Unix shell).
  • When referencing file paths, use platform-agnostic or dual examples (e.g., C:\... and ~/...).
  • Mention alternatives to Windows-specific tools like RDP (e.g., SSH for Linux/macOS users) when discussing VM access.
  • Explicitly state that the templates and workflows are supported on both Windows and Linux/macOS, and provide links to relevant cross-platform tooling documentation.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Service Fabric. However, Windows-specific tools and APIs (such as HTTP.sys and netsh) are mentioned exclusively and in detail, with Windows-focused explanations and examples appearing before Linux equivalents. There is a lack of explicit Linux/macOS guidance, and no Linux-specific examples or troubleshooting advice are provided. The documentation assumes familiarity with Windows concepts and tools, and does not offer parity for Linux users in areas such as endpoint configuration, port reservation, or debugging.
Recommendations
  • Add explicit Linux/macOS guidance for Service Fabric scenarios, including port reservation and firewall configuration.
  • Provide Linux-specific examples (e.g., how to configure Kestrel endpoints and firewall rules on Linux).
  • Clarify which features are Windows-only (such as HTTP.sys) and offer alternative approaches for Linux users.
  • Include troubleshooting tips for Linux/macOS environments, especially for common issues like port conflicts or permissions.
  • Balance the order of presentation so that cross-platform solutions (Kestrel) are discussed before Windows-only solutions (HTTP.sys), or clearly mark Windows-only sections.
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_tools ⚠ī¸ windows_first
Summary
The documentation page provides detailed examples for reporting health in Service Fabric using C# APIs and PowerShell, with all shell-based examples using PowerShell cmdlets and Windows-style prompts. There are no CLI or shell examples for Linux/macOS users (e.g., Azure CLI, Bash, or cross-platform tools), and PowerShell is presented as the primary scripting interface. REST is mentioned but not exemplified. This creates friction for Linux/macOS users, who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add equivalent examples using Azure CLI (az sf) or Bash scripts for common health reporting tasks.
  • Explicitly mention cross-platform alternatives to PowerShell for interacting with Service Fabric clusters.
  • Provide REST API request examples (e.g., using curl) for health reporting, with sample payloads.
  • Clarify which PowerShell cmdlets are available cross-platform (PowerShell Core) and which are Windows-only.
  • Reorder sections or provide parallel examples so that REST or CLI options are presented before or alongside PowerShell.
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 describes Azure Service Fabric terminology and concepts. While it is intended to be cross-platform, there are several instances where Windows-specific tools and patterns are mentioned first or exclusively. For example, the 'Node' definition references an auto-start Windows service and Windows executables (FabricHost.exe, Fabric.exe, FabricGateway.exe) without mentioning Linux equivalents or patterns. The code package section refers to EXE/DLL files, which are Windows-centric, and does not clarify Linux support or file types. However, the page does acknowledge Linux support in container and guest executable sections, and mentions development clusters for Windows, Linux, and Mac.
Recommendations
  • Add Linux-specific terminology and examples where Windows executables or services are mentioned (e.g., clarify what runs on Linux nodes, such as systemd services or relevant binaries).
  • When describing code packages, mention Linux executable formats (e.g., ELF binaries) and clarify that Service Fabric supports both Windows and Linux code types.
  • Ensure that descriptions of node startup and service management reference both Windows and Linux mechanisms.
  • Where Windows tools or patterns are referenced, provide Linux equivalents or note differences in operation.
  • Consider alternating the order of Windows and Linux mentions 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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Visual Studio workflows, which are primarily Windows-centric. All examples and instructions reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish), with no mention of Linux/macOS equivalents or alternative tooling. There are references to PowerShell modules for service creation, but no Linux CLI or cross-platform alternatives are discussed. The documentation does not provide guidance for Linux/macOS users on how to achieve similar outcomes, nor does it clarify whether StartupServices.xml can be used outside Visual Studio/Windows environments.
Recommendations
  • Add explicit guidance for Linux/macOS users, including whether StartupServices.xml is supported outside Visual Studio and on non-Windows platforms.
  • Provide examples using Azure CLI, Service Fabric CLI (sfctl), or other cross-platform tools for service deployment and configuration.
  • Clarify limitations or alternative workflows for users developing Service Fabric applications on Linux/macOS.
  • Mention any relevant SDK or tooling for Linux/macOS, or state if the feature is Windows-only.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
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, or REST API usage). There is no guidance for non-Windows environments, which may create friction for developers working on Linux or macOS.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI, Bash, or REST API to support Linux/macOS users.
  • Clarify whether the Fault Analysis Service APIs can be used from non-Windows environments and provide relevant instructions.
  • Mention cross-platform SDKs or tools (if available) and how to install/use them on Linux/macOS.
  • If PowerShell Core (pwsh) is supported, specify its usage for Linux/macOS.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 disks, but consistently uses Windows-centric values (e.g., 'Win2016Datacenter' as the VM image) in all CLI and PowerShell scripts. PowerShell (a Windows-first tool) is given equal prominence to Azure CLI, and there are no explicit Linux-specific examples or guidance for deploying Linux VMs or using Linux admin credentials. The documentation does not show how to use Linux images, nor does it clarify how Linux users should adapt the examples. This creates friction for Linux/macOS users, who may be unfamiliar with Windows defaults or PowerShell.
Recommendations
  • Add explicit Linux VM deployment examples in the Azure CLI sections (e.g., use 'UbuntuLTS' or another Linux image for the --image parameter, and show SSH key authentication).
  • Clarify in the variable initialization sections how to set up admin credentials for Linux VMs (e.g., using --authentication-type ssh and --ssh-key-values).
  • Where PowerShell is presented, consider also referencing Bash scripting for parity, or clarify that PowerShell is primarily for Windows users.
  • In the 'Next steps' section, ensure Linux links/examples are as prominent as Windows ones.
  • Consider reordering examples to show Azure CLI (cross-platform) before PowerShell, and ensure Linux VM deployment is not an afterthought.
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 examples for Azure Portal, Azure CLI, Azure PowerShell, and Resource Manager templates. While Azure CLI examples use Linux-friendly commands and Ubuntu images, PowerShell is heavily featured, and Resource Manager template examples are shown exclusively with PowerShell commands. Windows-specific tools (PowerShell) and Windows VM images are used in PowerShell and ARM template sections, and Windows is prioritized in some example flows. There are no Linux-specific ARM template or bash examples, and PowerShell is used for feature registration and deployment, potentially creating friction for Linux/macOS users.
Recommendations
  • Add bash or shell script equivalents for ARM template deployment and feature registration, using Azure CLI.
  • Provide ARM template deployment examples using Azure CLI (az deployment group create) instead of only PowerShell.
  • Ensure that Linux VM images are used in at least some PowerShell and ARM template examples, or clarify that Windows images are optional.
  • Where PowerShell is used for feature registration, add Azure CLI equivalents.
  • In sections where Windows tools are mentioned first, alternate the order or clarify cross-platform options.
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Medium 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 PowerShell and Azure CLI, but the custom RBAC role section links only to a PowerShell-based guide. Additionally, PowerShell is mentioned before CLI in the NetworkAccessPolicy configuration section, and the custom role link uses '/custom-roles-powershell', suggesting a Windows-first approach. Linux users may need to search for CLI or ARM template equivalents.
Recommendations
  • Add links to custom RBAC role creation using Azure CLI and/or ARM templates, not just PowerShell.
  • Ensure CLI and PowerShell examples are presented together or with CLI first, as CLI is cross-platform.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI.
  • Where possible, provide direct CLI commands or scripts for key actions.
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 PowerShell examples and scripts for enabling Write Accelerator, with detailed step-by-step instructions. Windows-specific tools (Chocolatey, cmd.exe, PowerShell) are referenced for installing armclient, with no mention of Linux/macOS alternatives. PowerShell instructions are presented before Azure CLI, and the REST API section assumes Windows environments for installation. While the feature is cross-platform and Linux is referenced in planning and REST API examples, Linux/macOS users may encounter friction due to missing parity in scripting and tool installation guidance.
Recommendations
  • Provide Bash or shell script examples for Azure CLI usage, especially for Linux/macOS users.
  • Include instructions for installing armclient on Linux/macOS (e.g., via npm, direct download, or other package managers).
  • Mention cross-platform alternatives to Chocolatey for package installation.
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize platform neutrality.
  • Clarify that all PowerShell/Chocolatey steps are Windows-specific and offer Linux/macOS equivalents where possible.
GitHub Create Pull Request
Virtual Machines HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs ...main/articles/virtual-machines/hbv3-series-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ recommended_windows ⚠ī¸ missing_linux_example
Summary
The documentation is generally cross-platform and includes both Linux and Windows support. However, there is a notable bias in the 'Recommended OS for Performance' row, which lists only Windows Server 2019+ and does not mention any Linux distributions. Additionally, in the software specifications, Windows is sometimes mentioned first, and there is no explicit Linux example or recommendation for optimal performance, despite Linux being widely used in HPC. The lstopo example is Linux-specific, but there are no equivalent Windows tools or guidance for topology inspection on Windows.
Recommendations
  • Add recommended Linux distributions for performance (e.g., RHEL, Ubuntu, SLES) alongside Windows Server 2019+ in the 'Recommended OS for Performance' row.
  • Where possible, provide parity in examples or guidance for both Linux and Windows users (e.g., suggest a Windows tool for inspecting NUMA topology, or clarify if such inspection is not relevant on Windows).
  • List Linux and Windows support in a consistent order or clarify that both are equally supported.
  • If Windows is recommended for specific workloads, explain why, and provide Linux tuning guidance for parity.
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, frequently references Windows-centric tools and workflows (notably Hyper-V and PowerShell's Convert-VHD) as the primary or sole example for creating and converting VHDs. Linux-native alternatives for creating and converting VHDs are not provided, and instructions for Linux users are minimal or absent in these areas. This creates friction for Linux/macOS users who may not have access to Hyper-V or PowerShell.
Recommendations
  • Provide Linux-native instructions for creating and converting VHD files, such as using qemu-img or VBoxManage.
  • Mention Linux virtualization solutions (e.g., KVM, VirtualBox, QEMU) alongside Hyper-V, and link to relevant guides.
  • Include example commands for extracting and converting VHDs on Linux/macOS, not just Windows.
  • Reorder sections or add parallel instructions so that Linux-native workflows are presented before or alongside Windows/Hyper-V ones.
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 example ('AzCopy.exe copy "c:\somewhere\mydisk.vhd" "sas-URI" --blob-type PageBlob') but does not offer a Linux/macOS equivalent. The AzCopy command is shown only in Windows syntax, and the file path example is Windows-specific. While the rest of the CLI commands are cross-platform, the upload step is Windows-centric, potentially creating friction for Linux/macOS users.
Recommendations
  • Add a Linux/macOS AzCopy example, e.g., 'azcopy copy /home/user/mydisk.vhd "sas-URI" --blob-type PageBlob'.
  • Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
  • Mention that file paths and command syntax differ between Windows and Linux/macOS.
  • Consider showing both Windows and Linux/macOS AzCopy examples side by side.
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 to Windows-specific clustering requirements. There is no mention of Linux clustering solutions (such as Pacemaker, Corosync, or other Linux HA tools), nor are Linux-specific limitations or guidance provided. Windows clustering is discussed as a primary use case for shared disks, suggesting a Windows-centric perspective.
Recommendations
  • Add information about Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
  • Include links to Linux HA documentation and clarify if shared disks are supported for Linux clusters, and under what conditions.
  • Explicitly state if certain limitations only apply to Windows clusters, and provide equivalent Linux guidance where possible.
  • Balance references to Windows Failover Cluster with Linux alternatives, or clarify if shared disks are not intended for Linux clustering scenarios.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs, but PowerShell examples are presented first and in greater detail. This may create friction for Linux users, as PowerShell is not the default or most common scripting environment on Linux. The Azure CLI examples are present and comprehensive, but the ordering and emphasis suggest a Windows/PowerShell bias.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is more native to Linux environments.
  • Clearly indicate that PowerShell examples are optional and primarily for users who have PowerShell Core installed on Linux, or for cross-platform administrators.
  • Add brief notes about the availability and installation of PowerShell on Linux, if PowerShell examples are retained.
  • Ensure that all PowerShell commands are matched with equivalent Azure CLI commands, and vice versa.
  • Consider grouping examples by platform (e.g., 'Azure CLI (Linux/macOS)', 'PowerShell (Windows/Linux)') rather than by tool.
GitHub Create Pull Request
Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Windows and Linux examples for Azure Image Builder, but there are several areas where Windows tools and patterns are emphasized or presented first. PowerShell is frequently referenced for checksum generation and image build operations, sometimes without equal prominence for Linux equivalents. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux customizers (Shell) are covered but with less depth. Windows tools (Get-FileHash, PowerShell commands) are often mentioned before Linux tools (sha256sum, bash), and some example sections (e.g., validation) show Windows examples first.
Recommendations
  • Ensure Linux commands (e.g., sha256sum) are always mentioned alongside Windows commands (e.g., Get-FileHash), and vice versa.
  • Alternate the order of Windows and Linux examples so Linux is not always second.
  • Provide equal detail and troubleshooting guidance for Linux customizers and validators as is given for Windows.
  • Where PowerShell is referenced for operations (e.g., build, cancel), highlight Azure CLI as the primary cross-platform tool, and clarify that PowerShell is optional.
  • Add explicit Linux troubleshooting sections or links, similar to Windows-focused troubleshooting.
  • Where Windows customizers (WindowsRestart, WindowsUpdate) are described, clarify Linux alternatives or limitations.
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_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is primarily focused on Linux VMs, but several sections introduce Windows-centric tools and patterns. PowerShell examples are given equal prominence to Azure CLI, and Windows-specific terminology (such as PowerShell cmdlets, SAS token generation via PowerShell, and references to Windows VM behaviors) appear throughout. REST API and ARM template examples use PowerShell script syntax (Write-Host, .ps1) even in Linux contexts, and some notes reference Windows VM-specific requirements. The PowerShell section is extensive, and PowerShell is presented as a main management tool for Linux VMs, which may not align with typical Linux admin workflows.
Recommendations
  • Where REST API and ARM template examples are given, use Linux shell script syntax (e.g., bash, sh) instead of PowerShell (e.g., Write-Host, .ps1) for Linux VM scenarios.
  • Clarify when PowerShell examples are for Windows VMs only, and provide bash or shell script equivalents for Linux VMs.
  • Move Azure CLI examples before PowerShell examples, as CLI is more native to Linux workflows.
  • When referencing SAS token generation, provide az CLI equivalents (e.g., az storage blob generate-sas) alongside PowerShell commands.
  • Remove or clearly separate Windows-specific notes (such as 'Secondary Logon' service) from Linux instructions.
  • Expand troubleshooting and scripting examples to show Linux-native commands and patterns (e.g., using bash, sh, or Python).
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides examples and configuration snippets for both Windows (ClusterManifest.xml under <WindowsServer>) and cross-platform/standalone (ClusterConfig.json) deployments. However, Windows-specific configuration (ClusterManifest.xml with <WindowsServer>) is presented first and more prominently, and PowerShell examples are included without Linux CLI equivalents. There is a mild bias toward Windows tools and patterns, but Linux/standalone parity is generally maintained.
Recommendations
  • Present Linux/standalone configuration examples (ClusterConfig.json) before or alongside Windows-specific examples.
  • Include CLI examples for Linux/macOS users (e.g., Azure CLI, Bash scripts) where PowerShell examples are given.
  • Clarify which examples apply to Windows-only deployments and which are cross-platform.
  • Add explicit notes or links for Linux/macOS users about how to perform equivalent tasks.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page for Service Fabric reliable services app manifest examples shows mild Windows bias. It references Windows-specific tools (e.g., ServiceFabric PowerShell module), uses Windows-centric terminology (e.g., 'Setup.bat', 'exe'), and describes user accounts and groups in a way that aligns with Windows conventions (e.g., 'Administrators', 'NetworkService'). Linux equivalents or cross-platform guidance are not provided, and Windows tools are mentioned before any alternatives.
Recommendations
  • Add Linux-specific examples or clarify cross-platform support for Service Fabric manifest features.
  • Mention Linux deployment tools (e.g., CLI, Bash scripts) alongside PowerShell, or clarify if PowerShell is required on Linux.
  • Provide guidance on user/group principals for Linux clusters, including mapping to Linux system users/groups.
  • Include notes or examples for running setup scripts in Linux environments (e.g., using .sh files instead of .bat).
  • Clarify any platform-specific limitations or behaviors for Service Fabric manifest elements.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell examples are often presented before CLI examples, and some sections (such as querying public IPs) show PowerShell commands first or in greater detail. Portal instructions are also included, but there is a slight tendency to present Windows-centric tools (PowerShell) before cross-platform CLI equivalents. No critical features are Windows-only, and Linux parity is generally maintained.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell examples in each section.
  • Ensure all PowerShell examples have equivalent Azure CLI examples, and vice versa.
  • Where possible, clarify that Azure CLI works on Linux/macOS/Windows, and PowerShell is primarily Windows-focused.
  • Add explicit notes or links for Linux/macOS users if any step differs or requires additional setup.
  • Review for any minor omissions of CLI examples and add them for completeness.
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 covers backup and disaster recovery for Azure Managed Disks on both Linux and Windows VMs. However, there is a mild bias toward Windows: Windows tools and mechanisms (like Volume Shadow Service and SQL Server Always On) are mentioned first or in greater detail, while Linux equivalents (such as fsfreeze) are referenced briefly and with less explanation. Some backup consistency concepts are explained primarily in Windows terms, and Windows-specific database examples (SQL Server) are more prominent than Linux alternatives.
Recommendations
  • Provide equally detailed explanations and examples for Linux tools (e.g., expand on fsfreeze usage, mention other Linux backup consistency solutions).
  • Include more Linux-centric database scenarios (e.g., MySQL, PostgreSQL) alongside SQL Server.
  • When discussing application-consistent backups, clarify Linux approaches and limitations, and reference relevant documentation.
  • Ensure parity in example ordering (e.g., mention Linux and Windows tools together, not Windows-first).
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell examples are always present even though the page is Linux-focused. In several sections, PowerShell examples are given equal prominence to CLI, and sometimes appear before or alongside CLI, despite PowerShell being less relevant for Linux users. There are no missing Linux examples, and all tooling is cross-platform, but the inclusion and prominence of PowerShell creates minor friction for Linux users.
Recommendations
  • Prioritize Azure CLI examples and explanations, as CLI is the primary cross-platform tool for Linux users.
  • Move PowerShell examples to secondary sections or appendices, or clearly label them as 'for Windows users or PowerShell users'.
  • Consider removing PowerShell examples from the main flow unless there is a strong use case for PowerShell on Linux.
  • Add explicit notes clarifying that Azure CLI is recommended for Linux and macOS users.
  • Where possible, provide Bash shell script examples for local operations (e.g., checking agent version) and troubleshooting.
GitHub Create Pull Request
Virtual Machines Create an encrypted image version with customer-managed keys .../articles/virtual-machines/image-version-encryption.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and Azure CLI examples for creating encrypted image versions with customer-managed keys, but PowerShell (a Windows-centric tool) is presented first and in greater detail. There is a slight Windows-first bias in the ordering and depth of examples, but Linux users can complete all tasks using the Azure CLI or Portal instructions.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as Azure CLI is fully cross-platform and more familiar to Linux/macOS users.
  • Ensure that CLI and PowerShell sections are equally detailed, with parallel explanations and example complexity.
  • Explicitly state that all steps can be performed on Linux/macOS using the Azure CLI, and link to CLI installation instructions if not already present.
  • Where possible, add Bash shell script snippets for common tasks, especially for VM creation, to further improve Linux parity.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation is overwhelmingly Linux-focused and provides detailed, distribution-specific Linux instructions for expanding disks on Azure VMs. However, there is a single section at the end that introduces a PowerShell script for checking classic VM SKU support for disk expansion without downtime. This script is only provided in PowerShell, with no Azure CLI or Bash equivalent, which may create friction for Linux users who do not use PowerShell.
Recommendations
  • Provide an Azure CLI or Bash equivalent for the PowerShell script that checks classic VM SKU support for disk expansion without downtime.
  • If the check cannot be performed with Azure CLI, explicitly state this and provide guidance for Linux users on how to run the PowerShell script (e.g., via Azure Cloud Shell, which supports PowerShell regardless of OS).
  • Consider moving the PowerShell-only section to an appendix or clearly mark it as optional/advanced for users who require classic VM SKU support.
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 is generally cross-platform and explicitly states applicability to both Linux and Windows VMs. However, there are minor instances of Windows bias: Windows tools and terminology are sometimes mentioned first (e.g., PowerShell and Windows-specific links), Windows partitioning concepts are referenced more heavily, and some links and examples are Windows-centric or listed before Linux equivalents. Linux tools and paths are included but sometimes after Windows references.
Recommendations
  • Ensure that Linux and Windows examples/tools are presented together or in parallel, rather than Windows-first.
  • Where partitioning or disk management is discussed, include Linux-specific references (e.g., parted, fdisk, GPT/MBR links for Linux).
  • When linking to guides (e.g., uploading VHDs), list Linux and Windows options side-by-side, not Windows-first.
  • Expand explanations of disk roles and partitioning to include Linux terminology and tools equally.
  • Review all links and ensure Linux equivalents are provided and equally visible.
GitHub Create Pull Request
Container Instances Configure role permissions for standby pools in Azure Container Instances ...container-instances-standby-pool-configure-permissions.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation primarily uses Azure Portal UI instructions for role assignment, which are platform-neutral but often associated with Windows environments. There is a brief mention of PowerShell and CLI in the context of querying the Runtime View API, but no explicit Linux/macOS command-line examples are provided. The documentation does not exclusively reference Windows tools, but it does not offer parity for Linux/macOS users (e.g., Azure CLI commands for role assignment).
Recommendations
  • Add Azure CLI examples for role assignment alongside portal instructions, as CLI is cross-platform and widely used on Linux/macOS.
  • Provide explicit Azure CLI or REST API examples for querying the Runtime View API, rather than referencing PowerShell or CLI generically.
  • Clarify that all instructions are applicable regardless of OS, and highlight cross-platform tools where possible.
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 in the ordering and emphasis: Windows container runtimes and tools (Mirantis Container Runtime, DockerEE) are listed in detail, while Linux only mentions Docker. Windows scenarios (IIS lift and shift) are described before Linux scenarios, and Windows links are sometimes presented before Linux equivalents. The documentation references Windows-specific tools and patterns (IIS, Windows Server containers) more prominently.
Recommendations
  • Ensure Linux and Windows examples/tutorials are presented in parallel or with equal prominence.
  • Expand Linux-specific scenarios (e.g., NGINX, Apache, Linux-based microservices) to match Windows-specific examples like IIS.
  • List Linux container runtimes and tools (e.g., containerd, Podman) if supported, not just Docker.
  • When describing container capabilities, clarify which features are available on Linux vs. Windows.
  • Avoid listing Windows tools or runtimes before Linux equivalents unless there is a technical reason.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates mild Windows bias. It references the Service Fabric SDK schema location using a Windows file path and mentions Visual Studio as a packaging/deployment tool before command-line utilities. There are no explicit Linux/macOS examples or references to cross-platform tools, and the directory structure example uses a Windows executable (.exe), which may imply Windows-centric workflows.
Recommendations
  • Add explicit Linux/macOS examples for packaging and deploying guest executables, including references to cross-platform tools.
  • Mention the location of Service Fabric SDK schema files on Linux/macOS, if available, or clarify if the SDK is Windows-only.
  • Provide guidance for using command-line utilities on Linux/macOS, and ensure parity with Visual Studio instructions.
  • Use neutral file extensions (e.g., .sh, .jar, .out) in directory structure examples, or clarify that .exe is just one possible format.
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 Service Fabric CLI (sfctl) examples for deploying Docker Compose files, but PowerShell commands are presented first and in greater detail. This may create a perception that Windows/PowerShell is the primary or preferred environment, even though cross-platform CLI alternatives are available. There is no explicit Linux/macOS bias, but the ordering and emphasis favor Windows users.
Recommendations
  • Present Service Fabric CLI (sfctl) examples before or alongside PowerShell examples, as sfctl is cross-platform and works on Linux/macOS.
  • Explicitly mention that sfctl is recommended for Linux/macOS users and provide installation instructions or a link.
  • Ensure parity in the level of detail for both PowerShell and sfctl command examples.
  • Add a note clarifying that PowerShell commands are for Windows users, while sfctl is suitable for all platforms.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ minor_windows_tools
Summary
The documentation covers both Windows and Linux VM Scale Sets, but there is a mild Windows bias in example ordering and tooling. Windows/PowerShell examples are often presented before Linux/Azure CLI equivalents, and ARM/Bicep template snippets default to Windows images. However, Linux support is clearly described, and CLI examples are provided throughout. No critical Linux gaps are present.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples so Linux users see their preferred tooling first in some sections.
  • Provide ARM/Bicep template snippets that default to a Linux image (e.g., Ubuntu) alongside the Windows example.
  • Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Where possible, clarify that all features and examples apply equally to Linux and Windows unless otherwise noted.
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, PowerShell examples are shown before or with equal prominence to CLI. The Application Health extension examples use 'ApplicationHealthWindows' in PowerShell, while CLI uses 'ApplicationHealthLinux', but there is no explicit explanation or parity guidance for Linux/macOS users regarding PowerShell alternatives or cross-platform scripting. Additionally, the portal instructions reference screenshots and steps that may be more familiar to Windows users, but do not exclude Linux/macOS users.
Recommendations
  • Clarify that Azure PowerShell is cross-platform, but provide explicit guidance for Linux/macOS users (e.g., installation links, usage notes).
  • Ensure that CLI examples are presented before PowerShell, as Azure CLI is natively cross-platform.
  • Add notes or links for Linux/macOS users on how to use Azure CLI and PowerShell in their environments.
  • Where extensions differ (e.g., ApplicationHealthWindows vs ApplicationHealthLinux), explain the distinction and provide both examples in each scripting section.
  • Consider including Bash shell scripting examples for common automation scenarios.
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations (attach, detach, move), but PowerShell examples are always present and shown alongside CLI. Azure PowerShell is a Windows-centric tool, and its inclusion in every section, with detailed parameters, may signal a Windows bias. Additionally, PowerShell examples are sometimes more elaborate than their CLI counterparts. However, Azure CLI is cross-platform and is included throughout, mitigating the bias. No Windows-only tools or patterns are mentioned, and Linux users can complete all tasks using Azure CLI.
Recommendations
  • Consider clarifying that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
  • If possible, provide Bash shell scripting examples for common scenarios (e.g., chaining CLI commands, error handling) to further support Linux users.
  • Review the order of examples: consider listing Azure CLI before PowerShell to emphasize cross-platform parity.
  • Explicitly state that Azure PowerShell is primarily for Windows users, and that Azure CLI is suitable for all platforms.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
Although the introduction claims Service Fabric clusters run on both Windows Server and Linux, the documentation page only provides details and examples for Windows environments. The 'Supported operating systems' section explicitly states that Linux isn't yet supported for standalone clusters, and all security and scaling guidance is Windows-centric. There are no Linux-specific instructions, examples, or parity guidance.
Recommendations
  • Clarify at the start that standalone clusters are currently Windows-only, despite the general Service Fabric support for Linux.
  • Remove or revise statements suggesting Linux support for standalone clusters if not yet available.
  • When Linux support becomes available, add equivalent Linux instructions, examples, and security guidance.
  • Consider linking to Linux cluster documentation or providing a roadmap/status update for Linux support.
GitHub Create Pull Request
Virtual Machine Scale Sets Azure Virtual Machine Scale Sets Attached Data Disks ...cale-sets/virtual-machine-scale-sets-attached-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Windows and Linux examples for preparing attached data disks in Azure Virtual Machine Scale Sets, but the Windows example is presented first. Both Azure CLI and PowerShell tutorials are linked, and the custom script extension examples are given for both OS types. There are no missing Linux examples or exclusive mention of Windows tools.
Recommendations
  • Present Windows and Linux examples side-by-side or alternate their order to avoid implicit prioritization.
  • Explicitly mention that both Windows and Linux are supported in the introductory sections.
  • Ensure parity in detail and clarity between Windows and Linux instructions.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ minor_windows_template_bias
Summary
The documentation provides both Windows and Linux parity in most command-line and portal instructions, but there are minor signs of Windows bias: PowerShell examples are always present and sometimes more detailed, and the ARM template example is Windows-centric (defaulting to Windows images and OS versions). However, the CLI examples use Ubuntu images and the documentation explicitly states it applies to both Windows and Linux VMs. No critical Linux gaps are present.
Recommendations
  • In ARM template examples, include a Linux image option or show how to switch the image to a Linux distribution, or provide a Linux-focused template tab.
  • When showing PowerShell examples, ensure Bash or CLI examples are equally detailed and shown first or in parallel.
  • In the ARM template parameters, add Linux OS SKU options and clarify how to deploy a Linux VM.
  • Consider alternating the order of CLI and PowerShell tabs or defaulting to CLI (which is cross-platform) to avoid subtle Windows-first bias.
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 presents Windows operating system support details before Linux, but provides parity in information for both platforms. No Windows-specific tools or examples are given, and Linux support is clearly described. The 'Next steps' section references CLI, Portal, and PowerShell, but does not prioritize Windows tools or omit Linux equivalents.
Recommendations
  • Consider presenting Linux and Windows operating system support in parallel or alphabetical order to avoid perceived prioritization.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users, if not already clear in linked pages.
  • Ensure that linked 'PowerShell' and 'CLI' documentation provide Linux/macOS examples where relevant.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides parity between Azure CLI and PowerShell for all major tasks (setting, updating, monitoring, canceling, and restarting rolling upgrades). However, PowerShell examples are consistently included alongside CLI, and in some sections, PowerShell is presented immediately after CLI, which may subtly reinforce Windows-centric workflows. There are no Linux-specific examples, but the Azure CLI is cross-platform and is presented first in most cases. No Windows-only tools or patterns are mentioned, and all features described are platform-agnostic.
Recommendations
  • Explicitly note that Azure CLI commands work equally on Linux, macOS, and Windows.
  • Consider adding brief Bash shell scripting examples for common automation scenarios, highlighting Linux/macOS workflows.
  • Clarify that PowerShell examples are for Windows and PowerShell Core users, while CLI is recommended for cross-platform use.
  • If possible, add a section or note about using Azure CLI in Bash or zsh shells, and reference installation instructions for Linux/macOS.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring custom metrics and the application health extension. However, there are several instances where Windows/PowerShell examples are presented first or in greater detail. Windows-specific extension types (ApplicationHealthWindows) are used in some code snippets and REST examples, sometimes without clear Linux alternatives. PowerShell scripts are more elaborate and detailed than Bash examples, and Windows tools (PowerShell cmdlets) are featured prominently alongside Azure CLI and REST. Linux examples are present but sometimes less detailed or not shown first.
Recommendations
  • Ensure Linux examples (using ApplicationHealthLinux) are shown alongside or before Windows examples in all relevant code snippets and REST payloads.
  • Provide equally detailed Bash/Python scripts for Linux as are provided for PowerShell/Windows.
  • Clarify in REST and extension configuration sections that both ApplicationHealthLinux and ApplicationHealthWindows are supported, and show both in sample payloads.
  • Where possible, avoid presenting Windows/PowerShell examples first unless there is a clear reason (e.g., user base data).
  • Expand troubleshooting and verification sections to include Linux-specific commands and scenarios.
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 cross-platform, referencing both Windows and Linux VM options and pricing. However, there is a minor bias where Windows-specific recommendations (e.g., 'Use at least B2 for Windows machines') are mentioned before Linux equivalents, and Windows pricing links are listed before Linux pricing links. No critical sections are Windows-only, and Linux users can complete all tasks described.
Recommendations
  • When mentioning VM sizing recommendations, provide equivalent guidance for Linux VMs (e.g., 'Use at least B2 for Linux machines' if applicable).
  • When linking to pricing pages, list both Windows and Linux links together or alternate their order to avoid Windows-first bias.
  • Ensure automation and scheduling examples reference cross-platform tools (e.g., Azure Automation, Logic Apps) without implying Windows-only usage.
  • Review for any implicit assumptions about Windows usage and clarify when recommendations apply to both platforms.
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 references both DiskSpd (Windows) and FIO (Linux) as benchmarking tools. However, DiskSpd (Windows) is mentioned first, and the overall tone and example setup (such as host caching configuration) may be more familiar to Windows users. The actual benchmarking examples are not shown in this excerpt, but the structure suggests Windows tools and patterns are prioritized.
Recommendations
  • Ensure Linux benchmarking examples (using FIO) are provided alongside Windows examples, with equal detail and visibility.
  • Alternate the order of tool presentation (sometimes mention FIO first) to avoid Windows-first bias.
  • Clarify any differences in disk setup or caching configuration for Linux users, as terminology and tooling may differ.
  • Explicitly state that both DiskSpd and FIO are equally supported and provide links to Linux-specific guidance where relevant.
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 PowerShell and Azure CLI examples for key tasks, but PowerShell examples are often presented before CLI (which is more cross-platform). References to the Azure portal, PowerShell, and CLI are generally balanced, but PowerShell is sometimes prioritized. The 'Next steps' section lists Linux and Windows resources separately, but the PowerShell (Windows) example appears before the CLI (Linux) example in some places.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and encourage its use for cross-platform scenarios.
  • Where possible, add Bash or shell script examples alongside PowerShell, especially for disk operations.
  • Ensure that links and instructions for Linux/macOS users are as prominent and accessible as those for Windows 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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ minor_windows_tools
Summary
The documentation generally maintains parity between Windows and Linux, providing links to both PowerShell (Windows) and CLI (Linux) guides for most procedures. However, there are several instances where Windows/PowerShell links or references are listed before their Linux/CLI equivalents, and some cross-references (such as for automatic key rotation) point only to a Windows/PowerShell-specific article. There is also a slight emphasis on PowerShell for certain tasks, with CLI mentioned second or as an alternative.
Recommendations
  • Ensure that all procedural links (such as enabling automatic key rotation) are provided for both Windows/PowerShell and Linux/CLI, or clarify if a feature is only available via one tool.
  • When listing options (e.g., PowerShell and CLI), alternate the order or present them together (e.g., 'using PowerShell or CLI') to avoid a consistent Windows-first pattern.
  • Where possible, provide direct Linux/CLI examples or links alongside PowerShell, especially for critical workflows.
  • Review references to Windows-specific tools or documentation (such as Cryptography API: Next Generation) and, if relevant, add Linux equivalents or clarify their applicability.
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 PowerShell examples for all disk types, but PowerShell (a Windows-centric tool) is given equal prominence and sometimes appears first in sections. There are no Linux-specific command-line examples (e.g., Bash, shell scripting), and no mention of Linux-native tools for disk management. However, Azure CLI is cross-platform and all steps can be completed on Linux/macOS. The documentation does not use Windows-only tools or patterns, but the heavy use of PowerShell and its parity with Azure CLI may create friction for Linux users.
Recommendations
  • Consider showing Azure CLI examples before PowerShell, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly note that Azure CLI commands can be run on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
  • Add brief Bash shell scripting examples for disk operations where relevant, or clarify that Azure CLI is the recommended tool for Linux/macOS.
  • Where PowerShell is used, clarify its platform support and recommend Azure CLI for Linux/macOS users.
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 generally platform-neutral, focusing on Azure Disk Storage features and regional availability. However, there are minor instances of Windows bias: some links and references point to Windows-specific documentation first or exclusively (e.g., 'expand with Ultra Disks and Premium SSD v2' links to a Windows article, and 'find unattached disks' links to a Windows page). The mention of Azure PowerShell in the context of disk properties is not accompanied by explicit Linux CLI parity, though Azure CLI is referenced elsewhere. No critical features are described as Windows-only, and Linux equivalents are usually available or referenced, but sometimes after Windows.
Recommendations
  • Ensure that all feature documentation links reference both Windows and Linux guides equally, or provide a platform-neutral landing page.
  • When referencing tools (e.g., Azure PowerShell), also mention Azure CLI or other cross-platform tools, and provide examples for both.
  • Where possible, avoid linking to Windows-specific documentation unless the feature is Windows-only; otherwise, include Linux/macOS links alongside.
  • Review the order of examples and links to avoid consistently showing Windows first.
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 VM scenarios for ephemeral OS disks and provides parity in technical explanations and examples. However, there is a mild Windows bias in the ordering of examples and references: Windows Server image sizing is discussed first in the 'Size requirements' section, and PowerShell is mentioned before CLI in the 'Customer Managed key' section. Both Linux and Windows tools are referenced, but Windows examples and tools tend to appear first.
Recommendations
  • Alternate the order of Linux and Windows examples in sections where both are relevant, or present them side-by-side.
  • In the 'Customer Managed key' section, mention Azure CLI and PowerShell together, or list CLI first for Linux parity.
  • Ensure that Linux-specific considerations (such as image sizing, disk placement, and OS disk management) are given equal prominence and detail as Windows examples.
  • Where possible, provide explicit Linux command examples alongside Windows/PowerShell examples.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on Linux, but several sections (notably deployment and troubleshooting) present Windows-centric tools (Azure PowerShell) before Linux-native equivalents (Azure CLI). PowerShell examples are detailed and appear before CLI examples, and troubleshooting references Azure PowerShell first. There is also a reference to a Windows-specific Key Vault access policy guide in the template deployment section. However, Linux-specific instructions, paths, and concepts are well covered, and CLI parity is generally maintained.
Recommendations
  • Present Azure CLI examples before Azure PowerShell examples, as CLI is cross-platform and native to Linux.
  • Clarify that Azure PowerShell is optional and not required for Linux users.
  • Remove or supplement references to Windows-specific guides (e.g., Key Vault access policy for Windows VM) with Linux equivalents.
  • Expand troubleshooting to highlight CLI commands and Linux-native log analysis tools before PowerShell.
  • Consider adding a short section explaining the difference between PowerShell and CLI for Linux users, emphasizing CLI as the preferred tool.
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 disk features. However, in the 'Sample workloads' section, Windows examples are presented first and in greater detail, with more application scenarios and links than Linux. Linux examples are present and include supported distributions, cluster managers, and utilities, but are less extensive and detailed compared to Windows. The performance throttles and reservation flow sections are neutral and apply to both OSes.
Recommendations
  • Expand the Linux sample workloads section to include more detailed application scenarios, similar to the Windows section (e.g., clustered databases, file servers, SAP workloads).
  • Add links to Linux-specific templates or guides for deploying clustered file servers, SAP Central Services, or other common Linux workloads using shared disks.
  • Ensure that Linux examples and tools are presented with equal detail and prominence as Windows examples.
  • Consider alternating the order of Windows and Linux sections or presenting them side-by-side for parity.
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 primarily focused on Linux, as indicated by the title and content. However, in the deployment section, PowerShell examples are presented before Azure CLI examples, and PowerShell is a Windows-centric tool. There is also mention of an extension for Windows VMs, but this is appropriately referenced as a cross-link. The troubleshooting section also includes PowerShell commands before Azure CLI. All other examples, instructions, and screenshots are Linux-specific, and Linux tools and commands are used throughout.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more relevant for Linux users.
  • Clearly label PowerShell sections as 'Windows only' or 'for Windows users', and Azure CLI as 'cross-platform'.
  • Consider removing or minimizing PowerShell examples unless there is a strong use case for Linux administrators using PowerShell.
  • Ensure troubleshooting commands prioritize Azure CLI and Linux-native tools.
GitHub Create Pull Request
Virtual Machines Deprovision or generalize a VM before creating an image ...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Linux and Windows instructions for generalizing/deprovisioning VMs before imaging. However, the Windows section presents PowerShell examples and Windows-specific registry/configuration steps, and the Windows example for marking a VM as generalized uses PowerShell, while the Linux example uses Azure CLI. The Windows section appears after the Linux section, but the PowerShell example is shown for Windows without an Azure CLI equivalent. There is minor bias in tool selection and example parity.
Recommendations
  • Provide Azure CLI examples for Windows VM generalization alongside PowerShell examples, ensuring parity with Linux instructions.
  • Mention that both Azure CLI and PowerShell can be used for marking VMs as generalized, and link to relevant documentation for both.
  • Consider including a note that Linux users can use PowerShell Core if desired, and Windows users can use Azure CLI.
  • Ensure that the documentation structure and tool recommendations are balanced between platforms.
GitHub Create Pull Request
Virtual Machines What's New in Azure VM Image Builder ...ual-machines/image-builder-api-update-release-notes.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for HTTP, Azure CLI, and Azure PowerShell when demonstrating how to pin to an older API version. PowerShell is a Windows-centric tool, and its inclusion alongside cross-platform tools (CLI and HTTP) is common, but the PowerShell example is given equal prominence. Additionally, in sections describing validation support, PowerShell (Windows) is mentioned separately and with more detail than Shell (Linux), including options like 'run elevated' and 'run as system' that are Windows-specific. However, the overall documentation is balanced, with frequent references to Linux, and most features and examples are not Windows-exclusive.
Recommendations
  • Ensure that Linux shell examples are as detailed as Windows PowerShell examples, especially regarding script execution options.
  • Consider listing cross-platform tools (HTTP, Azure CLI) before Windows-specific tools (PowerShell) in example tabs.
  • Where PowerShell-specific options are described, clarify their Linux equivalents or explicitly state if no equivalent exists.
  • Add explicit Bash or shell script examples where PowerShell examples are given, to reinforce Linux parity.
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides parity between Windows and Linux in most sections, including CLI, REST, and portal instructions. However, PowerShell examples are shown with Windows as the default, and Windows is mentioned first in some contexts. The PowerShell section uses Windows as the primary example, with Linux only referenced as an alternative. Additionally, PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • In PowerShell examples, provide Linux-focused examples or clarify that PowerShell can be used cross-platform.
  • Ensure that Linux and Windows examples are balanced in order and prominence, especially in scripting sections.
  • Add explicit notes about using Azure CLI and REST for Linux/macOS users, and highlight their parity.
  • Consider including Bash or shell script examples where appropriate, or link to Linux-specific guidance.
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 Linux VMs, with all technical instructions, examples, and requirements tailored for Linux distributions. However, in several places, Azure PowerShell is mentioned alongside Azure CLI as a management tool for Linux VMs, and PowerShell examples/scripts are referenced equally with CLI ones. In the 'Next steps' section and introductory guidance, PowerShell is listed after CLI, but its inclusion may cause minor confusion for Linux users, since PowerShell is less commonly used on Linux compared to CLI/bash. No Windows-specific tools, patterns, or examples are prioritized or exclusively presented.
Recommendations
  • Clarify that Azure PowerShell is cross-platform and can be used on Linux, but Azure CLI is generally preferred for Linux VM management.
  • Consider providing guidance on installing and using PowerShell on Linux, or explicitly recommend Azure CLI as the default for Linux users.
  • Ensure that PowerShell references are not presented as primary or default for Linux scenarios, and that CLI/bash examples are always shown first.
  • If PowerShell scripts are referenced, add a note about their Linux compatibility and any prerequisites.
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 is focused on Azure Disk Encryption for Linux VMs and provides parity between Azure CLI and Azure PowerShell examples throughout. However, PowerShell cmdlets and patterns are often mentioned first, especially in critical backup and encryption steps, and some explanations reference PowerShell-specific behaviors (e.g., sequence version requirements) before CLI equivalents. There is also frequent use of PowerShell terminology and links, which may create friction for Linux users unfamiliar with PowerShell.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is more native to Linux environments.
  • Clarify that PowerShell can be run cross-platform, but highlight CLI as the default for Linux users.
  • Where PowerShell-specific requirements are discussed (e.g., sequence version), provide equivalent CLI explanations in parallel.
  • Reduce references to PowerShell-specific backup patterns unless they are equally relevant for CLI users.
  • Add explicit notes or guidance for Linux users who may not use PowerShell, including links to CLI documentation and troubleshooting.
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 sync in Azure and provides comprehensive Linux-specific guidance, examples, and tools. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific content. No PowerShell or Windows-only tools are used for Linux configuration, except for a single PowerShell snippet for base64 encoding cloud-init (which is relevant for Azure users on Windows). All configuration and troubleshooting examples are Linux-centric.
Recommendations
  • Move the Windows Server 2016 discussion and links to a background section or an appendix, emphasizing Linux-specific mechanisms first.
  • Provide a Linux shell command alternative for base64 encoding cloud-init (e.g., `base64 cloud-config.txt`) alongside the PowerShell example.
  • Clarify that the Windows references are for Azure host context, not VM configuration, to avoid confusion.
  • Ensure Linux examples and tools are always presented first and Windows references are secondary or contextual.
GitHub Create Pull Request
Virtual Machines Create and upload a Red Hat Enterprise Linux VHD for use in Azure ...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation covers multiple hypervisors (Hyper-V, KVM, VMware, Kickstart) for preparing Red Hat Enterprise Linux VHDs for Azure. However, in most sections, instructions for Hyper-V (a Windows-centric hypervisor) are presented first, and references to Windows tools (e.g., Hyper-V Manager) appear before Linux-native alternatives. All major Linux workflows (KVM, VMware, Kickstart) are thoroughly documented, but the ordering and some phrasing subtly prioritize Windows/Hyper-V environments.
Recommendations
  • Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, rather than always after.
  • Explicitly state that all workflows are equally supported, and avoid implying Hyper-V is the default or preferred option.
  • Where possible, provide parity in detail and clarity for Linux-native workflows, ensuring they are as comprehensive as Hyper-V instructions.
  • Consider a summary table at the top listing all supported hypervisors with links to their respective sections, to avoid implicit prioritization.
  • In introductory text, clarify that users can use any of the listed hypervisors and that the order does not imply preference.
GitHub Create Pull Request