Scan Details - Linux-first Docs for Azure

268

Pages Scanned

82

Pages Flagged

268

Changed Pages

30.6%

% Pages Flagged

Scan Information

Started At: 2026-02-10 00:00:10

Finished At: 2026-02-10 18:00:39

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 268

Files Completed: 268

Problematic Pages

82 issues found

Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, using Windows-specific images (nanoserver), Windows paths (C:\), and Windows commands (cmd, echo, type, ping). There is no mention of Linux containers, Linux paths, or Linux command equivalents. The example is explicitly Windows-focused, and Linux users are not provided with guidance or parity.

Recommendations

Add a parallel example using a Linux container image (e.g., Ubuntu or Alpine), with Linux paths and commands.
Clarify whether Initializer CodePackages are supported for Linux containers in Service Fabric, and if not, state this explicitly.
If Linux containers are supported, provide guidance and code snippets for Linux users, including differences in volume mounts, entry points, and command syntax.
Mention Linux container compatibility and any limitations, similar to the Windows container version compatibility note.

Create Pull Request

Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page on scaling Azure Service Fabric standalone clusters shows a Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a 'windows-server' specific guide for scaling. There are no Linux or cross-platform CLI examples, nor is it clarified whether standalone clusters can be managed on Linux, leaving Linux users without guidance.

Recommendations

Clarify whether standalone Service Fabric clusters are supported on Linux. If not, explicitly state this early in the documentation.
If Linux is supported, provide equivalent Linux/bash/CLI examples for cluster management tasks (e.g., using sfctl or REST APIs).
Link to Linux-specific or cross-platform guides for adding/removing nodes, if available.
Avoid referencing only PowerShell cmdlets; include cross-platform alternatives where possible.

Create Pull Request

Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and guidance are tailored for Windows clusters. There are no Linux-specific instructions, examples, or workarounds provided. The page does not offer parity for Linux users, and the feature is unavailable on Linux, making the documentation Windows-centric by necessity.

Recommendations

Clearly state at the top of the page that the reverse proxy feature is Windows-only, to set expectations for Linux users.
Provide links or references to alternative approaches for service discovery and communication in Linux Service Fabric clusters, if available.
Consider adding a section outlining the roadmap or plans for Linux support, or explaining why the feature is Windows-only.
If possible, suggest equivalent patterns or tools for Linux clusters, or clarify limitations and alternatives.

Create Pull Request

Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation initially states Service Fabric clusters run on both Windows Server and Linux, but the 'Supported operating systems' section clarifies that Linux isn't yet supported for standalone clusters. Security sections reference Windows-specific features (Kerberos, group Managed Service Accounts, Windows accounts) without Linux equivalents or guidance. No Linux-specific examples, tools, or instructions are provided, and Windows terminology is used throughout.

Recommendations

Clarify at the top that standalone clusters are currently Windows-only, despite the initial mention of Linux.
Remove or revise the description to avoid implying Linux support where it does not exist.
If Linux support is planned, provide a roadmap or guidance for Linux users.
Where Windows-specific features are discussed, explicitly state their applicability and note the absence of Linux equivalents.
Add a section for Linux users explaining alternatives or limitations.

Create Pull Request

Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation page primarily references Windows custom images and provides a PowerShell example for role assignment, with Windows terminology and patterns appearing before Linux equivalents. While there are links to Linux custom image creation and Azure CLI usage, the main narrative and examples are Windows-centric, and the PowerShell command is given without a Linux/CLI equivalent.

Recommendations

Clarify in the introduction that both Windows and Linux custom images are supported, if applicable.
Provide equivalent Azure CLI examples for role assignment alongside the PowerShell example.
Include explicit ARM template examples for Linux node types, or clarify if the process is identical.
Balance references to Windows and Linux throughout the documentation, ensuring Linux terminology and links are not secondary.
Add a section or note about any Linux-specific considerations or limitations, if relevant.

Create Pull Request

Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation page frequently references PowerShell cmdlets (Az PowerShell, AzSF PowerShell) for managing Service Fabric resources, with no explicit mention of Linux/macOS equivalents or Azure CLI alternatives in some sections. PowerShell examples are presented first and predominantly, which may create friction for Linux/macOS users who typically use Azure CLI or bash scripting.

Recommendations

Add Azure CLI examples alongside PowerShell cmdlets for all management operations, especially for application type version unprovisioning and service creation.
Clarify which commands are cross-platform and which are Windows-only, and provide guidance for Linux/macOS users where appropriate.
Where possible, link to ARM template documentation and examples that are platform-agnostic.
Explicitly mention that Azure CLI can be used on Linux/macOS for resource management tasks.

Create Pull Request

Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first

Summary

The documentation page is generally platform-neutral, focusing on Azure Service Fabric backup configuration. However, in the 'File share' backup storage section, only Windows-style file share paths (\\StorageServer\BackupStore) and Windows authentication methods are described. Integrated Windows Authentication is mentioned exclusively, and no Linux or SMB/CIFS mounting instructions are provided. This suggests a Windows-first bias in the file share backup example, potentially creating friction for Linux/macOS users who may wish to use SMB/CIFS file shares.

Recommendations

Add examples and guidance for configuring file share backup storage using SMB/CIFS on Linux/macOS, including mount instructions and authentication options.
Clarify whether Linux-based Service Fabric clusters can use file share backup storage, and if so, provide platform-specific instructions.
Mention alternative storage options (such as NFS or Azure Files) if supported, and provide parity in examples for both Windows and Linux environments.

Create Pull Request

Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation page describes the architecture of Azure Service Fabric in a platform-neutral manner for most subsystems. However, in the Management subsystem section, it explicitly mentions 'PowerShell cmdlets' as a primary means of lifecycle management, without referencing Linux/macOS equivalents (such as Azure CLI or REST APIs). This creates a Windows-first impression and suggests a bias toward Windows tooling for administration.

Recommendations

Mention cross-platform management tools such as Azure CLI and REST APIs alongside PowerShell cmdlets.
Clarify which management operations can be performed using Azure CLI or other platform-neutral tools.
Add examples or references for Linux/macOS users to manage Service Fabric clusters.
Consider rephrasing to avoid implying PowerShell is the only or primary management interface.

Create Pull Request

Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation provides both Windows and Linux examples for key security tasks, such as certificate generation and secret encryption, but often presents Windows/PowerShell instructions first and in greater detail. Windows-specific tools and features (e.g., Windows Defender, PowerShell commands) are discussed prominently, sometimes without Linux equivalents or with less detail for Linux. Some sections (e.g., Windows security baselines, Windows Defender) are Windows-only, but these are appropriately marked as such.

Recommendations

Present Linux and Windows instructions in parallel, or alternate which comes first to avoid implicit prioritization.
Expand Linux-specific guidance where Windows-specific tools are discussed (e.g., mention Linux antimalware options or clarify if none are required).
Where PowerShell commands are given, ensure equivalent Bash/CLI commands are provided and described with equal detail.
Clearly label Windows-only sections and provide links or notes for Linux alternatives where applicable.
Review the order of examples and ensure Linux is not consistently secondary.

Create Pull Request

Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page on securing an Azure Service Fabric cluster presents security scenarios and technologies applicable to both Azure-hosted clusters and standalone Windows clusters. However, it consistently references standalone clusters as 'Windows Server clusters' and provides links and examples only for Windows-specific standalone cluster security (certificate and Windows security). There is no mention of standalone Linux cluster security, nor are Linux-specific instructions, examples, or links provided. Windows terminology and tools (e.g., Windows certificate service, MakeCert.exe) are referenced without Linux equivalents or alternatives.

Recommendations

Add explicit guidance for securing standalone Linux Service Fabric clusters, including certificate setup and any Linux-specific authentication mechanisms.
Provide links to Linux-focused documentation or instructions for certificate management and cluster configuration on Linux.
When referencing certificate creation tools, mention Linux-compatible alternatives (e.g., OpenSSL) alongside Windows tools.
Clarify which security scenarios and recommendations apply equally to Linux clusters, and which are Windows-specific.
Ensure parity in example commands, templates, and walkthroughs for both Windows and Linux environments.

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 is notably Windows-focused: all manifest examples are based on the 'Windows Server 2016 Container Sample', and several instructions reference Windows-specific tools and concepts (e.g., 'winver' for OS build, Windows path formats, and PFX certificates). There is no mention of Linux equivalents, nor are there Linux-specific manifest examples or guidance for Linux containers. This creates friction for Linux users deploying Service Fabric containers.

Recommendations

