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 551-575 of 2475 flagged pages
Service Fabric
Describe a cluster by using Cluster Resource Manager
...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux configuration examples for Service Fabric clusters, but Windows-specific XML (ClusterManifest.xml) and PowerShell examples are presented first and more frequently. PowerShell is the only CLI example shown for service creation and updates, with no Linux CLI or Bash equivalents. The XML configuration is labeled as 'WindowsServer', and while JSON examples are given for standalone (cross-platform) deployments, there is no explicit mention of Linux-specific tools or patterns. The bias is mostly in the ordering and CLI example selection.
Recommendations
- Add Bash/CLI examples for service creation and updates (e.g., using sfctl or Azure CLI) alongside PowerShell.
- Clarify that ClusterManifest.xml is for Windows clusters, and highlight Linux configuration patterns (e.g., use of ClusterConfig.json for Linux).
- Present JSON (cross-platform) configuration examples before or alongside Windows XML examples.
- Mention Linux node types and any relevant differences in cluster setup.
- Provide links or references to Linux-specific Service Fabric documentation where appropriate.
Create Pull Request
Service Fabric
Cluster Resource Manager - Management Integration
...fabric-cluster-resource-manager-management-integration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying health information, but does not include equivalent examples for Linux or cross-platform environments. The only command-line example is Windows/PowerShell-specific, and there is no mention of Linux tools or Service Fabric CLI (sfctl), which is the recommended cross-platform tool.
Recommendations
- Add equivalent Linux/cross-platform examples using the Service Fabric CLI (sfctl), e.g., show how to retrieve partition health with sfctl partition health.
- Explicitly mention that the PowerShell example is for Windows and provide guidance for Linux/macOS users.
- Where possible, prefer cross-platform tools in documentation examples or present both Windows and Linux options side by side.
Service Fabric
Manage Azure Service Fabric app load using metrics
...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both C# and PowerShell examples for managing Service Fabric metrics, but exclusively uses PowerShell for CLI examples. There are no Linux/macOS CLI equivalents (such as Azure CLI or REST API examples), and PowerShell is presented before any mention of cross-platform tools. This creates friction for Linux/macOS users, as Service Fabric can be managed from non-Windows environments using Azure CLI or REST APIs, but these options are not shown.
Recommendations
- Add Azure CLI examples for creating and managing Service Fabric services and metrics, as Azure CLI is cross-platform.
- Include REST API examples for metric management, which are usable from any OS.
- Clarify which PowerShell commands are available cross-platform (PowerShell Core) and which are Windows-only.
- Present CLI examples in a more OS-neutral way, e.g., show Azure CLI first or alongside PowerShell.
- Explicitly mention Linux/macOS management options in the relevant sections.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed PowerShell examples for managing node tags and service tag requirements, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). PowerShell is primarily a Windows tool, and its exclusive use creates friction for non-Windows users. The C# API examples are platform-neutral, but command-line guidance is Windows-centric.
Recommendations
- Add Azure CLI or Bash examples for managing node tags and service tag requirements, if supported.
- Include REST API usage examples for tag operations, highlighting cross-platform compatibility.
- Clarify whether PowerShell commands are available on Linux/macOS (via PowerShell Core), or provide alternative instructions if not.
- Explicitly mention any limitations or differences for Linux/macOS clusters, if applicable.
Service Fabric
Azure Service Fabric standalone cluster scaling
...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing Windows PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific guide for adding/removing nodes. There are no Linux-specific examples, tools, or instructions provided, despite Service Fabric standalone clusters being theoretically deployable on non-Windows environments.
Recommendations
- Include Linux-specific instructions and examples for scaling standalone clusters, such as using CLI tools or scripts compatible with Linux.
- Document equivalent Linux commands or REST API approaches for querying and updating cluster manifests and configurations.
- Clarify whether standalone Service Fabric clusters are supported on Linux, and if so, provide parity in guidance and tooling.
- If Windows-only tools are required, explicitly state this limitation and provide guidance for Linux users where possible.
Service Fabric
Secure an Azure Service Fabric cluster
...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page discusses securing Azure Service Fabric clusters, covering both Azure-hosted and standalone Windows clusters. However, it repeatedly provides detailed guidance and links for Windows Server standalone clusters, while omitting equivalent instructions or links for Linux standalone clusters. Windows security options (Kerberos, Windows accounts) are described, but Linux-specific security patterns (such as Linux user accounts, certificate management, or integration with Linux authentication mechanisms) are not mentioned. The structure and examples consistently prioritize Windows, with Linux clusters only briefly referenced.
Recommendations
- Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
- Include Linux-specific examples for certificate creation, installation, and management (e.g., using OpenSSL, Linux file paths, and permissions).
- Clarify whether Linux standalone clusters support Windows security (Kerberos) or if only certificate-based security is available.
- Provide parity in recommendations and best practices for Linux environments, such as using Linux CA tools or integrating with Linux authentication systems.
- Ensure that references to 'standalone clusters' consistently specify whether instructions apply to Windows, Linux, or both.
Service Fabric
Upgrading Azure Service Fabric clusters
...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page on upgrading Azure Service Fabric clusters exhibits mild Windows bias. While most upgrade concepts are platform-neutral, sections such as 'Upgrading OS images for cluster nodes' and references to Patch Orchestration Application (POA) specifically mention Windows and link only to Windows patching documentation. Additionally, examples for managing certificates and opening application ports mention PowerShell/Azure CLI but do not clarify Linux/macOS parity or provide explicit Linux/macOS examples. Windows terminology (NTLM, FileStoreService) is referenced without Linux equivalents or clarifications.
Recommendations
- Add explicit Linux/macOS examples alongside PowerShell/Azure CLI instructions, or clarify that Azure CLI commands are cross-platform.
- Include links or guidance for patching Linux-based Service Fabric clusters, if supported.
- Clarify when features or instructions are Windows-specific and provide Linux alternatives or note limitations.
- Ensure documentation for certificate management, port opening, and node property configuration includes cross-platform tooling and examples.
Service Fabric
Azure Service Fabric application resource model
...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority
View Details →
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 notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI equivalents or Linux/macOS workflows. Application packaging instructions rely on Visual Studio, a Windows-centric tool, and do not provide alternative methods for Linux/macOS users. The sample application is .NET-based, but the packaging and deployment steps are presented in a Windows-first manner.
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, sfctl, or manual zip commands).
- Mention alternative editors or IDEs for Linux/macOS (e.g., VS Code) and how to package applications without Visual Studio.
- Clearly indicate when steps are Windows-only and offer Linux/macOS alternatives where possible.
- Consider including sample scripts or workflows for Linux/macOS environments.
Service Fabric
Learn more about Azure Service Fabric
...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation covers Azure Service Fabric concepts for both Windows and Linux, but there is a notable Windows bias. Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned before Linux equivalents, and Windows terminology (e.g., Windows service, FabricHost.exe) is used throughout. Examples and links for creating clusters and standalone clusters are Windows-first or Windows-only, with Linux standalone clusters explicitly unsupported. PowerShell is referenced as a primary management tool, with CLI and REST APIs mentioned but not emphasized. Linux parity is acknowledged, but Linux-specific instructions and examples are sparse or missing.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, management, and health monitoring.
- Mention Linux tools (e.g., Bash, Linux CLI usage) before or equally with Windows tools like PowerShell.
- Clarify which features are Windows-only and which are cross-platform, and provide links to Linux documentation where available.
- Add explicit guidance for Linux users in sections about application lifecycle, monitoring, and diagnostics.
- Include Linux-focused quickstarts and tutorials in the 'Next steps' section.
Service Fabric
Azure Service Fabric Docker Compose Deployment Preview
...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell examples are presented first and in greater detail, which may suggest a Windows-first bias. The CLI examples are provided as an alternative, but there is no explicit mention of Linux/macOS compatibility or guidance for non-Windows users. There are no Linux-specific examples or notes about using sfctl on Linux/macOS, and PowerShell is a Windows-centric tool (though available cross-platform, it is less commonly used on Linux).
Recommendations
- Explicitly state that sfctl is cross-platform and suitable for Linux/macOS users.
- Provide example commands for Linux/macOS environments (e.g., using Bash or zsh).
- Mention installation instructions for sfctl on Linux/macOS.
- Consider listing CLI examples before PowerShell, or at least equally, to avoid Windows-first impression.
- Add notes about PowerShell Core availability on Linux/macOS if relevant.
Service Fabric
Health monitoring in Service Fabric
...s/service-fabric/service-fabric-health-introduction.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users who cannot use PowerShell natively.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
- Include REST API examples for health reporting and querying, which are platform-agnostic.
- Mention that PowerShell examples are specific to Windows and provide links or instructions for Linux/macOS alternatives.
- Ensure that all critical tasks demonstrated with PowerShell are also shown with cross-platform tools.
Service Fabric
Azure Service Fabric Events
...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page for Azure Service Fabric Events primarily references Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent. There are no explicit examples or instructions for accessing Service Fabric events on Linux clusters, nor are Linux-native tools or patterns mentioned. Windows tools and patterns are referenced first and exclusively.
Recommendations
- Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, or Azure Monitor integration for Linux).
- Mention Linux-native monitoring tools or patterns where applicable, such as using Log Analytics agents for Linux or integrating with Linux-based log collectors.
- Clarify which features or instructions are Windows-only and provide Linux equivalents or note limitations for Linux clusters.
- Provide example commands or configuration snippets for both Windows and Linux environments.
Service Fabric
Package an existing executable to Azure Service Fabric
...abric/service-fabric-guest-executables-introduction.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. It references the Service Fabric SDK schema location using a Windows file path, mentions Visual Studio as a packaging tool without listing Linux alternatives, and does not provide Linux/macOS-specific guidance or examples. There are no explicit PowerShell examples, but Windows tools and patterns are mentioned first and exclusively. No Linux packaging tools or directory paths are shown, and the sample directory structure uses a Windows executable (.exe) as the example.
Recommendations
- Add Linux/macOS-specific instructions for packaging and deploying guest executables, including example directory paths and file extensions.
- Mention cross-platform tools (such as Azure CLI or Service Fabric CLI) alongside Visual Studio, and clarify which steps are possible on Linux/macOS.
- Provide sample manifests and directory structures using non-Windows binaries (e.g., .sh, .out) and note any platform-specific requirements.
- Reference the location of schema files for Service Fabric SDK on Linux/macOS, if available.
- Explicitly state if Visual Studio is required or if alternatives exist for Linux/macOS users.
Service Fabric
Azure Service Fabric image store connection string
...fabric/service-fabric-image-store-connection-string.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and links to a PowerShell-based deployment guide as the main 'Next steps'. While .NET and REST are mentioned, PowerShell is presented first and most prominently. There are no explicit Linux/macOS CLI or tooling examples (such as Azure CLI, Bash, or cross-platform scripts), and no mention of Linux-specific workflows or tools, despite Service Fabric supporting Linux clusters.
Recommendations
- Add Azure CLI or Bash examples for retrieving the cluster manifest and deploying applications, highlighting cross-platform workflows.
- Include links to Linux/macOS documentation or guides for Service Fabric cluster management.
- Present .NET, REST, and cross-platform options alongside PowerShell, rather than PowerShell-first.
- Clarify that PowerShell examples are applicable on Linux/macOS via PowerShell Core, if relevant, or provide alternative commands.
Service Fabric
Azure Service Fabric container application manifest examples
...abric/service-fabric-manifest-example-container-app.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page provides Service Fabric container application manifest examples that are based on a Windows Server 2016 container sample. Windows-specific tools and patterns (such as 'winver' and Windows path formats) are referenced before or instead of Linux equivalents. There is little to no mention of Linux-specific guidance or parity in the manifest examples or explanations, despite Service Fabric supporting Linux containers.
Recommendations
- Provide equivalent manifest examples or notes for Linux-based Service Fabric clusters and containers.
- When referencing OS-specific commands (e.g., 'winver'), also mention the Linux equivalent (e.g., 'cat /etc/os-release' or 'uname -r').
- Clarify when features or settings are Windows-only, and highlight any differences or limitations for Linux clusters.
- Use platform-neutral path formats or provide both Windows and Linux path examples where relevant (e.g., for volume mounts).
- Explicitly state whether the manifest examples are portable to Linux clusters, and if not, provide Linux-specific samples.
Service Fabric
Specifying Service Fabric service endpoints
...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. The only command-line deployment example is given in PowerShell, and the use of Windows file paths and certificate store names (e.g., 'C:\Program Files\...', 'MY' store) is prevalent. While there is a brief note about the Linux certificate store location, Linux-specific deployment commands or examples are missing. Windows tools and patterns are referenced first and more thoroughly.
Recommendations
- Provide equivalent Linux CLI examples (e.g., using Azure CLI or sfctl) alongside PowerShell commands for deploying applications with ApplicationParameters.
- Clarify how to specify certificate stores and paths for Linux clusters, including more explicit examples.
- When referencing file paths or tools, include both Windows and Linux equivalents where applicable.
- Consider reordering or parallelizing examples so that Linux and Windows usage are presented with equal prominence.
Service Fabric
Manage apps for multiple environments
...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for managing application parameters in Azure Service Fabric, with a notable emphasis on PowerShell and Visual Studio workflows, which are Windows-centric. While sfctl (a cross-platform CLI) is mentioned, Windows tools and patterns (PowerShell, Visual Studio, Deploy-FabricApplication.ps1) are listed first and described in more detail, with less explicit guidance for Linux/macOS users.
Recommendations
- Provide Linux/macOS-specific examples and workflows, such as using sfctl and install.sh, with step-by-step instructions.
- Ensure parity in documentation by describing how to use parameter files and scripts on Linux/macOS, not just in Visual Studio or PowerShell.
- List cross-platform tools (sfctl, install.sh) before Windows-specific tools to avoid implicit prioritization.
- Clarify which scripts or tools are available and supported on Linux/macOS, and provide links to relevant documentation.
Service Fabric
Add custom Service Fabric health reports
...rticles/service-fabric/service-fabric-report-health.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides detailed PowerShell examples for health reporting and cluster connection, but does not offer equivalent examples for Linux/macOS users (e.g., Bash/CLI). PowerShell is presented as the primary scripting interface, and Windows-style paths/prompts are used. REST and API options are mentioned, but practical Linux-oriented command-line examples are missing.
Recommendations
- Add Azure CLI or Bash script examples for health reporting and cluster connection, demonstrating parity with PowerShell.
- Explicitly mention cross-platform tools (e.g., Azure CLI, Service Fabric CLI) and provide usage instructions for Linux/macOS.
- Clarify which PowerShell commands are available via cross-platform PowerShell Core, and note any Windows-only limitations.
- Reorder or balance examples so that REST/CLI approaches are shown before or alongside PowerShell, to avoid Windows-first impression.
Service Fabric
Define Service Configuration in StartupServices.xml for a Service Fabric Application
...service-fabric/service-fabric-startupservices-model.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented toward Visual Studio workflows, referencing Windows-specific build and deployment actions (Build/Rebuild/F5/Ctrl+F5/Publish) and UI elements. There are no examples or guidance for Linux/macOS users, nor mention of cross-platform tooling or alternatives to Visual Studio. The only alternative deployment methods referenced are ARM templates and PowerShell cmdlets, but these are not explained in detail or shown with Linux-compatible tools.
Recommendations
- Add explicit guidance for Linux/macOS users, including how to manage StartupServices.xml outside Visual Studio.
- Provide examples using cross-platform tools (e.g., Azure CLI, Service Fabric CLI) for deployment and configuration.
- Clarify which features are Visual Studio/Windows-only and suggest Linux/macOS alternatives where possible.
- Include sample workflows for editing and deploying StartupServices.xml on Linux/macOS environments.
Service Fabric
Fault Analysis Service overview
.../service-fabric/service-fabric-testability-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page provides usage instructions for the Fault Analysis Service in Service Fabric, mentioning C# and PowerShell as the primary ways to interact with the service. PowerShell is a Windows-centric tool, and no Linux or cross-platform CLI examples (such as Bash, Azure CLI, or REST API) are provided. There is no mention of Linux-compatible tools or patterns, nor guidance for Linux/macOS users on how to use the Fault Analysis Service.
Recommendations
- Add examples for using the Fault Analysis Service via Azure CLI, REST API, or Bash scripts, if available.
- Clarify whether the Fault Analysis Service APIs can be accessed from Linux/macOS environments, and provide guidance for those platforms.
- If PowerShell Core (cross-platform) is supported, mention it explicitly and provide relevant examples.
- Include information about any limitations or prerequisites for Linux/macOS users.
Service Fabric
Service Fabric Explorer blocking operations
...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page primarily references Az PowerShell cmdlets for managing Service Fabric resources, with explicit links to PowerShell modules and commands. While the az CLI is mentioned for deleting applications, PowerShell is consistently presented first and in more detail. There are no explicit Linux/macOS examples or references to Bash or cross-platform CLI usage, which may create friction for non-Windows users.
Recommendations
- Provide equivalent az CLI examples for all operations (e.g., unprovisioning application type versions, creating applications/services).
- Mention that az CLI is cross-platform and suitable for Linux/macOS users.
- Add Bash shell examples alongside PowerShell where relevant.
- Clarify that ARM templates and az CLI can be used from any OS.
Service Fabric
RunToCompletion semantics and specifications
...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page presents RunToCompletion semantics in Service Fabric with a strong Windows bias. All code examples use Windows containers (nanoserver:1809), Windows-specific commands (cmd, echo, ping, set, exit), and reference Windows container compatibility. Querying deployment status is shown only via PowerShell and C# APIs, with no mention of Linux equivalents or cross-platform CLI tools. There are no examples or guidance for Linux containers or Linux-based workflows.
Recommendations
- Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
- Clarify whether RunToCompletion semantics are supported for Linux containers and provide guidance if so.
- Include cross-platform CLI examples (e.g., Azure CLI, sfctl) for querying deployment status, not just PowerShell.
- Mention any limitations or differences for Linux users explicitly.
- If RunToCompletion is Windows-only, state this clearly at the top to avoid confusion.
Service Fabric
Deploy and upgrade with Azure Resource Manager
...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides PowerShell examples for removing Service Fabric application resources, but does not offer equivalent CLI or Linux/macOS-friendly examples. PowerShell is mentioned as the primary tool for post-deployment management, and the CLI is referenced only as an alternative in the 'Next steps' section. This creates friction for Linux/macOS users who may prefer or require cross-platform tools.
Recommendations
- Add Azure CLI examples alongside PowerShell for resource removal and management tasks.
- Explicitly mention that both PowerShell and CLI are supported for these operations, and provide links to relevant CLI documentation.
- Ensure that cross-platform tools (e.g., Service Fabric CLI, Azure CLI) are referenced equally and not only as secondary options.
- Consider including REST API examples where appropriate, as these are platform-agnostic.
Service Fabric
Architecture of Azure Service Fabric
...articles/service-fabric/service-fabric-architecture.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation mentions PowerShell cmdlets as a primary management interface for Service Fabric, without referencing equivalent Linux/macOS tooling (such as Azure CLI or REST APIs). Additionally, Windows security is mentioned alongside X509 certificates in the transport subsystem, with no discussion of Linux authentication mechanisms. These patterns suggest a Windows-first bias, though the architectural content is largely platform-neutral.
Recommendations
- Add examples or references to Linux/macOS management tools, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
- Clarify whether management operations can be performed from non-Windows environments and provide guidance for Linux/macOS users.
- Mention authentication mechanisms commonly used on Linux (e.g., SSH, certificate-based auth) if relevant, or clarify platform support.
- Ensure that platform-neutral language is used where possible, and avoid implying PowerShell is the only supported management interface.
Service Fabric
Service Fabric Cluster Resource Manager: Movement cost
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides PowerShell examples for configuring move cost in Service Fabric, but does not offer equivalent Linux CLI or Bash examples. PowerShell is presented first in each example section, followed by C#. There is no mention of Linux tools or cross-platform CLI alternatives, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
- Add Azure CLI or Bash examples for configuring and updating move cost, where possible.
- Mention whether PowerShell commands are supported on Linux/macOS, or provide guidance for Linux users.
- Consider presenting cross-platform CLI examples before or alongside PowerShell examples.
- Clarify if certain operations are Windows-only, or provide links to Linux-specific documentation if available.