Service Fabric
407
Total Pages
336
Linux-Friendly Pages
71
Pages with Bias
17.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
1235 issues found
Showing 76-100 of 1235 flagged pages
Service Fabric
Service Fabric application upgrade
...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation for Service Fabric application upgrades demonstrates a notable Windows bias. PowerShell is used exclusively in code examples, and Windows-specific tools (e.g., http.sys) are referenced without Linux equivalents. There are no CLI or Linux-native examples, and PowerShell-based upgrade instructions are presented first and exclusively. This creates friction for Linux/macOS users, who may use Service Fabric clusters on Linux or need cross-platform automation.
Recommendations
- Add equivalent Azure CLI or Service Fabric CLI (sfctl) examples for all PowerShell commands, especially for application parameter retrieval and upgrade operations.
- Explicitly mention cross-platform tools and workflows where possible, and clarify any Windows-only limitations.
- When referencing Windows-specific components (e.g., http.sys), provide Linux equivalents or note if the limitation is Windows-only.
- Reorder or parallelize examples so that Linux/macOS and Windows instructions are presented together or with equal prominence.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on PowerShell and the Microsoft.ServiceFabric.Powershell.Http module, with all command-line examples using PowerShell syntax and cmdlets. There are no equivalent examples for Linux/macOS users (e.g., using Bash, curl, or cross-platform Service Fabric CLI tools). The only alternative mentioned is Service Fabric Explorer (a web UI), but no guidance is provided for Linux command-line users.
Recommendations
- Provide equivalent examples using Bash and curl for REST API calls, including certificate authentication steps for Linux/macOS.
- Mention and demonstrate the use of cross-platform Service Fabric CLI tools (if available) for backup operations.
- Clarify in the prerequisites whether the PowerShell module is supported on PowerShell Core (pwsh) on Linux/macOS, or if it is strictly Windows-only.
- Add a section or callout for Linux/macOS users explaining how to perform on-demand backups without relying on Windows-specific tools.
Service Fabric
Understanding periodic backup configuration
...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally platform-neutral, focusing on Azure Service Fabric's backup configuration concepts and REST APIs. However, in the 'File share' backup storage section, examples and instructions exclusively reference Windows-style file shares (\\StorageServer\BackupStore) and Integrated Windows Authentication, without mentioning or providing Linux-compatible alternatives (such as SMB mounting on Linux or NFS). The documentation also describes Windows authentication patterns first and does not clarify Linux support or provide parity guidance.
Recommendations
- Add explicit guidance for Linux clusters, including how to configure file share backup storage using SMB or NFS mounts on Linux.
- Provide examples for mounting and accessing file shares from Linux nodes, including authentication options (e.g., username/password, Kerberos).
- Clarify whether Integrated Windows Authentication is required or if Linux-compatible authentication methods are supported.
- Mention any limitations or considerations for Linux clusters regarding file share backup storage.
- If file share backup is Windows-only, state this clearly to avoid confusion.
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 Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Resource Manager templates, but PowerShell is featured prominently and used for cluster upgrade operations without Linux shell equivalents. Windows-specific tools and registry keys are mentioned for VM patching, and PowerShell is used exclusively for manual cluster upgrades. Windows configuration properties are shown before Linux equivalents, and Linux-specific guidance is less detailed.
Recommendations
- Add Bash or Linux shell equivalents for manual cluster upgrade steps (e.g., using deb packages and Linux commands).
- Provide Linux-specific VM configuration examples, such as disabling automatic updates for Linux VMs.
- Include Linux registry/configuration guidance where relevant, or clarify when steps are Windows-only.
- Ensure Linux examples are given equal prominence and detail as Windows examples, especially for upgrade and patching scenarios.
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
Missing Linux Example
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias in several areas. Windows terminology (e.g., 'Windows Fabric', 'Windows only') is used in parameter descriptions, and Windows certificate store names ('MY', 'LocalMachine') are referenced without Linux equivalents or clarification. Some settings (e.g., NTLM authentication, Windows Update integration, log file settings) are marked as 'Windows only' or default to Windows values, with Linux-specific guidance missing or less prominent. The introductory guidance and links reference Windows standalone clusters before Linux, and Linux-specific settings (like certificate folders or executable paths) are less visible or explained. No explicit Linux examples or parity guidance are provided for settings that differ between platforms.
Recommendations
- Add Linux-specific examples and guidance for settings where behavior or defaults differ (e.g., certificate stores, log file locations, NTLM authentication).
- Clarify which parameters are Windows-only and which are cross-platform, and provide Linux equivalents or alternatives where possible.
- Ensure Linux terminology and paths are shown alongside Windows ones, especially for certificate management and file paths.
- Add explicit notes or tables summarizing platform-specific differences for key settings.
- Review introductory guidance and links to ensure Linux clusters are referenced equally and not only after Windows.
- Where settings are marked 'Windows only', provide Linux alternatives or state if the feature is unavailable.
Service Fabric
Azure Service Fabric networking best practices
...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides both Windows and Linux guidance in several areas, but there are notable Windows biases. Windows/PowerShell examples and terminology are often presented first or exclusively (e.g., PowerShell APIs, Windows container networking, ARM template samples for Windows clusters). Some explanations reference Windows-specific tools (e.g., netsh, PowerShell) without Linux equivalents. Linux examples are sometimes missing or less detailed, and Windows-centric scenarios (like patching) are described in more depth.
Recommendations
- Ensure Linux examples (e.g., CLI commands, Linux container networking) are provided alongside Windows/PowerShell examples.
- Where PowerShell or Windows tools are mentioned, add equivalent Linux commands (e.g., show dynamic port range on Linux).
- Balance the order of examples and explanations so Linux is not consistently secondary.
- Expand Linux-specific best practices, such as patching, monitoring, and application networking.
- Provide ARM template samples for Linux clusters with NSG setup, not just Windows.
- Clarify when guidance is Windows-only and provide Linux alternatives where possible.
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 examples (e.g., PowerShell commands, Windows Defender, Windows security baselines) are often presented first or in greater detail. Windows tools and terminology (PowerShell, Windows Defender, DSC) are mentioned exclusively or before Linux equivalents. Some sections (e.g., Windows Defender, Windows security baselines) are Windows-only, but these are clearly marked as such. Linux examples are present for certificate generation and secret encryption, but Windows examples are more prominent and detailed.
Recommendations
- Ensure Linux examples are presented alongside Windows examples, not after them, and with equal prominence.
- Where possible, provide Linux equivalents for security baseline guidance (e.g., reference CIS Linux benchmarks or Azure Linux security extensions).
- Add clarifying notes when a feature or tool is Windows-only, and link to Linux alternatives or best practices.
- For sections like certificate management and secret encryption, ensure Linux instructions are as detailed as Windows instructions.
- Consider structuring sections so that Windows and Linux guidance are parallel, rather than Windows-first.
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
Powershell Heavy
Missing Linux Example
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets, but there are subtle signs of Windows bias. While the JSON extension snippet references both 'ServiceFabricLinuxNode' and 'ServiceFabricNode', the example settings (e.g., 'dataPath': 'D:\\SvcFab') use Windows-style paths. Additionally, the 'Next steps' section links to PowerShell scripts for RDP port changes and admin credential updates, which are Windows-centric tasks, without mentioning equivalent Linux guidance or SSH examples.
Recommendations
- Provide Linux/Unix-style examples for paths (e.g., '/var/svcfab') alongside Windows paths in configuration snippets.
- Add links or guidance for managing Linux nodes, such as SSH access, changing SSH port ranges, and updating Linux admin credentials.
- Ensure parity in 'Next steps' by including Linux-focused operational tasks and scripts.
- Clarify when examples are Windows-specific and offer Linux alternatives where possible.
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, but does not include equivalent Linux/macOS CLI or scripting examples (e.g., Bash, Azure CLI). PowerShell is featured prominently and exclusively for command-line configuration, suggesting a Windows-centric approach. There is no mention of Linux tools or cross-platform alternatives, and PowerShell examples are shown before any Linux equivalents (which are missing).
Recommendations
- Add Azure CLI examples for configuring placement policies, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash or shell script snippets where applicable, especially for service deployment and configuration.
- Explicitly mention whether the PowerShell commands can be run on PowerShell Core (cross-platform) or if they are Windows-only.
- Provide guidance for Linux/macOS users on how to achieve the same configurations, referencing relevant tools or APIs.
- Clarify any platform-specific limitations or requirements for Service Fabric clusters (e.g., if certain policies are only supported on Windows nodes).
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
Windows First
Summary
The documentation page provides only PowerShell and C# examples for managing Application Groups in Service Fabric clusters. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API) are given. The PowerShell examples are consistently presented before C# code, reinforcing Windows-first patterns. There is no mention of Linux-native tools or cross-platform approaches, creating friction for Linux/macOS users.
Recommendations
- Add Azure CLI examples for all operations (creation, update, querying, removal) alongside PowerShell.
- Include REST API sample calls for managing Application Groups, which are platform-agnostic.
- Explicitly note any limitations or differences for Linux-based Service Fabric clusters, if applicable.
- Consider Bash scripting examples or references to cross-platform tools where possible.
- Clarify whether PowerShell examples are usable on PowerShell Core (cross-platform) or only Windows PowerShell.
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 configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json) deployments, but consistently presents Windows-specific XML examples first and includes PowerShell commands for service creation and updates without equivalent Linux CLI or SDK examples. The use of WindowsServer in XML examples and PowerShell for operational tasks may create friction for Linux users, though JSON-based configuration and .NET SDK examples are also present.
Recommendations
- Present Linux/standalone (ClusterConfig.json) examples before or alongside Windows (ClusterManifest.xml) examples to avoid Windows-first ordering.
- Add equivalent Linux CLI (e.g., Azure CLI, sfctl) or bash script examples for service creation and updates, alongside PowerShell commands.
- Clarify when XML examples are Windows-only and when JSON examples are cross-platform, to help users identify relevant sections.
- Explicitly mention Linux support for standalone Service Fabric clusters and link to Linux-specific operational 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 code examples for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash scripts) are provided. The PowerShell examples are given alongside C# code, but there is no mention of cross-platform tools or patterns for Linux users. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other scripting environments.
Recommendations
- Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Mention Bash scripting or REST API usage for metric configuration and dynamic load reporting, with sample commands.
- Clarify whether the PowerShell commands can be run in PowerShell Core (which is cross-platform) or if they require Windows PowerShell.
- Provide guidance or links for Linux/macOS users on how to perform equivalent operations without PowerShell.
- Consider reordering examples so that cross-platform tools are shown first or alongside Windows-specific tools.
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 First
Missing Linux Example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters exhibits Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. There are no Linux-specific examples, tools, or instructions, and the terminology and guidance assume a Windows environment, despite standalone clusters being theoretically cross-platform.
Recommendations
- Add equivalent Linux instructions, including examples using Bash, CLI, or relevant Linux tools for cluster manifest querying and configuration upgrades.
- Clarify whether standalone Service Fabric clusters can be managed on Linux, and if so, provide parity in documentation for Linux users.
- If PowerShell is required on Linux, explicitly state this and provide installation guidance.
- Link to or create Linux-specific guides for scaling standalone clusters, if supported.
Service Fabric
Upgrade an Azure Service Fabric standalone cluster
...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., service-fabric-cluster-upgrade-windows-server.md, service-fabric-cluster-config-upgrade-windows-server.md) and the Patch Orchestration Application for Windows. There are no explicit Linux examples, tools, or links to Linux-specific upgrade/configuration documentation. The page does not clarify whether Linux clusters are supported or provide guidance for Linux users.
Recommendations
- Add explicit guidance or links for upgrading Service Fabric standalone clusters running on Linux, if supported.
- Provide Linux-specific examples or documentation references alongside Windows ones.
- Clarify in the introduction whether the guidance applies to both Windows and Linux clusters, or is Windows-only.
- Mention Linux equivalents for patch orchestration or cluster configuration, if available.
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 Service Fabric service move cost, but does not offer equivalent Linux CLI or bash examples. PowerShell is primarily a Windows tool, and its exclusive use in examples creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before C# code, reinforcing a Windows-first bias. No Linux-native tools or commands (such as Azure CLI or REST API) are mentioned for these operations.
Recommendations
- Add equivalent Azure CLI or REST API examples for configuring and updating move cost, which are cross-platform and usable from Linux/macOS.
- Explicitly mention whether PowerShell commands can be run on Linux/macOS (via PowerShell Core), or clarify if they are Windows-only.
- Consider providing bash or shell script examples for common operations, or link to relevant cross-platform tooling.
- Reorder examples so that cross-platform methods (Azure CLI, REST API) are shown before or alongside PowerShell.
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 PowerShell examples for managing node tags and service requirements, but does not offer equivalent Linux/macOS command-line examples (such as Azure CLI, Bash, or REST API usage). PowerShell is primarily a Windows tool, and its prominence creates friction for Linux/macOS users. The documentation also references PowerShell before C# APIs and omits mention of cross-platform tools or workflows.
Recommendations
- Add examples using Azure CLI or REST API for managing node tags and service requirements, as these are cross-platform and accessible to Linux/macOS users.
- Explicitly state whether PowerShell commands are supported on Linux/macOS (via PowerShell Core), and provide guidance if so.
- Consider including Bash or shell script examples where appropriate, or reference relevant Service Fabric CLI tools if available.
- Reorder examples so that cross-platform tools (REST API, CLI) are presented before or alongside PowerShell.
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 extensive PowerShell examples for configuring service sensitivity and maximum load in Azure Service Fabric, but does not offer equivalent Linux/macOS CLI examples (such as Bash, sfctl, or REST API). The PowerShell-centric approach and references to Windows tools may create friction for Linux users, even though Service Fabric supports cross-platform management.
Recommendations
- Add equivalent examples using sfctl (Service Fabric CLI) for Linux/macOS users, especially for service creation and updates.
- Include REST API examples for configuring sensitivity and maximum load, which are platform-agnostic.
- Explicitly mention cross-platform support and clarify which tools are available on each OS.
- Reorder sections so that cross-platform or platform-agnostic methods (e.g., Application Manifest, REST API) are presented before Windows-specific tools like PowerShell.
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 for securing an Azure Service Fabric cluster consistently presents Windows-specific guidance and links before Linux equivalents, and omits explicit instructions or links for securing standalone Linux clusters. While the concept of certificate-based security is described as applicable to both Windows and Linux, practical setup instructions and references are only provided for Windows standalone clusters, leaving Linux users without clear guidance.
Recommendations
- Add explicit instructions and links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
- Ensure that examples and guidance for both Windows and Linux are presented in parallel, or clarify when features are Windows-only.
- Include references to Linux-compatible certificate management tools and patterns (e.g., OpenSSL, Linux certificate stores) where relevant.
- If Linux standalone clusters are not supported, state this clearly to avoid confusion.
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-centric tools and patterns, such as ETW/Windows Event logs and the Windows Azure diagnostics agent, without mentioning Linux equivalents or providing Linux-specific guidance. The examples and instructions focus on Windows mechanisms for event access and monitoring, and Windows tools are mentioned first and exclusively.
Recommendations
- Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration for Linux).
- Mention Linux-compatible diagnostics agents or methods, such as Azure Monitor agent for Linux, and clarify any differences in event collection and visualization.
- Provide examples or links for querying and analyzing Service Fabric events from Linux environments, including REST API usage and integration with cross-platform tools.
- Clearly state any limitations or differences in event access between Windows and Linux clusters, if applicable.
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
Summary
The documentation provides general guidance for upgrading Azure Service Fabric clusters, but there are subtle signs of Windows bias. For example, in the 'Upgrading OS images for cluster nodes' section, the only linked guidance is for patching Windows operating systems, with no mention of Linux node patching. Additionally, PowerShell is mentioned as a management tool alongside Azure CLI, but Linux-specific tools or workflows are not highlighted. Windows-related documentation is referenced first or exclusively in some sections, potentially creating friction for Linux users.
Recommendations
- Add explicit guidance or links for patching/upgrading Linux node OS images in Service Fabric clusters, if supported.
- Ensure examples for cluster management (certificates, ports, etc.) include both PowerShell and Bash/Azure CLI commands, or clarify parity.
- Mention Linux support and limitations where relevant, especially in sections referencing Windows-specific features or tools.
- Provide links to Linux-specific Service Fabric documentation where available.
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
Missing Linux Example
Windows Tools
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 any Azure CLI or Bash equivalents. The packaging step relies on Visual Studio, a Windows-centric tool, and the directory structure uses Windows path conventions. There are no Linux/macOS-specific instructions or alternatives provided, and Windows tools are referenced before any cross-platform options.
Recommendations
- Add Azure CLI examples for deployment and deletion alongside PowerShell cmdlets.
- Provide guidance for packaging applications using cross-platform tools (e.g., dotnet CLI, SF SDK, or manual zip commands) instead of only Visual Studio.
- Include Linux/macOS path conventions and instructions where relevant.
- Mention that the Azure portal and Resource Manager templates are platform-agnostic, and clarify any steps that are Windows-only.
- Where screenshots or instructions reference Windows UI/tools, add notes or alternatives for Linux/macOS users.
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 using PowerShell and C#, with no equivalent Linux CLI or scripting examples. Windows tools (PowerShell cmdlets) are referenced exclusively for cluster and service management, and Linux alternatives are not mentioned or demonstrated. The 'Choosing a platform' section does acknowledge Linux, but only in the context of implementation differences, not in operational guidance.
Recommendations
- Add equivalent Linux CLI examples (e.g., using Azure CLI, Bash scripts, or Service Fabric CLI) alongside PowerShell examples.
- Reference Linux management tools and workflows where PowerShell cmdlets are mentioned.
- Explicitly state when a feature or example is Windows-only, and provide Linux alternatives or note limitations.
- Ensure Linux operational guidance is present for tasks like scaling services, creating/removing instances, and cluster management.
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 is a cross-platform technology. However, there are several areas where Windows-specific tools, services, and patterns are mentioned first or exclusively, such as references to Windows services (FabricHost.exe), PowerShell cmdlets, and standalone cluster creation only for Windows. Linux equivalents are sometimes missing or mentioned later. This creates friction for Linux users, especially in cluster management and lifecycle operations.
Recommendations
- Ensure that CLI (sfctl) examples and references are given equal prominence to PowerShell, especially in lifecycle and health monitoring sections.
- Add explicit Linux examples and instructions where only Windows or PowerShell are mentioned, such as cluster creation, management, and scaling.
- Clarify which features are Windows-only and which are cross-platform, ideally with side-by-side comparison tables.
- Provide links to Linux-specific documentation and tools in 'Next steps' and throughout the page.
- Mention Linux container support and Java programming model earlier, alongside Windows/.NET references.
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
Windows First
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health, with no equivalent example for Linux or cross-platform tools (e.g., Bash, REST, or CLI). PowerShell cmdlets are mentioned before REST APIs, and no Linux-specific guidance or parity is provided for common health reporting tasks.
Recommendations
- Add equivalent examples using cross-platform tools such as Azure CLI, Bash scripts, or REST API calls for health reporting and querying.
- Explicitly mention how Linux/macOS users can perform the same health reporting and querying tasks, referencing any required Service Fabric CLI or REST endpoints.
- Reorder or supplement the 'Health reporting' section to present cross-platform methods (e.g., REST, CLI) before or alongside PowerShell examples.
- Clarify in the example section that PowerShell is one option, and provide links or code snippets for Linux/macOS users.
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, references ApplicationManifest.xml (a Windows-centric deployment artifact), and describes portal-based configuration (which is not supported for Linux clusters). While Linux support is mentioned, Linux-specific instructions, examples, and parity for non-containerized workloads are missing. Windows tools and patterns (PowerShell, Visual Studio, ApplicationManifest.xml) are presented first and exclusively, with no equivalent Linux CLI or YAML-based examples.
Recommendations
- Add Linux-specific instructions for enabling DNS service, including CLI (az, sfctl) or ARM template workflows.
- Provide examples for setting DNS names using Linux-compatible tools (e.g., sfctl, az CLI, YAML manifests for containerized workloads).
- Clarify limitations for Linux clusters and offer guidance/workarounds for Linux users (e.g., how to enable DNS service without portal access).
- Include sample workflows for Linux containerized services, such as Docker Compose or Kubernetes YAML, to demonstrate DNS integration.
- Balance the order of examples so Linux approaches are presented alongside or before Windows-specific tools.