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 851-875 of 2475 flagged pages
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md') and the Patch Orchestration Application for Windows. There are no explicit Linux examples or links to Linux-specific upgrade/configuration documentation, despite Service Fabric standalone clusters supporting Linux. Windows is mentioned first and exclusively in upgrade/configuration contexts.
Recommendations
  • Add links to Linux-specific upgrade and configuration documentation (e.g., 'service-fabric-cluster-upgrade-linux.md', if available).
  • Include examples or instructions for Linux clusters alongside Windows examples.
  • Mention Linux patch orchestration options or clarify if POA is Windows-only.
  • Ensure parity in guidance for customizing cluster settings and upgrades for Linux users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific guide for scaling standalone clusters. No Linux equivalents, commands, or tools are mentioned, nor are Linux-specific instructions provided. This creates friction for Linux users who may be running standalone clusters outside of Windows environments.
Recommendations
  • Add Linux-specific instructions for scaling standalone clusters, including relevant commands and tools (e.g., using sfctl or REST APIs).
  • Provide examples for querying and updating cluster manifests on Linux, not just via PowerShell.
  • Clarify whether standalone cluster scaling is supported on Linux, and if so, link to Linux documentation or guides.
  • Ensure parity in guidance and examples for both Windows and Linux environments.
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-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page covers security scenarios for Azure Service Fabric clusters, including both Azure-hosted and standalone Windows clusters. However, it repeatedly references standalone clusters as 'Windows Server clusters' and provides links and examples only for Windows (e.g., 'Secure a standalone cluster on Windows by using X.509 certificates', 'Secure a standalone cluster on Windows by using Windows security'). There is no mention of standalone Linux clusters, nor guidance or links for securing Service Fabric clusters running on Linux outside Azure. Certificate creation instructions and recommendations are also Windows-centric (e.g., Windows Server certificate service, MakeCert.exe), with no Linux tooling or process described.
Recommendations
  • Add explicit guidance and examples for securing standalone Service Fabric clusters running on Linux, if supported.
  • Provide links to Linux-specific documentation for certificate creation, installation, and cluster configuration.
  • Mention Linux certificate management tools (e.g., OpenSSL) and processes alongside Windows tools.
  • Clarify whether standalone Linux clusters are supported, and if not, state this clearly to avoid confusion.
  • Ensure parity in example coverage for both Windows and Linux environments where applicable.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-specific logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and tools. It does not mention Linux equivalents or provide guidance for accessing Service Fabric events on Linux-based clusters, nor does it offer Linux-specific examples or monitoring patterns. Windows tools and patterns are mentioned first and exclusively.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including any differences in logging channels, agents, or integration steps.
  • Provide examples or references for Linux-compatible monitoring tools and log aggregation methods (e.g., using Azure Monitor, Log Analytics, or other agents on Linux).
  • Clarify whether the EventStore REST APIs and Service Fabric Client Library are cross-platform and provide usage examples for Linux/macOS environments.
  • Explicitly state any limitations or differences for Linux clusters regarding event access and diagnostics.
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-26 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 setting DNS names but does not offer equivalent Linux CLI or scripting examples (e.g., Bash, Azure CLI). Windows tools and patterns (PowerShell, ApplicationManifest.xml, Visual Studio) are mentioned before Linux alternatives, and Linux-specific limitations are highlighted without guidance or parity. No Linux-centric workflow or example is provided for DNS service configuration or verification.
Recommendations
  • Add Azure CLI or Bash examples for configuring DNS names and services, especially for Linux clusters.
  • Include instructions for editing service manifests and deploying from Linux environments (e.g., using VS Code, nano, or other editors instead of Visual Studio).
  • Clarify Linux workflows for enabling DNS service, including any required steps or workarounds (such as using ARM templates or REST API).
  • Provide explicit guidance for verifying DNS configuration on Linux clusters, possibly using Linux-native tools (e.g., dig, nslookup).
  • Ensure Linux limitations are accompanied by actionable alternatives or links to relevant Linux documentation.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-02-26 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 provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is evidence of Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned before Linux equivalents, and Windows concepts (such as FabricHost.exe as a Windows service) are described in detail, while Linux-specific workflows and examples are less prominent or missing. Standalone cluster creation is only described for Windows, and Linux standalone clusters are noted as unsupported. CLI and REST API options are mentioned, but PowerShell is often listed first. There are few, if any, Linux-specific examples or guidance.
