Service Fabric

407
Total Pages
335
Linux-Friendly Pages
72
Pages with Bias
17.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

2475 issues found
Showing 276-300 of 2475 flagged pages
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides detailed PowerShell examples for reporting health in Service Fabric, including connection and health report commands, but does not offer equivalent Linux/macOS CLI examples (such as Azure CLI or Bash). PowerShell is presented as the primary scripting interface, and Windows-style paths and prompts are used. REST and API methods are mentioned, but scripting and command-line guidance is Windows-centric.
Recommendations
  • Add equivalent examples for Linux/macOS environments using Azure CLI, Bash, or cross-platform tools where possible.
  • Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS and provide examples if so.
  • Mention any limitations or differences for Linux users in Service Fabric health reporting.
  • Reorder sections or add notes to ensure REST and API methods are highlighted as cross-platform options, not secondary to PowerShell.
  • Use neutral prompts and paths in examples (e.g., $ instead of PS C:\>) when possible.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for Replica soft delete in Service Fabric consistently references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links only for PowerShell usage. There is no mention of Linux/macOS equivalents, CLI commands, or cross-platform SDK usage. The documentation assumes familiarity with Windows tooling and does not clarify how Linux users can perform these operations, creating friction for non-Windows users.
Recommendations
  • Add examples for performing replica soft delete and restore operations using cross-platform tools such as Azure CLI, REST API, or .NET Core SDK.
  • Clarify whether the PowerShell APIs are available on Linux/macOS (via PowerShell Core), and provide installation or usage guidance if so.
  • Include explicit instructions or code samples for Linux users, such as using FabricClient APIs in .NET Core or Java.
  • Mention any limitations or differences for Linux clusters, if applicable.
  • Ensure screenshots and command outputs are not exclusively from Windows environments.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example for deploying Service Fabric applications, which is specific to Windows. Windows file paths and store names (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd', 'MY' certificate store) are mentioned first or exclusively, with Linux equivalents only briefly referenced. Linux deployment methods and CLI examples are missing, and Windows-centric terminology appears throughout.
Recommendations
  • Add equivalent Linux deployment examples using Azure CLI or Service Fabric CLI (sfctl), especially for application parameter overrides.
  • Mention Linux file paths and certificate store locations alongside Windows paths, not only in passing.
  • Clarify when PowerShell commands are Windows-only and provide alternative commands for Linux/macOS users.
  • Ensure that Linux-specific configuration nuances (such as certificate handling and endpoint ACLing) are covered in parity with Windows.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is generally cross-platform and describes Service Fabric concepts applicable to both Windows and Linux. However, there is a notable Windows bias in the 'Node' section, which describes nodes as having an auto-start Windows service (FabricHost.exe) and references EXE/DLL files as typical code packages. Windows terminology and tools are mentioned first and more prominently, while Linux equivalents are not explicitly described. The Linux support is acknowledged in container and guest executable sections, but lacks parity in technical detail.
Recommendations
  • In the 'Node' section, clarify how node processes are managed on Linux (e.g., systemd, FabricHost process, etc.), not just Windows services.
  • When describing code packages, mention typical Linux executable formats (e.g., ELF binaries) alongside EXE/DLL.
  • Provide explicit examples or descriptions for Linux clusters where relevant, such as how Service Fabric services are started and managed.
  • Ensure that references to Windows-specific tools or terminology are matched with Linux equivalents, or note differences.
  • Consider alternating the order in which Windows and Linux are mentioned to avoid 'windows_first' bias.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is heavily oriented toward Windows development workflows, specifically Visual Studio. All deployment and configuration examples reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish) and Windows-centric tools. PowerShell is mentioned as the CLI for service creation, with no mention of Linux/macOS alternatives or cross-platform CLI tools. There are no examples or guidance for Linux/macOS users, nor is there any indication of how to use StartupServices.xml outside of Visual Studio or on non-Windows platforms.
