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 2151-2175 of 2475 flagged pages
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters and generally maintains platform neutrality. However, in several sections, Windows-centric tools (PowerShell) are mentioned before or instead of Linux equivalents. The section on OS image upgrades links only to Windows patching guidance, and PowerShell is referenced as a management tool alongside Azure CLI, but Linux-specific tools or examples are not provided. There is an implicit prioritization of Windows patterns and tools, which may create friction for Linux users.
Recommendations
  • When mentioning PowerShell, also provide Bash/Azure CLI examples or clarify cross-platform support.
  • For OS image upgrades, include or link to Linux node patching guidance if Service Fabric supports Linux clusters.
  • Explicitly state when steps or tools apply to both Windows and Linux clusters, or clarify any platform limitations.
  • Add examples or references for Linux management workflows where appropriate (e.g., Bash scripts, Linux CLI usage).
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for the Azure Service Fabric application resource model demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mentioning or providing equivalent Azure CLI commands, which are cross-platform and preferred on Linux/macOS. The application packaging workflow is described using Visual Studio, a Windows-centric tool, with no alternative instructions for packaging on Linux/macOS. No Linux or CLI examples are provided, and Windows tools are referenced first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
  • Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK commands) instead of or in addition to Visual Studio.
  • Explicitly mention that all steps can be performed on Linux/macOS, and link to relevant cross-platform tooling.
  • Where screenshots or UI steps are shown, clarify if there are differences for Linux/macOS users or provide alternative guidance.
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-01-31 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 provides a general overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a noticeable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned first or exclusively in several places, and Windows terminology (e.g., Windows service, FabricHost.exe) is used without always clarifying Linux equivalents. Examples and links for cluster creation and upgrades focus on Windows, with Linux standalone clusters explicitly noted as unsupported. Linux tools and workflows are referenced but often after Windows, and some sections lack Linux-specific examples or guidance.
Recommendations
  • Present Windows and Linux options side-by-side when discussing tools, commands, and workflows (e.g., PowerShell vs. CLI).
  • Add Linux-specific examples and links where only Windows instructions are given (e.g., cluster creation, upgrades).
  • Clarify when features or tools are Windows-only, and provide alternative guidance for Linux users.
  • Mention Linux equivalents (e.g., systemd services, Linux CLI tools) when describing Windows services and executables.
  • Ensure that getting started and next steps sections include Linux paths and resources.
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-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by prioritizing PowerShell and Visual Studio examples, mentioning Windows-centric tools and workflows first, and lacking explicit Linux/macOS command-line examples (e.g., Bash, shell scripts) for parameter passing and deployment. While sfctl and Jenkins are mentioned, the examples and workflow descriptions are predominantly Windows-oriented.
Recommendations
  • Add explicit Linux/macOS examples for application creation and parameter passing, such as Bash scripts using sfctl.
  • Present cross-platform tools (sfctl, Jenkins) before or alongside Windows tools (PowerShell, Visual Studio) in workflow descriptions.
  • Include sample shell script snippets for Linux users to mirror the PowerShell examples.
  • Clarify which steps are platform-agnostic and which are Windows-specific, to help users on all platforms navigate the documentation.
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-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for upgrading an Azure Service Fabric standalone cluster exhibits moderate Windows bias. References and links to upgrade instructions and configuration customization are directed to Windows Server-specific documentation (e.g., service-fabric-cluster-upgrade-windows-server.md, service-fabric-cluster-config-upgrade-windows-server.md). The Patch Orchestration Application is described only for Windows. There are no explicit Linux examples, nor is there mention of Linux-specific upgrade or patching guidance, despite Service Fabric standalone clusters supporting both Windows and Linux.
Recommendations
  • Add explicit guidance and examples for upgrading Service Fabric standalone clusters running on Linux, including links to Linux-specific documentation if available.
  • Clarify which features or tools (such as Patch Orchestration Application) are Windows-only, and provide Linux alternatives or state if none exist.
  • Ensure that configuration and upgrade instructions reference both Windows and Linux where applicable, or clearly indicate platform limitations.
  • Where possible, provide cross-platform examples or note differences in procedures between Windows and Linux clusters.
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-31 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions both Windows Server and Linux as supported platforms for Service Fabric clusters, but it highlights that standalone clusters are not available on Linux. The page does not provide Linux-specific examples or guidance, and Windows is mentioned first throughout. The lack of Linux standalone cluster support is a product limitation, but the documentation could better clarify Linux usage scenarios and alternatives.
Recommendations
  • Explicitly state the limitations for Linux (i.e., standalone clusters not supported) early in the document.
  • Provide guidance or links for deploying Service Fabric clusters on Linux within Azure, including any differences in management or feature support.
  • Include a comparison table summarizing feature parity and limitations between Windows and Linux clusters.
  • Add Linux-specific examples or references where applicable, especially for Azure-hosted clusters.
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-31 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 presents PowerShell as the primary CLI example for creating services with the Exclusive Process model, without providing equivalent Linux/macOS CLI examples (such as Azure CLI or Bash). The references to service management operations (creating, querying, reporting health, restarting) are all linked to PowerShell cmdlets, and the 'Next steps' section specifically mentions PowerShell for managing application instances. There is no mention of Linux-native tools or cross-platform command-line alternatives, nor are examples for Linux/macOS users provided.
Recommendations
  • Add Azure CLI or REST API command examples for service creation and management, demonstrating cross-platform usage.
  • Clarify in the documentation that PowerShell examples are applicable on Windows, and provide guidance for Linux/macOS users on how to perform equivalent operations.
  • Include links to Service Fabric SDK documentation for Linux/macOS, if available, and note any platform-specific limitations.
  • Where PowerShell cmdlets are referenced, provide REST API or Azure CLI equivalents in parallel.
  • In the 'Next steps' section, mention cross-platform management options, not just PowerShell.
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-01-31 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 and highlights cross-platform capabilities. However, there is a subtle Windows bias: Windows development is described first, with emphasis on Visual Studio and PowerShell integration, while Linux development is mentioned second and less prominently. No explicit Linux command-line examples or Linux-specific tooling are shown, and the quickstart link points to a .NET (typically Windows-first) example. There are no Linux shell or deployment examples, and the documentation does not provide parity in example depth or tooling coverage.
Recommendations
  • Present Windows and Linux development options with equal prominence and detail.
  • Include Linux shell (bash) and command-line examples alongside PowerShell examples.
  • Add quickstart links for both Windows (.NET) and Linux (Java/.NET Core) development.
  • Highlight Linux-specific tools (e.g., Yeoman, Eclipse) with example usage.
  • Ensure that deployment and management instructions include both Windows and Linux workflows.
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-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-specific tools and patterns, such as ETW/Windows Event logs and the Windows Azure diagnostics agent, without providing equivalent guidance or examples for Linux-based Service Fabric clusters. There is no mention of Linux event logging mechanisms or how Linux users can access or forward Service Fabric events, which may create confusion or friction for Linux users.
Recommendations
  • Add explicit guidance or examples for accessing Service Fabric events on Linux clusters, such as using syslog, journald, or other Linux-compatible logging solutions.
  • Clarify whether the described event access methods (e.g., EventStore REST APIs) are cross-platform and, if so, highlight these as the recommended approach for Linux clusters.
  • If certain features (like ETW/Windows Event logs or the Windows Azure diagnostics agent) are Windows-only, clearly state their platform limitations and provide Linux alternatives where possible.
  • Consider including a table or section comparing event access methods on Windows vs. Linux clusters.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Scanned: 2026-01-31 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 Windows PowerShell cmdlets (Send-ServiceFabricApplicationHealthReport, Get-ServiceFabricApplicationHealth), with no equivalent CLI, REST, or Linux/macOS example. This creates friction for Linux/macOS users, as the PowerShell tools are Windows-centric and not available natively on Linux clusters. The documentation also mentions PowerShell before REST or other cross-platform APIs when discussing how to send health reports.
