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 1851-1875 of 2475 flagged pages
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell examples are presented first and in greater detail, which may suggest a Windows-centric approach. While the CLI commands are cross-platform, the initial emphasis on PowerShell could create friction for Linux/macOS users.
Recommendations
  • Present CLI (sfctl) examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Explicitly mention that sfctl is supported on Linux/macOS and provide installation links or instructions.
  • Clarify that PowerShell examples are primarily for Windows users, and encourage Linux/macOS users to use sfctl.
  • Consider adding a short section or note highlighting platform parity and best practices for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Overview of Azure and standalone Service Fabric clusters ...icles/service-fabric/service-fabric-deploy-anywhere.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation discusses Service Fabric clusters on both Windows Server and Linux, but the standalone cluster feature is only available on Windows. Linux is mentioned as a supported OS for Service Fabric clusters, but standalone clusters are explicitly unavailable on Linux. There are no Linux-specific examples, tools, or operational guidance provided, and the documentation does not offer alternative solutions or workarounds for Linux users seeking standalone deployments.
Recommendations
  • Clearly state early in the document that standalone clusters are Windows-only, and provide guidance or alternatives for Linux users.
  • Add a section summarizing what Linux users can and cannot do, with links to relevant Linux documentation.
  • If possible, provide information on Azure-based Linux clusters and clarify the limitations for standalone Linux deployments.
  • Ensure that Linux users are not left without actionable next steps by referencing the 'Differences between Service Fabric on Linux and Windows' page more prominently.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page on Azure Service Fabric Events predominantly references Windows-centric logging and monitoring tools (ETW/Windows Event logs, Windows Azure diagnostics agent) and does not provide equivalent Linux examples or mention Linux-native logging mechanisms. The initial and primary guidance is focused on Windows approaches, with no explicit instructions for accessing or monitoring Service Fabric events on Linux clusters.
Recommendations
  • Include instructions or references for accessing Service Fabric events on Linux clusters, such as using syslog, journald, or other Linux-native logging solutions.
  • Clarify whether the described event logging mechanisms (ETW, Windows Event logs, Windows Azure diagnostics agent) apply only to Windows-based clusters, and provide parity guidance for Linux-based clusters if supported.
  • Add examples or links to documentation for monitoring Service Fabric events on Linux, including integration with Azure Monitor from Linux nodes.
  • Explicitly state any limitations or differences in event access between Windows and Linux clusters to help users understand platform-specific considerations.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Azure Service Fabric DNS service demonstrates several Windows biases. PowerShell is the only CLI example provided for setting DNS names, with no Linux CLI (e.g., Bash, Azure CLI) equivalent. Visual Studio is mentioned as the default editor for ApplicationManifest.xml, and there is no guidance for Linux users on how to perform these tasks. The limitations section notes reduced Linux support, but examples and instructions are generally Windows-centric or omit Linux-specific workflows.
Recommendations
  • Add equivalent Linux/Bash/Azure CLI examples for tasks currently shown only with PowerShell.
  • Provide instructions for editing ApplicationManifest.xml using common Linux editors (e.g., vim, nano) and clarify how Linux users can deploy and configure services.
  • Explicitly document any Linux-specific steps or differences, especially where portal functionality is unavailable.
  • Where features are Windows-only, clearly mark those sections and provide alternative guidance for Linux users where possible.
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-02-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 a detailed conceptual overview of Service Fabric health monitoring, which is a cross-platform feature. However, the only concrete example of reporting and evaluating health uses PowerShell cmdlets, which are Windows-centric. There are no equivalent Linux/bash/REST examples, nor is there mention of Linux tools or workflows for health reporting. The documentation also references Windows PowerShell tools as the primary method for interacting with Service Fabric health, creating friction for Linux/macOS users.
Recommendations
  • Add examples using REST API for health reporting and querying, which are platform-agnostic.
  • Include sample code snippets for reporting health using the Service Fabric SDK in cross-platform languages (e.g., Python, .NET Core, Java).
  • Provide Linux/bash CLI examples (e.g., using sfctl or curl) alongside PowerShell examples.
  • Explicitly mention Linux/macOS compatibility and tools where relevant, and link to cross-platform tooling documentation.
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-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 command-line examples only using PowerShell cmdlets (e.g., New-ServiceFabricService), with no equivalent examples for Linux/macOS users (such as Azure CLI, Bash, or REST via curl). All operational instructions reference PowerShell modules, and there is no mention of Linux-native tools or cross-platform workflows. This creates friction for non-Windows users, who must translate or research equivalent commands themselves.
Recommendations
  • Add Azure CLI examples for all service creation and management tasks alongside PowerShell examples.
  • Include REST API usage examples with curl or HTTPie to demonstrate cross-platform approaches.
  • Explicitly mention cross-platform tooling support and link to relevant documentation for Linux/macOS users.
  • Clarify in each example whether the command is Windows-only, and provide alternatives where possible.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-02-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 demonstrates a moderate Windows bias by prioritizing PowerShell and Visual Studio workflows, mentioning Windows-centric tools and scripts first, and lacking explicit Linux/macOS command examples for key tasks such as application creation and deployment. While sfctl and Jenkins are mentioned, the examples and guidance are primarily oriented toward Windows users.