Recommendations
  • Add explicit guidance for Linux/macOS users, including whether StartupServices.xml is supported outside Visual Studio and how to manage service configurations using cross-platform tools.
  • Provide examples using Azure CLI or Service Fabric CLI (sfctl) for service deployment and configuration, if supported.
  • Clarify any platform limitations for StartupServices.xml, and if it is Windows-only, state this clearly at the top of the documentation.
  • If possible, include instructions for editing and deploying Service Fabric applications from Linux/macOS environments, or link to relevant documentation.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides explicit PowerShell instructions for using the Fault Analysis Service but does not mention or provide examples for Linux/macOS users (e.g., Bash/CLI equivalents). It references the Service Fabric PowerShell module and SDK, which are Windows-centric tools, without discussing cross-platform alternatives or CLI usage.
Recommendations
  • Add examples or instructions for using the Fault Analysis Service from Linux/macOS environments, such as with Azure CLI, Bash scripts, or REST APIs.
  • Clarify whether the Fault Analysis Service APIs are accessible and supported from non-Windows platforms.
  • If PowerShell Core (cross-platform) is supported, specify this and provide relevant examples.
  • Mention any limitations or requirements for Linux/macOS users explicitly, so expectations are clear.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily references Az PowerShell cmdlets for managing Service Fabric resources, with explicit links to PowerShell modules. While the az CLI is mentioned for deleting applications, PowerShell is presented first and more frequently, potentially creating friction for Linux/macOS users who typically use the az CLI. There are no explicit Linux/macOS examples or references to Bash or shell scripting.
Recommendations
  • Add az CLI examples for all operations (unprovision, create, delete) alongside PowerShell examples.
  • Clarify that az CLI is cross-platform and provide links to relevant az CLI documentation.
  • Consider presenting az CLI examples before PowerShell, or at least in parallel, to improve parity.
  • Explicitly mention that PowerShell is available cross-platform, but az CLI is often preferred on Linux/macOS.
GitHub Create Pull Request
Service Fabric Deploy and upgrade with Azure Resource Manager ...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides PowerShell-only examples for removing Service Fabric application resources and references Remove-AzResource as the main tool, with no equivalent Azure CLI, Bash, or cross-platform REST examples. This creates friction for Linux/macOS users, who may not have access to PowerShell or prefer other tools. The rest of the documentation is largely platform-neutral, focusing on ARM templates, but operational examples are Windows-centric.
Recommendations
  • Add Azure CLI examples for resource removal (e.g., using az resource delete) alongside PowerShell.
  • Explicitly mention and provide REST API examples with curl for cross-platform users.
  • Clarify that PowerShell is not required and that all operations can be performed via Azure CLI or REST.
  • Where PowerShell is shown, provide equivalent Bash/CLI commands or reference them in 'See also'.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides best practice examples using Azure PowerShell modules and references PowerShell-based tools before mentioning cross-platform alternatives like Azure CLI and sfctl. The PowerShell examples are prominent, and the guidance links primarily to PowerShell documentation, which may create friction for Linux/macOS users who prefer CLI or ARM/Bicep templates.
Recommendations
  • Add explicit Azure CLI examples alongside PowerShell examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Ensure CLI and Bicep/ARM template usage is given equal prominence in guidance and links.
  • Clarify which tools are cross-platform and which are Windows-only, especially in the best practices section.
  • Consider providing sample commands for sfctl where relevant, as it is cross-platform.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides PowerShell examples exclusively for command-line operations related to Service Fabric Application Groups, with no mention of Linux-compatible tools or CLI equivalents. All command-line instructions use PowerShell cmdlets, which are native to Windows. There is no guidance for Linux/macOS users on how to perform these tasks, nor are cross-platform alternatives (such as Azure CLI or REST API) referenced.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and supported on Linux/macOS.
  • Mention REST API endpoints or SDK usage for application management where applicable.
  • Clearly state if PowerShell is required and provide guidance for Linux/macOS users (e.g., using PowerShell Core or alternative tools).
  • If certain operations are only possible via PowerShell, explicitly note this limitation and link to relevant cross-platform solutions or workarounds.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page references Windows-specific upgrade paths and tools, such as linking to 'service-fabric-cluster-upgrade-windows-server.md' and 'service-fabric-cluster-config-upgrade-windows-server.md'. The Patch Orchestration Application is described as 'for Windows', with no mention of Linux equivalents or guidance. There are no explicit Linux examples or references, and Windows terminology appears first or exclusively in upgrade instructions.