Recommendations
  • Add equivalent examples using Azure CLI, REST API, or SDKs (e.g., Python, .NET Core) for reporting and querying health, especially for Linux/macOS users.
  • Explicitly mention which tools are available on Linux clusters and provide links to cross-platform tooling.
  • When listing ways to report health, mention REST API and SDKs before or alongside PowerShell to avoid implying PowerShell is the primary or only method.
  • Consider adding a note clarifying tool availability and platform support for health reporting commands.
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-31 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 Azure Service Fabric hosting activation and deactivation life cycle demonstrates a moderate Windows bias. The 'Next steps' section exclusively references PowerShell for deployment/removal tasks, and the only example for downloading a ServicePackage in advance links to a PowerShell cmdlet. There are no Linux shell or cross-platform CLI examples, and Windows tools (PowerShell) are mentioned before any Linux alternatives, which are absent.
Recommendations
  • Add equivalent Linux/macOS instructions using Azure CLI or Service Fabric CLI (sfctl) for deployment and package management tasks.
  • Provide bash or shell script examples alongside PowerShell where possible.
  • Clarify in the 'Next steps' section that PowerShell is one option, and link to cross-platform alternatives if available.
  • Where cmdlets are referenced, note their platform compatibility and suggest alternatives for non-Windows users.
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-31 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation frequently references PowerShell for deployment and management tasks, and links to PowerShell-based workflows before mentioning alternatives. There is an implicit assumption of Windows tooling (e.g., Visual Studio, PowerShell) as the primary interface, with limited mention of Linux/macOS equivalents or cross-platform CLI usage.
Recommendations
  • Add explicit examples and instructions for deploying and managing Service Fabric clusters using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), especially for Linux/macOS users.
  • Include references to Linux/macOS development workflows, such as using VS Code or command-line tools, alongside Visual Studio.
  • When mentioning retrieval of cluster manifests, provide examples for REST API and .NET Core/.NET 5+ usage, and clarify which tools are cross-platform.
  • Ensure that links to PowerShell documentation are accompanied by links to equivalent CLI or REST documentation where available.
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-31 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 examples are explicitly based on the 'Windows Server 2016 Container Sample', and references to Windows-specific tools and patterns (such as 'winver' for OS build detection and Windows-style file paths like 'c:\VolumeTest\Data') are present. There is no mention of Linux equivalents, nor are Linux-specific manifest samples or guidance provided. While some features (like certificate handling) acknowledge both Windows and Linux behaviors, the overall focus and examples are Windows-centric, creating friction for Linux users.
Recommendations
  • Provide equivalent Linux-based manifest examples, referencing Linux container samples if available.
  • Include instructions for determining OS build/version on Linux (e.g., using 'cat /etc/os-release' or 'uname -r') alongside 'winver'.
  • Show Linux-style file paths (e.g., '/mnt/volume/data') in volume mount examples.
  • Clarify which features and manifest elements are cross-platform, and note any Windows-only limitations.
  • Link to Linux container documentation or samples where appropriate.
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-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation for 'Networking patterns for Azure Service Fabric' demonstrates a notable Windows bias. All deployment and management examples use PowerShell commands, with no mention of Azure CLI, Bash, or Linux/macOS workflows. The only command-line examples are Windows-centric (PowerShell, RDP, Windows-style file paths), and there is no guidance for users on Linux or macOS platforms. This creates friction for non-Windows users attempting to follow the documentation.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include notes or sections for Linux/macOS users, such as how to deploy templates using Bash or Azure CLI.
  • Replace or supplement Windows-style file paths (e.g., C:\SFSamples\...) with platform-agnostic or Linux-style paths.
  • Mention SSH as an alternative to RDP for accessing VMs, and provide SSH examples.
  • Clarify which steps are platform-agnostic and which are Windows-specific, to help users on other operating systems.
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-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides extensive PowerShell examples and references for health reporting in Service Fabric, with no equivalent Linux/macOS CLI examples (such as Bash, sfctl, or Azure CLI). PowerShell commands are shown before REST API usage, and there is no mention of Linux tooling or cross-platform command-line approaches for interacting with Service Fabric health reporting. This creates friction for users on Linux/macOS, who must infer or research alternative methods.
Recommendations
  • Add equivalent examples using sfctl (the cross-platform Service Fabric CLI) for health reporting tasks shown in PowerShell.
  • Include Azure CLI examples where possible, especially for REST-based operations.
  • Explicitly mention that PowerShell examples are for Windows and provide guidance for Linux/macOS users.
  • Reorder or parallelize examples so REST/sfctl/Azure CLI approaches are shown alongside PowerShell, not after.
  • Clarify any platform limitations for Service Fabric tooling, and link to cross-platform tool documentation.
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-01-31 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is notably Windows-focused, referencing Visual Studio-specific workflows (Build/Rebuild/F5/Ctrl+F5/Publish) and omitting any mention of Linux/macOS development environments or deployment tooling. All examples and process descriptions assume usage of Visual Studio on Windows, with no guidance for Linux/macOS users or cross-platform alternatives.
Recommendations
  • Add explicit statements clarifying that StartupServices.xml is only supported for Visual Studio deployments on Windows, and is not available for Linux/macOS environments.
  • Provide alternative guidance or links for Linux/macOS users, such as using ARM templates, Service Fabric CLI, or PowerShell Core (if supported cross-platform) for service deployment and configuration.
  • Include a comparison table or section outlining differences in workflow between Windows (Visual Studio) and Linux/macOS environments for Service Fabric application deployment.
  • Mention supported cross-platform tools (e.g., Service Fabric CLI, Azure DevOps pipelines) and clarify which features are Windows-only.
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-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates a notable Windows/PowerShell bias. All command-line/API usage examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica), with no mention of Linux CLI equivalents, REST APIs, or cross-platform tooling. The documentation assumes the use of PowerShell and Windows-centric Service Fabric management tools, omitting guidance for Linux-based Service Fabric clusters or users managing clusters from non-Windows environments.
Recommendations
  • Include equivalent examples for Linux environments, such as using Service Fabric CLI (sfctl) or REST APIs where available.
  • Explicitly state whether the described PowerShell cmdlets are available or supported on Linux/macOS, and provide alternatives if not.
  • Add notes or sections clarifying how Linux users can perform soft delete, restore, and query operations (e.g., via sfctl, REST API, or SDKs).
  • Where possible, provide cross-platform code snippets or command examples, and avoid assuming PowerShell as the default management interface.
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-01-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides examples and deployment instructions primarily using Windows-centric tools and patterns, such as PowerShell cmdlets (e.g., New-ServiceFabricApplication) and Windows file paths. Linux equivalents are mentioned only briefly (e.g., certificate store location), and no Linux-specific deployment commands or examples are provided. The use of PowerShell for application deployment and references to Windows SDK installation paths suggest a Windows-first approach, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Linux/macOS deployment instructions and examples, such as using Azure CLI or Service Fabric CLI (sfctl) for application deployment.
  • Include Linux file paths and certificate management details alongside Windows paths where relevant.
  • Present cross-platform examples side-by-side or clarify which steps are platform-specific.
  • Reference Linux/macOS tools and patterns (e.g., bash scripts, sfctl) where PowerShell is currently used.
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-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page consistently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources, without providing equivalent Azure CLI or ARM template examples. This creates friction for Linux/macOS users, as PowerShell is a Windows-centric tool and not always the default or preferred option on non-Windows platforms.
Recommendations
  • Include Azure CLI examples (e.g., az resource delete, az servicefabric managed-cluster application create) alongside PowerShell cmdlets for all management operations.
  • Explicitly mention ARM template usage and provide sample templates or links for common operations.
  • Clarify that Az PowerShell cmdlets can be run cross-platform, but highlight Azure CLI as the primary cross-platform tool.
  • Where possible, order examples so that cross-platform tools (Azure CLI, ARM templates) are shown before or alongside PowerShell examples.
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-01-30 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: all code examples use Windows containers and Windows-specific commands (cmd, set, exitCode, etc.), and the only tooling example for querying deployment status is PowerShell. There is no mention of Linux containers, Linux-compatible commands, or equivalent Linux tooling (such as Bash or CLI). The examples and guidance are Windows-centric, which may create friction for users deploying Service Fabric workloads on Linux.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu images) and Linux shell commands.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide Linux-specific code samples.
  • Include instructions for querying deployment status using Azure CLI or Bash, if available.
  • Explicitly state any platform limitations (e.g., if RunToCompletion is Windows-only) at the top of the page.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell cmdlets and Windows security as primary management and security mechanisms, without mentioning Linux equivalents (such as Bash, CLI, or OpenSSL). No examples or tooling for Linux/macOS users are provided, and Windows tools are referenced exclusively in management and security contexts.
