Service Fabric

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

Bias Trend Over Time

Pages with Bias Issues

718 issues found
Showing 601-625 of 718 flagged pages
Service Fabric Deploy a cluster across Availability Zones ...vice-fabric/service-fabric-cross-availability-zones.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias, especially in the migration section, where all operational examples are provided exclusively in PowerShell, referencing Windows-centric tools and patterns (e.g., disabling nodes, removing resources, updating DNS). There is no mention of equivalent Linux/macOS CLI commands (such as Azure CLI or bash scripts), and the only sample template link for Linux (Ubuntu) does not include operational steps. Windows/PowerShell instructions are presented first and exclusively for critical migration tasks, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Azure CLI (az) or bash script examples for all operational steps, especially in migration and resource management sections.
  • Explicitly mention cross-platform tooling options (e.g., Azure CLI, REST API) alongside PowerShell.
  • Add a Linux/macOS migration walkthrough, including disabling nodes, removing resources, and updating DNS using non-Windows tools.
  • Ensure sample templates and code snippets are available for both Windows and Linux deployments, and reference them equally.
  • Where PowerShell is used, add a note or table mapping each command to its Azure CLI equivalent.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation discusses Service Fabric clusters on both Windows Server and Linux, but it highlights that standalone clusters are not available on Linux. There are no Linux-specific examples, tools, or operational guidance, and the text generally references Windows Server first. This creates a bias toward Windows environments, especially for standalone deployments.
Recommendations
  • Explicitly state the limitations and alternatives for Linux users regarding standalone clusters.
  • Provide Linux-specific guidance or links for deploying Service Fabric clusters in supported scenarios.
  • Include operational examples or references for Linux environments where Service Fabric is supported.
  • Balance the order of mention between Windows and Linux to avoid implicit prioritization.
GitHub Create Pull Request
Service Fabric Deploy an existing executable to Azure Service Fabric ...s/service-fabric/service-fabric-deploy-existing-app.md
Medium Priority View Details →
Scanned: 2026-01-12 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 demonstrates a notable Windows bias. Windows tooling (Visual Studio, PowerShell) is presented first and in greater detail, with step-by-step instructions and explanations. Linux alternatives (Yeoman, manual packaging) are mentioned after Windows tools, with less detail and fewer examples. The deployment section only provides a PowerShell script for Windows, with no equivalent Bash or CLI example for Linux. Batch files and Windows-specific patterns (e.g., .cmd scripts) are referenced in examples, while Linux shell scripts are not. This creates friction for Linux/macOS users who may struggle to adapt Windows-centric instructions.
Recommendations
  • Provide Bash or Azure CLI deployment examples for Linux/macOS users alongside the PowerShell script.
  • Include Linux shell script examples (e.g., .sh) in the SetupEntrypoint section, not just .cmd batch files.
  • Expand the Yeoman section with more detailed, step-by-step instructions and screenshots, matching the depth of the Visual Studio walkthrough.
  • Present Windows and Linux tooling in parallel, or alternate which is shown first, to avoid implicit prioritization.
  • Add troubleshooting and verification steps for Linux/macOS environments, similar to those shown for Windows.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Diagnose Common Scenarios ...-fabric/service-fabric-diagnostics-common-scenarios.md
Medium Priority View Details →
Scanned: 2026-01-12 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 demonstrates mild Windows bias, particularly in the monitoring and diagnostics sections. Windows terminology and examples (such as '.NET CLR Memory', 'Windows Performance Counters') are presented first and in detail, while Linux equivalents are mentioned only briefly or parenthetically. There are no explicit Linux command-line or tool examples, and most counter examples are Windows-specific. The documentation assumes familiarity with Windows-centric tools and patterns, with Linux support referenced but not illustrated.
Recommendations
  • Provide explicit Linux examples for performance counters, including sample Linux counter names and formats.
  • Include screenshots or walkthroughs of the Linux-specific UI paths (e.g., 'Data > Linux Performance Counters').
  • Add sample queries and alert rules for Linux-specific metrics (such as CPU, memory, and disk counters).
  • Clarify any differences in setup or troubleshooting steps for Linux clusters.
  • Ensure parity in diagnostic tool recommendations, mentioning Linux-compatible agents and solutions where relevant.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Event Aggregation with EventFlow ...service-fabric-diagnostics-event-aggregation-eventflow.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows development tools (Visual Studio, Solution Explorer, Debug output window) and omitting Linux/macOS equivalents or instructions. All setup and verification steps assume a Windows environment, with no mention of cross-platform alternatives (e.g., dotnet CLI, VS Code, Linux file paths, or terminal commands). This creates friction for developers working on Linux or macOS, who may not use Visual Studio or have access to Windows-specific UI elements.
