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 576-600 of 2475 flagged pages
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-02 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 offer equivalent Linux/macOS CLI examples (such as Bash, Azure CLI, or REST API). PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users. The C# API examples are cross-platform, but operational scripting is Windows-centric.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, if supported.
  • Explicitly note whether PowerShell commands can be run cross-platform (PowerShell Core), or provide Bash equivalents.
  • Clarify if Service Fabric management tasks can be accomplished via Linux-native tools or scripts.
  • If PowerShell is the only supported scripting interface, state this clearly and link to any Linux/macOS installation guidance for PowerShell Core.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily references Windows-specific upgrade and configuration guides (e.g., links ending with '-windows-server.md'), and the patch orchestration application is described only for Windows. There is no mention of Linux-specific upgrade procedures, configuration files, or patch orchestration, nor are Linux examples or links provided. This creates friction for Linux users managing Service Fabric standalone clusters.
Recommendations
  • Add explicit references and links to Linux-specific upgrade and configuration documentation, if available.
  • Provide examples and procedures for Linux clusters alongside Windows examples.
  • Clarify which features or tools are Windows-only and offer Linux alternatives or workarounds where possible.
  • Include information about patch orchestration for Linux nodes, or state if it is not supported.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page primarily uses Windows/PowerShell tooling and paths in its examples and instructions. PowerShell is the only command-line example shown for deploying applications, and file paths reference Windows locations. Linux equivalents are only briefly mentioned (e.g., the certificate store path), and no Linux-native deployment commands or examples are provided.
Recommendations
  • Provide equivalent Linux CLI examples (e.g., using Azure CLI or Service Fabric CLI) alongside PowerShell commands for deploying applications.
  • When referencing file paths (such as the schema definition or certificate store), include both Windows and Linux locations in parallel.
  • Add notes or sections clarifying any differences in workflow or configuration for Linux clusters, especially for deployment and endpoint/certificate management.
  • Where possible, link to Linux-specific documentation or tutorials for common tasks.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on Visual Studio workflows and references PowerShell for service creation, with no mention of Linux/macOS equivalents or cross-platform tooling. All examples and instructions are centered around Windows tools and patterns, and there are no instructions or guidance for Linux/macOS users deploying Service Fabric applications.
Recommendations
  • Add explicit guidance for Linux/macOS users, including CLI-based workflows (e.g., Azure CLI, Service Fabric CLI) for managing service configurations.
  • Provide examples of how to deploy and manage Service Fabric applications using cross-platform tools, not just Visual Studio and PowerShell.
  • Clarify which features are Windows-only and which are available cross-platform, and link to Linux/macOS documentation where relevant.
  • Mention alternative editors or IDEs for non-Windows users, if applicable.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-03-02 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 the Fault Analysis Service overview provides usage instructions primarily for C# and PowerShell, with explicit mention of the Service Fabric SDK and PowerShell module. There are no examples or guidance for Linux/macOS users (e.g., Bash, CLI, or cross-platform tools), and PowerShell is presented as the only scripting interface. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or REST API, which are cross-platform.
  • Provide Bash or shell script equivalents for common tasks, or clarify if PowerShell Core (cross-platform) is supported.
  • Explicitly mention any Linux/macOS limitations or supported workflows for the Fault Analysis Service.
  • Include links or references to Linux/macOS documentation for Service Fabric where relevant.
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-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides detailed information on X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows certificate store paths (e.g., LocalMachine\My), Windows-specific troubleshooting tools (event logs, CAPI2 logging), and Win32 CryptoAPI references are mentioned first or exclusively. Linux equivalents are referenced only briefly or parenthetically, and no Linux-specific troubleshooting guidance or examples are provided.
Recommendations
  • Provide explicit Linux certificate store paths and management instructions alongside Windows examples (e.g., detail usage of /var/lib/sfcerts).
  • Include Linux-specific troubleshooting steps, such as relevant log locations, commands (e.g., journalctl, openssl), and error codes.
  • Reference cross-platform certificate management tools and APIs, not just Win32 CryptoAPI.
  • Ensure that configuration examples and explanations are equally applicable to Linux, and clarify any platform-specific differences.
  • Add a section or callouts for Linux/macOS users, highlighting any nuances or limitations.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-03-02 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 in Azure Service Fabric Managed Clusters. Windows terminology and examples are presented first and most prominently. The only CLI example given is in PowerShell, and there are no equivalent Linux shell or Azure CLI examples for role assignment. While the page references Linux custom image creation and Azure CLI for browsing Marketplace images, the main workflow and examples are Windows-centric.
