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 301-325 of 2475 flagged pages
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Scanned: 2026-03-07 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 authoring Service Fabric manifests. It explicitly recommends opening the Service Fabric XSD schema file in Visual Studio using a hardcoded Windows path (C:\Program Files\...), without mentioning Linux or cross-platform alternatives. Additionally, PowerShell is referenced as a way to create services, with no mention of Bash/CLI equivalents. However, the core manifest content and examples are platform-agnostic.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as how to access the XSD schema file on non-Windows installations and which editors (e.g., VS Code, JetBrains Rider) can provide XML schema validation.
  • Mention cross-platform tools (e.g., Azure CLI, Bash scripts) for creating and managing services, not just PowerShell.
  • When referencing file paths, include Linux/macOS paths or clarify if the feature is only available on Windows.
  • Consider including a note about cross-platform development environments and how to work with Service Fabric manifests outside of Visual Studio on Windows.
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-03-07 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 there are several instances where Windows-specific features, tools, and examples are mentioned before or instead of Linux equivalents. For example, running services under Active Directory domain accounts and group managed service accounts (gMSA) are highlighted for Windows standalone clusters, while Linux alternatives are not discussed. Disk encryption references PowerShell and BitLocker (Windows tools), with Linux disk encryption marked as a 'TO DO'. Some examples and terminology (e.g., NetworkService) are Windows-centric, and Linux-specific guidance is limited or absent.
Recommendations
  • Add Linux-specific examples and instructions where Windows features are discussed, such as running services under Linux user accounts or groups.
  • Provide guidance for disk encryption on Linux clusters, including supported tools and procedures.
  • Ensure parity in examples (e.g., manifest snippets) by including both Windows and Linux configurations.
  • Mention Linux alternatives to Windows-specific tools (e.g., BitLocker, PowerShell) and clarify which features are cross-platform.
  • Review terminology to ensure it is not unnecessarily Windows-centric (e.g., NetworkService) and provide Linux equivalents.
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-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page focuses on data serialization during application upgrades in Azure Service Fabric. While the main content is platform-neutral, the 'Next steps' section lists Windows-centric tools (Visual Studio and PowerShell) for upgrade walkthroughs, with no mention of Linux/macOS equivalents or CLI options. PowerShell is highlighted as a primary upgrade method, which may create friction for Linux users.
Recommendations
  • Add links or references to cross-platform upgrade methods, such as Azure CLI or Service Fabric CLI (sfctl), especially for Linux/macOS users.
  • Include examples or tutorials for upgrading applications using CLI tools available on Linux/macOS.
  • Clarify which upgrade methods are Windows-only and provide alternatives for other platforms.
  • Ensure parity in documentation by listing Linux/macOS-compatible tools alongside Windows tools in the 'Next steps' section.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-03-07 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 Service Fabric application upgrade demonstrates a notable Windows bias. All code examples are provided exclusively in PowerShell, with no equivalent CLI or Linux/macOS instructions. Windows-specific tools (PowerShell, http.sys) are referenced without mention of cross-platform alternatives. The 'Next steps' section prioritizes Windows-centric workflows (Visual Studio, PowerShell) and omits Linux-native options, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples alongside PowerShell scripts for application upgrades.
  • Explicitly mention cross-platform tools and workflows where possible, such as using sfctl for Linux/macOS.
  • Clarify which features or steps are Windows-only, and provide Linux/macOS alternatives or workarounds where available.
  • Include links or references to Linux/macOS documentation for Service Fabric application upgrades.
  • Reorder or balance 'Next steps' to include Linux/macOS upgrade tutorials and tools.
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-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 for restoring backup in Azure Service Fabric is heavily biased toward Windows/PowerShell usage. All command-line examples use PowerShell, including REST API calls, and require installation of a Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, curl, or other cross-platform tools. The documentation assumes the reader is using Windows and PowerShell, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using cross-platform tools such as curl or Azure CLI for REST API calls.
  • Document how to authenticate and interact with Service Fabric clusters from Linux/macOS environments.
  • Mention any prerequisites or limitations for Linux/macOS users explicitly, including alternative modules or tools if available.
  • Where possible, provide sample scripts in Bash or generic HTTP request formats alongside PowerShell.
  • Clarify if the Microsoft.ServiceFabric.Powershell.Http module is required only for Windows, and suggest alternatives for other platforms.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.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 page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-specific tooling throughout critical lifecycle operations (deploy, upgrade, remove, cleanup). While REST API and .NET methods are also mentioned, there is a notable absence of Linux-oriented command-line examples (such as Azure CLI or sfctl) and no explicit guidance for Linux/macOS users. The PowerShell cmdlets are presented alongside .NET and REST, but Linux equivalents are not discussed, creating friction for non-Windows users.
