Service Fabric

810
Total Pages
600
Linux-Friendly Pages
210
Pages with Bias
25.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

718 issues found
Showing 201-225 of 718 flagged pages
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is largely platform-neutral, but there are subtle indications of Windows bias. The only explicit OS-specific reference is in the section about upgrading OS images for cluster nodes, which links only to Windows patching guidance. Additionally, when mentioning command-line management, PowerShell is always listed before Azure CLI, and no Linux/macOS-specific tools or examples are provided. However, the majority of the content is applicable to all platforms, and Service Fabric supports both Windows and Linux clusters.
Recommendations
  • Add explicit references and links to Linux OS patching guidance for Service Fabric clusters, if available.
  • When listing management tools, alternate the order (e.g., 'using Azure CLI or PowerShell') or clarify that both are supported on all platforms.
  • If there are Linux/macOS-specific considerations for upgrades or cluster management, include a section or callout summarizing them.
  • Provide examples or links for Linux-based Service Fabric clusters where relevant, especially in sections about OS patching and certificate management.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally aims to be cross-platform, mentioning both Windows and Linux support for Service Fabric. However, there are several instances where Windows-specific tools, processes, or terminology are mentioned first or exclusively, such as references to 'auto-start Windows service', EXE/DLL files, and Windows-specific process names. Linux equivalents are not always provided or are mentioned after Windows. This may create confusion or friction for Linux/macOS users, though most critical concepts are still explained in a platform-agnostic way.
Recommendations
  • When describing node startup, clarify the equivalent process for Linux clusters (e.g., what starts the Service Fabric processes on Linux nodes).
  • When referencing EXE/DLL files, note that on Linux these would be ELF binaries or shared objects, and provide examples or clarifications.
  • Where Windows-specific process names are given (e.g., FabricHost.exe), mention the Linux equivalents or note that process names may differ.
  • In sections where Windows services or tools are referenced, add Linux equivalents or clarify cross-platform differences.
  • Review the ordering of examples and explanations to avoid always listing Windows first unless there is a technical reason.
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-02-10 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 deploying Service Fabric applications, which is a Windows-centric tool. Windows file paths and certificate store names are mentioned first, with Linux equivalents only briefly referenced. There are no Linux CLI (e.g., Bash, sfctl) examples for deployment, and Windows terminology/tools are presented before Linux alternatives.
Recommendations
  • Add Linux deployment examples using sfctl or Bash scripts alongside PowerShell examples.
  • Mention Linux file paths and certificate store locations equally with Windows paths, not just as a note.
  • Clarify any differences in endpoint configuration or deployment between Windows and Linux clusters.
  • Consider providing a table or section explicitly comparing Windows and Linux approaches for endpoint specification and deployment.
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-10 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 the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, and it is presented as the exclusive scripting option for command-line automation. There are no examples for Linux/macOS CLI tools such as Azure CLI or Bash scripts. Additionally, PowerShell examples are given equal prominence to portal and ARM template methods, and are sometimes required for certain operations (e.g., removing primary node types), which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly state when PowerShell is required due to Azure module limitations, and provide guidance for Linux/macOS users (e.g., using Azure Cloud Shell, which supports PowerShell and Bash).
  • Where possible, mention Bash scripting or other cross-platform automation options.
  • Review and update any sections where PowerShell is presented as the only automation option, ensuring Linux parity.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides extensive PowerShell examples and references Windows-specific tools and patterns (such as the Key Vault VM extension for Windows, S-channel, and Windows certificate store locations). While the overall guidance is Azure-centric and applicable to both Windows and Linux VM/VMSS, the hands-on examples, troubleshooting, and technical deep-dives are predominantly Windows-focused. Linux equivalents (such as Linux VM extensions, certificate store paths, or CLI/bash scripting) are not mentioned or provided, and Windows terminology and tooling are presented first and exclusively in several sections.
Recommendations
  • Add Linux-specific examples for certificate provisioning, such as using the Key Vault VM extension for Linux or Azure CLI/bash scripts.
  • Document Linux certificate store paths and how Service Fabric interacts with them.
  • Include troubleshooting steps and automation scripts for Linux environments (e.g., bash, Python, Azure CLI).
  • Clarify which steps are Windows-only and provide Linux alternatives where possible.
  • Reference the Key Vault VM extension for Linux and link to its documentation alongside the Windows version.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides detailed explanations and examples for X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows-specific terminology (e.g., 'LocalMachine\My' certificate store), Windows-centric troubleshooting (event logs, CAPI2 logging), and references to Win32 CryptoAPI and Windows cryptographic providers are presented before or instead of Linux equivalents. Linux paths (e.g., /var/lib/sfcerts) are mentioned only briefly and lack parity in troubleshooting and operational guidance.