Recommendations
  • Add equivalent Azure CLI or Bash examples for role assignment and other operations, not just PowerShell.
  • Clarify whether Linux custom images are supported for Service Fabric Managed Clusters and provide explicit guidance/examples if so.
  • Present Windows and Linux options equally, or note if only Windows images are supported for node types.
  • Include links to Linux-specific documentation 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-03-02 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 shown for certificate enrollment, and references to Windows-specific tools and patterns (such as the Key Vault VM extension for Windows, S-channel, and Windows certificate store concepts) are prevalent. The Key Vault VM extension is described primarily in its Windows context, and Windows-specific behaviors (like certificate linking and renewal properties) are discussed in detail. Linux equivalents, such as the Key Vault VM extension for Linux or Linux certificate store handling, are not mentioned or are relegated to secondary status. Windows terminology and tools are presented first and exclusively in critical sections, creating friction for Linux/macOS users.
Recommendations
  • Add Linux-specific examples for certificate enrollment and provisioning, such as using Azure CLI or Bash scripts instead of only PowerShell.
  • Include guidance for using the Key Vault VM extension for Linux, referencing its documentation and any differences in behavior compared to Windows.
  • Discuss certificate store handling and ACLing on Linux nodes, including relevant commands and security considerations.
  • Where Windows-specific behaviors (like S-channel and certificate linking) are described, clarify their applicability and provide Linux alternatives or note their absence.
  • Ensure troubleshooting and FAQ sections include Linux/macOS scenarios and commands.
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-03-02 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 tool shown, with no mention of Azure CLI or Bash equivalents. PowerShell examples are given for all major operations (add, remove, scale, configure placement properties), and are presented alongside Portal and ARM template methods. There is no explicit indication that these operations require Windows, but the exclusive use of PowerShell and lack of Azure CLI/Bash examples may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for all operations where PowerShell is used, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention if PowerShell is required for certain operations, or clarify if Azure CLI can be used instead.
  • Consider listing Azure CLI or Bash examples before or alongside PowerShell to improve parity.
  • Add notes or links for Linux/macOS users about how to perform equivalent tasks.
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-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell command example for bypassing Infrastructure Service, with no equivalent Linux/macOS CLI or REST API example. The use of PowerShell and the Invoke-ServiceFabricInfrastructureCommand cmdlet suggests a Windows-centric approach, and the example is given without mention of cross-platform alternatives. Service Fabric Explorer is referenced, but no Linux-friendly tooling is discussed.
Recommendations
  • Add equivalent examples using Azure CLI, REST API, or other cross-platform tools for managing Infrastructure Service.
  • Clarify whether the PowerShell command is required, or if Linux/macOS users can perform the same operation via other means.
  • Mention any limitations or prerequisites for non-Windows users, and provide guidance for Linux/macOS environments.
  • If Service Fabric Explorer is Windows-only, suggest alternative monitoring tools or interfaces for Linux/macOS users.
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-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides extensive PowerShell-based migration steps and scripts for Service Fabric clusters, especially in the section for migrating clusters with Basic SKU load balancer and IP resources. PowerShell is a Windows-centric tool, and the examples and commands are exclusively shown using PowerShell, with no equivalent Bash, Azure CLI, or cross-platform scripting alternatives. Additionally, references to Windows paths (e.g., 'D:\\SvcFab') and Windows-centric sample templates are present, and Windows tools are mentioned before any Linux alternatives. While there is a mention of an Ubuntu sample template, the actual migration steps and scripts are Windows/PowerShell-only.
Recommendations
  • Provide Azure CLI or Bash equivalents for all PowerShell scripts and migration steps to ensure Linux/macOS users can follow the guide without friction.
  • Explicitly note which steps require Windows/PowerShell and offer alternatives or workarounds for Linux/macOS environments.
  • Where sample templates reference Windows paths or configurations, include Linux/Ubuntu equivalents and clarify any OS-specific requirements.
  • Add links to cross-platform tooling documentation (e.g., Azure CLI, Bash) for relevant tasks.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers monitoring Azure Service Fabric clusters on both Windows and Linux, but several sections show a Windows-first bias. Windows tools and patterns (e.g., Event Log, Event Viewer, Diagnostics Agent) are mentioned before Linux equivalents, and some examples or tutorials are Windows-centric (.NET, Visual Studio templates). Linux-specific guidance is present but less prominent, sometimes only referenced via links. 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 less detailed or less prominent Linux guidance.
