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

1235 issues found
Showing 126-150 of 1235 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-18 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 explicit links to PowerShell cmdlets for cluster operations. While Azure CLI and ARM/Bicep are mentioned in a summary table, PowerShell is emphasized in the narrative and examples, and no Linux/macOS-specific command-line examples (such as Azure CLI usage) are provided. The ordering and focus on PowerShell may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples alongside PowerShell examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • In the 'Best practices' section, mention Azure CLI as an equally valid cross-platform option, not just in the summary table.
  • Provide sample commands for both Azure CLI and PowerShell where possible.
  • Clarify that PowerShell is available cross-platform, but highlight CLI as the default for Linux/macOS users.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides management guidance for Service Fabric Explorer blocking operations, primarily referencing Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for resource operations. While the Azure CLI (az resource) is mentioned once for deleting applications, most examples and instructions favor PowerShell, which is more commonly used on Windows. There is no explicit mention of Linux/macOS alternatives or parity for all operations.
Recommendations
  • Include Azure CLI equivalents for all PowerShell cmdlet examples, especially for provisioning and deleting resources.
  • Clarify that Az PowerShell cmdlets can be used cross-platform (on Linux/macOS via PowerShell Core), or provide links to relevant documentation.
  • Present examples for both PowerShell and Azure CLI side-by-side to ensure Linux/macOS users can follow along easily.
  • Explicitly mention that ARM templates and Azure CLI are fully supported on Linux/macOS.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page contains evidence of Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd') and recommends using Visual Studio for XML schema validation, which are Windows-centric tools. Additionally, the only mention of command-line tooling is the ServiceFabric PowerShell module, with no equivalent Linux CLI or cross-platform example provided. Windows terminology and tools are mentioned before any Linux alternatives (if any), and there are no explicit Linux/macOS examples or guidance.
Recommendations
  • Add instructions for validating manifest XML schema using cross-platform tools (e.g., VS Code, xmllint, or other editors) and provide Linux/macOS file path equivalents if applicable.
  • Include examples or references for using Service Fabric CLI (sfctl) or Azure CLI for service management, alongside PowerShell examples.
  • Mention cross-platform editors and tooling for authoring manifests, not just Visual Studio.
  • Clarify any platform-specific requirements for Service Fabric manifest authoring and deployment, and provide parity guidance for Linux clusters.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows-specific terminology and tools (e.g., certificate store paths like LocalMachine\My, references to Win32 CryptoAPI, Windows event logs, and error codes) are mentioned first or exclusively. Troubleshooting sections focus on Windows logs and tools, with only brief or parenthetical references to Linux equivalents. Linux certificate storage paths are mentioned, but Windows patterns dominate the narrative and examples.
Recommendations
  • Provide Linux-specific examples and troubleshooting steps alongside Windows instructions, including log locations, certificate store paths, and relevant commands.
  • Explicitly document Linux/macOS certificate store equivalents and how Service Fabric interacts with them.
  • Include Linux/macOS error codes and remediation steps where applicable.
  • Balance Windows and Linux terminology in examples and explanations.
  • Reference cross-platform tools (e.g., OpenSSL) for certificate management and validation.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no mention of Azure CLI or Bash scripting, which are cross-platform and preferred by Linux/macOS users. Additionally, PowerShell examples are presented alongside Portal and ARM template methods, but never alternatives for Linux users. There is no explicit mention that PowerShell Core (pwsh) is supported, nor are Linux-specific instructions or tools referenced.
Recommendations
  • Add Azure CLI examples for all tasks currently demonstrated with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Clarify whether PowerShell Core (pwsh) is supported for Linux/macOS, or recommend Azure CLI for those platforms.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or ARM templates.
  • Consider showing Azure CLI examples before or alongside PowerShell to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-02-18 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 the Infrastructure Service, and references Service Fabric Explorer (a Windows-centric tool) without mentioning Linux/macOS alternatives. No Linux-specific commands or cross-platform CLI options are given, and Windows tooling is presented as the default.