Recommendations
  • Provide equivalent Linux/macOS examples and troubleshooting steps, such as how to locate Service Fabric certificates on Linux nodes, relevant log locations, and commands for certificate management.
  • Expand on Linux certificate store paths and clarify how certificate loading and validation occurs on Linux, including any differences in behavior or configuration.
  • Include Linux/macOS-specific error codes and remediation steps, or reference relevant tools (e.g., OpenSSL, systemd journal logs) for diagnosing certificate issues.
  • Balance Windows and Linux terminology throughout the document, ensuring Linux paths and tools are mentioned alongside Windows ones.
  • Where Windows APIs (e.g., CertGetCertificateChain) are referenced, provide Linux equivalents or note if functionality is identical or differs.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, with no equivalent CLI or Linux/macOS instructions. It references Service Fabric Explorer (a web tool, but often Windows-centric in documentation) and does not mention cross-platform alternatives. No Linux/macOS command-line examples are given, and the only automation example uses PowerShell.
Recommendations
  • Provide equivalent Azure CLI or Service Fabric CLI (sfctl) commands for bypassing Infrastructure Service, or clarify if such functionality is not available cross-platform.
  • Explicitly state if certain operations (like 'Invoke-ServiceFabricInfrastructureCommand') are only supported on Windows/PowerShell, and suggest alternatives for Linux/macOS users if available.
  • Add notes or examples for Linux/macOS users, including how to connect to Service Fabric clusters and perform administrative tasks using cross-platform tools.
  • Clarify whether Service Fabric Explorer is fully cross-platform and accessible from any OS/browser, or if there are platform-specific limitations.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally aims for cross-platform coverage, but there are several areas where Windows tools and workflows are mentioned first or in more detail, and Linux equivalents are less prominent or only referenced via links. Some monitoring features (like EventStore APIs) are called out as Windows-only, but Linux alternatives are not always explained in equal depth. Examples and tutorials focus on .NET/Windows scenarios, and PowerShell/Windows Event Log are referenced without Linux command equivalents.
Recommendations
  • When mentioning Windows-specific tools (e.g., Event Log, Diagnostics Agent), provide parallel Linux instructions or explicitly link to Linux setup/configuration guides in the same section.
  • Add Linux-specific examples or code snippets where only Windows/PowerShell/Visual Studio workflows are shown (e.g., for application logging, cluster monitoring setup).
  • When listing recommended tools or agents, clearly indicate which are cross-platform and which are Windows-only, and provide Linux alternatives up front.
  • In the 'Recommended setup' section, include explicit Linux cluster monitoring instructions or a summary link to the Linux setup guide.
  • Where possible, provide sample commands or scripts for Linux (e.g., using Syslog, LTTng, or Linux CLI tools) alongside Windows/PowerShell examples.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is notably Windows-focused: all code examples use Windows containers (NanoServer), Windows-specific commands (cmd, set, exit), and reference only Windows container images. The only tooling example for querying deployment status is via PowerShell, with no Linux CLI or cross-platform alternatives given. There is no mention of Linux containers or how to implement RunToCompletion semantics for Linux-based workloads.
Recommendations
  • Provide parallel examples using Linux containers (e.g., using Ubuntu or Alpine images) with equivalent shell commands.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, add Linux-specific code and manifest examples.
  • Include instructions for querying deployment status using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), if available.
  • When referencing container images, mention both Windows and Linux options if the feature is supported on both.
  • Explicitly state if RunToCompletion is Windows-only, to avoid confusion for Linux users.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides multiple PowerShell-based examples for scaling operations, with no equivalent Linux CLI or cross-platform guidance. Steps for manual scaling reference PowerShell commands exclusively, and Windows tooling is mentioned first or solely in critical procedures. While Service Fabric supports Linux clusters, Linux users are left to infer or research their own command-line equivalents, creating friction.
