← Back to Dashboard
229
Pages Scanned
84
Pages Flagged
229
Changed Pages
36.7%
% Pages Flagged

Scan Information

Started At: 2026-01-30 00:00:07

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

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 229

Files Completed: 229

Problematic Pages

84 issues found
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric reverse proxy clearly states that the reverse proxy feature is not available for Linux clusters. All examples, configuration notes, and usage scenarios are written with Windows clusters in mind, and there are no Linux equivalents or workarounds provided. The page does not offer guidance for Linux users, nor does it clarify alternative approaches for Linux clusters.
Recommendations
  • Add a prominent note at the top of the page clarifying that reverse proxy is Windows-only and suggest alternative communication patterns for Linux clusters.
  • Provide links or references to Linux-compatible Service Fabric features or third-party solutions for service discovery and HTTP routing.
  • If possible, update the documentation when Linux support for reverse proxy becomes available, or maintain a comparison table of feature parity between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ missing_linux_example ⚠️ windows_tools ⚠️ windows_first
Summary
Although the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the documentation and supported OS list indicate that standalone clusters are currently Windows-only. The security section references Windows-specific tools and patterns (Kerberos, Active Directory, group Managed Service Accounts) without Linux equivalents or guidance. No Linux examples, instructions, or supported OS are provided, and Windows terminology is used throughout.
Recommendations
  • Clarify in the introduction that standalone clusters are currently Windows-only, and Linux support is not available yet.
  • Remove or update statements suggesting Linux parity unless Linux support is imminent.
  • If/when Linux support is added, provide equivalent Linux security guidance (e.g., certificate management, authentication patterns) and Linux-specific examples.
  • Explicitly state the lack of Linux support in the 'Supported operating systems' section to avoid confusion.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page consistently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources, without providing equivalent Azure CLI or ARM template examples. This creates friction for Linux/macOS users, as PowerShell is a Windows-centric tool and not always the default or preferred option on non-Windows platforms.
Recommendations
  • Include Azure CLI examples (e.g., az resource delete, az servicefabric managed-cluster application create) alongside PowerShell cmdlets for all management operations.
  • Explicitly mention ARM template usage and provide sample templates or links for common operations.
  • Clarify that Az PowerShell cmdlets can be run cross-platform, but highlight Azure CLI as the primary cross-platform tool.
  • Where possible, order examples so that cross-platform tools (Azure CLI, ARM templates) are shown before or alongside PowerShell examples.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation page demonstrates a notable Windows bias: all code examples use Windows containers and Windows-specific commands (cmd, set, exitCode, etc.), and the only tooling example for querying deployment status is PowerShell. There is no mention of Linux containers, Linux-compatible commands, or equivalent Linux tooling (such as Bash or CLI). The examples and guidance are Windows-centric, which may create friction for users deploying Service Fabric workloads on Linux.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu images) and Linux shell commands.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide Linux-specific code samples.
  • Include instructions for querying deployment status using Azure CLI or Bash, if available.
  • Explicitly state any platform limitations (e.g., if RunToCompletion is Windows-only) at the top of the page.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation references PowerShell cmdlets and Windows security as primary management and security mechanisms, without mentioning Linux equivalents (such as Bash, CLI, or OpenSSL). No examples or tooling for Linux/macOS users are provided, and Windows tools are referenced exclusively in management and security contexts.
Recommendations
  • Include references to Azure CLI, Bash scripts, or REST APIs for cluster management alongside PowerShell cmdlets.
  • Mention Linux-compatible security mechanisms (such as OpenSSL certificates) in addition to Windows security.
  • Add examples or notes for Linux/macOS users on how to perform management and security tasks.
  • Clarify when features or tools are Windows-only, and provide alternatives or guidance for cross-platform scenarios.
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 page exhibits moderate Windows bias. Several examples and explanations reference Windows tools (e.g., PowerShell, netsh), and Windows-centric patterns are described before or in more detail than Linux equivalents. Some sections (such as port usage and API access) mention PowerShell and Windows-specific behaviors without providing equivalent Linux/CLI examples. ARM template and networking guidance is generally cross-platform, but Windows examples and terminology are more prominent.
Recommendations
  • Provide Linux CLI examples alongside PowerShell references, especially for API access and cluster management.
  • When describing port usage or network configuration, clarify differences for Linux clusters and offer Linux-specific commands (e.g., for checking dynamic port ranges).
  • Balance references to Windows tools (e.g., PowerShell, netsh) with Linux alternatives (e.g., bash, iptables, ss/netstat).
  • Ensure that application networking and container guidance includes Linux container scenarios and flags where relevant.
  • Where Windows is mentioned first, alternate or parallel Linux-first examples to improve parity.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation for on-demand backup in Azure Service Fabric is heavily focused on PowerShell and Windows tooling. All command-line examples use PowerShell cmdlets or PowerShell-based REST calls, with no mention of Linux/macOS equivalents (such as Bash, Azure CLI, or curl). The prerequisite section requires installation of a PowerShell module and the use of PowerShell commands to connect to clusters and trigger backups. There is no guidance for users on Linux or macOS platforms, nor are cross-platform alternatives suggested.
Recommendations
  • Add equivalent examples using Bash and Azure CLI (az servicefabric) or curl for REST API calls.
  • Clarify whether the PowerShell module is supported on PowerShell Core (pwsh) on Linux/macOS, and provide installation instructions if so.
  • If REST API calls are platform-agnostic, provide curl or HTTPie examples.
  • Explicitly mention any platform limitations (e.g., if certain modules/tools are Windows-only) and suggest alternatives for Linux/macOS users.
  • Reorder examples or provide parallel examples for both Windows and Linux/macOS users.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation references PowerShell and Visual Studio as primary upgrade tools, both of which are most commonly used on Windows. PowerShell is mentioned as a method for upgrading applications, but there is no mention of Linux/macOS CLI equivalents or cross-platform tooling. The examples and recommendations focus on C# and .NET serialization, which are cross-platform, but the upgrade workflow references Windows-centric tools first.
Recommendations
  • Add instructions or references for upgrading Service Fabric applications using cross-platform CLI tools (e.g., Azure CLI, Service Fabric CLI) where available.
  • Include examples or links for Linux/macOS users to perform upgrades, if supported.
  • Clarify in the documentation if PowerShell and Visual Studio are required due to Service Fabric limitations, or if alternatives exist for non-Windows environments.
  • Consider listing cross-platform options before or alongside Windows-specific tools in the 'Next steps' section.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation on scaling Azure Service Fabric standalone clusters demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a 'scale a standalone cluster' guide that is Windows Server-focused. There are no Linux-specific instructions, examples, or mentions of Linux-compatible tools for managing or scaling standalone clusters, which may create friction for Linux users.
Recommendations
  • Include equivalent Linux command-line instructions (e.g., using sfctl or REST APIs) alongside PowerShell examples.
  • Clarify whether standalone cluster scaling is supported on Linux, and if so, provide Linux/macOS-specific guidance or links.
  • If certain operations are Windows-only, explicitly state this limitation to set user expectations.
  • Add references to cross-platform tools (such as sfctl) where possible, and provide example commands for both Windows and Linux environments.
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_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric Events demonstrates a Windows bias by referencing Windows Event logs, ETW, and the Windows Azure diagnostics agent as the primary mechanisms for accessing events. Linux equivalents or cross-platform instructions are not mentioned, and the examples and tooling described are Windows-centric. This creates friction for Linux/macOS users who may be running Service Fabric clusters on non-Windows environments.
Recommendations
  • Add explicit instructions and examples for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., syslog, journald, or custom log files).
  • Clarify whether the Windows Azure diagnostics agent is required or if there is a Linux-compatible alternative for event forwarding.
  • Include cross-platform guidance for integrating with Azure Monitor logs from Linux clusters.
  • List any differences in event access or monitoring setup between Windows and Linux Service Fabric clusters.
  • Provide REST API usage examples that work identically on all platforms.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides detailed PowerShell examples for managing node tags and service requirements, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). PowerShell is a Windows-centric tool, and its examples are presented before C# API usage, with no mention of Linux-friendly alternatives for command-line operations.