Recommendations
  • Add explicit examples and instructions using sfctl (Service Fabric CLI) and Azure CLI for all major lifecycle operations (deploy, upgrade, remove, cleanup).
  • Clarify which tools are cross-platform and which are Windows-only, and provide guidance for Linux/macOS users.
  • Where PowerShell is referenced, include parallel sfctl or Azure CLI commands, or link to relevant Linux/macOS documentation.
  • Consider reordering examples so that cross-platform tools are presented before or alongside Windows-specific tools.
  • Add a section or note summarizing tool parity and platform support for Service Fabric management.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.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 for 'Advanced Application Upgrade Topics' in Azure Service Fabric heavily features PowerShell cmdlets for all operational examples (e.g., creating, updating, upgrading, rolling back applications), with no mention of Linux/macOS equivalents or CLI commands. Windows/PowerShell tools are referenced exclusively, and Windows-centric patterns (such as Visual Studio integration) are mentioned first or solely. There is no guidance for Linux users on how to perform these tasks using cross-platform tools like Azure CLI or REST APIs.
Recommendations
  • Add equivalent examples using Azure CLI (az servicefabric) or REST API for all PowerShell cmdlet operations.
  • Explicitly mention cross-platform tooling and workflows for Linux/macOS users, including how to perform upgrades and configuration changes.
  • Provide links to Linux/macOS-specific documentation or note any limitations for non-Windows environments.
  • Clarify which features or steps are Windows-only, and which are available cross-platform, to reduce confusion.
  • Include sample scripts or commands for Linux shells (bash/zsh) where appropriate.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents PowerShell and Visual Studio (Windows tools) parameters and workflows before those for the cross-platform Service Fabric CLI (sfctl). Most parameter tables and examples are focused on PowerShell and Visual Studio, with Linux/macOS (sfctl) details grouped later. There are no explicit Linux/macOS command-line examples in the main body, and PowerShell/Windows-centric tools are described in more detail and with more context. This ordering and emphasis may create friction for Linux/macOS users.