Add parallel manifest examples based on Linux container samples, or clarify which elements differ for Linux clusters.
Where Windows-specific tools are referenced (e.g., 'winver'), provide Linux equivalents (e.g., 'cat /etc/os-release' or 'uname -r').
When discussing certificate handling, explicitly describe the Linux PEM scenario and how to access/use these files.
Use platform-neutral path formats in examples, or provide both Windows and Linux path variants.
Explicitly state at the top if the examples are only valid for Windows clusters, and link to Linux-specific documentation if available.

Create Pull Request

Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page exhibits a Windows bias by primarily referencing Windows-specific upgrade guides and tools, such as linking to Windows Server-specific instructions and the Patch Orchestration Application for Windows. There are no explicit Linux examples or references to Linux-based Service Fabric clusters, and all upgrade/configuration links point to Windows-focused documentation.

Recommendations

Clarify early in the article whether standalone Service Fabric clusters are supported on Linux, and if so, provide equivalent Linux upgrade/configuration instructions or links.
If Linux standalone clusters are supported, add Linux-specific examples and references alongside or before Windows ones.
If only Windows is supported for standalone clusters, explicitly state this at the top to avoid confusion for Linux/macOS users.
Where possible, generalize instructions or provide cross-platform guidance (e.g., editing ClusterConfig.json, using REST APIs) rather than referencing only Windows tools.

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 only PowerShell examples for reporting and querying Service Fabric health, with no equivalent examples for Linux/macOS users (e.g., using Azure CLI, REST API, or Service Fabric CLI). The only concrete example uses PowerShell cmdlets, and there is no mention of cross-platform tools or commands. This creates friction for Linux/macOS users who cannot use PowerShell natively.

Recommendations

Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
Include REST API examples for reporting and querying health, as these are platform-agnostic.
Mention and link to documentation for cross-platform tools (sfctl, REST API) alongside PowerShell, not just in passing.
Clearly indicate which tools are Windows-only and provide alternatives for other platforms.
Consider providing code snippets in Bash or with curl for REST API usage.

Create Pull Request

Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation is largely platform-neutral, but there are subtle indications of Windows bias. The only explicit OS-specific reference is in the section about upgrading OS images for cluster nodes, which links only to Windows patching guidance. Additionally, when mentioning command-line management, PowerShell is always listed before Azure CLI, and no Linux/macOS-specific tools or examples are provided. However, the majority of the content is applicable to all platforms, and Service Fabric supports both Windows and Linux clusters.

Recommendations

Add explicit references and links to Linux OS patching guidance for Service Fabric clusters, if available.
When listing management tools, alternate the order (e.g., 'using Azure CLI or PowerShell') or clarify that both are supported on all platforms.
If there are Linux/macOS-specific considerations for upgrades or cluster management, include a section or callout summarizing them.
Provide examples or links for Linux-based Service Fabric clusters where relevant, especially in sections about OS patching and certificate management.

Create Pull Request

Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation generally aims to be cross-platform, mentioning both Windows and Linux support for Service Fabric. However, there are several instances where Windows-specific tools, processes, or terminology are mentioned first or exclusively, such as references to 'auto-start Windows service', EXE/DLL files, and Windows-specific process names. Linux equivalents are not always provided or are mentioned after Windows. This may create confusion or friction for Linux/macOS users, though most critical concepts are still explained in a platform-agnostic way.

Recommendations

When describing node startup, clarify the equivalent process for Linux clusters (e.g., what starts the Service Fabric processes on Linux nodes).
When referencing EXE/DLL files, note that on Linux these would be ELF binaries or shared objects, and provide examples or clarifications.
Where Windows-specific process names are given (e.g., FabricHost.exe), mention the Linux equivalents or note that process names may differ.
In sections where Windows services or tools are referenced, add Linux equivalents or clarify cross-platform differences.
Review the ordering of examples and explanations to avoid always listing Windows first unless there is a technical reason.

Create Pull Request

Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides a PowerShell example for deploying Service Fabric applications, which is a Windows-centric tool. Windows file paths and certificate store names are mentioned first, with Linux equivalents only briefly referenced. There are no Linux CLI (e.g., Bash, sfctl) examples for deployment, and Windows terminology/tools are presented before Linux alternatives.

Recommendations

Add Linux deployment examples using sfctl or Bash scripts alongside PowerShell examples.
Mention Linux file paths and certificate store locations equally with Windows paths, not just as a note.
Clarify any differences in endpoint configuration or deployment between Windows and Linux clusters.
Consider providing a table or section explicitly comparing Windows and Linux approaches for endpoint specification and deployment.

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: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides examples for configuring Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, and it is presented as the exclusive scripting option for command-line automation. There are no examples for Linux/macOS CLI tools such as Azure CLI or Bash scripts. Additionally, PowerShell examples are given equal prominence to portal and ARM template methods, and are sometimes required for certain operations (e.g., removing primary node types), which may create friction for Linux/macOS users.

Recommendations

Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux/macOS.
Explicitly state when PowerShell is required due to Azure module limitations, and provide guidance for Linux/macOS users (e.g., using Azure Cloud Shell, which supports PowerShell and Bash).
Where possible, mention Bash scripting or other cross-platform automation options.
Review and update any sections where PowerShell is presented as the only automation option, ensuring Linux parity.

Create Pull Request

Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first

Summary

The documentation provides extensive PowerShell examples and references Windows-specific tools and patterns (such as the Key Vault VM extension for Windows, S-channel, and Windows certificate store locations). While the overall guidance is Azure-centric and applicable to both Windows and Linux VM/VMSS, the hands-on examples, troubleshooting, and technical deep-dives are predominantly Windows-focused. Linux equivalents (such as Linux VM extensions, certificate store paths, or CLI/bash scripting) are not mentioned or provided, and Windows terminology and tooling are presented first and exclusively in several sections.

Recommendations

Add Linux-specific examples for certificate provisioning, such as using the Key Vault VM extension for Linux or Azure CLI/bash scripts.
Document Linux certificate store paths and how Service Fabric interacts with them.
Include troubleshooting steps and automation scripts for Linux environments (e.g., bash, Python, Azure CLI).
Clarify which steps are Windows-only and provide Linux alternatives where possible.
Reference the Key Vault VM extension for Linux and link to its documentation alongside the Windows version.

Create Pull Request

Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy

Summary

The documentation provides detailed explanations and examples for X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows-specific terminology (e.g., 'LocalMachine\My' certificate store), Windows-centric troubleshooting (event logs, CAPI2 logging), and references to Win32 CryptoAPI and Windows cryptographic providers are presented before or instead of Linux equivalents. Linux paths (e.g., /var/lib/sfcerts) are mentioned only briefly and lack parity in troubleshooting and operational guidance.

Recommendations

Provide equivalent Linux/macOS examples and troubleshooting steps, such as how to locate Service Fabric certificates on Linux nodes, relevant log locations, and commands for certificate management.
Expand on Linux certificate store paths and clarify how certificate loading and validation occurs on Linux, including any differences in behavior or configuration.
Include Linux/macOS-specific error codes and remediation steps, or reference relevant tools (e.g., OpenSSL, systemd journal logs) for diagnosing certificate issues.
Balance Windows and Linux terminology throughout the document, ensuring Linux paths and tools are mentioned alongside Windows ones.
Where Windows APIs (e.g., CertGetCertificateChain) are referenced, provide Linux equivalents or note if functionality is identical or differs.

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 ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, with no equivalent CLI or Linux/macOS instructions. It references Service Fabric Explorer (a web tool, but often Windows-centric in documentation) and does not mention cross-platform alternatives. No Linux/macOS command-line examples are given, and the only automation example uses PowerShell.

Recommendations

Provide equivalent Azure CLI or Service Fabric CLI (sfctl) commands for bypassing Infrastructure Service, or clarify if such functionality is not available cross-platform.
Explicitly state if certain operations (like 'Invoke-ServiceFabricInfrastructureCommand') are only supported on Windows/PowerShell, and suggest alternatives for Linux/macOS users if available.
Add notes or examples for Linux/macOS users, including how to connect to Service Fabric clusters and perform administrative tasks using cross-platform tools.
Clarify whether Service Fabric Explorer is fully cross-platform and accessible from any OS/browser, or if there are platform-specific limitations.

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 generally aims for cross-platform coverage, but there are several areas where Windows tools and workflows are mentioned first or in more detail, and Linux equivalents are less prominent or only referenced via links. Some monitoring features (like EventStore APIs) are called out as Windows-only, but Linux alternatives are not always explained in equal depth. Examples and tutorials focus on .NET/Windows scenarios, and PowerShell/Windows Event Log are referenced without Linux command equivalents.

Recommendations