Recommendations
  • Provide Linux-specific examples and workflows alongside Windows examples, especially for cluster management and application lifecycle tasks.
  • Mention Linux tools (such as Bash, Linux CLI usage) before or alongside Windows tools like PowerShell.
  • Clarify which features are cross-platform and which are Windows-only, and provide links to Linux-specific documentation where available.
  • Add guidance for Linux users on cluster creation, management, and troubleshooting, even if standalone Linux clusters are not yet supported.
  • Ensure parity in example ordering (e.g., CLI before PowerShell, or both together) and tool recommendations.
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-02-26 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 moderate Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd') and does not provide equivalent Linux/macOS paths or examples. The application package structure and manifest files are described generically, but the only explicit tooling and directory references are Windows-centric. There are no Linux/macOS-specific instructions, examples, or clarifications about cross-platform support. Visual Studio is mentioned as a packaging tool, but alternatives for Linux/macOS users are not discussed.
Recommendations
  • Add Linux/macOS equivalent file paths for schema definitions and clarify where these files are located on non-Windows systems.
  • Provide command-line examples for packaging and deploying guest executables using cross-platform tools (e.g., Azure CLI, Service Fabric CLI) instead of or in addition to Visual Studio.
  • Mention or link to Linux/macOS-compatible tools and instructions for creating application and service manifests.
  • Clarify any platform-specific limitations or requirements for Service Fabric guest executables, including whether Linux clusters are supported and how packaging differs.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters, and links to PowerShell-based deployment/removal instructions as the main 'Next steps'. While Service Fabric is cross-platform, the documentation does not provide Linux/macOS CLI or scripting alternatives (such as Bash or Azure CLI), nor does it mention Linux-specific workflows or tools. The focus on PowerShell and Visual Studio (which are Windows-centric) creates friction for Linux/macOS users.
Recommendations
  • Add examples and links for deploying and managing Service Fabric clusters using Azure CLI or Bash scripts, where possible.
  • Mention cross-platform tools and workflows explicitly, such as using REST APIs or .NET Core SDKs on Linux/macOS.
  • Provide parity in 'Next steps' by linking to Linux/macOS instructions or general (platform-agnostic) guides.
  • Clarify which steps or tools are Windows-only and offer alternatives for other platforms.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for the Azure Service Fabric hosting model provides conceptual information applicable to all platforms, but the practical examples and tooling references are heavily skewed toward Windows and PowerShell. The only CLI example given is PowerShell, and all links to command references are for PowerShell modules. There are no Linux/macOS CLI examples (e.g., Bash, Azure CLI), nor is it mentioned how to perform equivalent operations on Linux clusters. The C# example is cross-platform, but the operational guidance is Windows-centric.
Recommendations
  • Add Azure CLI or Bash examples for creating services with ExclusiveProcess mode, especially for Linux clusters.
  • Mention or link to Linux/macOS-compatible tools or workflows for managing Service Fabric services.
  • Clarify if PowerShell examples are usable on Linux (via PowerShell Core), or provide alternative commands if not.
  • Balance example ordering so Linux/macOS users see relevant options alongside Windows users.
  • Add a note about platform support for Service Fabric management tools, specifying which tools are available on which OS.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page provides Service Fabric container application manifest examples that are based on Windows Server 2016 Container Sample manifests. Windows-specific tools and patterns are referenced first or exclusively in several places, such as instructions to use 'winver' to get the OS build version and the use of Windows-style paths (e.g., 'c:\VolumeTest\Data'). There is some mention of Linux (e.g., certificates being exposed as PEM files), but Linux-specific examples, paths, or instructions are missing.
