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 1651-1675 of 2475 flagged pages
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-02-10 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 primarily using Azure PowerShell, with PowerShell cmdlets referenced before Azure CLI or other cross-platform tools. While the table lists Azure CLI and ARM/Bicep as ARM-backed utilities, the narrative and example links focus on PowerShell, which is more native to Windows environments. No explicit Linux/macOS examples or command syntax are provided.
Recommendations
  • Include Azure CLI examples alongside PowerShell cmdlets for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Explicitly mention cross-platform compatibility of Azure CLI and Bicep, and provide sample commands for Linux/macOS users.
  • Clarify that PowerShell is available on Linux/macOS, but highlight Azure CLI as the default cross-platform tool.
  • Consider showing Azure CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides monitoring guidance for Azure Service Fabric clusters on both Windows and Linux, but there are several areas where Windows tools and examples are mentioned first or exclusively. Windows-specific tools (e.g., Event Log/Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some features (like EventStore APIs) are noted as Windows-only without Linux alternatives or workarounds. Linux monitoring is addressed, but often as an afterthought or with less detail, and some example/tutorial links are Windows/.NET-focused.
Recommendations
  • Ensure Linux monitoring tools and workflows are described with equal prominence and detail as Windows equivalents.
  • Provide Linux-specific examples and tutorials (e.g., instrumenting applications, configuring monitoring agents, querying logs).
  • Where features are Windows-only, clearly state Linux alternatives or workarounds, or link to relevant Linux documentation.
  • Avoid listing Windows tools or workflows first unless they are more widely used; alternate order or group by OS.
  • Expand references to Linux logging frameworks and monitoring solutions beyond Syslog and LTTng, including practical examples.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation contains a notable Windows bias in its tooling recommendations. It explicitly suggests opening the Service Fabric XSD schema in Visual Studio using a Windows file path ("C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd") for schema validation and IntelliSense. There is no mention of equivalent tools or workflows for Linux or macOS users, nor are cross-platform editors (e.g., VS Code) or alternative validation methods referenced. Additionally, the only explicit tooling guidance is Windows/Visual Studio-centric and appears early in the article.
Recommendations
  • Provide instructions for validating and editing manifest XML files on Linux and macOS, such as using VS Code with XML extensions, or command-line tools like xmllint.
  • Mention the location of the Service Fabric XSD schema on non-Windows installations, or provide a download link.
  • Avoid referencing only Windows file paths; include cross-platform alternatives or clarify when instructions are Windows-specific.
  • If Visual Studio is not available, suggest other editors or IDEs that support XML schema validation on Linux/macOS.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-10 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 numerous PowerShell cmdlet examples (e.g., New-ServiceFabricService, Update-ServiceFabricService, Start-ServiceFabricApplicationUpgrade) without mentioning or demonstrating equivalent CLI or scripting approaches for Linux/macOS users. The PowerShell-centric instructions and examples are presented throughout, with no clear guidance for Linux users on how to perform these tasks using cross-platform tools. This creates friction for non-Windows users, especially since Service Fabric supports Linux clusters and the Azure CLI.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlet usage, especially for service creation, updates, and application upgrades.
  • Explicitly mention which PowerShell cmdlets are available cross-platform (via PowerShell Core) and which are Windows-only.
  • Provide guidance or links for Linux/macOS users on managing Service Fabric applications, including references to REST APIs and Azure CLI.
  • Where possible, show XML/ARM template snippets alongside CLI commands, not just PowerShell.
  • Clarify any limitations or differences for Linux clusters in relevant sections.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and examples before Linux equivalents (SFCTL), and provides more detailed parameter tables and explanations for PowerShell/Visual Studio. SFCTL (the cross-platform CLI) is covered in a separate section with less detail and fewer examples. The 'Next steps' section also lists Windows upgrade tutorials before Linux ones.
Recommendations
  • Present SFCTL (Service Fabric CLI) parameters and examples alongside PowerShell/Visual Studio, rather than in a separate section, to emphasize parity.
  • Provide equally detailed parameter tables and usage examples for SFCTL as for PowerShell.
  • Include sample upgrade commands for SFCTL in the main parameter tables.
  • In the 'Next steps' section, list Linux/SFCTL tutorials before or alongside Windows tutorials.
  • Clarify that SFCTL is the recommended cross-platform tool for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation covers Azure Service Fabric application security in a generally cross-platform manner, but several sections show Windows bias. Windows-specific tools and features (e.g., BitLocker, Active Directory, gMSA) are mentioned without Linux equivalents or with Linux information relegated to brief mentions. Examples and guidance often focus on Windows scenarios first or exclusively, with Linux alternatives missing or referenced only in passing.
Recommendations
  • Provide explicit Linux examples and guidance for securing disks (e.g., using Azure Disk Encryption for Linux, dm-crypt, or other supported methods).
  • When discussing running services under different accounts, clarify Linux options (e.g., running as custom users, systemd service accounts) and provide relevant examples.
  • For certificate management and access in containers, include step-by-step Linux container guidance alongside Windows instructions.
  • Ensure parity in coverage for Linux clusters, including links to Linux-specific documentation where available.
  • When referencing Windows tools (e.g., BitLocker, Active Directory), add notes or links for Linux alternatives or clarify if a feature is Windows-only.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation frequently references PowerShell cmdlets and Windows-specific tools for managing the Service Fabric application lifecycle. While REST API and .NET methods are also mentioned, PowerShell examples and terminology are prominent and often listed first. There is little explicit mention of Linux-native tools or CLI examples (such as sfctl or Azure CLI), and no Linux/macOS-specific guidance is provided. This creates friction for Linux/macOS users, who must infer their workflow or consult external resources.
Recommendations
  • Add explicit examples using sfctl (Service Fabric CLI) and Azure CLI for each lifecycle operation, alongside PowerShell.
  • Where PowerShell cmdlets are referenced, provide equivalent Linux/macOS commands or links to relevant documentation.
  • Clarify which tools are cross-platform and which are Windows-only, to help users select appropriate methods.
  • Consider listing REST API, sfctl, or Azure CLI examples before PowerShell to avoid implicit Windows-first bias.
  • Add a section or note summarizing Linux/macOS support and recommended tooling for Service Fabric operations.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page primarily references Windows-centric tools and patterns, such as Visual Studio and PowerShell, in its 'Next steps' section. These tools are mentioned first and exclusively as upgrade walkthroughs, with no Linux/macOS equivalents or CLI examples provided. The content also assumes C# and .NET serialization, which, while cross-platform in .NET Core/.NET 5+, is historically Windows-centric. There are no explicit Linux/macOS examples or guidance.
Recommendations
  • Add equivalent upgrade walkthroughs using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Mention cross-platform development environments (such as VS Code or JetBrains Rider) alongside Visual Studio.
  • Clarify that PowerShell examples can be run on Linux/macOS using PowerShell Core, or provide Bash examples where possible.
  • Explicitly state .NET Core/.NET 5+ support and cross-platform compatibility for serialization.
  • Provide links or references to Linux/macOS-specific documentation for Service Fabric application upgrades.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides several manual scaling instructions using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux/CLI/Bash examples or alternatives. This creates friction for Linux users, as Service Fabric clusters can be run on both Windows and Linux, and the page is not Windows-specific. The focus on PowerShell and lack of cross-platform command examples is a notable bias.
Recommendations
  • For every PowerShell command or workflow, provide equivalent Azure CLI, Bash, or REST API examples where possible.
  • Explicitly note if certain operations (e.g., Disable-ServiceFabricNode) are only available via PowerShell, and suggest alternative approaches for Linux users.
  • Add links to Linux-specific Service Fabric management documentation or tools.
  • Clarify in each section whether the instructions apply to both Windows and Linux clusters, or if there are differences.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Service Fabric application upgrade demonstrates a notable Windows bias. The only code example provided is in PowerShell, which is a Windows-centric tool. References to Service Fabric PowerShell cmdlets and Windows-specific technologies (such as http.sys and Windows HTTP Server API) are present, with no equivalent Linux or cross-platform CLI examples. The 'Next steps' section prioritizes Visual Studio and PowerShell tutorials, both of which are primarily Windows tools, and does not mention Linux-compatible alternatives (such as Azure CLI, REST API, or Service Fabric CLI). This creates friction for Linux/macOS users, who may not have access to PowerShell or Visual Studio environments.
Recommendations
  • Provide equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include references and links to Linux/macOS-compatible upgrade workflows, such as using Azure CLI or REST API.
  • Clarify which features or commands are Windows-only, and offer guidance for Linux users where possible.
  • Reorder or balance 'Next steps' to include Linux/macOS upgrade tutorials alongside Windows/PowerShell options.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page is generally platform-neutral, focusing on Service Fabric's backup configuration concepts and REST APIs. However, in the 'File share' backup storage section, only Windows-style UNC paths (\\StorageServer\BackupStore) and Windows authentication mechanisms are described, with no mention of Linux-compatible file share paths (e.g., SMB/CIFS mounts) or authentication methods. There are no Linux-specific examples or guidance for configuring file shares, which may create friction for Linux cluster administrators.
Recommendations
  • Add examples for configuring file share backup storage using Linux-compatible paths and authentication (e.g., SMB/CIFS mounts, NFS, or guidance on mounting Azure Files on Linux nodes).
  • Clarify whether file share backup storage is supported on Linux clusters, and if so, provide instructions for Linux environments.
  • If file share backup is Windows-only, explicitly state this limitation to avoid confusion for Linux users.
  • Consider including a table or section comparing storage options and their platform compatibility.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
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 Service Fabric clusters, but PowerShell is featured prominently and exclusively for certain operations (e.g., cluster upgrades). Windows-specific tools and registry keys are mentioned without Linux equivalents. Windows configuration details are presented before Linux, and some upgrade instructions are Windows-centric.
Recommendations
  • Add Linux-specific examples for cluster upgrade operations, such as using Bash or relevant Linux tools.
  • Include instructions for disabling automatic updates on Linux VMs (e.g., using cloud-init or systemd), not just Windows registry keys.
  • Provide parity in PowerShell and Bash/CLI examples throughout, especially for critical operations.
  • When referencing VM configuration, mention both Windows and Linux properties, or clarify if a property is Windows-only.
  • Ensure upgrade instructions (manual and automatic) are available for both OS types, or clearly state if a step is Windows-only.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page covers Azure Service Fabric networking best practices for both Windows and Linux clusters, but exhibits several Windows biases. PowerShell and Windows-specific tools are referenced more frequently and prominently (e.g., Client API endpoint described as 'used by PowerShell', Azure DevOps section focuses on classic PowerShell tasks, and Windows container networking is discussed in detail). Windows examples and terminology often appear before Linux equivalents, and some sample links and templates are Windows-centric. Linux-specific guidance is less detailed, and Linux command-line examples are missing.
Recommendations
  • Provide Linux CLI (az CLI, bash) examples alongside PowerShell examples, especially for cluster management and networking tasks.
  • Clarify when guidance applies to both Windows and Linux, and highlight any Linux-specific differences or requirements.
  • Include links to Linux-focused ARM templates and sample clusters, not just Windows ones.
  • Expand Linux container networking guidance, including best practices and troubleshooting.
  • Balance references to Windows tools (e.g., PowerShell) with Linux equivalents (e.g., bash, az CLI).
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
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 guidance for most security best practices, but there is a notable tendency to present Windows-specific examples, tools, and recommendations first. PowerShell commands and Windows Defender are discussed in detail, while Linux equivalents are sometimes less prominent or referenced after Windows. Some sections (e.g., Windows Defender, Windows security baselines) are Windows-only, but this is appropriate given the context. Overall, Linux users can complete all tasks, but may encounter friction due to Windows-centric ordering and tool emphasis.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, or in parallel sections, rather than after Windows.
  • Where possible, provide Linux-first or equally prominent Linux command examples (e.g., bash/openssl) for certificate generation and secret encryption.
  • Clarify Windows-only sections (e.g., Windows Defender, Windows security baselines) as intentionally platform-specific, and provide links or notes about Linux alternatives (e.g., mention common Linux security tools or practices).
  • Review ordering of examples and guidance to avoid implicit prioritization of Windows.
  • Add explicit notes about parity and limitations for Linux clusters where relevant.
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-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, covering both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows terminology and tools (such as certificate store names like 'My', 'LocalMachine', and references to NTLM authentication) are used throughout, and Windows-specific configuration options (e.g., Windows Update, Windows-only log file settings) are mentioned without always providing Linux equivalents or clarifying platform differences. Some parameters default to Windows patterns or mention Windows-only behaviors first. While Linux is referenced in some settings, parity is inconsistent and Linux-specific guidance is limited.
Recommendations
  • For each configuration parameter, explicitly state platform applicability (Windows, Linux, or both) and provide Linux-specific guidance where relevant.
  • Where Windows certificate store names or NTLM authentication are referenced, clarify Linux equivalents (e.g., file paths, OpenSSL usage) and provide Linux-specific examples.
  • Add Linux-specific configuration examples and highlight any differences in behavior or default values.
  • Ensure that Linux tools, paths, and patterns are mentioned alongside Windows ones, not only as afterthoughts.
  • Where Windows-only features are described (e.g., Windows Update integration), clearly mark them as such and provide alternative approaches for Linux if possible.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides general information about Azure Service Fabric node types and virtual machine scale sets, but several sections and examples show a Windows bias. The JSON snippet uses a Windows-style file path (D:\SvcFab) for 'dataPath', and the 'Next steps' section links to PowerShell scripts for RDP port changes and admin credential updates, which are Windows-centric tasks. There are no explicit Linux/macOS examples, and Windows tools (RDP, PowerShell) are referenced without Linux alternatives.
Recommendations
  • Provide Linux/macOS equivalents for remote connection (e.g., SSH instructions alongside RDP/PowerShell).
  • Show Linux-style file paths (e.g., /var/svcfab) in JSON snippets when 'type' is 'ServiceFabricLinuxNode'.
  • Add links or guidance for managing Linux node types, including credential changes and port updates using Linux tools.
  • Clarify which steps are Windows-only and which apply to Linux, to help users navigate platform-specific instructions.
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-02-10 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 only PowerShell and C# examples for managing Application Groups in Service Fabric, with no mention of Linux-compatible tools or CLI equivalents. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users who may prefer or require cross-platform alternatives such as Azure CLI or REST APIs.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used by Linux/macOS users.
  • Mention REST API endpoints for managing Application Groups, with example requests.
  • Explicitly state if certain features or commands are only available via PowerShell, and provide guidance for Linux users.
  • Consider referencing Service Fabric SDK tools or scripts that work on Linux, if available.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-02-10 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 in C# and PowerShell for configuring Service Fabric placement policies, but does not include equivalent Linux/macOS CLI examples (e.g., Azure CLI or Bash). PowerShell is featured prominently, and Windows-centric tools are referenced before any cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI or Bash script examples for each placement policy configuration, ensuring Linux/macOS users can follow along without PowerShell.
  • Explicitly mention cross-platform alternatives to PowerShell, such as Azure CLI, and link to relevant documentation.
  • Clarify which configuration steps are platform-agnostic and which are Windows-specific, if any.
  • Consider reordering examples so that cross-platform tools are presented alongside or before Windows-specific tools.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows and cross-platform (JSON-based) configuration examples, but there is a notable tendency to present Windows-specific formats (ClusterManifest.xml with <WindowsServer> blocks) and PowerShell commands before or more prominently than Linux equivalents. While standalone (non-Azure) deployments are shown using JSON, the XML examples are explicitly for Windows, and all imperative command-line examples use PowerShell, with no Bash/CLI equivalents. This may create friction for Linux users, especially those running Service Fabric on Linux or in cross-platform environments.
Recommendations
  • Add explicit Linux configuration examples (e.g., show ClusterManifest.xml for Linux clusters, or clarify if the JSON config is the preferred cross-platform method).
  • Provide Azure CLI or Bash script equivalents for all PowerShell command examples, or clarify if only PowerShell is supported for imperative operations.
  • When showing both XML and JSON, clarify which is for Windows and which is for Linux, and ensure Linux-first or parity in ordering.
  • Where possible, use neutral language and ordering (e.g., 'For Windows, use... For Linux, use...'), and avoid implying Windows is the default unless it is for Service Fabric.
  • If certain features are Windows-only, explicitly state this to avoid confusion.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Scanned: 2026-02-10 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 for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash scripts) are given. The PowerShell examples are presented alongside C# code, but there is no mention of cross-platform tools or how Linux users can accomplish the same tasks. The documentation implicitly assumes a Windows environment for scripting and service management.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention Bash scripting or REST API usage for managing Service Fabric services and metrics, providing sample commands or links to relevant documentation.
  • Clarify whether PowerShell Core (pwsh), which is cross-platform, can be used for these commands, and provide guidance for Linux/macOS users.
  • Where possible, provide equivalent instructions for Linux/macOS users, or explicitly state if certain operations are Windows-only.
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-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides code examples for configuring auto scaling in Azure Service Fabric using C#, application manifests, and PowerShell. The PowerShell examples are Windows-specific, and there are no equivalent CLI or shell script examples for Linux/macOS users. The documentation references Windows tools and patterns (e.g., PowerShell cmdlets) without offering Linux alternatives or guidance, despite Service Fabric supporting Linux containers for auto scaling.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for Linux/macOS users where PowerShell is currently used.
  • Explicitly state which management operations (such as updating scaling policies) can be performed from Linux environments, and provide guidance or references for those.
  • Clarify any limitations or differences in auto scaling support between Windows and Linux clusters, especially for resource monitoring and governance.
  • Where possible, provide cross-platform instructions or note when a given example is Windows-only.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-02-10 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 querying Service Fabric partition health, using a Windows-style prompt and cmdlet (Get-ServiceFabricPartitionHealth). No equivalent Linux or cross-platform CLI example is given, and the example is presented early in the page. The rest of the content is platform-neutral, but the only practical example is Windows-centric.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users, e.g., 'sfctl partition health --partition-id <id>'.
  • Mention that PowerShell examples are for Windows and provide alternative commands for other platforms.
  • Consider showing cross-platform examples first, or side-by-side, to improve parity.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing Windows tools and PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without mentioning Linux equivalents or providing Linux-specific guidance. There are no examples or instructions for Linux-based standalone clusters, even though Service Fabric standalone clusters can theoretically run on Linux. This creates friction for Linux users attempting to scale clusters.