Recommendations
  • Add links and instructions for upgrading Service Fabric standalone clusters on Linux, if supported.
  • Include Linux-specific configuration and upgrade guidance alongside Windows instructions.
  • Clarify whether Patch Orchestration Application or similar solutions exist for Linux clusters.
  • Ensure parity in examples and references for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples and references PowerShell cmdlets for managing Service Fabric services, but does not include equivalent Linux CLI or cross-platform examples. Windows tooling (PowerShell) is mentioned first and exclusively in command-line sections, creating friction for Linux/macOS users who may use Service Fabric CLI or REST APIs instead.
Recommendations
  • Add Service Fabric CLI (sfctl) examples for Linux/macOS users alongside PowerShell examples.
  • Mention REST API usage more prominently and provide concrete REST examples, not just links.
  • Clarify which management tools are cross-platform and which are Windows-only.
  • Consider including bash or shell script examples where applicable.
  • Explicitly state PowerShell cmdlets are Windows-only and suggest alternatives for Linux/macOS.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
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 and administrative instructions primarily using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or bash examples, nor are Linux-native tools or patterns mentioned. PowerShell commands are referenced before any mention of Linux alternatives, and the administrative actions section exclusively uses Windows tooling. This creates friction for Linux users, who must translate these examples or find their own equivalents.
Recommendations
  • Add equivalent Linux CLI examples (e.g., using sfctl or bash scripts) alongside PowerShell examples.
  • Mention Linux-native tools (such as sfctl) and provide links to their documentation.
  • Where administrative actions are described, explicitly note how to perform them on Linux clusters.
  • Ensure code samples are platform-neutral or provide both Windows and Linux versions.
  • Clarify any platform-specific limitations or differences in the examples.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a comprehensive reference of Service Fabric cluster settings, but exhibits some Windows bias. Windows-specific terminology (e.g., certificate store names like 'MY', 'LocalMachine', NTLM authentication, Windows account types) is used throughout, often without Linux equivalents or clarification. Windows tools and patterns (such as certificate store access, NTLM, and account types) are mentioned exclusively or before Linux alternatives. Some settings (like log file paths, account types, and container network setup) default to Windows values or only reference Windows behaviors. Linux-specific options are present in some places (e.g., 'LinuxExternalExecutablePath', 'X509Folder'), but are not consistently explained or prioritized. There are missing Linux examples or guidance for several settings, especially those referencing Windows stores, accounts, or authentication.
Recommendations
  • For each parameter referencing Windows-specific concepts (e.g., certificate stores, NTLM, account types), add Linux equivalents or clarify Linux behaviors.
  • Where settings differ between Windows and Linux (e.g., default values, paths, authentication), explicitly document both platforms.
  • Provide Linux-specific examples or guidance, especially for certificate management, account configuration, and file paths.
  • Review and update descriptions to avoid Windows terminology as the default; use cross-platform language where possible.
  • Add a summary table or section highlighting platform-specific settings and differences.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI or scripting examples. Windows tools (PowerShell, ApplicationManifest.xml via Visual Studio) are mentioned before Linux alternatives, and Linux-specific limitations are listed but not accompanied by guidance or parity examples. There is no mention of how Linux users can set DNS names via CLI (e.g., Bash, Azure CLI), nor are Linux-friendly workflows or code samples provided.
Recommendations
  • Add Linux CLI examples (e.g., Azure CLI, Bash scripts) for setting DNS names and managing Service Fabric services.
  • Explicitly document how Linux users can perform equivalent tasks, such as configuring DNS names, without relying on PowerShell or Visual Studio.
  • Provide guidance for Linux users on editing ARM templates and deploying services, including any required tools or commands.
  • Clarify Linux limitations with actionable alternatives or workarounds, such as using ARM templates or REST APIs.
  • Ensure code samples and instructions are platform-neutral or provide both Windows and Linux variants.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
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 Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no equivalent Bash, Linux CLI, or cross-platform scripting examples. PowerShell is presented as the only scripting option, which creates friction for Linux/macOS users. Additionally, there is no mention of Linux-specific tools or commands, and PowerShell examples are given after C# but before any Linux alternatives (which are missing).
Recommendations
  • Add Bash or Azure CLI examples for configuring scaling policies, especially for Linux clusters.
  • Clarify which PowerShell commands are cross-platform (if any), or provide alternatives for Linux/macOS users.
  • Explicitly mention any limitations or differences for Linux clusters, and link to relevant Linux documentation.
  • Consider including sample scripts or instructions for Linux users, such as using REST APIs or Azure CLI.
  • Indicate whether PowerShell examples are usable on Linux (PowerShell Core), or if they're Windows-only.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example for deploying Service Fabric applications, which is Windows-centric. References to the Service Fabric SDK schema location use a Windows file path first, and PowerShell is mentioned as the primary deployment tool. Linux-specific deployment tools or examples (such as Azure CLI or Bash) are not provided, though there is a brief mention of Linux certificate store location. The overall guidance and XML manifest examples are platform-neutral, but deployment instructions and tooling are Windows-biased.