Recommendations
  • Add instructions for installing EventFlow NuGet packages using the dotnet CLI (e.g., 'dotnet add package') for Linux/macOS users.
  • Include guidance for editing configuration files and setting build actions outside of Visual Studio, such as using VS Code or command-line tools.
  • Provide verification steps that work on Linux/macOS, such as viewing logs in the terminal or using cross-platform IDEs.
  • Mention file paths and project structure conventions for non-Windows environments.
  • Explicitly state that the instructions apply to all platforms, and highlight any platform-specific considerations.
GitHub Create Pull Request
Service Fabric Event Aggregation with Microsoft Azure Diagnostics ...ic/service-fabric-diagnostics-event-aggregation-wad.md
Medium Priority View Details →
Scanned: 2026-01-12 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 exhibits a notable Windows bias. It focuses almost exclusively on the Windows Azure Diagnostics (WAD) extension, with all configuration examples, templates, and code snippets tailored to Windows clusters. Windows-specific tools (PowerShell, Visual Studio Diagnostic Event Viewer, ETW logs) are referenced throughout, and all step-by-step instructions use Windows terminology and patterns. There is no coverage of Linux diagnostics (LAD) or Linux-specific configuration, nor any Linux command-line examples. Although a selector for Linux documentation is present at the top, this page itself is Windows-centric and does not provide Linux parity.
Recommendations
  • Add equivalent Linux (LAD) configuration examples and templates directly to this page, or clearly link to them in each relevant section.
  • Include Linux command-line instructions (e.g., Azure CLI, Bash) alongside PowerShell examples.
  • Reference Linux-compatible tools for viewing and analyzing logs (e.g., less, grep, Kibana, etc.), not just Visual Studio.
  • Clarify which instructions and templates are Windows-only, and provide guidance for Linux clusters where steps differ.
  • Ensure that all major sections (deployment, configuration, log analysis) have Linux-specific guidance or links.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric logging mechanisms (ETW/Windows Event logs), mentioning the Windows Azure diagnostics agent, and omitting explicit instructions or examples for accessing Service Fabric events on Linux clusters. There are no Linux-specific event access patterns or tools discussed, nor is parity established in example order or detail.
Recommendations
  • Add explicit instructions and examples for accessing Service Fabric events on Linux clusters, such as using Linux diagnostics agents or syslog integration.
  • Mention Linux-compatible monitoring tools and logging channels (e.g., journald, syslog) alongside Windows Event logs.
  • Clarify whether the EventStore REST APIs and Service Fabric Client Library are fully cross-platform, and provide usage examples on Linux/macOS.
  • Ensure documentation sections reference both Windows and Linux approaches equally, ideally presenting cross-platform methods first.
GitHub Create Pull Request
Service Fabric Set up monitoring with Azure Monitor logs ...service-fabric/service-fabric-diagnostics-oms-setup.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a notable Windows bias: Windows clusters and tools (such as PowerShell and WAD) are referenced first and in detail, with Linux-specific instructions relegated to external links. All code examples use PowerShell, with no Linux CLI or Bash equivalents. The Service Fabric Analytics solution is stated to be Windows-only, and Linux users are repeatedly redirected elsewhere, with no direct guidance or parity in examples.
Recommendations
  • Include direct Linux/Bash/CLI examples alongside PowerShell commands for deploying and configuring Azure Monitor logs.
  • Provide a step-by-step Linux workflow for connecting clusters to Log Analytics, not just a link to another article.
  • Clarify which features are Windows-only and offer Linux alternatives or workarounds in the same document.
  • Present instructions for both platforms side-by-side or clearly label platform-specific sections.
  • Reference Linux tools (e.g., OMSAgent, syslog integration) with equal prominence and detail as Windows tools (WAD, PowerShell).