When mentioning Windows-specific tools (e.g., Event Log, Diagnostics Agent), provide parallel Linux instructions or explicitly link to Linux setup/configuration guides in the same section.
Add Linux-specific examples or code snippets where only Windows/PowerShell/Visual Studio workflows are shown (e.g., for application logging, cluster monitoring setup).
When listing recommended tools or agents, clearly indicate which are cross-platform and which are Windows-only, and provide Linux alternatives up front.
In the 'Recommended setup' section, include explicit Linux cluster monitoring instructions or a summary link to the Linux setup guide.
Where possible, provide sample commands or scripts for Linux (e.g., using Syslog, LTTng, or Linux CLI tools) alongside Windows/PowerShell examples.

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: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation is notably Windows-focused: all code examples use Windows containers (NanoServer), Windows-specific commands (cmd, set, exit), and reference only Windows container images. The only tooling example for querying deployment status is via PowerShell, with no Linux CLI or cross-platform alternatives given. There is no mention of Linux containers or how to implement RunToCompletion semantics for Linux-based workloads.

Recommendations

Provide parallel examples using Linux containers (e.g., using Ubuntu or Alpine images) with equivalent shell commands.
Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, add Linux-specific code and manifest examples.
Include instructions for querying deployment status using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), if available.
When referencing container images, mention both Windows and Linux options if the feature is supported on both.
Explicitly state if RunToCompletion is Windows-only, to avoid confusion for Linux users.

Create Pull Request

Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides multiple PowerShell-based examples for scaling operations, with no equivalent Linux CLI or cross-platform guidance. Steps for manual scaling reference PowerShell commands exclusively, and Windows tooling is mentioned first or solely in critical procedures. While Service Fabric supports Linux clusters, Linux users are left to infer or research their own command-line equivalents, creating friction.

Recommendations

Add equivalent Linux CLI (e.g., Bash, sfctl) examples alongside PowerShell commands for scaling operations.
Explicitly mention cross-platform tools and workflows where possible, such as Azure CLI or REST API usage.
Clarify which steps are universal and which are OS-specific, and provide links to Linux-specific documentation where relevant.
Consider restructuring step-by-step guides to present both Windows and Linux options in parallel.

Create Pull Request

Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation generally aims to be cross-platform, but several sections show a Windows-first bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are described in detail, while Linux equivalents are not mentioned or are left as TODOs. Some examples and links focus on Windows tools (e.g., PowerShell for disk encryption), and Linux instructions are missing or deferred. In some sections, Windows options are described before Linux, and Linux parity is not always clear.

Recommendations

Add explicit Linux examples and instructions where only Windows or PowerShell examples are given (e.g., disk encryption for Linux clusters).
When mentioning Windows-specific features (e.g., BitLocker, gMSA), provide Linux equivalents or state if not supported.
Ensure that Linux and Windows options are presented with equal prominence and detail, ideally side-by-side.
Remove or resolve TODOs about Linux support (e.g., 'Encrypt disks on Linux clusters?') and provide actionable guidance.
Include references to Linux tools (e.g., dm-crypt, LUKS) and Linux-compatible Service Fabric features where relevant.

Create Pull Request

Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation page for Service Fabric application upgrades demonstrates a notable Windows bias. PowerShell is used exclusively for code examples, and only Windows-specific tools (e.g., PowerShell cmdlets, http.sys) are mentioned. There are no equivalent examples or guidance for Linux users (e.g., using Azure CLI, REST API, or sfctl). The documentation assumes a Windows environment, which may create friction for Linux/macOS users.

Recommendations

Add equivalent Linux/macOS examples using Azure CLI, REST API, or sfctl where PowerShell is used.
Mention cross-platform tools and workflows alongside Windows-specific ones.
Clarify when certain features or limitations (e.g., http.sys, PowerShell cmdlets) are Windows-only.
Reorder sections or examples to present cross-platform solutions first, or at least in parallel with Windows examples.

Create Pull Request

Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation provides detailed PowerShell examples for managing dynamic node tags and configuring services, but does not include equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API usage). PowerShell is a Windows-centric tool, and its exclusive use here creates friction for users on non-Windows platforms.

Recommendations

Add examples using cross-platform tools such as Azure CLI or REST API for managing node tags and configuring services.
Explicitly mention whether PowerShell Core (cross-platform) is supported, and if so, provide guidance for Linux/macOS users.
Include Bash or shell script examples where possible.
Clarify if certain operations are only possible via PowerShell or C# APIs, and provide workarounds or alternatives for Linux/macOS users.

Create Pull Request

Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation page on describing Azure Service Fabric apps and services demonstrates some Windows bias. It references the use of Visual Studio (a Windows-centric tool) for authoring manifests and checking schema, and mentions the ServiceFabric PowerShell module as a way to create service instances, without mentioning Linux/macOS equivalents or cross-platform alternatives. Windows paths are used in examples for schema files, and there are no references to Linux tooling or workflows for manifest authoring or validation. However, the core manifest concepts and XML examples themselves are platform-agnostic.

Recommendations

Add instructions or references for validating manifest XML schema on Linux/macOS, such as using xmllint or VS Code with the XML extension.
Mention cross-platform tools (e.g., Azure CLI, Service Fabric CLI (sfctl)) for managing Service Fabric applications and services, in addition to or instead of PowerShell.
When referencing file paths or tools, provide Linux/macOS equivalents or note if a feature is only available on Windows.
Clarify that Visual Studio is optional and suggest VS Code or other editors for cross-platform development.
If Service Fabric features are Windows-only, explicitly state this to set expectations for Linux/macOS users.

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 heavily references PowerShell cmdlets and .NET APIs for operational tasks (deploy, upgrade, remove, maintain), with only passing mention of REST APIs and no explicit Linux/CLI examples. There is no coverage of Linux-native tools or Service Fabric CLI (sfctl) usage in the main procedural steps, despite a link to CLI docs at the top. This creates friction for Linux/macOS users, who are likely to use sfctl or Azure CLI rather than PowerShell.

Recommendations

Add explicit sfctl (Service Fabric CLI) command examples alongside PowerShell cmdlets for all operational steps (deploy, upgrade, remove, maintain, etc.).
Where PowerShell is mentioned, clarify if/when it is available cross-platform (e.g., via PowerShell Core on Linux/macOS), or provide alternative commands.
In procedural lists, present REST API, sfctl, and PowerShell options together, or group by platform/tool.
Add a short section or callout for Linux/macOS users, linking to relevant CLI documentation and noting any platform-specific considerations.
Ensure that all code snippets and automation examples have Linux equivalents (e.g., bash/sfctl/az CLI).

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 heavily features PowerShell cmdlets for Service Fabric application upgrades, with all command-line examples given in PowerShell syntax. There is no mention of Linux/macOS equivalents, such as Azure CLI, REST API, or Service Fabric CLI (sfctl), nor are cross-platform tools or workflows discussed. The documentation assumes the reader is using Windows/PowerShell, creating friction for Linux/macOS users.

Recommendations

Add equivalent examples using Azure CLI and/or Service Fabric CLI (sfctl) for all PowerShell commands.
Explicitly mention cross-platform tools and workflows where applicable.
Clarify which features are available on Linux clusters and provide guidance for Linux/macOS users.
Reorganize sections so that cross-platform approaches are presented alongside or before Windows-specific ones.
Link to Linux-specific documentation or note any limitations for Linux clusters.

Create Pull Request

Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first

Summary

The documentation page primarily discusses data serialization concepts in the context of Azure Service Fabric, which is cross-platform. However, in the 'Next steps' section, it lists 'Upgrading your Application Using Visual Studio' and 'Upgrading your Application Using PowerShell' as the first two upgrade guides, both of which are Windows-centric tools. There are no explicit Linux/macOS CLI or cross-platform upgrade examples or links provided, and the default serializer discussed is .NET's Data Contract, which is cross-platform, so no bias there.

Recommendations

Add links or references to cross-platform upgrade guides using Azure CLI or Service Fabric CLI (sfctl), if available.
If PowerShell is mentioned, also mention cross-platform PowerShell Core or Bash equivalents, or clarify if only Windows PowerShell is supported.
Consider listing cross-platform or Linux/macOS upgrade options before or alongside Windows-specific tools in the 'Next steps' section.
Explicitly state if certain upgrade methods (e.g., Visual Studio) are Windows-only, and provide alternatives for Linux/macOS users.

Create Pull Request

Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation page presents PowerShell and Visual Studio (Windows tools) upgrade parameters first, with detailed tables and examples, while Linux/macOS equivalents (SFCTL/CLI) are described later and less prominently. Most parameter tables and examples are Windows-centric, and Linux users must scroll further to find relevant information. There are no explicit Linux/macOS command examples in the main body, and the structure implies a Windows-first workflow.

Recommendations