Recommendations
  • Add equivalent Linux CLI (e.g., Bash, sfctl) examples alongside PowerShell commands for scaling operations.
  • Explicitly mention cross-platform tools and workflows where possible, such as Azure CLI or REST API usage.
  • Clarify which steps are universal and which are OS-specific, and provide links to Linux-specific documentation where relevant.
  • Consider restructuring step-by-step guides to present both Windows and Linux options in parallel.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation generally aims to be cross-platform, but several sections show a Windows-first bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are described in detail, while Linux equivalents are not mentioned or are left as TODOs. Some examples and links focus on Windows tools (e.g., PowerShell for disk encryption), and Linux instructions are missing or deferred. In some sections, Windows options are described before Linux, and Linux parity is not always clear.
Recommendations
  • Add explicit Linux examples and instructions where only Windows or PowerShell examples are given (e.g., disk encryption for Linux clusters).
  • When mentioning Windows-specific features (e.g., BitLocker, gMSA), provide Linux equivalents or state if not supported.
  • Ensure that Linux and Windows options are presented with equal prominence and detail, ideally side-by-side.
  • Remove or resolve TODOs about Linux support (e.g., 'Encrypt disks on Linux clusters?') and provide actionable guidance.
  • Include references to Linux tools (e.g., dm-crypt, LUKS) and Linux-compatible Service Fabric features where relevant.
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-10 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 upgrades demonstrates a notable Windows bias. PowerShell is used exclusively for code examples, and only Windows-specific tools (e.g., PowerShell cmdlets, http.sys) are mentioned. There are no equivalent examples or guidance for Linux users (e.g., using Azure CLI, REST API, or sfctl). The documentation assumes a Windows environment, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent Linux/macOS examples using Azure CLI, REST API, or sfctl where PowerShell is used.
  • Mention cross-platform tools and workflows alongside Windows-specific ones.
  • Clarify when certain features or limitations (e.g., http.sys, PowerShell cmdlets) are Windows-only.
  • Reorder sections or examples to present cross-platform solutions first, or at least in parallel with Windows examples.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed PowerShell examples for managing dynamic node tags and configuring services, but does not include equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API usage). PowerShell is a Windows-centric tool, and its exclusive use here creates friction for users on non-Windows platforms.
Recommendations
  • Add examples using cross-platform tools such as Azure CLI or REST API for managing node tags and configuring services.
  • Explicitly mention whether PowerShell Core (cross-platform) is supported, and if so, provide guidance for Linux/macOS users.
  • Include Bash or shell script examples where possible.
  • Clarify if certain operations are only possible via PowerShell or C# APIs, and provide workarounds or alternatives for Linux/macOS users.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page on describing Azure Service Fabric apps and services demonstrates some Windows bias. It references the use of Visual Studio (a Windows-centric tool) for authoring manifests and checking schema, and mentions the ServiceFabric PowerShell module as a way to create service instances, without mentioning Linux/macOS equivalents or cross-platform alternatives. Windows paths are used in examples for schema files, and there are no references to Linux tooling or workflows for manifest authoring or validation. However, the core manifest concepts and XML examples themselves are platform-agnostic.
Recommendations
  • Add instructions or references for validating manifest XML schema on Linux/macOS, such as using xmllint or VS Code with the XML extension.
  • Mention cross-platform tools (e.g., Azure CLI, Service Fabric CLI (sfctl)) for managing Service Fabric applications and services, in addition to or instead of PowerShell.
  • When referencing file paths or tools, provide Linux/macOS equivalents or note if a feature is only available on Windows.
  • Clarify that Visual Studio is optional and suggest VS Code or other editors for cross-platform development.
  • If Service Fabric features are Windows-only, explicitly state this to set expectations for Linux/macOS users.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for the Service Fabric application lifecycle heavily references PowerShell cmdlets and .NET APIs for operational tasks (deploy, upgrade, remove, maintain), with only passing mention of REST APIs and no explicit Linux/CLI examples. There is no coverage of Linux-native tools or Service Fabric CLI (sfctl) usage in the main procedural steps, despite a link to CLI docs at the top. This creates friction for Linux/macOS users, who are likely to use sfctl or Azure CLI rather than PowerShell.
