Service Fabric

407
Total Pages
336
Linux-Friendly Pages
71
Pages with Bias
17.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1305 issues found
Showing 251-275 of 1305 flagged pages
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-02-17 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 GUI tool primarily used on Windows). No Linux/bash alternatives or cross-platform CLI examples are given, even though Service Fabric clusters can be managed from Linux/macOS environments.
Recommendations
  • Add equivalent bash/CLI examples for bypassing Infrastructure Service, using Azure CLI or Service Fabric CLI (sfctl) where possible.
  • Clarify whether the PowerShell command is required or if cross-platform tools can be used.
  • Mention Service Fabric Explorer alternatives or accessibility from non-Windows platforms.
  • Provide guidance for Linux/macOS users on connecting to Service Fabric clusters and performing similar operations.
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-02-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples and links primarily for Azure PowerShell, mentioning it before Azure CLI and other cross-platform tools. PowerShell is highlighted in the best practices section and in the recommended APIs for managing Service Fabric managed clusters, which may create friction for Linux/macOS users who prefer Azure CLI or other cross-platform utilities.
Recommendations
  • Provide Azure CLI examples alongside Azure PowerShell examples for key operations such as deleting NodeTypes, restarting, and reimaging scale sets.
  • Mention Azure CLI before or equally with Azure PowerShell in the best practices section to reinforce cross-platform parity.
  • Clarify that Azure PowerShell is available cross-platform, but also highlight CLI usage for Linux/macOS users.
  • Add explicit Linux/macOS guidance or callouts where relevant, especially in sections referencing PowerShell-heavy workflows.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a general overview of Service Fabric application security, but several sections exhibit Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned before or without Linux equivalents. Examples and guidance for Linux clusters are sparse or missing, especially regarding disk encryption and user account management. The use of Windows terminology and tools (e.g., NetworkService, BitLocker, gMSA) is more prominent, and Linux-specific instructions are often absent or relegated to TODO comments.
Recommendations
  • Add explicit Linux examples for disk encryption (e.g., using Azure Disk Encryption with Linux, or dm-crypt/LUKS).
  • Provide guidance on managing user accounts and security principals for Linux clusters, including relevant Linux account types and group management.
  • Include Linux-specific instructions or references for certificate management and service startup scripts.
  • Ensure parity in examples and mention Linux options alongside Windows options, rather than only in passing or as TODOs.
  • Clarify which features are Windows-only and provide alternative approaches for Linux where possible.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily discusses data serialization in the context of Azure Service Fabric, which is cross-platform. However, in the 'Next steps' section, application upgrade tutorials are listed for Visual Studio and PowerShell, both of which are Windows-centric tools. PowerShell is mentioned as a primary upgrade method, and there is no mention of Linux/macOS CLI or tooling alternatives, nor are Linux-specific examples provided. The serialization discussion is focused on C# and .NET, but this is appropriate for Service Fabric workloads.
