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 401-425 of 2475 flagged pages
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for the Fault Analysis Service overview provides usage examples for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell (via the Service Fabric SDK and PowerShell module). No Linux-specific tools, CLI commands, or cross-platform scripting examples are mentioned. The PowerShell example is prominent, and PowerShell is primarily a Windows-centric tool, although it is available on Linux. There is no mention of Linux-native equivalents (such as Bash, Azure CLI, or REST API usage), nor is there guidance for Linux/macOS users.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or REST API, which are cross-platform.
  • Mention PowerShell Core compatibility and clarify if the PowerShell module works on Linux/macOS.
  • Provide Bash or shell script examples for Linux users, if applicable.
  • Explicitly state platform requirements or limitations for the Fault Analysis Service and its tooling.
  • Ensure parity in documentation for Linux/macOS users by listing cross-platform tools before or alongside Windows-specific tools.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides links to application upgrade tutorials using Visual Studio and PowerShell, both of which are primarily Windows tools. There are no Linux/macOS equivalents or examples provided for upgrading applications, nor is there mention of cross-platform CLI tools. The serialization guidance is C#-centric, but Service Fabric supports .NET Core, which is cross-platform.
Recommendations
  • Add examples or links for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are available on Linux/macOS.
  • Mention that PowerShell Core is available cross-platform, and clarify if the PowerShell tutorial is compatible with PowerShell Core on Linux/macOS.
  • Provide guidance for Linux/macOS users on how to perform application upgrades without Visual Studio, possibly using command-line tools or other IDEs.
  • Explicitly state platform requirements for each upgrade method to help users identify which tutorials are relevant to their environment.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily focuses on deploying custom Windows images in Azure Service Fabric Managed Clusters. Windows terminology and examples (such as PowerShell commands) are presented first and exclusively, with no equivalent Linux shell examples. Although there are references to Linux custom image creation and Azure CLI for browsing marketplace images, the main workflow and examples are Windows-centric, and Linux-specific guidance is minimal.
Recommendations
  • Add Linux shell (bash/CLI) equivalents for PowerShell commands, especially for role assignment.
  • Clarify whether Linux custom images are supported for Service Fabric Managed Clusters and provide explicit examples if so.
  • Include ARM template examples for Linux node types if applicable.
  • Balance the order of Windows and Linux references, mentioning both platforms equally where possible.
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-03-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page frequently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources, and does not provide equivalent Azure CLI or Linux/macOS command examples. While some mention of 'az resource' exists, PowerShell is emphasized and listed first, creating friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell cmdlet examples, especially for resource deletion and creation.
  • List both PowerShell and Azure CLI options side-by-side, or clarify which tools are cross-platform.
  • Explicitly state that Azure CLI is supported on Linux/macOS and provide links to relevant documentation.
  • Where possible, include ARM template usage examples that are platform-agnostic.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides several critical operational examples (such as disabling and removing nodes) exclusively using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning or providing equivalent commands or guidance for Linux environments. This creates friction for Linux users, who may not have access to PowerShell or may prefer bash/CLI alternatives. Additionally, the documentation does not clarify whether these commands are available cross-platform, nor does it offer Azure CLI or REST API equivalents where possible.