Recommendations
  • Add Linux/macOS deployment examples using Azure CLI or Bash scripts alongside PowerShell examples.
  • Mention cross-platform tools (e.g., Azure CLI, REST API) for application deployment.
  • Provide Linux file path equivalents for SDK/schema locations if relevant.
  • Clarify which steps are platform-specific and offer alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits a moderate Windows bias. PowerShell is the only scripting example given for certificate enrollment, and the Key Vault VM extension is discussed primarily in its Windows variant. The documentation references Windows-specific certificate store locations and ACLing patterns, and the Key Vault VM extension is described using its Windows-specific schema and behaviors. There is no mention of Linux equivalents (e.g., Key Vault VM extension for Linux), nor are Bash/CLI examples provided. Windows tools and patterns are presented first and sometimes exclusively, which may create friction for Linux users.
Recommendations
  • Add parallel examples using Azure CLI and/or Bash for certificate enrollment and management, alongside or instead of PowerShell.
  • Explicitly mention and link to the Key Vault VM extension for Linux, and clarify any differences in behavior or configuration.
  • Discuss certificate store locations and ACLing for Linux nodes (e.g., /etc/ssl/certs, permissions, etc.), not just Windows certificate stores.
  • Where Windows-specific behaviors are described (such as S-channel or CERT_RENEWAL_PROP_ID), add notes about Linux equivalents or clarify if not applicable.
  • Provide at least one end-to-end example for a Service Fabric cluster running on Linux nodes, or clarify if certain features are Windows-only.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters. However, there is evidence of Windows bias: Windows certificate store paths and terminology are mentioned first and more frequently, Windows-specific tools and APIs (e.g., Win32 CryptoAPI, CertGetCertificateChain, CAPI2 logging) are referenced without Linux equivalents, and troubleshooting sections focus on Windows event logs and error codes. Linux paths (e.g., /var/lib/sfcerts) are mentioned only in passing, and there are no Linux/macOS-specific troubleshooting steps or tool recommendations.
Recommendations
  • Add Linux/macOS certificate store paths and management instructions alongside Windows examples.
  • Include troubleshooting steps for Linux/macOS nodes, such as relevant log locations and commands (e.g., journalctl, openssl, systemd logs).
  • Reference Linux certificate validation APIs/tools (e.g., OpenSSL, NSS, GnuTLS) where Windows CryptoAPI is discussed.
  • Provide Linux/macOS error codes and remediation steps for common certificate issues.
  • Ensure examples and configuration snippets are platform-neutral or include both Windows and Linux variants.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a tool with Windows-centric usage). No Linux CLI or cross-platform alternatives are mentioned for cluster operations or command execution. While Service Fabric clusters can run on both Windows and Linux, the guidance here assumes Windows tooling and patterns.
Recommendations
  • Add equivalent Linux CLI (e.g., sfctl) or REST API examples for cluster operations, especially for bypassing Infrastructure Service.
  • Clarify whether Service Fabric Explorer is available/cross-platform, or provide alternatives for Linux users.
  • Where PowerShell is used, note if the command can be run from Azure Cloud Shell (which supports Linux), or provide Bash equivalents if possible.
  • Explicitly state if certain operations are Windows-only, or provide guidance for Linux clusters.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides migration guidance for Azure Service Fabric clusters to availability zone support. While most of the content is platform-neutral (focused on Azure Resource Manager templates and JSON), the critical migration steps for clusters with Basic SKU load balancer and IP resources rely exclusively on PowerShell commands and Windows-centric tooling (e.g., Remove-AzureRmVmss, Connect-ServiceFabricCluster). These commands are presented without Linux/bash equivalents, and the PowerShell examples are shown first and only. Additionally, some sample templates referenced are Windows-specific, though at least one Ubuntu sample is linked.