Recommendations
  • Ensure Linux-specific monitoring tools and patterns are described with equal prominence and detail as Windows equivalents.
  • Provide Linux-first or parallel examples in sections that currently show Windows tools or workflows first (e.g., mention Syslog, LTTng, and Linux agent configuration alongside Windows Event Log/Diagnostics Agent).
  • Include explicit Linux sample code/tutorial links wherever Windows/.NET examples are given.
  • Clarify when features are Windows-only and provide alternative Linux approaches or links.
  • Add more Linux-focused screenshots and walkthroughs, especially for cluster and infrastructure monitoring.
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-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy
Summary
The documentation contains some Windows bias, primarily in the form of referencing Windows tools (e.g., Visual Studio, C:\Program Files paths) and mentioning PowerShell for service creation. There are no explicit Linux/macOS equivalents or cross-platform tooling suggestions, and the only tool-based guidance is Windows-specific.
Recommendations
  • Where Visual Studio is recommended for schema validation, suggest cross-platform alternatives such as VS Code with XML plugins, or xmllint for schema validation on Linux/macOS.
  • When referencing file paths (e.g., C:\Program Files\...), mention the equivalent location or approach for Linux clusters (e.g., /opt/microsoft/servicefabric/schemas/ or a note about schema availability).
  • When mentioning PowerShell for service creation, also mention the Service Fabric CLI (sfctl), which is cross-platform, and provide example commands.
  • Add explicit notes or examples for Linux-based Service Fabric clusters, especially for common developer tasks.
  • Review and update any tool or workflow recommendations to ensure Linux/macOS parity where possible.
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-02 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 show Windows bias. Windows-specific tools and patterns (e.g., Active Directory, gMSA, BitLocker, NetworkService account) are mentioned, often before or instead of Linux equivalents. Some examples and links focus on Windows scenarios, and Linux-specific guidance is either missing or relegated to brief mentions. Disk encryption is discussed primarily with Windows/PowerShell, and Linux disk encryption is left as a TODO. The use of Windows accounts and features is described in detail, while Linux approaches are less explicit.
Recommendations
  • Add explicit Linux examples and guidance for disk encryption, including supported tools and patterns (e.g., dm-crypt, Azure Disk Encryption for Linux).
  • Provide parity in user account and security principal configuration for Linux clusters, including how to run services under Linux user accounts and groups.
  • Include Linux-specific instructions for certificate management and container security, not just Windows/gMSA.
  • Ensure that all code snippets and walkthroughs are available for both Windows and Linux environments.
  • Clarify which features are cross-platform and which are Windows-only, and provide alternative approaches for Linux where possible.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides links to upgrade tutorials using Visual Studio and PowerShell, both of which are Windows-centric tools. There are no equivalent Linux/macOS upgrade examples or CLI alternatives mentioned. The serialization guidance is focused on C# and .NET, but Service Fabric supports .NET Core, which is cross-platform. The page does not mention Linux tooling or workflows for application upgrades.