Recommendations
  • For each PowerShell example (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode), provide equivalent Azure CLI, REST API, or bash script examples suitable for Linux users.
  • Clearly indicate if certain commands are only available on Windows, and provide alternative approaches for Linux clusters.
  • Add a section or note summarizing cross-platform management options for Service Fabric clusters, including links to Linux-specific tools or documentation.
  • Where programmatic examples are given (e.g., C#), clarify if they are cross-platform and provide guidance for running them on Linux (e.g., using .NET Core).
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-03-05 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) parameters and workflows before those for SFCTL (cross-platform CLI), and provides more detailed parameter tables and examples for PowerShell/Visual Studio. SFCTL (the primary Linux/macOS tool) is covered later and less extensively. There are no explicit Linux/macOS examples or parity tables, and the PowerShell/Visual Studio sections dominate the page, which may cause friction for non-Windows users.
Recommendations
  • Reorganize the documentation to introduce SFCTL (cross-platform CLI) parameters and workflows before or alongside PowerShell/Visual Studio.
  • Provide equivalent examples for SFCTL commands wherever PowerShell examples are given.
  • Add a parity table or mapping between PowerShell/Visual Studio parameters and SFCTL/REST equivalents.
  • Explicitly mention that SFCTL is the recommended tool for Linux/macOS users at the top of the page.
  • Ensure that all parameter descriptions and workflows are equally detailed for SFCTL as for PowerShell/Visual Studio.
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-03-05 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 primarily using C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS command-line examples (such as Azure CLI or REST API) are provided. The PowerShell examples are consistently shown alongside C# code, with no mention of cross-platform alternatives or Linux-native tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tooling.
Recommendations
  • Add Azure CLI examples for each placement policy, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention REST API or ARM template approaches for configuring placement policies, which are platform-agnostic.
  • Explicitly note any limitations or differences for Linux clusters, if applicable.
  • Consider reordering examples to show cross-platform tools first or in parallel with PowerShell.
  • Clarify whether PowerShell examples are required or if alternatives exist for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides PowerShell and C# examples for configuring Service Fabric move cost, but does not include equivalent Linux shell (e.g., Bash/CLI) examples or mention cross-platform tools. PowerShell is a Windows-centric tool, and its exclusive use in command-line examples creates friction for Linux/macOS users.
Recommendations
  • Add Azure CLI or Bash examples for creating and updating Service Fabric services with move cost settings, if supported.
  • Clarify if PowerShell commands are available cross-platform (e.g., via PowerShell Core) or if they require Windows.
  • Explicitly mention any platform limitations for the provided tools.
  • Consider including REST API or ARM template examples, which are platform-agnostic.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page for the Azure Service Fabric application resource model demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any equivalent Azure CLI or Bash examples. The application packaging step is described using Visual Studio (a Windows-centric tool), and directory paths use Windows-style notation. There are no Linux/macOS-specific instructions or alternative workflows provided, even though Azure Resource Manager and Service Fabric support cross-platform tooling.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion alongside PowerShell commands.
  • Include instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, zip utilities) instead of only Visual Studio.
  • Show directory paths in both Windows and Linux/macOS formats.
  • Mention that all steps can be performed from Linux/macOS and provide relevant guidance.
  • Clarify that PowerShell is not required and that Azure CLI is supported on all platforms.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides security guidance for Azure Service Fabric clusters, referencing both Azure-hosted and standalone Windows clusters. However, it consistently presents Windows-specific instructions and links before any mention of Linux, and omits explicit examples or guidance for standalone Linux clusters. Certificate security is described as applicable to both platforms, but only Windows standalone cluster links are provided. Windows authentication (Kerberos) is discussed without Linux equivalents, and recommendations for standalone clusters are exclusively Windows-focused.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and any Linux-specific authentication options.
  • Clarify which security scenarios and features apply equally to Linux and Windows, and provide parity in examples and walkthroughs.
  • Where Windows-specific tools (e.g., Windows certificate services, MakeCert.exe) are mentioned, offer Linux alternatives (such as OpenSSL) and instructions.
  • Ensure that recommendations for standalone clusters include Linux scenarios, or clearly state if Linux standalone clusters are not supported.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page primarily uses Windows-based examples and references, such as referencing the Windows Server 2016 Container Sample, specifying Windows file paths (e.g., c:\VolumeTest\Data), and mentioning Windows-specific tools like 'winver' for OS build detection. There is minimal mention of Linux equivalents, and no Linux-specific manifest examples or guidance are provided, despite Service Fabric supporting Linux containers.
