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 126-150 of 2475 flagged pages
Service Fabric
Describing Azure Service Fabric apps and services
...ic/service-fabric-application-and-service-manifests.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation contains a notable Windows bias in its guidance for validating manifest XML schemas. It exclusively recommends opening the schema file in Visual Studio at a Windows-specific path (C:\Program Files\...), with no mention of Linux/macOS equivalents or cross-platform tools. Additionally, the PowerShell module is referenced before any mention of cross-platform alternatives for service creation, though this is minor.
Recommendations
- Provide instructions or examples for validating manifest XML schemas using cross-platform editors (e.g., VS Code with XML extensions) or command-line tools available on Linux/macOS.
- Mention the location of the ServiceFabricServiceModel.xsd schema file on Linux clusters, or clarify if it is not available.
- When referencing the Service Fabric PowerShell module, also mention cross-platform alternatives (such as Azure CLI or REST API) for service management, if available.
- Consider reordering examples or providing parallel instructions for Linux/macOS users where applicable.
Create Pull Request
Service Fabric
Application lifecycle in Service Fabric
...service-fabric/service-fabric-application-lifecycle.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., PowerShell commands, .NET APIs) throughout critical lifecycle operations (deploy, upgrade, remove, cleanup). While REST API and .NET method alternatives are sometimes mentioned, Linux-friendly tools (such as Azure CLI or sfctl) are not referenced in the main procedural steps, and no Linux/macOS-specific examples or guidance are provided. PowerShell commands are often listed before REST API options, reinforcing a Windows-first bias.
Recommendations
- Add examples and procedural steps using Azure CLI and sfctl for all major lifecycle operations (deploy, upgrade, remove, cleanup).
- Explicitly mention Linux/macOS compatibility for REST API and CLI tools.
- Where PowerShell is referenced, provide equivalent Linux/macOS command-line instructions (e.g., bash, sfctl, Azure CLI).
- Reorder examples so that cross-platform tools (REST API, CLI) are listed before or alongside PowerShell.
- Include a section or note clarifying which tools are available on Linux/macOS and how to perform common tasks without PowerShell.
Service Fabric
Capacity planning and scaling for Azure Service Fabric
...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides several critical operational examples (such as scaling in/out nodes) exclusively using PowerShell commands, with no equivalent Linux/bash/CLI examples. This creates friction for Linux users, who must translate PowerShell steps to their platform without guidance.
Recommendations
- For every PowerShell command (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState), provide equivalent Azure CLI or Service Fabric CLI (sfctl) commands, or at least mention them.
- Add explicit Linux/bash examples for common scaling workflows, or link to relevant Linux/CLI documentation.
- Clarify in each section whether the steps are OS-agnostic or if there are differences for Linux clusters.
- Where C# SDK examples are given, note if they are cross-platform, and if not, provide a Linux-compatible alternative or guidance.
Service Fabric
Service Fabric application upgrade
...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page for Service Fabric application upgrade presents PowerShell examples exclusively and references Windows-specific tools (e.g., http.sys, Windows HTTP Server API). There are no Linux or cross-platform CLI examples, and the upgrade process is described primarily in terms of Windows tooling and APIs. This creates friction for Linux/macOS users, as Service Fabric supports Linux clusters and the Azure CLI and REST APIs are available for cross-platform management.
Recommendations
- Add equivalent examples using Azure CLI, REST API, or Service Fabric CLI (sfctl) for application upgrades, especially for retrieving and passing application parameters.
- Clarify which features or steps are Windows-only (e.g., http.sys, Windows HTTP Server API) and provide Linux-specific guidance or alternatives where applicable.
- Include notes or sections for Linux/macOS users, highlighting any differences in upgrade procedures or tooling.
- Ensure that references to PowerShell or Windows tools are balanced with cross-platform options, or at least mention their existence.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page primarily references Windows-centric tools and patterns, such as Visual Studio and PowerShell, in the 'Next steps' section. Linux equivalents (e.g., CLI, Bash, cross-platform editors) are not mentioned, and PowerShell is presented as the only scripting example. The serialization guidance is focused on C# and .NET, which is cross-platform, but the upgrade workflow references Windows tools first and exclusively.
Recommendations
- Add instructions or links for upgrading applications using Azure CLI or Bash scripts, which are cross-platform.
- Mention cross-platform editors (e.g., VS Code) alongside Visual Studio for application upgrades.
- Clarify if PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide Bash/CLI alternatives.
- Ensure that Linux/macOS users are guided to equivalent workflows and tools for Service Fabric application upgrades.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page for on-demand backup in Azure Service Fabric demonstrates notable Windows bias. All code examples use PowerShell, and the prerequisite is to install a PowerShell module. There are no examples or guidance for Linux/macOS users (e.g., Bash, curl, or cross-platform tools). The REST API is only shown via PowerShell, and Windows-centric tools are mentioned exclusively and first.
Recommendations
- Add equivalent Bash/curl examples for REST API calls to support Linux/macOS users.
- Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available or supported on PowerShell Core (pwsh) for Linux/macOS, or provide alternatives.
- Mention cross-platform tools (such as Azure CLI or direct REST calls) where possible.
- Include a note about Linux/macOS support and any limitations, if applicable.
- Reorder sections or provide parallel examples so Linux/macOS users are not forced to adapt Windows-centric instructions.
Service Fabric
Restoring backup in Azure Service Fabric
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page for restoring backup in Azure Service Fabric exclusively uses PowerShell for all command-line examples and references the Microsoft.ServiceFabric.Powershell.Http module, which is a Windows-centric tool. No Linux/macOS CLI or REST API examples using cross-platform tools (such as curl or Azure CLI) are provided. All scripting and automation guidance assumes a Windows environment, creating friction for Linux/macOS users.
Recommendations
- Add equivalent examples using cross-platform tools such as curl for REST API calls.
- Provide Azure CLI examples where possible, as Azure CLI is supported on Windows, Linux, and macOS.
- Clarify whether the PowerShell module is supported on PowerShell Core (pwsh) for Linux/macOS, and if so, provide installation and usage instructions for those platforms.
- Include explicit guidance for Linux/macOS users, such as how to authenticate and make REST calls without PowerShell.
- Mention any limitations or requirements for Linux/macOS environments if certain features are Windows-only.
Service Fabric
Azure Service Fabric security best practices
...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux guidance for key security tasks, but Windows-specific tools and examples (e.g., PowerShell, Windows Defender, Windows security baselines) are often presented first or exclusively. Windows-centric terminology and recommendations (such as Windows Defender and DSC) are included without Linux equivalents or alternatives. However, Linux-specific instructions are present for certificate creation and secret encryption, and links to Linux cluster creation are provided.
Recommendations
- Where Windows-specific tools (e.g., PowerShell, Windows Defender, DSC) are mentioned, add equivalent Linux guidance or clarify if no Linux equivalent exists.
- Present Windows and Linux examples side-by-side or in parallel sections, rather than Windows-first.
- For sections like 'Windows security baselines' and 'Windows Defender', explicitly state if there are Linux alternatives (e.g., CIS Linux benchmarks, common Linux antimalware solutions) or clarify that these are Windows-only.
- Ensure Linux-specific terminology and tools are referenced where appropriate (e.g., SELinux, AppArmor, Linux firewall tools).
- Add links to Linux security best practices for Azure workloads where relevant.
Service Fabric
Change Azure Service Fabric cluster settings
...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation covers Service Fabric cluster settings for both Azure-hosted and standalone clusters. While the content is largely platform-neutral, there are several areas where Windows terminology and tools are referenced first or exclusively. For example, certificate store names default to "My" and store locations like "LocalMachine", which are Windows-centric. Some parameters reference Windows-specific concepts (e.g., NTLM authentication, Windows Defender Firewall, and Windows-only log file settings). Additionally, links and guidance for standalone clusters point to Windows Server documentation, with no explicit mention of Linux standalone clusters or parity for Linux tools and patterns.
Recommendations
- Where certificate store names or locations are referenced, clarify Linux equivalents (e.g., file system paths, openssl usage, etc.).
- Add explicit examples or guidance for Linux standalone clusters, including how to update ClusterConfig.json and perform configuration upgrades on Linux.
- When referencing NTLM, Windows Defender Firewall, or other Windows-specific features, note their applicability and provide Linux alternatives or state if not supported.
- Ensure that links and guidance for standalone clusters include Linux documentation or clarify if only Windows is supported.
- Review default values and terminology (e.g., 'My', 'LocalMachine') and provide Linux equivalents where appropriate.
Service Fabric
Service Fabric Cluster Resource Manager - Placement Policies
...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides code examples in C# and PowerShell for configuring Service Fabric placement policies. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or REST API) are provided. The PowerShell examples are given alongside C# code, but there is no mention of how Linux users can perform these tasks, nor are Linux-friendly tools referenced. The documentation implicitly assumes Windows environments for operational tasks.
Recommendations
- Add Azure CLI examples for configuring placement policies, as Azure CLI is cross-platform.
- Mention REST API options for placement policy configuration, if available.
- Clarify whether these PowerShell commands can be run on PowerShell Core (cross-platform) or only Windows PowerShell.
- Provide guidance for Linux/macOS users on how to configure these policies without relying on Windows tools.
- Consider including YAML or ARM template snippets if relevant for cross-platform deployment scenarios.
Service Fabric
Azure Service Fabric infrastructure as Code Best Practices
...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell examples are given equal prominence despite PowerShell being primarily a Windows tool. In the cluster upgrade section, only PowerShell commands are provided for manual upgrades, with no Linux/bash equivalents. Windows registry keys and Windows Update configuration are discussed without mentioning Linux alternatives or clarifying Linux applicability. Windows-specific configuration is described before Linux, and Windows tools are referenced more frequently.
Recommendations
- Add bash or Linux shell equivalents for manual cluster upgrade commands (currently only PowerShell is shown).
- Clarify which steps are Windows-only and provide Linux-specific guidance where applicable (e.g., for OS upgrades and update management).
- When referencing Windows registry keys or Windows Update settings, explicitly state if these are not relevant for Linux clusters and provide Linux alternatives if available.
- Ensure Linux examples are given equal prominence, not just linked in 'Next steps', but integrated throughout the documentation.
- Consider adding a table or section summarizing differences between Windows and Linux cluster management for clarity.
Service Fabric
Node types and virtual machine scale sets
...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page discusses Azure Service Fabric node types and their relationship to virtual machine scale sets. While it mentions both Windows and Linux node types in the extension configuration, there is a subtle bias toward Windows: the JSON snippet uses a Windows-style path ('D:\\SvcFab') for the 'dataPath' property, and the 'Next steps' section links to PowerShell scripts for changing RDP port ranges and admin credentials, which are Windows-specific tasks. No Linux-specific examples or guidance are provided for equivalent operations, and Windows terminology (RDP, PowerShell) appears without Linux alternatives.
Recommendations
- Provide Linux-specific examples for 'dataPath' (e.g., '/var/svcfab') and clarify OS-specific configuration differences.
- Add guidance or links for connecting to Linux nodes (e.g., SSH instructions) alongside RDP/PowerShell content.
- Include Linux-focused scripts or documentation for changing admin credentials and port ranges.
- Ensure that both 'ServiceFabricNode' (Windows) and 'ServiceFabricLinuxNode' (Linux) are equally represented in examples and explanations.
Service Fabric
Service Fabric Cluster Resource Manager - Application Groups
...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page provides all command-line examples using PowerShell cmdlets (e.g., New-ServiceFabricApplication, Update-ServiceFabricApplication), which are Windows-specific tools. There are no equivalent examples for Linux/macOS environments (such as Azure CLI, REST API, or cross-platform Service Fabric tools). This creates friction for Linux users, as they cannot directly follow the examples unless they use Windows or adapt the instructions themselves.
Recommendations
- Add Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform.
- Include REST API sample requests for application creation, update, and querying load information.
- Mention and link to any cross-platform Service Fabric management tools or SDKs.
- Clarify which features are available on Linux clusters and note any Windows-only limitations.
- Consider showing cross-platform examples before or alongside PowerShell examples.
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-specific (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json) configuration examples. However, Windows/PowerShell examples are often presented first or exclusively, and the XML configuration is shown only for WindowsServer clusters, with no explicit Linux configuration example. PowerShell is the only CLI example given, with no Bash or Linux-native CLI equivalents. The documentation does not mention Linux node configuration or Linux-specific tools, even though Service Fabric supports Linux clusters.
Recommendations
- Add explicit Linux cluster configuration examples, such as ClusterManifest.xml for Linux or relevant Linux-specific settings.
- Provide Bash or Linux-native CLI examples alongside PowerShell, such as using sfctl (Service Fabric CLI) for service creation and updates.
- Clarify that ClusterConfig.json and Template.json are cross-platform, and note any differences for Linux deployments.
- Include guidance or links for Linux users on how to set up and manage Service Fabric clusters, node properties, and placement constraints.
- Ensure that examples and explanations are not Windows-first; alternate or parallel Linux examples should be provided.
Service Fabric
Azure Service Fabric Auto Scaling Services and Containers
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using Application Manifest, C# APIs, and PowerShell. However, all scripting examples are PowerShell-based, which is primarily a Windows tool. There are no equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API). Additionally, PowerShell examples are given equal prominence to C# and manifest examples, and there is no mention of cross-platform command-line alternatives. This creates friction for Linux users, especially since Service Fabric supports Linux containers and clusters.
Recommendations
- Add Azure CLI or Bash script examples for configuring scaling policies, especially for Linux-based clusters.
- Explicitly mention whether PowerShell examples are usable on Linux (e.g., via PowerShell Core), or provide guidance for Linux users.
- Include REST API examples for scaling operations, which are platform-agnostic.
- Clarify any platform-specific limitations in scripting or tooling, and provide links to Linux-specific documentation where relevant.
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 only PowerShell is shown for CLI-based operations. There are no Linux/macOS equivalents (such as Azure CLI or Bash examples), and PowerShell is presented as the primary scripting method, which may create friction for Linux/macOS users. The documentation does not mention cross-platform tools or alternatives, and PowerShell examples are given before any Linux-friendly options.
Recommendations
- Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash scripting examples where applicable, or reference REST API calls for metric management.
- Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users.
- Document any limitations or differences for Linux/macOS users in Service Fabric management.
- Consider referencing Service Fabric SDK tools that are available for Linux/macOS, if relevant.
Service Fabric
Cluster Resource Manager - Management Integration
...fabric-cluster-resource-manager-management-integration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides a PowerShell example for querying Service Fabric partition health, using Windows-specific command syntax (PS C:\Users\User > Get-ServiceFabricPartitionHealth). No equivalent Linux/macOS CLI or REST API example is provided. The example is presented early in the page, potentially creating friction for non-Windows users. However, the rest of the documentation is platform-neutral, focusing on concepts and configuration files.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
- Mention REST API alternatives for health queries, with example requests.
- Clarify that PowerShell is one option, and provide links or references to cross-platform tools.
- Where possible, show both Windows and Linux/macOS command examples side-by-side.
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 on scaling Azure Service Fabric standalone clusters predominantly references Windows tools and PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without mentioning Linux equivalents or providing cross-platform guidance. There are no examples or instructions for Linux users, and the linked 'scale a standalone cluster' page appears to be Windows Server-focused, implying that Linux users may lack clear guidance for cluster scaling operations.
Recommendations
- Include instructions and examples for scaling Service Fabric standalone clusters on Linux, if supported.
- Mention and link to any Linux-specific tools or commands for cluster management.
- Clarify whether standalone clusters can be managed on Linux, and if not, explicitly state Windows-only support.
- Provide parity in documentation structure, ensuring Linux/macOS users can follow equivalent steps.
- If PowerShell is required, note any cross-platform alternatives or limitations.
Service Fabric
Service sensitivity
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides PowerShell API examples for configuring service sensitivity and maximum load, but does not offer equivalent CLI or scripting examples for Linux/macOS users. It assumes the use of Windows-native tools (PowerShell, C# APIs) without mentioning cross-platform alternatives or clarifying platform requirements. This creates friction for Linux administrators managing Service Fabric clusters.
Recommendations
- Clarify whether the PowerShell commands are supported on Linux/macOS (e.g., via PowerShell Core), or provide equivalent examples using Azure CLI, REST API, or other cross-platform tools.
- Explicitly state any platform requirements for the Service Fabric management APIs.
- Add guidance for Linux/macOS users on how to perform these tasks, including references to supported tools and workflows.
- If only Windows tools are supported, clearly indicate this limitation to set user expectations.
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, but does not include equivalent Linux/bash/CLI examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. The C# examples are cross-platform, but the lack of Linux-native command-line instructions (such as Azure CLI or bash) means Linux users may struggle to perform basic operations without additional research.
Recommendations
- Add Azure CLI or bash examples for creating and updating Service Fabric services with move cost settings.
- Explicitly mention whether PowerShell Core (cross-platform) is supported, or provide guidance for Linux users.
- Clarify if certain operations are only possible via PowerShell or C#, or provide links to Linux/macOS-compatible tools.
- Consider adding a table or section comparing Windows and Linux approaches for service management.
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 primarily discusses security scenarios for Azure Service Fabric clusters, but consistently references Windows Server for standalone clusters and omits explicit guidance or examples for standalone Linux clusters. Windows security (Kerberos) is described in detail, while Linux equivalents (such as certificate-based authentication or Linux user/group management) are not mentioned. Links and instructions for standalone clusters are exclusively for Windows, and certificate creation advice is Windows-centric (e.g., Windows Server certificate service, MakeCert.exe).
Recommendations
- Add explicit guidance and examples for securing standalone Service Fabric clusters running on Linux, including certificate setup and client authentication.
- Provide links to Linux-specific documentation or tools for certificate creation and management (e.g., OpenSSL).
- Clarify whether standalone Linux clusters are supported and, if so, how their security setup differs from Windows clusters.
- Balance references to Windows tools (like MakeCert.exe) with Linux alternatives (such as OpenSSL or certbot).
- Include Linux user/group-based authentication options if available, or explicitly state if only certificate-based authentication is supported for Linux.
Service Fabric
Azure Service Fabric DNS service
...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority
View Details →
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 (e.g., Bash, Azure CLI) examples. Windows tools and patterns (PowerShell, ApplicationManifest.xml in Visual Studio) are mentioned before Linux alternatives, and Linux-specific limitations are highlighted without guidance or parity. There are no Linux-specific walkthroughs for enabling DNS service or managing DNS names, and portal-based instructions are Windows-centric.
Recommendations
- Add Azure CLI or Bash examples for managing Service Fabric services and setting DNS names, especially for Linux clusters.
- Clarify how Linux users can set DNS names (e.g., via ARM templates, Azure CLI, or other supported methods).
- Provide explicit instructions and examples for enabling DNS service on Linux clusters, including workarounds for portal limitations.
- Mention Linux-compatible editors and workflows when referencing ApplicationManifest.xml (e.g., VS Code, nano, vim).
- Ensure that Linux limitations are accompanied by actionable alternatives or links to relevant Linux documentation.
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 Windows directory paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd'), and mentions Visual Studio as a packaging tool without listing Linux alternatives or command-line options. There are no explicit Linux/macOS examples or instructions, and the directory structure and file naming conventions are Windows-centric. However, the content does not restrict the guidance to Windows-only features, and Service Fabric itself supports Linux clusters.
Recommendations
- Add explicit Linux/macOS instructions and examples for packaging and deploying guest executables.
- Mention cross-platform tools (such as Azure CLI or Service Fabric CLI) and provide sample commands for Linux/macOS.
- Reference Linux file paths and installation locations for the Service Fabric SDK and schema files.
- Clarify that guest executables can be packaged and deployed from Linux/macOS environments, not just Windows/Visual Studio.
Service Fabric
Scalability of Service Fabric services
.../service-fabric/service-fabric-concepts-scalability.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides code examples and administrative instructions primarily in PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or scripting examples (e.g., Bash, Azure CLI) for scaling Service Fabric services. Windows tools (PowerShell cmdlets) are mentioned first and exclusively, creating friction for Linux users who may need to perform similar tasks. The only explicit mention of Linux is in the platform comparison section, but it does not provide Linux-specific operational guidance.
Recommendations
- Add Linux-friendly examples using Bash scripts or Azure CLI commands for scaling operations.
- Mention and link to Linux-specific Service Fabric management tools and documentation.
- Where PowerShell cmdlets are referenced, provide equivalent Azure CLI or REST API examples for cross-platform parity.
- Clarify which operations are supported on Linux clusters and provide guidance for Linux users.
- Consider restructuring examples so that Windows and Linux approaches are presented side-by-side.
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 provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) and processes are often mentioned first or exclusively, and several examples reference Windows executables and services. Linux equivalents are sometimes referenced, but often after Windows or in less detail. Some sections (e.g., standalone clusters) are Windows-only, with Linux support explicitly noted as unavailable. CLI tools and REST APIs are mentioned, but PowerShell is frequently highlighted. There are few explicit Linux command examples or Linux-centric workflows.
Recommendations
- Ensure Linux and cross-platform examples are provided alongside Windows/PowerShell examples, especially for cluster management and health monitoring.
- Mention Linux CLI tools (e.g., sfctl) and workflows before or alongside Windows tools.
- Add explicit Linux instructions or links for tasks where Linux is supported (e.g., cluster creation, application lifecycle).
- Clarify when a feature or example is Windows-only, and provide Linux alternatives or workarounds where possible.
- Balance references to Visual Studio with Linux-friendly IDEs or command-line approaches.