GitHub Create Pull Request
Service Fabric Monitor Linux cluster events in Azure Service Fabric ...ervice-fabric/service-fabric-diagnostics-oms-syslog.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is focused on monitoring Service Fabric events for Linux clusters via Syslog, but the configuration examples and terminology reference Windows-oriented tools and patterns (e.g., 'AzureWinFabCsv', 'AzureWinFabCrashDump', 'AzureTableWinFabEtwQueryable', 'WinFabLttProducer') before or alongside the Linux-specific SyslogConsumer. The naming and example values in configuration are Windows-centric, which may create confusion for Linux users. However, the core instructions are Linux-relevant and do not prevent Linux users from completing the task.
Recommendations
  • Provide Linux-specific configuration examples that omit or clarify the purpose of Windows-related consumer instances.
  • Explain the relevance (or irrelevance) of Windows-named parameters for Linux clusters.
  • List Linux-relevant tools and patterns first, and clarify which configuration items are required for Linux clusters only.
  • Add a note to explicitly distinguish between Windows and Linux configuration sections.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates several Windows biases. Windows clusters are described as fully supported, while Linux support is called out as limited and with restrictions. Examples for setting DNS names via PowerShell are provided, but there are no equivalent Linux CLI or Bash examples. The ApplicationManifest.xml example references Visual Studio, a Windows-centric tool. Enabling DNS service via the Azure portal is described as available for Windows but not for Linux clusters, with no Linux-specific alternatives shown first or in detail. The limitations section reiterates Linux restrictions, but does not offer Linux workarounds or parity guidance.
Recommendations
  • Provide Linux-specific CLI examples (e.g., Bash, Azure CLI, or REST API) for tasks currently shown only with PowerShell.
  • Include instructions for enabling DNS service on Linux clusters using supported methods (e.g., ARM templates, CLI), with step-by-step guidance.
  • Offer guidance for editing ApplicationManifest.xml using cross-platform editors and tools, not just Visual Studio.
  • Present Linux alternatives or parity information alongside Windows instructions, rather than only listing limitations.
  • Add troubleshooting and workaround sections specifically for Linux users where features are limited.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell-based deployment instructions first and in greater detail, with no equivalent Linux/macOS shell or script examples for the PowerShell commands. The CLI (sfctl) section is present but comes after the PowerShell examples, and the documentation refers to Windows-specific features (e.g., 'Isolation (only for Windows)'). There is no mention of Linux/macOS-specific guidance, nor are there bash or shell script equivalents for the PowerShell commands.
Recommendations
  • Provide Linux/macOS shell (bash/zsh) equivalents for all PowerShell commands, especially for deployment, status checks, upgrades, and rollbacks.
  • Present CLI (sfctl) instructions before or alongside PowerShell examples to avoid Windows-first ordering.
  • Explicitly mention platform compatibility for each tool and command, clarifying which steps work on Linux/macOS.
  • Add notes or sections for Linux/macOS users, including any prerequisites or differences in setup.
  • Where Windows-only features are mentioned (e.g., Isolation), clarify alternatives or limitations for Linux/macOS.