Recommendations
  • Add links or references to application upgrade tutorials using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and commonly used on Linux/macOS.
  • Clarify that PowerShell and Visual Studio are Windows-centric, and provide Linux/macOS alternatives where possible.
  • Consider including examples or guidance for upgrading Service Fabric applications on Linux clusters, if supported.
  • Ensure parity in 'Next steps' by listing Linux/macOS-friendly tools alongside Windows tools.
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-17 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 demonstrates a notable Windows bias. PowerShell is the only command-line example shown, and Windows-specific tools (e.g., http.sys) are referenced without Linux equivalents. There are no CLI or SDK examples for Linux/macOS users, and the guidance assumes familiarity with Windows administration patterns. The 'Next steps' section also prioritizes Visual Studio and PowerShell, both Windows-centric tools.
Recommendations
  • Add equivalent Azure CLI or Service Fabric CLI (sfctl) examples for Linux/macOS users alongside PowerShell commands.
  • When referencing Windows-specific components (like http.sys), clarify their Linux/macOS equivalents or note platform limitations.
  • Include guidance or links for performing upgrades using cross-platform tools (e.g., sfctl, REST API, or SDKs) where possible.
  • In 'Next steps', add tutorials for Linux/macOS workflows (e.g., using sfctl or Azure CLI) and not just Visual Studio/PowerShell.
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-02-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page predominantly references Az PowerShell cmdlets for managing Service Fabric resources, with no explicit mention of Linux/macOS equivalents or CLI usage except for a brief reference to 'az resource' for deleting applications. PowerShell examples and terminology are presented first and most frequently, which may create friction for Linux/macOS users who typically use Azure CLI or bash scripts.
Recommendations
  • Add Azure CLI examples for all operations (e.g., creating, deleting, scaling applications/services) alongside PowerShell cmdlets.
  • Clarify that Az PowerShell cmdlets can be used cross-platform, or specify any limitations for Linux/macOS users.
  • Where possible, provide ARM template examples and instructions for both PowerShell and CLI users.
  • Ensure that references to PowerShell are balanced with CLI/bash alternatives, especially in 'Best practices' sections.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation covers monitoring for both Windows and Linux Service Fabric clusters, but there is a tendency to mention Windows-specific tools and workflows first (e.g., EventStore APIs, Event Log/Event Viewer, Diagnostics Agent). Some examples and tutorials focus primarily on .NET applications and Windows clusters, with Linux equivalents referenced but not always given equal detail or prominence. Linux-specific guidance is sometimes relegated to links or brief mentions, rather than integrated examples or walkthroughs.
Recommendations
  • Ensure Linux monitoring examples and workflows are presented alongside Windows equivalents, not just referenced via links.
  • Provide explicit Linux sample code, configuration snippets, and screenshots where Windows examples are shown (e.g., for EventStore, logging setup, agent configuration).
  • Clarify when a feature is Windows-only (such as EventStore APIs) and offer alternative Linux approaches or tools.
  • Balance tutorial coverage so that Linux users can follow step-by-step guides without needing to search for additional resources.
  • Highlight cross-platform tools and practices (such as Service Fabric Explorer, FabricObserver, and Azure Monitor agent) with equal detail for both OSes.
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-17 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 guidance for validating manifest XML schemas. It exclusively recommends opening the schema file in Visual Studio using a Windows file path, with no mention of Linux/macOS alternatives or cross-platform editors. Additionally, the only tool-specific advice is Windows-centric and appears early in the article.
Recommendations
  • Provide instructions for validating manifest XML schemas using cross-platform tools such as VS Code, xmllint, or other XML editors available on Linux/macOS.
  • Include Linux/macOS file paths for the schema file, or clarify where the schema can be found on those platforms.
  • When referencing editors like Visual Studio, also mention cross-platform alternatives (e.g., VS Code with XML extensions, JetBrains Rider, or command-line tools).
  • Ensure that any tool-specific guidance is either cross-platform or that platform-specific instructions are grouped together and clearly labeled.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-17 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 extensive PowerShell examples and references to PowerShell cmdlets for Service Fabric application upgrades, with no mention of Linux/macOS equivalents or cross-platform CLI tools. Windows/PowerShell tools are presented as the default method for performing upgrades, and there is no guidance for Linux users on how to accomplish these tasks using Azure CLI, REST API, or Service Fabric CLI (sfctl).
Recommendations
  • Add equivalent examples using Azure CLI (az), Service Fabric CLI (sfctl), or REST API for application upgrade operations.
  • Clearly indicate which PowerShell cmdlets are available cross-platform (if any), and provide guidance for Linux/macOS users.
  • Include links or references to Linux/macOS documentation or tools for Service Fabric management.
  • Where possible, show both Windows and Linux/macOS workflows side by side, or note any limitations for non-Windows users.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation references PowerShell cmdlets and administrative APIs as the primary means for managing Service Fabric clusters, without mentioning Linux equivalents such as Azure CLI or REST APIs. This may give the impression that management is Windows/PowerShell-centric, potentially confusing or excluding Linux/macOS users.