Recommendations
  • Add Azure CLI or REST API examples for managing node tags and service requirements, as these are cross-platform and usable on Linux/macOS.
  • Explicitly mention whether PowerShell commands are available on Linux (via PowerShell Core), and provide installation guidance if so.
  • If PowerShell is not supported on Linux for these commands, clarify this and direct Linux users to supported alternatives.
  • Consider providing Bash or shell script examples where appropriate.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation is notably Windows-centric, focusing exclusively on Visual Studio workflows and referencing Windows-specific tools (e.g., F5/Ctrl+F5, right-click Publish, Visual Studio project templates). There are no examples or guidance for Linux/macOS users or cross-platform tooling, and alternative deployment methods are only briefly mentioned.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide examples using cross-platform tools (e.g., Azure CLI, Service Fabric CLI, or PowerShell Core on Linux/macOS) for tasks currently described with Visual Studio.
  • Clarify which features are Visual Studio/Windows-only and offer parity instructions for non-Windows environments where possible.
  • Include sample workflows for deploying Service Fabric applications using DevOps pipelines or command-line tools on Linux/macOS.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for Service Fabric reliable services app manifest examples demonstrates a mild Windows bias. Example scripts and executables use Windows conventions (e.g., .exe, .bat), and references to user accounts and groups (Administrators, NetworkService) are Windows-centric. There are no explicit Linux equivalents or examples, nor is there guidance for Linux Service Fabric clusters (e.g., using shell scripts, Linux user/group patterns). The only mention of PowerShell is in a comment, but no Linux CLI or Bash alternatives are presented.
Recommendations
  • Include Linux-specific examples, such as using shell scripts (.sh) for SetupEntryPoint and EntryPoint, and referencing Linux user/group conventions.
  • Clarify which manifest elements and patterns are cross-platform, and note any differences for Linux clusters (e.g., user account handling, service startup scripts).
  • Provide parallel examples for Linux deployments, including sample manifests with Linux-style executables and scripts.
  • Explicitly state in relevant sections if certain features or patterns are Windows-only, and link to Linux documentation where available.
GitHub Create Pull Request
Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell examples are significantly more detailed and complex, including full network setup and VM configuration, while the CLI examples are minimal. PowerShell is a Windows-centric tool, and there are no equivalent Bash or Linux shell scripting examples for users who prefer Linux-native automation. Additionally, in several sections, PowerShell examples are presented before CLI, and the CLI examples lack parity in terms of completeness and depth. There are no references to Linux-specific tools or workflows beyond the CLI, and the documentation does not address Linux/macOS users who may wish to automate these tasks outside of PowerShell.
Recommendations
  • Provide full Bash/Linux shell script examples that match the depth and completeness of the PowerShell examples, including network resource creation and VM configuration.
  • Ensure CLI examples are as detailed as PowerShell examples, covering all necessary steps for both Windows and Linux users.
  • Explicitly mention that PowerShell is available cross-platform, but also offer native Linux automation alternatives (e.g., Bash scripts, use of Azure CLI in Linux environments).
  • Alternate the order of CLI and PowerShell examples, or present CLI first to reduce Windows-first perception.
  • Add notes or links for Linux/macOS users on best practices for scripting and automation in those environments.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page primarily references Windows images and provides a PowerShell example for role assignment, with limited mention of Linux equivalents. While it briefly links to Linux instructions for creating custom images and finding marketplace images, the main examples and terminology focus on Windows, and no Linux-specific CLI or shell examples are provided.
Recommendations
  • Add explicit examples and instructions for deploying Linux custom images on Service Fabric Managed Clusters.
  • Provide equivalent Azure CLI or Bash examples for role assignment and other operations, not just PowerShell.
  • Clarify in the introduction that both Windows and Linux images are supported, and structure examples to show parity.
  • Include references to Linux-specific documentation where appropriate, and ensure links are clearly labeled.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page 'Manage certificates in a Service Fabric cluster' demonstrates a notable Windows bias. PowerShell is the only scripting language used for automation examples, and references to Windows-specific tools and extension schemas (e.g., Key Vault VM extension for Windows, S-channel, CERT_RENEWAL_PROP_ID) are prevalent. The documentation does not provide equivalent Linux/macOS automation examples (such as Bash, Azure CLI, or cross-platform SDKs), nor does it mention Linux-specific certificate management patterns or VM extensions. Windows terminology and mechanisms are introduced before any cross-platform alternatives, and some features (like certificate linking) are explicitly described as Windows-only, but without guidance for Linux users.
Recommendations
  • Add automation examples using Bash and Azure CLI for certificate enrollment and management, alongside PowerShell.
  • Clarify which mechanisms (e.g., Key Vault VM extension, certificate linking) are Windows-only and provide Linux/macOS alternatives or workarounds where possible.
  • Reference and link to Linux-specific documentation for Service Fabric clusters, especially for certificate provisioning and rotation.
  • Explicitly state platform limitations for features that are not available on Linux/macOS, and suggest supported cross-platform approaches (e.g., using Azure CLI, REST API, or SDKs).
  • Include notes or sections for Linux/macOS users, outlining differences in certificate storage, access control, and automation.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation page provides detailed conceptual and configuration guidance for X.509 certificate-based authentication in Service Fabric clusters. While it covers both Windows and Linux in some configuration examples, there is a notable Windows bias in troubleshooting and operational guidance: Windows certificate store paths and tools are mentioned first and in detail, Windows event log locations are referenced exclusively, and troubleshooting steps rely on Windows-specific tools (e.g., CAPI2 logging, Win32 CryptoAPI references). Linux equivalents for certificate storage, logging, and troubleshooting are mentioned only briefly or not at all.
Recommendations
  • Add explicit Linux/macOS troubleshooting instructions, including log file locations and relevant commands.
  • Provide Linux/macOS equivalents for certificate store paths (e.g., expand on /var/lib/sfcerts usage and management).
  • Include examples of how to inspect and manage certificates on Linux/macOS (e.g., using openssl, keytool, or systemd journal for logs).
  • Reference cross-platform APIs or tools where possible, or clarify platform-specific differences.
  • Ensure that configuration examples and operational guidance are presented for both Windows and Linux/macOS environments, or clearly indicate when a step is Windows-only.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, without mentioning or providing equivalent Linux/macOS command-line instructions. The use of PowerShell cmdlets and references to Service Fabric Explorer (a Windows-centric tool) further reinforce a Windows bias, making it less accessible for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Provide equivalent Linux/macOS instructions using Service Fabric CLI (sfctl) or REST API where possible.
  • Clarify whether the PowerShell command is required, or if cross-platform alternatives exist.
  • Mention and link to cross-platform management tools (e.g., sfctl, REST API) alongside Service Fabric Explorer.
  • Add explicit notes about platform requirements for any commands or tools.
  • Ensure examples are provided for both Windows and Linux/macOS environments where supported.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias by prioritizing Azure PowerShell examples and references in the 'Best practices' section, listing PowerShell before Azure CLI, and omitting explicit Linux/macOS command-line examples for key operations. While ARM, Bicep, and Azure CLI are mentioned, actionable examples and links focus on PowerShell, which is traditionally Windows-centric, potentially creating friction for Linux/macOS users.
Recommendations
  • Add explicit Azure CLI examples and links for all key operations (e.g., deleting NodeType, restarting/reimaging scale sets) alongside PowerShell.
  • Ensure that CLI examples are shown before or alongside PowerShell, not after.
  • Clarify that Azure CLI and ARM/Bicep templates are fully cross-platform and provide sample commands for Linux/macOS users.
  • Where PowerShell is referenced, note that Azure PowerShell is available cross-platform, but CLI is often preferred on Linux/macOS.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation consistently provides PowerShell examples for command-line operations (add, remove, scale, configure node types), but does not mention or provide equivalent examples for cross-platform tools such as Azure CLI, Bash, or scripting for Linux/macOS users. PowerShell is referenced as the only scripting interface outside of ARM templates and the Portal, and is listed before ARM templates in some sections. There is no mention of Azure CLI, which is widely used on Linux/macOS. This creates friction for non-Windows users who may not have access to or familiarity with PowerShell.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly state that PowerShell examples can be run on any OS using PowerShell Core, or provide Bash scripting equivalents where appropriate.
  • In each section, present Azure CLI and PowerShell examples together, or at least mention both, to avoid Windows-first ordering.
  • Clarify if any operation is only possible with PowerShell and not Azure CLI, and provide guidance for Linux/macOS users in such cases.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, using Windows-specific images (mcr.microsoft.com/windows/nanoserver:1809), Windows file paths (C:\...), and Windows shell commands (cmd, type, ping). There are no Linux container examples, nor any mention of how to use Initializer CodePackages with Linux containers or Linux-based workloads, despite Service Fabric supporting both Windows and Linux containers. The examples and guidance are exclusively Windows-focused, potentially creating friction for Linux users.