Recommendations
  • Add Linux-based container manifest examples, referencing the Linux sample repository if available.
  • Include Linux file path conventions (e.g., /mnt/VolumeTest/Data) alongside Windows paths in volume examples.
  • Mention Linux tools for OS build/version detection (e.g., 'cat /etc/os-release', 'uname -r') where 'winver' is referenced.
  • Clarify which features or manifest settings are cross-platform and which are Windows-only.
  • Provide links to Linux container documentation and samples for Service Fabric.
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-03-05 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 creating services and managing Service Fabric hosting models, but does not include equivalent CLI or Linux-native examples. Windows/PowerShell tools are referenced first and exclusively in command-line scenarios, creating friction for Linux/macOS users who may use Azure CLI or REST APIs. The documentation does not mention Linux-specific tools or provide guidance for non-Windows environments.
Recommendations
  • Add Azure CLI examples for service creation and management alongside PowerShell examples.
  • Explicitly mention REST API usage as a cross-platform option, and provide sample REST payloads or curl commands.
  • Clarify which tools are available on Linux/macOS and provide links or instructions for those platforms.
  • Consider including a section or note about Service Fabric support and tooling differences between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users who cannot use PowerShell natively.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Include REST API examples for health reporting and querying, which are platform-agnostic.
  • Mention cross-platform tools and patterns alongside PowerShell, not just after or instead of it.
  • Clarify in the example section that PowerShell is one option, and link to Linux/macOS alternatives.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell as the primary example for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and links to a PowerShell-based deployment guide as the next step. While .NET and REST are mentioned, PowerShell is presented first and most prominently. There are no explicit Linux/macOS CLI or tooling examples (such as Azure CLI or Bash), and no mention of cross-platform deployment tools or workflows.
Recommendations
  • Add examples and links for Linux/macOS users, such as using Azure CLI or Bash scripts to retrieve the cluster manifest and deploy applications.
  • Provide parity in deployment instructions, referencing cross-platform tools (e.g., Azure CLI, REST API usage with curl) alongside PowerShell.
  • Clarify which steps or tools are cross-platform and which are Windows-specific, to help users on non-Windows systems.
  • Include a note or section for Linux/macOS users outlining recommended workflows 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-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides a mix of JSON ARM template snippets and PowerShell scripts for certificate management in Service Fabric clusters. The only explicit scripting example for certificate enrollment uses PowerShell (with Az modules), and references to the Key Vault VM extension are Windows-specific. The documentation repeatedly refers to Windows tools and patterns (e.g., S-channel, Windows certificate store, Key Vault VM extension for Windows), and troubleshooting/FAQ sections only provide PowerShell-based automation examples. Linux equivalents (such as Bash/CLI, Key Vault VM extension for Linux, or Linux certificate store handling) are not mentioned or illustrated, and Windows-specific mechanisms are discussed before any cross-platform alternatives.
Recommendations
  • Add Azure CLI (az) or Bash scripting examples for certificate enrollment and management alongside PowerShell examples.
  • Explicitly document the Key Vault VM extension for Linux, including its configuration and limitations, or clarify if it is not supported.
  • Discuss Linux certificate store handling and how Service Fabric on Linux nodes interacts with certificates, including any differences in ACLing or provisioning.
  • Provide troubleshooting steps and automation examples for Linux/macOS environments.
  • Clearly indicate which steps or mechanisms are Windows-only, and offer Linux/macOS alternatives where possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions and provides examples focused on these Windows images. There is no mention of Linux container images, Linux-specific cleanup patterns, or parity for Linux container scenarios. The examples and descriptions prioritize Windows containers and tools, potentially creating friction for Linux/macOS users deploying Linux containers on Service Fabric.
Recommendations
  • Add examples and explanations for Linux container images (e.g., Ubuntu, Alpine) in the 'ContainerImagesToSkip' setting.
  • Clarify whether the cleanup and management features apply equally to Linux containers and Service Fabric clusters running on Linux VMs.
  • Include sample configurations and descriptions relevant to Linux container scenarios.
  • Explicitly state any limitations or differences between Windows and Linux container image management in Service Fabric.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides a comprehensive overview of X.509 certificate-based authentication in Service Fabric clusters, but there is evidence of Windows bias. Windows-specific tools and terminology (e.g., certificate stores like LocalMachine\My, Win32 CryptoAPI, CAPI2 logging, and error codes) are mentioned first or exclusively, with Linux equivalents only briefly referenced (e.g., 'var/lib/sfcerts'). Troubleshooting sections focus on Windows event logs and tools, with little guidance for Linux users. Examples and configuration snippets use Windows-centric paths and concepts.