Recommendations
  • Explicitly mention cross-platform management options such as Azure CLI and REST APIs alongside PowerShell.
  • Provide examples or references for managing Service Fabric clusters from Linux/macOS environments.
  • Clarify that PowerShell Core is available cross-platform, if relevant, or link to documentation on using PowerShell on Linux/macOS.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation for on-demand backup in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all code examples using PowerShell cmdlets or PowerShell-based REST calls. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or Azure CLI. The prerequisite section also assumes PowerShell usage and module installation, which is Windows-centric. This creates friction for Linux/macOS users who may need to perform the same tasks.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, demonstrating how to trigger backups and track progress from Linux/macOS.
  • Mention Azure CLI commands if available for backup operations.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all platforms or provide alternatives for Linux/macOS.
  • Reorganize examples to show cross-platform parity, e.g., REST API via curl first, then PowerShell.
  • Add a note about platform support and limitations, explicitly stating if certain operations are Windows-only.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides numerous PowerShell-based examples and instructions for scaling Service Fabric clusters, but does not offer equivalent Linux CLI (bash, Azure CLI) examples or guidance. Windows/PowerShell commands are presented first and exclusively, creating friction for Linux users who may not have access to PowerShell or Windows tools.
Recommendations
  • Add equivalent Azure CLI or bash examples for scaling operations, such as disabling/removing nodes and managing cluster resources.
  • Clearly indicate which commands are Windows-specific and provide alternative instructions for Linux environments.
  • Where PowerShell is referenced, link to Linux-compatible tools or scripts (e.g., Azure CLI, REST API calls).
  • Ensure that manual and programmatic scaling instructions are platform-neutral or include both Windows and Linux options.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses PowerShell and the Microsoft.ServiceFabric.Powershell.Http module for all CLI and scripting examples, with no mention of Linux/macOS-compatible tools or equivalent Bash/cURL examples. All REST API calls are demonstrated via PowerShell, and prerequisites focus on installing Windows-specific PowerShell modules. There is no guidance for Linux/macOS users on how to perform these tasks, despite Service Fabric supporting cross-platform clusters.
Recommendations
  • Add Bash/cURL examples for REST API calls, showing how to authenticate and trigger restores from Linux/macOS.
  • Mention any cross-platform CLI tools (such as Azure CLI or Service Fabric CLI) that can be used for backup/restore operations.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST API calls can be made directly from any platform.
  • Provide guidance on certificate handling and authentication for Linux/macOS users.
  • Include a note about platform compatibility and limitations, if any exist.
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-17 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 Resource Manager templates, 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, and Windows configuration is discussed before Linux. While Linux is referenced and linked, some critical upgrade tasks are only shown for Windows/PowerShell.
Recommendations
  • Add Linux-specific examples for cluster upgrades, including equivalent commands (e.g., using Bash or Azure CLI) for manual upgrades.
  • When referencing registry keys or Windows Update settings, clarify Linux equivalents or explicitly state if not applicable.
  • Provide parity in scripting examples (e.g., show Bash or Python for deployment and upgrade tasks alongside PowerShell).
  • Ensure that Linux configuration options (such as disabling automatic updates) are discussed with equal prominence.
  • Where possible, avoid presenting Windows tools or patterns before Linux equivalents unless Windows is the default or only supported platform.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation presents Service Fabric cluster settings in a platform-neutral way, but several parameters and descriptions reference Windows-specific concepts (e.g., certificate store names like 'MY', store locations like 'LocalMachine', NTLM authentication, and Windows Defender Firewall). Windows terminology and tools are often mentioned first or exclusively, with Linux equivalents less visible or absent. Some settings are described as 'Windows only' without Linux alternatives or guidance. There are also references to Windows-specific behaviors (e.g., 'Windows Fabric Replicator', 'Windows Fabric waits', 'Windows only' log settings) and links to Windows-focused documentation. Linux-specific settings are present but less prominent.