Recommendations
  • Add a parallel example using Linux containers (e.g., mcr.microsoft.com/ubuntu or other Linux images), with Linux shell commands and file paths.
  • Clarify in the introduction whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance for Linux users.
  • Where file paths or commands are shown, provide both Windows and Linux equivalents, or note platform-specific differences.
  • Explicitly mention any platform limitations (if Initializer CodePackages are not supported for Linux containers, state this clearly).
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 generally cross-platform manner, but several sections show Windows bias. Windows-specific features (Active Directory, gMSA, BitLocker) are mentioned with no Linux equivalents or with Linux options referenced only briefly or as TODOs. Examples and links often focus on Windows tools and patterns, and Linux-specific instructions (e.g., disk encryption) are missing or deferred. Windows features are sometimes described first or exclusively, creating friction for Linux users.
Recommendations
  • Add explicit Linux examples and instructions where only Windows options are described (e.g., disk encryption for Linux clusters).
  • When mentioning Windows-specific features (e.g., BitLocker, gMSA), clarify Linux alternatives or note platform limitations.
  • Ensure parity in documentation links and examples for both Windows and Linux clusters, especially for common security tasks.
  • Where possible, provide side-by-side guidance for both platforms, or clearly indicate platform-specific sections.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation covers both Windows and Linux clusters, but there is a noticeable tendency to mention Windows tools, features, and examples first or in greater detail. Windows-specific tools like Event Viewer, Diagnostics Agent, and EventStore APIs are highlighted, sometimes with less detail or fewer examples for Linux equivalents. Linux monitoring is referenced, but often as a secondary note or with links out to other pages, rather than inline examples. Some sections (e.g., EventStore APIs, Diagnostics Agent) are Windows-only, but this is generally called out. However, Linux users may need to follow additional links or infer parity, which creates friction.
Recommendations
  • Provide Linux-specific examples and configuration steps inline, especially for key monitoring workflows.
  • When mentioning Windows tools (e.g., Event Viewer, Diagnostics Agent), immediately follow with Linux equivalents (e.g., Syslog, LTTng) and usage instructions.
  • Ensure that sample queries, alert rules, and setup instructions explicitly mention any differences or additional steps for Linux clusters.
  • Add more direct links to Linux-focused tutorials and documentation where parity is not possible in the main text.
  • Consider a summary table comparing Windows and Linux monitoring tools and workflows for Service Fabric.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page primarily describes Service Fabric application and service manifests in a platform-neutral manner, focusing on XML configuration. However, there is a notable Windows bias in the tooling recommendations: the only explicit tool mentioned for authoring manifests is Visual Studio, referencing a Windows file path ("C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd") and suggesting opening it in Visual Studio for IntelliSense and schema validation. Additionally, the PowerShell module is referenced for service creation, with no mention of Linux/macOS equivalents or cross-platform CLI alternatives. No Linux-specific tools, workflows, or examples are provided, and Windows tooling is mentioned first and exclusively.
Recommendations
  • Add instructions for validating and editing manifest XML files on Linux/macOS, such as using VS Code, JetBrains Rider, or command-line XML validators.
  • Reference the location of Service Fabric schema files on Linux installations, if available.
  • Mention cross-platform alternatives to Visual Studio for schema validation and IntelliSense, such as VS Code with XML plugins.
  • Include examples or references for using Azure CLI or Service Fabric CLI (sfctl) for service creation and management, alongside PowerShell.
  • Clarify that PowerShell is available on Linux/macOS, or provide bash/shell equivalents for common tasks.
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 ⚠️ missing_linux_example
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., Remove-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) throughout critical lifecycle operations (deploy, upgrade, remove, cleanup). While REST API and .NET SDK methods are mentioned, there is a notable lack of Linux/macOS-specific CLI examples (such as Azure CLI or sfctl), and PowerShell is often presented as the primary or only command-line interface. This creates friction for Linux/macOS users, who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add explicit examples using sfctl (Service Fabric CLI) and/or Azure CLI for each lifecycle operation alongside PowerShell and .NET SDK references.
  • Clearly indicate which tools are cross-platform and which are Windows-only, helping users choose the appropriate interface.
  • Where PowerShell is referenced, provide equivalent Linux/macOS commands or links to relevant documentation for those platforms.
  • Consider reordering examples so that cross-platform tools (REST API, sfctl, Azure CLI) are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for advanced Service Fabric application upgrade topics is heavily focused on PowerShell-based workflows and examples, with all command-line instructions and code snippets using PowerShell cmdlets. There is no mention of Linux/macOS equivalents (such as Service Fabric CLI or REST API), nor are there examples for non-Windows environments. The documentation implicitly assumes users are operating in a Windows/PowerShell environment, which creates friction for Linux/macOS users who may be using Service Fabric on those platforms.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Where PowerShell cmdlets are referenced, also provide the corresponding REST API calls or CLI commands.
  • Explicitly mention platform compatibility for each tool or command, and guide users to the appropriate tool for their OS.
  • Include notes or sections for Linux/macOS users, especially for common upgrade workflows.
  • Update 'Next steps' to include tutorials for CLI-based upgrades, not just Visual Studio and PowerShell.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for Service Fabric application upgrades demonstrates a notable Windows bias. The only command-line example provided is in PowerShell, and all references to Service Fabric management tools are Windows-centric (PowerShell cmdlets). There are no CLI or Linux/macOS-compatible examples or instructions. Additionally, the documentation references Windows-specific components such as http.sys and error messages from the Windows HTTP Server API, without mentioning Linux equivalents or cross-platform considerations.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for application upgrades, especially for retrieving and passing application parameters.
  • Include notes or sections describing how to perform equivalent operations on Linux clusters, or clarify if certain features are Windows-only.
  • Where Windows-specific APIs or error messages are referenced (e.g., http.sys), provide Linux/macOS context or explicitly state if the limitation is Windows-only.
  • In the 'Next steps' section, add links to cross-platform upgrade tutorials (e.g., using Azure CLI, sfctl, or REST API) if available.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation for restoring backups in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all command-line examples using PowerShell syntax and modules. There is no mention of Linux/macOS equivalents, nor are cross-platform REST API examples provided using curl or other non-Windows tools. The prerequisites and step-by-step instructions assume the use of PowerShell and related modules, which are primarily Windows-centric, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent examples using cross-platform tools such as curl, az CLI, or bash scripts for REST API calls.
  • Clarify whether the PowerShell modules can be used on Linux/macOS via PowerShell Core, and provide installation instructions if so.
  • Add explicit guidance for Linux/macOS users, including any required authentication steps and certificate handling.
  • Reorder examples so that REST API usage is shown first, followed by platform-specific tooling.
  • Indicate any platform limitations or requirements for Service Fabric backup/restore operations.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides detailed step-by-step instructions for scaling Service Fabric clusters, but consistently uses PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode) without mentioning Linux equivalents or cross-platform alternatives. Windows/PowerShell tooling is presented as the default, with no Bash, CLI, or REST API examples for Linux users. The examples and manual procedures are Windows-centric, creating friction for Linux/macOS users who may not have access to PowerShell or prefer native Linux tools.
Recommendations
  • Add equivalent instructions and examples for Linux environments, using Bash, Azure CLI, or REST API where possible.
  • Explicitly note which commands are Windows-only and provide cross-platform alternatives if available.
  • Reorder examples or provide parallel instructions for both Windows and Linux users to improve parity.
  • Reference Linux-specific documentation sections where appropriate, especially for cluster management tasks.
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, but does not offer equivalent CLI or Linux/macOS examples. The only command-line example is Windows/PowerShell-specific, and there is no mention of cross-platform tools or commands for Linux users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • When showing command-line examples, provide both PowerShell and CLI (sfctl) commands side-by-side.
  • Explicitly mention that the PowerShell cmdlets are Windows-only and link to cross-platform alternatives.
  • Review other sections for implicit assumptions of Windows environments and clarify where features or commands are platform-specific.
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 prioritizes Windows-centric tools (PowerShell and Visual Studio) in both structure and example detail. PowerShell and Visual Studio parameters are described first and in greater depth, with example formats and usage, while Linux/macOS equivalents (SFCTL CLI) are covered later and with less practical guidance. There are no explicit Linux/macOS command-line examples or walkthroughs in the main body, and the SFCTL section lacks concrete usage examples. This creates friction for Linux/macOS users, who must infer parameter usage and mapping from Windows-focused sections.
Recommendations
  • Reorder sections so that cross-platform tools (SFCTL CLI) are presented before or alongside Windows-specific tools.
  • Provide concrete SFCTL CLI command examples for common upgrade scenarios, similar to the PowerShell examples.
  • Explicitly note platform compatibility for each tool (e.g., PowerShell for Windows, SFCTL for Linux/macOS/Windows).
  • Add a table or mapping showing how parameters correspond between PowerShell, Visual Studio, and SFCTL.
  • Ensure that walkthroughs and examples for Linux/macOS users are as detailed and accessible as those for Windows users.
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: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for configuring periodic backups in Azure Service Fabric exhibits mild Windows bias. While the majority of the content is platform-neutral, the only example of on-premises backup storage is a Windows file share (with Windows authentication and UNC path syntax), and no Linux or cross-platform file share options (such as NFS or SMB mounting on Linux) are mentioned. Additionally, the file share example uses Windows authentication patterns and does not discuss Linux-compatible alternatives. Azure Blob storage examples are platform-neutral, but the file share section is Windows-centric.
Recommendations
  • Add examples for configuring backup storage to Linux-compatible file shares, such as NFS or SMB shares mounted on Linux nodes.
  • Clarify whether Service Fabric supports Linux-based clusters using file shares for backup, and if so, provide guidance for Linux authentication and mounting.
  • Include notes or examples for Linux/macOS users where applicable, especially in sections discussing file share paths and authentication.
  • If file share backup is Windows-only, explicitly state this to avoid confusion for Linux users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and detailed upgrade commands, while Linux equivalents (e.g., Bash, shell scripts) are absent. Windows-specific configuration details (registry keys, Windows Update settings) are described without Linux alternatives or guidance. Upgrade instructions and examples focus on Windows tools and patterns, with no parity for Linux users in critical operational steps.
