Service Fabric

407
Total Pages
336
Linux-Friendly Pages
71
Pages with Bias
17.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1305 issues found
Showing 176-200 of 1305 flagged pages
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-19 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 is heavily focused on Windows tooling, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and upgrade instructions reference Windows tools, with no mention of Linux/macOS equivalents or cross-platform alternatives. There are no CLI or script examples for Linux users, and PowerShell is presented as the primary method for manual upgrades.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Include guidance for Linux/macOS users, such as how to configure upgrades without Visual Studio or PowerShell.
  • Mention and link to any available cross-platform tooling or SDKs for Service Fabric application management.
  • Clarify if certain features (like Visual Studio integration) are Windows-only, and provide alternative workflows for non-Windows environments.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents RunToCompletion semantics primarily in the context of Windows containers and Windows-specific tools. All code examples reference Windows container images and use Windows command syntax (cmd.exe). Querying deployment status is described using PowerShell and C# APIs, with no mention of Linux equivalents or cross-platform CLI tools. There are no examples or guidance for Linux containers or Linux-based workflows, despite Service Fabric supporting containers in general.
Recommendations
  • Add Linux container examples (e.g., using Ubuntu or Alpine images) alongside Windows container examples.
  • Provide equivalent Linux shell commands (bash/sh) for CodePackage entry points.
  • Mention and demonstrate querying deployment status using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Clarify any limitations or differences in RunToCompletion semantics for Linux containers, if applicable.
  • Reorganize examples to show both Windows and Linux scenarios, or explicitly state if RunToCompletion is Windows-only.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page on advanced Service Fabric application upgrade topics consistently uses PowerShell cmdlets for examples and references, with no mention of Linux/macOS equivalents or cross-platform CLI tools. All command-line instructions are given in PowerShell, and there is no guidance for Linux users on how to perform these tasks using Service Fabric CLI (sfctl) or REST APIs. This creates friction for Linux/macOS users, who may not have access to PowerShell or may prefer native tools.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Mention REST API options for relevant operations, with links to documentation.
  • Clarify which PowerShell cmdlets are Windows-only and provide guidance for Linux/macOS users.
  • In 'Next steps', include links to tutorials for Linux/macOS users, such as 'Upgrading your Application Using sfctl'.
  • Where possible, provide ARM template examples alongside PowerShell, and clarify their cross-platform applicability.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific guide for scaling standalone clusters. There are no Linux-specific instructions, examples, or mentions of Linux tooling for cluster scaling, despite Service Fabric standalone clusters being theoretically deployable on Linux.
Recommendations
  • Add Linux-specific instructions for scaling standalone clusters, including relevant CLI commands and configuration steps.
  • Provide examples using Linux shell tools (e.g., Bash, sfctl) alongside PowerShell examples.
  • Clarify whether standalone cluster scaling is supported on Linux, and if not, state this explicitly to avoid confusion.
  • Link to Linux documentation or guides if available, or note limitations if Linux support is incomplete.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily focused on PowerShell-based workflows, specifically using the Microsoft.ServiceFabric.Powershell.Http module and PowerShell scripting for REST API calls. All code examples and instructions are provided exclusively in PowerShell, with no mention of Linux/macOS equivalents (such as Bash, curl, or Azure CLI). The prerequisite section also assumes PowerShell usage and Windows tooling, and there is no guidance for Linux users on how to perform equivalent operations. This creates friction for Linux/macOS users, who may not have access to PowerShell or the required modules.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls, as Service Fabric REST APIs are platform-agnostic.
  • Document how to authenticate and make REST calls from Linux/macOS, including certificate handling.
  • Mention Azure CLI commands where possible for cross-platform parity.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST calls can be made directly from any OS.
  • Provide guidance for Linux/macOS users on connecting to Service Fabric clusters and restoring backups.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration examples using Application Manifest (XML/JSON), PowerShell, and C# APIs. PowerShell examples are prominent and shown before C# API examples, but there are no CLI or Bash examples for Linux/macOS users. The PowerShell API is Windows-centric, and no equivalent Linux-friendly command-line instructions (such as Azure CLI or REST API usage) are provided. This creates friction for Linux/macOS administrators managing Service Fabric clusters.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, if supported.
  • Clarify whether PowerShell commands can be run cross-platform (PowerShell Core), or specify Windows-only limitations.
  • Provide guidance for Linux/macOS users on how to perform equivalent operations, or explicitly state if certain operations are Windows-only.
  • Consider including Bash shell script examples or references to SDKs/libraries usable on Linux/macOS.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides code examples for configuring Service Fabric placement policies using C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or REST API) are provided. All operational examples for service creation and placement policy configuration use PowerShell, which may create friction for Linux/macOS users who do not have access to PowerShell or prefer cross-platform tools. Additionally, PowerShell examples are consistently shown alongside C# code, with no mention of Linux-native alternatives.