Recommendations
  • For parameters referencing Windows concepts (e.g., certificate stores, NTLM, firewall), add explicit Linux equivalents or clarify Linux behavior.
  • Where settings are 'Windows only', provide Linux alternatives or note Linux limitations.
  • Ensure Linux-specific settings (e.g., X509Folder, LinuxExternalExecutablePath, EnforceLinuxMinTlsVersion) are as prominent as Windows settings.
  • Add examples or guidance for Linux cluster configuration and upgrade, not just Windows/Windows Server.
  • Review descriptions and guidance to avoid defaulting to Windows terminology when Linux is supported.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets, but several sections and examples show Windows bias. The JSON snippet for the Service Fabric Virtual Machine extension uses a Windows-style file path (e.g., 'D:\\SvcFab'), and the 'Next steps' section links to PowerShell scripts for RDP port changes and admin credential updates, which are Windows-specific tasks. There are no Linux/macOS equivalents or guidance for Linux node types, and Windows tools (RDP, PowerShell) are referenced without alternatives.
Recommendations
  • Provide Linux-specific examples, such as using Linux file paths (e.g., '/var/svcfab') in the 'dataPath' property.
  • Include guidance or links for connecting to Linux nodes (e.g., SSH instructions) alongside RDP/PowerShell examples.
  • Add parity for admin credential changes and port management on Linux VMs, referencing Bash scripts or Azure CLI.
  • Clarify when a step is Windows-only and offer Linux alternatives where possible.
  • Mention Linux node types and their configuration explicitly, not just as an option in the property table.
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-17 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 primarily in C# and PowerShell for configuring Service Fabric placement policies. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or REST API) are provided. All operational examples for service creation and placement policy configuration use PowerShell, which may create friction for users managing Service Fabric clusters from Linux or macOS environments.
Recommendations
  • Add Azure CLI examples for service creation and placement policy configuration, if supported.
  • Include REST API examples for configuring placement policies, to provide platform-neutral guidance.
  • Clarify whether PowerShell is required or if cross-platform tools can be used, and link to relevant documentation.
  • Consider mentioning or linking to any available Linux/macOS management tools for Service Fabric clusters.
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-17 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 provided. The PowerShell examples are given alongside C# code, but there is no mention of cross-platform alternatives or guidance for Linux/macOS users. This creates friction for users operating Service Fabric clusters on non-Windows environments.
Recommendations
  • Add Azure CLI examples for service creation and metric management, which are cross-platform.
  • Mention and link to any REST API documentation for Service Fabric metric management, as REST APIs are platform-neutral.
  • If PowerShell is required, clarify whether PowerShell Core (pwsh) is supported on Linux/macOS, and provide guidance for installation and usage.
  • Explicitly state any limitations or differences for Linux/macOS users, and provide alternative workflows if available.
  • Consider including bash script examples or references to Service Fabric SDK tools available for Linux.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Scanned: 2026-02-17 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 PowerShell examples for configuring MoveCost in Service Fabric, but does not include equivalent Linux CLI (e.g., Bash, Azure CLI) or cross-platform scripting examples. PowerShell is presented before C# in each example section, and no Linux-specific guidance or parity is offered for command-line operations. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add Azure CLI or Bash examples for creating and updating Service Fabric services with MoveCost, where possible.
  • Clarify whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), and provide instructions if so.
  • Consider including REST API or SDK examples for cross-platform usage.
  • Explicitly mention any limitations or alternatives for Linux/macOS users in relevant sections.
  • Present cross-platform examples (e.g., Azure CLI, REST API) before or alongside PowerShell to avoid Windows-first bias.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides example code for configuring auto scaling policies using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. The documentation does not mention or demonstrate Linux-native tools or workflows for managing Service Fabric auto scaling policies, nor does it clarify whether PowerShell Core (cross-platform) is supported. Additionally, PowerShell examples are presented alongside C# and manifest examples, but no Linux-first or cross-platform CLI guidance is given.