Recommendations
  • Add Linux-specific instructions and examples for scaling standalone Service Fabric clusters, including relevant CLI commands and configuration steps.
  • Mention and link to Linux tools or documentation where applicable, such as using sfctl or REST APIs for cluster management.
  • Clarify whether certain steps or tools are Windows-only, and provide alternative guidance for Linux users.
  • Ensure parity in example order and visibility for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
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-native or cross-platform CLI examples (e.g., Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its exclusive use in examples may create friction for Linux/macOS users. Additionally, the documentation references Windows-specific implementation details (e.g., kernel driver for logging) before discussing Linux differences, but does not provide Linux-oriented operational guidance or examples.
Recommendations
  • Add Azure CLI or REST API examples for service scaling operations alongside PowerShell and C#.
  • Explicitly mention Linux/macOS-compatible tools and workflows for managing Service Fabric clusters.
  • Where PowerShell is referenced, clarify if PowerShell Core (cross-platform) is supported, or provide Bash equivalents.
  • Expand the 'Choosing a platform' section with more Linux-specific operational advice and best practices.
  • Consider reordering or balancing the presentation of Windows and Linux details to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page discusses security for Azure Service Fabric clusters, including both Azure-hosted and standalone clusters. However, it consistently provides detailed guidance and links for Windows Server standalone clusters, while omitting equivalent instructions or links for standalone Linux clusters. Windows security (Kerberos) is discussed, but no Linux authentication mechanisms are mentioned. Windows-specific certificate creation tools and services are referenced, with no mention of Linux alternatives. The structure and examples are Windows-first, and Linux standalone scenarios are not covered.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and authentication options.
  • Mention Linux-compatible certificate creation tools (e.g., OpenSSL) alongside Windows tools.
  • Clarify which security features and recommendations apply equally to Linux clusters, and provide Linux-specific instructions where needed.
  • Include examples or references for Linux authentication mechanisms if supported (e.g., integration with Linux user accounts or other identity providers).
  • Ensure parity in documentation structure, so Linux users can easily find relevant information.
GitHub Create Pull Request
← Previous Page 67 of 99 Next →