Reorganize the documentation to present SFCTL (CLI) parameters and workflows alongside PowerShell/Visual Studio, or in parallel sections, rather than after all Windows tooling.
Provide explicit Linux/macOS command-line examples (using SFCTL) in the main parameter tables, not only in a separate section.
Clarify at the start that all features are available cross-platform, and that SFCTL is the recommended tool for Linux/macOS.
Add a summary table mapping PowerShell/Visual Studio parameters to SFCTL equivalents for easy cross-reference.
Ensure that Linux/macOS users are not required to refer to Windows tooling sections for parameter explanations.

Create Pull Request

Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page for on-demand backup in Azure Service Fabric is heavily biased towards Windows/PowerShell usage. All code examples use PowerShell, including REST API calls, and there are no examples or guidance for Linux/macOS users (e.g., Bash, curl, or Azure CLI). The prerequisite section requires installation of a PowerShell module, and there is no mention of cross-platform alternatives. The REST API is always demonstrated via PowerShell, not via curl or other tools. This creates friction for Linux/macOS users, who may not have access to PowerShell or prefer native tools.

Recommendations

Add Bash/curl examples for REST API calls alongside PowerShell examples.
Mention Azure CLI commands if available for triggering backups and tracking progress.
Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available cross-platform (PowerShell Core), and if not, provide alternatives.
Provide guidance for connecting to Service Fabric clusters from Linux/macOS (e.g., using REST API directly, Azure CLI, or other tools).
Reorder examples so that REST API usage (which is platform-neutral) is shown first, followed by platform-specific tooling.

Create Pull Request

Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation is heavily focused on PowerShell-based workflows, with all command-line examples using PowerShell syntax and Windows-specific modules. There are no equivalent examples for Linux/macOS users (e.g., using Bash, curl, or cross-platform tools), and the required tooling (Microsoft.ServiceFabric.Powershell.Http) is Windows/PowerShell-centric. This creates friction for non-Windows users, who must adapt or reverse-engineer the REST API calls from PowerShell examples.

Recommendations

Provide equivalent Bash/curl examples for REST API calls, demonstrating how to authenticate and trigger restores from Linux/macOS.
Clarify whether the PowerShell modules are supported on PowerShell Core (pwsh) on Linux/macOS, and document any limitations.
List required certificates and authentication steps in a cross-platform manner.
Explicitly state if certain operations are only supported on Windows, and offer alternative guidance for Linux/macOS users where possible.
Add a section summarizing cross-platform support for Service Fabric backup/restore tooling.

Create Pull Request

Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first

Summary

The documentation provides both Azure CLI and PowerShell examples for deploying Resource Manager templates, but PowerShell is presented as a primary alternative, which is Windows-centric. In the cluster upgrade section, only PowerShell commands are given for manual upgrades, with no Linux/bash equivalent. Windows registry keys and Windows Update settings are discussed without mentioning Linux equivalents or alternatives. Windows configuration properties are shown before Linux is referenced. However, links to both Windows and Linux cluster creation tutorials are provided, and the core template examples are platform-neutral.

Recommendations

Add Linux/bash equivalents for manual cluster upgrade commands (e.g., using bash or Azure CLI instead of PowerShell).
When discussing OS upgrade configuration, mention Linux-specific options or clarify if steps are Windows-only.
Provide guidance or examples for disabling automatic updates on Linux VMSS nodes, if applicable.
Where Windows registry keys or Windows Update settings are referenced, add notes about Linux patching approaches or clarify if the guidance is Windows-specific.
Ensure that PowerShell examples are accompanied by bash/Azure CLI equivalents throughout the documentation.

Create Pull Request

Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation provides both Windows and Linux guidance for Service Fabric networking, but there are several areas where Windows is prioritized or Linux parity is lacking. Windows/PowerShell examples and terminology are mentioned first or exclusively in some sections (e.g., Client API, Azure DevOps, ARM template sample, and application networking). PowerShell is referenced as the primary API client, and Windows-specific tools and features (such as RDP, Windows Updates, and Windows container networking) are discussed in detail, sometimes without equivalent Linux examples or guidance. Linux-specific instructions are present but often secondary or less detailed.

Recommendations

Ensure Linux examples and terminology are provided alongside Windows/PowerShell examples, especially in sections discussing API access, DevOps, and application networking.
Add explicit Linux CLI (az, bash) examples where PowerShell is referenced.
Provide Linux-focused ARM template samples and links, not just Windows ones.
Clarify when guidance applies to both Windows and Linux, and highlight any differences.
Expand Linux container networking guidance to match Windows container coverage.

Create Pull Request

Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides some Windows-centric examples and references, such as using Windows-style file paths (e.g., 'D:\\SvcFab') in the Service Fabric extension snippet and linking to PowerShell scripts for tasks like changing RDP port ranges and admin credentials. While Linux is mentioned in the extension type ('ServiceFabricLinuxNode'), the examples and next steps focus on Windows tools and patterns.

Recommendations

Provide Linux-style file path examples (e.g., '/var/lib/servicefabric') alongside Windows paths in extension configuration.
Include links or references to equivalent Linux-based management scripts or instructions for tasks like changing SSH port ranges or updating Linux admin credentials.
When referencing remote connection methods, mention SSH for Linux nodes in addition to RDP for Windows nodes.
Ensure that examples and guidance are balanced between Windows and Linux where both are supported.

Create Pull Request

Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page provides code examples for advanced placement policies in Service Fabric using C# and PowerShell. All CLI examples are PowerShell-based, with no equivalent Bash, Linux CLI, or cross-platform command-line examples. PowerShell is presented as the only scripting interface for service creation and configuration, which may create friction for Linux/macOS users who typically use Bash or Azure CLI. The documentation does not mention or provide guidance for Linux-native tools or workflows.

Recommendations

Add Azure CLI or Bash examples for service creation and placement policy configuration, if supported.
Explicitly mention whether PowerShell commands are cross-platform or provide alternatives for Linux/macOS users.
Clarify any platform limitations for Service Fabric management tools and link to Linux/macOS-specific guidance if available.
Consider including a table or section comparing Windows and Linux management options for Service Fabric clusters.

Create Pull Request

Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides examples for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no Linux/macOS shell (e.g., Bash, CLI) equivalents. PowerShell is presented as the only scripting option, and there is no mention of Linux tools or cross-platform CLI commands. This creates friction for Linux/macOS users, especially since Service Fabric supports Linux containers and clusters.

Recommendations

Add Azure CLI or Bash script examples for configuring scaling policies, especially for Linux clusters.
Explicitly mention cross-platform tooling where available (e.g., Azure CLI, REST API).
Clarify which PowerShell commands are available on Linux (via PowerShell Core), and provide alternatives if not.
Include notes or links to Linux-specific guidance for Service Fabric auto scaling.
Consider providing sample YAML or JSON for ARM templates if relevant.

Create Pull Request

Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying health reports but does not include equivalent examples for Linux/macOS users (e.g., using sfctl or REST API). The only concrete command-line example is Windows/PowerShell-specific, which may create friction for users managing Service Fabric clusters from non-Windows environments.

Recommendations

Add equivalent Linux/macOS examples using sfctl (the Service Fabric CLI) or REST API calls alongside PowerShell examples.
Explicitly mention cross-platform management options and link to relevant documentation for Linux/macOS users.
When showing command-line examples, provide both PowerShell and sfctl/REST API versions to ensure parity.

Create Pull Request

Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation provides command-line examples exclusively using PowerShell cmdlets (e.g., New-ServiceFabricApplication, Update-ServiceFabricApplication, Get-ServiceFabricApplicationLoadInformation) and C# APIs. There are no examples for Linux/macOS users, such as using Azure CLI, REST API, or cross-platform tools. This creates friction for users managing Service Fabric clusters from non-Windows environments.

Recommendations

Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform.
Mention and link to REST API documentation for users who may wish to automate via HTTP.
Explicitly state if certain management operations are only possible via PowerShell or C# SDK, and if so, clarify the platform requirements.
If PowerShell Core (pwsh) is supported cross-platform, clarify this and provide guidance for Linux/macOS users.
Consider adding a section summarizing cross-platform management options for Service Fabric clusters.

Create Pull Request

Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json), but Windows-specific XML examples and references (e.g., <WindowsServer> element) are consistently presented first and more prominently. PowerShell examples are included, but there are no Linux shell or CLI equivalents. The documentation does not mention Linux-specific tools or patterns, nor does it clarify Linux/macOS parity for local development clusters or standalone deployments.

Recommendations

Present Linux/cross-platform examples (ClusterConfig.json) before or alongside Windows (ClusterManifest.xml) examples to avoid Windows-first bias.
Include Azure Service Fabric CLI (sfctl) or REST API examples for service creation and updates, which are cross-platform, instead of only PowerShell and C#.
Clarify whether standalone Service Fabric clusters can be run on Linux, and if so, provide explicit Linux/macOS guidance and examples.
Add notes or sections highlighting any differences or limitations for Linux/macOS users, especially for local development clusters.
Where possible, provide bash or shell script equivalents for PowerShell commands.