Recommendations
  • Add explicit Linux/macOS command-line examples for application creation and parameter passing using sfctl and shell scripts.
  • Provide parity in deployment workflow examples, such as showing how to use Bash scripts or Linux-native CI/CD tools alongside PowerShell and Visual Studio.
  • Ensure that references to tools like Replace Tokens include Linux-compatible alternatives or usage instructions.
  • Clarify which steps or tools are cross-platform and which are Windows-specific, to help users on non-Windows systems navigate the documentation more easily.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides manifest examples for Service Fabric applications, but several elements and examples show a bias toward Windows environments. The startup script is specified as a .bat file (Setup.bat), which is a Windows batch script, and the service executables are .exe files, both of which are Windows-specific. There are no Linux-equivalent examples (such as .sh scripts or ELF binaries), nor is there guidance for Linux users on how to adapt these manifest entries for Linux clusters. Additionally, references to running services as NETWORKSERVICE and local admin accounts are Windows-centric, with no mention of Linux service accounts or equivalents.
Recommendations
  • Provide parallel examples using Linux-compatible scripts (e.g., Setup.sh) and service executables (e.g., ELF binaries) in the manifest.
  • Add notes or sections explaining how to configure service manifests for Linux clusters, including differences in user accounts, permissions, and startup scripts.
  • Clarify which manifest elements are cross-platform and which require platform-specific configuration, ideally linking to Linux-specific documentation where available.
  • Where Windows-specific accounts (e.g., NETWORKSERVICE) are mentioned, provide Linux equivalents or note their absence.
  • Ensure that references to PowerShell or Windows tools are balanced with Linux CLI or scripting alternatives if relevant.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-02-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 'Networking patterns for Azure Service Fabric' demonstrates a notable Windows bias. All command-line deployment examples use PowerShell cmdlets (New-AzResourceGroup, New-AzResourceGroupDeployment, Get-AzPublicIpAddress), with no mention of Azure CLI or Bash equivalents. Additionally, some example outputs and instructions reference Windows-specific tools (e.g., RDP, Windows command prompt ping syntax), and the use of Windows file paths (C:\SFSamples\...). There are no Linux/macOS-specific instructions or examples, and the documentation assumes a Windows environment for both authoring and cluster access.