Recommendations
  • Reorganize the documentation to present cross-platform (sfctl/REST) options before or alongside Windows-specific tools (PowerShell, Visual Studio).
  • Add explicit Linux/macOS command-line examples using sfctl in the main parameter sections, not just in a separate section.
  • Clarify in the introduction that sfctl is the recommended cross-platform tool for Linux/macOS users.
  • Balance the depth of explanation and examples between PowerShell/Visual Studio and sfctl/REST.
  • Where possible, provide parameter tables that show mappings for all tools (PowerShell, Visual Studio, sfctl, REST) side-by-side.
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-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 for on-demand backup in Azure Service Fabric exclusively uses PowerShell for all CLI examples and module instructions, with no mention of Linux/macOS-compatible tools or commands. All REST API examples are shown using PowerShell, and the prerequisite is to install a PowerShell module. There are no Bash, curl, or cross-platform CLI examples, nor is there guidance for Linux/macOS users on how to perform equivalent actions.
Recommendations
  • Add Bash/curl examples for REST API calls, demonstrating how Linux/macOS users can trigger backups and track progress.
  • 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 instructions for connecting to Service Fabric clusters from Linux/macOS, including authentication and certificate handling.
  • Mention cross-platform tools (such as Azure CLI or Service Fabric CLI) if available, and provide equivalent examples.
  • Explicitly state platform requirements for PowerShell-based steps, and offer alternatives where possible.
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-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides several manual scaling instructions using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning or providing equivalent CLI commands for Linux/macOS users. There are no Bash, Azure CLI, or cross-platform alternatives shown for these critical operations, which may create friction for non-Windows users.
Recommendations
  • For every PowerShell example, provide equivalent Azure CLI or REST API commands that can be run on Linux/macOS.
  • Explicitly mention cross-platform tools and workflows where possible, or link to documentation for Linux/macOS users.
  • Clarify whether the PowerShell commands are required (i.e., if no cross-platform alternative exists), and if so, provide guidance for Linux users (e.g., using Azure Cloud Shell, which supports PowerShell).
  • Add Bash or Azure CLI examples for common operations like disabling nodes, scaling in/out, and cleaning up node state.
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-03-07 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 provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and is the only scripting language shown for cluster upgrades. Windows-specific registry and VM configuration details are included without Linux equivalents. The upgrade process shows only PowerShell commands, with no Linux shell or cross-platform alternatives. Some configuration snippets and guidance are Windows-focused, and Linux parity is not always maintained.
Recommendations
  • Provide equivalent Bash or Linux shell commands for all PowerShell examples, especially for cluster upgrades.
  • Include Linux-specific guidance for disabling automatic updates and managing upgrades, or clarify if not required on Linux.
  • When mentioning Windows registry or VM configuration, add a note or section for Linux users, or explicitly state if the step is Windows-only.
  • Present cross-platform tools (like Azure CLI) first, or in parallel with PowerShell, to avoid a Windows-first impression.
  • Ensure all critical workflows (deployment, upgrade, configuration) have Linux examples or clear statements about platform differences.
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-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 some Windows-centric examples and references, such as using Windows-style file paths (e.g., 'D:\\SvcFab') in the Service Fabric extension snippet and referencing RDP and PowerShell scripts in the 'Next steps' section. There is no explicit Linux example for the dataPath or for connecting to Linux nodes, and Linux tools or SSH are not mentioned, which may cause friction for Linux users.
Recommendations
  • Provide Linux-specific examples, such as using a Linux-style dataPath (e.g., '/var/lib/servicefabric') in the extension snippet.
  • Include guidance or links for connecting to Linux nodes (e.g., SSH instructions) alongside RDP/PowerShell references.
  • Add parity in the 'Next steps' section by including Linux/SSH-related scripts or documentation for common management tasks.
  • Clarify when instructions or examples are Windows-specific, and offer Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally platform-neutral, focusing on Azure Service Fabric backup configuration. However, the 'File share' backup storage section exclusively describes Windows-style file shares (UNC paths, Integrated Windows Authentication), with no mention of Linux-compatible alternatives (e.g., SMB/CIFS mounts on Linux, NFS, or Azure Files usage from Linux). Additionally, Windows authentication patterns are described first and in detail, while Linux scenarios are not addressed.