Recommendations
  • Add equivalent Linux/macOS command-line examples using Azure CLI or Service Fabric CLI (sfctl), if available.
  • Clarify whether the PowerShell command is required, or if cross-platform alternatives exist.
  • Mention if Service Fabric Explorer is accessible from non-Windows platforms, or provide alternative tools for Linux/macOS users.
  • Explicitly state platform requirements for any commands or tools referenced.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, exclusively references Windows container images (mcr.microsoft.com/windows/nanoserver:1809), and uses Windows-specific paths and commands (e.g., C:\WorkspaceOnHost, cmd, echo, type, ping). There is no mention of Linux containers, Linux paths, or Linux command equivalents, and the example is explicitly described as a Windows container scenario.
Recommendations
  • Add a parallel example using Linux containers (e.g., mcr.microsoft.com/linux/base image), with Linux file paths and shell commands (e.g., /workspace/log.txt, bash, echo, cat, ping).
  • Clarify whether Initializer CodePackages are supported for Linux container workloads in Service Fabric, and if so, provide guidance and examples.
  • If Initializer CodePackages are Windows-only, explicitly state this limitation at the top of the article to set expectations for Linux/macOS users.
  • Include links or references to Linux container documentation if available.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers both Windows and Linux clusters, but there are several areas where Windows tools and patterns are mentioned first or exclusively. Windows-specific tools (e.g., Event Log/Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some examples/tutorials focus on .NET/Windows. Linux-specific guidance is present but often secondary, and Linux configuration details are sometimes referenced via links rather than described inline. Some features (like EventStore APIs) are Windows-only, but this is clearly stated. Overall, Linux users can complete the tasks, but may experience friction due to Windows-centric ordering and tool emphasis.
Recommendations
  • Ensure Linux examples and tools are given equal prominence and described inline, not just linked.
  • Where Windows tools (e.g., Event Viewer, Diagnostics Agent) are mentioned, immediately follow with Linux equivalents (e.g., Syslog, Linux platform diagnostics) and provide comparable detail.
  • Add Linux-focused tutorials and examples alongside .NET/Windows ones, especially for application monitoring and logging.
  • Clarify when features are Windows-only, and provide alternative approaches for Linux clusters.
  • Review ordering so Linux and Windows guidance is presented in parallel, not Windows-first.
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-18 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 cross-platform context but exhibits some Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned with more detail and examples, while Linux equivalents are either briefly referenced or omitted. Some sections (e.g., disk encryption, running services under accounts) provide Windows instructions or links first, with Linux options marked as TODO or not explained. PowerShell is referenced for disk encryption, but Linux CLI or disk encryption methods are not provided.
Recommendations
  • Add explicit Linux examples for disk encryption (e.g., using Azure CLI and dm-crypt/LUKS).
  • Provide parity in instructions for running services under Linux user accounts, including relevant manifest configuration and security policies.
  • Ensure that Linux container certificate access is described with equal detail as Windows.
  • Where Windows tools (e.g., BitLocker, PowerShell) are mentioned, add corresponding Linux tools and commands.
  • Remove or resolve TODOs regarding Linux disk encryption and provide links to Linux documentation.
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-18 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. There are no Linux/macOS equivalents or examples provided for application upgrades, and the recommended serialization approach (Data Contract serializer) is tied to .NET Framework/WCF, which is historically Windows-focused. The page assumes C# usage and does not mention cross-platform alternatives or workflows for Linux/macOS users.
Recommendations
  • Add examples or links for upgrading Service Fabric applications using cross-platform tools (e.g., Azure CLI, REST API, or .NET Core CLI).
  • Include guidance for Linux/macOS users, such as using VS Code or other IDEs instead of Visual Studio.
  • Clarify whether the Data Contract serializer recommendation applies to .NET Core/.NET 5+ workloads, which are cross-platform, or only .NET Framework (Windows-only).
  • Provide parity in upgrade instructions for Linux/macOS environments, including PowerShell Core (pwsh) or Bash examples.
  • Explicitly state any Windows-only limitations if applicable, so Linux/macOS users are aware.
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-18 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 for Service Fabric application upgrade demonstrates a notable Windows bias. PowerShell is used exclusively in code examples, and only Windows-specific tools (e.g., PowerShell cmdlets like Get-ServiceFabricApplication and Start-ServiceFabricApplicationUpgrade) are mentioned. There are no equivalent examples or guidance for Linux/macOS users (e.g., using sfctl or REST APIs). Additionally, the documentation references Windows-specific components such as http.sys and error messages from the Windows HTTP Server API, without clarifying platform differences or providing Linux alternatives.
Recommendations
  • Add equivalent Linux/macOS examples using sfctl (Service Fabric CLI) or REST API calls alongside PowerShell examples.
  • Clearly state when a feature or limitation is Windows-specific (e.g., http.sys certificate handling).
  • In sections referencing PowerShell, provide a note or link to Linux/macOS instructions.
  • Reorder or parallelize examples so that Linux/macOS and Windows users are equally supported.
  • Include a table or section summarizing tool equivalence (PowerShell vs sfctl vs REST API) for common upgrade operations.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on PowerShell and the Microsoft.ServiceFabric.Powershell.Http module for all command-line examples. There are no examples using cross-platform tools (such as Azure CLI, curl, or bash scripting), nor is there any mention of Linux/macOS equivalents for connecting to clusters or triggering backups. All REST API examples are shown via PowerShell, and there is no guidance for Linux users on how to perform these tasks.
Recommendations
  • Add equivalent examples using cross-platform tools such as curl or HTTPie for REST API calls.
  • Provide instructions for connecting to Service Fabric clusters from Linux/macOS environments, including certificate handling.
  • Mention and demonstrate the use of Azure CLI (if supported) for relevant operations.
  • Clearly state if certain features or modules are only available on Windows, and provide alternatives or workarounds for Linux/macOS users.
  • Include bash or shell script examples alongside PowerShell where possible.
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-18 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 move cost in Service Fabric, but does not include equivalent Linux/bash/CLI examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before C# code samples, reinforcing Windows-first bias. There is no mention of Azure CLI, REST API, or bash alternatives for Linux users.
Recommendations
  • Add Azure CLI examples for configuring and updating move cost, if supported.
  • Include bash or shell script equivalents for PowerShell commands.
  • Mention REST API options for cross-platform usage.
  • Present Windows and Linux/macOS examples side-by-side or alternate their order.
  • Clarify if certain operations are only possible via PowerShell, and provide guidance for Linux users if so.
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-18 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 tooling (e.g., Remove-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) alongside .NET APIs and REST operations. PowerShell examples and cmdlets are consistently mentioned before or alongside REST and .NET methods, but Linux-native CLI equivalents (such as sfctl or Azure CLI) are not directly referenced in the main lifecycle steps. The only explicit cross-platform mention is an include link to 'service-fabric-sfctl.md', but no concrete sfctl or Azure CLI commands are shown in the main sections. This creates friction for Linux/macOS users, who must infer or search for their own equivalents.
Recommendations
  • Add explicit examples and references for sfctl and Azure CLI commands in each lifecycle phase (deploy, upgrade, remove, etc.), not just as a sidebar link.
  • Where PowerShell cmdlets are listed, also list the equivalent sfctl or Azure CLI command immediately alongside.
  • Clarify which tools are cross-platform and which are Windows-only, especially for operators and administrators.
  • Consider providing sample command sequences for Linux/macOS users in critical sections.
  • Review and update the 'Preserving disk space' and 'Cleaning up files' sections to include sfctl/Azure CLI equivalents where possible.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page gives prominence to Windows-centric tools (PowerShell and Visual Studio) by listing them first and providing detailed parameter tables for these tools before mentioning cross-platform alternatives like SFCTL. The PowerShell and Visual Studio sections are more extensive and appear before SFCTL, which is the primary CLI for Linux/macOS users. Examples and parameter descriptions are often PowerShell-focused, and Linux-specific guidance is less detailed.
Recommendations
  • Reorder the tools section to list SFCTL (Service Fabric CLI) alongside PowerShell and Visual Studio, or even before them, to emphasize cross-platform parity.
  • Expand the SFCTL section to include more detailed parameter tables and usage examples, matching the depth provided for PowerShell and Visual Studio.
  • Add explicit Linux/macOS examples and clarify which tools are recommended for each platform.
  • Where PowerShell-specific syntax is shown (e.g., hashtables), provide equivalent SFCTL JSON examples.
  • Ensure that all parameters described for PowerShell/Visual Studio are also mapped to SFCTL, noting any differences or limitations.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page primarily describes Service Fabric's periodic backup configuration in a platform-neutral manner, but the only example for on-premises backup storage is a Windows-style file share path (\\StorageServer\BackupStore) and references Integrated Windows Authentication. There are no examples or guidance for Linux-based file shares (such as NFS or SMB mounts on Linux), nor is there mention of Linux authentication patterns. This creates friction for Linux users of standalone Service Fabric clusters who wish to use on-premises backup storage.
Recommendations
  • Add examples and guidance for configuring file share backup storage using Linux-based file shares (e.g., NFS or SMB mounts) and authentication methods suitable for Linux environments.
  • Clarify whether Linux-based Service Fabric clusters can use file share backup storage, and if so, provide sample paths and credential usage for Linux.
  • If file share backup storage is Windows-only, explicitly state this limitation to avoid confusion for Linux users.
  • Consider including both Windows and Linux file share path formats and authentication options in the documentation.
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-18 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 cluster upgrade operations. Windows-specific registry keys and template properties are discussed for disabling Windows Update, with no equivalent Linux guidance. Upgrade instructions rely on PowerShell, omitting Linux shell or cross-platform alternatives. Windows configuration details are presented before Linux, and some sections lack Linux parity.
Recommendations
  • Add Linux shell (bash) examples for cluster upgrade operations, especially where PowerShell is currently the only option.
  • Include guidance for disabling automatic updates on Linux VMs (e.g., using cloud-init or OS-specific package managers).
  • Provide parity in upgrade instructions for Linux clusters, including references to .deb package handling and relevant commands.
  • Where possible, present cross-platform tools (Azure CLI, REST API) before platform-specific tools like PowerShell.
  • Clarify when instructions are Windows-only and provide links or notes to Linux equivalents.
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-18 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 manual scaling instructions and references Windows-centric tooling (e.g., PowerShell cmdlets like Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux/bash/CLI examples. Windows/PowerShell instructions are presented first and exclusively in critical workflow sections, creating friction for Linux users. While Service Fabric supports Linux clusters, the guidance for scaling and node management is heavily Windows-biased.
Recommendations
  • Provide equivalent Azure CLI or bash examples for scaling operations, including node disablement/removal and cluster management.
  • Clearly indicate which PowerShell commands are available on Linux (via PowerShell Core) or provide alternative commands/scripts for Linux environments.
  • Add Linux-specific guidance for manual scaling, including references to Service Fabric CLI (sfctl) or REST API usage.
  • Ensure that both Windows and Linux cluster creation and management workflows are equally documented and accessible.
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-18 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 several Windows/PowerShell-centric examples and references, such as mentioning PowerShell APIs and Azure DevOps classic PowerShell tasks, and links to Windows-specific ARM templates. Windows terminology and tools are often referenced before Linux equivalents, and some examples (like network port usage and tooling) are Windows-focused. Linux is mentioned, but Linux-specific examples and guidance are less detailed or appear after Windows content.
Recommendations
  • Provide Linux CLI examples alongside PowerShell examples, especially for cluster management and networking tasks.
  • Ensure Linux-specific ARM templates and sample links are included and referenced equally.
  • Clarify when port ranges or tooling differ for Linux clusters (e.g., ephemeral ports, client APIs).
  • Add more Linux-focused guidance for Azure DevOps and application networking scenarios.
  • Balance the order of Windows and Linux references in sections and tables.
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-18 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 Service Fabric Application Groups. PowerShell is a Windows-centric tool, and no Linux/macOS CLI equivalents (such as Azure CLI, Bash, or REST API examples) are provided. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools.
Recommendations
  • Add Azure CLI examples for all operations shown (application creation, updating, querying load, removing capacity).
  • Include REST API sample calls for relevant actions, as these are platform-agnostic.
  • Mention if PowerShell cmdlets are available cross-platform (PowerShell Core), or clarify Windows-only limitations.
  • Consider Bash scripting examples if relevant.
  • Explicitly state any limitations or differences for Linux clusters, if applicable.
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-18 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 examples for key security tasks, such as encrypting secrets, but Windows examples (PowerShell) are presented first and in greater detail. Windows-specific tools and features like Windows Defender and Azure Desired State Configuration (DSC) are discussed without Linux equivalents or alternatives. Some sections, such as Windows security baselines and Windows Defender, are inherently Windows-focused, but the overall structure tends to prioritize Windows tools and patterns before Linux ones.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate their order to avoid Windows-first bias.
  • Where Windows-specific tools (e.g., Windows Defender, DSC) are mentioned, provide Linux alternatives or explicitly state their absence and recommend best practices for Linux clusters.
  • Expand Linux-specific guidance where possible, such as referencing common Linux security baselines or antimalware solutions.
  • Ensure parity in detail and clarity between Windows and Linux instructions, especially for certificate and secret management.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides some Windows-centric details, such as using Windows-style file paths (e.g., 'D:\\SvcFab') in JSON configuration examples and referencing RDP port changes and admin username/password updates, which are Windows-specific tasks. There is a lack of explicit Linux/macOS examples or guidance, especially for connecting to nodes or configuring Service Fabric on Linux. The extension configuration does mention 'ServiceFabricLinuxNode', but practical Linux usage is not demonstrated.
Recommendations
  • Add explicit Linux/macOS examples for connecting to cluster nodes (e.g., SSH instructions alongside RDP).
  • Include Linux-style file paths (e.g., '/var/svcfab') in configuration examples or clarify that the path should match the OS.
  • Provide guidance or links for updating Linux admin credentials and port ranges, not just Windows/RDP.
  • Ensure parity in 'Next steps' by referencing Linux-relevant scripts or documentation where available.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using Application Manifest, C# APIs, and PowerShell. All CLI examples are PowerShell-based, with no Linux shell (bash/CLI) equivalents. PowerShell is presented as the only scripting option, and there is no mention of Linux-native tools or commands. While Service Fabric supports Linux containers, the documentation does not show how Linux users can perform these tasks, creating friction for non-Windows users.
Recommendations
  • Add equivalent bash/CLI examples for Linux users alongside PowerShell examples.
  • Clarify which steps or commands are cross-platform and which are Windows-only.
  • Mention and link to Linux-specific tooling or documentation where relevant.
  • Explicitly state PowerShell requirements and provide alternatives for Linux environments.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json) deployments. However, code samples for service creation and updates are given in C# and PowerShell only, with PowerShell shown as the only CLI example. The XML configuration is labeled as <WindowsServer>, and PowerShell is a Windows-centric tool, which may create friction for Linux/macOS users who typically use Bash or other CLI tools. There are no explicit Linux-specific examples or references to Linux-native tools or shell commands.
Recommendations
  • Add CLI examples using Azure CLI or Bash scripts for service creation and updates, especially for standalone and Linux clusters.
  • Clarify whether ClusterManifest.xml applies only to Windows or if there is an equivalent for Linux clusters.
  • Include references to Linux/macOS environments where applicable, and note any differences in configuration or tooling.
  • If PowerShell is required for certain operations, mention alternatives or limitations for Linux/macOS users.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying health reports, but does not include equivalent examples for Linux/macOS users (e.g., using sfctl or REST API). The only command-line example is Windows/PowerShell-specific, and there is no mention of Linux tooling or cross-platform alternatives for cluster management tasks.
Recommendations
  • Add equivalent examples using sfctl (the cross-platform Service Fabric CLI) for querying partition health and other management tasks.
  • Mention REST API options for health queries, which are platform-agnostic.
  • Where PowerShell examples are given, provide Linux/macOS alternatives alongside or immediately after.
  • Clarify in the text that management tasks can be performed from any OS using sfctl or REST APIs, not just via PowerShell.
GitHub Create Pull Request
← Previous Page 6 of 50 Next →