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 876-900 of 2475 flagged pages
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily discusses deploying custom Windows images on Azure Service Fabric Managed Clusters, with Windows terminology and PowerShell examples appearing before Linux equivalents. While Linux custom image creation is referenced, Windows is emphasized throughout, and the only CLI example is PowerShell.
Recommendations
  • Provide explicit Linux/macOS examples for role assignment (e.g., using Azure CLI or Bash).
  • Clarify that custom images can be Linux-based and show ARM template examples for Linux node types.
  • Balance the order of Windows and Linux references, ensuring Linux is not secondary.
  • Add links to Linux-specific documentation for Service Fabric Managed Clusters where relevant.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits Windows bias in several areas. PowerShell is the only scripting example provided for certificate enrollment, and references to Key Vault VM extension are explicitly for Windows. The documentation frequently refers to Windows-specific behaviors (such as certificate linking and S-channel), and the Key Vault VM extension is described in a Windows-centric manner. Linux equivalents (such as the Key Vault VM extension for Linux or CLI/bash scripting) are not mentioned, and Windows tools and patterns are presented first or exclusively.
Recommendations
  • Add Linux-specific guidance and examples, such as using the Key Vault VM extension for Linux (if supported), or alternative certificate provisioning mechanisms for Linux nodes.
  • Provide Bash/Azure CLI examples alongside PowerShell for certificate enrollment and management.
  • Clarify which steps or mechanisms are Windows-only and which are cross-platform, especially for VM extensions and certificate linking.
  • Reference Linux documentation or tools where applicable, and indicate parity or gaps.
  • Consider including troubleshooting or FAQ entries for Linux-based Service Fabric 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-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page covers X.509 certificate-based authentication in Service Fabric clusters and is generally cross-platform, referencing both Windows and Linux certificate storage paths. However, there is a notable Windows bias in several areas: Windows certificate store terminology and paths are mentioned first and more frequently; troubleshooting sections reference Windows event logs and tools (such as CAPI2 logging) without Linux equivalents; and configuration flags are described in terms of Windows CryptoAPI and Win32 APIs, with Linux behaviors only briefly mentioned or implied.
Recommendations
  • Provide Linux-specific troubleshooting guidance, such as log file locations, relevant systemd services, and certificate store paths (e.g., /var/lib/sfcerts).
  • Include examples of certificate management and validation using Linux tools (e.g., openssl, certutil) alongside Windows/PowerShell examples.
  • Clarify how configuration flags and certificate validation behaviors map to Linux environments, including any differences in API calls or error codes.
  • Ensure that references to certificate stores and paths always mention both Windows and Linux equivalents, not just Windows first.
  • Add explicit guidance for Linux/macOS users on how to provision, rotate, and troubleshoot certificates in Service Fabric clusters.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently provides PowerShell examples for command-line operations (add, remove, scale, configure node types), with no mention of Linux/macOS equivalents such as Azure CLI, Bash, or cross-platform scripting. PowerShell is a Windows-first tool (despite cross-platform support, the Azure PowerShell module is most commonly used on Windows), and no Azure CLI or Bash examples are given. This creates friction for Linux/macOS users who may not have or want to use PowerShell.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell (e.g., az sf managed-node-type create, update, delete, etc.).
  • Explicitly mention that PowerShell examples can be run cross-platform (if true), or provide installation guidance for non-Windows users.
  • Where possible, provide Bash or shell-agnostic examples, or clarify that ARM templates can be deployed using Azure CLI or the portal.
  • Consider listing Azure CLI examples before or alongside PowerShell to improve parity.
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-25 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, without offering equivalent Linux/bash/CLI guidance. The use of PowerShell cmdlets and the absence of Linux-native commands or cross-platform alternatives suggest a Windows-first bias, especially in operational guidance.
Recommendations
  • Add Azure CLI or bash examples for cluster operations where possible.
  • Clarify whether the PowerShell command is supported on Linux/macOS (via PowerShell Core), or provide alternative instructions for those platforms.
  • Mention any limitations or requirements for Linux/macOS users in relevant sections.
  • Where Service Fabric Explorer is referenced, note its accessibility from non-Windows platforms.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page frequently references Az PowerShell cmdlets for managing Service Fabric resources, such as Remove-AzResource and AzSF PowerShell cmdlets, and provides links to PowerShell documentation. While az CLI is mentioned for deleting applications, PowerShell examples and terminology are more prominent and appear first, potentially creating friction for Linux/macOS users who typically use az CLI or Bash scripts.