Recommendations
  • Add Linux/Bash equivalents for PowerShell deployment and upgrade commands, especially for cluster upgrades.
  • Include Linux-specific configuration guidance for OS upgrades and disabling automatic updates, such as relevant systemd or apt/yum settings.
  • Present examples for both Windows and Linux side-by-side, or clearly indicate when a step is Windows-only.
  • Reference Linux documentation and tools where appropriate, not just in 'Next steps'.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page provides code samples for configuring Service Fabric placement policies using C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or REST API) are provided. The PowerShell examples are presented for every scenario, and there is no mention of Linux-compatible tooling or workflows. This creates friction for users managing Service Fabric clusters from Linux/macOS environments.
Recommendations
  • Add equivalent Azure CLI examples for each placement policy scenario, as Azure CLI is cross-platform.
  • Document REST API or ARM template approaches for configuring placement policies, which are platform-agnostic.
  • Explicitly mention whether these operations can be performed from Linux/macOS, and provide guidance for non-Windows users.
  • If PowerShell is required, clarify if PowerShell Core (cross-platform) is supported and provide installation instructions.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation provides both Windows and Linux guidance for most security best practices, including certificate management and secret encryption. However, Windows examples and tools (such as PowerShell and Windows Defender) are frequently presented first or exclusively, with Linux equivalents sometimes appearing later or in less detail. Windows-specific tools and configuration options (e.g., Windows Defender, PowerShell commands) are described in dedicated sections, while Linux alternatives are not always given equal prominence or detail.
Recommendations
  • Present Windows and Linux examples side-by-side or in parallel sections, rather than listing Windows first.
  • Where Windows-specific tools (e.g., PowerShell, Windows Defender) are discussed, provide Linux alternatives or clarify their absence.
  • Expand Linux-specific guidance for security baselines and antimalware, referencing common Linux security tools (e.g., SELinux, AppArmor, ClamAV) and best practices.
  • Ensure that all code samples and configuration snippets have Linux equivalents where applicable.
  • Add explicit notes when a feature or recommendation is Windows-only, to avoid confusion for Linux users.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page provides general information about Service Fabric node types and VM scale sets, but several examples and guidance sections show Windows-centric patterns. The JSON snippet uses a Windows-style file path (D:\SvcFab) in the dataPath property, and the next steps section links to PowerShell scripts for changing RDP port ranges and admin credentials, both of which are Windows-specific tasks. There are no Linux/macOS equivalents or examples for these operations, nor is there guidance for connecting to Linux nodes or managing them.
Recommendations
  • Provide Linux-specific examples, such as using Linux file paths (e.g., /var/svcfab) in the dataPath property.
  • Include guidance or links for managing Linux node types, such as SSH connection instructions and scripts for changing SSH port ranges or admin credentials.
  • Balance examples and instructions so that both Windows and Linux users can easily follow the documentation.
  • Clearly indicate when a step or example is Windows-only, and provide alternatives for Linux/macOS where possible.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides only PowerShell and C# examples for managing Service Fabric Application Groups. PowerShell is a Windows-centric tool, and there are no examples or guidance for Linux/macOS users (e.g., Azure CLI, REST API, or bash scripting). This creates friction for users operating Service Fabric clusters on Linux or from non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI or REST API for all operations shown in PowerShell.
  • Explicitly mention cross-platform management options for Service Fabric clusters.
  • Clarify which management operations are supported on Linux clusters and how to perform them.
  • If PowerShell is required, note its availability on Linux and provide installation guidance.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides configuration examples for both WindowsServer (ClusterManifest.xml) and generic VM nodes (ClusterConfig.json), but code samples for service creation and updates are shown only in C# and PowerShell, with no Linux CLI or Bash examples. The XML configuration is labeled for WindowsServer, and PowerShell is used exclusively for command-line operations, suggesting a Windows-first approach. There is no explicit mention of Linux Service Fabric clusters or parity for Linux-based management tools.
Recommendations
  • Add equivalent Linux/Bash/CLI examples for service creation and updates (e.g., using Service Fabric CLI or REST API).
  • Clarify whether ClusterManifest.xml configuration is applicable to Linux clusters, or provide a Linux-specific configuration example if available.
  • Explicitly mention Linux support for standalone clusters and provide links to Linux-specific Service Fabric documentation.
  • Include notes on differences (if any) in node property and capacity configuration for Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides code examples for configuring auto scaling in Azure Service Fabric using C#, application manifest (XML), and PowerShell. The PowerShell examples are Windows-specific, and there are no equivalent CLI or shell script examples for Linux/macOS users. Additionally, the use of PowerShell cmdlets and .NET types in scripting sections assumes a Windows environment, which may create friction for Linux users. While the text notes that resource monitoring is supported for containerized applications on Linux, the practical guidance and automation examples are Windows-centric.
Recommendations
  • Add equivalent examples using Azure CLI or bash scripts for Linux/macOS users where PowerShell is used.
  • Clarify in each scripting section whether the example is Windows-only, and provide Linux alternatives if available.
  • Document any limitations or differences in auto scaling configuration and management between Windows and Linux clusters.
  • Where .NET APIs are shown, mention cross-platform compatibility if applicable, or provide Python/REST API examples where possible.
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 examples for creating and updating Service Fabric services with move cost, but does not offer equivalent Linux/macOS CLI (such as Azure CLI or SFCTL) or bash examples. PowerShell is a Windows-centric tool, and its exclusive use here creates friction for Linux/macOS users. The documentation also lacks mention of Linux-native tools or workflows for these operations.
Recommendations
  • Add equivalent examples using Azure CLI (az servicefabric) or SFCTL (Service Fabric CLI), which are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention how Linux/macOS users can perform these tasks, including installation and usage of SFCTL or Azure CLI.
  • If PowerShell Core (pwsh) is supported cross-platform for these commands, clarify compatibility and provide usage notes.
  • Consider ordering examples so that cross-platform tools are shown first or alongside PowerShell.
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 samples in C# and PowerShell, with PowerShell being a Windows-centric tool. There are no CLI or Bash examples for Linux/macOS users, nor is there mention of cross-platform equivalents (e.g., Azure CLI, REST API, or Bash scripting). PowerShell examples are presented as the only command-line option, which may create friction for users managing Service Fabric clusters from Linux or macOS environments.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, especially for service creation and metric configuration.
  • Explicitly mention whether the PowerShell commands are supported on PowerShell Core (cross-platform) or only on Windows PowerShell.
  • Provide REST API examples for metric management tasks, as these are platform-agnostic.
  • Include Bash script snippets or instructions for Linux/macOS users where relevant.
  • Clarify any platform-specific limitations in a dedicated section, so users know if certain features are Windows-only.
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 Application Manifest (XML/JSON), PowerShell, and C# APIs. PowerShell examples are prominent and presented before C# API examples, with no mention of Linux/macOS CLI equivalents (such as Azure CLI, REST API, or cross-platform Service Fabric CLI). There are no Linux-specific instructions or parity for command-line operations, which may create friction for non-Windows users managing Service Fabric clusters.
Recommendations
  • Add equivalent examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and usable on Linux/macOS.
  • Explicitly mention REST API options for configuration where possible.
  • Clarify which operations require Windows-only tooling (e.g., PowerShell) and provide alternatives or workarounds for Linux/macOS users.
  • Reorder examples so that cross-platform methods (JSON, CLI, REST) are presented before or alongside Windows-specific tools like PowerShell.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for upgrading an Azure Service Fabric standalone cluster exhibits a moderate Windows bias. Key upgrade and configuration instructions link to Windows Server-specific documentation (e.g., service-fabric-cluster-upgrade-windows-server.md, service-fabric-cluster-config-upgrade-windows-server.md), and the patch orchestration application is described only for Windows. There are no explicit Linux examples or references to Linux-specific upgrade/configuration procedures, nor is there mention of Linux equivalents for patch orchestration or cluster management.