Recommendations
  • Add explicit sfctl (Service Fabric CLI) command examples alongside PowerShell cmdlets for all operational steps (deploy, upgrade, remove, maintain, etc.).
  • Where PowerShell is mentioned, clarify if/when it is available cross-platform (e.g., via PowerShell Core on Linux/macOS), or provide alternative commands.
  • In procedural lists, present REST API, sfctl, and PowerShell options together, or group by platform/tool.
  • Add a short section or callout for Linux/macOS users, linking to relevant CLI documentation and noting any platform-specific considerations.
  • Ensure that all code snippets and automation examples have Linux equivalents (e.g., bash/sfctl/az CLI).
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page heavily features PowerShell cmdlets for Service Fabric application upgrades, with all command-line examples given in PowerShell syntax. There is no mention of Linux/macOS equivalents, such as Azure CLI, REST API, or Service Fabric CLI (sfctl), nor are cross-platform tools or workflows discussed. The documentation assumes the reader is using Windows/PowerShell, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Azure CLI and/or Service Fabric CLI (sfctl) for all PowerShell commands.
  • Explicitly mention cross-platform tools and workflows where applicable.
  • Clarify which features are available on Linux clusters and provide guidance for Linux/macOS users.
  • Reorganize sections so that cross-platform approaches are presented alongside or before Windows-specific ones.
  • Link to Linux-specific documentation or note any limitations for Linux clusters.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page primarily discusses data serialization concepts in the context of Azure Service Fabric, which is cross-platform. However, in the 'Next steps' section, it lists 'Upgrading your Application Using Visual Studio' and 'Upgrading your Application Using PowerShell' as the first two upgrade guides, both of which are Windows-centric tools. There are no explicit Linux/macOS CLI or cross-platform upgrade examples or links provided, and the default serializer discussed is .NET's Data Contract, which is cross-platform, so no bias there.
Recommendations
  • Add links or references to cross-platform upgrade guides using Azure CLI or Service Fabric CLI (sfctl), if available.
  • If PowerShell is mentioned, also mention cross-platform PowerShell Core or Bash equivalents, or clarify if only Windows PowerShell is supported.
  • Consider listing cross-platform or Linux/macOS upgrade options before or alongside Windows-specific tools in the 'Next steps' section.
  • Explicitly state if certain upgrade methods (e.g., Visual Studio) are Windows-only, and provide alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents PowerShell and Visual Studio (Windows tools) upgrade parameters first, with detailed tables and examples, while Linux/macOS equivalents (SFCTL/CLI) are described later and less prominently. Most parameter tables and examples are Windows-centric, and Linux users must scroll further to find relevant information. There are no explicit Linux/macOS command examples in the main body, and the structure implies a Windows-first workflow.
Recommendations
  • Reorganize the documentation to present SFCTL (CLI) parameters and workflows alongside PowerShell/Visual Studio, or in parallel sections, rather than after all Windows tooling.
  • Provide explicit Linux/macOS command-line examples (using SFCTL) in the main parameter tables, not only in a separate section.
  • Clarify at the start that all features are available cross-platform, and that SFCTL is the recommended tool for Linux/macOS.
  • Add a summary table mapping PowerShell/Visual Studio parameters to SFCTL equivalents for easy cross-reference.
  • Ensure that Linux/macOS users are not required to refer to Windows tooling sections for parameter explanations.
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-10 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 is heavily biased towards Windows/PowerShell usage. All code examples use PowerShell, including REST API calls, and there are no examples or guidance for Linux/macOS users (e.g., Bash, curl, or Azure CLI). The prerequisite section requires installation of a PowerShell module, and there is no mention of cross-platform alternatives. The REST API is always demonstrated via PowerShell, not via curl or other tools. This creates friction for Linux/macOS users, who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add Bash/curl examples for REST API calls alongside PowerShell examples.
  • Mention Azure CLI commands if available for triggering backups and tracking progress.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available cross-platform (PowerShell Core), and if not, provide alternatives.
  • Provide guidance for connecting to Service Fabric clusters from Linux/macOS (e.g., using REST API directly, Azure CLI, or other tools).
  • Reorder examples so that REST API usage (which is platform-neutral) is shown first, followed by platform-specific tooling.
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-10 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-based workflows, with all command-line examples using PowerShell syntax and Windows-specific modules. There are no equivalent examples for Linux/macOS users (e.g., using Bash, curl, or cross-platform tools), and the required tooling (Microsoft.ServiceFabric.Powershell.Http) is Windows/PowerShell-centric. This creates friction for non-Windows users, who must adapt or reverse-engineer the REST API calls from PowerShell examples.
Recommendations
  • Provide equivalent Bash/curl examples for REST API calls, demonstrating how to authenticate and trigger restores from Linux/macOS.
  • Clarify whether the PowerShell modules are supported on PowerShell Core (pwsh) on Linux/macOS, and document any limitations.
  • List required certificates and authentication steps in a cross-platform manner.
  • Explicitly state if certain operations are only supported on Windows, and offer alternative guidance for Linux/macOS users where possible.
  • Add a section summarizing cross-platform support for Service Fabric backup/restore tooling.
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-10 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 presented as a primary alternative, which is Windows-centric. In the cluster upgrade section, only PowerShell commands are given for manual upgrades, with no Linux/bash equivalent. Windows registry keys and Windows Update settings are discussed without mentioning Linux equivalents or alternatives. Windows configuration properties are shown before Linux is referenced. However, links to both Windows and Linux cluster creation tutorials are provided, and the core template examples are platform-neutral.
Recommendations
  • Add Linux/bash equivalents for manual cluster upgrade commands (e.g., using bash or Azure CLI instead of PowerShell).
  • When discussing OS upgrade configuration, mention Linux-specific options or clarify if steps are Windows-only.
  • Provide guidance or examples for disabling automatic updates on Linux VMSS nodes, if applicable.
  • Where Windows registry keys or Windows Update settings are referenced, add notes about Linux patching approaches or clarify if the guidance is Windows-specific.
  • Ensure that PowerShell examples are accompanied by bash/Azure CLI equivalents throughout 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-02-10 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 provides both Windows and Linux guidance for Service Fabric networking, but there are several areas where Windows is prioritized or Linux parity is lacking. Windows/PowerShell examples and terminology are mentioned first or exclusively in some sections (e.g., Client API, Azure DevOps, ARM template sample, and application networking). PowerShell is referenced as the primary API client, and Windows-specific tools and features (such as RDP, Windows Updates, and Windows container networking) are discussed in detail, sometimes without equivalent Linux examples or guidance. Linux-specific instructions are present but often secondary or less detailed.