Recommendations
  • Provide equivalent az CLI examples for all operations (e.g., unprovisioning application type versions, creating applications/services).
  • Mention az CLI commands before or alongside PowerShell cmdlets to ensure Linux/macOS users can easily follow the documentation.
  • Clarify that both PowerShell and az CLI are supported and provide links to az CLI documentation.
  • Add Bash script examples where relevant.
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-25 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 and links primarily for Azure PowerShell, with PowerShell-based tools mentioned before Azure CLI and sfctl. While Azure CLI and ARM/Bicep are referenced, PowerShell is emphasized, and Linux-native tools (like sfctl) are listed last and marked as 'No' for ARM-backed support. There are no explicit Linux/macOS examples or command snippets, and the guidance assumes familiarity with PowerShell.
Recommendations
  • Provide equivalent Azure CLI command examples alongside PowerShell examples for managing NodeTypes and VMSS actions.
  • Mention sfctl and its usage more prominently, including its Linux/macOS compatibility.
  • Clarify that Azure CLI and sfctl are cross-platform and suitable for Linux/macOS users.
  • Consider reordering tool lists to avoid always listing PowerShell first.
  • Add explicit notes or examples for Linux/macOS users where relevant.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally covers both Windows and Linux clusters, but there is a tendency to mention Windows-specific tools (such as Event Log/Event Viewer, ETW, Diagnostics Agent) first or in more detail, and some examples/tutorials are focused on Windows or .NET applications. Linux equivalents (such as LTTng, Syslog, and Linux-specific configuration) are referenced but often after Windows tools and sometimes with less detail or fewer examples. Some sections lack explicit Linux example links or walkthroughs.
Recommendations
  • Ensure Linux-specific monitoring tools and workflows (e.g., Syslog, LTTng) are described with equal detail and prominence as Windows tools.
  • Add Linux-focused tutorials and examples, especially for application monitoring and cluster diagnostics.
  • Where Windows tools are mentioned (e.g., Event Viewer, Diagnostics Agent), immediately provide the Linux equivalent and link to relevant guides.
  • Review example code and walkthroughs to ensure parity for Linux (e.g., instrumenting applications, configuring monitoring agents).
  • Consider alternating the order of Windows and Linux mentions, or grouping by OS, to avoid 'Windows-first' bias.
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-25 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 display Windows bias. Windows-specific features (such as running services under AD domain accounts or gMSA) are described in detail, while Linux equivalents are missing or only briefly mentioned. Examples and links for disk encryption reference Windows/PowerShell, with Linux disk encryption marked as a 'TO DO'. Windows terminology (e.g., NetworkService) is used in code snippets without Linux alternatives. Linux-specific guidance is often absent or deferred.
Recommendations
  • Add explicit Linux examples and instructions for disk encryption, including supported tools and configuration steps.
  • Provide Linux equivalents for user accounts and security principals, clarifying how to configure service identities and permissions on Linux clusters.
  • Include code snippets and manifest examples that demonstrate Linux-specific settings and terminology.
  • Ensure parity in coverage for container security features on Linux, not just Windows (e.g., gMSA is Windows-only, but clarify Linux alternatives).
  • Review all sections for Windows-centric language and add Linux guidance where applicable.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides numerous PowerShell-based examples and references, with no mention of Linux/macOS equivalents (such as Azure CLI, REST API, or cross-platform tools). Windows/PowerShell commands are used exclusively for critical upgrade operations, and the PowerShell module is referenced throughout. There is no guidance for Linux/macOS users on how to perform these tasks, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for all upgrade operations, including creating/updating services and application upgrades.
  • Reference REST API endpoints for Service Fabric management tasks, with example requests.
  • Clarify which operations can be performed using cross-platform tools and provide links to relevant documentation.
  • Explicitly state if certain operations are only possible via PowerShell, and provide alternatives or workarounds for Linux/macOS users.
  • Include a section summarizing cross-platform support and tool parity for Service Fabric application upgrades.
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-25 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, focusing on C# and .NET Data Contract serialization. In the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are highlighted for application upgrades, with no mention of Linux/macOS equivalents or cross-platform CLI tools. This creates a moderate Windows bias, especially in upgrade guidance.
Recommendations
  • Add examples or links for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are available on Linux and macOS.
  • Clarify whether the upgrade process can be performed on Linux/macOS, and provide relevant instructions if so.
  • Include guidance for developers using non-Windows environments, such as VS Code or command-line workflows.
  • Explicitly state any limitations if certain upgrade steps are Windows-only, to help Linux/macOS users understand their options.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides migration steps for Azure Service Fabric clusters to availability zone support. While most of the guidance is platform-neutral and focuses on Azure Resource Manager templates and cluster configuration, the step-by-step migration for clusters with Basic SKU load balancer and IP resources relies heavily on PowerShell commands. These commands are presented exclusively, with no equivalent Bash, Azure CLI, or Linux-native examples. Additionally, the PowerShell examples are shown first and only, which may create friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell migration steps, especially for resource deployment, node disabling, and removal.
  • Include Bash script examples or instructions for Linux/macOS users where applicable.
  • Clarify in the documentation that PowerShell steps can be performed using Azure CLI or REST API, and link to relevant cross-platform guides.
  • Consider adding a section or callout for Linux/macOS users, summarizing alternative approaches.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation contains a notable Windows bias in its tooling recommendations and example paths. Specifically, it recommends using Visual Studio (a Windows-centric tool) to author and validate manifest XML files, referencing a Windows file path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd). Additionally, it mentions the ServiceFabric PowerShell module for service creation, which is primarily a Windows tool, without mentioning cross-platform alternatives or Linux/macOS equivalents. However, the core content and examples are platform-neutral XML, and the documentation does not restrict Service Fabric usage to Windows.