Recommendations
  • Provide equivalent Azure CLI (az ...) commands alongside PowerShell examples for all deployment steps.
  • Include Bash shell examples and Linux/macOS file path formats where relevant.
  • When referencing remote access, mention SSH as an alternative to RDP for Linux-based VMs.
  • Avoid using only Windows command prompt syntax (e.g., ping); provide cross-platform alternatives.
  • Clarify that the templates and instructions are platform-agnostic, and highlight any steps that are Windows-specific.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Scanned: 2026-02-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 detailed PowerShell examples for health reporting and cluster connection, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or cross-platform scripts). PowerShell is presented as the primary scripting interface, and Windows-style command prompts are shown first. REST API usage is mentioned but not demonstrated with concrete examples, and there is no guidance for Linux-native tools or workflows.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for Linux/macOS users, especially for connecting to clusters and sending health reports.
  • Clarify whether PowerShell Core (cross-platform) is supported, and if so, provide usage notes for Linux/macOS.
  • Provide REST API example requests using curl or similar Linux-native tools, including sample payloads and authentication guidance.
  • Explicitly mention any platform limitations (e.g., if PowerShell cmdlets are Windows-only) and direct Linux/macOS users to supported alternatives.
  • Reorder examples so that cross-platform or REST approaches are presented before or alongside Windows/PowerShell-specific instructions.
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-02-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 repeatedly references PowerShell and Visual Studio for deployment and configuration tasks, which are primarily Windows-centric tools. Examples and next steps focus on PowerShell, with no mention of Linux/macOS equivalents (such as Azure CLI, Bash, or cross-platform SDKs). There is no guidance for Linux/macOS users on how to retrieve or set the ImageStoreConnectionString, nor are alternative workflows provided.
Recommendations
  • Add examples using Azure CLI, Bash, or cross-platform SDKs for retrieving and setting the ImageStoreConnectionString.
  • Include instructions for deploying applications from Linux/macOS environments, highlighting any differences or limitations.
  • Reference cross-platform tools and workflows alongside PowerShell and Visual Studio, ensuring parity in documentation.
  • Clarify whether any steps are Windows-only, and provide alternatives or workarounds for non-Windows users where possible.
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-02-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias: it references the Windows Server 2016 Container Sample as the basis for its examples, and in the manifest XML and explanatory text, Windows-specific tools and patterns (such as 'winver' to get the OS build version and Windows file paths like 'c:\VolumeTest\Data') are mentioned before or instead of Linux equivalents. However, the documentation does mention Linux in some explanatory comments (e.g., PEM files for certificates on Linux), and the manifest schema itself is not inherently Windows-only.
Recommendations
  • Provide Linux-based example manifests or explicitly note Linux compatibility where applicable.
  • When referencing OS build version detection (e.g., for image overrides), include Linux commands (such as 'uname -r') alongside 'winver'.
  • Use cross-platform file paths in examples, or show both Windows and Linux path formats.
  • Clarify in the introduction if the examples are Windows-specific, and if so, link to Linux equivalents if available.
  • Ensure that referenced sample repositories or links include both Windows and Linux samples, or clearly indicate their OS focus.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions both Windows and Linux support for Service Fabric, but Windows development tools (Visual Studio, PowerShell, .NET SDK) are described first and in more detail, while Linux equivalents (Eclipse, Yeoman, Java SDK) are mentioned briefly. There are no example commands or workflows shown for Linux, and the quickstart link points to a .NET (Windows-centric) guide, with no immediate Linux alternative provided.
Recommendations
  • Provide parallel quickstart links for both Windows (.NET) and Linux (Java/.NET Core) development.
  • Include example workflows or commands for Linux environments, such as using Yeoman or Eclipse.
  • Balance the description of development tools by giving equal detail to Linux options (e.g., how to set up a local cluster, deploy, and manage applications on Linux).
  • Consider listing Linux development options before or alongside Windows options in relevant sections.
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-05 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 Replica soft delete in Service Fabric predominantly references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) for administrative operations and API usage. There are no examples or instructions for Linux/macOS users, such as using Service Fabric CLI (sfctl) or REST APIs, nor is there mention of equivalent tooling or workflows outside of PowerShell. This creates friction for users managing Service Fabric clusters on Linux or from non-Windows environments.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and commonly used on Linux/macOS.
  • Document REST API endpoints or FabricClient SDK usage for replica management, with code snippets in languages/platforms supported on Linux/macOS.
  • Clarify whether the PowerShell cmdlets are required, or if all functionality is available via CLI/SDK/REST for Linux users.
  • Include a note or section explicitly addressing Linux/macOS cluster management workflows for replica soft delete.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page focuses on defining service configuration in StartupServices.xml for Service Fabric applications, with a strong emphasis on Visual Studio workflows and PowerShell usage. All examples and workflows are described in the context of Visual Studio, a Windows-only tool, and PowerShell is referenced as the method for creating service instances. There are no Linux/macOS equivalents or alternative instructions provided, and the documentation does not mention cross-platform tooling or workflows.