Recommendations
  • Add examples or links for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl).
  • Include guidance for Linux/macOS users, such as how to perform upgrades from non-Windows environments.
  • Mention .NET Core/.NET 5+ compatibility and serialization options for cross-platform scenarios.
  • Ensure parity in documentation by providing Linux/macOS-specific instructions alongside Windows/PowerShell/Visual Studio examples.
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-02 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. PowerShell is the only CLI example provided, and references to Windows-specific tools (e.g., http.sys, PowerShell cmdlets) are present. There are no Linux or cross-platform CLI examples (such as Azure CLI, REST API, or Service Fabric CLI), and Windows tools and patterns are mentioned exclusively or before any Linux equivalents. This creates friction for Linux/macOS users, who may not have access to PowerShell or Windows-specific APIs.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), Azure CLI, or REST API for application upgrades.
  • Mention cross-platform upgrade workflows and tools where possible.
  • Clarify which features or commands are Windows-only, and provide guidance for Linux/macOS users.
  • Include links or references to Linux/macOS documentation for Service Fabric application upgrades.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page frequently references PowerShell cmdlets and Windows-centric tooling (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) alongside .NET APIs and REST operations, but does not provide equivalent Linux/CLI examples or highlight cross-platform tools (such as sfctl or Azure CLI) in the main procedural sections. PowerShell examples are shown first and most prominently, and Windows tools are mentioned before REST or cross-platform alternatives, creating friction for Linux/macOS users.
Recommendations
  • Add explicit examples and procedural steps using sfctl (Service Fabric CLI) and Azure CLI for all major lifecycle operations (deploy, upgrade, remove, etc.), ensuring parity with PowerShell examples.
  • Where PowerShell cmdlets are referenced, also mention or link to the equivalent sfctl/Azure CLI commands, and clarify which tools are cross-platform.
  • Consider reordering tool mentions so that cross-platform options (sfctl, Azure CLI, REST API) appear before or alongside Windows-specific tools.
  • Add a short section or note clarifying which management tools are available on Linux/macOS and how to use them for common tasks.
  • Ensure that all code snippets and automation examples include Linux-compatible options where possible.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-03-02 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 equivalent CLI or Linux-native examples. The Service Fabric PowerShell cmdlets are used throughout for application upgrade operations, and there is no mention of cross-platform tools (such as Azure CLI or REST API) for Linux/macOS users. Additionally, PowerShell examples are presented first and exclusively, creating friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for all upgrade operations (e.g., creating/updating services, starting upgrades, rolling back upgrades, updating parameters).
  • Mention REST API options for Service Fabric management where applicable.
  • Clarify which PowerShell cmdlets are available cross-platform (via PowerShell Core) and which are Windows-only.
  • Provide guidance for Linux/macOS users on how to perform equivalent operations, including links to relevant documentation.
  • Where possible, present cross-platform examples (Azure CLI, REST API) alongside PowerShell examples, not just after or instead of them.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-03-02 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 with less depth. The 'Next steps' section also lists Windows-centric tutorials first, with Linux CLI guidance appearing later.
Recommendations
  • Reorganize the documentation so that SFCTL (cross-platform CLI) parameters and examples are presented alongside or before PowerShell/Visual Studio sections.
  • Provide equally detailed parameter tables and explanations for SFCTL as are given for PowerShell and Visual Studio.
  • Add explicit Linux/macOS usage examples for SFCTL, including sample commands and parameter usage.
  • In the 'Next steps' section, list Linux/SFCTL tutorials alongside or before Windows/PowerShell/Visual Studio tutorials to signal parity.
  • Clarify that SFCTL is the recommended cross-platform tool for Linux/macOS users.
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-02 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, which are inherently Windows-centric. There are no examples or guidance for Linux/macOS users, such as using Bash, Azure CLI, or cross-platform REST tools (e.g., curl). The prerequisite section requires installation of a PowerShell module, and all REST API calls are demonstrated using PowerShell cmdlets, with no mention of alternatives for non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for REST API calls (e.g., using curl or wget).
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module can be used on PowerShell Core (pwsh) on Linux/macOS, or provide alternatives.
  • Include instructions for connecting to Service Fabric clusters from Linux/macOS environments.
  • Provide guidance for Linux/macOS users on prerequisites and tool installation.
  • Consider showing REST API payloads and headers separately from PowerShell, so users can use any HTTP client.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily biased toward Windows/PowerShell usage. All code examples and instructions rely exclusively on PowerShell cmdlets and scripts, with no mention of Linux/macOS-compatible tools or workflows. The prerequisite explicitly requires the Microsoft.ServiceFabric.Powershell.Http module, and REST API usage is only demonstrated via PowerShell. There are no Bash, curl, or cross-platform CLI examples, nor guidance for Linux users.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to trigger restores and track progress from Linux/macOS.
  • Document how to authenticate and manage certificates for REST calls on Linux/macOS (e.g., using OpenSSL, curl --cert, etc.).
  • Mention Azure CLI or Service Fabric CLI (sfctl) alternatives if available, and provide cross-platform instructions.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module functionality is available or required on non-Windows platforms, and provide alternatives if not.
  • Include a section explicitly addressing Linux/macOS users, outlining supported workflows and any limitations.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides PowerShell-based manual scaling instructions and references Windows tooling (e.g., PowerShell commands) without offering equivalent Linux CLI or cross-platform alternatives. Windows/PowerShell examples are given first and exclusively in critical scaling procedures, which creates friction for Linux users. However, the page does mention Linux clusters and links to Linux-specific documentation, indicating Service Fabric is not Windows-only.