Recommendations
  • Provide equivalent Linux-based manifest examples or explicitly state Linux compatibility where applicable.
  • Include Linux-style paths (e.g., '/mnt/data') in volume mount examples alongside Windows paths.
  • When referencing OS build version detection, mention Linux equivalents (e.g., 'uname -r' or '/etc/os-release') in addition to 'winver'.
  • Clarify which features or manifest elements are cross-platform and which are Windows-only.
  • Link to or provide Linux container sample manifests if available.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides both Windows-specific (HTTP.sys) and cross-platform (Kestrel) guidance for ASP.NET Core service communication in Azure Service Fabric. However, Windows-only tools and APIs (HTTP.sys, Windows HTTP Server API, netsh) are discussed in detail, sometimes before their Linux equivalents. Windows-specific configuration steps and limitations are highlighted, and Windows terminology is used throughout. While Kestrel is recommended for Linux and cross-platform scenarios, the HTTP.sys sections and endpoint configuration guidance are Windows-centric and may create friction for Linux/macOS users.
Recommendations
  • Clearly separate Windows-only guidance (HTTP.sys, netsh, Windows HTTP Server API) from cross-platform guidance.
  • Add explicit notes or sections for Linux/macOS users, clarifying that Kestrel is the only supported web server and that HTTP.sys is not available.
  • Move Kestrel guidance and examples before HTTP.sys sections to emphasize cross-platform support.
  • Provide Linux/macOS-specific troubleshooting tips or configuration notes where relevant.
  • Ensure that all code samples and configuration steps are clearly labeled as Windows-only or cross-platform.
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-26 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 APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and screenshots based on Windows tooling. There is no mention of Linux-specific command-line equivalents, nor are cross-platform usage patterns or examples provided. The focus on PowerShell and Windows tools creates friction for Linux/macOS users, who may need to use FabricClient APIs or other methods not documented here.
Recommendations
  • Add explicit examples for Linux/macOS users, such as using Service Fabric CLI (sfctl) or REST APIs where available.
  • Clarify whether the PowerShell APIs are available or supported on Linux/macOS, and if not, provide guidance for equivalent operations.
  • Include sample commands or code snippets for FabricClient usage in cross-platform languages (e.g., Python, Java, .NET Core).
  • Mention any limitations or differences in replica soft delete behavior on Linux clusters, if applicable.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides extensive PowerShell examples for health reporting, with no equivalent Linux/bash CLI examples. Windows/PowerShell commands are shown first and exclusively, while REST and API options are mentioned but not demonstrated with Linux-friendly tools. There is no mention of Linux Service Fabric CLI usage or cross-platform scripting, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Show bash or cross-platform scripting examples alongside PowerShell.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Mention and link to Linux-specific documentation or guidance for health reporting.
  • Ensure REST examples include curl or other Linux-friendly command-line usage.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation is heavily focused on Visual Studio workflows, which are Windows-centric. All deployment and configuration examples reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish), and PowerShell is mentioned as the CLI tool for service creation. There are no examples or guidance for Linux/macOS users, nor are cross-platform tools (such as Azure CLI or other SDKs) referenced. The documentation assumes a Windows development environment and omits Linux/macOS parity.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide examples using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), if supported.
  • Clarify whether StartupServices.xml is strictly a Windows/Visual Studio feature, and if so, mention alternatives for Linux/macOS users.
  • If PowerShell is referenced, also mention Bash or other shell equivalents for Linux/macOS.
  • Include a section outlining limitations or differences for non-Windows environments.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-26 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 is heavily focused on Windows-specific tools (Visual Studio and PowerShell) for upgrading Service Fabric applications. All examples and instructions reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS equivalents or cross-platform CLI tools. Linux users are not provided with alternative approaches or guidance, creating friction for non-Windows environments.