Recommendations
  • Provide Linux-specific troubleshooting guidance, including log locations and relevant tools (e.g., journalctl, syslog, Service Fabric logs on Linux).
  • Expand on Linux certificate store handling, including how certificates are provisioned and managed in Linux clusters.
  • Include Linux/macOS equivalents for error codes and diagnostic steps.
  • Ensure that configuration examples and explanations mention Linux paths and behaviors alongside Windows, not as an afterthought.
  • Clarify any differences in certificate handling or validation between Windows and Linux nodes.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. However, it exclusively uses PowerShell for CLI-based scripting examples and does not provide equivalent Azure CLI (az) or bash examples, which are preferred by Linux/macOS users. There is no mention of cross-platform tools or scripting approaches outside of PowerShell, and PowerShell is presented as the only scripting option. This creates friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI (az) command examples for all operations currently shown only with PowerShell (add, remove, scale, configure placement properties, etc.).
  • Explicitly mention that PowerShell Core is cross-platform if PowerShell is required, and provide installation guidance for Linux/macOS if relevant.
  • Reorder sections or provide parallel examples so that Azure CLI and ARM template approaches are shown before or alongside PowerShell.
  • Clarify in notes when a feature or command is only available in PowerShell and provide workarounds or alternatives for Linux/macOS users where possible.
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-03-05 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page presents RunToCompletion semantics in Service Fabric, but all code examples and container references are Windows-specific (Windows Server containers, Windows NanoServer images, Windows command syntax). Querying deployment status is described only via PowerShell and C# APIs, with no mention of Linux CLI or Bash equivalents. There are no examples or guidance for Linux containers or non-Windows environments, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
  • Provide guidance for querying deployment status using Linux tools (such as Bash, sfctl CLI, or REST APIs).
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, include relevant code samples.
  • Present examples for both Windows and Linux environments, or explicitly state if RunToCompletion is Windows-only.
  • Mention Linux container compatibility considerations alongside Windows container version compatibility.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation contains evidence of Windows bias, notably in the warning that recommends using Visual Studio to open the ServiceFabricServiceModel.xsd file located at a Windows file path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd). Additionally, the ApplicationManifest.xml section references the ServiceFabric PowerShell module for creating service instances, without mentioning Linux equivalents or cross-platform CLI options. Windows tools and patterns are mentioned first and exclusively, with no Linux/macOS alternatives or parity guidance.
Recommendations
  • Provide instructions for validating XML schema ordering using cross-platform tools (e.g., VS Code, xmllint, or other editors) and note the location of the schema file on Linux/macOS installations.
  • Mention and provide examples for using Azure CLI or Service Fabric CLI (sfctl) for service management, especially for creating service instances, alongside PowerShell examples.
  • Clarify any differences in file paths or tooling between Windows and Linux/macOS environments.
  • Ensure that cross-platform development environments are referenced, not just Visual Studio and Windows-specific paths.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, 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 tools are referenced first and exclusively.