Recommendations
  • Add equivalent Bash/CLI instructions for scaling operations, such as using Azure CLI or REST API calls, especially for disabling/removing nodes.
  • Clearly indicate which commands are Windows-specific and provide cross-platform alternatives where possible.
  • Include examples for Linux users in critical sections, such as scaling in/out, to ensure parity.
  • Reference Service Fabric CLI (sfctl) or Azure CLI for cluster management tasks alongside PowerShell.
  • Consider restructuring sections so Linux and Windows instructions are presented in parallel or clearly separated.
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-02 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 given its own section and is more prominent. Windows-specific tools and registry keys are mentioned in the VM upgrade section, with no Linux equivalents or guidance. PowerShell is used for cluster upgrades, with no Linux command-line alternatives (e.g., Bash or CLI) provided. Windows configuration properties are shown before any Linux-specific guidance, and Windows registry keys are referenced without mentioning Linux update management.
Recommendations
  • Add Linux-specific examples for cluster upgrades, such as Bash scripts or Azure CLI commands.
  • Include guidance for disabling automatic updates on Linux VMs (e.g., using apt or yum configuration) alongside Windows registry instructions.
  • Provide parity in upgrade instructions, showing both Windows and Linux approaches for manual upgrades.
  • Ensure PowerShell examples are paired with equivalent Bash or CLI examples where possible.
  • Clarify which steps are Windows-only and which are cross-platform, to help Linux/macOS users navigate the documentation.
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-02 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 bias towards Windows: PowerShell is referenced as the primary client API example, Windows-specific tools and terminology (e.g., netsh, RDP, Windows container workloads) are mentioned first or exclusively, and some example links and ARM templates are Windows-focused. Linux equivalents are sometimes mentioned, but often after Windows or less prominently.
Recommendations
  • Include Linux CLI (az CLI, bash) examples alongside PowerShell, especially for client API access and cluster management.
  • Mention Linux tools (e.g., ss, ip, netstat) where Windows tools like netsh are referenced.
  • Provide ARM template examples for Linux clusters, not just Windows.
  • Ensure Linux container networking scenarios are described with equal detail as Windows container scenarios.
  • When referencing reverse proxy solutions, highlight Linux-native options and usage patterns.
  • Balance the order of Windows and Linux references in sections and links.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page primarily describes Service Fabric's periodic backup configuration in a platform-neutral way, but the only example for file share backup storage uses Windows-style UNC paths (\\StorageServer\BackupStore) and references 'Integrated Windows Authentication' as the default method for file share access. There are no Linux or SMB-specific examples or guidance for file share configuration, and Windows authentication is mentioned first and exclusively. Azure Blob storage examples are platform-neutral, but file share backup is presented as a Windows-centric scenario.
Recommendations
  • Add examples and guidance for configuring file share backup storage using SMB on Linux, including sample paths and authentication methods (e.g., username/password, mount options).
  • Clarify whether Linux-based Service Fabric clusters can use file share backup, and if so, provide parity instructions.
  • Mention Linux-compatible authentication mechanisms for file shares, such as Kerberos or username/password, and note any limitations.
  • Consider including a note about cross-platform support for file share backup, or explicitly state if Windows-only.
GitHub Create Pull Request
← Previous Page 24 of 99 Next →