GitHub Create Pull Request
Service Fabric Enable disk encryption for Linux clusters ...c/service-fabric-enable-azure-disk-encryption-linux.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page for enabling disk encryption for Linux clusters in Azure Service Fabric exhibits a moderate Windows bias. PowerShell commands are presented first and in greater detail throughout, with explicit references to Windows-style paths (e.g., c:\certificates) and reliance on PowerShell-specific tooling. Although Azure CLI examples are provided for most steps, PowerShell is consistently prioritized and some instructions (such as certificate handling) are more Windows-centric. There is minimal mention of Linux-native tools or shell scripting, and the use of Windows file paths in Linux contexts may confuse non-Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
  • Replace Windows-style file paths (e.g., c:\certificates) with Linux-style paths (e.g., /home/user/certificates) in Linux-specific documentation.
  • Include bash shell scripting examples for certificate password handling and file manipulation.
  • Clarify any steps that require PowerShell, and provide Linux-native alternatives or note platform limitations.
  • Add explicit notes or sections for Linux/macOS users, highlighting differences in environment setup and command usage.
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-01-12 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, but the only concrete example for reporting and querying health uses Windows PowerShell cmdlets. There are no equivalent examples for Linux/macOS users (e.g., using Bash, REST API, or cross-platform CLI tools). The documentation also references PowerShell as a primary mechanism for interacting with Service Fabric health, without mentioning Linux-compatible alternatives or providing parity in example coverage.
Recommendations
  • Add equivalent health reporting and querying examples using Bash and the Service Fabric CLI (sfctl), which is cross-platform.
  • Include REST API examples for health reporting and querying, as these are platform-agnostic.
  • Explicitly mention Linux/macOS support and tools (e.g., sfctl, REST) alongside PowerShell in all sections discussing health reporting.
  • Reorder examples or provide both Windows and Linux/macOS examples side-by-side to ensure parity.
  • Link to documentation pages that describe Linux/macOS usage of Service Fabric health features.
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-01-12 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 Windows bias by referencing PowerShell as the primary tool for interacting with Service Fabric clusters, mentioning Visual Studio for publishing (a Windows-centric IDE), and linking to PowerShell-based deployment guides. There are no explicit Linux or macOS command-line examples, nor are cross-platform tools like Azure CLI or Bash scripts mentioned. The documentation assumes a Windows development environment and does not provide guidance for Linux/macOS users.
Recommendations
  • Add examples using Azure CLI or REST API for cluster manifest retrieval and application deployment, which are cross-platform.
  • Include instructions for deploying applications from Linux/macOS environments, possibly with Bash or Python scripts.
  • Reference cross-platform editors (e.g., VS Code) in addition to Visual Studio.
  • Link to documentation pages that describe Linux/macOS workflows for Service Fabric.
  • Explicitly state platform compatibility for each tool or method mentioned.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific tools and paths (e.g., Service Fabric SDK installed in 'C:\Program Files\...'), mentioning Visual Studio as a primary packaging/deployment method, and omitting explicit Linux/macOS equivalents or examples. There are no Linux/macOS-specific instructions, examples, or tool references, which may create friction for non-Windows users.
Recommendations
  • Add explicit instructions and examples for packaging and deploying guest executables from Linux/macOS environments, including command-line utilities and file paths.
  • Reference cross-platform tools (such as Azure CLI, Service Fabric CLI) and provide parity in documentation for Linux/macOS users.
  • Include sample directory structures and manifest file locations as they would appear on Linux/macOS systems.
  • Mention alternative IDEs or editors for Linux/macOS users, not just Visual Studio.
  • Clarify whether the Service Fabric SDK and packaging tools are available and supported on Linux/macOS, and provide installation instructions if so.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. The 'Next steps' section specifically directs users to PowerShell-based deployment and removal instructions, and the only example for downloading a ServicePackage in advance links to a PowerShell cmdlet. There are no explicit Linux or cross-platform CLI examples, and Windows tools (PowerShell) are mentioned exclusively for operational tasks, suggesting a Windows-first approach.
Recommendations
  • Include equivalent Linux/macOS instructions using Azure CLI, Service Fabric CLI (sfctl), or REST API where possible.
  • Provide cross-platform examples side-by-side, especially for deployment, removal, and package management tasks.
  • Reference documentation pages for Linux/macOS workflows in the 'Next steps' section.
  • Clarify which steps or tools are platform-specific and offer alternatives for non-Windows environments.
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-01-12 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 demonstrates a notable Windows bias. All command-line examples use PowerShell cmdlets (e.g., New-ServiceFabricService), and there are no equivalent CLI or bash examples for Linux/macOS users. References to management operations (deploy, remove, query) link exclusively to PowerShell modules, and the 'Next steps' section explicitly describes using PowerShell to manage applications. There is no mention of Azure CLI, Service Fabric CLI (sfctl), or bash scripting, which are the primary tools for Linux/macOS environments.
Recommendations
  • Add equivalent examples using Azure CLI (az sf) and/or Service Fabric CLI (sfctl) for all PowerShell commands.
  • Include bash shell examples where appropriate, especially for service creation and management.
  • Reference cross-platform tools (Azure CLI, sfctl, REST API) before or alongside PowerShell, not exclusively after.
  • Clarify in the 'Next steps' and relevant sections that management can be performed from Linux/macOS using CLI tools.
  • Where PowerShell is mentioned, explicitly note its cross-platform availability or provide alternatives for non-Windows users.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Visual Studio (Windows-centric tools) are mentioned first and in more detail when describing how to pass parameters during application creation. The use of PowerShell cmdlets and Visual Studio parameter files is emphasized, while Linux/macOS workflows (such as sfctl and install.sh) are mentioned but not elaborated upon. There is also a reference to Azure DevOps and Jenkins for string substitution, but the examples and guidance lean toward Windows tooling.