Recommendations
  • Add instructions or recommendations for validating manifest XML files using cross-platform editors (such as VS Code, JetBrains Rider, or command-line XML validators) and provide Linux/macOS file path equivalents if available.
  • Mention cross-platform tools or CLI alternatives (such as Azure CLI or Service Fabric CLI) for service creation and management, alongside PowerShell.
  • Clarify when tooling or examples are Windows-specific and provide Linux/macOS alternatives where possible.
  • Consider referencing documentation or guides for Linux-based Service Fabric clusters if relevant.
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-25 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 the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling for operational tasks (deploy, upgrade, remove, cleanup), often without equivalent Linux/CLI examples or explicit mention of cross-platform alternatives. While REST API and .NET methods are sometimes listed, PowerShell cmdlets are always present and frequently appear first, and there is little guidance for Linux/macOS users on using sfctl or Azure CLI for these tasks.
Recommendations
  • Add explicit sfctl (Service Fabric CLI) and Azure CLI examples for each operational task (deploy, upgrade, remove, cleanup), alongside PowerShell.
  • Where PowerShell cmdlets are referenced, also mention the equivalent sfctl command and REST API, and clarify their platform compatibility.
  • Provide guidance or links for Linux/macOS users on installing and using sfctl and Azure CLI for Service Fabric management.
  • Reorder examples so that cross-platform tools (sfctl, REST API, Azure CLI) are listed before or alongside PowerShell, not after.
  • Include notes about platform support for each tool, so users know which options are available on their OS.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and examples before Linux equivalents (SFCTL), and provides more detailed parameter tables and explanations for PowerShell and Visual Studio. SFCTL (the cross-platform CLI) is covered later and less extensively. There are no Linux-specific examples or patterns in the main parameter sections, and Windows tools are mentioned first throughout.