Create Pull Request

Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides code examples for C# and PowerShell, with PowerShell being the only CLI example shown. There are no Linux/macOS CLI equivalents (such as Azure CLI or Bash scripts), and PowerShell is presented before any mention of cross-platform tools. This creates friction for Linux/macOS users who may not use PowerShell or develop on Windows.

Recommendations

Add Azure CLI examples for service creation and metric configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
Include Bash script examples or reference how to use REST APIs for metric management, which are platform-agnostic.
Clarify whether PowerShell examples are usable on PowerShell Core (cross-platform) or are Windows-only.
Consider providing sample YAML for ARM templates or Bicep for resource deployment, which are platform-neutral.
Explicitly mention any limitations or differences for Linux-based Service Fabric clusters, if applicable.

Create Pull Request

Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation provides PowerShell and C# examples for configuring Service Fabric move cost, but does not include equivalent Linux/bash/CLI examples. PowerShell is a Windows-centric tool, and the lack of Azure CLI or REST API examples creates friction for Linux/macOS users. The configuration file examples (ClusterManifest.xml, ClusterConfig.json) are platform-neutral, but the operational examples are Windows-focused.

Recommendations

Add Azure CLI examples for creating and updating Service Fabric services with move cost settings.
If possible, include REST API examples for move cost operations.
Clarify whether PowerShell examples can be run cross-platform (e.g., with PowerShell Core on Linux/macOS), or provide bash equivalents.
Explicitly mention if certain operations are only supported via PowerShell or C# SDK, and provide guidance for Linux users.

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_tools ⚠️ missing_linux_example

Summary

The documentation provides configuration examples using XML, JSON, PowerShell, and C# APIs. However, all command-line examples for dynamic configuration use PowerShell, which is Windows-centric. There are no CLI or script examples for Linux/macOS users, such as Azure CLI, Bash, or REST API equivalents. This creates friction for non-Windows users wishing to automate or script these operations.

Recommendations

Add equivalent Azure CLI or REST API examples for creating and updating service sensitivity and maximum load, as these are cross-platform.
If PowerShell is required due to Service Fabric SDK limitations, explicitly state this and provide guidance for Linux users (e.g., using Azure CLI, REST, or Service Fabric CLI if available).
Consider including Bash or shell script examples for configuration file edits, or reference cross-platform tools where possible.
Clarify in the documentation if certain APIs or tools are only available on Windows, and suggest alternatives for Linux/macOS users.

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 for the Azure Service Fabric application resource model demonstrates a notable Windows bias. All command-line deployment and resource management examples use PowerShell cmdlets (e.g., New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without providing Azure CLI equivalents. The application packaging workflow is shown using Visual Studio, a Windows-centric tool, with no mention of cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented exclusively and first.

Recommendations

Add Azure CLI examples for all PowerShell cmdlets used (e.g., az deployment group create, az resource delete).
Include instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SFCTL, or manual packaging via scripts).
Mention or provide examples for using VS Code or other cross-platform editors for application packaging.
Explicitly state that the steps can be performed on Linux/macOS where applicable, or clarify any Windows-only requirements.
Reorder or parallelize examples so that both Windows and Linux/macOS users see relevant instructions.

Create Pull Request

Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI (e.g., Bash, Azure CLI) examples. Windows tools and patterns (PowerShell, ApplicationManifest.xml/Visual Studio) are mentioned before Linux alternatives, and Linux-specific limitations are highlighted without guidance for Linux users. There are no Linux-native command examples or instructions for Linux users to accomplish the same tasks.

Recommendations

Add Azure CLI or Bash examples for setting DNS names and managing services, especially for Linux clusters.
Clarify how Linux users can set DNS names (e.g., via ARM templates, Azure CLI) and manage Service Fabric services without PowerShell.
Provide guidance or links for Linux users to accomplish tasks that are shown with Windows tools (e.g., ApplicationManifest.xml editing, PowerShell commands).
Explicitly state any differences in workflow for Linux users and offer alternatives where portal or Windows tools are not available.

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: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page demonstrates moderate Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd'), and does not provide equivalent Linux/macOS paths or instructions. The examples and directory structures use Windows conventions (e.g., .exe files), and there is no mention of Linux packaging, deployment, or cross-platform tooling. Visual Studio is mentioned as a packaging tool, but no Linux alternatives (such as CLI tools or cross-platform editors) are discussed. No PowerShell-specific commands are present, but Windows-centric patterns are evident.

Recommendations

Add Linux/macOS equivalents for file paths and SDK installation locations.
Provide examples using Linux executables (e.g., ELF binaries) and directory structures.
Mention and document cross-platform command-line tools for packaging and deploying guest executables.
Clarify whether Service Fabric supports Linux guest executables and, if so, provide guidance for Linux users.
Include instructions for using editors and tools available on Linux/macOS, not just Visual Studio.

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 with sfctl) examples. PowerShell and Windows-centric tools are referenced exclusively for command-line operations, creating friction for Linux users. There is a brief mention of platform differences, but practical Linux usage is not demonstrated.

Recommendations

Add examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS, alongside PowerShell examples.
Explicitly mention Linux-compatible tools and commands where administrative actions are discussed.
Where PowerShell cmdlets are referenced (e.g., New-ServiceFabricService, Update-ServiceFabricService), provide equivalent sfctl commands.
Clarify in each example which platforms the commands apply to, and link to Linux/macOS setup guides for Service Fabric CLI.
Consider including a short section or appendix summarizing cross-platform management options for Service Fabric clusters.

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_tools ⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific tools and processes (e.g., PowerShell, Visual Studio, Windows services like FabricHost.exe) are often mentioned first or exclusively, with Linux equivalents either omitted or referenced only briefly. Some sections (e.g., standalone clusters) are Windows-only, but this is called out. Linux support is acknowledged, but practical Linux examples, commands, and tools are largely missing.

Recommendations

Add Linux-specific examples and commands (e.g., using Bash/CLI instead of or alongside PowerShell).
When referencing tools like Visual Studio, also mention cross-platform alternatives (e.g., VS Code, CLI tools) for Linux users.
Where Windows services/executables are described (e.g., FabricHost.exe), clarify Linux equivalents or note differences explicitly.
In 'Next steps' and quickstart links, include Linux getting started guides and not just Windows-focused ones.
Ensure that CLI and REST API examples are shown alongside PowerShell, not as an afterthought.
Where features are Windows-only, clearly call this out (as is done for standalone clusters), and provide alternative guidance for Linux where possible.

Create Pull Request

Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation page on Azure Service Fabric Events demonstrates a Windows bias by primarily referencing ETW/Windows Event logs and the Windows Azure diagnostics agent as the default mechanisms for event logging and collection. There is no mention of Linux equivalents or guidance for accessing Service Fabric events on Linux clusters, nor are Linux-specific tools or patterns discussed. Windows tools and patterns are presented first and exclusively.

Recommendations

Add explicit guidance on how Service Fabric events are logged and accessed on Linux clusters, including any differences in event sources or logging mechanisms.
Include examples or references to Linux-compatible monitoring tools (e.g., syslog, journald, or Azure Monitor integration for Linux nodes).
Clarify if certain event types or logging features are Windows-only, and provide Linux alternatives or note any limitations.
Reorder or balance the documentation so that Linux and Windows approaches are presented with equal prominence where both are supported.

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_tools ⚠️ missing_linux_example

Summary

The documentation provides only PowerShell and C# examples for managing Service Fabric services, with no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST via curl). All command-line instructions reference PowerShell cmdlets, which are primarily Windows-centric, and there is no mention of Linux-native tools or workflows.

Recommendations

Add Azure CLI examples for creating and managing Service Fabric services, as Azure CLI is cross-platform and widely used on Linux/macOS.
Include REST API examples using curl or similar tools to demonstrate platform-agnostic management.
Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS for Service Fabric management, and provide examples if so.
Where possible, provide Bash or shell script equivalents for common operations.
Explicitly mention any differences or limitations for Linux/macOS users, and link to relevant cross-platform documentation.

Create Pull Request

Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation frequently references PowerShell for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and the main example for programmatic access is PowerShell. There is no mention of Linux/macOS command-line tools (such as Azure CLI or Bash scripts), nor are there examples for these platforms. The 'Next steps' section also points only to PowerShell-based deployment guidance, reinforcing a Windows-first perspective.

Recommendations

Add equivalent examples for Linux/macOS users, such as using Azure CLI or Bash scripts to retrieve the cluster manifest.
Include references to cross-platform tools (e.g., Azure CLI, REST API usage with curl) alongside PowerShell.
Update 'Next steps' to include links to documentation for deploying applications using Linux/macOS tools.
Clarify in the text that Service Fabric management can be performed from non-Windows platforms and provide relevant guidance.