Recommendations
  • Provide equivalent Linux/macOS command-line examples (e.g., bash scripts, sfctl usage) alongside PowerShell examples.
  • Expand on the use of sfctl and install.sh for Linux/macOS users, including sample commands and parameter file handling.
  • Include guidance for non-Windows IDEs or editors (such as VS Code) for managing parameter files.
  • Ensure that references to deployment workflows (e.g., Jenkins) include both Windows and Linux script examples.
  • Consider reordering examples so that Linux/macOS options are presented alongside or before Windows options.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The manifest examples are based on a Windows Server 2016 container sample, and Windows-specific tools and patterns (such as 'winver' for OS build detection and 'c:\VolumeTest\Data' paths) are referenced. Windows instructions and terminology (e.g., PFX certificates, LocalMachine store) are given before or instead of Linux equivalents. There are no Linux-specific manifest examples, and Linux/macOS users are left to infer how to adapt the instructions.
Recommendations
  • Provide equivalent Linux-based manifest examples, referencing Linux container images and filesystem paths (e.g., '/mnt/VolumeTest/Data').
  • Explicitly mention Linux/macOS procedures for tasks like OS build detection (e.g., 'cat /etc/os-release') and certificate handling (PEM format, Linux certificate stores).
  • Clarify cross-platform differences in resource governance, volume drivers, and certificate import, with side-by-side instructions or notes.
  • Avoid referencing Windows tools (e.g., 'winver') without Linux alternatives.
  • Ensure all features and patterns are described for both Windows and Linux environments, or clearly state any platform limitations.
GitHub Create Pull Request
Service Fabric Change FabricTransport settings ...service-fabric-reliable-actors-fabrictransportsettings.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows certificate store concepts (e.g., 'LocalMachine', 'My'), using Windows-centric certificate subject names (e.g., 'WinFabric-Test-SAN1-Alice'), and omitting Linux-specific configuration examples. Although there is a brief note about PEM certificates for Linux, all XML configuration samples and parameter values are tailored to Windows environments, with no guidance for Linux equivalents.
Recommendations
  • Add explicit Linux configuration examples, including how to specify certificate paths and stores on Linux nodes.
  • Clarify which parameters are Windows-only (e.g., 'CertificateStoreLocation', 'CertificateStoreName') and provide Linux alternatives or note if they should be omitted.
  • Include sample XML snippets for Linux, demonstrating PEM certificate usage and typical Linux certificate paths.
  • Use neutral or Linux-relevant subject names in examples, not just 'WinFabric-Test-SAN1-Alice/Bob'.
  • Provide a table or section comparing Windows and Linux certificate configuration parameters and behaviors.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a Windows bias through references to Windows-specific tools and patterns, such as mentioning ServiceFabric PowerShell modules for service creation, using .exe and .bat files for entry points, and referencing Windows accounts (NetworkService, Administrators). There is no mention of Linux equivalents, nor are Linux-specific examples (e.g., shell scripts, Linux user/group patterns) provided. The documentation assumes Windows conventions throughout, which may create friction for Linux/macOS users.
Recommendations
  • Add Linux-specific examples, such as using shell scripts (.sh) for SetupEntryPoint and EntryPoint, and clarify how to configure these for Linux clusters.
  • Document Linux user/group equivalents and how Service Fabric maps or creates principals on Linux nodes.
  • Include instructions or references for managing Service Fabric applications using Linux CLI tools (e.g., sfctl) instead of only PowerShell.
  • Explicitly note differences in resource governance, endpoint configuration, and security policies between Windows and Linux clusters.
  • Reorder examples or add parallel Linux sections so that Linux users do not have to mentally translate Windows patterns.