Recommendations
  • Add Bash or Azure CLI examples for configuring auto scaling policies, especially for Linux-based Service Fabric clusters.
  • Clarify whether PowerShell Core can be used on Linux/macOS, or specify if the PowerShell examples are Windows-only.
  • Mention and demonstrate Linux-native management workflows (e.g., REST API, Azure CLI, Bash scripts) for Service Fabric auto scaling.
  • Consider providing a table or section comparing Windows and Linux management options for Service Fabric auto scaling.
  • Explicitly state any limitations or differences for Linux clusters in auto scaling configuration and management.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying cluster health, with no equivalent Linux/macOS CLI or REST API example. The example is shown using Windows paths and PowerShell syntax, and no mention is made of cross-platform tools or commands. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform management via CLI and REST, but only Windows tooling is demonstrated.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Mention REST API options for health queries, which are platform-agnostic.
  • When showing PowerShell examples, also provide the analogous sfctl or REST command, and note any differences.
  • Avoid using Windows paths (e.g., C:\Users\User) unless necessary; use generic or platform-neutral prompts.
  • Clarify that management operations can be performed from Linux/macOS, and link to relevant cross-platform tooling documentation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
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 node tags and configuring services, but does not include equivalent CLI or scripting 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 other platforms.
Recommendations
  • Add examples using Azure CLI or Bash scripts for managing node tags and configuring services, as these are cross-platform and widely used by Linux/macOS users.
  • Include REST API examples for all operations (adding/removing node tags, creating/updating services with tags), as REST is platform-agnostic.
  • Explicitly state whether the PowerShell cmdlets are available cross-platform (e.g., via PowerShell Core), and if not, provide alternatives.
  • Consider reordering or parallelizing examples so that non-Windows methods are shown alongside PowerShell and C#.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page covers security for Azure Service Fabric clusters, including both Azure-hosted and standalone Windows clusters. However, it consistently references Windows Server clusters and Windows-specific security mechanisms (such as Kerberos, group Managed Service Accounts, Windows certificate services, MakeCert.exe), and links only to Windows-specific guides for standalone clusters. There are no explicit examples or guidance for standalone Linux clusters, nor are Linux certificate creation tools or Linux security patterns mentioned. The concept section briefly states that Linux clusters follow the same security principles, but practical Linux guidance is missing.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
  • Include Linux-specific certificate creation tools (e.g., OpenSSL) and examples alongside Windows tools like MakeCert.exe.
  • Provide parity in example links and walkthroughs for Linux clusters, not just Windows clusters.
  • Clarify which security features are available or recommended for Linux clusters, and note any limitations.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Provide REST API examples for health reporting and querying, as these are platform-agnostic.
  • Mention PowerShell as one option, but ensure Linux/macOS users are equally supported with their native tools.
  • Clarify in the example section that PowerShell is Windows-specific, and link to Linux/macOS alternatives.
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-02-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page on upgrading an Azure Service Fabric standalone cluster demonstrates a Windows bias. It references Windows-specific upgrade guides and tools (e.g., Patch Orchestration Application for Windows), and links to documentation with 'windows-server' in the URL. There are no examples or guidance for Linux-based standalone clusters, nor is it clarified whether Linux is supported or not.
Recommendations
  • Clarify early in the documentation whether standalone clusters are Windows-only or if Linux is supported.
  • If Linux-based standalone clusters are supported, provide equivalent upgrade instructions, configuration examples, and patching guidance for Linux.
  • If only Windows is supported, explicitly state this to avoid confusion for Linux/macOS users.
  • Where possible, use platform-neutral language and examples, or provide parallel sections for both Windows and Linux.
GitHub Create Pull Request
← Previous Page 11 of 53 Next →