Recommendations
  • Add instructions for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Include examples for Linux/macOS users, such as using Bash scripts or relevant CLI commands.
  • Clarify whether Visual Studio and PowerShell are required, or if alternative tools exist for non-Windows platforms.
  • Provide links to documentation for Linux/macOS workflows, if available.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples use Windows container images (mcr.microsoft.com/windows/nanoserver:1809), Windows paths (C:\...), and Windows commands (cmd, echo, type, ping). There are no examples or guidance for Linux containers or Linux-based workloads, and the page explicitly references Windows container compatibility. This creates friction for Linux users and does not demonstrate Linux parity.
Recommendations
  • Add examples using Linux container images (e.g., mcr.microsoft.com/ubuntu or other Linux distros) and Linux commands (bash, echo, cat, etc.).
  • Show how Initializer CodePackages can be used in Linux container scenarios, including volume mounts with Linux paths (/workspace/log.txt).
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide equivalent Linux-focused guidance.
  • If Initializer CodePackages are Windows-only, state this clearly at the top of the article to set expectations.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-02-25 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 notable Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set, exit), and Windows-centric naming. The 'Query deployment status' section only provides PowerShell and C# examples, with no mention of Linux CLI or Bash alternatives. There is no guidance or example for Linux containers or cross-platform usage, despite Service Fabric supporting containers in general.
Recommendations
  • Add examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
  • Provide equivalent Bash or Linux CLI instructions for querying deployment status, such as using sfctl or REST APIs.
  • Clarify whether RunToCompletion semantics are supported for Linux containers, and if so, provide relevant guidance.
  • Balance Windows and Linux examples, or explicitly state if Windows containers are required for this feature.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-25 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 provides PowerShell-only examples and references to Windows-specific tools (e.g., http.sys), with no equivalent CLI or Linux/macOS instructions. The only code sample is in PowerShell, and the upgrade process is described using Windows-centric tooling and APIs. Linux users are not provided with alternative commands or guidance, which may cause confusion or block them from following the documented procedures.
Recommendations
  • Add equivalent Azure CLI or Service Fabric CLI (sfctl) examples for application upgrades, especially for retrieving and passing application parameters.
  • Clearly indicate when a feature or limitation (such as http.sys or certificate handling) is Windows-specific, and provide Linux/macOS alternatives or workarounds if available.
  • Include Linux/macOS-specific instructions or notes where behavior or commands differ.
  • Reorder or supplement sections so that cross-platform tools (e.g., Azure CLI, REST API, sfctl) are mentioned alongside or before Windows-specific tools like PowerShell.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell cmdlets as primary management tools and mentions Windows security as a transport option. There are no explicit Linux or cross-platform management tool examples (such as CLI or REST API), and PowerShell is presented as the default for provisioning and lifecycle management, which may create friction for Linux/macOS users.
Recommendations
  • Mention and provide examples for cross-platform management tools such as Azure CLI or REST APIs alongside PowerShell.
  • Clarify whether PowerShell cmdlets are required or if equivalent functionality is available via other tools on Linux/macOS.
  • Add notes or links to Linux/macOS-specific guidance for managing Service Fabric clusters.
  • Explicitly state platform support for each subsystem/tool where relevant.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell and C# examples for managing Service Fabric Application Groups. PowerShell is a Windows-centric tool, and no Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API) are included. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform management but the documentation does not reflect this.
Recommendations
  • Add Azure CLI examples for all operations shown (application creation, updating, querying load, removing capacity).
  • Include REST API sample requests for relevant actions.
  • Mention cross-platform tools and clarify which commands are available on Linux/macOS.
  • If PowerShell is required, note whether PowerShell Core is supported and provide installation guidance for non-Windows users.
  • Consider adding Bash scripts or references to SDKs usable on Linux/macOS.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for most security best practices, but Windows-specific tools and examples (such as PowerShell commands and Windows Defender) are often presented first or exclusively. Windows-centric features like Windows Defender and security baselines are discussed without Linux equivalents or alternatives. The encryption workflow gives Windows (PowerShell) and Linux (openssl) examples, but Windows instructions are presented first. Some sections reference Windows tools (e.g., Azure Desired State Configuration, Windows Defender) without mentioning Linux alternatives.