Recommendations
  • Add explicit guidance or links for upgrading and configuring Service Fabric standalone clusters running on Linux, if supported.
  • Include Linux-specific examples and instructions alongside Windows examples, especially for cluster upgrades and configuration changes.
  • Clarify whether features like the Patch Orchestration Application are available for Linux clusters, and provide alternatives or workarounds if not.
  • Ensure that references to configuration files, tools, and commands are applicable to both Windows and Linux environments, or note platform limitations.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page demonstrates a notable Windows bias. All command-line deployment and resource management examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI equivalents. The application packaging workflow is described using Visual Studio, a Windows-centric tool, and screenshots reinforce this. There are no Linux/macOS-specific instructions or examples, and the PowerShell workflow is presented as the default path for deployment and deletion.
Recommendations
  • Add Azure CLI examples for deployment, resource retrieval, and deletion alongside PowerShell examples.
  • Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK on Linux/macOS).
  • Provide guidance for performing the workflow on Linux/macOS, including alternative tools and commands.
  • Present both Windows and Linux/macOS workflows in parallel or clarify which steps are platform-specific.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation frequently references standalone Windows Server clusters and provides explicit links and instructions for securing them, while omitting equivalent guidance for standalone Linux clusters. Windows-specific security mechanisms (Windows security/Kerberos) are described in detail, but there is no mention of Linux authentication options or links to Linux-specific setup guides. Certificate-based security is presented as cross-platform, but examples and walkthroughs are only given for Azure and Windows clusters, not Linux.
Recommendations
  • Add explicit instructions and links for securing standalone Linux Service Fabric clusters, including certificate setup and any Linux-specific considerations.
  • If Linux clusters support authentication mechanisms other than certificates, document those options and provide setup guidance.
  • When listing security options, avoid presenting Windows options first or exclusively; ensure Linux parity in examples and references.
  • Clarify which security features and recommendations apply equally to Linux and Windows clusters, and note any differences.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page provides upgrade guidance for Azure Service Fabric clusters and generally maintains platform neutrality. However, in sections about managing certificates, opening application ports, and other cluster updates, PowerShell is mentioned before Azure CLI, and references to Windows-specific tools (such as Patch Orchestration Application for Windows OS patching) are present. The link for OS patching is explicitly Windows-focused, and there is no mention of Linux OS image upgrade options or parity. Examples and instructions for Linux environments (such as Bash, Linux-specific tools, or Linux node pools) are missing or not referenced, which may create friction for Linux users.
Recommendations
  • Include explicit examples for Linux users (e.g., Bash/Azure CLI commands) alongside PowerShell instructions.
  • Clarify whether Patch Orchestration Application or OS image upgrade guidance is available for Linux-based Service Fabric clusters, and provide links if so.
  • When listing management options (e.g., certificates, ports), mention Azure CLI and Bash scripts before or alongside PowerShell, and provide example commands for both.
  • If certain features are Windows-only (such as Patch Orchestration Application), clearly state this and provide Linux alternatives or note the lack thereof.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides code examples for scaling Service Fabric services using C# and PowerShell, but does not include equivalent Linux CLI (e.g., Bash, Azure CLI, or sfctl) examples. PowerShell is a Windows-centric tool, and its exclusive use for command-line examples creates friction for Linux/macOS users. Additionally, the documentation references Windows-specific implementation details (e.g., kernel driver for logging) before describing Linux differences, but does not provide Linux-first or parity in operational guidance.
Recommendations
  • Add equivalent Linux command-line examples using sfctl or Azure CLI where PowerShell examples are provided.
  • Clearly indicate when a command or tool is Windows-only, and provide Linux/macOS alternatives where possible.
  • Where implementation differences are discussed, provide actionable guidance for both platforms (e.g., how to monitor or manage logs on Linux).
  • Consider including a table or section summarizing platform-specific commands and behaviors for common scaling operations.
GitHub Create Pull Request
Service Fabric Overview of Azure and standalone Service Fabric clusters ...icles/service-fabric/service-fabric-deploy-anywhere.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation discusses both Windows Server and Linux as platforms for Service Fabric clusters, but it notes that standalone clusters are not available on Linux. The explanations and benefits sections do not provide Linux-specific examples or guidance, and the mention of standalone clusters is implicitly Windows-focused due to the lack of Linux support. The page does not provide parity in examples or operational guidance for Linux users.
Recommendations
  • Explicitly clarify the limitations for Linux users regarding standalone clusters, including a direct statement about the lack of support and possible alternatives.
  • Provide links or references to documentation for deploying Service Fabric clusters on Linux within Azure, if available.
  • Add a comparison table summarizing feature differences between Windows and Linux clusters, with clear guidance for Linux users.
  • Ensure that next steps or related links include Linux-relevant documentation where applicable.
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, covering both Windows and Linux support. However, there is a notable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned before or more prominently than Linux equivalents, and some examples (such as standalone cluster creation and scaling) are Windows-only. The documentation often refers to Windows services and executables (FabricHost.exe, etc.) without clarifying Linux equivalents or differences. Linux support is acknowledged, but Linux-specific instructions, examples, and tooling are less visible or missing in key lifecycle and management sections.
Recommendations
  • Ensure Linux equivalents are mentioned alongside Windows tools (e.g., highlight sfctl CLI and bash scripting where PowerShell is referenced).
  • Provide explicit Linux examples for cluster creation, scaling, and management, or clearly state limitations where Linux support is not available.
  • When describing node services and executables, clarify differences between Windows and Linux implementations.
  • Balance the order of presentation so Linux options are not consistently listed after Windows ones.
  • Add links to Linux-specific quickstarts, tutorials, and troubleshooting guides where available.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides detailed PowerShell examples for health reporting and querying in Service Fabric, but does not offer equivalent examples for Linux/macOS environments (such as Bash, CLI, or REST). The only concrete example is Windows PowerShell, and Windows-specific tools (PowerShell cmdlets) are mentioned before REST or other cross-platform options. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer platform-agnostic approaches.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or REST API for health reporting and querying.
  • Explicitly mention cross-platform tools and workflows before or alongside Windows-specific ones.
  • Clarify which tools are available on Linux/macOS and provide links or instructions for their use.
  • Where PowerShell is used, note its availability on Linux/macOS or suggest alternatives if not supported.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for Azure Service Fabric DNS service exhibits several Windows-centric biases. PowerShell is the only CLI example provided for setting DNS names, with no Linux CLI (e.g., Bash, Azure CLI) alternatives. The ApplicationManifest.xml example assumes Visual Studio, a Windows tool, and does not mention Linux development workflows. The limitations section clearly states that Linux support is restricted and that DNS service cannot be enabled via the Azure portal for Linux clusters, but the documentation does not offer Linux-specific guidance or parity in examples. Windows methods and tools are presented first and in greater detail.
Recommendations
  • Add Linux/Bash/Azure CLI examples for service creation and DNS name assignment.
  • Clarify Linux development workflows for ApplicationManifest.xml editing (e.g., using VS Code, nano, or other editors).
  • Explicitly document how Linux users can enable DNS service (e.g., via ARM templates or REST API), since portal support is missing.
  • Where PowerShell is shown, provide equivalent commands for Linux environments (e.g., Azure CLI, REST API calls).
  • Add a section summarizing the differences and workarounds for Linux users, including limitations and alternative approaches.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page demonstrates a mild Windows bias. The only explicit file path given for the Service Fabric SDK schema is a Windows path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd), and there is no mention of Linux/macOS equivalents or installation locations. The examples and directory structures use Windows-style naming (e.g., .exe files), and Visual Studio is referenced as a primary tool for packaging and deploying, which is predominantly a Windows application. There are no Linux/macOS-specific instructions or examples, nor is there guidance for cross-platform tooling.
Recommendations
  • Include Linux/macOS installation paths for Service Fabric SDK schemas, or clarify if the SDK is Windows-only.
  • Provide examples or notes for packaging non-Windows executables (e.g., .sh, ELF binaries) and clarify cross-platform support.
  • Mention cross-platform alternatives to Visual Studio, such as Visual Studio Code or command-line tools available on Linux/macOS.
  • Add explicit guidance for Linux/macOS users where relevant, or clarify platform limitations if Service Fabric guest executables are Windows-only.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation is generally OS-neutral in its technical explanations, but the only concrete example of deployment/removal references PowerShell, and the 'Next steps' section links to a PowerShell-specific guide for deploying/removing applications. No Linux or cross-platform CLI examples or links are provided, and PowerShell is mentioned before any Linux equivalent tools.