Recommendations
  • Add guidance for Linux/macOS users, including how to manage Service Fabric application configuration and deployment using cross-platform tools (e.g., Azure CLI, Service Fabric CLI, or REST APIs).
  • Provide examples for deploying and managing Service Fabric applications outside of Visual Studio, such as using command-line tools available on Linux/macOS.
  • Clarify which features or workflows are Windows/Visual Studio-specific and offer alternative instructions for non-Windows environments where possible.
  • Include references to cross-platform documentation or tooling for Service Fabric application development and deployment.
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-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 several examples and deployment instructions using Windows-centric tools and patterns, notably PowerShell (e.g., New-ServiceFabricApplication) and references to Windows file paths (e.g., C:\Program Files\...). While Linux is mentioned briefly (regarding certificate store location), most practical deployment examples and tooling references are Windows-first or Windows-only, with no Linux CLI equivalents or parity in example ordering.
Recommendations
  • Provide equivalent Linux deployment examples using Service Fabric CLI (sfctl) or bash scripts alongside PowerShell examples.
  • Mention Linux file paths and configuration locations in parallel with Windows paths wherever relevant.
  • Clarify which commands and tooling are cross-platform, and link to Linux/macOS-specific documentation where available.
  • Order examples so that Linux and Windows are presented with equal prominence, or explicitly note platform-specific steps.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is generally cross-platform and describes Service Fabric concepts applicable to both Windows and Linux. However, there is a subtle Windows bias in the 'Node' section, where Windows-specific tools and processes (auto-start Windows service, FabricHost.exe) are mentioned first and in detail, while Linux equivalents are not described. The terminology and examples tend to reference Windows processes and executable types (EXE/DLL) before mentioning Linux support. There are no explicit Linux/Unix examples or references to Linux-specific tools or patterns.
Recommendations
  • Add parallel descriptions for Linux nodes, including how Service Fabric is started and managed on Linux (e.g., systemd services, process names).
  • When referencing executables, clarify that on Linux, these may be ELF binaries and not EXE/DLL files.
  • Provide examples or notes for Linux-specific deployment and management patterns where they differ from Windows.
  • Ensure that mentions of Windows services and processes are balanced with Linux equivalents, or explicitly state when a concept is Windows-only.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation predominantly references PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources, with no mention of Linux/macOS CLI equivalents or examples. While az resource (Azure CLI) is briefly mentioned for application deletion, most guidance and links focus on PowerShell, which is traditionally Windows-centric. There are no explicit Linux/macOS instructions or examples, which may create friction for non-Windows users.
Recommendations
  • Include Azure CLI examples for all operations (e.g., creating/deleting applications, services, scaling) alongside PowerShell cmdlets.
  • Clarify which commands are cross-platform and which are Windows-specific.
  • Add notes or links for installing and using Azure CLI on Linux/macOS.
  • Where PowerShell is required, mention PowerShell Core's cross-platform support and provide installation guidance for Linux/macOS.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page on X.509 Certificate-based Authentication in a Service Fabric Cluster exhibits a moderate Windows bias. While the conceptual explanations are platform-neutral, practical details, troubleshooting, and examples often reference Windows-specific tools, APIs, and patterns (e.g., certificate stores like LocalMachine\My, Win32 CryptoAPI, CAPI1/CNG providers, and event log paths). Linux equivalents are mentioned only briefly or as afterthoughts, and there are no concrete Linux/macOS command-line or troubleshooting examples. This may create friction for Linux users, especially when diagnosing issues or configuring certificates.
Recommendations
  • Include explicit Linux/macOS equivalents for all Windows-specific instructions, such as certificate store locations, certificate management commands, and log file paths.
  • Provide Linux/macOS command-line examples for common tasks (e.g., using openssl, certutil, or other cross-platform tools to manage certificates).
  • Clarify how Service Fabric on Linux handles certificate discovery, validation, and storage, especially where it differs from Windows (e.g., /var/lib/sfcerts vs. LocalMachine\My).
  • Add troubleshooting steps and error messages relevant to Linux environments, including where to find logs and how to interpret common errors.
  • When referencing Windows APIs or tools (e.g., Win32 CryptoAPI, CAPI1), provide context or alternatives for Linux users, or note if certain features are 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-04 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 demonstrates a notable Windows bias. All command-line examples use PowerShell cmdlets, with no mention of Linux/macOS equivalents (such as Service Fabric CLI or REST API usage). Windows/PowerShell tools are referenced exclusively and repeatedly, and the structure of the documentation assumes familiarity with PowerShell workflows. There are no examples or guidance for users managing Service Fabric clusters from Linux or macOS environments.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Where PowerShell cmdlets are referenced, include a note or section on how to perform the same operations using sfctl or REST API.
  • Clarify which features or commands are available cross-platform and which are Windows-only, to help users on non-Windows systems.
  • Provide links to Service Fabric CLI documentation alongside PowerShell references.
  • Reorder or balance examples so that Linux/macOS workflows are not consistently presented after Windows/PowerShell ones.
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-04 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, requiring the Microsoft.ServiceFabric.Powershell.Http module and providing all CLI examples in PowerShell syntax. There are no examples or guidance for performing on-demand backups using cross-platform tools (such as Azure CLI, curl, or bash scripts), nor is there mention of Linux/macOS-compatible alternatives for connecting to Service Fabric clusters or invoking REST APIs. This creates friction for Linux/macOS users who may not have access to PowerShell or the required modules.
Recommendations
  • Provide equivalent examples using cross-platform tools such as Azure CLI, curl, or bash scripts for invoking REST APIs.
  • Document how to authenticate and connect to Service Fabric clusters from Linux/macOS environments, including certificate handling.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available and supported on PowerShell Core (pwsh) on Linux/macOS, or suggest alternatives if not.
  • Include REST API request examples using curl or HTTPie, with sample JSON payloads and authentication details.
  • Add a note or section specifically addressing Linux/macOS users and their options for performing on-demand backups.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows and Linux configuration examples for standalone Service Fabric clusters (via ClusterManifest.xml and ClusterConfig.json), but consistently presents Windows-specific XML examples first and uses Windows terminology (e.g., <WindowsServer> infrastructure). Additionally, code samples for interacting with Service Fabric services are given in C# and PowerShell, with no Linux-native CLI or Bash examples. PowerShell is a Windows-centric tool, and its exclusive use for scripting examples may create friction for Linux/macOS users.