Recommendations
  • Present Windows and Linux examples side-by-side or alternate their order to avoid Windows-first bias.
  • Where Windows-specific tools are discussed (e.g., Windows Defender, DSC), add notes or links to Linux security alternatives (such as common Linux antivirus solutions or configuration management tools).
  • Clarify when a feature or recommendation is Windows-only, and provide Linux-specific guidance where possible.
  • Expand Linux-focused sections to match the detail and prominence of Windows-focused sections.
  • Ensure all critical workflows (certificate management, secret encryption, endpoint configuration) have clear Linux instructions, not just links.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides PowerShell examples for managing node tags and service requirements, but does not include equivalent Linux/macOS CLI examples (such as Azure CLI or bash). PowerShell is primarily a Windows tool, and its use here creates friction for Linux/macOS users. There is no mention of cross-platform tools or commands, and the documentation does not clarify if PowerShell Core (cross-platform) is supported or required.
Recommendations
  • Add Azure CLI or REST API examples for managing node tags and service requirements, as these are cross-platform and accessible from Linux/macOS.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide instructions for Linux/macOS users if so.
  • Mention any limitations or alternative workflows for Linux/macOS users, especially if certain commands are Windows-only.
  • Consider including bash script examples or references to relevant Service Fabric CLI tools if available.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily references Windows Server-specific upgrade and configuration guides, and the Patch Orchestration Application is described only for Windows. There is no mention of Linux-specific upgrade procedures, configuration files, or patch orchestration, nor are Linux examples or links provided. The linked guides and instructions are Windows-focused, creating friction for Linux users managing Service Fabric standalone clusters.
Recommendations
  • Add explicit guidance or links for upgrading Service Fabric standalone clusters on Linux, if supported.
  • Provide Linux-specific examples for cluster configuration, node properties, and capacity metrics.
  • Clarify whether Patch Orchestration Application or similar solutions exist for Linux nodes, and provide relevant documentation.
  • Ensure that references to upgrade/configuration guides include both Windows and Linux versions, or clearly state platform limitations.
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-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is generally OS-neutral in its explanations of the Service Fabric hosting lifecycle. However, the 'Next steps' section only links to PowerShell-based deployment/removal guidance, and the only explicit example of downloading a ServicePackage in advance references a PowerShell cmdlet. There are no Linux CLI or cross-platform examples or links, which may create friction for Linux users.
Recommendations
  • Provide equivalent Linux/Bash/CLI examples or links alongside PowerShell references, especially for common tasks like deploying or removing applications.
  • In the 'Next steps' section, add links to documentation for deploying/removing applications using Azure CLI, REST API, or Service Fabric CLI (sfctl), which are cross-platform.
  • When referencing commands or tools (such as in [download the ServicePackage in advance on the node]), clarify if the method is Windows-only and suggest Linux alternatives if available.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell example for deploying Service Fabric applications, which is a Windows-centric tool. While Linux clusters are mentioned (e.g., certificate store location), the deployment example uses PowerShell exclusively, and there are no equivalent Linux CLI (e.g., sfctl) or bash examples. Windows file paths and tools are referenced first or exclusively in some sections.
Recommendations
  • Add equivalent Linux deployment examples using sfctl or Azure CLI.
  • Mention Linux/macOS file paths and tools alongside Windows paths (e.g., schema location).
  • Provide bash or shell script examples where PowerShell is used.
  • Clarify any platform-specific differences in endpoint configuration and deployment.
GitHub Create Pull Request
← Previous Page 35 of 99 Next →