Recommendations
  • Ensure Linux examples and terminology are provided alongside Windows/PowerShell examples, especially in sections discussing API access, DevOps, and application networking.
  • Add explicit Linux CLI (az, bash) examples where PowerShell is referenced.
  • Provide Linux-focused ARM template samples and links, not just Windows ones.
  • Clarify when guidance applies to both Windows and Linux, and highlight any differences.
  • Expand Linux container networking guidance to match Windows container coverage.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides some Windows-centric examples and references, such as using Windows-style file paths (e.g., 'D:\\SvcFab') in the Service Fabric extension snippet and linking to PowerShell scripts for tasks like changing RDP port ranges and admin credentials. While Linux is mentioned in the extension type ('ServiceFabricLinuxNode'), the examples and next steps focus on Windows tools and patterns.
Recommendations
  • Provide Linux-style file path examples (e.g., '/var/lib/servicefabric') alongside Windows paths in extension configuration.
  • Include links or references to equivalent Linux-based management scripts or instructions for tasks like changing SSH port ranges or updating Linux admin credentials.
  • When referencing remote connection methods, mention SSH for Linux nodes in addition to RDP for Windows nodes.
  • Ensure that examples and guidance are balanced between Windows and Linux where both are supported.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides code examples for advanced placement policies in Service Fabric using C# and PowerShell. All CLI examples are PowerShell-based, with no equivalent Bash, Linux CLI, or cross-platform command-line examples. PowerShell is presented as the only scripting interface for service creation and configuration, which may create friction for Linux/macOS users who typically use Bash or Azure CLI. The documentation does not mention or provide guidance for Linux-native tools or workflows.
Recommendations
  • Add Azure CLI or Bash examples for service creation and placement policy configuration, if supported.
  • Explicitly mention whether PowerShell commands are cross-platform or provide alternatives for Linux/macOS users.
  • Clarify any platform limitations for Service Fabric management tools and link to Linux/macOS-specific guidance if available.
  • Consider including a table or section comparing Windows and Linux management options for Service Fabric clusters.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for configuring auto scaling policies in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no Linux/macOS shell (e.g., Bash, CLI) equivalents. PowerShell is presented as the only scripting option, and there is no mention of Linux tools or cross-platform CLI commands. This creates friction for Linux/macOS users, especially since Service Fabric supports Linux containers and clusters.
Recommendations
  • Add Azure CLI or Bash script examples for configuring scaling policies, especially for Linux clusters.
  • Explicitly mention cross-platform tooling where available (e.g., Azure CLI, REST API).
  • Clarify which PowerShell commands are available on Linux (via PowerShell Core), and provide alternatives if not.
  • Include notes or links to Linux-specific guidance for Service Fabric auto scaling.
  • Consider providing sample YAML or JSON for ARM templates if relevant.
GitHub Create Pull Request
← Previous Page 9 of 29 Next →