Recommendations
  • Provide equivalent bash/CLI examples for all PowerShell commands, especially for cluster node management and resource cleanup.
  • Explicitly mention whether the PowerShell steps can be performed using Azure CLI or REST API, and link to relevant documentation.
  • Add guidance for Linux/macOS users, including any prerequisites or limitations for Service Fabric cluster management on non-Windows platforms.
  • Ensure sample templates include both Windows and Linux VM options, and clarify which steps are OS-agnostic.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates notable Windows bias. All code examples use Windows containers (nanoserver:1809) and Windows-specific commands (cmd, echo, ping, set, exit). The 'Query deployment status' section only references PowerShell and C# APIs, with no mention of Linux or cross-platform CLI tools. There are no examples or guidance for Linux containers, Linux shell commands, or querying deployment status from Linux/macOS environments.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine) and Linux shell commands (bash, echo, ping, exit).
  • Provide guidance for querying deployment status using Azure CLI or REST APIs, which are cross-platform.
  • Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, include relevant examples.
  • Mention Linux/macOS compatibility and any limitations explicitly.
  • If PowerShell is referenced, also mention Bash or other Linux-native tools where possible.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page is not strictly Windows-only, but it demonstrates Windows bias by repeatedly referencing 'custom windows images' and providing a PowerShell example for role assignment without a Linux CLI equivalent. Windows terminology and examples are presented first and more prominently, even though Service Fabric Managed Clusters can use Linux images. Linux-specific guidance is minimal and secondary.
Recommendations
  • Clarify that custom images can be Windows or Linux, and provide equal coverage for both.
  • Add Azure CLI examples for role assignment (e.g., az role assignment create) alongside PowerShell.
  • Include explicit Linux image ARM template examples and reference Linux image documentation directly.
  • Avoid using 'custom windows images' as the default term; use 'custom images' and specify OS where relevant.
  • Ensure links to Linux image creation and marketplace browsing are as prominent as Windows equivalents.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
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-AzServiceFabricManagedNodeType, Remove-AzServiceFabricManagedNodeType, Set-AzServiceFabricManagedNodeType), which are Windows-centric tools. There are no equivalent examples using Azure CLI, Bash, or cross-platform scripting tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer using Azure CLI. The documentation also refers to drive letters (e.g., S, C, D), which are a Windows disk convention, without clarifying Linux implications.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell (add, remove, scale, configure placement properties, etc.), as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly state if certain operations are only possible with PowerShell, and provide guidance or workarounds for Linux/macOS users (e.g., using Azure Cloud Shell, which supports PowerShell and Bash).
  • Clarify the meaning of drive letters in the context of Linux-based node types, or note if this is only relevant for Windows-based nodes.
  • Consider listing Azure CLI examples before or alongside PowerShell to promote parity.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally covers both Windows and Linux Service Fabric clusters, but there are several areas where Windows tools and patterns are mentioned first or exclusively. Windows-specific tools (e.g., Event Log/Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some examples/tutorials focus on .NET/Windows. Linux-specific guidance is present but often secondary or less detailed. Some features (like EventStore APIs) are Windows-only, but this is clearly stated. Overall, Linux users can complete monitoring tasks, but may encounter friction due to Windows-centric examples and tool references.
Recommendations
  • Ensure Linux monitoring tools and patterns are described with equal prominence and detail as Windows equivalents.
  • Provide Linux-specific examples and tutorials (e.g., instrumenting applications, configuring diagnostics, querying logs) alongside Windows/.NET examples.
  • When referencing Windows tools (e.g., Event Viewer, Diagnostics Agent), immediately mention Linux alternatives (e.g., Syslog, LTTng) and link to relevant Linux documentation.
  • Clarify which features are Windows-only and offer Linux workarounds or alternatives where possible.
  • Add sample code and walkthroughs for Linux clusters using popular languages and frameworks (e.g., Python, Java, Node.js) in addition to .NET.
GitHub Create Pull Request
← Previous Page 12 of 99 Next →