Recommendations
  • Add Azure CLI examples for service creation and placement policy configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Document REST API usage for configuring placement policies, providing sample requests and responses.
  • Explicitly mention whether PowerShell is required, and provide guidance for Linux/macOS users on alternative tools.
  • Consider including Bash scripts or references to Service Fabric SDK tools available on Linux.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-specific tools and patterns, such as ETW/Windows Event logs and the Windows Azure diagnostics agent, without mentioning Linux equivalents or providing Linux-specific guidance. The examples and instructions focus on Windows channels and tools, and do not address how Linux-based Service Fabric clusters can access or monitor events.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including any differences in event channels or monitoring tools.
  • Provide examples or instructions for accessing events using Linux-compatible tools (e.g., syslog, journald, Azure Monitor integration for Linux).
  • Clarify whether the EventStore REST APIs and Service Fabric Client Library are fully cross-platform, and provide usage examples for Linux environments.
  • Explicitly state if certain features or event channels are Windows-only, and offer alternative approaches for Linux users where possible.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates a notable Windows/PowerShell bias. All command-line/API usage examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica), with no mention of Linux CLI equivalents, REST APIs, or cross-platform SDK usage. The documentation assumes the use of Windows tooling and does not provide guidance for Linux or macOS users, despite Service Fabric supporting cross-platform clusters.