Recommendations
  • Add references or links to cross-platform deployment/removal guides, such as using Azure CLI or Service Fabric CLI (sfctl), alongside or instead of PowerShell.
  • Where possible, provide examples or notes for both Windows (PowerShell) and Linux/macOS (Bash, CLI) users.
  • Clarify in the 'Next steps' section that PowerShell is one option, and mention alternatives for Linux/macOS users.
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 the Azure Service Fabric hosting model provides conceptual information applicable to all platforms, but operational examples and tooling references are heavily Windows/PowerShell-centric. The only concrete command-line example is a PowerShell cmdlet, and all operational instructions (creating services, querying service state, reporting health, restarting code packages) reference PowerShell modules without mentioning Linux equivalents or cross-platform CLI options. There are no bash, Azure CLI, or Linux-native examples, and PowerShell is presented as the default/primary method for management tasks.
Recommendations
  • Add equivalent examples using Azure CLI (az service-fabric) or REST API calls for service creation and management, especially for Linux/macOS users.
  • Explicitly mention cross-platform management options and clarify which tools are supported on Linux/macOS clusters.
  • Where PowerShell is referenced, provide a note or link to Linux-compatible alternatives, or clarify if PowerShell Core is supported on Linux for Service Fabric management.
  • Consider including bash or shell script examples for common tasks.
  • Update references to management tasks to include both Windows and Linux tooling, or clarify platform limitations if any exist.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.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 mentions both Windows and Linux support for Service Fabric, but Windows development tools (Visual Studio, PowerShell) are listed first and in more detail than Linux equivalents. The Linux section is shorter, and there are no direct Linux command-line or deployment examples. The quickstart link points to a .NET/Windows-centric tutorial, with no immediate parity for Linux users.
Recommendations
  • Present Windows and Linux development options with equal prominence and detail.
  • Include direct Linux command-line examples (e.g., using Bash, CLI) alongside PowerShell examples.
  • Add quickstart links for Linux development (e.g., Java SDK, .NET Core on Linux) in the 'Next steps' section.
  • Clarify tooling parity (e.g., Visual Studio vs. Eclipse/Yeoman) and provide links to Linux-specific guides.
  • Ensure that deployment and management instructions cover both Windows and Linux workflows.
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 the Service Fabric cluster manifest and links to PowerShell-based deployment guides. It mentions Visual Studio (a Windows-centric tool) for publishing, and PowerShell is listed first among programmatic options, with no explicit Linux/macOS CLI or Bash examples. This creates a subtle Windows-first bias, though the underlying concepts are cross-platform.
Recommendations
  • Include equivalent Linux/macOS examples using Azure CLI or Bash where applicable.
  • Reference cross-platform tools (e.g., Azure CLI, Service Fabric CLI) alongside PowerShell and Visual Studio.
  • Clarify that PowerShell and Visual Studio are examples, and provide links or instructions for non-Windows environments.
  • Add guidance for retrieving the cluster manifest and deploying applications from Linux/macOS.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Visual Studio (Windows-centric tools) are mentioned first and in detail for application parameterization, while Linux-native workflows (e.g., sfctl, shell scripting) are referenced but not elaborated. There is a lack of concrete Linux/macOS examples, such as shell commands or parameter file usage outside Visual Studio, which may create friction for non-Windows users.
Recommendations
  • Provide explicit Linux/macOS examples for parameterization, such as using sfctl with install.sh and sample shell commands.
  • Clarify how parameter files can be used in non-Visual Studio workflows (e.g., with Azure DevOps on Linux agents).
  • Balance the order of examples so that Linux/macOS tools (sfctl, shell scripts) are presented alongside or before Windows tools.
  • Include sample scripts or command lines for Linux/macOS environments where appropriate.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. The manifest examples and explanations are based on the 'Windows Server 2016 Container Sample', with explicit references to Windows tools (e.g., 'winver' for OS build detection) and Windows file paths (e.g., 'c:\VolumeTest\Data'). There is no mention of Linux-specific patterns, tools, or examples, and Linux container scenarios are not illustrated, even though Service Fabric supports both Windows and Linux containers. The certificate handling section does mention both PFX (Windows) and PEM (Linux) formats, but practical Linux usage details are missing.
Recommendations
  • Provide parallel Linux-based manifest examples, including Linux file paths and volume mounts (e.g., '/mnt/data').
  • Reference Linux tools for OS build/version detection (e.g., 'cat /etc/os-release') alongside 'winver'.
  • Clarify which manifest settings and features are cross-platform and which are Windows-only.
  • Include links or references to Linux container samples in addition to the Windows sample.
  • Explicitly document any differences in behavior or configuration between Windows and Linux containers in Service Fabric.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides only PowerShell-based deployment examples and command-line instructions, which are specific to Windows. There are no equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). Additionally, Windows tools and patterns (such as RDP and Windows-style paths) are referenced without mention of Linux alternatives. This creates friction for users on non-Windows platforms, though the underlying Azure features are cross-platform.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps.
  • Include Bash shell examples for template deployments.
  • Mention SSH as an alternative to RDP for accessing VMs, and provide relevant instructions.
  • Use platform-neutral file paths in examples, or clarify differences for Linux/macOS users.
  • Explicitly state that the steps can be performed from Linux/macOS using Azure CLI, and link to relevant documentation.
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 for enhanced data protection in Service Fabric' demonstrates a bias towards Windows environments. All command-line/API examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica), with no mention of Linux equivalents, CLI commands, or REST API usage. The documentation assumes familiarity with Windows tooling and does not provide guidance for Linux/macOS users, even though Service Fabric supports Linux clusters.
Recommendations
  • Include equivalent examples using Service Fabric CLI (sfctl) or REST APIs where available, especially for operations like removing, restoring, and querying replicas.
  • Explicitly state if certain APIs or features are only available via PowerShell and provide alternative guidance for Linux users if possible.
  • Add a section or callout clarifying cross-platform support and any limitations for Linux/macOS clusters.
  • Provide links to Linux/macOS-specific documentation or tools for managing Service Fabric clusters.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation is heavily focused on Windows tooling, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and instructions reference Windows-specific tools and workflows, with no mention of Linux/macOS alternatives or cross-platform CLI options. This creates friction for users on non-Windows platforms who wish to perform similar upgrade tasks.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), where possible.
  • Clarify which steps are Windows-only and provide alternative workflows for Linux/macOS users, especially for manual upgrades.
  • Include Linux/macOS-specific notes or links to relevant documentation for non-Windows environments.
  • Reorder sections or provide parity so that non-Windows approaches are presented alongside Windows ones, not only after them.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides detailed examples for reporting health in Service Fabric using C#/.NET APIs and PowerShell, both of which are primarily Windows-centric. PowerShell examples are given for connecting to clusters and sending health reports, but there are no equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI, or cross-platform scripting). The REST API is mentioned as a cross-platform option, but no concrete example is provided, and the PowerShell workflow is described before REST. There is no discussion of Linux-specific tooling or patterns for Service Fabric health reporting.
Recommendations
  • Add explicit examples for reporting health using Bash scripts or Azure CLI, which are cross-platform and commonly used on Linux/macOS.
  • Provide REST API usage examples with sample curl commands, including authentication and payload details.
  • Clarify which PowerShell commands (if any) are supported on PowerShell Core on Linux/macOS, or note any limitations.
  • Reorder examples so that REST and cross-platform methods are presented before or alongside Windows/PowerShell examples.
  • Mention any Linux/macOS-specific considerations for Service Fabric health reporting, if applicable.
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 provides several examples and deployment instructions using Windows-centric tools and patterns, notably PowerShell cmdlets (e.g., New-ServiceFabricApplication) and Windows file paths (e.g., C:\Program Files\...). Linux equivalents are mentioned only briefly, such as the certificate store location, and there are no Linux CLI examples or deployment instructions. Windows tooling and patterns are presented first and exclusively in critical deployment sections.
Recommendations
  • Add equivalent Linux CLI examples (e.g., using Azure CLI, Bash scripts, or Service Fabric CLI) for application deployment and parameter overrides.
  • Include Linux file paths and configuration details alongside Windows paths wherever relevant.
  • Clarify which steps or commands are platform-agnostic and which require platform-specific tools.
  • Provide links or references to Linux/macOS-specific Service Fabric deployment documentation.
  • Ensure parity in example coverage, showing both Windows and Linux workflows for common tasks.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides explicit instructions for using the Fault Analysis Service via PowerShell, which is a Windows-centric tool, and references the Service Fabric SDK and PowerShell module without mentioning equivalent Linux/macOS CLI or scripting options. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform Service Fabric tools.
Recommendations
  • Add instructions and examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash scripts, or REST APIs.
  • Clarify whether the PowerShell and SDK instructions are Windows-only, and provide alternative steps for non-Windows platforms if available.
  • Include cross-platform code samples and tool references where possible, or explicitly state platform limitations if features are Windows-only.