Recommendations
  • Add guidance for configuring file share backup storage from Linux nodes, including supported protocols (e.g., SMB/CIFS, NFS, Azure Files) and authentication methods.
  • Clarify whether Linux Service Fabric clusters can use file share backup storage, and if so, provide Linux-specific examples (e.g., mounting Azure Files via SMB from Linux, using Linux credentials).
  • If file share backup is Windows-only, explicitly state this limitation to avoid confusion for Linux users.
  • Consider including parity examples for Azure Blob storage usage from Linux clusters, if there are any platform-specific considerations.
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-03-07 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 provides both Windows and Linux guidance for Service Fabric networking, but there are several areas where Windows tools (e.g., PowerShell, Windows-specific port ranges, Windows container guidance) are mentioned first or exclusively. PowerShell is referenced as the primary client API example, and some sample ARM templates and links are Windows-centric. Linux equivalents are sometimes mentioned, but not always with equal detail or prominence.
Recommendations
  • Provide Linux CLI examples alongside PowerShell, especially for client API access and cluster management.
  • Include Linux-focused ARM template samples and links, not just Windows ones.
  • Clarify when port ranges or networking rules are Windows-only and provide Linux-specific guidance where applicable.
  • Ensure reverse proxy and container networking guidance is equally detailed for Linux workloads.
  • Where Windows tools are mentioned (e.g., netsh), offer Linux equivalents (e.g., ss, iptables, etc.).
  • Balance the order of presentation so Linux and Windows are treated equally (e.g., do not always mention Windows first).
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-03-07 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 key security tasks, but Windows-specific tools (PowerShell, Windows Defender, DSC) are often mentioned first or exclusively. Windows examples (especially PowerShell commands) precede Linux equivalents in some sections, and Windows Defender configuration is covered in detail while Linux antimalware is only referenced generically. Some sections (e.g., Windows security baselines, Windows Defender) are Windows-only, but this is appropriate given their nature.
Recommendations
  • Where possible, present Windows and Linux examples side-by-side or alternate which comes first.
  • Expand Linux-specific guidance for antimalware and baseline configuration, referencing common Linux tools (e.g., ClamAV, auditd, CIS benchmarks) and how to apply them to Service Fabric clusters.
  • Clarify when sections are Windows-only and provide links or notes for Linux alternatives if available.
  • Ensure parity in detail and clarity for Linux commands and workflows, matching the depth of Windows instructions.
  • Add explicit notes when a feature or tool is Windows-only, to avoid confusion for Linux users.
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-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 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 Bash scripts) are provided. PowerShell examples are consistently shown alongside C# code, with no mention of cross-platform alternatives or Linux-native tooling. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer platform-agnostic approaches.
Recommendations
  • Add Azure CLI examples for each placement policy, as Azure CLI is cross-platform and widely used.
  • Mention whether PowerShell examples are supported on Linux/macOS (via PowerShell Core), and clarify any limitations.
  • Provide Bash or shell script equivalents where possible, or reference relevant REST API calls.
  • Explicitly state if certain configuration steps require Windows, or if they can be performed from any OS.
  • Consider reordering examples so that platform-neutral options (e.g., Azure CLI, REST API) are presented before PowerShell.
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-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows-specific (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json) configuration examples. However, Windows/PowerShell examples are consistently presented first and are more detailed, with Windows terminology (e.g., <WindowsServer> element) appearing before Linux equivalents. PowerShell is the only CLI example shown, with no Linux shell or CLI parity. There is no explicit mention of Linux-specific node configuration or Linux command-line usage, though Service Fabric does support Linux clusters.
Recommendations
  • Provide Linux-specific configuration examples, such as referencing <Linux> infrastructure elements in ClusterManifest.xml.
  • Add Linux CLI examples (e.g., Bash, Azure CLI) alongside PowerShell for service creation and updates.
  • Clarify that both Windows and Linux clusters are supported and highlight any differences in configuration or terminology.
  • Ensure that JSON-based configuration examples are clearly marked as cross-platform.
  • Consider alternating the order of Windows and Linux examples, or grouping them together for parity.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.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 querying Service Fabric partition health, using Windows-style paths and commands (e.g., 'PS C:\Users\User > Get-ServiceFabricPartitionHealth'). There are no equivalent Linux/macOS CLI examples or references to cross-platform tools. The PowerShell example is presented as the only way to interact with the cluster, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Mention that PowerShell is one option, but that sfctl or REST APIs can be used from any OS.
  • Provide Linux/macOS command-line examples alongside Windows/PowerShell examples.
  • Clarify any OS-specific limitations if certain commands/tools are Windows-only.
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-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 for Azure Service Fabric dynamic node tags provides command-line examples exclusively using PowerShell, which is a Windows-centric tool. There are no Linux shell (bash/CLI) examples or references to Linux-native tools for managing node tags, despite Service Fabric supporting Linux nodes and clusters. The documentation also does not mention cross-platform alternatives or clarify whether the PowerShell commands are available on Linux (via PowerShell Core), nor does it provide REST API or CLI examples for Linux/macOS users.
Recommendations
  • Add equivalent bash/CLI examples for managing node tags on Linux clusters.
  • Include Azure CLI or REST API examples for cross-platform usage.
  • Clarify whether PowerShell commands are supported on Linux (via PowerShell Core), and if so, provide guidance.
  • Mention any limitations or differences for Linux users, if applicable.
  • Ensure examples are balanced and not Windows-first unless the feature is Windows-only.
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-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 page for scaling Azure Service Fabric standalone clusters shows notable Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without mentioning Linux equivalents or cross-platform tools. The linked 'scale a standalone cluster' guide is Windows Server-specific, and there are no examples or guidance for Linux-based standalone clusters, even though Service Fabric can be deployed on Linux. This creates friction for Linux users seeking parity.
Recommendations
  • Add examples and instructions for scaling standalone clusters deployed on Linux, including relevant CLI commands or scripts.
  • Mention cross-platform tools (such as sfctl or REST APIs) alongside PowerShell cmdlets.
  • Clarify which steps are Windows-specific and provide Linux alternatives where possible.
  • Update links and references to include Linux documentation if available.
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-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily discusses security scenarios for Azure Service Fabric clusters, but consistently presents Windows-specific guidance and links before Linux equivalents. Standalone cluster security is only described for Windows Server, with no mention of Linux standalone clusters or their security setup. Certificate creation recommendations and tooling are Windows-centric, and there are no Linux-specific examples or instructions for standalone clusters.
Recommendations
  • Add explicit guidance and links for securing standalone Service Fabric clusters running on Linux, including certificate and authentication setup.
  • Provide Linux-specific examples and instructions alongside Windows examples, especially for certificate management, cluster configuration, and client authentication.
  • Clarify which security scenarios and features are supported on Linux clusters, and note any differences or limitations.
  • Mention Linux-compatible certificate creation tools (e.g., OpenSSL) and provide sample commands.
  • Ensure parity in recommendations and best practices for both Windows and Linux environments.
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-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 for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API) are provided. Additionally, PowerShell examples are presented before any mention of cross-platform alternatives, and there is no guidance for Linux users on how to perform these tasks. This creates friction for Linux/macOS users deploying or managing Service Fabric clusters.
Recommendations
  • Add Azure CLI examples for service creation and metric management, which are cross-platform.
  • Include REST API sample calls for metric configuration and load reporting.
  • Explicitly mention cross-platform tools and workflows, and clarify which features are available on Linux Service Fabric clusters.
  • If PowerShell is required for certain tasks, note any Linux alternatives or limitations.
  • Consider providing Bash scripts or instructions for Linux environments where applicable.
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-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides PowerShell and C# examples for configuring Service Fabric MoveCost, but does not include equivalent Linux/CLI (e.g., Azure CLI, Bash) examples. PowerShell is Windows-centric, and the absence of Linux-native command-line examples may hinder Linux/macOS users.
Recommendations
  • Add Azure CLI or Bash examples for creating and updating Service Fabric services with MoveCost, if supported.
  • Clarify if PowerShell commands are cross-platform (e.g., Azure PowerShell Core) or Windows-only.
  • Mention any Linux/macOS limitations or provide guidance for users on those platforms.
  • Consider including REST API examples, which are platform-agnostic.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
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 configuring service sensitivity and maximum load, but does not mention or provide equivalent Linux/macOS CLI examples (such as Azure CLI or REST API). PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users. The C# API is also shown, but this is platform-neutral. No explicit Windows-only features are discussed, so Linux parity is expected.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, if supported.
  • Clarify whether PowerShell commands can be run cross-platform (e.g., via PowerShell Core), or if they are Windows-only.
  • Mention any Linux/macOS tools or workflows for Service Fabric administration, or link to relevant guides.
  • If PowerShell is the only supported scripting interface, explicitly state this limitation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI or Bash equivalents. Application packaging is described via Visual Studio, a Windows-centric tool, and directory paths use Windows-style notation. There are no Linux/macOS-specific instructions or examples, and Windows tools are referenced before any cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
  • Include instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, zip utilities) instead of only Visual Studio.
  • Use platform-neutral directory paths or provide both Windows and Linux/macOS path examples.
  • Mention that PowerShell examples are for Windows and provide Bash/Azure CLI alternatives for Linux/macOS users.
  • Clarify that Visual Studio is optional and suggest cross-platform editors or build tools.
GitHub Create Pull Request
← Previous Page 13 of 99 Next →