Recommendations
  • Include equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Document REST API or FabricClient SDK usage for soft delete and restore operations, with code snippets in a cross-platform language (e.g., Python, C# .NET Core).
  • Explicitly state if certain features or APIs are only available via PowerShell or Windows, or clarify cross-platform support.
  • Add a section or callouts for Linux/macOS users, outlining the steps and tools they should use to achieve the same tasks.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides explicit PowerShell instructions for using the Fault Analysis Service, but does not mention or provide examples for Linux/macOS command-line tools or SDKs. The PowerShell section is prominent, and no equivalent Bash, CLI, or cross-platform scripting guidance is given. This creates friction for Linux/macOS users, though workarounds exist via the C# API or REST endpoints.
Recommendations
  • Add Azure CLI or Bash examples for inducing faults and running test scenarios, if supported.
  • Clarify whether the Fault Analysis Service APIs can be accessed from Linux/macOS environments, and provide guidance for those platforms.
  • Mention or link to any cross-platform SDKs or tools (e.g., .NET Core, REST API) usable from Linux/macOS.
  • If PowerShell is required, note whether PowerShell Core (cross-platform) is supported, and provide installation instructions for Linux/macOS.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for the Azure Service Fabric hosting model provides conceptual information applicable to both Windows and Linux clusters. However, it exhibits Windows bias in several ways: PowerShell is the only CLI example shown for service creation, and all operational links reference PowerShell cmdlets. There are no Linux-specific CLI examples (e.g., Bash, Azure CLI), and PowerShell is presented before REST and .NET API options. This creates friction for Linux users, as Service Fabric supports Linux clusters but the documentation does not demonstrate parity in tooling or examples.
Recommendations
  • Add Azure CLI or Bash examples for service creation and management, especially for commands like New-ServiceFabricService.
  • Include references to Linux-compatible tools and workflows, such as sfctl (Service Fabric CLI) and REST API usage from Bash.
  • Clarify in the introduction that the concepts apply to both Windows and Linux clusters, and provide links to Linux-specific operational documentation.
  • Where PowerShell is referenced, add a note or section for Linux users explaining equivalent commands and tools.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides a significant number of PowerShell-based examples for certificate management and provisioning, and references Windows-specific tools and behaviors (such as Key Vault VM extension for Windows, S-channel, and certificate linking). While the overall guidance is Azure-centric and much of the process is cross-platform, the hands-on and troubleshooting sections focus on Windows and PowerShell, with little to no mention of Linux equivalents or alternative scripting approaches. Windows-specific mechanisms (e.g., certificate store locations, S-channel, linking on renewal) are discussed in detail, while Linux/macOS scenarios are not addressed.
Recommendations
  • Add equivalent Linux/bash examples for certificate enrollment, provisioning, and management (e.g., using Azure CLI or REST API instead of PowerShell).
  • Clarify which steps are Windows-specific and provide guidance for Linux/macOS clusters where applicable.
  • Reference Key Vault VM extension for Linux and document any differences in behavior or configuration.
  • Include troubleshooting steps and FAQs relevant to Linux/macOS environments.
  • Where Windows-specific concepts (like S-channel or certificate linking) are discussed, explicitly state their applicability and provide alternatives or note limitations for Linux/macOS.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily discusses deploying custom Windows images in Service Fabric Managed Clusters, with Windows terminology and PowerShell examples shown. While there are references to Linux custom image creation and Azure CLI for browsing Marketplace images, the main focus and examples are Windows-centric, and PowerShell is used for role assignment without a Linux CLI equivalent.
Recommendations
  • Provide explicit Linux-focused examples for deploying custom images, including ARM template snippets for Linux node types.
  • Add Azure CLI or Bash equivalents for role assignment commands alongside PowerShell.
  • Clarify which steps are applicable to both Windows and Linux node types, and highlight any differences.
  • Include links to Linux-specific documentation where relevant, such as custom image creation and deployment.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides best practice examples primarily using Azure PowerShell, with explicit links to PowerShell cmdlets for cluster operations. While Azure CLI and ARM/Bicep are mentioned in a summary table, PowerShell is emphasized in the narrative and examples, and no Linux/macOS-specific command-line examples (such as Azure CLI usage) are provided. The ordering and focus on PowerShell may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples alongside PowerShell examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • In the 'Best practices' section, mention Azure CLI as an equally valid cross-platform option, not just in the summary table.
  • Provide sample commands for both Azure CLI and PowerShell where possible.
  • Clarify that PowerShell is available cross-platform, but highlight CLI as the default for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides management guidance for Service Fabric Explorer blocking operations, primarily referencing Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for resource operations. While the Azure CLI (az resource) is mentioned once for deleting applications, most examples and instructions favor PowerShell, which is more commonly used on Windows. There is no explicit mention of Linux/macOS alternatives or parity for all operations.
Recommendations
  • Include Azure CLI equivalents for all PowerShell cmdlet examples, especially for provisioning and deleting resources.
  • Clarify that Az PowerShell cmdlets can be used cross-platform (on Linux/macOS via PowerShell Core), or provide links to relevant documentation.
  • Present examples for both PowerShell and Azure CLI side-by-side to ensure Linux/macOS users can follow along easily.
  • Explicitly mention that ARM templates and Azure CLI are fully supported on Linux/macOS.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page contains evidence of Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd') and recommends using Visual Studio for XML schema validation, which are Windows-centric tools. Additionally, the only mention of command-line tooling is the ServiceFabric PowerShell module, with no equivalent Linux CLI or cross-platform example provided. Windows terminology and tools are mentioned before any Linux alternatives (if any), and there are no explicit Linux/macOS examples or guidance.
Recommendations
  • Add instructions for validating manifest XML schema using cross-platform tools (e.g., VS Code, xmllint, or other editors) and provide Linux/macOS file path equivalents if applicable.
  • Include examples or references for using Service Fabric CLI (sfctl) or Azure CLI for service management, alongside PowerShell examples.
  • Mention cross-platform editors and tooling for authoring manifests, not just Visual Studio.
  • Clarify any platform-specific requirements for Service Fabric manifest authoring and deployment, and provide parity guidance for Linux clusters.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows-specific terminology and tools (e.g., certificate store paths like LocalMachine\My, references to Win32 CryptoAPI, Windows event logs, and error codes) are mentioned first or exclusively. Troubleshooting sections focus on Windows logs and tools, with only brief or parenthetical references to Linux equivalents. Linux certificate storage paths are mentioned, but Windows patterns dominate the narrative and examples.
Recommendations
  • Provide Linux-specific examples and troubleshooting steps alongside Windows instructions, including log locations, certificate store paths, and relevant commands.
  • Explicitly document Linux/macOS certificate store equivalents and how Service Fabric interacts with them.
  • Include Linux/macOS error codes and remediation steps where applicable.
  • Balance Windows and Linux terminology in examples and explanations.
  • Reference cross-platform tools (e.g., OpenSSL) for certificate management and validation.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no mention of Azure CLI or Bash scripting, which are cross-platform and preferred by Linux/macOS users. Additionally, PowerShell examples are presented alongside Portal and ARM template methods, but never alternatives for Linux users. There is no explicit mention that PowerShell Core (pwsh) is supported, nor are Linux-specific instructions or tools referenced.
Recommendations
  • Add Azure CLI examples for all tasks currently demonstrated with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Clarify whether PowerShell Core (pwsh) is supported for Linux/macOS, or recommend Azure CLI for those platforms.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or ARM templates.
  • Consider showing Azure CLI examples before or alongside PowerShell to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, and references Service Fabric Explorer (a Windows-centric tool) without mentioning Linux/macOS alternatives. No Linux-specific commands or cross-platform CLI options are given, and Windows tooling is presented as the default.
Recommendations
  • Add equivalent Linux/macOS command-line examples using Azure CLI or Service Fabric CLI (sfctl), if available.
  • Clarify whether the PowerShell command is required, or if cross-platform alternatives exist.
  • Mention if Service Fabric Explorer is accessible from non-Windows platforms, or provide alternative tools for Linux/macOS users.
  • Explicitly state platform requirements for any commands or tools referenced.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, exclusively references Windows container images (mcr.microsoft.com/windows/nanoserver:1809), and uses Windows-specific paths and commands (e.g., C:\WorkspaceOnHost, cmd, echo, type, ping). There is no mention of Linux containers, Linux paths, or Linux command equivalents, and the example is explicitly described as a Windows container scenario.
Recommendations
  • Add a parallel example using Linux containers (e.g., mcr.microsoft.com/linux/base image), with Linux file paths and shell commands (e.g., /workspace/log.txt, bash, echo, cat, ping).
  • Clarify whether Initializer CodePackages are supported for Linux container workloads in Service Fabric, and if so, provide guidance and examples.
  • If Initializer CodePackages are Windows-only, explicitly state this limitation at the top of the article to set expectations for Linux/macOS users.
  • Include links or references to Linux container documentation if available.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers both Windows and Linux clusters, but there are several areas where Windows tools and patterns are mentioned first or exclusively. Windows-specific tools (e.g., Event Log/Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some examples/tutorials focus on .NET/Windows. Linux-specific guidance is present but often secondary, and Linux configuration details are sometimes referenced via links rather than described inline. Some features (like EventStore APIs) are Windows-only, but this is clearly stated. Overall, Linux users can complete the tasks, but may experience friction due to Windows-centric ordering and tool emphasis.
Recommendations
  • Ensure Linux examples and tools are given equal prominence and described inline, not just linked.
  • Where Windows tools (e.g., Event Viewer, Diagnostics Agent) are mentioned, immediately follow with Linux equivalents (e.g., Syslog, Linux platform diagnostics) and provide comparable detail.
  • Add Linux-focused tutorials and examples alongside .NET/Windows ones, especially for application monitoring and logging.
  • Clarify when features are Windows-only, and provide alternative approaches for Linux clusters.
  • Review ordering so Linux and Windows guidance is presented in parallel, not Windows-first.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation covers Azure Service Fabric application security in a cross-platform context but exhibits some Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned with more detail and examples, while Linux equivalents are either briefly referenced or omitted. Some sections (e.g., disk encryption, running services under accounts) provide Windows instructions or links first, with Linux options marked as TODO or not explained. PowerShell is referenced for disk encryption, but Linux CLI or disk encryption methods are not provided.
Recommendations
  • Add explicit Linux examples for disk encryption (e.g., using Azure CLI and dm-crypt/LUKS).
  • Provide parity in instructions for running services under Linux user accounts, including relevant manifest configuration and security policies.
  • Ensure that Linux container certificate access is described with equal detail as Windows.
  • Where Windows tools (e.g., BitLocker, PowerShell) are mentioned, add corresponding Linux tools and commands.
  • Remove or resolve TODOs regarding Linux disk encryption and provide links to Linux documentation.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page primarily references Windows-centric tools and patterns, such as Visual Studio and PowerShell, in its 'Next steps' section. There are no Linux/macOS equivalents or examples provided for application upgrades, and the recommended serialization approach (Data Contract serializer) is tied to .NET Framework/WCF, which is historically Windows-focused. The page assumes C# usage and does not mention cross-platform alternatives or workflows for Linux/macOS users.
Recommendations
  • Add examples or links for upgrading Service Fabric applications using cross-platform tools (e.g., Azure CLI, REST API, or .NET Core CLI).
  • Include guidance for Linux/macOS users, such as using VS Code or other IDEs instead of Visual Studio.
  • Clarify whether the Data Contract serializer recommendation applies to .NET Core/.NET 5+ workloads, which are cross-platform, or only .NET Framework (Windows-only).
  • Provide parity in upgrade instructions for Linux/macOS environments, including PowerShell Core (pwsh) or Bash examples.
  • Explicitly state any Windows-only limitations if applicable, so Linux/macOS users are aware.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for Service Fabric application upgrade demonstrates a notable Windows bias. PowerShell is used exclusively in code examples, and only Windows-specific tools (e.g., PowerShell cmdlets like Get-ServiceFabricApplication and Start-ServiceFabricApplicationUpgrade) are mentioned. There are no equivalent examples or guidance for Linux/macOS users (e.g., using sfctl or REST APIs). Additionally, the documentation references Windows-specific components such as http.sys and error messages from the Windows HTTP Server API, without clarifying platform differences or providing Linux alternatives.
Recommendations
  • Add equivalent Linux/macOS examples using sfctl (Service Fabric CLI) or REST API calls alongside PowerShell examples.
  • Clearly state when a feature or limitation is Windows-specific (e.g., http.sys certificate handling).
  • In sections referencing PowerShell, provide a note or link to Linux/macOS instructions.
  • Reorder or parallelize examples so that Linux/macOS and Windows users are equally supported.
  • Include a table or section summarizing tool equivalence (PowerShell vs sfctl vs REST API) for common upgrade operations.
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on PowerShell and the Microsoft.ServiceFabric.Powershell.Http module for all command-line examples. There are no examples using cross-platform tools (such as Azure CLI, curl, or bash scripting), nor is there any mention of Linux/macOS equivalents for connecting to clusters or triggering backups. All REST API examples are shown via PowerShell, and there is no guidance for Linux users on how to perform these tasks.
Recommendations
  • Add equivalent examples using cross-platform tools such as curl or HTTPie for REST API calls.
  • Provide instructions for connecting to Service Fabric clusters from Linux/macOS environments, including certificate handling.
  • Mention and demonstrate the use of Azure CLI (if supported) for relevant operations.
  • Clearly state if certain features or modules are only available on Windows, and provide alternatives or workarounds for Linux/macOS users.
  • Include bash or shell script examples alongside PowerShell where possible.
GitHub Create Pull Request
← Previous Page 8 of 53 Next →