GitHub Create Pull Request
Virtual Machines VM vCore Customization ...lob/main/articles/virtual-machines/vm-customization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring vCore customization, but the PowerShell section is more detailed and uses direct object manipulation, which is specific to Windows/PowerShell users. The CLI example uses Ubuntu as the image, but there is no explicit Linux shell or scripting example, nor is there parity in depth between PowerShell and CLI sections. The PowerShell example appears after the CLI, but its depth and specificity may create friction for Linux/macOS users seeking equivalent automation or scripting guidance.
Recommendations
  • Provide a Bash shell script example for Linux/macOS users that demonstrates the same VM customization using Azure CLI.
  • Ensure that CLI and PowerShell sections are equally detailed, including notes on how to script or automate the process on Linux/macOS.
  • Clarify that all features are available regardless of guest OS, and explicitly state that the CLI examples are cross-platform.
  • If possible, add a note or example for using Azure CLI in PowerShell and Bash to highlight parity.
GitHub Create Pull Request
Virtual Machines Create a VM from a generalized image in a gallery ...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from generalized images, but PowerShell coverage is extensive and primarily Windows-focused. In PowerShell sections, Windows VM creation is shown by default, with explicit use of Windows-specific parameters (e.g., Set-AzVMOperatingSystem -Windows). Linux VM creation via PowerShell is not demonstrated, and Windows-centric networking (RDP port rules) is prominent. CLI examples do show Linux VM creation and SSH key usage, but PowerShell examples are Windows-first and lack Linux parity. REST and Portal instructions are generally neutral, but password requirements link to Windows documentation.
Recommendations
  • Add PowerShell examples for creating Linux VMs, including use of Set-AzVMOperatingSystem -Linux and SSH key authentication.
  • In PowerShell networking examples, show how to allow SSH (port 22) for Linux VMs, not just RDP (port 3389) for Windows.
  • Where possible, present Linux and Windows examples side-by-side in PowerShell sections, or clarify how to adapt commands for Linux.
  • In password requirement links, reference both Windows and Linux complexity requirements, or clarify when requirements are OS-specific.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides some examples and scenarios that mention Windows-specific tasks (e.g., Windows VM activation, Windows updates) before Linux equivalents, and does not provide explicit Linux-focused examples or commands. While the migration process itself is platform-agnostic, the documentation could better address Linux parity by including Linux-specific migration considerations and examples.
Recommendations
  • Add explicit Linux migration scenarios, such as package manager connectivity requirements (e.g., apt, yum, zypper) and troubleshooting steps for Linux VM activation or updates.
  • Provide example commands for both Windows and Linux VMs where relevant, especially in sections discussing outbound connectivity and VM extensions.
  • Ensure that references to OS-specific requirements (e.g., Windows Activation KMS) are paired with Linux equivalents (e.g., connectivity for package updates).
  • Where PowerShell or Windows-centric tools are mentioned, also mention Bash/Azure CLI or Linux-native tools if applicable.
GitHub Create Pull Request
Virtual Machine Scale Sets Spot Placement Score ...les/virtual-machine-scale-sets/spot-placement-score.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides usage instructions for Azure portal, REST API, Azure CLI, and Azure PowerShell. The PowerShell example is given its own section and is presented after the CLI example, but both are included. There is a slight Windows bias in that PowerShell is called out explicitly, and PowerShell is a Windows-centric tool, though it is available cross-platform. No Linux-specific tools (such as Bash scripts) or macOS-specific instructions are provided, but the CLI and REST API examples are platform-neutral and suitable for Linux/macOS users. The order of examples (portal, REST API, CLI, PowerShell) does not strongly favor Windows, but PowerShell is the only shell scripting example shown.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users, demonstrating how to call the REST API or use Azure CLI in a shell environment.
  • Clarify that Azure CLI and REST API examples are cross-platform and suitable for Linux/macOS users.
  • Consider mentioning that PowerShell Core is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for most networking tasks related to Azure Virtual Machine Scale Sets, but PowerShell examples are often presented before CLI, and some sections (such as querying public IPs) give more detailed PowerShell usage. There are no Linux-specific shell examples (e.g., Bash scripts), and some CLI examples are generic but lack explicit Linux context. The documentation does not mention Linux-specific networking tools or patterns, and Windows/PowerShell is sometimes prioritized in example ordering.
Recommendations
  • Ensure CLI examples are presented before or alongside PowerShell, especially for tasks that are cross-platform.
  • Add explicit Bash/Linux shell examples where relevant, especially for querying and scripting tasks.
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide sample outputs from Linux environments.
  • Where PowerShell is used for querying or scripting, provide equivalent Bash/CLI commands and outputs.
  • Avoid ordering examples so that Windows/PowerShell appears first unless there is a technical reason.
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Gen2 VMs ...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides parity for both Linux and Windows VMs when enabling Trusted launch, with clear notes and instructions applicable to both platforms. However, there is a mild Windows bias in the ordering and example tooling: PowerShell examples are shown alongside CLI and template methods, and PowerShell is referenced for ARM template deployment and VM deallocation, which is more common on Windows. Additionally, in several places, RDP (Windows) is mentioned before SSH (Linux) when verifying VM access.
Recommendations
  • Where PowerShell is used for generic Azure VM operations (deallocation, deployment), provide equivalent Bash or Azure CLI examples for Linux/macOS users.
  • When listing access methods (RDP/SSH), alternate or list SSH first in Linux-specific contexts.
  • Clarify that PowerShell commands can be run cross-platform (Windows, Linux, macOS) if true, or provide Bash/CLI alternatives.
  • Consider including Bash scripts for ARM template deployment and VM deallocation to improve Linux parity.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric container image management demonstrates mild Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are referenced as default exclusions in cleanup, and the examples for 'ContainerImagesToSkip' mention Windows images first. There is no mention of Linux container images, Linux-specific patterns, or examples, nor is there guidance for Linux users managing container images in Service Fabric clusters.
Recommendations
  • Add examples and explanations for common Linux container images (e.g., Ubuntu, Alpine, CentOS) in the 'ContainerImagesToSkip' setting.
  • Clarify whether the cleanup features and settings apply equally to Linux-based Service Fabric clusters and containers.
  • Provide parity in documentation by listing both Windows and Linux base images as examples, or explicitly state platform applicability.
  • Include a note or section addressing any differences in container image management between Windows and Linux clusters.
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 Windows-first bias in some sections, such as listing Windows container runtimes in more detail and referencing IIS lift-and-shift scenarios (which are inherently Windows-centric). Windows tutorials and links are sometimes listed before Linux equivalents, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are mentioned with more granularity than Linux (which is simply listed as 'Docker').
Recommendations
  • Ensure Linux and Windows examples/tutorials are presented with equal prominence, alternating order or grouping them together.
  • Provide more detail about Linux container runtime options if relevant (e.g., mention containerd, CRI-O if supported).
  • Clarify when scenarios (like IIS lift-and-shift) are Windows-only, and offer Linux-centric examples for similar use cases.
  • Where possible, balance references to Windows tools with Linux equivalents, or note if only Docker is supported on Linux.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation presents PowerShell-based deployment instructions first and in detail, followed by cross-platform Service Fabric CLI (sfctl) commands. While the CLI examples provide Linux/macOS parity, the initial focus on PowerShell and the ordering may create a perception of Windows bias. No critical functionality is Windows-only, and Linux users can complete all tasks using sfctl.
Recommendations
  • Reorder the deployment instructions to present the cross-platform CLI (sfctl) examples before PowerShell, or clarify that sfctl is recommended for Linux/macOS users.
  • Explicitly state that sfctl works on Linux/macOS and provide installation or usage links for those platforms.
  • Add a note indicating that PowerShell commands are for Windows users, while sfctl is for all platforms.
  • Consider balancing example depth between PowerShell and CLI, ensuring both are equally detailed.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_only_feature_callout
Summary
The documentation covers both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Service Fabric. It clearly notes that HTTP.sys is Windows-only, and recommends Kestrel for Linux/cross-platform scenarios. There are no PowerShell-heavy examples, and Kestrel is consistently presented as the preferred and supported option for Linux. All code samples are in C# and are OS-agnostic unless using HTTP.sys, which is explicitly marked as Windows-only. There is a minor bias in that HTTP.sys (a Windows-only technology) is described in detail, but this is balanced by clear guidance for Linux users.
Recommendations
  • Ensure that all HTTP.sys sections are clearly marked as Windows-only (which is already done).
  • Consider adding a brief section or callout at the top summarizing that Kestrel is the only supported option for Linux and macOS, and that HTTP.sys is only for Windows.
  • Where HTTP.sys is discussed, always immediately reference Kestrel as the cross-platform alternative.
  • If possible, provide a table or quick reference for which features/scenarios are supported on which OS.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation is largely platform-neutral and describes Service Fabric concepts applicable to both Windows and Linux. However, there are subtle signs of Windows bias: Windows-specific tools and processes (such as 'FabricHost.exe' as an auto-start Windows service) are mentioned first or exclusively in some infrastructure descriptions, and executable file types are described as EXE/DLL, which are Windows-centric. Linux equivalents or behaviors are not always described with equal prominence or detail.