Recommendations
  • Reorganize the page so that cross-platform tools (SFCTL) are presented before or alongside Windows-specific tools (PowerShell, Visual Studio).
  • Provide equally detailed parameter tables and explanations for SFCTL, matching the depth given to PowerShell/Visual Studio.
  • Add explicit Linux/macOS usage examples for SFCTL, including sample commands and parameter usage.
  • Clarify which tools are cross-platform and which are Windows-only at the start of the article.
  • Consider adding a summary table comparing upgrade methods (PowerShell, Visual Studio, SFCTL, REST) and their platform support.
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-25 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 partition health, using Windows-specific syntax and paths (e.g., 'PS C:\Users\User'). No equivalent Linux/macOS CLI example (such as using sfctl or REST API) is given. The only command-line example is Windows-centric, and Windows tools are implicitly prioritized.
Recommendations
  • Add equivalent Linux/macOS examples using sfctl (Service Fabric CLI) or REST API for querying partition health.
  • Mention cross-platform tools and approaches alongside Windows/PowerShell examples.
  • Clarify that PowerShell is one option, and provide guidance for Linux/macOS users.
  • Consider showing Linux/macOS examples first or equally alongside Windows examples.
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-25 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 towards Windows/PowerShell usage. All code examples, module installation instructions, and REST API invocation are provided exclusively via PowerShell, with no mention of Linux/macOS-compatible tools or CLI alternatives. The Microsoft.ServiceFabric.Powershell.Http module is a Windows/PowerShell-specific tool, and there are no Bash, Azure CLI, or cross-platform REST invocation examples. This creates friction for Linux/macOS users who may need to restore backups but cannot follow the provided instructions directly.
Recommendations
  • Add equivalent examples using Bash (curl), Azure CLI, or cross-platform tools for REST API calls.
  • Document how to authenticate and invoke Service Fabric REST APIs from Linux/macOS environments.
  • Mention any Linux/macOS-compatible Service Fabric management tools, if available.
  • Clarify if the PowerShell module is required or if REST API calls can be made directly from any platform.
  • Provide guidance for certificate handling and authentication on Linux/macOS.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally platform-neutral, focusing on Service Fabric's backup configuration concepts and REST APIs. 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 (such as NFS, SMB on Linux, or Azure Files usage from Linux). Additionally, the file share examples and authentication patterns are Windows-centric and presented before any Linux-compatible guidance.
Recommendations
  • Add guidance for configuring backup storage using Linux-compatible file shares (e.g., NFS, SMB mounts on Linux, or Azure Files accessed from Linux nodes).
  • Clarify whether Linux Service Fabric clusters can use file share backup storage and provide relevant examples or limitations.
  • If only Windows file shares are supported, explicitly state this limitation to avoid confusion for Linux users.
  • Consider including example paths and authentication methods for Linux environments where applicable.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides detailed PowerShell-based instructions for scaling operations, but does not offer equivalent Linux/bash examples or mention cross-platform CLI alternatives. Windows/PowerShell tools are referenced exclusively for manual node operations, creating friction for Linux users. Additionally, Windows-centric instructions (e.g., PowerShell commands) are presented before any mention of Linux clusters, and Linux-specific guidance is only linked in the 'Next steps' section without integration into the main content.
Recommendations
  • Add Azure CLI or bash script examples for scaling and node management operations alongside PowerShell instructions.
  • Explicitly mention that Service Fabric management commands can be performed from Linux/macOS using Azure CLI or REST API, and provide links or examples.
  • Include cross-platform guidance in the main scaling sections, not just in 'Next steps'.
  • Clarify which commands are Windows-only and provide alternatives for Linux clusters 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-25 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/CLI (e.g., Azure CLI, Bash) examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before C# code, reinforcing a Windows-first bias. No Linux-specific tools or commands are mentioned, and there is no guidance for Linux users on how to perform these tasks.