Recommendations
  • Include references to Azure CLI, Bash scripts, or REST APIs for cluster management alongside PowerShell cmdlets.
  • Mention Linux-compatible security mechanisms (such as OpenSSL certificates) in addition to Windows security.
  • Add examples or notes for Linux/macOS users on how to perform management and security tasks.
  • Clarify when features or tools are Windows-only, and provide alternatives or guidance for cross-platform scenarios.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-01-30 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 moderate Windows bias. Several examples and explanations reference Windows tools (e.g., PowerShell, netsh), and Windows-centric patterns are described before or in more detail than Linux equivalents. Some sections (such as port usage and API access) mention PowerShell and Windows-specific behaviors without providing equivalent Linux/CLI examples. ARM template and networking guidance is generally cross-platform, but Windows examples and terminology are more prominent.
Recommendations
  • Provide Linux CLI examples alongside PowerShell references, especially for API access and cluster management.
  • When describing port usage or network configuration, clarify differences for Linux clusters and offer Linux-specific commands (e.g., for checking dynamic port ranges).
  • Balance references to Windows tools (e.g., PowerShell, netsh) with Linux alternatives (e.g., bash, iptables, ss/netstat).
  • Ensure that application networking and container guidance includes Linux container scenarios and flags where relevant.
  • Where Windows is mentioned first, alternate or parallel Linux-first examples to improve parity.
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-01-30 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for on-demand backup in Azure Service Fabric is heavily focused on PowerShell and Windows tooling. All command-line examples use PowerShell cmdlets or PowerShell-based REST calls, with no mention of Linux/macOS equivalents (such as Bash, Azure CLI, or curl). The prerequisite section requires installation of a PowerShell module and the use of PowerShell commands to connect to clusters and trigger backups. There is no guidance for users on Linux or macOS platforms, nor are cross-platform alternatives suggested.
Recommendations
  • Add equivalent examples using Bash and Azure CLI (az servicefabric) or curl for REST API calls.
  • Clarify whether the PowerShell module is supported on PowerShell Core (pwsh) on Linux/macOS, and provide installation instructions if so.
  • If REST API calls are platform-agnostic, provide curl or HTTPie examples.
  • Explicitly mention any platform limitations (e.g., if certain modules/tools are Windows-only) and suggest alternatives for Linux/macOS users.
  • Reorder examples or provide parallel examples for both Windows and Linux/macOS users.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Scanned: 2026-01-30 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell and Visual Studio as primary upgrade tools, both of which are most commonly used on Windows. PowerShell is mentioned as a method for upgrading applications, but there is no mention of Linux/macOS CLI equivalents or cross-platform tooling. The examples and recommendations focus on C# and .NET serialization, which are cross-platform, but the upgrade workflow references Windows-centric tools first.
Recommendations
  • Add instructions or references for upgrading Service Fabric applications using cross-platform CLI tools (e.g., Azure CLI, Service Fabric CLI) where available.
  • Include examples or links for Linux/macOS users to perform upgrades, if supported.
  • Clarify in the documentation if PowerShell and Visual Studio are required due to Service Fabric limitations, or if alternatives exist for non-Windows environments.
  • Consider listing cross-platform options before or alongside Windows-specific tools in the 'Next steps' section.
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-01-30 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation on scaling Azure Service Fabric standalone clusters demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a 'scale a standalone cluster' guide that is Windows Server-focused. There are no Linux-specific instructions, examples, or mentions of Linux-compatible tools for managing or scaling standalone clusters, which may create friction for Linux users.
Recommendations
  • Include equivalent Linux command-line instructions (e.g., using sfctl or REST APIs) alongside PowerShell examples.
  • Clarify whether standalone cluster scaling is supported on Linux, and if so, provide Linux/macOS-specific guidance or links.
  • If certain operations are Windows-only, explicitly state this limitation to set user expectations.
  • Add references to cross-platform tools (such as sfctl) where possible, and provide example commands for both Windows and Linux environments.
GitHub Create Pull Request
← Previous Page 87 of 99 Next →