Recommendations
  • When describing node infrastructure, clarify how Linux nodes operate (e.g., what processes/services are used instead of 'FabricHost.exe').
  • When referencing executable file types (EXE/DLL), add a note about Linux equivalents (e.g., ELF binaries, .so files).
  • Where Windows-specific processes or services are mentioned, provide parallel Linux details if available, or explicitly state if the process is Windows-only.
  • Ensure that examples and terminology are inclusive of both Windows and Linux, especially in sections describing deployment, packaging, and runtime behaviors.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring, monitoring, canceling, and restarting rolling upgrades on Virtual Machine Scale Sets. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as 'Setting or updating the rolling upgrade policy'), PowerShell examples are shown immediately after CLI, which may suggest a slight Windows-first bias. There are no Linux-specific tools or shell examples (e.g., Bash scripts), but the Azure CLI commands are cross-platform and suitable for Linux/macOS users. No critical functionality is locked to Windows-only tools.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS as well as Windows.
  • Consider adding Bash shell script examples for Linux users, especially for automation scenarios.
  • Clarify that PowerShell examples are primarily for Windows users, and suggest using Azure CLI on Linux/macOS.
  • If possible, add a note about Azure Cloud Shell, which supports both Bash and PowerShell, to highlight cross-platform parity.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response and for installing/querying the extension. However, there are several instances of Windows bias: PowerShell examples are given equal or greater prominence than Bash, and Windows-specific extension types (ApplicationHealthWindows) are shown before or alongside Linux types. The PowerShell examples are more verbose and detailed, and Windows extension types are sometimes used as the default in code samples, even when Linux is equally supported. The documentation does not omit Linux examples, but Windows tools and patterns are often presented first or with more detail.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail. For example, alternate the order of Bash and PowerShell tabs, or present Linux examples first in some sections.
  • Use neutral extension type placeholders (e.g., <ApplicationHealthLinux or ApplicationHealthWindows>) consistently, and clarify when to use each based on the OS.
  • Expand Linux/Bash examples to match the depth and clarity of PowerShell examples, including troubleshooting and advanced scenarios.
  • Explicitly state that all features and steps apply equally to both Linux and Windows VMSS, unless a step is OS-specific.
  • Where possible, provide cross-platform scripts or highlight platform-agnostic approaches (e.g., using REST API or Azure CLI).
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell for all major operations (attach, detach, move VMs). While Azure CLI is cross-platform and examples use Linux images (e.g., Ubuntu2204), PowerShell examples are included in every section and shown immediately after CLI, which may suggest a slight Windows bias. There are no Linux shell-specific examples (e.g., Bash scripts), and troubleshooting links sometimes point to Windows-specific documentation (e.g., proximity placement group migration). However, the CLI coverage ensures Linux/macOS users can complete all tasks.
Recommendations
  • Consider explicitly stating that Azure CLI commands work on Linux/macOS and Windows, and that PowerShell is primarily for Windows users (with PowerShell Core available cross-platform, but less common on Linux).
  • Add Bash script examples for common operations to further improve parity for Linux/macOS users.
  • Where troubleshooting links point to Windows-specific docs, add or reference equivalent Linux documentation if available.
  • Clarify in introductory sections that all operations can be performed from Linux/macOS using Azure CLI.
GitHub Create Pull Request
Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides configuration instructions for rolling upgrades with MaxSurge on Azure Virtual Machine Scale Sets. While the CLI (az) example is cross-platform, the PowerShell example is given equal prominence and is listed after the CLI, not before. There are no Linux-specific tools or patterns mentioned, but the PowerShell example may be less relevant for Linux/macOS users. No Linux/macOS-specific issues or missing examples are present, and the ARM template and portal instructions are platform-agnostic.
Recommendations
  • Clarify that PowerShell examples are primarily for Windows users, and highlight that the Azure CLI is cross-platform and recommended for Linux/macOS.
  • Consider adding a note or a Linux/macOS tab (if relevant) to reinforce CLI usage for non-Windows environments.
  • Ensure that CLI instructions are always presented first or marked as the default for cross-platform scenarios.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones, but PowerShell examples are given equal prominence to CLI, and in some sections (such as updating scale sets), PowerShell is shown before REST API and ARM template examples. There is a slight 'windows_first' bias in the ordering of example methods and tabs, and PowerShell is featured as a primary automation method alongside CLI, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Ensure Azure CLI examples are shown before PowerShell in all sections, as CLI is cross-platform and more commonly used by Linux/macOS users.
  • Explicitly note that Azure CLI is available on all platforms, while PowerShell is primarily used on Windows (though cross-platform PowerShell exists).
  • Where possible, provide Bash shell snippets for CLI usage, and clarify that PowerShell examples are optional for users on non-Windows platforms.
  • Review tab ordering and example ordering to ensure CLI and ARM template methods are presented first, followed by PowerShell.
  • Add a brief note in the 'Use Azure PowerShell' section indicating that Linux/macOS users may prefer Azure CLI.
GitHub Create Pull Request
Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides examples for creating an Azure Compute Gallery using the Portal, Azure CLI, PowerShell, and REST API. While the CLI and REST examples are cross-platform, PowerShell is Windows-centric and is presented as a primary method alongside CLI and Portal. The PowerShell example is given equal prominence to CLI, but there is no mention of Linux/macOS equivalents for scripting (e.g., Bash), and PowerShell is not explicitly marked as Windows-only. Additionally, the ordering of examples sometimes places PowerShell before REST, which may subtly reinforce Windows-centric workflows.
Recommendations
  • Clearly indicate that PowerShell examples are intended for Windows users, and suggest CLI or REST for Linux/macOS users.
  • Consider providing Bash script examples for Linux/macOS users where appropriate, or clarify that Azure CLI is the recommended cross-platform tool.
  • Reorder example tabs so that CLI (cross-platform) appears before PowerShell, or group Windows-specific tooling separately.
  • Add a note at the start of the examples section explaining which tools are cross-platform and which are Windows-specific.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation page is focused on time synchronization for Linux VMs in Azure and provides comprehensive Linux-specific guidance and examples. However, the introduction and overview sections discuss Windows Server 2016 time sync improvements and Windows Time Service before explaining Linux mechanisms. All technical instructions, configuration steps, and examples are Linux-centric, with only one minor PowerShell snippet shown for base64 encoding a cloud-init file (which is an Azure ARM template pattern, not a time sync operation). No Windows tools or PowerShell-heavy bias is present in the core guidance.
Recommendations
  • Move or condense the Windows Server 2016 time sync discussion to a background or context section, making it clear that the focus is on Linux VM configuration.
  • Consider providing a Linux-native command for base64 encoding the cloud-init file (e.g., `base64 cloud-config.txt`) alongside the PowerShell example for ARM template users on Linux/macOS.
  • Ensure that links and references in the 'Next steps' section prioritize Linux resources over Windows ones, or clearly separate them.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation is generally Linux-focused, as expected for the Azure Key Vault VM Extension for Linux. However, there are several instances where Windows-oriented tools (PowerShell) are presented before or alongside Linux-native alternatives, and PowerShell deployment examples are given equal or greater prominence than Azure CLI (which is more common on Linux). The troubleshooting section also lists PowerShell before CLI. There are no missing Linux examples, and all technical details are Linux-specific.
Recommendations
  • Present Azure CLI examples before PowerShell examples in all deployment and troubleshooting sections, as CLI is more native to Linux environments.
  • Explicitly note that PowerShell examples are optional for Linux users and primarily for those who prefer PowerShell cross-platform.
  • Add brief instructions for running Azure CLI commands on Linux (e.g., bash syntax, file path conventions) to reinforce Linux parity.
  • In troubleshooting, list CLI commands first and clarify that PowerShell is available for users who have it installed on Linux.
GitHub Create Pull Request
Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell example is given equal prominence and detail as the CLI example, despite PowerShell being primarily a Windows tool. The CLI example is suitable for Linux/macOS, but PowerShell is listed as a main tab, which may imply parity or preference for Windows users. There is no explicit Linux/macOS bias, but the presence and prominence of PowerShell may create minor friction for non-Windows users.
Recommendations
  • Clarify that PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
  • Consider listing the CLI example first, as it is cross-platform.
  • Add a note explaining platform compatibility for each tool.
  • If possible, provide Bash or shell script examples for Linux users, or clarify that Azure CLI is the recommended approach for Linux/macOS.
GitHub Create Pull Request