Recommendations
  • Add explicit Linux configuration examples for Service Fabric clusters, such as using <Linux> infrastructure blocks in ClusterManifest.xml.
  • Provide Bash or Azure CLI examples for service creation and updates, alongside PowerShell, to improve parity for Linux/macOS users.
  • Clarify in configuration sections that both Windows and Linux clusters are supported, and link to platform-specific setup guides if available.
  • When presenting code/configuration samples, alternate or parallelize Windows and Linux examples, rather than always listing Windows first.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides command-line examples exclusively using PowerShell, which is primarily a Windows tool. There are no equivalent examples for Linux/macOS users, such as using Bash, Azure CLI, or REST API calls. The PowerShell examples are presented before C# API examples, further reinforcing a Windows-first approach. This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add examples using Azure CLI or REST API for managing node tags and service tag requirements, which are cross-platform.
  • Explicitly mention whether PowerShell Core (cross-platform) is supported, and provide Bash or shell script equivalents if possible.
  • Clarify any platform limitations for Service Fabric management tools and link to relevant Linux/macOS documentation.
  • Reorder examples so that cross-platform methods (REST API, Azure CLI) are presented before or alongside PowerShell.
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-02-04 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 detailed conceptual overview of Service Fabric health monitoring, which is a cross-platform feature. However, the only concrete example for reporting and evaluating health uses PowerShell cmdlets, which are Windows-centric and not available natively on Linux clusters. There are no equivalent examples for Linux/macOS users (e.g., using REST API, Azure CLI, or SDKs). The documentation also references Windows tools (PowerShell) exclusively for practical usage, creating friction for non-Windows users.
Recommendations
  • Add equivalent examples for Linux/macOS users, such as using the Service Fabric REST API, Azure CLI, or SDKs (C#, Python, etc.) to report and query health.
  • Clearly indicate that PowerShell is Windows-only and provide links or guidance for Linux/macOS alternatives.
  • Where possible, show both Windows (PowerShell) and cross-platform (REST/CLI/SDK) examples side-by-side.
  • Reference cross-platform tools and patterns before or alongside Windows-specific ones.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Azure Service Fabric DNS service exhibits moderate Windows bias. While it acknowledges Linux support, most operational examples (such as setting DNS names) are provided only for Windows-centric tools like PowerShell and Visual Studio. There are no Linux-specific command-line examples (e.g., using CLI, Bash, or cross-platform tools), and the workflow for Linux clusters is described as more limited, with enabling DNS service not possible via the Azure portal. Windows tools and patterns (PowerShell, ApplicationManifest.xml in Visual Studio) are mentioned first and exclusively, with no parity for Linux-native workflows.
Recommendations
  • Provide Linux-specific examples for setting DNS names, such as using Azure CLI, Bash scripts, or editing manifests with Linux-native editors.
  • Clarify how Linux users can deploy and manage DNS service, especially for process-based services, and explicitly document any workarounds or alternative workflows.
  • Add guidance for enabling DNS service on Linux clusters outside the portal, with step-by-step instructions.
  • Include notes or tables summarizing feature parity and limitations between Windows and Linux clusters.
  • Where PowerShell is used, offer equivalent Azure CLI or REST API examples for cross-platform accessibility.
GitHub Create Pull Request
← Previous Page 75 of 99 Next →