Recommendations
  • Add equivalent Azure CLI or REST API examples for bypassing Infrastructure Service, if available.
  • Clarify whether Service Fabric Explorer is accessible from Linux/macOS or provide alternative cross-platform management tools.
  • Include Linux/macOS-compatible instructions or note any limitations for non-Windows users.
  • Explicitly state if certain operations are Windows-only, to help set expectations 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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page provides migration guidance for Azure Service Fabric clusters to availability zone support. While the main content is platform-neutral and focuses on Azure Resource Manager templates, the step-by-step migration for nonmanaged clusters with Basic SKU load balancer and IP resources relies heavily on PowerShell scripts and cmdlets (e.g., New-AzureRmResourceGroupDeployment, Connect-ServiceFabricCluster, Disable-ServiceFabricNode, Remove-ServiceFabricNodeState, Remove-AzureRmVmss, Remove-AzureRmLoadBalancer, Remove-AzureRmPublicIpAddress, Set-AzureRmPublicIpAddress). These are Windows-centric tools, and no equivalent Azure CLI or Bash examples are provided. Additionally, the PowerShell examples are given exclusively and prominently, which may create friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell steps, especially for resource deployment, node disabling/removal, and DNS updates.
  • Add Bash script examples or reference how to perform these actions using Azure CLI on Linux/macOS.
  • Clarify which steps require Windows/PowerShell and offer alternatives or links for cross-platform users.
  • Mention that Service Fabric management can be done from Linux/macOS using Azure CLI or REST API where applicable.
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-05 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 on both Windows and Linux clusters, but there are several areas where Windows tools and patterns are mentioned first or exclusively. Windows-specific tools (such as Event Log/Event Viewer, ETW, Diagnostics Agent) are described in detail, while Linux equivalents (such as LTTng, Syslog) are referenced but not explained as thoroughly. Some example/tutorial links focus on .NET applications, which are more common on Windows, and Windows cluster monitoring is often described before Linux. Linux-specific configuration and examples are less prominent, and in some cases, only referenced via links rather than explained inline.
Recommendations
  • Provide Linux-specific examples and walkthroughs alongside Windows ones, especially for cluster monitoring and event collection.
  • Ensure that Linux tools (LTTng, Syslog, Azure Monitor agent configuration) are described with equal detail and clarity as Windows tools (ETW, Event Log, Diagnostics Agent).
  • Add explicit Linux sample queries, configuration steps, and troubleshooting tips where Windows instructions are given.
  • When referencing tutorials or examples, clarify whether they apply to both Windows and Linux, and provide Linux alternatives if not.
  • Avoid listing Windows tools or patterns first unless they are more widely used; consider parallel presentation or clear separation.
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-05 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 generally platform-agnostic manner, but several sections exhibit Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned without Linux equivalents or with Linux options listed after Windows. Some examples and links are Windows-centric, and disk encryption is only described for Windows clusters, with Linux disk encryption left as a TODO. Linux-specific guidance is missing or less prominent in several areas.
Recommendations
  • Add explicit Linux examples and guidance for disk encryption, including supported tools and Azure integration.
  • Ensure parity in describing how to run services under different accounts on Linux clusters, including relevant Linux user/group management and security practices.
  • Provide Linux-specific instructions or links for certificate management and container security, matching the detail given for Windows features like gMSA.
  • When listing options (e.g., container certificate access), mention Linux and Windows equally, not Windows first.
  • Clarify which features are Windows-only and provide alternative recommendations for Linux users where possible.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation frequently references PowerShell cmdlets and Windows-centric tooling (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) alongside .NET APIs and REST operations. PowerShell examples and cmdlets are often mentioned first or exclusively, with little to no explicit mention of Linux/macOS equivalents or cross-platform CLI usage (such as sfctl or Azure CLI). This creates friction for Linux/macOS users, who may need to infer or search for alternative commands.
Recommendations
  • Add explicit examples using sfctl (Service Fabric CLI), which is cross-platform, for each lifecycle operation (deploy, upgrade, remove, etc.).
  • Where PowerShell cmdlets are referenced, also provide equivalent Azure CLI or sfctl commands, and mention their applicability to Linux/macOS.
  • Reorder examples so that cross-platform tools (REST API, sfctl, Azure CLI) are presented before or alongside Windows/PowerShell examples.
  • Clarify which tools are Windows-only and which are cross-platform, to help users select the right approach for their environment.
  • Include a section or table summarizing tool parity for Windows, Linux, and macOS users.
GitHub Create Pull Request
← Previous Page 17 of 99 Next →