Create Pull Request

Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Service Fabric. However, there is a notable Windows bias in several areas: HTTP.sys (a Windows-only technology) receives extensive coverage and is discussed before Kestrel in many sections, with detailed explanations and code samples. Windows-specific tools and concepts (such as netsh and Windows HTTP Server API) are referenced without Linux equivalents. While Kestrel is recommended for Linux and cross-platform scenarios, the documentation often presents Windows patterns first and provides more depth for Windows-specific features.

Recommendations

Reorder sections to present Kestrel (cross-platform) before HTTP.sys (Windows-only), emphasizing Linux/macOS parity.
Clearly mark HTTP.sys sections as Windows-only and provide links or notes for Linux/macOS users.
Add explicit Linux/macOS guidance for Service Fabric scenarios, including any OS-specific configuration steps or troubleshooting.
Where Windows tools (like netsh) are mentioned, clarify their purpose and note that they are not required for Linux/Kestrel scenarios.
Ensure all code samples and configuration instructions for Kestrel are as detailed as those for HTTP.sys, including HTTPS setup and endpoint configuration.

Create Pull Request

Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page for Replica soft delete in Service Fabric heavily references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) as the primary method for interacting with the feature. There are no examples or explicit instructions for Linux/macOS users, such as using the Service Fabric CLI (sfctl) or REST APIs, nor is it clarified whether equivalent functionality is available cross-platform. This creates friction for non-Windows users.

Recommendations

Add equivalent examples using sfctl (Service Fabric CLI) commands for Linux/macOS users, if available.
Document REST API usage for managing replica soft delete, if supported.
Clarify in the documentation whether the PowerShell cmdlets are Windows-only and what alternatives exist for Linux/macOS users.
Explicitly state platform support for the feature and its management APIs.
Consider including a table summarizing management options (PowerShell, sfctl, REST) and their platform compatibility.

Create Pull Request

Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation references PowerShell for deployment/removal tasks and links to a PowerShell module for downloading ServicePackages. There are no explicit Linux or cross-platform CLI examples, and PowerShell is mentioned as the primary tool for operational tasks, suggesting a Windows-first approach. However, the core lifecycle concepts are platform-neutral.

Recommendations

Add equivalent Linux/macOS CLI examples (e.g., Azure CLI, Bash) alongside PowerShell instructions.
Clarify which steps/tools are cross-platform and which are Windows-specific.
Provide links to Linux/macOS documentation for Service Fabric operations where available.
Mention if PowerShell Core (pwsh) is supported on Linux/macOS for relevant tasks.

Create Pull Request

Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides examples for managing application parameters in Service Fabric, with a noticeable emphasis on PowerShell and Visual Studio workflows. PowerShell is mentioned first for application creation, and Visual Studio parameter files are discussed in detail, both of which are Windows-centric tools. Linux equivalents (sfctl and install.sh) are mentioned, but not as prominently or with as much detail.

Recommendations

Provide more detailed examples and workflows for Linux/macOS users, such as using sfctl and install.sh for parameter passing.
Ensure that Linux tools and commands are given equal prominence and explanation as Windows/PowerShell tools.
Add explicit guidance for configuring and deploying applications from Linux/macOS environments, including sample scripts.
Consider reordering sections so that cross-platform tools (sfctl, install.sh) are presented before Windows-specific tools.

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 commands and examples, with no mention of Azure CLI, Bash, or Linux/macOS workflows. Windows tools and patterns (such as RDP and Windows command prompt ping) are referenced exclusively or before any cross-platform alternatives. This creates friction for Linux/macOS users, who must translate instructions or find their own equivalents.

Recommendations

Add Azure CLI examples alongside PowerShell for all deployment steps, as Azure CLI is cross-platform.
Mention Bash or shell scripting options for Linux/macOS users where relevant.
Provide guidance for accessing Service Fabric nodes using SSH instead of RDP, and show SSH-based 'ping' commands.
Clarify that all ARM template operations can be performed from any OS, and link to cross-platform tooling documentation.
Where PowerShell is used, note that Azure CLI is available and provide equivalent commands.

Create Pull Request

Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page provides detailed examples for reporting health in Service Fabric using PowerShell, which is primarily a Windows tool. PowerShell examples are prominent and shown before REST examples. There are no equivalent Linux/macOS CLI or scripting examples (e.g., Bash, curl, Azure CLI), nor is there mention of Linux-native tools or patterns for health reporting. This creates friction for Linux/macOS users, who must rely on REST or API without clear guidance or parity.

Recommendations

Add examples using Bash and curl for REST health report submission.
Mention and demonstrate use of Azure CLI (az) for Service Fabric health reporting if supported.
Clarify which PowerShell commands are cross-platform (PowerShell Core) and which are Windows-only.
Provide guidance for Linux/macOS users on how to perform equivalent tasks, including prerequisites and authentication.
Consider reordering examples so REST or cross-platform methods are shown before or alongside PowerShell.

Create Pull Request

Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation is heavily oriented towards Visual Studio workflows, referencing Windows-specific tools and patterns (e.g., F5/Ctrl+F5/Publish, right-click in Visual Studio, Visual Studio deployments). There are no examples or guidance for Linux/macOS users or for cross-platform tooling (e.g., CLI, VS Code). PowerShell is mentioned as an alternative for service creation, but only in passing. The documentation does not clarify whether or how StartupServices.xml can be used outside Visual Studio/Windows.

Recommendations

Clarify whether StartupServices.xml is supported or relevant for Linux/macOS users and non-Visual Studio workflows.
If possible, provide equivalent instructions or guidance for cross-platform tools (e.g., Azure CLI, Service Fabric CLI, VS Code).
Explicitly state if StartupServices.xml is a Visual Studio/Windows-only feature at the top of the documentation.
If the feature is Windows-only, add a clear note to prevent confusion for Linux/macOS users.
If partial support exists for non-Windows environments, provide examples and workflows for those platforms.

Create Pull Request

Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation page provides usage instructions for the Fault Analysis Service in Service Fabric, mentioning C# and PowerShell as the primary ways to interact with the service. PowerShell is a Windows-centric tool, and no Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API usage) are given. Additionally, PowerShell is mentioned before any Linux-friendly alternatives, and there is no guidance for Linux users on how to use the Fault Analysis Service.

Recommendations

Add examples for interacting with the Fault Analysis Service using Azure CLI, Bash scripts, or REST API calls, which are cross-platform.
Clarify whether the Fault Analysis Service APIs can be used from Linux/macOS environments, and provide guidance if so.
If PowerShell Core (cross-platform) is supported, specify this and provide examples for Linux/macOS users.
Mention any limitations or prerequisites for Linux/macOS users explicitly.

Create Pull Request

Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation is heavily focused on Windows-centric tools and workflows, specifically Visual Studio and PowerShell. All upgrade instructions and examples reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS alternatives or cross-platform CLI tools. There are no examples or guidance for users on Linux or macOS, and the PowerShell requirement for manual upgrades is presented without alternatives.

Recommendations

Add instructions and examples for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST APIs.
Include guidance for Linux/macOS users, such as how to configure upgrades without Visual Studio or PowerShell.
Mention and link to any available Service Fabric SDKs or tools for Linux/macOS, if applicable.
Clarify if certain upgrade scenarios are Windows-only, or provide parity where possible.

Create Pull Request

Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page, while focused on Ubuntu Linux VHD creation for Azure, exhibits Windows bias in several areas. Hyper-V (a Windows-only virtualization tool) is mentioned as the primary example for creating VHDs, and PowerShell's Convert-VHD cmdlet is referenced for disk conversion without providing Linux alternatives. Steps involving Hyper-V Manager are described in detail, but equivalent instructions for Linux-based virtualization tools (like qemu-img or VirtualBox) are missing. Windows extraction instructions are given (via WSL), but Linux-native extraction is not explicitly described. This bias may create friction for Linux/macOS users who do not have access to Windows tools.

Recommendations

Add Linux-native instructions for creating and converting VHDs (e.g., using qemu-img or VBoxManage).
Provide extraction steps for prebuilt images directly on Linux/macOS, not just via WSL on Windows.
Include guidance for Linux-based virtualization platforms (such as KVM, VirtualBox, or QEMU) alongside Hyper-V.
Reference Linux/macOS tools for disk conversion and management, and clarify which steps are platform-specific.
Reorder sections so Linux-native approaches are presented first or in parallel with Windows-specific instructions.

Create Pull Request