GitHub Create Pull Request
Service Fabric Package an Azure Service Fabric app ...articles/service-fabric/service-fabric-package-apps.md
Medium Priority View Details →
Scanned: 2026-01-12 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 exhibits a notable Windows bias. All command-line examples use Windows-specific tools (tree, msbuild.exe, PowerShell cmdlets), and all file paths are Windows-style. Visual Studio is presented as the primary packaging tool, with no mention of Linux/macOS alternatives. There are no Linux shell or cross-platform examples for packaging, testing, or compressing Service Fabric applications. PowerShell is used exclusively for validation and compression, with no Bash or CLI alternatives provided.
Recommendations
  • Add equivalent Linux/macOS examples for directory structure (e.g., using 'tree' or 'ls' with Unix paths).
  • Document how to package Service Fabric applications using cross-platform .NET CLI (dotnet) or msbuild on Linux/macOS.
  • Provide instructions for validating and compressing packages using Service Fabric CLI (sfctl) or REST API, where available.
  • Include file path examples in both Windows and Unix formats.
  • Clarify which steps/tools are Windows-only and offer alternatives for Linux/macOS users.
  • Mention any platform limitations explicitly so users can plan accordingly.
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-01-12 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 demonstrates a notable Windows bias: all deployment and management examples use PowerShell commands, with no mention of Azure CLI, Bash, or Linux/macOS alternatives. Windows tools and patterns (such as RDP and Windows-style file paths) are referenced exclusively, and Windows-centric terminology is used throughout. There are no Linux/macOS-specific instructions or examples, which could create friction for non-Windows users.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash script snippets and Linux/macOS terminal commands where relevant, especially for deployment and resource management.
  • Mention SSH as an alternative to RDP for accessing VMs, and provide instructions for both.
  • Use platform-neutral file paths and command syntax in examples, or show both Windows and Linux/macOS variants.
  • Explicitly state that all templates and procedures are compatible with Linux/macOS, and highlight any platform-specific considerations.
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-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is heavily featured for command-line examples, with no mention of Linux/macOS equivalents (such as Bash, CLI, or cross-platform tools). Windows-specific tools and patterns (PowerShell cmdlets, Windows paths) are presented exclusively and before REST or API alternatives. There are no Linux/macOS shell examples, nor guidance for users on non-Windows platforms.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or other cross-platform tools for health reporting and querying.
  • Explicitly mention Linux/macOS compatibility for Service Fabric health reporting, including any required setup or differences.
  • Provide REST API usage examples with curl or httpie, showing how Linux/macOS users can perform the same operations.
  • Clarify which tools are available on which platforms, and link to installation/setup guides for Linux/macOS users.
  • Reorder examples so REST and cross-platform methods are presented before or alongside PowerShell, not after.
GitHub Create Pull Request
Service Fabric Change ReliableDictionaryActorStateProvider settings ...e-actors-reliabledictionarystateprovider-configuration.md
Medium Priority View Details →
Scanned: 2026-01-12 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 demonstrates a Windows bias by referencing Visual Studio (Windows-only for Service Fabric), using Windows-style paths in examples, and mentioning PowerShell commands without Linux equivalents. The configuration workflow is described in terms of files and tools typically found on Windows, with little guidance for Linux users. Linux-specific instructions are minimal and relegated to a single note about certificate formatting.
Recommendations
  • Provide explicit instructions for configuring settings.xml and cluster manifests on Linux, including typical file locations and editing workflows.
  • Include Linux command-line equivalents (e.g., Azure CLI, sfctl, or bash commands) for PowerShell commands like Get-ServiceFabricClusterManifest.
  • Show sample paths using Linux conventions (e.g., /var/log/servicefabric/SharedLog.Log) alongside Windows paths.
  • Clarify how Linux users can generate and edit configuration files if not using Visual Studio.
  • Add a Linux/macOS-specific example for certificate configuration and other platform-dependent settings.
GitHub Create Pull Request
← Previous Page 25 of 29 Next →