Recommendations
  • Add Azure CLI or Bash examples for creating and updating Service Fabric services with move cost settings.
  • Clearly indicate whether PowerShell commands are cross-platform or provide alternatives for Linux/macOS users.
  • Present CLI or cross-platform examples alongside PowerShell, or list CLI examples first to avoid Windows-first bias.
  • Include notes or links to Linux/macOS documentation for Service Fabric management.
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-25 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 provides PowerShell-based examples and instructions, including module installation and REST API invocation via PowerShell. There are no examples or guidance for Linux/macOS users (e.g., Bash, curl, Azure CLI), and the prerequisite steps assume a Windows environment. This creates friction for non-Windows users, as Service Fabric clusters can be managed from Linux/macOS but the documentation does not address their needs.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to trigger backups and track progress from Linux/macOS.
  • 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 Azure CLI examples if possible, or note limitations if PowerShell is required.
  • Explicitly state platform requirements and alternatives for Linux/macOS users.
  • Reorder examples so that REST API usage (platform-agnostic) is shown before PowerShell-specific instructions.
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-25 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 upgrade). Windows-specific tools and registry keys are mentioned without Linux equivalents. Windows configuration details (such as disabling Windows Update via registry and template properties) are given, while Linux-specific guidance is missing or less emphasized. PowerShell is used for manual upgrades, with no Linux command-line alternatives shown.
Recommendations
  • Add Linux-specific examples for manual cluster upgrades, such as using Bash or relevant Linux tools.
  • Include guidance for disabling automatic updates on Linux VM scale sets (e.g., using cloud-init or OS-specific methods).
  • When mentioning registry keys or Windows configuration, provide Linux equivalents or clarify if not applicable.
  • Balance PowerShell and Azure CLI examples, and consider including Bash scripts where appropriate.
  • Ensure that for every Windows-specific operation, a Linux equivalent is either provided or explicitly noted as not required/applicable.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides networking best practices for Azure Service Fabric clusters and covers both Windows and Linux scenarios. However, there is a noticeable Windows bias: PowerShell is referenced as the primary API client, Windows-specific tools and tasks (e.g., RDP, Windows Update patching, Windows container networking) are discussed in detail, and Windows examples or terminology often appear before Linux equivalents. Linux is mentioned, but examples and guidance are less detailed or are referenced second. Some sample links and ARM templates are Windows-focused, and PowerShell is highlighted as the main client API, even though CLI and REST are also supported.
Recommendations
  • Provide Linux CLI (az) and Bash examples alongside PowerShell, especially for cluster management and networking tasks.
  • Ensure Linux-specific networking scenarios (e.g., SSH, Linux container networking) are described with equal detail as Windows scenarios.
  • Add links to Linux-focused ARM templates and sample clusters, not just Windows ones.
  • Mention Linux tools and patterns (e.g., iptables, netstat, systemd) where relevant, especially for troubleshooting.
  • Clarify when guidance is Windows-only and provide Linux alternatives where possible.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page lists Service Fabric cluster settings in a platform-neutral way, but there are several subtle signs of Windows bias. Windows-specific terminology (e.g., 'MY' certificate store, 'LocalMachine', NTLM authentication, Windows Defender Firewall) is used throughout, often without Linux equivalents or clarification. Windows-centric settings (e.g., log file locations, container network setup defaults, Docker npipe usage, firewall configuration) are described without always mentioning Linux alternatives. Some parameters reference Windows-only behaviors or tools, and Windows terminology is used as the default or primary example. Linux-specific settings are present but less prominent and sometimes only mentioned as exceptions.
Recommendations
  • For parameters referencing Windows-specific concepts (e.g., certificate stores, NTLM, firewall), explicitly note Linux equivalents or clarify if the setting is not applicable on Linux.
  • Where Windows terminology is used as the default (e.g., 'MY' store, 'LocalMachine'), add Linux examples or clarify Linux paths and behaviors.
  • For settings with platform-specific defaults (e.g., ContainerNetworkSetup), make both Windows and Linux defaults equally prominent.
  • Add explicit Linux-focused guidance or examples for settings that are ambiguous or Windows-centric.
  • Review descriptions for references to Windows tools or patterns and ensure Linux alternatives are mentioned where relevant.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides general information about Azure Service Fabric node types and VM scale sets, but several sections and examples show Windows bias. The JSON snippet uses a Windows-style file path (D:\\SvcFab) as the default for 'dataPath', and the 'Next steps' section links primarily to Windows/PowerShell-based scripts (changing RDP port range, admin username/password) without Linux equivalents or guidance. There is no mention of Linux-specific remote access methods (e.g., SSH), and Windows tools/patterns (RDP, PowerShell) are referenced before or instead of Linux alternatives.
Recommendations
  • Add Linux-specific examples for 'dataPath' (e.g., /var/svcfab) and clarify OS-specific path requirements.
  • Include guidance or links for Linux remote access (SSH) to cluster nodes, not just Windows RDP.
  • Provide parity in 'Next steps' by linking to Linux/SSH-based scripts or documentation for managing cluster VMs.
  • Where PowerShell is referenced, also mention Bash/CLI alternatives for Linux users.
  • Clarify when instructions are OS-specific and provide separate guidance for Windows and Linux clusters.
GitHub Create Pull Request
← Previous Page 36 of 99 Next →