Virtual Machines Resize a virtual machine ...blob/main/articles/virtual-machines/sizes/resize-vm.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 detailed PowerShell examples for resizing Azure VMs, including scripts for both standalone VMs and those in availability sets. PowerShell is a Windows-centric tool, and its examples are more extensive and appear before Azure CLI and Terraform. The Terraform section references Windows VM quickstart code, and the CLI examples use Bash, but PowerShell is presented as the primary scripting method. There is no explicit Linux example (e.g., Bash or shell script) for resizing VMs outside of Azure CLI, and Windows tools/patterns are mentioned first and more thoroughly.

Recommendations

Add parity between PowerShell and Azure CLI examples by providing equally detailed Bash/shell scripts for Linux/macOS users.
In the Terraform section, reference both Windows and Linux VM quickstart code, not just Windows.
Reorder sections so that Azure CLI (cross-platform) is presented before PowerShell.
Explicitly mention that Azure CLI works on Linux/macOS and provide guidance for those environments.
Where PowerShell is used, clarify that it is available on Linux/macOS, but provide Bash alternatives for common tasks.

Create Pull Request

Virtual Machines Create a VM from a generalized image in a gallery ...icles/virtual-machines/vm-generalized-image-version.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides both Azure CLI and PowerShell examples for creating VMs from generalized images in a gallery. However, PowerShell examples are heavily focused on Windows-specific patterns (e.g., Set-AzVMOperatingSystem -Windows), and Windows VM creation is shown first or exclusively in several PowerShell sections. CLI examples generally default to Linux, but PowerShell sections do not offer Linux-specific instructions or parity. Additionally, PowerShell is a Windows-centric tool, and its usage is prominent throughout the page.

Recommendations

Add explicit Linux VM creation examples in PowerShell sections, using Set-AzVMOperatingSystem -Linux.
Clarify in PowerShell sections how to create Linux VMs, including SSH key authentication and Linux-specific configuration.
Where possible, provide Bash or shell script equivalents for resource setup (network, NIC, etc.) for Linux users.
Ensure that both CLI and PowerShell sections consistently mention Linux and Windows options, rather than defaulting to Windows in PowerShell.
Consider adding a note that PowerShell is cross-platform, but highlight any Windows-specific limitations or patterns.

Create Pull Request

Virtual Machines Deploy a Trusted Launch VM ...ain/articles/virtual-machines/trusted-launch-portal.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides both Linux and Windows guidance for deploying Trusted Launch VMs, but PowerShell examples are exclusively for Windows, and Windows is often the default in PowerShell and some template sections. CLI examples are Linux-focused, but PowerShell sections do not show Linux VM creation, and Windows images are used by default. In some multi-OS sections, Windows is shown first or exclusively in PowerShell, which may create friction for Linux users who prefer or require scripting via PowerShell.

Recommendations

Add PowerShell examples for deploying Linux Trusted Launch VMs, including using Linux images and parameters.
In PowerShell sections, provide both Linux and Windows variants, or clearly indicate that PowerShell is Windows-focused and recommend Azure CLI for Linux users.
When showing multi-OS template or scripting examples, alternate the order or provide parallel Linux and Windows examples in each section.
In PowerShell code, use Linux images and parameters where appropriate, or provide a toggle/tab for Linux/Windows.
Explicitly mention in PowerShell sections that Linux users should use Azure CLI if PowerShell support is limited.

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: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

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. CLI examples are simpler and less comprehensive. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. Additionally, PowerShell examples are often presented immediately after CLI, which is a more cross-platform tool, but the CLI examples are less thorough.

Recommendations

Expand Azure CLI examples to include full VM/network configuration steps, matching the detail level of PowerShell examples.
Explicitly note that Azure CLI is cross-platform and recommend it for Linux/macOS users.
Consider including Bash shell scripting examples for Linux users where appropriate.
Ensure that all critical workflows shown in PowerShell are also available in CLI, with equivalent detail.
Add a brief section clarifying tool parity and platform recommendations for users.

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: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, in some sections, Windows-specific scenarios (such as IIS lift-and-shift) are mentioned before Linux examples, and Windows container details are sometimes more elaborated. Still, Linux examples and tutorials are present and linked, and Linux support is clearly described.

Recommendations

Ensure Linux and Windows examples are presented with equal prominence and detail.
When listing scenarios or features, alternate the order or group by OS to avoid implicit prioritization.
Expand Linux-specific scenarios (e.g., Apache/Nginx lift-and-shift) to match the detail given to Windows/IIS.
Where possible, provide parallel Linux and Windows code snippets or references.

Create Pull Request

Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation page for Service Fabric application and service manifest examples displays mild Windows bias. Windows-specific concepts (such as running scripts via .bat files, references to NETWORKSERVICE, and local admin accounts) are used throughout the examples. The only script example is a Windows batch file (Setup.bat), and the documentation mentions using the ServiceFabric PowerShell module for service creation. There is no explicit mention of Linux equivalents, such as shell scripts (.sh), Linux user accounts, or Linux-specific deployment notes. However, the manifest XML itself is cross-platform, and the page does not block Linux users from completing the task.

Recommendations

Add examples or notes for Linux deployments, such as using shell scripts (.sh) in SetupEntryPoint.
Clarify that user and group principals can be mapped to Linux users/groups and provide guidance for Linux clusters.
Mention Linux-compatible tools for service creation (e.g., Azure CLI or REST API) alongside PowerShell.
Include a brief section on cross-platform considerations for Service Fabric manifests.

Create Pull Request

Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell (a Windows-centric tool) is often presented before CLI, and some advanced configuration examples are more detailed in PowerShell. There are no Linux-specific shell examples (e.g., Bash scripts), and PowerShell is referenced more frequently than necessary, which may create friction for Linux/macOS users.

Recommendations

Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
Ensure all PowerShell examples have equivalent Azure CLI examples with equal detail and explanation.
Where possible, include Bash shell script examples for common tasks, especially for querying or manipulating resources.
Clarify in each section that Azure CLI commands work on all platforms, and PowerShell Core is available cross-platform if relevant.
Review tab ordering and ensure CLI is the default/first tab in tabbed code blocks.

Create Pull Request

Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.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 provides a comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias. Windows-specific terminology and tools (e.g., certificate store names like 'My', NTLM authentication, references to Windows Defender Firewall, and default paths like 'd:\svcfab') are prevalent. Windows concepts (such as certificate store handling and account types) are mentioned before or instead of Linux equivalents. Some settings and guidance reference Windows-only behaviors or tools, and Linux-specific guidance is minimal or absent. While many settings are cross-platform, Linux users may need to infer or adapt instructions, as Linux-specific examples, paths, and terminology are often missing.

Recommendations

Add explicit Linux equivalents for settings that reference Windows concepts (e.g., certificate stores, account types, NTLM authentication).
Provide Linux-specific examples, paths, and terminology alongside Windows references.
Clarify which settings are platform-specific and which are cross-platform, ideally with a table or annotation.
Include guidance for Linux users where Windows tools or behaviors are mentioned (e.g., how to handle certificates, firewall configuration, or file paths on Linux).
Ensure Linux settings (such as '/usr/bin/' for external executables, '/var/lib/waagent' for certificates) are given equal prominence and explanation.

Create Pull Request

Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files on Azure Service Fabric. However, PowerShell examples are presented first and in greater detail, which may suggest a Windows-first bias. The CLI examples are included and are cross-platform, but there is no explicit mention of Linux/macOS compatibility or guidance for those environments. The documentation does not exclusively use Windows tools, but the ordering and emphasis favor Windows users.

Recommendations

Explicitly state that sfctl is cross-platform and suitable for Linux/macOS users.
Consider presenting CLI examples before PowerShell, or at least side-by-side, to avoid Windows-first ordering.
Add brief instructions or links for installing sfctl on Linux/macOS.
Clarify any limitations or differences for Linux/macOS users, if applicable.

Create Pull Request

Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ minor_windows_tools

Summary

The documentation generally presents Azure Service Fabric as a cross-platform solution, explicitly mentioning both Windows and Linux support throughout. However, there is a subtle 'Windows-first' ordering in some sections, and Windows tools (Visual Studio, PowerShell) are mentioned before Linux equivalents. Linux tooling is referenced, but with less detail and after Windows tools.

Recommendations

When listing supported platforms or environments, alternate the order (e.g., 'Linux and Windows Server') or mention both together to avoid implicit prioritization.
Provide equal detail for Linux development tools (e.g., mention Bash, VS Code, or other common Linux workflows alongside Visual Studio/PowerShell).
Ensure that links to getting started guides for both Windows and Linux are equally prominent.
Where possible, include examples or references for both .NET and Java SDKs in parallel, not just in separate sections.

Create Pull Request

Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are listed before any Linux/macOS alternatives, and PowerShell is specifically highlighted without mention of cross-platform CLI options. There are no Linux-specific examples or references to Linux tooling for application upgrades.

Recommendations

Add examples or references for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), especially for Linux/macOS users.
Ensure that Linux/macOS-friendly upgrade tutorials are linked alongside Visual Studio and PowerShell guides.
Explicitly state platform requirements for any tool or process mentioned, and provide alternatives when available.
Consider including sample code or instructions for running Service Fabric workloads on Linux, if applicable.

Create Pull Request

Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides both Azure CLI and Azure PowerShell examples for all operations (attach, detach, move VMs), but consistently lists PowerShell examples after CLI and portal instructions. PowerShell is a Windows-centric tool, and while Azure CLI is cross-platform, there are no explicit Linux/macOS shell examples (e.g., Bash, zsh). The documentation does not reference Windows-only tools or patterns, but the presence of PowerShell examples and lack of Linux-specific shell instructions may create minor friction for Linux/macOS users.

Recommendations

Clarify that Azure CLI commands are fully supported on Linux/macOS and Windows.
Consider adding explicit Bash/zsh shell examples for Azure CLI usage, especially for scripting scenarios.
Mention that PowerShell Core (pwsh) is cross-platform, but traditional Azure PowerShell is Windows-centric.
Ensure parity in troubleshooting and limitations sections by referencing both CLI and PowerShell where appropriate.
If possible, provide links to Azure CLI installation guides for Linux/macOS users.

Create Pull Request

Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides configuration examples for rolling upgrades with MaxSurge using Azure Portal, Azure CLI, PowerShell, and ARM Template. While the CLI and ARM Template examples are cross-platform, the PowerShell example is Windows-centric, and PowerShell is presented as a distinct tab alongside CLI. The CLI example is shown before PowerShell, which is positive, but the presence of PowerShell-specific instructions may create friction for Linux/macOS users who do not have access to PowerShell by default.

Recommendations

Clarify that PowerShell instructions are optional and primarily for Windows users.
Add Bash shell scripting examples for Azure CLI where relevant.
Explicitly note that Azure CLI works on Linux/macOS and provide links to installation guides for those platforms.
Consider adding a note in the PowerShell section about cross-platform PowerShell Core availability, if applicable.
Ensure parity in example complexity and completeness between CLI and PowerShell sections.

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 extension installation. However, in several sections, PowerShell/Windows examples are presented before or with more detail than Linux equivalents. The PowerShell tab for installing the extension uses 'ApplicationHealthWindows' as the default type, while the CLI example uses 'ApplicationHealthLinux'. The PowerShell HTTP server example is more elaborate than the Bash/Python one. The documentation sometimes refers to Windows-specific extension types first and provides more PowerShell-centric guidance, which may create friction for Linux users.

Recommendations

Ensure Linux and Windows examples are presented with equal prominence, and alternate which is shown first in tabbed sections.
When referencing extension types, clarify when to use 'ApplicationHealthLinux' vs. 'ApplicationHealthWindows' and provide explicit Linux-focused examples in PowerShell sections if relevant.
Balance the detail and complexity of Linux and Windows sample scripts (e.g., the Bash/Python HTTP server could include more robust error handling or logging, similar to the PowerShell example).
Where possible, provide cross-platform (e.g., Python-only) examples that work on both Linux and Windows.
In troubleshooting and verification sections, ensure Linux commands (e.g., Bash/curl) are as detailed as PowerShell equivalents.

Create Pull Request

Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as 'Create zone spanning or zonal scale sets'), PowerShell is listed before ARM templates and REST API. There are no Linux-specific shell examples (e.g., Bash), and the CLI examples are generic but do not reference Linux-specific considerations. The documentation does not mention Windows tools exclusively, but the ordering and prominence of PowerShell may create a slight Windows bias.

Recommendations

Ensure that Azure CLI examples are clearly labeled as cross-platform and, where relevant, provide Bash shell examples for Linux/macOS users.
Consider listing Azure CLI examples before PowerShell in sections to emphasize cross-platform parity.
Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
Add notes or links for Linux/macOS users regarding SSH key generation and authentication differences, if relevant.
Review the ordering of example sections to avoid implicit Windows prioritization.

Create Pull Request

Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.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 (bash-style) and Azure PowerShell examples for creating instant access snapshots, but the PowerShell example is given equal prominence and appears immediately after the CLI example. There is no explicit Linux/macOS bias, but the ordering and inclusion of PowerShell (a Windows-centric tool) may suggest a slight Windows-first approach. No Windows-specific tools or patterns are mentioned exclusively, and all instructions are cross-platform except PowerShell, which is primarily used on Windows. No Linux-specific examples (e.g., Bash scripting, references to Linux tools) are provided, but the CLI example is applicable to Linux/macOS users.

Recommendations

Consider explicitly stating that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
Add a brief note clarifying that PowerShell is primarily for Windows users, while Azure CLI works on Linux/macOS.
If possible, provide a Bash shell script example for Linux users, or highlight CLI usage as the default for non-Windows environments.
Ensure that CLI examples are always shown first and labeled as the recommended approach for Linux/macOS.

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

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation is focused on the Azure Key Vault VM Extension for Linux and provides both Azure CLI and Azure PowerShell deployment instructions. However, PowerShell examples and troubleshooting commands are presented before their Azure CLI equivalents, and PowerShell-specific warnings are highlighted. There is a slight bias toward PowerShell/Windows tooling, even though the extension is Linux-specific. All technical instructions and examples are applicable to Linux, but the ordering and emphasis may create friction for Linux/macOS users who typically use Azure CLI or shell scripting.

Recommendations

Present Azure CLI examples before PowerShell examples, as CLI is more commonly used on Linux/macOS.
Add explicit notes clarifying that Azure PowerShell is cross-platform, but Azure CLI is the default for Linux users.
Highlight Linux-native troubleshooting tools (e.g., journalctl, systemctl) for extension diagnostics in addition to Azure CLI/PowerShell.
Remove or minimize PowerShell-specific warnings unless they are critical for Linux users.
Ensure all example commands use Linux shell syntax (e.g., avoid PowerShell backticks in CLI examples).

Create Pull Request

Virtual Machines Deprovision or generalize a VM before creating an image ...docs/blob/main/articles/virtual-machines/generalize.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation covers both Linux and Windows VM generalization, but the Windows section presents Windows-specific tools (Sysprep, PowerShell) and registry commands before their Linux equivalents. Windows examples (PowerShell, Command Prompt) are shown in detail, and the Windows section includes more granular prerequisites and troubleshooting steps. However, Linux instructions are present and clearly separated, with links to distro-specific guides.

Recommendations

Ensure Linux and Windows sections are equally detailed, including troubleshooting and prerequisites for Linux (e.g., common waagent issues, disk encryption, supported distros).
Present Linux and Windows sections in parallel structure, possibly with a summary table comparing steps for both OSes.
Add Linux-specific command-line examples for marking a VM as generalized (currently only Azure CLI is shown, but PowerShell is used for Windows).
Include links to Linux troubleshooting or waagent logs, similar to the Windows Panther directory step.
Consider alternating the order of Linux and Windows sections or presenting them side-by-side to avoid 'windows_first' bias.

Create Pull Request

Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Linux and Windows guidance, but there is a subtle Windows bias. In the PowerShell example, Windows is shown first and Linux is mentioned as an alternative. The CLI example shows Linux first, but the PowerShell section is more detailed and prominent, which may favor Windows users. There are no missing Linux examples, and both platforms are covered, but Windows terminology and tools (Sysprep, PowerShell) are referenced before their Linux equivalents in some sections.

Recommendations

Ensure that Linux and Windows examples are presented with equal prominence and detail in all sections.
In PowerShell sections, show Linux examples first or alternate the order to avoid Windows-first bias.
Where Windows-specific tools (e.g., Sysprep) are mentioned, ensure Linux equivalents (e.g., waagent -deprovision) are referenced with equal clarity.
Consider adding Bash or shell script examples for Linux users alongside PowerShell examples.
Review the language to avoid defaulting to Windows terminology when both platforms are supported.

Create Pull Request

Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation covers both Windows and Linux VM images, but there is a mild bias toward Windows in example ordering and tooling. PowerShell examples are provided alongside Azure CLI, but PowerShell is a Windows-centric tool. In several places, Windows-specific links and terminology are mentioned before Linux equivalents. However, Linux support is clearly stated and Linux-specific tools (waagent) are referenced where relevant.

Recommendations

Ensure Linux and Windows examples are presented in parallel, with equal prominence.
Where PowerShell is used, always provide a CLI or Bash equivalent for Linux/macOS users.
When linking to upload instructions or specialized image guides, list Linux and Windows links together or alternate their order.
Explicitly mention cross-platform support for Azure CLI and encourage its use for Linux/macOS users.
Review FAQ and example sections to ensure Linux scenarios are not secondary to Windows.

Create Pull Request